Database Users

help with bootloop and "no command"

I rooted my N10 using CF-Auto-Root without unlocking the bootloade (on purpose). The N10 has been working fine and I loaded 10G of personal files. Then I sideloaded an old version of the LBE privacy guard. It installed, but then when I returned to the homescreen I got bootlooped.
I turn it off and back on, and I got the dreadful android-with-red-triangle saying "no command".
I could get into the recovery mod using power+volume up/down. "Restart bootloader" got me back to the recovery manual; "recovery mode" or "start" got back to the red triangle. I was able to turn it off. The battery is at 80%.
Is there a way I can wipe my N10 and do a factory reset? I did not unlock my bootloader; is that why I can flash a factory image?
Since I can't boot up the N10, at this point I probably can't use adb to remove the bad apk?
I'd prefer not to unlock the device, in case I need to RMA back... And I'd rather not return it at all, since I just uploaded lots of personal info...
Your help is **most** appreciated.

I think that if you press power, volume up and volume down at the red triangle screen it will get you to the stock recovery. You should read the stickies in the two development sections lots of people needing to do factory resets after unlocking.
Sent from my Nexus 10 using xda app-developers app

Sounds like you are getting into fastboot mode fine, so worse comes to worse, you can unlock it, flash a factory image and re-lock it ..
Of course doing that you are going to loose all your data ..
Check out the tut's for flashing factory from fastboot, or you could use mskip's toolkit ..

[Q] How can I fix a bad recovery flash?

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.

[Q] Issue after flashing stock

So basically, from running PA, i decided to try stock 4.4.2, so using the nexus root toolkit, i tried to do it, however once it said it was all done and ready, my nexus 7 remained on the bootloader screen, and when i clicked start from that, it said boot failed. So in the bootloader menu i pressed restart to see if that'd do anything, but now it won't boot up at all, not even to the google screen and there is no charge screen when plugged in. It was running the 4.13 bootloader and i think i needed the 4.23 or 4.19 for 4.4.2, but i don't see how that would have caused a failure because doesn't the bootloader get flashed and therefore updated when flashing stock?
If anyone could help that'd be truly great

Can you at least get into the recovery of your device?

I can't get it to turn on at all
Happy christmas by the way :laugh:

Youve held down your power button and used other button configs? I had an issue almost like that, but I wiped everything. I was able to reflash with under fastboot. If you can at least get the boot loader up you can use the NRT to get back to stock.

i can't seem to, its completely blank, i'll give it another go for longer

TWRP Frozen on load Screen Help!

So here is my predicament, I got a warranty Axon 7 replacement. Was going through the procedures to get everything setup. I got everything done and flashed RR. Booted up RR and then hit the "Enter Password Screen", which I remember from my first time the data partition needed to be reformatted with a new file system. Here is where my idiot self screwed up. I accidentally chose the system partition used xfat 4 and now TWRP won't load back up. I have one of those devices where EDL is not longer accessible from the hardware keys, it boots into DFU mode instead.
Things I've tried:
- I've tried getting into EDL mode from fast-boot modifications, It simply reboots normally and the whole system is frozen
- I've tried Re-Flashing TWRP using the Axon 7 Toolkit and it freezes on the TWRP load screen. Any solution to completely re-flash stock software includes getting into EDL mode, which I'm unable to do with the hardware keys. (My old Axon 7 gets into it just fine still)
- (update) Tried to flash a new TWRP image via fastboot as well. It's still frozen on the TWRP load screen.
Things I can do
- Get into Fastboot
- Get to a Twrp loading Screen
- Sit on the ZTE logo or unlocked boot loader screen at startup
If anyone can be of assistance, I'd greatly appreciate it. I really do love this phone! If you need more info just ask, I'm happy to provide it. Generally I figure these things out when I screw up(which has happened more often than I care to admit) but I'm honestly stuck here and at a loss of what to do to fix this issue. If anyone has any suggestions, I'd love your help!
UPDATE/EDIT - I figured out a solution! I pulled a factory Image from the EDL Files and pushed it via fastboot. I'm not back into TWRP! Wahoo!

Nexus 10 boot stuck on google logo... bootloader ok, but recovery does same thing.

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.