My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
thisisjjd said:
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
Click to expand...
Click to collapse
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
charesa39 said:
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Click to expand...
Click to collapse
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
thisisjjd said:
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
Click to expand...
Click to collapse
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051. Pay particular attention to what you need to modify to make sure you don't wipe your userdata.
charesa39 said:
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051.
Click to expand...
Click to collapse
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
thisisjjd said:
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
Click to expand...
Click to collapse
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
charesa39 said:
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
Click to expand...
Click to collapse
I thought I had tried that, but thank you, I'll try again. I appreciate your advice.
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
thisisjjd said:
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
Click to expand...
Click to collapse
Hmm. Unfortunately, this is issue seems beyond my knowledge. That's odd that yesterday it was showing unlocked, and today it randomly is locked. If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
charesa39 said:
That's odd that yesterday it was showing unlocked, and today it randomly is locked.
Click to expand...
Click to collapse
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.
charsea39 said:
If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
Click to expand...
Click to collapse
I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
hector333 said:
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
Click to expand...
Click to collapse
thisisjjd said:
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
Click to expand...
Click to collapse
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary. If you are stuck in a boot loop long press the power button to force a reboot, as soon as the screen turns off press the volume down button that will get you to the bootloader. Or if the device is off press and hold both the power button and volume down button to get to the bootloader. Choose recovery with the volume button then press the power button. You should see android laying down with exclamation mark. Press and hold the power button and while holding the power button press and release the volume up button. Stock recovery! Use the volume button to select "wipe data/factory reset" then press power button. If that doesn't take care of it download the factory image and extract, if running 4.4.2 wifi version you should see ;
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
if you double click the "flash-all.bat" with the device already at the bootloader that will flash the complete image including userdata which wipes the device. You can also open flash-all.bat with notepad and remove -w from the script and it should not flash the userdata.img. Or... you could extract all of the images from the "image-razor-kot49h.zip" and flash them seperately with fastboot, whatever images you try to flash need to be in the same folder as fastboot.exe (platform-tools) so you do have multiple options as long as there is no hardware issue that is causing the reboot. Hope this helps!
wantabe said:
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary.
Click to expand...
Click to collapse
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
thisisjjd said:
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
Click to expand...
Click to collapse
Sorry to hear that! I don't remember ever hearing being able to get into the bootloader but not into recovery from there. Your probably right about having to do doing an RMA. If it's any consolation I had a good experience with ASUS when I had to RMA my 1st gen N7 32GB after the speakers went bad.
I'm glad to hear you had a good experience with ASUS support. I have an RMA and am sending it to them. Thanks for your help.
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
mnunez611 said:
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
Click to expand...
Click to collapse
I would say definitely RMA it. With you having a stock tablet it's not worth risking messing something up trying to fix your tablet and then maybe you can't RMA. I would start with Best Buy and them what their warranty period is. If it is within their stories warranty then take it to them. If not then call ASUS.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Help me
Hello Guys I am stuck in a very annoying situation at the moment which is that my nexus 7 has become inaccessiblhttp://forum.xda-developers.com/images/smilies/eek.gife. This is how it happened
one day I tried to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' errohttp://forum.xda-developers.com/images/smilies/crying.gifr. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
thanks in advance
I have the exact same issue as the OP. Can't get to recovery cause the Google logo hangs there. I can fastboot but the N7 is locked since it was not rooted. Using fast boot and Wugs I get the same thing where it just hangs on erasing userdata for hours. Wondering if any fix has been discovered for this since the OP issue was months ago.
Use fastboot OEM unlock command to unlock the boot loader then re flash stock.
Sent from my Nexus 7
I bought a phone off eBay. User was selling for parts, but the unit turns on and gets to the lockscreen. Seller couldn't get past the lock pattern 9does that mean it's GPE? I use Sense on my other M8). I"m convinced I can bring it back to life.
I can't get it into Bootloader when I power-volume down because I assume Debugging is off. If I could get into bootloader I could unlock it, throw a custom recovery onto it and flash a new ROM. But the key challenge is to get it into Bootloader. Alternatively I was thinking I could reflash a stock executable (not an RUU).
Any ideas?
diceman725 said:
I bought a phone off eBay. User was selling for parts, but the unit turns on and gets to the lockscreen. Seller couldn't get past the lock pattern 9does that mean it's GPE? I use Sense on my other M8). I"m convinced I can bring it back to life.
I can't get it into Bootloader when I power-volume down because I assume Debugging is off. If I could get into bootloader I could unlock it, throw a custom recovery onto it and flash a new ROM. But the key challenge is to get it into Bootloader. Alternatively I was thinking I could reflash a stock executable (not an RUU).
Any ideas?
Click to expand...
Click to collapse
unplug phone, power and vol up for EXACTLY 10 seconds, let go of both, vol down and power till boot loader comes up. Debugging is only for going to boot loader with adb.
If boot loader shows 3 skating androids, you are sense, if it shows android laying on the job, you are gpe. You can convert back as there are many guides to this.
an0ther said:
unplug phone, power and vol up for EXACTLY 10 seconds, let go of both, vol down and power till boot loader comes up. Debugging is only for going to boot loader with adb.
If boot loader shows 3 skating androids, you are sense, if it shows android laying on the job, you are gpe. You can convert back as there are many guides to this.
Click to expand...
Click to collapse
Brilliant. That was easier than I thought. Figured it would take me more than 17 seconds to crack it. Thank you!
diceman725 said:
Brilliant. That was easier than I thought. Figured it would take me more than 17 seconds to crack it. Thank you!
Click to expand...
Click to collapse
The reason you were not able to enter bootloader is probably because Fast Boot was turned on in Power Options which means when you shutdown the phone and then power it up again it will skip the boot loader part and start immediately with the boot animation. You can see that it skips the Splash Screen part
Hi there.
My partner recently tried to update his HTC one m8 Telstra phone. The screen got stuck on "android is upgrading" starting apps. With a little blue loading circle going round and round. Eventually his phone went flat and now the phone will not load past the HTC one powered by android screen. Have tried pressing volume - and power button to go into boot loader and the same thing happens. If I select recovery a little red triangle appears. Have wiped cache. Still no change. If I do factory reset, it goes through the process of "optimizing apps" and then gets stuck on android is upgrading screen etc.
My partner is even more technologically ignorant that I am so he has never done any back ups or anything .
SD card slot does not work (as he ran over his phone last year) however phone has functioned normally for the most part, up until he attempted to update. Please help if possible.
If it is not hardware problem .. only possible to fix it if the bootloader is unlocked.
Why ? because there is no Telstra RUU available, you can only fix it with a nandroid backup
To get to bootloader, press & hold both power + volume up buttons until the screen turns black, release both buttons and press & hold volume down button only to get to hboot. Then select "fastboot" on the menu to get to bootloader screen.
Can you tell what's written on bootloader ? Is it LOCKED, UNLOCKED or RELOCKED ?
Thank you for replying.
Ok so firstly, how do I tell if it's a hardware problem.?
Secondly, although the phone displays a Telstra icon upon startup, my Optus SIM card, well any carrier SIM card really, works in the phone, therefore would it be possible to use another RUU? (What on earth is an RUU?) And nandroid??? Please explain what all these terms mean, if you don't mind of course.
Because his phone screen is damaged from running over it last year, it is hard to see all the information. I'm fairly certain it is still S-on though. Is there any way I could view the boot loader details on a laptop?
I have tried the fastboot option and it still returns to HTC one screen.
How do I get a nandroid back up? Is the phone at all fixable in your opinion? I don't believe it's hard bricked from what I've managed to learn so far, though I could be wrong, as it still goes through the cycle of "optimizing apps" and attempts to start apps after selecting factory reset in boot loader.
I apologise for my lack of knowledge and ignorance on this matter and I appreciate all your help
A lot of your questions are answered here : http://forum.xda-developers.com/showthread.php?p=52484527
I don't say it is really hardware problem, I say if it is not then it is fixable by restoring correct software.
That's why it is important to get to bootloader because most info are available there.
I want you to give the details of what's written there before I can guide you further.
Those details will tell whether that's a Telstra device, whether the device was rooted which may explain the problem and so on.
If you can't get the right button combination works as I mentioned above, then you need to switch it off (maybe let the battery runs out), charge it for a few hours. Take out from charger then press & hold volume down (read again above I mentioned volume up & volume down because which volume button is important) then connect to PC or charger (this comes after you press & hold volume down button not before)
No bootloader .. not possible to fix (unless it is send to HTC centre)
I am able to get to the boot loader screen (I googled so much before posting on here) but most of the information is blacked out due to the screen being wrecked. I will try and gather as much information from what I can see and post here when I get home and I will also try and upload a picture.
Do you have any advice on how I would determine if the issue is due to hardware?
I will provide further information shortly and once again I'm am sincerely grateful for all your help.
Not easy to know it's a hardware issue when it is still can boot-up but bootloop.
hard brick means no response at all (still sometime it is due to no battery)
Ok so here a few photos of the boot loader screen, the fast boot screen and the recovery mode screen. Please bear in mind a lot of (possibly vital) information is not viewable due to screen damage that happened last year.
The most important detail that I need to know is not visible there.
Really need to know whether the bootloader is LOCKED, UNLOCKED or RELOCKED because that portion is blank out with the damage screen.
What you can try ... while on fastboot/bootloader screen (your pic #1), try to install TWRP recovery
Download TWRP 2.8.7.0 from here : https://dl.twrp.me/m8/
Make sure your PC has the required drivers, ADB/fastboot - if not sure, install these :
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
After connecting the device to PC, install the TWRP recovery with command :
fastboot flash recovery twrp-2.8.7.0-m8.img
advise the outcome, if it successful then it is easier to fix the problem.
Ok thanks. I'll download those things and then try that. From what I've learnt so far, I'm pretty certain the boot loader is locked. He got the phone brand new and has done nothing further than change his ringtone, screen display and lock screen. He's worse at technological stuff than I am lol.
Hi,
I am experiencing something very weird with my G4. Started this morning once I got into work.
I woke up, read my messages and then locked the phone while I went to get dressed. Put the phone in my pocket then left for work. When I arrived at work the phone would not unlock. I repeatedly put my unlock code into the keypad and every time it told me it was incorrect.
I hadn't changed the code, and I know what I am putting in is definitely correct, but I still can't unlock my phone to use it.
What can I do!?
Thanks
In addition, I have gone to the Android Device Manager web page and locked my phone from there with a password in the hope I could recover it that way. While my home screen now says it is locked by ADM, it won't let me enter any passwords - there is a pad lock icon on the screen, but thats all and nothing responds to me pressing the screen.
kingdave82 said:
In addition, I have gone to the Android Device Manager web page and locked my phone from there with a password in the hope I could recover it that way. While my home screen now says it is locked by ADM, it won't let me enter any passwords - there is a pad lock icon on the screen, but thats all and nothing responds to me pressing the screen.
Click to expand...
Click to collapse
Sorry for asking the obvious : do you have tried to reboot? It sounds like the gatekeeper service is crashed which should be fixable by just reboot.
If you tried that already:
Do you had enabled USB debugging? If so you can delete the gatekeeper files and after a reboot it will be unlocked.
Or
Is your bootloader unlocked and do you have twrp installed? then you can do the same in twrp.
EDIT
----------
Here are the details if adb or twrp is in place:
https://forum.cyanogenmod.org/topic...crypted-device/?do=findComment&comment=596099
.
Hi ppl,
I've unlocked my bootloader and now, every time i power on the OP3, shows a screen saying my phone is insecure because it is unlocked, and offer key settings to go recovery menu, etc.
It shows about 3 seconds and continues the booting process.
Is there any way to flash my own image or something to hide it (as i did on my old moto g/g3-te)?
Thanks.
Sergio.
Nope, you'll have to live with it.
You can skip that message by pressing power button, but there's no way to remove it.
Sent from my OnePlus 3 using Tapatalk
recrunchi said:
Hi ppl,
I've unlocked my bootloader and now, every time i power on the OP3, shows a screen saying my phone is insecure because it is unlocked, and offer key settings to go recovery menu, etc.
It shows about 3 seconds and continues the booting process.
Is there any way to flash my own image or something to hide it (as i did on my old moto g/g3-te)?
Thanks.
Sergio.
Click to expand...
Click to collapse
Other way of removing that message is to lock the bootloader.
Type in terminal: fastboot oem lock. this will wipe clean the userdata and you'll need to install everthing again.
You can't remove that message with the unlocked bootloader. You'll have to live with it.