Hi, I remember that today in the morning my phone said that the latest update was installed, but I didn't reboot yet. Then some when later I ran out of battery and when I plugged the phone in it greeted me with "Your device is corrupt. It can't be trusted and may not work properly."
My first thought was to switch boot slot, but that doesn't seem to work when locked. Then I thought about sideloading the latest update via https://grapheneos.org/usage#updates-sideloading but that resulted in "ErrorCode::kInstallDeviceOpenError". I have to admit that I'm not used to locked devices, is there anything else I can do? I can't even unlock it since I'd have to get to the OEM toggle in the developer settings first, right?
Pixel 6a won't boot after 2024022300 update and empty battery
herndlm man this is concerning you’re telling me that it locked you out of your phone and you can’t even charge the battery?
Sporeondeloreon charging is not an issue, that works without booting. The battery is not the problem any more :)
- Edited
oh weird, I swear it was boot looping and I tried multiple times, but when trying to enter recovery I randomly hit the volume up button after the boot continued after the corrupt message and it succeeded. I'm slightly worried though since I have no clue what just happened hmm
EDIT: first thing I'll do is enable OEM unlocking. just in case ...
EDIT2: just confirmed that it's still using the same slot and rebooting works. The "device is corrupt" message stayed, was that the "normal" one when booting? I was sure the behaviour was different, like I need to actively click through it now, while before it would continue booting without that. I'm starting to question my sanity, I guess it was never bricked after all 🤦♂️
Aah I see, instead of https://source.android.com/docs/security/features/verifiedboot/boot-flow#dm-verity-corruption I have https://source.android.com/docs/security/features/verifiedboot/boot-flow#dm-verity-corruption
I tried https://grapheneos.org/usage#updates-sideloading and this time it worked fine. Afterwards the verity corruption message on boot is still there though.
herndlm When there is an update and your phones battery dies, it gets stuck inbetween I believe. This is why A/B on android exists.
From what I understand, attempting to boot it enough times while plugged in will fix it.
If you disabled OEM unlocking, you would have to go into the settings. You can check by running the unlock command in fastboot (this will wipe the data tho)
I would just try to boot a few more times and see what happens