Develop Bugs

[Q] Stuck at Unlock Bootloader screen

My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?

i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?

Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?

molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?

herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!

OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"

Bricked nexus 7 won't even charge

So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?

Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium

Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???

je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.

destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .

phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....

phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).

I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD

destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).

hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.

phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.

First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?

alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.

phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.

destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??

shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!

destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:

phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.

alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.

phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.

[Q] Nexuz 7 stuck at the google logo

Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.

Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.

aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on

Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.

I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.

He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?

sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.

Another Bricked Nexus 7 after Lollipop

Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.

this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!

I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".

Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.

Tried all NRT options including force flash.
Problem is none work with the locked bootloader.

Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.

IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?

Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.

Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."

I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!

As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..

Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.

tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..

tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?

dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.

tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does

I ve given up . Bought a Nexus 9. Wasted too much time on this.

Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.

My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.

Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.