Develop Bugs

[Q] Crashing on Bootloader / Display Tear

OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?

So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?

What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.

can you still get to the bootloader and is it stable to sit on the bootloader?

I can get to the boot loader but it is not stable there (I think I was conflating the two.)

does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)

try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?

I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.

i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock

Wow, same crash while in download mode. That can't be good...

yeah thats not good at all. i'd lock the bootloader and return it

http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing

Yeah return to the store and show them this, the board is probably bad.

thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html

Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.

What is this screen, and how do I stop this from happening?

I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA

That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.

jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA

Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)

jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA

[Q] [Battery level is too low] on stock rom, can't charge

battery level is too low
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no cwm, no root, no falsh anything.
Last night, I play game when I have charging too, HOX is so hot.
It say unable to charge.
I unplug and plug it again.
In a few minute, it was empty battery.
I charge and try to power on, but it 's nothing happen.
There is only red LED blink.
Now I just open HBoot mode "volume down + power", and can't do anything.
Helppppppp me
Thanks.

Just try to leave your device plugged in charge for at least one hour and then try to switch it on.
Hope that this will help you.

omar_bazaraa said:
Just try to leave your device plugged in charge for at least one hour and then try to switch it on.
Hope that this will help you.
Click to expand...
Click to collapse
I have tried.
These is always blinking red LED and hot when I was charged.
Is it abnormal?

i-Hatcha said:
I have tried.
These is always blinking red LED and hot when I was charged.
Is it abnormal?
Click to expand...
Click to collapse
My device always get warm when the battery is low.
You can't switch your device after charging it for about one hour ??

I'm trying to "Factory reset" in HBoot mode.
But it 's fail, HOX was turned off itself.
Trying to charge on recovery mode.
but nothing change. (stock rom)
Trying to wall charge for 10 minute.
Blinking red LED and hot. >> Look like battery nothing change.
I have searched many thread, they said it like I should flash custom recovery and rom?
That 's only way to solved this problem?
Or should I send it to HTC warranty?

omar_bazaraa said:
My device always get warm when the battery is low.
You can't switch your device after charging it for about one hour ??
Click to expand...
Click to collapse
Ok, I will try it for 1 hour.

You can also try to flash custom recovery then charge your device on it.

omar_bazaraa said:
My device always get warm when the battery is low.
You can't switch your device after charging it for about one hour ??
Click to expand...
Click to collapse
Yes!
I can't switch on my HOX after charging for 1 hour!!!!!
I can't "volume down + power On" without charging plugged in.
What should I do next?

i-Hatcha said:
Yes!
I can't switch on my HOX after charging for 1 hour!!!!!
I can't "volume down + power On" without charging plugged in.
What should I do next?
Click to expand...
Click to collapse
Try to flash custom recovery, lunch it then try charging again.
Wiping data from custom recovery is recommended.

omar_bazaraa said:
Try to flash custom recovery, lunch it then try charging again.
Wiping data from custom recovery is recommended.
Click to expand...
Click to collapse
Thank you so much.
I will try them.

i-Hatcha said:
Thank you so much.
I will try them.
Click to expand...
Click to collapse
I'm waiting...
Hope you will solve it.

Guys i know you try to help ....but .....
He's fully locked. Never tell somebody to unlock it and try to fix it. First is sending it in for warranty !!!!!
I see too many replies with incomplete or wrong info lately !
Read up first yourself and know what to do ! This is good advice ...not mented badly

Mr Hofs said:
Guys i know you try to help ....but .....
He's fully locked. Never tell somebody to unlock it and try to fix it. First is sending it in for warranty !!!!!
I see too many replies with incomplete or wrong info lately !
Read up first yourself and know what to do ! This is good advice ...not mented badly
Click to expand...
Click to collapse
The reason of my replies is that I'm sure that 90% of people won't create a new thread and wait for this reply (Send your device to HTC service). In addition, the thread written by mike1986 >> http://android-revolution-hd.blogspot.com/2013/03/unlocking-bootloader-or-flashing-custom.html .
Anyway, thanks.

Om not talking about making new threads. When somebody comes in with a full locked bootloader never tell them to unlock it. They will deny warranty when it appears to be a software problem. That article is nice.....but certainly does not count for everybody. 100% warranty with a locked bootloader no discussion there. Why take the risk ?
Unlocking is a absolute last resort !

Mr Hofs said:
Om not talking about making new threads. When somebody comes in with a full locked bootloader never tell them to unlock it. They will deny warranty when it appears to be a software problem. That article is nice.....but certainly does not count for everybody. 100% warranty with a locked bootloader no discussion there. Why take the risk ?
Unlocking is a absolute last resort !
Click to expand...
Click to collapse
Okay, I'll take with your advice next time.
+1 thanks to you.

I know what Mr Hofs said.
I understand what omar_bazaraa reasons too.
Very thanks everybody for help to solved this.
I ever unlock, but I just got new mainboard for 2 month ago.
And now I have new "Locked" which don't wanna do anything yet.
I just wait official stock rom 4.2.2.
-------------------------------
After my false yesterday, I just goodluck on this time.
I try to factory reset, but I have no luck.
It was die when screen is showing "phone reset" image.
So I have tried to unlock bootloader.
Try to charge it for boot to Fastboot mode.
First time, Hox was switched off itself after I get code.
I have tried again (flash unlock bin), it was showed message successful.
But "Accept unlock permission" screen never show, then it was turned off itself again.
At this time, this is strange, HOX is charging!!!
Now, I have factory reset and lunch it on stock rom which HBoot is "Locked"
Thank you again.:victory:

i-Hatcha said:
I know what Mr Hofs said.
I understand what omar_bazaraa reasons too.
Very thanks everybody for help to solved this.
I ever unlock, but I just got new mainboard for 2 month ago.
And now I have new "Locked" which don't wanna do anything yet.
I just wait official stock rom 4.2.2.
-------------------------------
After my false yesterday, I just goodluck on this time.
I try to factory reset, but I have no luck.
It was die when screen is showing "phone reset" image.
So I have tried to unlock bootloader.
Try to charge it for boot to Fastboot mode.
First time, Hox was switched off itself after I get code.
I have tried again (flash unlock bin), it was showed message successful.
But "Accept unlock permission" screen never show, then it was turned off itself again.
At this time, this is strange, HOX is charging!!!
Now, I have factory reset and lunch it on stock rom which HBoot is "Locked"
Thank you again.:victory:
Click to expand...
Click to collapse
Glad to know that you managed to solve your problem.
Good luck. :good:

Stock HTC One (M8) in boot lock - please help

Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) . Picture IMAG1839.jpg is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) .
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil

did you Factory Reset while at fastboot mode?

Factory Reboot
aM- said:
did you Factory Reset while at fastboot mode?
Click to expand...
Click to collapse
Hi,
Yes - I did try a factory reset but this didn't resolve the problem and it literally rebooted immediately without appearing to do anything.
Thanks
Phil

PhillipLegg said:
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg) View attachment 2966734 which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) View attachment 2966736. Picture IMAG1839.jpg View attachment 2966735is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) View attachment 2966747.
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
Click to expand...
Click to collapse
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.

Battery Pull
xunholyx said:
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Click to expand...
Click to collapse
Hi, it was a good idea - but unfortunately this hasn't resolved the problem. Sounds like it's going away for repair unless any other forum users have a stroke of inspiration. It does feel like something has overwritten or corrupted the bootup code somehow!! At least it doesn't feel like anything I've done so warranty is still in place
Thanks for your help.

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.

Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.

Anyone ?

yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there

debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?

xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.

debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.

With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.

debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.

XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here