Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,106 Members 42,534 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Temporary brick

Tip us?
 
dexvility
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 1
Join Date: Feb 2012
Plug [Q] Temporary brick

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?
 
bitdomo
Old
#2  
Senior Member
Thanks Meter 656
Posts: 1,069
Join Date: Nov 2011
Location: Göd
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
 
Lethargy
Old
(Last edited by Lethargy; 20th June 2014 at 09:15 AM.)
#3  
Lethargy's Avatar
Senior Member
Thanks Meter 1,617
Posts: 2,914
Join Date: Jan 2014
Location: Sydney, Australia
Quote:
Originally Posted by dexvility View Post
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?
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/goog...-read-t2784527
http://forum.xda-developers.com/goog...-desk-t2523217
Quote:
Originally Posted by kyphur
You ask us to understand your position. Well if you want to benefit from our experience and time then I think it is only fair that you understand our position.
I actively add ignorant people to my ignore list.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes