GrapheneOS version 2025030800 released

lumzl

Since the update, my device shows a red "You device is corrupt" warning. I didn't really understand what happened, I just rebooted my phone after the update. (Pixel 7a)

GrapheneOS

lumzl That sounds like SSD data corruption. It should automatically roll back if it fails to boot several times regardless. Did it roll back and boot up the old version again?

GrapheneOS

co77 Try resetting Bluetooth & Wi-Fi settings via Settings > System > Reset. It's unfortunately not split up between the two so you have to clear both and add back your Wi-Fi networks. You could try using ADB to clear only Bluetooth data but we don't have time to figure out how to do that right now to give you a command. Using pm clear com.android.bluetooth may work but may not be enough.

co77

GrapheneOS

Thanks, its working again after clearing data using adb.

lumzl

GrapheneOS No, it just showed "the device can't be trusted" and booted fine, but the integrity IDs are different, that's my main problem. here: https://imgur.com/a/oTm88JU . Sorry for such blurry photo, taken on an old phone.

GrapheneOS

lumzl That's very strange and quite concerning. It's hard to understand how it could boot if that's the case. Try booting into recovery and sideloading the latest update again. See https://grapheneos.org/usage#updates-sideloading for instructions. You can download it from the releases page. You could try sideloading a 2nd time if the 1st time doesn't work.

lumzl

GrapheneOS No, that didn't work either. It's really weird. I have sideloaded the system update twice, nothing changed(integrity IDs too). what can I try, factory reset? Thanks for your help!

de0u

lumzl Does the sideload succeed, or does it return an error?

lumzl

de0u it succeeds, but still outputs that image: https://imgur.com/a/oTm88JU . I tried different cables, networks, etc. Still nothing.

de0u

lumzl Ok, I just compared the picture to the web site and I think the signature hash in the picture is the correct hash for the 7a according to the web site. Can you say what you mean by "the integrity IDs are different"?

GrapheneOS

lumzl It's supposed to show that and the hash appears to match what it's supposed to be. See https://grapheneos.org/install/web#verified-boot-key-hash.

lumzl

de0u You're absolutely right. I stupidly thought that these two lines should be the same, even though there is only one, lol.
This is probably a hardware issue, and it has nothing to do with GrapheneOS. My device just died for no reason. I'll try flashing factory image anyway. Thanks for the help!
Here it is: https://imgur.com/a/eSq4GvM

lumzl

GrapheneOS Yeah, sorry for wasting time. Thanks for help!

ToffoliGate

Dear team and users,
for me the haptics on this version are really f'd up. Pixel 8 has one of the best vibration motor I ever used, and the haptics were perfect. Now, agree this update, I would describe them very "springy", with reverb, and unpleasant. Have you made some modifications or is it something that Google screwed?

Thank you.

Edit: I searched the forum, and it may be Google's fault: https://arstechnica.com/google/2025/03/bad-vibes-google-may-have-screwed-up-haptics-in-the-new-pixel-drop-update/

DeletedUser216

ToffoliGate I agree with you.
The haptics feel very strange. I am using 3-buttons-navigation and since the update the buttons don't work like before. I often have to tap a seconds time. I have the feeling that you now have to press the buttons more centrally.

bzybee

ToffoliGate lumzl

Just found your comments after posting a thread. Experiencing the same thing with 2025030800.

lumzl

lumzl Ok, as a result, there was a problem with the software. flashing the factory image fixed all the problems. That's really weird.

othemad

SCRCPY not working after this release. Any help please

Kira902

I can no longer long press the home button to call assistant app...

JollyRancher

Pixel 9 Pro running 2025030800

The Messaging App isn't working in secondary profiles. It sends & receives in Owner but does neither in a secondary profile.

Other messaging apps (QUIK and Fossify) work as normal.

The issue didn't exist before the 2025030800 update.

JollyRancher

JollyRancher
And it fixed itself on the third restart of that profile. No clue what was going on.

« Previous Page Next Page »