My phone was updating to Android Marshmallow 6.0 and everything was going smoothly until the little green android bot appeared dead on the ground with an exclamation point in a red triangle above it with the text "No Command." below it. I've tried going into recovery mode and cleared the cache, but still no luck. Please help!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
No Command screen after system update
- Thread starter aotoole
- Start date
I think I'd start with the Verizon Software Repair Assistant. It's not always up to date (in other words, it may not have the Marshmallow update yet - it tends to lag the over the air updates), but it may help.
https://www.verizonwireless.com/support/knowledge-base-116950/
Let us know if that works. If not, your best bet may be to visit a Verizon Wireless Store, tell them that your phone bricked when you tried to apply the update, and see if they can either help or get you a replacement.
https://www.verizonwireless.com/support/knowledge-base-116950/
Let us know if that works. If not, your best bet may be to visit a Verizon Wireless Store, tell them that your phone bricked when you tried to apply the update, and see if they can either help or get you a replacement.
test post
DonnyJr
Lurker
Hi, I had this problem too with my Droid Turbo 2. The Software Upgrade Assistant (which I was told is the same as repair assistant by Verizon rep) did update my device and it did eventually turn on correctly.
However, I'm having problems with it again. Last night the battery ran out and when I tried to turn it back after plugging it in I'm getting the No command screen again. I used the SUA tool but all it does is tell me my device is up to date and won't do any sort of repair. I can access my boot menu but not sure if a factory reset is the way to go at this moment.
Any suggestions?
However, I'm having problems with it again. Last night the battery ran out and when I tried to turn it back after plugging it in I'm getting the No command screen again. I used the SUA tool but all it does is tell me my device is up to date and won't do any sort of repair. I can access my boot menu but not sure if a factory reset is the way to go at this moment.
Any suggestions?
Can't you hold down the power button and tap the volume up button to get the menu and then tap the power button to reboot?
... Thom
... Thom
DonnyJr
Lurker
Every time i do tell it to reboot, it cycles the Motorola M beginning screen and even eventually goes to the no command screen. doesn't tell me it failed to boot or anything.
If there's a boot up problem. Will a factory reset even do anything? Or will I need to find an older OS version (currently on the newest Nougat) and manually install that from an SD card?
Thanks!
If there's a boot up problem. Will a factory reset even do anything? Or will I need to find an older OS version (currently on the newest Nougat) and manually install that from an SD card?
Thanks!
Im having same problem. Continually reboots, but never makes it to the animated (second) Motorolla splash screen. Goes to "No Command" screen after the first one times out. Have tried reboots and diagnostic screen, nothing seems to make any difference.
Was fine before Nougat. Since Nougat, at least 20 apps crash instantaneously upon startup.
Was fine before Nougat. Since Nougat, at least 20 apps crash instantaneously upon startup.
Not loading ... did you charge your phone to 100%? That was the earlier solution noted.
Failing apps ... did you do a Wipe Cache partition after the update?
... Thom
Failing apps ... did you do a Wipe Cache partition after the update?
... Thom
I didnt try the charging. As a prior user mentioned, the level of battery charge does not appear, just that the battery is charging.
In the end, I unseated the SIM card & microSD card, then I noticed the battery charge level appeared when the device was off and plugged in. So I tried to start the device and it came up. I put the SIM card in, all OK. I put the MicroSD card in, then rebooted, and device came up again (woohoo!).
Then did Wipe Cache, and then phone was back to not booting up again. So tried process again, and the device booted. The app instability continues though, but one app that wouldnt start at all before worked for about 5 seconds before crashing this time.
Wondering if just tossing a new MicroSD card in might be worth it.
In the end, I unseated the SIM card & microSD card, then I noticed the battery charge level appeared when the device was off and plugged in. So I tried to start the device and it came up. I put the SIM card in, all OK. I put the MicroSD card in, then rebooted, and device came up again (woohoo!).
Then did Wipe Cache, and then phone was back to not booting up again. So tried process again, and the device booted. The app instability continues though, but one app that wouldnt start at all before worked for about 5 seconds before crashing this time.
Wondering if just tossing a new MicroSD card in might be worth it.
The other user charged the battery to 100% before doing anything else.
... Thom
... Thom
DonnyJr
Lurker
Hi all,
I'm back with a semi permanent solution. So, charging my battery to 100% must have been a fluke. Doesn't seem to work anymore other than that one time. The only solution I've come up with to successfully restart my phone is removing the SD card/Sim card and my phone restarts every time. Anytime the SD card/Sim card is in the phone it won't restart and goes to No Command screen.
A full reset of the phone didn't work nor reloading the latest update. I'm not sure why nothing else has worked.
Thanks all. Hope this helps others.
I'm back with a semi permanent solution. So, charging my battery to 100% must have been a fluke. Doesn't seem to work anymore other than that one time. The only solution I've come up with to successfully restart my phone is removing the SD card/Sim card and my phone restarts every time. Anytime the SD card/Sim card is in the phone it won't restart and goes to No Command screen.
A full reset of the phone didn't work nor reloading the latest update. I'm not sure why nothing else has worked.
Thanks all. Hope this helps others.
I suppose I'd do two troubleshooting steps:
1. Start the phone with only the SIM card in, to see if it is something on the SD card.
2. If that doesn't work, ask Verizon for a new SIM card (which is free) and see if it is the SIM card. You can order a new SIM online and provision it for your line yourself, though it's probably much easier just to walk into a Verizon Wireless store and have them do it for you. (I've done both in the past.)
Verizon once told me (not sure if this is actually true) that Android phones should not have SIM cards swapped while powered on, though you can do this with an iPhone/iOS device. If I ever switch in a new SIM, I always do it from powered off.
Same with me. battery state seems to be irrelevant. Removing the SIM/SD card works every time, I now keep a pin behind my rubber case just for this purpose.
Eventually the SIM card completely failed, so I went to Verizon and got a replacement. This worked for about 2-3 weeks, but then the reboot-crash cycle began again intermittently. So now am back to removing SIM/SD card to fix the issue. Annoying, but it works.
I reinsert my SIM once it's powered up. The "No SIM Card" notification sits in my notifier bar for several minutes afterwards, even though I nearly immediately get a carrier connection and everything works normally. It clears itself after a few minutes.
Eventually the SIM card completely failed, so I went to Verizon and got a replacement. This worked for about 2-3 weeks, but then the reboot-crash cycle began again intermittently. So now am back to removing SIM/SD card to fix the issue. Annoying, but it works.
I reinsert my SIM once it's powered up. The "No SIM Card" notification sits in my notifier bar for several minutes afterwards, even though I nearly immediately get a carrier connection and everything works normally. It clears itself after a few minutes.