[Q] Temporary brick - Nexus 5 Q&A, Help & Troubleshooting

Yesterday a strange thing occured to me. My phone got bricked but a simple battery re-plug was enough to fix it. Here's what's happened:
For about 2 weeks it had been telling me that there's new update available (4.4.3., I think), but I've downloaded and installed several times. After every reboot (after downloading and installing update) the notification about it popped up again. So the last time I did it, I plugged in the cable during the update (even though the power was at 82%) and when I came back, the phone was bricked. I could only start it if it was powered by a cable and after the "Google with the padlock at the bottom" screen it went dark again. Same thing with Recovery boot. I thought I would need to factory reset, but then I tried pulling the battery out and plugging it back in and the device is fine.
I have a rooted 32GB, bootloader version HHZ11k. Any idea what might have caused this issue and how to avoid it in the future?

Intresting. A lot of people's phone got bricked and behaving similar. Like bootloader gets locked after unlocik. Emmc acts like it is write protected or something. Maybe a simple battery replug could solve this issue?
Tapatalk-kal küldve az én Nexus 5-el

dexvility said:
Yesterday a strange thing occured to me. My phone got bricked but a simple battery re-plug was enough to fix it. Here's what's happened:
For about 2 weeks it had been telling me that there's new update available (4.4.3., I think), but I've downloaded and installed several times. After every reboot (after downloading and installing update) the notification about it popped up again. So the last time I did it, I plugged in the cable during the update (even though the power was at 82%) and when I came back, the phone was bricked. I could only start it if it was powered by a cable and after the "Google with the padlock at the bottom" screen it went dark again. Same thing with Recovery boot. I thought I would need to factory reset, but then I tried pulling the battery out and plugging it back in and the device is fine.
I have a rooted 32GB, bootloader version HHZ11k. Any idea what might have caused this issue and how to avoid it in the future?
Click to expand...
Click to collapse
No such thing as "temporary brick" or "soft-brick". Those terms are ridiculous. If your phone were to be bricked, it would not turn on, would not boot into recovery, would not boot into bootloader, and would not boot into the secondary bootloader. Your device would be completely dead.
Since you're rooted you can't take the OTA normally, you have to flash the OTA.zip in recovery manually. Which is why it tells you that there's a new update, because you never successfully updated in the first place.
I suggest you read these:
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

Related

[Q] Restart loop(not bootloop) - really weird

Hey lads,
I got a really weird problem and I've tried nearly everything I can think of. I had EMUI 2.3(b121sp06) and I tried the online OTA update to b307 if I remember right(was automatically suggesting the update) and at the update screen it loaded to about 99% and then stopped. Said not to press power while on this screen but obviously it wasn't going to finish. So I reset the phone and it started the "recovery loop", so basically keep trying to apply the update. I had to flash CWM to break out and flashed the whole system by hand(recovery,system,boot,cache,cust and userdata img files) and it starts up but it keeps resetting and seemingly it's random. Android boots up, I don't touch the phone--> boom reset. Weird thing is it even does it in recovery.
If I really want to explain the problem it's like as if my finger got stuck on the power button(that naturally made me think that the button might be f*cked), but booting into fastboot and not having resets cleared my suspicion. What I also noticed is that every time it boots up it doesn't recognize the sim card and I have no signal or whatsoever.
Tried multi tool unbricking method -> doesn't work
Tried factory reset from stock recovery(had to be fast so it doesn't reset before) ->doesn't work
Tried wiping dalvik cache and factory reset from CWM ->doesn't work
Tried killing battery by letting it keep resetting -> battery drained, reset loop stopped ->put the phone on charger->reset loop started again
I have no f*cking clue how can I get out of this, will keep trying though. Any help is appreciated, thank you!
Hi
Did you try to remove the Sd Card ? Honor 6 reboot is often due to faulty SD Card.
Which model do you have ? L04 ?
B307 upgrade sure ?
Seb
Yes, that was my first idea, still does it though. I have the L02 and I'm not positive it was b307, but it started with 3, could be b303 if there is one.
I don't know for L02 but for L04 there is a Full ROM that you can flash with the three buttons method. (Vol+,Vol-, power and put the ROM in /dload folder on the SD card).
Maybe there is such thing for L02 ?
There is, but as I said the phone restarts even in recovery. It's like the phone restarts every 30 secs except for fastboot.
if it's not SD card or internal flash problem so, it seems to be hardware related to me (
Would make sense but it occurred only after I tried OTA. Would be really surprised if that killed that hardware :-/
xXPhoenixXx said:
Would make sense but it occurred only after I tried OTA. Would be really surprised if that killed that hardware :-/
Click to expand...
Click to collapse
Have u fixed the issue yet????
kamalnath93 said:
Have u fixed the issue yet????
Click to expand...
Click to collapse
Unfortunately not, I'm out of ideas, trying to negotiate with the seller to sort something out, I think the phone is beyond saving
Same thing happened with me. Don't have any solution. Have you fixed it?
xXPhoenixXx said:
Hey lads,
I got a really weird problem and I've tried nearly everything I can think of. I had EMUI 2.3(b121sp06) and I tried the online OTA update to b307 if I remember right(was automatically suggesting the update) and at the update screen it loaded to about 99% and then stopped. Said not to press power while on this screen but obviously it wasn't going to finish. So I reset the phone and it started the "recovery loop", so basically keep trying to apply the update. I had to flash CWM to break out and flashed the whole system by hand(recovery,system,boot,cache,cust and userdata img files) and it starts up but it keeps resetting and seemingly it's random. Android boots up, I don't touch the phone--> boom reset. Weird thing is it even does it in recovery.
If I really want to explain the problem it's like as if my finger got stuck on the power button(that naturally made me think that the button might be f*cked), but booting into fastboot and not having resets cleared my suspicion. What I also noticed is that every time it boots up it doesn't recognize the sim card and I have no signal or whatsoever.
Tried multi tool unbricking method -> doesn't work
Tried factory reset from stock recovery(had to be fast so it doesn't reset before) ->doesn't work
Tried wiping dalvik cache and factory reset from CWM ->doesn't work
Tried killing battery by letting it keep resetting -> battery drained, reset loop stopped ->put the phone on charger->reset loop started again
I have no f*cking clue how can I get out of this, will keep trying though. Any help is appreciated, thank you!
Click to expand...
Click to collapse
Its might be a battery problem Or power flex cable. Try to turn on the phone during charge
guys im facing the same problem now... waiting for any solutions
I have tried stop & uninstall some app
I've tried as quickly as I can when the phone (nokia x) is on, then I stop> uninstall I consider potentially cause this problem (facebook, whatsapp, uc browser) and then it managed to prevent the continuous restarts. but problems arise even though the application had me uninstall and then I restart the phone. and it is back again, I uninstalled the app that has remained with the error settings and restart repeatedly. who knows what else : '(
xXPhoenixXx said:
Hey lads,
I got a really weird problem and I've tried nearly everything I can think of. I had EMUI 2.3(b121sp06) and I tried the online OTA update to b307 if I remember right(was automatically suggesting the update) and at the update screen it loaded to about 99% and then stopped. Said not to press power while on this screen but obviously it wasn't going to finish. So I reset the phone and it started the "recovery loop", so basically keep trying to apply the update. I had to flash CWM to break out and flashed the whole system by hand(recovery,system,boot,cache,cust and userdata img files) and it starts up but it keeps resetting and seemingly it's random. Android boots up, I don't touch the phone--> boom reset. Weird thing is it even does it in recovery.
If I really want to explain the problem it's like as if my finger got stuck on the power button(that naturally made me think that the button might be f*cked), but booting into fastboot and not having resets cleared my suspicion. What I also noticed is that every time it boots up it doesn't recognize the sim card and I have no signal or whatsoever.
Tried multi tool unbricking method -> doesn't work
Tried factory reset from stock recovery(had to be fast so it doesn't reset before) ->doesn't work
Tried wiping dalvik cache and factory reset from CWM ->doesn't work
Tried killing battery by letting it keep resetting -> battery drained, reset loop stopped ->put the phone on charger->reset loop started again
I have no f*cking clue how can I get out of this, will keep trying though. Any help is appreciated, thank you!
Click to expand...
Click to collapse
Hey I tried to root my phone and its stuck in the same restart loop. I am trying to install some roms, CM or stock. U also try and let me know if it works.
Kuber.ksp said:
Hey I tried to root my phone and its stuck in the same restart loop. I am trying to install some roms, CM or stock. U also try and let me know if it works.
Click to expand...
Click to collapse
my phone is working only on charhing.. pufffff
snrtrt said:
my phone is working only on charhing.. pufffff
Click to expand...
Click to collapse
Did you follow the guide here?
Sent from my Honor 8 using XDA Labs
In the past my battery lost it's endurance pretty much. Furthermore I've read that a defective battery causes lots of weird behaviours on our Honor 6, which was the same to mine.
In my case a replacement of the battery worked well, to get my Honor 6 back to life:
https://www.youtube.com/watch?v=ceyzXavxFAw
It's not that difficult and lasts approx. 30-45 mins. Spare Batteries are available for 6 - 10 bucks on ebay or directly from the chinese internet stores.
Borg666 said:
In the past my battery lost it's endurance pretty much. Furthermore I've read that a defective battery causes lots of weird behaviours on our Honor 6, which was the same to mine.
In my case a replacement of the battery worked well, to get my Honor 6 back to life:
It's not that difficult and lasts approx. 30-45 mins. Spare Batteries are available for 6 - 10 bucks on ebay or directly from the chinese internet stores.
Click to expand...
Click to collapse
It's really important that we use original chargers for the health of our device.

[Q] Trouble flashing Stock & Custom ROM's

So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.

Lenovo K4 Note (A7010). Won't power up. How to recover?

Ok so, I flashed a CM13 rom on a K4 Note (16GB internal and 3GB ram version). I pretty much followed all the steps required for flashing - unlocked bootloader - installed TWRP - wiped (factory reset) - flashed the Rom. Now, the phone booted up alright and worked for a day. The phone doesn't belong to me, and the owner decided that he wanted to factory reset it one more time. Since I also wamted to show him how TWRP functions, I booted into recovery via the advanced boot option in Cyanogen (Did not use the key combination). So this phone turns off and decides not to start. I waited for some time and decided to manually power it up. It won't. I held down the key for about 5 minutes and yet, to no avail. Not even a vibration. No response at all.
So, I would like to understand what happened with the phone, since as far as I can tell, TWRP was working fine. I used the key combo method to boot into TWRP thrice the night before - to flash CM, to flash gapps and to flash thr xposed installer. I can say CM was working fine since I used it for a night to get a hold of any bugs. Nothing went wrong at that time.
So, what can I do now? Since the phone is completely unresponsive and is not being detected upon being connected to the PC, I suppose it's hard bricked. But what cause the brick in the first place? Any possibe way to recover the phone? Is it even hard bricked though?
What about battery charging % frist chik battery I think battery fult
Sent from my GT-I9505 using Tapatalk
Nah, it doesn't charge either. I tried plugging it in and turning it on. It still won't.
It's just sitting there. Doing nothing.

Trying OTA update on Root + BL Unlocked phone has caused plethora of problems.

I recently attempted an OTA update on my Rooted Moto G5 with unlocked Bootloader and TWRP recovery (stupid mistake I know), and since then it has caused a plethora of problems.
First when my phone rebooted to install the update, it would only boot into TWRP recovery, I worked around this by going into Fastboot and going into factory mode.
I still have to do this process every time I startup my phone.
Once I started up my phone I noticed my phone displayed "No Service" and showed I didn't have a signal (I haven't tested whether or not I actually could use cellular services yet)
A day later I went to charge my phone but my phone 'stopped charging' at 10%, I thought it was my plug or cable so I switched sockets.
When I plug my phone in it recognizes its being plugged in however it said 'Not Charging'.
When I restarted my phone and went into TWRP my phone was actually at 13%. When I went into factory mode my phone said it had 13% battery, however still said it wasn't charging.
I haven't attempted to fix anything at the moment, any advice or help would be appreciated.

Question Bricked can't Seem to access anything

Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware

Categories

Resources