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 ..
Related
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery
brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.
From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway
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.
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
I did root my device with Kingo root. It worked. Then I tried to unroot it with Nexus Root Toolkit v2.0.5. I couldn't apparently and the Goggle update that tried to install yielded an error.
At the end I tried the Flash Stock + Unroot option installing the last Lollipop version. It apparently worked but Android kept loading forever. I could still reach the bootloader.
I tried the same but with a early Lillipop version. The same happened.
And if I try to go to the bootloader -> then recovery -> then the android icon -> then volume up and power button -> then I do see the red led.
So, what can I do? Have I lost my nexus4?
Stay in the bootloader and use fastboot to flash the latest image from Google's site.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Stay in the bootloader and use fastboot to flash the latest image from Google's site.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I have followed the instructions of here forum.xda-developers.com /nexus-4/general/how-to-how-to-flash-factory-image-t2010312, which I'd say does exactly the same as the toolkit.
And the result is the same, the X boot gets ethernal. If I try to do what's said there:
"Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...). "
Then it's the same, I cannot go to that menu, instead I see the red light if it's plugged, nothing if it's unplugged (only a black screen). So I'm stuck (!), I'm still under shock that I've brick my nexus 4 not doing anything really strange.
surprisingly, after having tried to enter to the recovery menu like 8 times (not being plugged), the SO has unstucked and has said "optimizing apps", after which it has been able to start normally.
Curious ^_^
So all is working? Glad you managed to fix it.
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.