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] Galaxy Nexus stuck at Yellow Triangle - Tried many solutions but still DEAD?

Following is the state of my Brother's Galaxy Nexus. NO FASTBOOT Just the Yellow triangle :crying:
{
"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"
}
He said he was flashing a rom when this happened. I have been trying to revive it since yesterday but nothing has been working yet
I first did the OMAPFlash from this thread So I bricked my GNEX...Then brought it back to life!. Even though the OMAPFlash went through but nothing happened on my device unlike in the OP's case wherein he could just power it up back
And then tried to flash the stock firmware from this site Update Firmware of Samsung I9250 Galaxy Nexus . Herer I just couldn't get past the NAND write thing
So all these methods have till now given no results, hence I was forced to create this thread. Hope I get some help/solutions from the experts out here

Someone please help me out

Help me out guys:crying:

I've same thing screaming!
SENT BY POST...

I haven't had anyone confirm this, but i believe that screen seems to indicate a lack of drivers, or improper drivers. I think of it like the exclamation point showing there is no bridge or way to communicate between the devices. I would love if someone could confirm or refute this, though. Perhaps try reinstalling your drivers? Or even the universal naked drivers...

try flash via odin. see my sig

samersh72 said:
try flash via odin. see my sig
Click to expand...
Click to collapse
I tried ODIN flash also but it gets stuck and couldn't get past the NAND write thing

sumru said:
I tried ODIN flash also but it gets stuck and couldn't get past the NAND write thing
Click to expand...
Click to collapse
try my odin package

samersh72 said:
try my odin package
Click to expand...
Click to collapse
Yup I tried that also but operation failed at NAND Write

Unfortunately there is not much you can do if it won't write in odin. Had the same happen to my phone.
Sent from my Galaxy Nexus using xda app-developers app

sumru said:
Yup I tried that also but operation failed at NAND Write
Click to expand...
Click to collapse
retry omap flash https://www.dropbox.com/s/gzcu9fpwwz55u7l/OMAPFlash_tuna.zip
or http://www.4shared.com/zip/gXdZ-Ab8/OMAPFlash_tuna.html

samersh72 said:
retry omap flash https://www.dropbox.com/s/gzcu9fpwwz55u7l/OMAPFlash_tuna.zip
or http://www.4shared.com/zip/gXdZ-Ab8/OMAPFlash_tuna.html
Click to expand...
Click to collapse
Thanks for the links.
Tried OMAP flash and then odin but same thing...gets stuck at NAND write

Guys any solution???

sumru said:
Guys any solution???
Click to expand...
Click to collapse
download attached file, unzip it, flash tar.md5 file via odin as bootloader and not pda. after, try to boot in fastboot mode

It didnt work...FAILED yet again at NAND write

idk if this will help: try older versions of odin.
there is a corrupted partition. see this http://forum.xda-developers.com/showthread.php?t=1667886

samersh72 said:
idk if this will help: try older versions of odin.
Click to expand...
Click to collapse
I tried versions 1.3/1.83/1.85/1.87 and the latest 3.07 but all gave the same result:crying:
samersh72 said:
there is a corrupted partition. see this http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
This seemed pretty confusing and I downloaded the zip file for i9250 and it contained two folders; one with stock pits and other with patched pits.
But couldnt figure as to what needs to be done

try this odin package: http://forum.xda-developers.com/showthread.php?t=1827685

Both didnt work...each time it got stuck at NAND Write

Any help... Hasn't anyone faced such an issue

[Q] Odin stuck at NAND write start

I will keep this brief but thorough:
I've had the phone for 2 years and I've been a flashaholic ever since. I have flashed several ROMs on the phone and I have recovered some goof ups. I recently upgraded to the N5 and passed my E4GT to my wife until I get her a new phone and we jump ship from Sprint. I flashed a stock rooted ICS ROM and past it off to her as if it were a brand new phone, she set it up and went about her week. Yesterday her sister borrows the phone to browse a website (nothing malicious, black friday deals etc). The phone craps out on her and now wont boost past the Galaxy S2 Splash screen. I can't boot into recovery it just hangs on the splash screen no matter how long I hold vol up + pwr. I CAN boot into download mode. I went about the standard method of flashing EL26 recovery to try and factory reset or flash a diff ROM. Odin 1.85 freezes at NAND Write Start. Odin 1.3 doesn't read that the phone is plugged in. The Odin one clicks don't register that the phone is connected either. I tried to reflash the ICS Stock Rooted ROM and it hangs at sbl.bin and eventually fails. The cable and USB ports are not defective, I've switched them up. Are there any means of saving the E4GT?

Do you have the Samsung drivers installed on your computer? Odin won't work without them.
{
"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"
}

bilgerryan said:
Do you have the Samsung drivers installed on your computer? Odin won't work without them.
Click to expand...
Click to collapse
Well...Yes. Like I said I've been flashing things on this phone for 2 years. Although a new issue seems to be that the computer won't recognize it at all now. I tried to reinstall the drivers and it still comes up as unrecognized. No version of Odin recognizes the phone now. Any suggestions are appreciated.

FlipDroid said:
Well...Yes. Like I said I've been flashing things on this phone for 2 years. Although a new issue seems to be that the computer won't recognize it at all now. I tried to reinstall the drivers and it still comes up as unrecognized. No version of Odin recognizes the phone now. Any suggestions are appreciated.
Click to expand...
Click to collapse
Sorry, I've never had any problems with Odin.

bilgerryan said:
Sorry, I've never had any problems with Odin.
Click to expand...
Click to collapse
I don't think Odin is the issue. I'm wondering if the internal memory of the phone died. It won't boot to recovery and if it is plugged in to charge it only shows an empty battery with the charging circle in the middle. It never changes to the battery charging with a green filler despite the battery having a charge.

[Q] Did something very bad! OPPO FIND 7

I was going about flashing my Oppo Find 7 not 7A, succesfully rooted, flashed TWRP, booted into Cyanogenmod 11 successfully. I then went on and attempted to flash cyanogenmod 11s(one plus one system dump) on my Find 7, rebooted, One plus one was split into two on each side of screen, when attempting to go into recovery it was not there anymore and screen was just black. I tried putting back original recovery no luck and tried reflashing with TWRP but still no luck and phone does not boot into anything when turning on. Any help would be deeply appreciated since I can no longer use my new phone.

When completely off, hold power and up, that should put it in fastboot. Can you confirm whether this works or not?
Sent from my Find7 using XDA Premium 4 mobile app

Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next

coscos17 said:
Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next
Click to expand...
Click to collapse
Even if the graphics are messed up in fastboot, it still could work fine.
Download the AndroidSDKSlimCustom here https://www.dropbox.com/s/41p7peig4wt5kav/AndroidSDKSlimCustom.zip
Navigate into platform-tools, hold shift anywhere in that directory and right click while holding shift. Click 'Open command window here'
Turn off your phone completely, take the battery out to be sure, and hold power and volume up until you see something appear on the screen.
Connect the phone via usb, go back to the command window that opened and type
Code:
fastboot devices
If you're lucky you'll get something like this:
{
"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"
}
This means you can then flash TWRP, get into that recovery, wipe everything and ADB sideload a fresh CM nightly (actually made for the find 7!) which you can find here:
http://download.cyanogenmod.com/?device=find7
Let me know how you get on.

I had done that before but still same result, even in recovery the screen looks like it was shifted.

GOT EM! SOLVED!
For anyone else who has this problem use this!
I cant post links cause i am a noob
but in oppo forums look for these
threads/find-7-x9076-bricked-need-help.18112/
/threads/brick-my-oppo-find-7-x9076-doesnt-load-any-recovery.17906/
com/threads/stock-recovery-for-find-7-7a.17397/
and when in stock recovery i flashed X9006&X9076ColorOS_V1.2.1i_full.zip
and BOOM it worked!
Once again thank you Chewbyte for taking the time to answer and try to help me I appreciate it!!

No problem friend, I'm glad you managed to fix it.
Sent from my Find7 using XDA Premium 4 mobile app

just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?

coscos17 said:
just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?
Click to expand...
Click to collapse
I googled your issue around a bit. Try factory reset/clear cache.