os-issue-tracker icon indicating copy to clipboard operation
os-issue-tracker copied to clipboard

Post-OTA reboot → System UI crash, black screen

Open TonySmol opened this issue 1 week ago • 5 comments

Good afternoon. Right after the system update completed, I tapped the “Reboot” button, stepped away for about two minutes, and upon reboot, the device displayed an error overlay (while the system itself was partially running) stating: “System UI isn’t responding.” After dismissing the dialog, the screen went black and remained unresponsive — no further input was processed. However, pressing the power button brought up the standard Android power menu (white overlay with three options: Lock, Power off, Restart).

At one point, I accidentally entered Recovery mode, which only displayed two options: Wipe data/factory reset and Reboot system now.

I expected that in case of a boot failure, Android would automatically fall back to the previous (working) A/B partition (if supported). What should I do now?

pixel 6a

TonySmol avatar Dec 14 '25 19:12 TonySmol

Reboot the device so it can roll back.

thestinger avatar Dec 14 '25 19:12 thestinger

Перезагрузите устройство, чтобы можно было выполнить откат.

Naturally, I rebooted. I tried installing the OTA archive from recovery, but the timestamp on the archives, even the alpha ones, was one lower. So I'm sitting here waiting for the new release.

TonySmol avatar Dec 17 '25 08:12 TonySmol

If you're not able to obtain logs, it will be hard to resolve.

thestinger avatar Dec 17 '25 08:12 thestinger

Если вам не удастся получить журналы ошибок, решить проблему будет сложно.

So, surely there are some common repair methods for this situation? For example, my theory, which I can't test yet, is to try flashing the firmware or OTA archive over it, since recovery works. What do you think? And in general, the A/B partitions only change if the boot fails? Is that why I'm having problems?

TonySmol avatar Dec 17 '25 08:12 TonySmol

was one lower

maybe you use security builds. their build numbers ends in "01", while regulars in "00". You can rename build number in the download link, so you can download the latest security build.

U-ENERGY avatar Dec 18 '25 03:12 U-ENERGY

was one lower

maybe you use security builds. their build numbers ends in "01", while regulars in "00". You can rename build number in the download link, so you can download the latest security build.

I didn't understand anything, but my approach fixed everything. I even thought the patch notes mentioned me, but maybe that's a bad translation)))

So, download the alpha version archive and save it via recovery. Thanks everyone, the problem is gone.

TonySmol avatar Dec 18 '25 10:12 TonySmol