Develop Bugs

[Q] Will warranty service knows if my device is rooted and unlocked?

Hi guys! I want to send my Nexus 7 (2013) to warranty service because it's bricked and I think the motherboard is destroyed. Will the service understand that the device is unlocked (bootloader) and rooted?

I could be wrong so wait for confirmation from someone else but if it won't even power on I don't think they would know, however if it powers on as far as the white Google logo you can see it is unlocked by the white padlock that is opened at the bottom, or closed lock for locked boot loader.
Sounds like it won't power on though if the main board is dead so I doubt they could know...

If it helps i had an iphone 4 that i jailbroke and it ended up bricked. It wouldnt connect to the computer or anything else. I had the same worry you have and when it was sent off i thought theyd find out. They didnt, and i got a replacement. If it doesnt connect to a computer they just dismantle them for parts. A repair engineer is more expensive to employ than a few idiots with screw drivers.

May be I am wrong about the mainboard. Yeah, I can turn it on, but I can go only to boatloader. It can be connected to computer (only fastboot mode) and there is unlocked padlock.
I guess need to lock the bootloader. But the device does not see any space (free or used) - I was connected it to computer and used a recovery mode with Skipsoft application. May be the memory is dead. It shows that cannot mount any partition. I don't know. Is there any way to lock the bootloader?

I am guessing you used Wug's root toolkit to unlock. I have seen others relock there's when there has been problems similar to yours, maybe check his thread out and ask in there.

Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.

ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Yeah I know the feeling
I am always worried about devices failing but after I have had it for about a year I wont be so scared and will take more risks with it usually. Only had mine for around 2 weeks and am also worried it could go off at anytime as mine is unlocked and rooted. Lots of people seem to have had problems with this device, my Xperia S never had problems

ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Try this... http://www.android.gs/restore-un-br...4-3-jelly-bean-twrp-and-root-guides-included/
It might at least get it locked for you....

Thank you! I will try that as soon as I go home...

This is pretty much what danvee posted but still..
If you can use fastboot that's a good sign. You probably don't even need to send it in. Try this: http://forum.xda-developers.com/showthread.php?t=2469508&highlight=stock
You say something about no space? If the above link doesn't get you running again try this first: http://forum.xda-developers.com/showthread.php?t=2380913 Worked for me.
You can just flash twrp with "fastboot flash recovery recoveryname.img"(without quotes), wipe, then use the steps in the first link.
If that doesn't work it probably is some kind of hardware problem.

I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.

ryderbg said:
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
Click to expand...
Click to collapse
heres a funny story but what it resulted in and how i fixed it seem to apply to the problem you have.
i have a cracked screen on my nexus and it was registering a touch at intermittent intervals making the device unusable. i posted in here about the same time you did for help. while i was waiting to see if anyone knew if i could just disconnect the screen and use a bluetooth mouse with a hdmi adapter (slimport not mhl, thanks meekrawb) i connected a usb mouse with an otg cable. the mouse worked but i couldnt see how to turn off touch screen as an imput. as kitkat has been release and i hadnt updated i thought i would give it a try and see if that would reset the screen and stop the touch. It downloaded the update and when it rebooted it opened up a mod recovery screen (i forgot that i had rooted it). it asked me to slide a bar on the bootloader screen to continue. The usb mouse cursor was not present on this screen and the touch screen doesnt work so i couldnt get past it. i turned the device off and on again (what else do you do when your stuck) and it would open the google screen with the unlocked padlock but then just stay on a completely black screen. same as yours. I connected it to the computer and it recognised it. i opened wugfresh's root tool kit (old apple jb's sometimes had recovery abilities built into them so i thought this may aswell) i clicked on flash stock and unroot with the radial button on soft bricked and followed the instructions. now my device is unbricked and even the touch has stopped. Happy days hey. you'll need to unlock your boot loader again but its worth a try before going to the store, you can always lock the bootloader again if it doesnt work.
i know it didnt need all this to say "connect it to the root tool kit and try that" but i thought you would enjoy a laugh

Funny story. But my issue is hardware. The device doesn't show any space in it. No free nor used. I think the memory is dead. Also I relocked the bootloader, but now I cannot unlock it again because there is no space
Now when the tablet is with locked bootloader, it is unrooted, right?
Tommorow I will visit the warranty service and hope they don't understand about rooting and unlocking.

according to an email from "google play support India" , the device will be accepted under warranty as long as it has a stock firmware installed when you send in the device to claim the warranty.

[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.

[Q] Nexus 7 Bricked due to 4.4.3 Update?

I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).
A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:
System UID's Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.
I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.
I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).
Anyone have any ideas/suggestions? Thanks so much!

To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.

xbi0s said:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
Click to expand...
Click to collapse
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.
Any other thoughts? Thanks!

Anyone else have any suggestions/ideas? Thanks!

mbressman said:
Anyone else have any suggestions/ideas? Thanks!
Click to expand...
Click to collapse
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.

Aerowinder said:
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Click to expand...
Click to collapse
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!

mbressman said:
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
Click to expand...
Click to collapse
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.

Aerowinder said:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Click to expand...
Click to collapse
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!

mbressman said:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
Click to expand...
Click to collapse
You can try different drivers. Uninstall current ones, and install the ones from my signature.

Aerowinder said:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Click to expand...
Click to collapse
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).
I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...
Anything else I can try?
Thanks!

Hi,
I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.
Maybe some ****ty update? I've got the LTE version.

Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.

mbressman said:
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
Click to expand...
Click to collapse
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.

Gawson said:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Click to expand...
Click to collapse
Gawson - when you got it back did it still have your data on it, or was it wiped?

mbressman said:
Gawson - when you got it back did it still have your data on it, or was it wiped?
Click to expand...
Click to collapse
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.
Now its working like new. In fact it has all new guts except battery and screen.
Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.

[q] hard bricked

OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman

I can't help... but am in the same boat as of last night with the 5.0 update.

Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.

Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!

im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?

When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.

ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.

tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.

When i boot to recovery i get the TWRP startup screen but stays stuck.

Bump
bump.. any ideas?

i have the same :/

kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."

tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?

NO success because I cannot unlock the bootloader.

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