So my Nexus 7 is stuck in an infinite loading loop and Im unsure of how to fix it. Supposedly it should be fixable but none of the guides I've come across really address my specific issue. I've been able to unlock the device using the Nexus Root Toolkit, but that's about it. Since I cant access the tablet past the loading screen, I cant turn on USB debugging and I also cant access recovery mode when in bootloader(I just get a dead android screen and the tablet restarts), rendering me unable to follow through with pretty much every guide that I've come across to fix the tablet. Anyone know how I would be able to unbrick my Nexus based on my current limitations?
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
Bricked Nexus 7...Not sure what to do
- Thread starter Onemic
- Start date
- Status
Like I said in the OP, I cant access recovery mode. It just shows a dead android with a red exclamation and restarts.
You push power and volume down and that is what it loads up on the screen?
No, I can access bootloader, but when I specifically try and access recovery mode I get the dead android.
Did you try rooting it or something? This exact thing happened to my sister's samsung but it was never rooted. It gave some kimd of warning that someone tried fucking with the OS and the dead andy with a red exclamation would pop up. We just took it back and got it replaced without a problem. I was never able to fix it since i couldnt access anything.
Okay so you're soft bricked. In recovery can you see the device via adb on your windows or mac machine?
Nope, I just got an infinite loading loop one day for no reason.
Nexus 7 2013? Stuck on the Google logo bootscreen?
If so, same thing happened to mine and many others. As far as I can tell, there is no fix. You need to replace the motherboard, the NAND memory is shot on yours.
Nevermind, you said that much. I'd think as long as you can get it there you should be able to toggle some sort of recovery downloader but if you can't get it via ADB I wouldn't be sure where to go from there.
Nope, it doesnt show up as anything on my PC
Vanillalite
Ask me about the GAF Notebook
He's fucked without USB debug on
I have the 2012 wifi version. It gets past the initial google screen to the part where you see a bunch of colours flying about and just loads forever.
I can access bootloader, but not recovery mode, no.
You may be right. Does the device show as any type of connected media in device manager or under My PC?
CharlieDigital
Banned
Yes, I have the same issue; been pondering whether it's worth it to fix or not
Kind of ridiculous, IMO.
So you get to a screen like the one below and then it just restarts itself with you doing anything?
It looks like that, but with no options. Just the dead android with the exclamation point, then it restarts.
MarkMclovin
Member
OP, when you have the image of the dead android, you then need to press a button order to get to the menu. Took me a few times to get to it to clear the cache.
Forgotten what the button order was sorry, but youtube it.
EDIT - Try this.
http://forums.androidcentral.com/go...e-nexus-7-2012-2013-cache-partition-wipe.html
Point number 6 is what I had to do several times before it worked.
Forgotten what the button order was sorry, but youtube it.
EDIT - Try this.
http://forums.androidcentral.com/go...e-nexus-7-2012-2013-cache-partition-wipe.html
Point number 6 is what I had to do several times before it worked.
Check this: http://forum.xda-developers.com/showthread.php?t=1907796
You should be able to get to download mode with some combination of buttons. From there, use android dev tool fastboot to flash the factory firmware.
You should be able to get to download mode with some combination of buttons. From there, use android dev tool fastboot to flash the factory firmware.
Doesnt show up. If its not under recovery mode it tries to install device drivers, but fails.
Vanillalite
Ask me about the GAF Notebook
Up + Power when you get to the dead Android on it's side.
This Works! Should I do a factory reset/data wipe?
What are your options?
DrROBschiz
Member
What in the world did you do to mess up the recovery?
MarkMclovin
Member
Try clearing the cache first.
If that fails, then yeah fuck it. Your data should be backed up anyway.
Taco_Human
Member
Wug Fresh Nexus Root Toolkit, it'll fix the bootloop. Best thing I've learned about nexus devices is that this program exists. It should help.
bananafactory
Banned
Try washing it
Though that may only work for Flagship phones
Though that may only work for Flagship phones
That's what he's using. Not sure how he managed to mess it up, as the program makes it pretty hard to do so.
In order, i'd try 1) wipe cache, 2) factory reset, and 3) adb, advancing to the next one if the prior one doesn't work for you.
Went into recovery mode and wiped data and the cache.(unsure of how to apply the ADB update) Im still getting the infinite loop though
The problem with the program is that it assumes you can get past the loading screen, since you need to in order to turn on USB debugging. I can't.
The problem with the program is that it assumes you can get past the loading screen, since you need to in order to turn on USB debugging. I can't.
MarkMclovin
Member
If you're still getting the bootloop after wiping it and doing a factory reset, then yeah it's probably fucked.
I'm not sure if you can get a custom bootloader on there in that state.
I'm not sure if you can get a custom bootloader on there in that state.
Very worst case is you find an official update.zip and use the "apply update from ADB" option. Maybe that would even work with the Factory Images from Google, but I'm not sure how the files in those are organized in update.zip.
edit: this is all assuming there isn't a hardware issue. Though I guess if you didn't root/install custom ROMs then it is unlikely to be only a software issue if it's still doing it after a factory reset.
Adb debug is only to send it commands to restart to the bootloaderr or to recovery(well and do actual debugging). Adb drivers and bootloader drivers are different. You can still unlock your bootloader, reflash a stock image, and then relock the bootloader unless there is something wrong in the hardware. Can you see devices with no drivers in device manager?
Nope, the bootloop just happened one day for no reason. Used my Nexus to watch a youtube vid. Turned it off and the next day I got a bootloop.
It shows up as MTP USB device in device manager. The Nexus is already unlocked because the tool was somehow able to do that without me having access to USB debugging. The Root option is completely unavailable to me though as the program says it cant find and ADB device
evanswolves
Member
Weird, I had the same thing happen to my nexus 7 yesterday, was stuck in a bootloop (4 colours going round and around for hours) luckily NRT saved the day! It wasn't being recognised when I plugged it into my PC or anything.
Got the right build and stuff selected and downloaded via NRT, had to clear the drivers then reinstall them through NRT. Got the nexus onto the bootloader, on NRT I selected the bootloop option and selected the No Wipe option, few more clicks and a couple of mins wait my nexus 7 was back up and running with all my Apps, pics, Vids all still there. Think I had already elected the debug mode, glad I did, have made sure my nexus 4 is the same, just incase...
Got the right build and stuff selected and downloaded via NRT, had to clear the drivers then reinstall them through NRT. Got the nexus onto the bootloader, on NRT I selected the bootloop option and selected the No Wipe option, few more clicks and a couple of mins wait my nexus 7 was back up and running with all my Apps, pics, Vids all still there. Think I had already elected the debug mode, glad I did, have made sure my nexus 4 is the same, just incase...
evanswolves
Member
Silly queestion, but are you on the bootloader when you use NRT? It would only see my nexus when it was on the bootloader, during the bootloop it was come up as no adb device detected
You should see a composite adb device when in recovery mode. The bootloader device has a different name but I'm not near my computer to check. If you're seeing that mtp device while in the bootloader, Windows choose the wrong drivers. I don't think I've ever seen an mtp device while in recovery either.
Ah, I had checked it while it was under the loop. When in bootloader it shows up as Android Bootloader Interface
EDIT: I got through the ATB not found when doing the root, but now Im getting an infinite waiting for device loop since the software failed to reboot the android :/
EDIT2: After a few tries, it was finally able to communicate with the Android and restart it, but it's once again on an infinite 'waiting for your device' loop. My nexus boots up but looks absolutely messed. I only see a back button, a battery/wifi symbol. And am greeted with a bunch of "unfortunately Setup Wizard has stopped" prompts.
evanswolves
Member
Now that NRT sees the nexus 7 have you tried the softlock/bootloop option in NRT?
fluffydelusions
Member
No idea if it will help you but my Nexus 5 recently started going in a loop at the google screen and my power button was stuck though it didn't appear to be. I tapped the button a bunch of times quickly and it fixed the issue.
Schrade
Member
OP. I had this exact same thing happen to me with my Nexus 7 (2013) 32GB.
Basically, from everything I've read it sounds like the nVRAM is toasted and you have to replace the mainboard to "fix" it.
I ended up just buying a new one since mine was out of warranty and I cracked the screen trying to get the damn thing open to replace the mainboard.
I didn't realize how much I used it until I couldn't use it :-/
Basically, from everything I've read it sounds like the nVRAM is toasted and you have to replace the mainboard to "fix" it.
I ended up just buying a new one since mine was out of warranty and I cracked the screen trying to get the damn thing open to replace the mainboard.
I didn't realize how much I used it until I couldn't use it :-/
Sorry for the late reply, just got out of work. Since the bootloader is being recognized you can download an image from Google and flash it yourself. They have insructions on how to do everything, but you need to have the android sdk installed. If you flash the image and it still doesn't work then something is wrong with the device.
http://www.androidpolice.com/2013/11/14/android-4-4-kitkat-factory-images-and-binaries-are-up-for-nexus-4-all-variants-of-nexus-7-2012-and-2013-and-nexus-10/
http://www.androidpolice.com/2013/11/14/android-4-4-kitkat-factory-images-and-binaries-are-up-for-nexus-4-all-variants-of-nexus-7-2012-and-2013-and-nexus-10/
- Status