Can't lock the bootloader on FP5 with /e/OS version 3.0.4

Using /e/OS Setup
, ,
1

Hi All,

Tried out /e/OS and I’m loving it so far (the battery life gains are a pleasant surprise). There are definitely some quirks and limitations, but I can live with most of them. I’d like to move to this as my daily driver OS but I have a serious issue.

I installed /e/ on my Fairphone 5 a couple of weeks ago using the official command line guide and it worked well, however I couldn’t re-lock my bootloader due to the security patch version being one version older. No biggie, the next one would be out soon.

And here it is! /e/OS “3.0.4-a14-20250708507308-official-FP5” has become available and I installed it right away. It has the same June 2025 patch level as my previous FPOS installation " FP5.UT2Q.B.125" so I figured I’d be able to lock the bootloader no problemo.

Unfortunately, problemo is what I have.

After updating to the latest version of /e/OS, I attempted to lock the bootloader. “lock_critical” went fine but the final “lock” command resulted in the infamous “Your device is corrupt. It cannot be trusted” screen. Bugger.

I reinstalled the new version of /e/OS again and checked the security update level in settings to confirm, “1 June 2025”. There’s a separate “Vendor security patch level” that shows “5 May 2025” but I’ve read that it shouldn’t mean anything for re-locking the bootloader.

So why can’t I lock my bootloader? This is becoming a fairly urgent issue as without a locked bootloader I can’t access my banking. Additionally problematic since Starling conveniently offers no alternative for accessing my account without a phone on a locked bootloader.

Thanks in advance!

1 Like
2

Can you confirm for certain the exact Android SPL of this build?

If you performed the preinstall unlock on this build then that date is the one locked into your phone’s anti-rollback index.

You are correct that Vendor SPL is not part of the “can I relock” comparison.

This thread Installed 3.0.2 official and tried to lock bootloader explores an issue affecting users who come back to relocking the bootloader after a gap (like your situation).

1 Like
3

According to Fairphone’s website their latest version (the one I was originally on) has the same June 2025 Android SPL.

I’ll take a look at that thread. Thanks for your swift reply :slight_smile:

Edit: I’d like to clarify I’ve only had the unlocked bootloader for a couple of weeks. Nowhere near as long as the person in the post. Not sure if that’s relevant.

4

Well this is unfortunate.

I didn’t realise there was more than one security patch per month (based on both Fairphone and /e/'s somewhat unhelpful wording). It looks like FP5.UT2Q.B.125 actually uses ASPL 2025-06-05 - 4 days newer than the patch included in /e/OS 3.0.4.

I don’t think I can wait any longer for the next /e/OS update so I’m going to have to reinstall FPOS for the time being. I’ll keep an ear out for 3.0.5 (or whatever comes next) so that I can make the switch proper without sacrificing the ability to access my bank account :rofl:

5

Thanks for your information.
Same situation here, but my only banking app works even fine with a unlocked bootloader.

Question: If I try to relock the bootloader with the next eOS (>3.0.4) security patch release, will there be another wipe (like during unlocking)?

6

[HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc

7

I mean the next update after the current available version
3.0.4-a14-20250708507308-official-FP5

8

It is Android documented that every Lock and Unlock Wipes all data.

For explanation of the Fairphone anti-rollback there is (answered) Install /e/ on FP5 with newer Security Patches

Basic rule

Only Android SPL is significant.

Record the shown Android SPL in the FairphoneOS at time of unlocking.

One can now only lock another build if the date is equal or in advance of this date.

1 Like
9

Thanks!
OK, I will double check, if I really need a closed bootloader. Currently all important apps incl. banking work without complaints on murena 3.0.4

10

This topic was automatically closed after 90 days. New replies are no longer allowed.