Pixel 4 XL totally stuck on eOS 2.1-s-20240603406609-stable-coral

/e/OS Devices Google
1

**Hello all,

Around June 2024, I installed eOS 2.0 stable on my trusty Pixel 4 XL and then got later the 2.1 version thru an OTA update. During the eOS 2.0 install, I also got the associated eOS Recovery.

Since that time, I forgot about that device and recently I tried to update it to the latest eOS but I have seen those issues:

  1. the bootloader is strangely locked. I NEVER locked it myself as it is my rule of thumb to leave a bootler unlocked after unlocking it. But the fact is in Developer Options the “OEM unlock” entry is grayed and on the “OFF” position. This is also confirmed by locking at the informations on “fasboot” mode.

This is preventing me to flash anything except a “stable” eOS version. I tried to install the recent “community” updated thru “adb sideload” but each time the update it rejected. IIRC I could see a “signature verification” issue due to the different build signature between “stable” and “community”.

  1. During one of the “adb sideload” I tried, I could even see that the SPL was increased to some 2024 value compared to the 2022 value that is present in the latest official Google build.

That is also preventing me to “return to the official” Google build. Here is some message during the “adb sideload”:

E: Current SPL: 2024-05-05 Target SPL: 2024-04-05 this is considered a downgrade

So all in all, after many attempts I am stuck and don’t see for now any path to do the eOS update or even install any other firmware** … which is a real issue.

I am also wondering if I could get an old “stable” eOS build, like 2.2 or 2.3 to try tin install it. I tried to find one but without success. It seems that the “Coral” builds here on only “community” ones:

I would appreciate any suggestion.

Thank you in advance,

Fabrice

2

all /e/OS releases older than 2.4 were lost during the 2024 october server-reset

please share outputs for :

fastboot oem device-info

fastboot flashing get_unlock_ability

.

look like there is no anti-roll back feature on this device

from Factory Images for Nexus and Pixel Devices  |  Google Play services  |  Google for Developers

“coral” pour le Pixel 4 XL

Version Flash Download SHA-256 Checksum
13.0.0 (TP1A.221005.002.B2, fĂŠvrier 2023) Flash Lien db99b1f89e2fea16cbf48c876809c78d6dc46279e7311ab52d00d8125ef3a5d9

.

you should use Android Flash Tool using

3

Hello Piero,

Thank you for your response. I am surprised to hear that releases older than 2.4 were lost. Were no archives or backups preserved?

Here are the requested information:

% fastboot oem device-info

FAILED (remote: ‘Invalid oem command device-info’)

fastboot: error: Command failed

and:

% fastboot flashing get_unlock_ability

(bootloader) get_unlock_ability: 0

OKAY [  0.286s]

Finished. Total time: 0.286s

Regarding the statement that there is no anti-rollback feature on this device, Recovery clearly reports:

Current SPL: 2024-05-05
Target SPL: 2024-04-05
This is considered a downgrade
Denying OTA because it’s SPL downgrade

This indicates that rollback protection is active and enforced at the bootloader level.

Because of the raised SPL (2024-05-05), I can no longer flash the last official Google factory images (2022), as they are rejected as downgrade attempts.

Additionally:
• Android Flash Tool using Chrome cannot proceed because the bootloader is locked.
• The /e/OS web installer requires Android 13+, but I cannot boot Android 13+ due to signing chain mismatch and rollback constraints.

The core issue now is:

The Developer Option “OEM unlocking” is disabled, and:

fastboot flashing get_unlock_ability
→ 0

This means the bootloader is not allowing unlock.

From a technical perspective, I see only a few possible paths:

  1. Is there an official stable build for coral with SPL ≥ 2024-05-05 that is signed with the same key lineage and can boot on a locked device?
  2. Is there any supported method to restore unlock_ability = 1 on a Pixel 4 XL that was previously OEM-unlockable but now reports get_unlock_ability = 0 after installing a stable /e/OS build?
  3. If official archives are unavailable, does anyone have a backup of a stable coral build with SPL ≥ 2024-05-05 that matches the current signing lineage and can boot on a locked device?

I would appreciate clarification on:
• The rationale behind raising the SPL beyond Google’s final official release.
• Whether there is any supported recovery path when rollback index exceeds Google’s final stock image.

Thank you for your help.

Fabrice

1 Like
4

Can I have some form of response ?? I put some time to give all the requested information and details.

Fabrice

5

You do appear to be stuck; Google devices are usually easy to free up using Google resources.

I think you know that within the locked phone downgrades by adb are expected impossible and will report an error.

The rollback would have to happen with a Fastboot ROM as available from the Factory images page. If the device really will not unlock one would need to check with Google support whether there is available a Firehose or EDL solution in order to free up the phone for a Custom ROM.

This is a blocker, have you tried to unlock connected to Wi-Fi? Perhaps Google support for the device contains other ideas ??

Edit add link [How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled - | XDA Forums. This seems to include the idea that (on some Pixel) a signed Custom ROM will cause OEM unlock to be greyed out.