I used the /e/ OS web installer to install the OS on my Fairphone 6. The FP6 used the Android version FP6.QREL.16.82.0 before that. At the end, the web installer didn’t ask if I wanted to relock my FP6. But I read that it is possible on official /e/ OS builds. I just have to make sure the /e/ OS version is newer than the installed Android security update. I’m now a little confused, which date regarding the /e/ OS version is now the important one.
The Android security update is clear. It’s June 1, 2026
The /e/ OS version itself is 4.0-a15-20260610morenumbers-offical-FP6. That probably means June 10, 2026?
Then there is a Vendor security patch level: December 5, 2025
And a Build date: June 10, 2026
So, what’s the important date here, and how much newer than the Android security update does it have to be? Let’s say my /e/ OS version has to be newer to relock: Is installing normal updates enough to fix this issue when new versions are released, or do I have to reinstall the OS completely for that?
In case I can relock my bootloader (sooner or later), what is the best backup possibility? Seedvault backup? I already read it doesn’t include, e.g., Signal chats (but I can backup those separately). What about my contacts and calendars? Do I also have to backup them separately? And app settings? Is the Murena cloud good for that?
And, last but not least: Is it worth the trouble? After reading different threads, it sounds like there is not a real risk in an open bootloader. If I don’t plug my device in random machines and don’t visit countries that take my phone and give it back to me with a keylogger, there is not really a way someone could profit from this “destroyed” wall? If someone would steal my phone and would be interested in my data, he/she could, in theory, copy my encrypted data, but not decrypt it, so if he/she doesn’t get my PIN, it’s useless for them?
Thanks for tips in advance, and have a nice weekend!
Because FP is one of the manufacturers that supports relocking with a custom ROM and partnered with /e/ OS in some form, my question is now, is there a situation where relocking the bootloader will ever be problematic for an /e/ OS update?
I used iodéOS on my FP4, but at some point, I couldn’t update it to a newer version because the bootloader was locked (that was some form of unplanned accident on iodé and/or Fairphones side). If there is a real chance that this could happen again, I will not relock my bootloader. The risk of getting hacked is not worth the risk of this kind of problem.
Any form of experience you made regarding that would be really helpful.
Okay, that definitely made some questions clear. The security patch level on the Fairphone side for the newest Android 16 version of the FP6 is 05. June 2026. The Stock Android on my FP6 was on the newest version on 10. July 2026. So, my SPL is most probably the 05. June 2026. But to be safe, I shouldn’t attempt relocking /e/ OS before any version for the Fairphone 6 releases that includes all SPLs until 10. July 2026. Which I can check on this page: Releases · e / os / 🚀 Releases · GitLab
Once a newer version of /e/ OS releases, I can just update directly on my phone via the Update button in the Settings. And after making sure I have all my data backed up I then can relock my phone.