If your Pixel 7 freezes on the Panther logo or early boot, first identify the state: looping, hanging before the lock screen, or failing after a recent update. Start with the least destructive fix, and only wipe or flash if you have a backup plan. Ignoring the boot state can turn a recoverable startup glitch into lost photos and a harder repair. This guide shows how to tell each failure state apart and which steps to try in order to protect your data.
Common causes and freeze symptoms
A Pixel 7 stuck on the Panther logo usually means Android has started loading but cannot finish the next stage. That is different from a phone that is completely dead, and different from a true boot loop that keeps restarting on its own. A recent update, low storage, damaged system data, or a charging problem are common reasons.
Panther is the Pixel 7 codename used in factory image and repair guides. If a guide says Panther, it is pointing to the Pixel 7 variant, not a different phone. That matters when you choose firmware or check flashing instructions.
Likely causes, from most to least common
- Recent OTA update stalled: The phone may hang after rebooting into a new build, especially if the last change was an update.
- Low storage at startup: Very little free space before the problem started can leave too little room for boot-time work.
- Corrupted system or app data: Bad data can stop the phone before the home screen appears.
- Battery or charge problem: A weak battery can make startup look frozen even when the phone is still trying.
- Hardware fault signs: Repeated failure with no detection in recovery or fastboot can point to hardware.
How this differs from a boot loop or bricked bootloader
A freeze sits on one screen. A boot loop restarts again and again. A bootloader problem is different again: the phone may enter fastboot, show device state details, or fail to respond to normal boot commands. If the phone still reaches Google logo, recovery, or fastboot, it is not the same as a dead bootloader.
Say your Pixel 7 reaches the big G with a progress bar and then stops for 30 minutes after an update. That points more toward a stalled boot than a hard failure. If the screen never changes and no vibration or restart occurs, that is a stronger clue than a phone that keeps rebooting every minute.
What should you try first?
Start with the least destructive checks: force restart, charge the phone, then wait long enough to rule out a slow boot. If the problem started right after an update, give the device a little more time before you move to recovery or flashing.
- Press and hold the power button until the phone restarts.
- Connect a known-good charger and leave it alone for at least 30 minutes.
- If the phone was just updated, let it sit through one more boot attempt after charging.
- Watch for any sign of a different stage, such as a recovery screen, charging icon, or fastboot screen.
How long should you wait before assuming the boot screen is frozen?
A boot logo stall becomes worrying after more than 20 minutes. That is long enough to separate a normal slow start from a stuck startup process. If the phone is still changing icons, vibrating, or moving past the logo, wait a bit longer. If nothing changes at all for that long, move on.
Why charging comes before deeper fixes
A nearly empty battery can make the phone appear hung. Charge first because a low battery can block recovery, fastboot, and flashing steps. If the phone feels warm but does not progress, that still does not rule out low charge.
Can recovery mode fix it?
Recovery mode can help if the Pixel 7 still responds to button combinations and reaches stock recovery. It can reboot the phone, and sometimes it may offer a factory reset. It cannot repair every startup failure, and cache wiping is not normally part of Pixel 7 stock recovery.
- Turn the phone off as fully as possible.
- Use the bootloader first, then press Volume Down and Power to reach the bootloader screen, and from there choose Recovery mode.
- If you see No command, hold Power and tap Volume Up once to open the menu.
- Choose Reboot system now first.
- If a cache option appears, use it only if the menu offers it directly.
- Choose Factory reset only if photos are already backed up or data is expendable.
Should you wipe cache on a Pixel 7 stuck at startup?
Only if stock recovery offers a cache-related menu item. Pixel 7 recovery does not normally expose a cache wipe, and when it is absent, there is nothing to clear. Even when available, cache wiping is a limited fix; it will not solve corruption in the system partition or damage from a failed update.
What if the No command screen appears?
That screen is normal in stock recovery. It does not mean the phone is broken. Use Power with a single Volume Up tap to reach the recovery menu, then choose the reboot option before trying anything more invasive.
Can ADB or fastboot still help?
ADB and fastboot can still help if the Pixel 7 is visible to a computer. ADB is useful when the phone boots far enough to accept commands, and fastboot is useful when the device reaches bootloader mode. If the phone is not detected, those tools stop being useful for simple recovery.
- Connect the phone to a computer with a known-good USB cable.
- Run
adb devicesand look for a listed device. - If ADB sees it, try
adb reboot. - If the phone is in fastboot, run
fastboot devicesto confirm detection. - Check battery health before flashing with
fastboot getvar battery-voltage.
What does device state: locked(unlockable) mean?
In fastboot, locked(unlockable) means the bootloader is still locked, but the phone is eligible to be unlocked later if OEM unlocking is enabled in Android settings. That is not the same as an unlocked bootloader. A locked phone can still be flashed with official paths in some cases, but unlocking changes data security and usually wipes data.
Why battery voltage matters before flashing
A low battery can interrupt flashing. That check helps avoid interrupting a flash on a weak battery. If fastboot getvar battery-voltage shows a lower value, charge longer before trying a factory image.
Pixel 7 startup decision table
Use this table to match the exact screen or state before you choose the next step. The safest action depends on whether the phone is still visible to recovery, ADB, or fastboot.
| Screen shown | Likely failure type | Data at risk? | Recovery / ADB / fastboot usable? | Safest next action | When to stop and escalate |
|---|---|---|---|---|---|
| Google logo with spinner, then a big G with a progress bar | Boot stall after update or system data issue | Possible, but not immediate | Sometimes recovery; sometimes ADB or fastboot | Force restart, charge, then enter recovery | If it stays unchanged for more than 20 minutes and recovery does not load |
| Google logo flashes, then restarts again and again | Boot loop | Yes, if you reset or flash | Often fastboot is still available | Check fastboot, then recovery if available | If the loop prevents detection by adb devices and fastboot devices |
| Recovery screen or No command | Stock recovery reached | Only if you factory reset | Recovery usable; ADB sometimes limited | Try reboot system now first | If recovery cannot finish a reboot and reset is the only option left |
| Fastboot screen with device state text | Bootloader path still alive | Possible if you flash or unlock | Fastboot usable | Check device state and battery-voltage | If the phone cannot be detected or the battery is too low |
| No screen change, no detection | Possible hardware or deeper power fault | High if you keep forcing resets | Usually not usable | Charge longer, then try one more forced restart | If still invisible after charging and force restart |
A common first-timer mistake is to see the Google logo and jump straight to a wipe. Suppose the phone started showing the logo after a storage warning and a reboot from settings. In that case, recovery and fastboot checks are worth trying before anything that erases photos.
When should you flash a factory image?
Use a factory image only after recovery and fastboot checks indicate the phone is still reachable and the battery seems ready. This is the last-resort restore path when startup stalls persist and safer fixes fail. A factory image usually wipes user data, so it is not a step that preserves photos.
- Confirm the Pixel 7 appears in
fastboot devices. - Run
fastboot getvar battery-voltageand aim for 4200 mV before flashing. - Match the factory image to the Pixel 7 Panther variant.
- Flash only official image components from the Google package.
- Expect user data to be erased unless the repair path explicitly says otherwise.
What if your Pixel 7 is stuck after an update?
A post-update stall often points to a bad first boot, a storage squeeze, or a system-data problem rather than a broken screen. If the phone still reaches fastboot or recovery, try rebooting first, then consider a factory image only if the device keeps failing after those checks. Do not assume the update itself is the only cause.
Is my Pixel 7 hard-bricked if it only shows the boot logo?
No. A device that still reaches the boot logo is not the same as a hard-bricked phone. Hard-brick signs are more like no display, no charging response, and no detection in recovery, ADB, or fastboot. If fastboot still opens, there is usually still a recovery path.
Still not working?
If the phone will not boot after force restart, charging, recovery attempts, and fastboot checks, move to the least invasive remaining path you have left: a factory image if the device is detected and battery voltage is acceptable, or vendor support if it is not. Stop trying random resets once the phone stops showing up in recovery or fastboot.
Contact Google or a repair center sooner if you see no detection over USB, repeated power loss, a charging fault, or signs that the phone never reaches recovery or fastboot. At that point, software steps are unlikely to solve the problem alone.
Frequently asked questions
Why is my Pixel 7 stuck on the Panther logo?
That usually means the phone is starting Android but cannot complete the boot sequence. The most common next checks are a restart, then charging, then recovery mode.
How do I fix a Pixel 7 stuck on the Google logo?
Restart the phone, then charge the phone and try recovery through the bootloader with Volume Down + Power. If recovery opens, choose reboot first. If it does not, check adb devices or fastboot devices from a computer.
Will a Pixel 7 boot logo issue erase my photos?
Not by itself. Photos are at risk when you choose a factory reset, unlock the bootloader, or flash a factory image. Recovery reboot options do not usually erase data, but a reset from recovery does.
Can ADB or fastboot fix a Pixel 7 stuck on the boot screen?
Yes, if the phone is still detected. Use adb devices to check ADB visibility and fastboot devices for bootloader mode. If detected, adb reboot is a safe first command, and fastboot getvar battery-voltage should be checked before flashing.