Android 'No Command' Boot Error: Recovery Mode Fix That Works

You reboot your phone after an OTA update, or you're trying to factory reset it, and instead of the recovery menu you get a little Android robot on its back with the words "No Command" underneath. Screen's frozen. Your power button does nothing useful. This usually hits right after a failed system update, a corrupted cache partition, or when someone holds the wrong button combo trying to enter recovery. I've seen it mostly on Pixel 4a–6a, Samsung A-series, and a bunch of Motorola G devices after a botched incremental update.

What's actually going on

Recovery mode has two layers. The bootloader hands off to a recovery kernel, and that kernel is supposed to load a small menu UI. The "No Command" screen is the recovery kernel telling you the UI never came up. Either the userdata/cache partition is in a bad state, the OTA package half-installed, or you triggered recovery without the second button press that tells it to draw the menu. It's not a brick. It's not dead. It's just sitting in a mode with no input prompt.

The robot lying down is literally the stock recovery placeholder image. On AOSP-based recoveries, that's what you see before the menu loads. On a healthy device it flashes for a second. On a broken one, it just stays.

The fix — step by step

1. Force a clean reboot first. Hold Power for 20–30 seconds. On some devices (Pixel, OnePlus) it's Power + Volume Down for 20. Let it fully cycle. Half the time the boot succeeds because the OTA just needed one more pass.
2. Get the recovery menu to appear. With the "No Command" screen visible, do this in order:
   • Hold Power for one second
   • While still holding Power, press Volume Up once
   • Release both
   On older Samsung devices (pre-2019), it's Power + Volume Up + Home held together for 3 seconds. On some Motorola and Xiaomi units, tap Power then Volume Down. If nothing happens, try the other order — worst case you reboot and try again.
3. Wipe the cache partition. From the recovery menu:

   Wipe cache partition → Yes
   Reboot system now

   On Android 10+ devices with A/B partitions, the cache wipe option may be gone. If it's not there, skip to step 4.
4. Wipe data / factory reset if the cache wipe didn't help. Yes, you lose app data. Back up first if the phone boots at all via USB debugging. From recovery:

   Wipe data/factory reset → Yes → Yes
   Wipe cache partition → Yes
   Reboot system now

   First boot after this can take 5–10 minutes. Don't panic-wipe it again.
5. If recovery itself is broken (menu never loads even after the button trick), flash the stock recovery and boot image with fastboot. You'll need the matching factory image for your exact build number — not "the latest." Pixel factory images are on Google's developer site; Samsung uses Odin with the correct CSC firmware.

   fastboot flash boot boot.img
   fastboot flash recovery recovery.img
   fastboot reboot

   Wrong build number = more problems. Verify the fingerprint in Settings → About phone before you download anything.
6. Last resort — full reflash. Flash every partition from the factory image (flash-all.bat on Windows, ./flash-all.sh on Linux/macOS). This nukes everything including the bootloader state. Only do this if you've already accepted data loss.

What to do if it still fails

Check these in order before you throw the phone away:

• Battery. A nearly-dead battery gives random recovery behavior. Charge for 30 minutes on a wall charger (not USB from a laptop) before trying again.
• Button hardware. A stuck Volume Up or Power button will keep you looping into recovery forever. Press each button 20 times and feel for a click. If Volume Up is mushy, that's your culprit.
• EMMC/UFS failure. If fastboot can't write partitions and throws FAILED (remote: 'Write protected'), the flash memory is toast. No software fix. Board-level repair or replacement.
• Wrong firmware region. Samsung users especially — flashing a U1 firmware on a U device or vice versa will bootloop or hit "No Command" repeatedly. Match the CSC exactly.
• USB cable/port. Fastboot needs a data cable, not a charge-only one. Swap cables before blaming the phone.

Don't bother with those "one-click Android repair" tools you see advertised. I've never seen one genuinely fix a No Command screen. They just flash generic images that break region locks and knox counters.

If the phone is under warranty, stop here and RMA it. Once you've unlocked the bootloader on a Samsung, the Knox counter trips and you lose warranty permanently. On Pixel, unlocking is reversible but only if the phone is already booting. Nine times out of ten, the Power + Volume Up trick gets you back into the recovery menu and a cache wipe buys another year of life.