Pixel 6 stuck at Google logo despite successful ADB sideload (status 0)

lucama

Hi everyone,

I’m dealing with a severe bootloop on my Pixel 6 (oriole) and hoping there's any last-resort way to avoid a factory reset.

The Problem:
The phone is continuously bootlooping, but it only shows the Google logo and then restarts. It never even reaches the GrapheneOS logo. It was doing this before I tried any fixes, and it continues to do so now.

What I've tried:
I managed to get into Recovery Mode and successfully sideloaded the latest Stable OTA via ADB. The process reached 100% on the PC, and the phone displayed Install from ADB complete (status 0).
However, after selecting "Reboot system now", the exact same Google logo bootloop continues.

Previous Context:
A few weeks ago, I experienced a different bootloop. Back then, my ADB sideload failed due to a 1-second timestamp mismatch (I had 'Security preview releases' enabled). In that instance, force-rebooting the phone eventually triggered the A/B partition fallback, booting into the previous working slot and saving my setup.
This time, I'm strictly on the Stable channel, the sideload was 100% successful, but force-rebooting doesn't trigger any slot change, and the phone remains stuck at the very first Google logo.

My Question:
Since the OS was freshly installed via sideload (status 0) but it still crashes before reaching the GrapheneOS boot animation, is there any advanced command (e.g., forcing a slot change via fastboot) or method to fix the boot process / salvage the current userdata before I give up and select Wipe data/factory reset?

Thank you in advance for any insights!

Developer-Dude

lucama do you know if you had Developer Options on? What happens if you power off the phone and let it charge for a while (30-60 mins)?

Novalissoide

lucama Remove any physical SIM if got any.

de0u

lucama

If there isn't a hardware problem (such as a failure in the flash storage), boot loops can mostly be broken down into two categories: corrupted system partitions and corrupted user data partitions.

A corrupted system partition is susceptible to replacing or swapping the system partition, but neither of those will heal a corrupted user data partition. In turn, user-data problems can be at the file-system level or at a higher level (settings, but also other things). If a restart happens very early in the boot process that is more likely to indicate file-system corruption. Meanwhile, since the report mentions multiple independent occurrences of boot loops, this raises that possibility that the device has repeatedly been run out of power, which has a non-zero chance of inducing file-system corruption each time -- in theory that shouldn't happen, but "In theory there is no difference between theory and practice, while in practice there is".

Overall it sounds as if the device may have file-system level corruption of the user data partition. If so, a "factory reset" may be the only option.

lucama

Novalissoide Developer-Dude yes I had Developer Options on. I let the phone charge for 45 mins and it is still stuck at Google logo. I also removed the physical SIM in it.

Developer-Dude

lucama I'm hoping developer options don't have to do with this. Its not recommended to have them on.
https://discuss.grapheneos.org/d/27184-developer-options-changes-unsupported-by-grapheneos/2
Can you enter Safe Mode at all and get the phone to boot? I believe the way to enter it is to power off the phone, and press and hold the power button and volume down button together until it boots. Someone will have to clarify this as I'm not 100%sure. Has the phone been in any prior accidents? Like getting dropped, or the screen cracking or any other physical damage that may have caused this?

lucama

Developer-Dude Regarding the Developer Options, I want to clarify that while I did have them turned on, I never actually changed or tweaked any of the specific settings inside.
Also, when I hold Power + Volume Down, it just takes me to the Fastboot/Bootloader menu. From there, I only have options like "Recovery Mode" (which takes me to the Android with the "No command" text) and "Rescue Mode" (which just sends the phone straight back into the bootloop). I can't reach the actual OS Safe Mode because the phone crashes at the Google logo before the system even attempts to load.
Lastly, to answer your other question: no, the phone hasn't suffered any physical damage, drops, or cracks.

de0u Thank you for the detailed explanation, that makes sense.

Thank you all for the support!

Developer-Dude

lucama thanks for all the info! As de0u said, you may just have to end up factory resetting the phone. And I wouldn't put any data back on it (or make a good backup if you do) to see if this continues happening

Johnnyloans

moist lucama

I'd see what boot slot I'm on right before sideloading an OTA update. Repeat if the phone reboots without sideloading.

https://grapheneos.org/usage#updates-sideloading

If that doesn't work then boot into safe mode:
Hold the volume down button immediately after the screen disappears for: "a different OS is running, warning go to this google site"

Or boot into safe mode first.

moist

Developer-Dude Did you find any solution?? I seem to be facing similar situation and I've tried all the possible solutions. Nothing works as everything comes back to the G logo and the loading indication getting stuck at 90% again and again.