Pixel 6 Stuck on GrapheneOS Boot Logo (OEM Unlock Disabled)

MrDexter899

Hello,

I have been using GrapheneOS on my Pixel 6 for over a year without any issues. Recently, my device suddenly froze, rebooted, and got stuck on the GrapheneOS boot logo.

Device: Pixel 6
OS Version: GrapheneOS (Android 15)
Problem: Device is stuck at the boot logo and cannot boot into the system.
Recovery Attempts:
I can access Fastboot, Fastbootd, Recovery, and Rescue mode.
I tried sideloading the latest GrapheneOS update via ADB. The process completed successfully, but it did not resolve the issue.
OEM Unlocking: I had enabled OEM Unlocking in the past but later disabled it. It is now disabled, so I cannot unlock the bootloader.

Is there any way to recover my data or fix the device without performing a factory reset?

de0u

MrDexter899 I have been using GrapheneOS on my Pixel 6 for over a year without any issues. Recently, my device suddenly froze, rebooted, and got stuck on the GrapheneOS boot logo.

That is unfortunate. It sounds as if the user data partition has gone bad, perhaps due to a partial storage failure.

MrDexter899 I can access Fastboot, Fastbootd, Recovery, and Rescue mode.

Have you tried safe mode?

MrDexter899 Is there any way to recover my data or fix the device without performing a factory reset?

It is possible that a commercial data recovery service might be able to recover something. This question recently arose: https://discuss.grapheneos.org/d/17801-p6p-not-rebooting

If you go that route, it would be best to operate the device as little as possible, and especially to avoid writing to the device's storage.

MrDexter899

de0u Thank you for the response. Unfortunately, booting into Safe Mode doesn't work; the device vibrates but remains stuck on the GrapheneOS boot animation

de0u

MrDexter899 Unfortunately, booting into Safe Mode doesn't work; the device vibrates but remains stuck on the GrapheneOS boot animation

I'm sorry to hear that. Honestly it's hard to know from the outside whether the situation is due to a flash-storage failure or some freak OS issue. Given the age of the device, a storage failure is unfortunately plausible.

The two options that seem apparent to me would be shipping the device off to a professional data-security company (see thread linked agove above) or booting into Recovery and wiping the user-data partition. Neither approach guarantees data recovery or even recovering the device in a usable state. In some cases a flash storage can be local, so that wiping the user-data partition can result in the device working fine for some time.

I can imagine that you might want to wait a day or two to see if you get a better answer than I have to offer.