Following the security update of May do not install e /os on a pixel (6) that already has place 15 because there is an anti-rool back protection that brick the smartphone when you downgrade from Android 15 to 14.
Not having any warning on the e os documentation I launched the instant from Iodé OS which was running Android 15 with the June security patch.
My phone is completely brick. Nothing lights up anymore.
I was very happy with Iodé OS, but I wanted to try E os 3, and now I’m without a smartphone.
If Android rollback protection is at play here, it didn’t get triggered by going from Android 15 to 14, it got triggered by going from June security patch level to May security patch level (/e/OS 3.0.x).
At least according to the documentation of other devices which has such a warning.
It clearly say this in the oriole install instructions: Warning:
" Before following these instructions please ensure that the device is on the latest Android 14 firmware."
You can roll back A15 to A14 with the google tool. Least last time I checked.
My Pixel 6 Pro never rebooted after v3.0 installation attempt. (Clean install)
Dead. No sign of life at all including inserting charge cable.
I left it overnight plugged into Pixel charger…no heat from the charger or device. Tried various cables, chargers. I think it had a stroke!!
Warning: The May 2025 update for Pixel 6 (6, 6 Pro, 6a) and Pixel 8 (8, 8 Pro, 8a) devices contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing the May 2025 update on these devices you won’t be able to flash and boot older Android 15 builds.
Thanks but the documentation states that unlocked devices are not subject to rollback.
“Rollback protection errors are IGNORED when the bootloader is UNLOCKED .”
What’s more, the examples in the doc are given with dates from 2022, not alerting us to the 05/2025 problem.
Anyway, that’s the problem. It’s bad timing on my part “Murphy’s Law”. That’ll teach me to want to change rom when mine works just fine on Android 15 with the latest security update.
Anti-Rollback was incorporated back in Android 8 so this has been a consideration for some time.
Anti-Rollback is a specific consideration with the security patch level. For Pixel phones Anti-rollback is ignored with an unlocked bootloader and only activates when the bootloader is locked. As far as I know that’s not changed. If the phone fails to boot because of anti-rollback you can simply go into fastboot and unlock the bootloader. One exception is the Xiaomi phones where anti-rollback is active regardless of bootloader state.
With the exception mentioned, only official versions of /e/os are subject to this consideration where the boot loader can be locked. Most of the /e/os supported phones are on community builds where the bootloader can not be locked. It’s mainly the phones sold at the Murena shop that get official builds.