To relock or not to relock bootloader

Hello,

On my new FP6, I’ve just installed /e/os using the web installer. Everything is working fine. But the bootloader is unlocked.
I’d like to know if I can relock the bootloader without any risk.

My phone:

  • Refurbished FP6 supplied with Android (I haven’t checked the version).
  • /e/os version 3.7.3-a15-20260506618655-official-FP6
  • Warning on startup: ‘The bootloader is unlocked…’
  • OEM unlock option greyed out (locked or not?)

Having looked through the official /e/OS and Fairphone documentation, and this forum, I understand that I need to check the security patch level, and that the version of /e/OS must be the official one. Otherwise, relocking the bootloader could result in a bricked device.

I think I have the latest official /e/OS version.
But how can I check the version of the original security patch?
Can I relock the bootloader without any risk?

Thank you for your help

Regards

I don’t own the FairPhone 6 but it says it can be locked here:

Unsure if the web installer offers this feature. Good idea to do a search (once you have forum rights) on re-locking.

This is an interesting read on the IodeOS forum. They suggest that only the vendor SPL date matters, not necessarily the Android SPL date. I’m still unsure about that as many people has bricks without change in the vendor SPL AFAIK

The requirements to avoid the anti-rollback hazard are explored here (answered) Install /e/ on FP5 with newer Security Patches.

You probably read similar. It could be the subject of Report an issue if eosinstaller did not warn you to note the Android SPL of the installed version at time of unlock.

Was the phone recently updated?

If yes can you recognise for certain your build from https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone ? The Android SPL appears in each build details.

The method to ensure safe locking is covered here [HOWTO] a Safe Guide to install "IMG-e-builds" even if the /e/ web installer fails.

1 Like

Many thanks to all three of you for your prompt replies, you’ve helped me ask myself the right questions.
I should have compared the Android SPL and the /e/os SPL before installing. I came very close to bricking my device.

Sorry, I can’t remember if I was warned.

Most likely: I’ve just bought the FP6 from Fairphone and the support information regarding refurbished FP6 seems clear:

For Fairphone (Gen. 6) refurbished devices, the software is completely wiped and updated to the latest Android version available. The current Gen. 6 software version is Android 16 (e.g., FP6.QREL.16.69.0).

So Android version was :

Version: FP6.QREL.16.69.0
Release Date: 26 May 2026
Security Patch: 05 May 2026

VS my /e/os version is :

/e/os version 3.7.3-a15-20260506618655-official-FP6
release: 2026-05-06
This /e/OS 3.7.3 version includes all Android security patches available as of 1 May 2026.

So I can’t relock the bootloader. Is that right?

I could try to relock it after an update with a security patch date later than 5 May 2026, even though A15 AOSP version is older than A16. Is that right too?

Is not significant / is ignored.

From
Fairphone Version: FP6.QREL.16.69.0
Security Patch: 05 May 2026
To

This /e/OS 3.7.3 version includes all Android security patches available as of 1 May 2026.

Does look like a Rollback, so I will say don’t.

However if you can find it written that /e/OS devs worked together with Fairphone on FP6 to accommodate this, then you might consider to proceed. Edited Marked deleted as I have not found the quote in order to link it and would not do this myself without being 100% certain of the source.

1 Like

You should be able to relock the bootloader. A security patch dated to the 5th of a month effectively only contains the security patches until the 1st of that month.

In the release notes, they claim to have the Security Patch date 2026-05-05:

https://support.fairphone.com/hc/en-us/articles/24463713641234-The-Fairphone-Gen-6-Release-Notes

but the SPD (from the link therein) is in fact 2026-05-01

/e/-OS 3.7.3 itself claims a SPD 2026-05-05 too, despite, as you’ve already found out, its also just 2026-05-01:

https://doc.e.foundation/devices/FP6/install

2 Likes

@aibd @Philip456, Thanks for your two posts showing that it should work.

But

So neither will I. I’ll wait for the next update.

It can be difficult to express complexity / uncertainty on the forum, others for sure will be better informed than me. For you own education you might read the bulletin carefully and see the way that the updates are two (now more fully separated) parts of a cycle as said by @Philip456.

2 Likes

Sure, hard to understand too, especially when using a translation tool. Thanks to your advice to read the link carefully, I changed my mind.

Late thanks! The vulnerability fixed by the update was a significant one.

With the same SP date, I successfully relocked the bootloader. Everything is working.

It’s great to have such a helpful community.

3 Likes

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