Develop Bugs

[Q] Recovering from unusual boot loop

Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.

jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.

RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?

jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there

I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.

This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719

RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.

jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.

jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.

[Q] HTC G2 stuck on boot screen! Help!

My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
ClockworkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Thanks
-Kagen

notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
How did u get it bricked?

xudsa II USERT said:
How did u get it bricked?
Click to expand...
Click to collapse
A friend rooted it over a year ago.
Everything worked fine, so we flashed a ROM. (don't remember which one)
That worked fine, then few days later things on the phone started to fail. Slowly more and more things failed. Then I was forced to reboot the phone.
When I rebooted It stuck on boot screen. now I get those logs in recovered that I originally posted.

To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)

xudsa II USERT said:
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
Click to expand...
Click to collapse
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.

notKagen said:
Yes, I can get there very easily.
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse

EDITED: GAVE EXPLAINATION
notKagen said:
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/

xudsa II USERT said:
EDITED: GAVE EXPLAINATION
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
Click to expand...
Click to collapse
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.

notKagen said:
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
Click to expand...
Click to collapse
Okay, I tried what you said but no success. My ClockworkMod seems to not be mounting. Because of the Errors I posted previously in my first post. So this way I can't flash anything from recovery because it will just stay on that screen with the top hat and the orange circle with the arrow. Nothing happens. If I tap the power button, it just goes back to the menu.
Should I be updating clockwork somehow?
Is there another way to flash?
Could there be a problem with my SD's? (i've tried on 2 different ones)
Do you have any ideas?

This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)

Firstly, don't select stuff with power button in clockwork, use the camera or trackpad.
Secondly, those errors may indicate a bad emmc, which is a hardware defect, and cannot be fixed. More info here
You can either go for a warranty replacement, or you can boot cm7.1 from your sdcard, using Catherall's instructions
-Nipqer

EdWaRdW818 said:
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Click to expand...
Click to collapse
Sure, I can try that. Is there a step by step....don't really know what im doing.

Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium

demkantor said:
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Alrighty! Thanks for your help!

reflash a new ROM
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
Dude This happened to me too first if you downgraded to froyo and if you kept a nandroid backup of it restore to the froyo nandroid backup BE SURE THE NANDROID BAKUP OF THE FROYO VERSION IS A ROOTED ONE OR ELSE YOU'LL BRICK YOUR PHONE OR SCREW UP THE ROOT!! then after that flash another ROM using fastboot in bootloader mode
okay heres what to do
1.Open A CMD window in windows
2.Navigate to the folder where you have fastboot for example cd...
cd...
cd /
C:\Android SDK\Platform Tools
then you should also have ADB at the same folder together with Fastboot
then plug your phone while it fastboot mode in Bootloader
it should say "FASTBOOT USB"
3.Then verify that your computer recognizes your Phone by typing "fastboot devices" without (" ")
4.put the ROM.zip on the same folder where you have Fastboot and ADB
5. type in fastboot clear cache (I don't know the exact command but you need to clear cache)
6. AFTER CLEARING CACHE TYPE IN "fastboot flash zip ROM.zip (REPLACE "ROM" with the right ROM name it ahould be like ICS.zip or whatever your gonna flash
7. just let it do its job
8.Celebrate if it worked =))
PM me if you need more help
SOMEONE PLEASE CORRECT ME IF I DID SOMETHING WRONG
-goodluck

HOX bricked help to flash (no ROM in sd card)

ok i got my phone bricked since i change some fonts ¬¬ yeah its stupid but its done, my htc stays in HTC ONE X splash screen
1.- i already did wipe cache & dalvik (i dont want to try full restore yet)
2.- i cant access to the SD card to put the ROM.zip into it
any idea on how to bring it to life again?? (without losing data)

ok i did a full reset and now its showing only ANDROID label (splash screen) and thats all u.u still bricked, any idea????
is there any way to flash from PC i mean having ROM on PC i dont have it on my HTC

flash lastest clockworkmod and you can mount USB from recovery, copy rom and install as normal.
Sent from my Transformer TF101
@vorticalbox tweet me

what the latest version i got 5.8.4.0 i think this is the latest but i dont know hot to mount USB :/

Yep that's the latest version. Flash it via fastboot:
Put the recovery.img in your fastboot folder and rename it to "recovery.img", then open a command prompt and:
cd..
cd..
cd fastboot
fastboot flash recovery recovery.img
Now extract the boot.img from the ROM you want to flash on your PC, and copy it to your fastboot folder and:
fastboot flash boot boot.img
Then boot into recovery and:
Go to mounts and storage
Choose Mount USB Storage
Copy ROM to your phone
Factory reset
Wipe Dalvik cache
Choose Zip from SD Card
Flash Rom
Reboot and enjoy
If this doesn't work, you'll have to boot into flastboot mode and run the RUU for your phone.
Either way, it's not 'BRICKED'.
Just make sure your battery doesn't go below 30% before you fix it or it will be much more difficult to recover (but not impossible).
It's impossible to totally brick an S-ON One X as whatever happens, you can always get into fastboot mode.

Guys i have problem too. I flashed boot.img with kernel http://forum.xda-developers.com/showthread.php?t=1967897 via this tool http://forum.xda-developers.com/showthread.php?t=1962428
Now phone is bricked. It's only showin "htc quietly brilliant"" logo and i can't do anything. Won't go into fastboot, won't reset at all . Only logo..
Please help me. My hands are shaking.... :|||
EDIT
ok luckily i can restart it, but only restart. I can't turn it off by holding power button.
EDIT 2
Ok i managed to turn bootloader on. There is some hope!!

Einstein001 said:
Guys i have problem too. I flashed boot.img with kernel http://forum.xda-developers.com/showthread.php?t=1967897 via this tool http://forum.xda-developers.com/showthread.php?t=1962428
Now phone is bricked. It's only showin "htc quietly brilliant"" logo and i can't do anything. Won't go into fastboot, won't reset at all . Only logo..
Please help me. My hands are shaking.... :|||
EDIT
ok luckily i can restart it, but only restart. I can't turn it off by holding power button.
EDIT 2
Ok i managed to turn bootloader on. There is some hope!![/QUOTE
try this. http://forum.xda-developers.com/showthread.php?t=1734365
Click to expand...
Click to collapse

Ok guys. I almost had heartattack. By holding vol down buttont and power it went into Bootloader mode. I was able to get into recovery and then used venom flasher to change back to stock kernel. Oh god... Thank you guys trying to help me

Dudes, when its stuck in start up logo doesn't mean its bricked. It's bricked when you can't turn it on or go into bootloader. Please don't use "bricked" to describe every problem you encounter please.
Sent from my HTC One X using xda app-developers app

That is true. What's more I was stupid enough to flash kernel to totally different phone (One XL). Luckily my stupidity was spared this time.
I hope OP will repair his phone too.

Like I said, it's pretty much impossible to 'BRICK' an S-ON device.

What about If you flash a Ron intended for a different phone, doesn't this change the layout of system positions? Or I'm just being stupid and you need s-off to mess things up like that?
Sent from my HTC One X using xda premium

Einstein001 said:
That is true. What's more I was stupid enough to flash kernel to totally different phone (One XL). Luckily my stupidity was spared this time.
I hope OP will repair his phone too.
Click to expand...
Click to collapse
thanks i know how to mount UB from now when this happens my htc is alife again and sorry for the title

Sentinel196 said:
Like I said, it's pretty much impossible to 'BRICK' an S-ON device.
Click to expand...
Click to collapse
and than everybody cry, cause they have no s-off...Guys, You better say thanks for this one, you don`t know how many devices with s-off was bricked for real...

It still cant overwrite the bootloader, firnd you can always repartition by running the RUU
Sent from my HTC One X using xda premium

eltoffer said:
ok i got my phone bricked since i change some fonts ¬¬ yeah its stupid but its done, my htc stays in HTC ONE X splash screen
1.- i already did wipe cache & dalvik (i dont want to try full restore yet)
2.- i cant access to the SD card to put the ROM.zip into it
any idea on how to bring it to life again?? (without losing data)
Click to expand...
Click to collapse
Flash the newest CWM Recovery. Or any recovery with that you can use the option "advanced restore". Now Backup your Rom> wipe everything> restore>advanced restore>restore data only
Here you go
Sry, can one the mods delete this post? My browser is f****** up and didn't show me there are already answers...

I think this qualifies as "bricked"
OK, I am trying to help my sister with her HTC 1X. It will not turn on whatsoever. I hold down the power button, nothing. I hold down the power and one of the volume buttons (up or down), nothing. I hold down the power button and both of the volume buttons, nothing.
I have hooked it up to my laptop because I was able to find some drivers for the device and some files that will allow me to root it, should I be able to get the phone to do anything. Anyway, the only thing I get is a message from Windows saying that the device has malfunctioned and that I should disconnect it and reconnect it or replace the device.
I've scanned through several of the threads but cannot seem to find anyone with as legitimately bricked a 1x as my sister has. I am used to rooting and ROMing Samsung devices and thought I would lend a hand by trying to help out with this HTC device but I cannot get it to even show up in MY Computer.
Any help would be greatly appreciated.

D5S said:
OK, I am trying to help my sister with her HTC 1X. It will not turn on whatsoever. I hold down the power button, nothing. I hold down the power and one of the volume buttons (up or down), nothing. I hold down the power button and both of the volume buttons, nothing.
I have hooked it up to my laptop because I was able to find some drivers for the device and some files that will allow me to root it, should I be able to get the phone to do anything. Anyway, the only thing I get is a message from Windows saying that the device has malfunctioned and that I should disconnect it and reconnect it or replace the device.
I've scanned through several of the threads but cannot seem to find anyone with as legitimately bricked a 1x as my sister has. I am used to rooting and ROMing Samsung devices and thought I would lend a hand by trying to help out with this HTC device but I cannot get it to even show up in MY Computer.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
sounds like you need to activate the warranty

zuadao said:
sounds like you need to activate the warranty
Click to expand...
Click to collapse
Yeah, I was afraid she was going to have to send it back to HTC. What really stinks is that she's only had the phone for 35 days at this point. Started having problems a couple of days ago and ATT doesn't seem to want to do diddly.
Anyway, thanks for the response!

No worries. Pls let us know the outcome. Good luck.
Sent from my HTC One X

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link

[Q] [Nexus 7 - 2013, wifi, 16G]Got stuck at Google logo

Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html

Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279

Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg

How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.

nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en

Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.

nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb

RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.

nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor

nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.

Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:

nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb

Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username

nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol

RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?

RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!

*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?

is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app

Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.

Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.