Pixel 6 stuck in bootloop after automatic reboot (BP2A.250605.031.A5)

w0lfzb3rg

Hi,

my Pixel 6 (oriole) started rebooting by itself and got stuck in a bootloop.

At first yesterday evening it managed to boot back into the OS and i could briefly read an error message about the Kernel crashing. Unfortunately i could not copy the error message or take a picture of it.

At the moment, it shows the Google logo, then (only once the GrapheneOS logo briefly) and restarts again.
Eventually it ends up in recovery mode after pressing power and lower volume button. When I select “Power off”, the device turns off for a few seconds and then powers on again automatically.

Current build: google/oriole/oriole:16/BP2A.250605.031.A5/2025102801:user/release-keys
Bootloader: locked
GrapheneOS channel: Stable

What happened:

The device was running normally, then suddenly rebooted on its own.

Since then, it keeps looping and never reaches the lock screen.

Recovery shows:

Command: "/system/bin/recovery" "--rescue"
Waiting for rescue commands...
Install from ADB complete (status: 1)
I:Clearing BCB

Attempting adb sideload results in:

recovery update package is older than the current build,
expected a build newer than timestamp 1761691051
but package has timestamp 1761691050
and downgrade not allowed.
Installation aborted.

No filesystem errors or mount failures appear in the recovery logs.
Kernel version: 6.6
Verified Boot state: yellow (bootloader locked).
Data, system and vendor partitions mount successfully.

Current situation:

Device can enter fastboot and recovery sporadically.

Cannot boot into the OS.

Cannot stay powered off (it reboots automatically after a few seconds).

Data partition appears intact and should be recoverable once a compatible build is available.

[removed]

Thankful for any help!

Mod note: removed AI generated content because it's not allowed.

wizoatk

You might want to try the sideload with the 102801 update.

https://releases.grapheneos.org/oriole-ota_update-2025102801.zip

w0lfzb3rg

Thanks a lot. I will try.

I also want to confess that I used ChatGPT to ease translation as I’m not a native speaker. I just became aware of the other thread that there is a well made point why not to use AI translation.

nandohyphen1

w0lfzb3rg I also want to confess that I used ChatGPT to ease translation as I’m not a native speaker. I just became aware of the other thread that there is a well made point why not to use AI translation.

Its OK to use AI to translate as long as it doesn't change what you are saying and that you specify that your post was translated with AI (I think just putting that in the first post should be OK)

w0lfzb3rg

At the moment im having trouble starting the recovery mode after the fastboot. I now attached my phone to a charger hoping that this will help.

Is there anything else i can try to get into recovery mode?

I also one saw the GrapheneOs logo while booting. Someone sad i should press and hold volume down to boot in safe mode and only load essential apps. Is that correct?

w0lfzb3rg

I had trouble reaching the recovery mode until it eventually worked. I did the adb side load update with the 102801 and the newest stable 110800 version because the first update didn't help. In the current state the phone reaches the pulsating GrapheneOS logo and seems to be stuck there.

Right after performing the last update I checked out the recovery log and found that there are multiple thermal errors.

In the meantime I remembered that I dropped the phone from about hip-height a day before the bootloop trouble started.

Is there a feasable repair I can do to save the data from the phone? Is it possible to tell which part/connector is causing problems?

Beneath I pulled the last page from the recovery log from an image I had taken using ocr from chatgpt:

(If necessary I can provide about 20 additional pages of recovery log)

finished last action PostinstallRunnerAction with code ErrorCode::kSuccess I 11-19 17:48:41.495 438 438 I update_engine: I_sideload: [INFO:update_attempted_android.cc(733)] Processing Done. I 1637.046919 11-19 17:48:41.497 438 438 I update_engine: I_sideload: [INFO:update_attempted_android.cc(975)] Writing I_sideload: [INFO:update_attempted_android.cc(749)] Update successfuly applied, waiting to reboot. I_sideload: [INFO:dynamic_partition_control_android.cc(354)] Destroying Dm-From I_sideload: [INFO:dynamic_partition_control_android.cc(358)] All partitions done I 1637.057512 11-19 17:48:41.508 438 438 I update_engine: I_sideload: [INFO:metrics_utils.cc(341)] Updated Marker 1/22/28 GMT I_sideload: [INFO:dynamic_partition_control_android.cc(105)] Destroying Dm-From LastStrongRef automatically unlinking death recipients: android.hardware.boot.IBootControl I 1637.367362 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone0/temp: Invalid argument I 1637.600097 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone5/temp: Invalid argument I 1637.608614 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone1/temp: Invalid argument I 1637.611551 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone1/temp: Invalid argument I 1637.623356 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone1/temp: Invalid argument I 1637.641497 11-19 17:48:41.508 428 428 W failed to read /sys/class/thermal/thermal_zone0/temp: Invalid argument I 1637.654305 11-19 17:48:41.508 428 428 I: current maximum temperature: 40000 I 1637.614438 11-19 17:48:41.508 428 428 I:sideload/package.zip I 1637.614953 11-19 17:48:41.508 428 428 time_total: 316 retry: 0 target_build: 2025110800 temperature_start: 31000 temperature_end: 40000 temperature_max: 40000 I 1637.615760 I:command 0 finished with 1 I 11-19 17:48:44.071 428 437 W minadbd: sockets.cpp:310 timeout expired while flushing socket, closing