Pixel 7 boot loop after 2026011000 OTA - can't unlock phone

walhfmf

I updated my phone to 2026011000 today, rebooted from the notification, and now it soft-reboots ₁₀ s after I enter the PIN.

I'm on stock GrapheneOS, locked boot-loader
OTA 2026011000 (update flashed from recovery after having issues just to be sure, tried both panther-ota_update-2026011000.zip and panther-ota_update-2026011001.zip).

Booting from a fully powered off device shows the lock screen and no signal bars, the battery icon is just grey, even on charger.
When I type my PIN it shows black screen with only the gesture pill at the bottom and about 10s later it invariably crashes and reboots to the GrapheneOS animation. Before it crashes, in this half unlocked state, I can open the camera with double power button tap. The camera works but after a few seconds it will show a "process system isn't responding" popup with "Close app", "Wait" and "Show details". None of the buttons respond to the touch. After a bit in the camera app the phone crashes and reboots.

Also I noticed that after a tried unlock and a reboot I can select other users (they were greyed out before when starting from a cold boot) but unlocking any of them with PIN also fails.

The boot loop I get i a soft reboot only (no Google logo) so with this plus the "process system isn't responding" thing it really seems like a userspace failure. I'm on the a version after 2026010800 which the changelog says included:

add "Reboot to Safe Mode" power menu button in Before First Unlock state
add workaround for upstream UsageStatsDatabase OOM system_server crash
add workaround for upstream WindowContext.finalize() system_server crash
disable buggy upstream disable_frozen_process_wakelocks feature causing system_server crashes for some users

I can see the Reboot to Safe Mode button but clicking it does nothing (and weirdly, neither does clicking power off or reboot)

I know some people were experiencing bootloops with UsageStatsDatabase OOM but I don't know if it's the same issue I'm having.

I can't manage to get adb shell (either device won't show or says unauthorized and I can't unlock so can't authorize) so I don't have any logs..

I don't think it's related to a power failure during update or anything like that although I cannot see the phone's charge state right now. I do remember having very little storage space left so idk if that could have impacted the update.

Anyways the only thing I haven't tried is a factory reset because I really don't want to lose my data. I promise I'll do backups more often but if someone could help me with this it would be immensely appreciated 🙏

GrapheneOS

walhfmf There's a known upstream bug in Android 16 QPR2 impacting many stock Pixel OS users for people with very low storage space. We haven't been able to get the logs we need to make any progress on resolving it ourselves. If you had low storage space, that's likely the issue you're having and there's likely not going to be a quick resolution.

walhfmf

GrapheneOS Well, shucks! Thank you. Do you think it is worth letting the phone be and wait for an eventual fix that I can sideload to unlock the phone? I could use a spare for a while.

Also if you have any ideas on how to get logs off the device I'd be happy to try.