If your Pixel 8 is stuck in rescue mode, start with the least destructive fix that fits the screen you can actually reach: try recovery first, then fastboot, then a factory reset only if the phone keeps looping back right away. Picking the wrong state wastes time, can trigger more boot attempts, or wipe data you might still save. This guide shows how to identify each state and choose the next step for a Pixel 8 stuck in rescue mode.

What the screen state means

What the screen state means
A laptop screen shows vertical lines highlighted by a red circle

On a Pixel 8, the screen in front of you matters more than any label you expect to see. Recovery, fastboot, and rescue paths are different, and they fail in different ways. The fastest first move is a forced restart with Power and Volume Up held for 30 seconds, then a check of which screen comes back.

Rescue mode can show waiting for rescue commands. Recovery mode can show no command. Fastboot is the bootloader screen used for checks and menu navigation, and it is also where Android platform tools can talk to the phone.

Rescue mode versus recovery mode

Rescue mode is a troubleshooting state that may hand off to recovery, but it is not the same screen as recovery. Recovery is the Android maintenance environment used for rebooting or wiping. If the phone reaches rescue mode and then stops at waiting for rescue commands, that points to a different path than a plain recovery screen.

How fastboot fits into the path

Fastboot mode is the bootloader menu on the Pixel 8. Fastboot is commonly reached with Power + Volume Down from a powered-off phone. From there, the phone can often be told to enter recovery or rescue mode, and computer-based tools can check status or attempt a reboot.

Exact screen or state seen Most likely cause Safest next action Data risk level and when to stop
waiting for rescue commands Repair flow has not completed its handoff yet, or the phone is waiting for a command from the computer side Wait a few minutes, then try recovery or a restart if the screen never changes Low. Stop if it keeps returning here after a forced restart
no command You are in recovery but have not opened the menu yet Press Power, then tap Volume Up once to show recovery options Low. Stop if the menu never appears after several tries
Instant return to fastboot Boot slot trouble, corrupted boot files, or a lock-state problem blocking a change Check fastboot status, then try a repair flow before wiping Medium. Stop if slot switching fails with a lock error
Repeated boot loop after logo or lock screen Corrupted software, failed update, or hardware fault Try recovery reboot first, then consider reset or repair tools High. Stop if it loops after recovery and fastboot checks

Likely causes, from most to least common

Most often, the problem is corrupted system software after a bad update or a failed boot. Less often, the active boot slot is wrong or cannot switch. A missing USB debugging setup can block adb. Hardware faults can look like software boot failures, especially when the phone keeps looping after the logo.

Corrupted software or a failed update

  1. Hold Power and Volume Up for 30 seconds to force a restart.
  2. If the phone reaches recovery, choose Reboot system now before any wipe.
  3. If the phone returns to the same screen or loops again, move to fastboot with Power + Volume Down.
  4. If recovery cannot complete the boot, prepare for Pixel Repair or, if needed, a factory reset.

Boot slot A/B trouble

Pixel devices use a dual-slot system. A fastboot session can report the current slot with fastboot getvar current-slot. A reported active slot of b does not prove a hardware problem by itself. A lock-state error during slot switching is a stronger sign that the bootloader is blocking the change. (Nvidia)

  1. Enter fastboot with Power + Volume Down.
  2. On a computer with platform tools, run fastboot getvar current-slot.
  3. If the device replies with b, note the slot and try a normal reboot from fastboot.
  4. If slot switching fails with a lock-state error, stop trying to force slot changes and move to repair tooling.

Suppose the phone shows fastboot, reports slot b, and then returns to fastboot after fastboot reboot. That pattern points away from a simple button problem and toward boot corruption or a blocked repair path.

ADB was never set up before the failure

ADB only helps if USB debugging was already enabled and the computer was already trusted beforehand. If that was never done, adb reboot recovery will not help. The command needs Android SDK platform tools on the computer, and the phone must already accept ADB connections.

  1. Install Android SDK platform tools on the computer.
  2. Connect the Pixel 8 with a USB data cable.
  3. Run adb devices and check whether the phone appears as authorized.
  4. If it does, run adb reboot recovery.

Hardware fault or storage failure

Repeated loops after the Google logo, failed recovery attempts, and fastboot returning only briefly can point to hardware as well as software. Storage faults can stop the phone from completing a normal boot. At that point, repeated button cycling is less useful than a repair or service decision.

Rescue mode decision matrix

Use this as triage, not as a guess. Match the screen you actually see, then choose the least destructive next step. If the phone keeps going back to fastboot or rescue mode after a valid reboot attempt, stop treating it like a simple UI problem.

Exact screen/state seen Most likely cause Safest next action Data risk level and when to stop troubleshooting
waiting for rescue commands Rescue handoff is stalled or still waiting Wait a few minutes, then try recovery or a forced restart Low. Stop if it never changes or returns after restart
no command Recovery menu has not been opened yet Press Power, then Volume Up once Low. Stop if the recovery menu never appears
instant return to fastboot Slot or boot corruption, or a blocked boot transition Use fastboot checks, then try repair tooling Medium. Stop if slot switching fails with a lock-state error
repeated boot loop Corrupted software or hardware fault Try recovery reboot, then escalate High. Stop if the loop persists after repair attempts

How do I get my Pixel 8 into fastboot?

Power the phone off, then hold Power + Volume Down together until the bootloader screen appears. If the phone only vibrates or restarts, release the buttons and try again from a full power-off state. Fastboot is the right place to check slot status and reach recovery.

  1. Hold Power and Volume Up for 30 seconds if the phone seems frozen.
  2. Wait until the screen goes fully dark.
  3. Press and hold Power + Volume Down.
  4. Release when the bootloader or fastboot screen appears.

Check that the screen shows the bootloader menu, not the normal startup logo. If it drops back into a reboot loop, the issue is bigger than button timing.

How do I get past the no command screen?

The no command screen usually means recovery is waiting for the menu to be opened. On a Pixel 8, the usual move is Power, then Volume Up. Do not hold both buttons blindly for long periods; use the specific sequence that opens the recovery menu.

  1. When no command appears, press and hold Power.
  2. While still holding Power, tap Volume Up once.
  3. Release both buttons when the recovery menu appears.
  4. Select Reboot system now first.

A common first-time mistake is assuming the phone has frozen and repeatedly pressing both volume buttons. That usually does not help and can blur what screen state you are actually in.

Can adb help if the phone was already trusted?

Yes, but only if USB debugging was enabled before the failure and the computer was already authorized. In that case, adb reboot recovery can send the phone straight into recovery without relying on button timing. If ADB was never set up, skip it.

  1. Install Android SDK platform tools on the computer.
  2. Connect the phone by USB and open a terminal in the platform-tools folder.
  3. Run adb devices.
  4. If the device is authorized, run adb reboot recovery.

If adb devices shows nothing, or the phone asks for trust confirmation that cannot appear, ADB is not the right tool here.

Fastboot checks and slot troubleshooting

Fastboot can tell you whether the phone can still speak to the bootloader and which slot it is trying to use. That matters because a boot loop can come from slot corruption, not just from the recovery screen. A lock-state error during a slot change is a warning sign, not a puzzle to keep retrying.

  1. Enter fastboot with Power + Volume Down.
  2. Connect the phone to a computer with platform tools installed.
  3. Run fastboot getvar current-slot.
  4. If needed, run fastboot reboot once and watch whether the phone returns to fastboot.
  5. Stop if the phone comes back to fastboot immediately or slot changes fail with a lock-state error.

In one reported case, fastboot detected the device correctly, showed slot b, and then refused a slot change with a lock-state error. Another fastboot reboot succeeded only briefly; the phone returned to fastboot. That pattern usually points to a deeper boot problem.

When should you factory reset or use Pixel Repair?

When should you factory reset or use Pixel Repair?
A phone displays Android Recovery options with factory reset highlighted

Use a factory reset when recovery reboot fails and the phone keeps looping back, or when repair tooling cannot clear the fault. If data matters, try every non-destructive option first. Google’s Pixel Repair flow runs in a Chrome browser on a computer, and a repair guide says the Pixel 8 Pro can be fixed that way.

  1. Open recovery and choose Reboot system now first.
  2. If that fails, decide whether your data is worth one more non-wipe attempt.
  3. On a computer, open Chrome and use Google’s Pixel Repair flow.
  4. If the phone still will not boot, return to recovery and choose Wipe data/factory reset.

Do not treat flashing firmware as a no-loss shortcut. A factory image flash commonly wipes data unless a non-wipe method is used, and the package needs to match the device and build requirements. If the phone is still looping after repair attempts, a wipe may be the practical next step.

Prevention is limited here, but one useful step exists: keep the phone updated normally and avoid interrupting a system update or repair flow once it starts.

Still not working?

Still not working?
A hand holds a smartphone showing settings on its screen

If the Pixel 8 still returns to rescue mode, recovery, or fastboot after the steps above, stop cycling through the same buttons. The next escalation is either the Google repair tool, a factory reset, or vendor service if the phone keeps looping after a reset attempt. Hardware faults can look exactly like software boot damage.

Say your Pixel 8 shows waiting for rescue commands, then jumps back to fastboot every time. That pattern is not a reason to keep waiting for long periods. It is a sign to move from on-device recovery to a computer-based repair path or service support.

Keep reading

Frequently asked questions

What is rescue mode on google pixel?

On a Pixel, rescue mode is a repair state that can appear during software recovery. It may show waiting for rescue commands and then hand off to recovery. If the phone only reaches that screen, the next step is usually a forced restart, then recovery or fastboot.

What is pixel rescue mode?

It is not the same as normal startup. It is a troubleshooting path for corrupted software or a failed update, and it can sit waiting for input from a repair process. If the screen never advances, use Power + Volume Up for a forced restart first, then check recovery.

How do I get my Pixel 8 out of rescue mode?

Try a forced restart with Power and Volume Up held for 30 seconds. If the phone returns to rescue mode, move to fastboot with Power + Volume Down, then open recovery and select Reboot system now. If that fails, a factory reset may be unavoidable.

Why does my Pixel 8 say waiting for rescue commands?

That screen usually means the phone is waiting for a repair step or still handshaking with a recovery flow. Wait a few minutes once, then switch to recovery or a forced restart if nothing changes. If it keeps coming back, the problem is not just timing.

Is rescue mode the same as recovery mode on Pixel 8?

No. Rescue mode is a repair state that may lead into recovery, while recovery is the maintenance menu where reboot and wipe options live. If you see no command, you are already in recovery and need Power, then Volume Up to show the menu.

Can a hardware fault cause Pixel 8 rescue mode loops?

Yes. Repeated returns to fastboot, rescue mode, or a boot loop after the logo can come from hardware as well as software. If fastboot checks, recovery reboot, and Pixel Repair do not stop the loop, service support becomes the next practical step.