WARNING install e OS 3 to Pixel BRICK

Hello everyone,

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.

@Manoj … would Pixel 6 (oriole) have rollback protection? Is this missing in Install /e/OS on a Google Pixel 6 - “oriole”?

Let me check with the build team and get back. Should have a response later today.

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.

BTW you can unbrick the phone, it’s not bricked.

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!!

I was coming from LineageOS/MicroG v22.2

2 Likes

This warning is seen in Factory Images for Nexus and Pixel Devices  |  Google Play services  |  Google for Developers

:warning: 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.

2 Likes

Thanks for sharing this @aibd …will have the documentation updated

1 Like

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.

So you mean to tell me Google is bricking devices now if you update them wrong? Did you try their tool to try to restore A15?

You would think it would still post to the green Android man?

Sorry to hear of your situation.

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.

1 Like

Several similar problems on the Google community forum.

Phone has no sign of life. Impossible to see it with fastboot or other. Impossible to boot into recovery or bootloader.

No further action is possible.

What I don’t understand is that my Bootloader was unlocked, so this shouldn’t have happened.

Anyway, it’s done, I just wanted to warn the community, because I’m clearly not the only one, even on E OS.

Translated with DeepL.com (free version)

CraigHB read the link aibd provided, I didn’t at first but have now. There is an issue with May 2025 a15.

Seems it may also be bricking devices with unlocked bootloaders too.

Hi, I posted a similar topic and it looks like last Android 16 (june update) has a anti-rollback too…

So no way to go back to Android 15 for future A15 /e/OS builds…