A co-worker bought a N7 for his 10yr old. Around the same time Android 4.3 was being pushed to devices, this particular tablet stopped working. The child won't explain what happened, but I think he possibly did something to it while 4.3 was installing. I dunno.
I have the tablet in my possession, it's stuck on the X screen. If I power button/volume down I can get into the recovery screen, but when I select recovery, I get the Android on his back with "No Command" written under it, and it hangs there. In my computers device manager, the tablet is listed as MTP USB device with an exclamation point.
Since I cant boot into the device and turn on debugging, I'm not sure what to do. Can anyone offer me any advice? it would sure make this kid happy to get his tablet back, it was his birthday present
Try flashing a custom tech recovery like TWRP to the device via fastboot. Then use adb to push a custom or stock ROM to the device and flash from recovery.
Or you can flash a factory image from the boot loader via fast boot.
Just follow this guide if you are unsure http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using Tapatalk HD
Related
As a previous user posted here http://forum.xda-developers.com/showthread.php?t=1899024&page=172 I'm also having the same problem as he where the geen circle is revolving around the android in a loop. It only once completed the boot process but I only had a black screen with no choices to make. Since then, it only loops with the circle around the android. The tablet will not boot into recovery using all the options I've read on the forum and elsewhere. I used the JROMFlasher as noted [I usually use the Nexus 7 Toolkit]. Went through all the steps as indicated and loaded the SmoothROM. It only loops and the author really didn't answer the poster's question on how to get out of the loop. He just sadi to use the JROMFlasher. Trying to boot into Fastboot with the JROMFlasher only asks me if the device is turned on/plugged in. Pressing the Boot into Recovery tells me the same. I'm able to boot into the screen to choose power off/recovery/and restart bootloader. Only the restart bootloader and power off works, so I've powered off for the time being until I'm able to get the tablet "unbricked." I've previously used various ROMs on this site without incident using both JROMFlasher but mostly the Nexus Toolkit, except for this one incident where I've run into problems. It looks as if this problem is permanent on my tablet.
Well I managed to actually connect to the device and I can see the folders in Windows 7, but they're all empty, no system files, nothing, only the SmoothROM zip file I managed to get on the device yesterday befoe I began having problems. JROMFlasher cannot see the device, and niether can the Nexus 7 Tookit, so I guess I have a completely POS on my hands as of this minute. The looping is still there on the animation screen, but that's all I see. Time to power off this POS and send it to the trash. Don't think I'll be rooting any more devices.
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
stickplayer said:
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
Click to expand...
Click to collapse
So you've tried using fastboot to flash a custom recovery image? The command fastboot is a part of the Android SDK.
fastboot flash recovery <name of recovery .img>
There's plenty of stickies and information in this forum, which I won't re-hash here.
The stock recovery WILL show the android with the red triangle. To get into recovery from there, I believe you need to hold the up volume key. Other recoveries shouldn't do this though. Perhaps you should try using ROM Manager or Goomanager to flash a recovery from within android.
It took several attempts - flashing stock, then cwm, from the toolkit, before cwm finally "took". It's all working now.
So my 4 year old nephew was playing with my 2012 Nexus 7 and now it's stuck in a bootloop and I can't get into anything but bootloader. Every option takes me right back to the google startup logo of the merging color dots. It was rooted but I was using stock kit kat at the time.
I've done my reading on how to fix a bootloop, lots of tutorials with the same info: use wug fresh tool kit to restore to factory. However, all of these instruct turning on USB Debugging on the Nexus. How do you do that when you are stuck in bootloop with only access to bootloader and the Android System Recovery screen????? I have to totally be missing something here are these guys aren't thinking through the problem. I'm smart enough to know I could be the problem, but I don't think so?
So, can someone tell me how I can get my Nexus 7 back to stock, considering that I am only able to get into bootloader? Also I have a mac, so any mac compatible solutions would be awesome, but I can get my hands on a PC if necessary.
I have unlock/rooted/rom'd before, so I'm not a complete idiot on this subject. Yet, obviously far from an expert. I know I have to use fastboot but will it work if I can't get into my nexus to turn on usb debugging?
Some details:
1. Only Bootloader is accessible through the Power/Vol UP/Vol Down combo (see pic)
2. From the Bootloader, Start/Power Off/Restart Bootloader all take you to the bootloop of the merging dots.
3. Recovery Mode takes you to the "No Command" screen (see pic)
4. From the No Command Screen, a quick button combo of Power/Vol UP/Vol Down takes you to the Android System Recovery screen (see pic)
5. I have tried the wipe data/factory reset option to no affect, still get bootloop.
Thank you for any help you can provide!
The USB debugging toggle is only to use adb with a booted ROM. Your ROM isn't booting. Fastboot and adb side load will work in boot loader and recovery, respectively. As for Mac commands, not my wheelhouse.
sent by mirrorflash Morse code
If you want wug's toolkit, boot your tablet into bootloader, and check the option for "Soft Bricked/Boot Loop" on the toolkit. Then do the flash stock and unroot.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...
I replaced my GNEX10 battery last january. Aside from the battery calibration being off... (which eventually corrected itself!) it's been working fine. As of late it had rebooted itself while I was using it a few times. A few days ago, it had enough battery such that I left it on overnight. I picked it up the next morning and the notification lamp was flashing so I knew it was still on. I tried to wake it up without success. Usually a quick tap on the power button should do it. Nothing. So I rebooted... and on the google logo it stuck. I knew that a factory reset was probably in order since I didn't do it when I replaced the batter... I got it into the recovery screen... but I could not get the menu. I likely didn't press the right volume rocker. Then I tried again... booted to the bootloader, and selected recovery. This time, and since, only the google logo comes up. No andy on his back with "no command". It just tries to boot into something. I can't do a factory reset this way.
I tried the Nexus Root Toolkit. I can only get it to recognize the device if it's in the bootloader... when I try to use it to boot to recovery, same thing and the NRT says waiting for device... and gets no further. I tried to use it to flash (stock?) recovery but the N10 just sits there on the twrp logo screen and nothing more after temporarily booting into twrp. Just keeps saying "waiting for device"
Anyone have any suggestions! Getting seriously bummed!
So one more data point... I manually rebooted into the bootloader after trying to flash the stock recovery using the NRT. Then it appeared to flash the recovery image.... here is the bit of the log where it ended up:
Checking Fastboot Connectivity
fastboot devices
R32CB04GHGT fastboot
+ Fastboot Device Connected
Flashing Stock Recovery to RECOVERY partition...
fastboot flash recovery "C:\usr\NRT\data\Recovery_Stock\recovery_stock_mantaray_5.1.1_LMY49J.img"
Temporarily Booting TWRP...
fastboot boot "C:\usr\NRT\data\Recovery_Custom\TWRP\twrp-3.0.2-0-manta.img"
Flashing 'undo-perm-recovery-signed.zip'...
Waiting for your device...
That's where it ended up... not getting any further. Once again, attempting to boot into recovery gets it stuck on the Google logo.
How screwed am I? Is there a thread somewhere in the forum anyone can point me at?
Well, in spite of the crickets... I understand. I've managed to resurrect my Nexus 10. Alas there are no good contemporary replacements. The last so-called nexus table google put out there was too damn expensive in the first place and they seem to have abandoned the tablet market to others.
So the key question here: So long as I can get this tablet into the bootloader is it generally possible to reflash a stock image? I'd like to know of any types of caveats etc. The mystery I have still though is: How or why did my N10 get into this state (of of only being able to get to the Google screen) in the first place? I didn't have any questionable apps installed etc. I was totally on stock. One thing that did happen a week or two prior to my tablet going belly up... was somehow the thing lost my google account info and gmail had none of my accounts in place... it was very odd.
I did have to wipe the system because evidently you can't flash anything onto a locked bootloader (the Nexus Root Toolkit by wugfresh is up to date so far as the N10 is concerned at least). I know I could have resorted to using fastboot.exe and the adb directly but this was a touch easier. Alas the backup options for it say you need an unlocked bootloader which seems to be a chicken/egg issue if you've always been on stock.... so it goes.