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

Help unrooting HTC Evo 4G

First I apologize if there is already a post for this question. This is my situation. A friend of mine has the HTC Evo 4g, it was purchase through Page plus. The phone appears to be rooted.
I'd like to unroot the phone, restore it to its original rom so I can add it to my sprint account. Is this possible? And if so, any help will be greatly appreciated. I have never rooted a phone, so I will need step by step instructions.
Thnx in advance, Charles
View attachment 1246904

Please post what it says on the bootloader screen. pull the battery, reinstall it, hold vol up, hold power. After a few seconds it will boot into a text screen. Is it unlocked? S-on or s-off? and what it the hboot version?

koker93 said:
Please post what it says on the bootloader screen. pull the battery, reinstall it, hold vol up, hold power. After a few seconds it will boot into a text screen. Is it unlocked? S-on or s-off? and what it the hboot version?
Click to expand...
Click to collapse
Pull the battery out put it back in hold volume down and power at the same time wait until a white screen comes up post a pic of that
Sent from my PC36100 using xda premium

{
"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"
}
koker93 said:
please post what it says on the bootloader screen. Pull the battery, reinstall it, hold vol up, hold power. After a few seconds it will boot into a text screen. Is it unlocked? S-on or s-off? And what it the hboot version?
Click to expand...
Click to collapse

Cperrry1 said:
View attachment 1247473
View attachment 1247473
Click to expand...
Click to collapse
Not sure why you think it's rooted, because it's not. That's stock as can be.
----------------------
Current Device: HTC EVO 4G LTE | ROM: Viper4G 1.0.0 | Kernel: 3.0.8-AwesomeSauce1.2

Captain_Throwback said:
Not sure why you think it's rootedw, because it's not. That's stock as can be.
----------------------
Current Device: HTC EVO 4G LTE | ROM: Viper4G 1.0.0 | [cB]Kernel:[/B] 3.0.8-AwesomeSauce1.2
Click to expand...
Click to collapse
So i should be able to activate the phone on my sprint plan then. When i try to do an update i get the red triangle. When i try download apps i get an error. I did a factory reset, and its the same problem. Also the phone starts reseting like there isnt enough memory but it plenty availble. May be a bad phone.
Thnx for ur help an any ideas would be appreciated.
Charles

Cperrry1 said:
So i should be able to activate the phone on my sprint plan then. When i try to do an update i get the red triangle. When i try download apps i get an error. I did a factory reset, and its the same problem. Also the phone starts reseting like there isnt enough memory but it plenty availble. May be a bad phone.
Thnx for ur help an any ideas would be appreciated.
Charles
Click to expand...
Click to collapse
The red triangle is the stock recovery. What update are you trying to do? The software update? That has nothing to do with activating the device.
You should probably download and run the RUU for your software version, to essentially start you from scratch. However if the device was activated on carrier, and you're trying to get it working on Sprint, that might pose a different problem. You'll probably need to call Sprint.
And I'm still curious to know what made you say that it appears to be rooted. The fact that it wouldn't activate? Rooting doesn't prevent that.

Captain_Throwback said:
The red triangle is the stock recovery. What update are you trying to do? The software update? That has nothing to do with activating the device.
You should probably download and run the RUU for your software version, to essentially start you from scratch. However if the device was activated on carrier, and you're trying to get it working on Sprint, that might pose a different problem. You'll probably need to call Sprint.
And I'm still curious to know what made you say that it appears to be rooted. The fact that it wouldn't activate? Rooting doesn't prevent that.
Click to expand...
Click to collapse
I read on line to check if a phone is rooted to download a root app from the google play store and it downloaded fine, but I didnt check to see if the app worked. Most apps download but I get an error with most.

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

HELP! SYSTEM DESTROYED / LOCKED BOOTLOADER

First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!

Please help...

ronniem18 said:
Please help...
Click to expand...
Click to collapse
Brother it is nit destroyed you have to wait a while to foramate the phone after relocking boot loader it will erase your all data from phone and restart the device .

ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available.
Click to expand...
Click to collapse
ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
If you are in this situation then simply flash redmi fastboot rom first and try it would suerly boot your device to orginal version or your problem will be solved

ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
Did you find a solution?

ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
....

hello, please help me, my system is destroyed and at the same time I can’t enter the recovery
{
"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"
}