Bug: It not possible to lock the Fairphone 5 with the community eOS 2.7 img

Using /e/OS Setup
1

Hi, I downloaded IMG-e-2.7-u-20250110460550-community-FP5.zip.

This /e/OS v2.7 version includes the Android security patches available as of December 2024.

The security patch before flashing was of Nov 2024, so the anti-rollback “feature” mentioned on the install page should not be kicking in.

$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true

After following all the guide to flash the phone, it restarts the phone and relocking it spits out the “Your device is corrupt” bla bla bla.

It does lock however with the official build! IMG-e-2.7-t-20250111460957-official-FP5.zip. Either community build cannot be locked or could be locked and regressed.

Could an eOS team-member provide feedback? Should I create a bug report on the gitlab instance?

2

Hi, I had the same issue.
I upgraded from official to community to have Android 14.
I installed all the apps and then locked the phone.
I lost everything as I could not start the phone anymore.
I reinstalled without locking but now Netflix does not work (on unlocked device).
I am wondering if I should go back to official Android 13 or should I wait for the fix…
Do you know when aproximately the fix will be available (eg. in a month, in 6 months) or when official will be upgraded to Android 14?

3

Yes, that’s because community builds are lacking certificates which are allowing to lock the bootloader. We must wait for official build to upgrade to Android 14.

1 Like
4

It would be great to add that to the tutorial, because it doesn’t say that the community version cannot be locked.

5

You can actually install an older version and it won’t barf as long as the bootloader remains unlocked.

The instructions tell you to lock the bootloader with a back referenced warning about anti-rollback, easy to overlook.

They need to put that warning about anti-rollback maximally highlighted just prior to bootloader re-lock since that’s what actually bricks the phone. Really it should say if you’re not sure, don’t do it.

6

The instructions tell you to lock the bootloader with a back referenced warning about anti-rollback, easy to overlook.

I think you missed the part in my initial post addressing that very issue.

7

I tried with 2.7 and 2.8 official builds: Both would not let me lock the bootloader. (also: Fairphone 5 - locking bootloader - #13 by Segment)

8

I tried the same with the official build and the community version and its not working. I create an issue on Gitlab (Locking the bootloader with official and community build not possible (#8578) · Issues · e / Backlog · GitLab)

1 Like