yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] thisisjjd:
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.

It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)

I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.

Subsequent attempts to normal boot hung at the "Google" logo.

Attempts to enter recovery hang at the Google logo.
[Nexus 7 (2013) Q&A] charesa39:
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://xdaforums.com/showthread.php?t=2382051. Pay particular attention to what you need to modify to make sure you don't wipe your userdata.
[Nexus 7 (2013) Q&A] thisisjjd:
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.

Or am I not understanding something?
[Nexus 7 (2013) Q&A] charesa39:
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
[Nexus 7 (2013) Q&A] thisisjjd:
I thought I had tried that, but thank you, I'll try again. I appreciate your advice.
[Nexus 7 (2013) Q&A] thisisjjd:
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:

Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".

The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:

(bootloader) Unlocking bootloader...

(bootloader) erasing userdata...

and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.

Suggestions? Thanks for your help.
[Nexus 7 (2013) Q&A] charesa39:
Hmm. Unfortunately, this is issue seems beyond my knowledge. That's odd that yesterday it was showing unlocked, and today it randomly is locked. If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
[Nexus 7 (2013) Q&A] thisisjjd:
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.

I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".

I'd still like some help if anyone has any ideas.
[Nexus 7 (2013) Q&A] wantabe:
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary. If you are stuck in a boot loop long press the power button to force a reboot, as soon as the screen turns off press the volume down button that will get you to the bootloader. Or if the device is off press and hold both the power button and volume down button to get to the bootloader. Choose recovery with the volume button then press the power button. You should see android laying down with exclamation mark. Press and hold the power button and while holding the power button press and release the volume up button. Stock recovery! Use the volume button to select "wipe data/factory reset" then press power button. If that doesn't take care of it download the factory image and extract, if running 4.4.2 wifi version you should see ;

bootloader-flo-flo-04.02.img

flash-all.bat

flash-all.sh

flash-base.sh

image-razor-kot49h.zip

if you double click the "flash-all.bat" with the device already at the bootloader that will flash the complete image including userdata which wipes the device. You can also open flash-all.bat with notepad and remove -w from the script and it should not flash the userdata.img. Or... you could extract all of the images from the "image-razor-kot49h.zip" and flash them seperately with fastboot, whatever images you try to flash need to be in the same folder as fastboot.exe (platform-tools) so you do have multiple options as long as there is no hardware issue that is causing the reboot. Hope this helps! ;)
[Nexus 7 (2013) Q&A] thisisjjd:
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.

I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.

I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
[Nexus 7 (2013) Q&A] wantabe:
Sorry to hear that! I don't remember ever hearing being able to get into the bootloader but not into recovery from there. Your probably right about having to do doing an RMA. If it's any consolation I had a good experience with ASUS when I had to RMA my 1st gen N7 32GB after the speakers went bad.
[Nexus 7 (2013) Q&A] thisisjjd:
I'm glad to hear you had a good experience with ASUS support. I have an RMA and am sending it to them. Thanks for your help.
[Nexus 7 (2013) Q&A] mnunez611:
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.

When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.

Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
[Nexus 7 (2013) Q&A] LinearEquation:
I would say definitely RMA it. With you having a stock tablet it's not worth risking messing something up trying to fix your tablet and then maybe you can't RMA. I would start with Best Buy and them what their warranty period is. If it is within their stories warranty then take it to them. If not then call ASUS.
[Nexus 7 (2013) Q&A] Gloftking:
Help me

Hello Guys I am stuck in a very annoying situation at the moment which is that my nexus 7 has become inaccessiblhttp://xdaforums.com/images/smilies/eek.gife. This is how it happened

one day I tried to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' errohttp://xdaforums.com/images/smilies/crying.gifr. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).

if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://xdaforums.com/images/smilies/fingers-crossed.gif

thanks in advance
[Nexus 7 (2013) Q&A] Mista513:
I have the exact same issue as the OP. Can't get to recovery cause the Google logo hangs there. I can fastboot but the N7 is locked since it was not rooted. Using fast boot and Wugs I get the same thing where it just hangs on erasing userdata for hours. Wondering if any fix has been discovered for this since the OP issue was months ago.
[Nexus 7 (2013) Q&A] Pezmet:
Use fastboot OEM unlock command to unlock the boot loader then re flash stock.

Sent from my Nexus 7
[Nexus 7 (2013) Q&A] Mista513:
It doesn't work... It hangs on erasing userdata.
[Nexus 7 (2013) Q&A] beartrap:
You're not alone, there's a lot of us that's been screwed by Google. It's the last Nexus I'll ever buy. I've since moved on to a Samsung Galaxy TabS 8.4.
[Nexus 7 (2013) Q&A] Pezmet:
Use: "fastboot format userdata", "fastboot format cache" from the bootloader.
[Nexus 7 (2013) Q&A] Mista513:
It hangs at erasing userdata no matter what process I try. I've found at least 7 others across multiple post who seem to have this identical issue after the Lollipop OTA.
[Nexus 7 (2013) Q&A] zoltecrules:
Make that 8. Mine experienced the same exact thing last week. I'm considering buying a new motherboard since I'm out of warranty.
[Nexus 7 (2013) Q&A] greycobalt:
This has happened to me as well. Just the Google screen, no luck entering recovery or flashing anything. I can actually get the fastboot to be recognized, but none of the commands will be accepted (unknown error). Really frustrating, as it happened out of nowhere. I'm probably WAY out of warranty seeing as I got it in July 2013, so I'm not sure what to do. I got a Galaxy Tab 4 off of Craigslist, but I'm so unimpressed so far - the resolution is abysmal, and it was an AT&T variant so it's just constantly telling me to get a SIM card and that I'm not connected to the network. I wanted to get help on here to flash something to it, but no one is responding in that forum. :-/ But I digress...

This sucks!
[Nexus 7 (2013) Q&A] trifold:
Just checking in

Yeah, having the same issue too, so count me among those hoping a solution is found.

Not sure if anyone else is in the situation as me, but I actually never got around to unlocking/rooting, so it must have had something to do with the OTA?
[Nexus 7 (2013) Q&A] Mista513:
Yeah mine was 100% factory, no root not unlocked or anything. All was fine till a few weeks after I got the OTA.
[Nexus 7 (2013) Q&A] Norcalz71:
I dont want to jump the gun here and assume all is well (I sure hope it is), but I sent mine in (past warranty by 1 month) for RMA, took forever to show up in their system (2.5 weeks) but as of today 1-2 days later it says it should be delivered to me tomorrow fixed with a new motherboard...

So I basically heard nothing/got no updates and then within 3 days it shows up on the RMA status website and is repaired and being shipped back. If it shows tomorrow we will see but fingers crossed.
[Nexus 7 (2013) Q&A] didit70:
count me in as well... stock N7 (2013)... got the update a few weeks ago... i let my battery drain to 0% overnight by accident and, after a charge, i attempted to reboot... i was stuck at the "Google" screen... i attempted the soft and hard reset without any success... i also tried the fastboot commands above, didn't work... i called Asus who informed me that they would fix it for a fee since it's out of warranty... Google said they can't do anything for me since i didn't purchase it from them... so i'm left with a brick because of an OTA...
[Nexus 7 (2013) Q&A] lordstalker:
Mine bricked itself yesterday. Woke up to the Google screen.
[Nexus 7 (2013) Q&A] Mista513:
Yeah that's pretty much how it happens. Good luck, I still haven't found a fix anywhere on the web still. Nor anything with Google acknowledging it is happening.
[Nexus 7 (2013) Q&A] superaj13:
Still no fix for this? Ive been bricked for almost a month now.
[Nexus 7 (2013) Q&A] LinearEquation:
If it turns on, it's not "bricked." Boot into the bootloader and flash a factory image.
[Nexus 7 (2013) Q&A] beartrap:
Can't be done in this situation. There's a lot of us that have been bricked by Lollipop. We can get into the bootloader but that's it. Can't unlock so we can't flash. The device hangs on reading user data. It's bricked.
[Nexus 7 (2013) Q&A] Norcalz71:
So my tablet finally showed back up, FedEx had some issuing delivering. I have only so far turned it on but...seems fine. They replaced the motherboard as they said the OS partition was corrupt and since I was not unlocked, they also could not reflash it. No charge just the shipping to get it there and technically I was about a month out of warranty BUT the OTAs did start when I was in warranty, I just got it pretty late.

So there may be hope, I laid out fairly clearly that I thought it was a premature hardware failure and a few weeks later I have my tablet back with a new motherboard, so I am pleased with the honoring of the warranty service
[Nexus 7 (2013) Q&A] Mista513:
Thankfully they took care of you... Unfortunately for any other day one buyers we are too far outside of the warranty for any luck like that. At the prices they charge for the motherboard replacement, work and shipping it's better off to buy a new for the small amount of extra money. I'm gonna have to buy a new one at this point and it sure as hell won't be anything Asus.
[Nexus 7 (2013) Q&A] Norcalz71:
I have to imagine that Lollipop has something to do with these failures. Asus indicated that my OS (I know thats not an actual partition name) was corrupt and due to my bootloader being still locked, they could not reflash the system and it was hanging at erase user data. It just seems too strong a coincidence that so many cases pop up during the update, but how it would cause a permanent hardware failure that cannot be reflashed (others who were unlocked prior to failure have indicated that they cannot reflash) I am not sure.
[Nexus 7 (2013) Q&A] beartrap:
I agree. I don't think I'll ever buy another Nexus but will unlock any device I get. This has been a humongous blunder by Google and their refusal to rectify this says a lot.
[Nexus 7 (2013) Q&A] jetracers:
Im in the same boat as I accepted the OTA which installed fine and after using the tablet for a few minutes got a random reboot, and cant get past the google screen .
[Nexus 7 (2013) Q&A] :sasquatch::
i have the same problem! nexus 7 2013 (wifi) 32gb

i have tried everything! cannot unlock bootloader to flash factory image! i have even tried a nexus toolkit, but it doesnt work...

when i trie to unlock the bootloader, it freezes... im almost sure that if we manage to unlock the bootloader, we can flash all the files we need...

is there smone who can help us? :(
[Nexus 7 (2013) Q&A] beartrap:
The only fix I've been able to find has been a motherboard replacement. Google refuses to respond to this issue on their own forum and just want to sweep this problem under the rug.
[Nexus 7 (2013) Q&A] _MetalHead_:
Did you try flashing a recovery with fastboot?
[Nexus 7 (2013) Q&A] barryholroyd:
Very good question. However, I believe that flashing the system image includes flashing the recovery. At least this was part of the output of flashing the system image:

sending 'recovery' (7600 KB)...

OKAY [ 0.245s]

writing 'recovery'...

OKAY [ 0.289s]
​

I've included a full trace of the entire session, including the output of the script, in a new attachment ("session_trace.txt"). The actual name of the script, as seen in session_trace.txt, is "barry.sh". That is the same as the file I already attached (as "firmware_install_4-4-4.txt") -- I renamed it when I attached it to my initial message for purposes of clarity (which this sentence has probably now ruined :)). Summary: barry.sh == firmware_install_4-4-4.txt.

Thanks,

Barry
[Nexus 7 (2013) Q&A] SDotNY:
Add me to this list now too, just happened today for me. I suck at ADB to begin with but I really can't figure this one out at all. I can get to fast boot as you can see in the image I attached but I can't do anything after that. I can't get into TWRP or clockwork either. Anyone have some other ideas?
[Nexus 7 (2013) Q&A] Mista513:
You are at least unlocked, which is the issue the rest of us have... Try using Wugs Toolkit and flash back to factory, or a recovery.
[Nexus 7 (2013) Q&A] ViccNL:
Hi guys, another victim here.

My Stock Nexus 7 (2013) 16GB got the OTA couple of weeks ago. Got stuck on Google a week after, but fortunately the first time this occured I was able to boot into Recovery and perform a cache wipe, which at that point solved the issues. Used it happily for another 2 weeks and got stuck at Google logo again.

Unfortunately now I am no longer able to boot into Recovery mode, same as OP and everyone else here.

At this point I started researching the issue and tried everything.

I can successfully Lock/Unlock the device using fastboot oem unlock. I have succesfully flashed stock image from google website for 5.0.2, 5.0.0, 4.4.4 and another earlier version, all resulting the same way > Stuck at Google, cannot boot Recovery. I have used the flash-all.bat and I have done it by hand step by step using fastboot commands. All steps were succesfull and without error.

I have used the Nexus Toolkit, still no success. I have tried multiple custom Recovery files including TWRP. Which does boot up, but then freezes and I cannot use any buttons.

I purchased this model in the US (but I live in Europe) and no longer have any warranty (been using it for 14-15 months now)

Sending it to ASUS for repairs will cost at least 75euros for shipping and inspection and on top of that additional costs for replacing/fixing components. Which to me is unacceptable considering I can probably buy a new one for that money...

I am most displeased to say the least, and this all happened because of an official OTA? I never tinkered with the device in any way (never unlocked it before, rooted or whatever) and have only downloaded official apps from Google Play.

Will subscribe to this post, hoping someday someone will find a fix. Any suggestions are welcome, but at this point I am done with Nexus...
[Nexus 7 (2013) Q&A] raSHOREY:
I also have the same issue:confused:
[Nexus 7 (2013) Q&A] SDotNY:
This is what I get when I try to flash a stock recovery..

Warning! This will delete everything on your device! BACKUP your device!

First make sure your in FASTBOOT MODE!

Press enter to continue

sending 'bootloader' (3911 KB)... OKAY

writing 'bootloader'... FAILED (remote: flash write failure)

rebooting into bootloader... OKAY

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-03.14

Baseband Version.....: none

Serial Number........: 0585b85d

--------------------------------------------

checking product... OKAY

checking version-bootloader... OKAY

sending 'boot' (6880 KB)... OKAY

writing 'boot'... FAILED (remote: flash write failure)
[Nexus 7 (2013) Q&A] barryholroyd:
Problem FIXED.

Yes, I flashed everything. Thanks for the suggestion, however.

I did finally get the problem resolved: it is now FIXED.

I received helped from Hikari on Android Authority forums. It turned out that I had a mild (but blocking) hardware problem. I removed the back of the Nexus 7 and pressed down on all connections, including a both ends of a metal "tape" that were peeling up from their contacts. After doing that I was able to once again get to the Recovery mode screen from the boot loader.

Barry
[Nexus 7 (2013) Q&A] kmharman:
Same issue as of a day ago...

Stock and locked Lollipop, hangs at Google logo, can enter fastboot but not recovery, oem unlock never completes, even after 2 hours, stuck at 'erasing userdata'.
[Nexus 7 (2013) Q&A] trifold:
Just put in a new motherboard I got off eBay. Works again. Kind of annoying that's what it takes, but oh well.

Now to root and make sure it never installs another OTA again.
[Nexus 7 (2013) Q&A] Mista513:
I looked up 32gb motherboards and can't find any at a decent price, only 16gb. I took the back cover off checked all the connections and all is fine. Motherboard replacement seems to be the only fix unless one of the wizards on XDA can find some kind of fix for this somehow. I still don't believe Google is ignoring this issue like it is not happening.
[Nexus 7 (2013) Q&A] wis38:
Bye bye Asus

It happened to me too yesterday...

I was reading a web page when suddenly the tablet hanged, rebooted and blocked on the "Google" screen. Same problem as the others highlighted here: no way to enter the recovery mode, nor any other method suggested worked. :mad:

Of course this happens when the warranty is expired since few months (thanks Asus), and no way to have them taking care of it (they were incredibly fast in answering me they will be more then happy to repair it, but outside the warranty). It's my second tablet from Asus that dies (the first one was the old glory TF101), always few months outside the warranty period.

So, let's now give a chance to Samsung: I just took the Galaxy TAB S 8.4, hoping for better durability (at least Samsung provides 2y warranty in Europe). 323€ VAT included -50€ mail-in rebate looks a good price for a forced upgrade :fingers-crossed:
[Nexus 7 (2013) Q&A] ccjb100:
Well I'm yet another one. Tablet was working normally, but we left it at someones house since Superbowl. It had fully drained battery and shutdown. Got it back yesterday, let it charge. After turning on:

Normal boot = hang at Google screen.

Boot to bootloader = ok

Boot to recovery = hangs at Google screen.

Unlock bootloader = hang/freeze at erasing userdata
[Nexus 7 (2013) Q&A] Ohmanwhy:
Hey can you please post a pick of that metal "tape" it would help me figure out if I'm a total moron :laugh:
[Nexus 7 (2013) Q&A] Mista513:
This big one going across the device. Mine was fine and tablet still a useless brick.
[Nexus 7 (2013) Q&A] Ohmanwhy:
Thanks managed to get mine to work by pushing on the places where that tape connects but now my touch doesn't work. I lost the tape thing highlighted with red , is that why the touch won't work?
[Nexus 7 (2013) Q&A] Mista513:
Probably, not sure exactly what that particular piece goes to. The video that shows how to take it apart mentions what most are, but don't remember that exact spot circled mentioned... How did you lose it? I un-snapped the ends of the tape then snapped them back w/o removing other parts.

---------- Post added at 09:32 AM ---------- Previous post was at 09:28 AM ----------

It could also be if you used too much force while pressing on the ends and cracked something on the board.
[Nexus 7 (2013) Q&A] mrcyco:
Add me

Happened last night, cant boot to recovery etc. Had the back off touched everything no luck no warranty.

Just want to add to the numbers.
[Nexus 7 (2013) Q&A] caohui:
One more bricked device

Found the device showing google while charging, then everything is the same:

Normal boot = hang at Google screen.

Boot to bootloader = ok

Boot to recovery = hangs at Google screen.

Unlock bootloader = hang/freeze at erasing userdata (1.5 hours past and I'm still waiting)
[Nexus 7 (2013) Q&A] pokeycd:
Another one bites the dust

Completely stock, and bought the tablet the day it was released.

Got lollipop recently. Maybe a month or so ago.

Was watching Netflix at about 67% battery when it hung. Forced it off. Reboot brings "Google" in white letters. Like most people, I was able to get into Bootloader (fastboot), but not able to get into Recovery (sticks on "Google" again). Haven't tried to send fastboot commands yet, but not entirely convinced it will help. Seems like everyone else gets stuck on "userdata".

----

UPDATE: I opened up the back and disconnected both ends of the main ribbon that jumps over the battery. Reconnected. Still BRICKED.