Nexus 7 (2012) stuck in "no command" bootloop

[dasmoothride]

I did exactly this after the "no command" loop kept on looping on my nx7 wifi. Now its back to working again with 4.4

I second this!

 

[ehardt]

Step 1: Power Off Your Device (Nexus 7)
Step 2: Power On Your Device While Holding The Two Buttons On The Volume Rocker
(This Will Take You To The BootLoader)
Step 3: Press The Volume Up Intil You Find The One That Says: Recovery Mode
Step 4: Then Press And Hold The Power Button And Volume Up Button Intil You See "No Command"
Step 5: Press And Hold The Power Button And Volume Up Button Again
(This Will Take You To The Recover Menu)

easy'n'quick!!!! no need to refresh, SDK, root, just that and back to A4.4.2 tks all

 

[cprog]

I also managed to fix my Nexus 7 2012 Wifi using Wug's Nexus Toolkit. ( I assume this toolkit will work with Nexus 4,7 and 10 as it is a unified toolkit.) NB: As you will flash stock you will loose all your apps and settings. At least it is better than being stuck with the "No Command" screen.

1. Download and install Nexus Root Toolkit v1.7.8: Nexus Root Toolkit v1.7.8 | WugFresh
2.. Connect to PC and Boot in Fastboot Mode: VOL DOWN + POWER ON
3. In the toolkit, under "Back to stock" tick "Soft-Bricked/Bootloop"
4. Click "Flash Stock + Unroot"
5. When done you will have a working Nexus again. I thought I was going back to stock and would have to install 4.4. But ended up with 4.4. .

I hope this helps someone else.

Thanks a ton. You saved me from a heart-attack. I've tried a 101 solutions but nothing worked. I was thinking that i'll never see my tab working but your solution finally saved me from a lot of troubles. Thanks once again. It worked for me in 4 attempts finally. Yaay!

 

[Thomas Poleski]

Thanks. Great advice. Took me a couple of times to get it right but I'm up and working like new.

 

[cerebrotecnologico]

Did you ever got a solution? My nexus 7 just got into the same state yesterday. The four colored dots after booting keep merging in the screen forever. I already left the tablet running 24 hours in that state. Google said I had to wait 2 days. (WTF!) I called Google again and they basically said my device is bricked, out of warranty; they offered to contact me with ASUS (the manufacturer). This is clearly a software problem, not a hardware problem. Google sucks.

 

[GedBlake]

Did you ever got a solution? My nexus 7 just got into the same state yesterday. The four colored dots after booting keep merging in the screen forever. I already left the tablet running 24 hours in that state. Google said I had to wait 2 days. (WTF!) I called Google again and they basically said my device is bricked, out of warranty; they offered to contact me with ASUS (the manufacturer). This is clearly a software problem, not a hardware problem. Google sucks.

Hi, cerebrotecnologico...

There maybe a way of getting your Nexus 7 up and running again.

Your device is 'bootlooping'... which, as the name suggests, means it's stuck in an endless cycle of booting.

I assume you don't have anything as exotic as a Custom Recovery, such as TWRP or CWM, installed ('flashed'). Bootlooping behaviour can (usually) be easily fixed with such a Custom Recovery available.

However, in the absence of a Custom Recovery, it still may be possible to perform a factory reset using the standard default Stock Recovery that is part of Android... and which should be available to you on your Nexus 7.

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

First off, you need to 'break' out of the bootloop... by booting into the bootloader.

1). Press and hold the VOLUME-DOWN button...
2). Whilst holding, press the POWER button...
3). Maintain your hold on both buttons until the device boots into the bootloader.

See my first attached screenshot for what the bootloader looks like.

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

Next, you need to boot into RECOVERY...

Whilst still in the bootloader, you should see the word START in the uppermost right hand corner of the screen... adjacent to the VOLUME buttons. This is actually part of a rudimentary menu scheme. You use the VOLUME buttons to 'navigate' through the following options... and the POWER BUTTON to select one.

** START - Starts the device normally.
** RESTART BOOTLOADER - Reboots you back here again, ie, the bootloader.
** RECOVERY MODE - Boots the device into the Recovery. Custom Recovery if one is installed; Factory Stock Recovery otherwise.
** POWER OFF - Shuts down the device.

So, using either VOLUME UP or DOWN, 'cycle' through to the RECOVERY MODE option, and press the POWER BUTTON to select.

Your Nexus 7 should now boot into Recovery.

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

See my second attached screenshot of what you should expect to see...

...which, granted, initially isn't much. A green android lying on it's back... and a black exclamation mark in a red triangle poking out of its 'stomach'. The stock recovery doesn't seem to offer much in the way of user interaction. If the Nexus 7 is left in this state for 120 seconds, the device will reboot automatically.

However, what doesn't seem to be generally known, is that the stock recovery has a 'hidden' menu available... and it maybe the key to easily getting your Nexus 7 working again.

Accessing this hidden menu, requires a certain keypress sequence, precise timing and some patience to get right.

The keypress sequence is, (and whilst in STOCK RECOVERY)...

- Press VOLUME UP and POWER BUTTON - SIMULTANEOUS PRESS -

This can sometimes be frustratingly difficult to get right, and I've had to repeat it myself, many times before the hidden menu appears. All I can say is... persist.

See this XDA link for more info on this, and other useful Nexus 7 keypress combos.

Upon success, you should see something similar to my third attached screenshot.

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

It's all pretty straightforward from hereon in... just follow the on-screen instructions. Use the VOL UP and DOWN buttons to scroll up and down the various menu options, and the POWER button to select an option.

Navigate to WIPE DATA/FACTORY RESET, press POWER BUTTON to select... and you should see something like my fourth and final attached screenshot.

This, of course, will WIPE everything on the device... so perhaps you might want to try WIPE CACHE PARTITION first.

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

Finally... if, for whatever reason, the above doesn't work, and you're still bootlooping, there's always another option - flashing a Google factory stock image.

There are plenty of guides and pointers, both here and on XDA, on how to do this... and whilst the process is more technically challenging than the above... it's not insurmountable. And, if as you say, your device is out of warranty... then what have you got to loose?

Checkout these guides on how to flash a Google stock factory image.

http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html

[GUIDE] Flashing a Factory Image with fastboot / return to stock - xda-developers

The key thing to remember is this... if you can access your Nexus 7's bootloader, you have a very good chance of getting it up and running again.

Good luck... and hope this helps.

Rgrds,
Ged.

 

[thebrick2014]

Thank you GedBlake. I already tried that. It didn't work. I cleared the cache, I tried the factory system recovery without success. I will probably attempt to flash the ROM.
My point is that no regular user could do this. There shouldn't be trashing a device. Google should fix it even if out of warranty. It wasn't my fault that the device got bricked. It was their update procedure.
In my view, legal action is required. I can't understand that they can be so sloppy and get away with it.

 

[thebrick2014]

What would a regular user would do with a Nexus brick? Just toss it to the electronic garbage pile?

 

[oscat3g]

I?m trapped in to a boot loop.
My battery is not charging any more. I unplugged the battery 5 times, I also unplugged the processor. After that the charger warmed up a little but didn?t got any juice at all.
I try to re-charge in all the mentioned ways. I?m considering to re-charge my battery installing it in to other nexus???. I?m afraid of affecting the other nexus settings, or losing two n7 instead of one.
I just don?t have any access to anything, boot loader, anything. And I have this creepy beeping every time I connect the Nexus 7 to the USB I have the normal two beeps + three short low tone beeps.
There is always hope, so, I?ll be very great full you can help me.
Thanks

 

[oscat3g]

I?m trapped in to a boot loop.
My battery is not charging any more. I unplugged the battery 5 times, I also unplugged the processor. After that the charger warmed up a little but didn?t got any juice at all.
I try to re-charge in all the mentioned ways. I?m considering to re-charge my battery installing it in to other nexus???. I?m afraid of affecting the other nexus settings, or losing two n7 instead of one.
I just don?t have any access to anything, boot loader, anything. And I have this creepy beeping every time I connect the Nexus 7 to the USB I have the normal two beeps + three short low tone beeps.
There is always hope, so, I?ll be very great full you can help me.
Thanks

 

[qjuju]

Hi, my Nexus 7 is doing exactly the same; did you get a solution to the problem?

Many thanks,

Q.

 

[kmath71]

If you are having trouble with drivers then perhaps you might try using a Linux distro, as you don't need to worry about drivers on Linux. You can run many distros from a usb stick without installing them to your computer. I would suggest Ubuntu or something based on Ubuntu because they have the android tools in their repository which makes installing them easier. On Ubuntu, you can install adb and fastboot from the command line with the command "sudo apt-get install android-tools-adb android-tools-fastboot". When using adb and fastboot on Linux you may need to prefix the commands with "sudo " to get them to work, the "sudo" command runs other commands with root privileges.

Posted via Android Central App

Would this need the device to have 'debugged' set? I'm having a hell of a job trying to get a driver to recognise my Nexus 7 (GSM 2013). I've managed to unlock it, and do a hard reset, but can't get any further than that. Obviously I can't access the setting to enable debugging

 

[lr622349]

Did anyone find a solution for this? I just bought a nexus 7 2012. and i tried to do the update. got the error Andriod, then it has been in the startup loops for hours

 

[lr622349]

hey, I followed your steps and screenshots ( and they were really helpful ! ) I did the wipe data / factory reset. then i did reboot and im stuck in the reboot loop again.
any other suggestions?

thanks!

 

[russelb]

My Nexus 7 suffers a boot loop about every 6 months. Previously I had to use the Nexus Toolkit to completely wipe and reinstall the OS. This method allowed me to eliminate the boot loop without losing data. I have 4.4.2 on mine, but these instructions still work, just use with the updated download of the OS.

OK, I fixed mine without losing any data by following the instructions below, copied from here.
EDIT: To clarify, I have a 2012 wifi so used JWR66Y factory image and then used ADB sideload to install the kitkat zip update which I found on this page. link

-----------
I was in the same situation and ran into that issue as well. What I did was download the 4.3 factory image from here: https://developers.google.com/androi...s/images?hl=vi

Make sure you get the correct one for your device. I have a 2013 wifi so I chose: Android 4.3 (JSS15R)

Inside that downloaded file, you'll find image-razor-jss15r.zip. It's a couple of levels down. Unzip the files from there to your SDK folder (should be boot.img, recovery.img, system.img, userdata.img, and cache.img).

Boot your Nexus 7 to the bootloader (volume down + power) and connect to your PC with USB cable. Do NOT go into Recovery mode yet.

From the command prompt, make sure you can see your device: fastboot devices

Then, run the following commands:

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img

At this point you have a clean install of 4.3 JSS15R.

Now go to Recovery mode and sideload the 4.4 OTA as you originally tried and it should work this time.

I followed these steps and was able to update to 4.4 without losing any data. YMMV

 

[TheAngryDog]

Hi,

I have an issue like this. I cannot get fastboot devices to work. What am I doing wrong?

 

[kellsarah]

If your tablet is on, turn it off.
Press & hold the Volume Down button, then press & hold the Power button simultaneously until the tablet turns on. You'll see the word "Start" with an arrow drawn around it.
Press the Volume Down button twice to higlight Recovery mode.
Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation mark and the words "No command."
While holding down the Power button, press the Volume Up button.
Use the volume buttons to scroll to "wipe data/factory reset," then press the Power button to select it.
Scroll down to "Yes - erase all user data," then press the Power button to select it.
Note: If your tablet becomes unresponsive at any point during the steps above, you can restart it by holding down the Power button for several seconds.

 

[freesamples24]

Thank you for these useful instructions!
I accidentally started with the 4.4 image instead of 4.3 and it seems to work also...

 

[gennytea]

So I have the same issue with my nexus 4. only thing is that, it's stuck on the google screen. it won't go anywhere after that. not even the fastboot mode. so I'm stuck with no solutions. does anyone know what to do?

 

[Cat Dumitru]

that worked for me too, thanks a lot for sharing! Got the factory image from here: https://developers.google.com/android/nexus/images