I had TWRP recovery installed but wanted to go back to stock so I can install OTA updates.
Try as I might I can't get stock recovery installed!
I tried SkipSoft Android Toolkit, no joy.
Manually flashing via fastboot from the factory image of various builds, still no joy..
Finally I used the SkipSoft Toolkit to upgrade to Android 7.0 and again still no stock recovery!
Every time I try to boot to recovery I just get a black screen with the green robot in the centre, belly open and a red warning triangle, in 7.0 it says "no command" underneath.
Anyone have any ideas?...
darrenspence said:
I had TWRP recovery installed but wanted to go back to stock so I can install OTA updates.
Try as I might I can't get stock recovery installed!
I tried SkipSoft Android Toolkit, no joy.
Manually flashing via fastboot from the factory image of various builds, still no joy..
Finally I used the SkipSoft Toolkit to upgrade to Android 7.0 and again still no stock recovery!
Every time I try to boot to recovery I just get a black screen with the green robot in the centre, belly open and a red warning triangle, in 7.0 it says "no command" underneath.
Anyone have any ideas?...
Click to expand...
Click to collapse
Hi, darrenspence....
The red triangle with the "no command" message IS the stock recovery.
To access the recoveries menu, you need to press VOL UP and the POWER ON button simultaneously. This key press combo can sometimes be a bit tricky to get the exact timing right, so persevere.
Rgrds,
Ged.
Sent from my HTC One_M8 using XDA Labs
GedBlake said:
Hi, darrenspence....
The red triangle with the "no command" message IS the stock recovery.
To access the recoveries menu, you need to press VOL UP and the POWER ON button simultaneously. This key press combo can sometimes be a bit tricky to get the exact timing right, so persevere.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi Ged, thanks for the advice.
I'm already familiar with the menu options in fastboot, guess I was expecting a more "spectacular" recovery screen, at least with a few simple options!
Have to wait for the next OTA update to see what happens..
Cheers
Darren
darrenspence said:
Hi Ged, thanks for the advice.
I'm already familiar with the menu options in fastboot, guess I was expecting a more "spectacular" recovery screen, at least with a few simple options!
Have to wait for the next OTA update to see what happens..
Cheers
Darren
Click to expand...
Click to collapse
...And those options are there... They're just hidden!
I wasn't referring to the menu options in fastboot... I was referring to the hidden menu options in the stock recovery.
So, whilst on the unspectacular red triangle and "no command" stock recovery screen, do the following...
** Press and hold the Power Button.
** Whilst holding it, press Volume Up once.
The screen will suddenly become a trifle more spectacular.
We're not talking fireworks and acrobats here . Just a few menu options and the version of the stock recovery currently installed, if confirmation is needed.
See attached photographs of the Stock Recovery (from Nougat) on my Nexus 9, showing the hidden menu options. (Apologies for the image quality).
Hope this helps.
Rgrds,
Ged.
GedBlake said:
...And those options are there... They're just hidden!
I wasn't referring to the menu options in fastboot... I was referring to the hidden menu options in the stock recovery.
So, whilst on the unspectacular red triangle and "no command" stock recovery screen, do the following...
** Press and hold the Power Button.
** Whilst holding it, press Volume Up once.
The screen will suddenly become a trifle more spectacular.
We're not talking fireworks and acrobats here . Just a few menu options and the version of the stock recovery currently installed, if confirmation is needed.
See attached photographs of the Stock Recovery (from Nougat) on my Nexus 9, showing the hidden menu options. (Apologies for the image quality).
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ged,
I bow to your superior knowledge!
Found the menu first time! Fairly unspectacular but at least the basic options are there.
I now await the next OTA to see if the device updates or no.. Still rooted via SuperSu systemless but feeling hopeful..
Cheers,
Darren
Related
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
Trying to get my phone into recovery mode. Droid DNA, root and s-off via Moonshine.
When I try to go into recover either through the bootloader or adb, the phone resets, goes dark for a bit, then shows a triangle with an exclamation point hovering over an image of the phone.
I can smother the phone and reboot, but I can't get into recovery.
Thanks in advance.
psetnik said:
Trying to get my phone into recovery mode. Droid DNA, root and s-off via Moonshine.
When I try to go into recover either through the bootloader or adb, the phone resets, goes dark for a bit, then shows a triangle with an exclamation point hovering over an image of the phone.
I can smother the phone and reboot, but I can't get into recovery.
Thanks in advance.
Click to expand...
Click to collapse
What recovery do you have on the phone, CWM ,TWRP? Or are you trying to get into the stock recovery?
Stock recovery.
psetnik said:
Stock recovery.
Click to expand...
Click to collapse
I lifted the following from somewhere....:angel:
Shut down the device. Hold down Volume Down and hold down Power until you boot into the HBOOT menu. Select the RECOVERY option using the Volume buttons. Your phone will show the white HTC screen, then you'll see a black screen. It will take a while but it will say failed to mount sd four times. Wait until it turns into a red triangle with an exclamation point inside the triangle and from there, hold down the Volume Up and then press the Power button. You will see a small list, this is stock recovery
Ha! That worked perfectly. I need to start a different thread now to understand the error message.
Thanks!
I havent been in the rooting/custom rom game for a few years because i never wanted to trip this knox bs.
but now i decided to root my galaxy s5... i am having trouble. i used this CF-Auto root. I followed instructions, used odin in download mode, loaded the file. etc.
My phone reset with:
"Recovery booting" (in blue) ...
"Recovery is not seandroid enforcing" (in red)
"Set warranty bit: recovery" (yellow)
And it will not allow me to do anything anymore. (only download mode actually works now). I tried loading it thru odin again, still the same error.
What should i do??? i would like to root it anyway possible, idc how. i am down to load a new rom on it. i am down for whatever.
PLEASE HELP!!! thanks.,
piffdaddy420 said:
I havent been in the rooting/custom rom game for a few years because i never wanted to trip this knox bs.
but now i decided to root my galaxy s5... i am having trouble. i used this CF-Auto root. I followed instructions, used odin in download mode, loaded the file. etc.
My phone reset with:
"Recovery booting" (in blue) ...
"Recovery is not seandroid enforcing" (in red)
"Set warranty bit: recovery" (yellow)
And it will not allow me to do anything anymore. (only download mode actually works now). I tried loading it thru odin again, still the same error.
What should i do??? i would like to root it anyway possible, idc how. i am down to load a new rom on it. i am down for whatever.
PLEASE HELP!!! thanks.,
Click to expand...
Click to collapse
If you can get it to boot into recovery (hold volume up button, home button and power button . Release power button as soon as phone vibrates. Hold home and power up until menu appears), push volume down button to navigate to Factory reset. Use power button to accept.
Hopefully this will get you up and running. This is one important step that is left out of instructions. Sometimes it isn't needed when rooting, but more often than not I find I have to do this with my phones
k8108 said:
If you can get it to boot into recovery (hold volume up button, home button and power button . Release power button as soon as phone vibrates. Hold home and power up until menu appears), push volume down button to navigate to Factory reset. Use power button to accept.
Hopefully this will get you up and running. This is one important step that is left out of instructions. Sometimes it isn't needed when rooting, but more often than not I find I have to do this with my phones
Click to expand...
Click to collapse
Advice is good, But I would install TWRP recovery and then SuperSU, not CFautoroot.
unfortunately wont let me in recovery. it only lets me in download mode...? should i try the super su ontop of the cf that i already tried?
piffdaddy420 said:
unfortunately wont let me in recovery. it only lets me in download mode...? should i try the super su ontop of the cf that i already tried?
Click to expand...
Click to collapse
Yes
Do what I say in this post, it works, you'll be rooted:
http://forum.xda-developers.com/showpost.php?p=65685380&postcount=148
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
Hello, world! This is my first time posting on the forums, so I'd appreciate grace where it's due, haha. Anyhow, onto my problem. I have an LG K20 V (model # VS501) with bootloader locked and unrooted. I've been able to boot into recovery by simply running
Code:
adb reboot recovery
but the recovery menu never appears, only the android on its back and the words "No Command". I've read up somewhat on the error but no combination of the volume keys and power button (my device doesn't have a physical home button) seems to ever put me through to the actual recovery menu, only booting the phone up normally or no results. I have read a few places that it could be an issue with the cache (no idea how), so would simply wiping the cache fix it? The internet is sparse on info on my specific device and I've always found the answers I'm looking for on XDA so I'm hoping I'll get one for this problem as well. Thanks in advance!
after pressing the keys:there is a blue screen which shows a killed android and an error signal and says no command?if yes you just have to wait and it will go to recovery mode after a bit
paranoic(d) said:
after pressing the keys:there is a blue screen which shows a killed android and an error signal and says no command?if yes you just have to wait and it will go to recovery mode after a bit
Click to expand...
Click to collapse
Not blue, a black screen. And I don't get to recovery by pressing keys, in fact I've tried and I cant. Only with the adb command. Or are you saying I just need to wait a while longer after pressing the key combinations to get past the error?
well.lg phones are secure so i dont really know from them :/.i have used only sony and samsung devices