Where does it fail ?
Hello,
I’m trying to install eos on my new FP6 but I’m very new at all that stuff (all I ever did is install linux on an old pc)
Can I install eos when it’s the 4.0 version (security patches available as of june 1st 2026) if my FP is on the Android 16 version with security update from the 5th of june?
Yes, it’s safe. As long as you don’t lock the bootloader yet.
When eos has an update with a security date past June 5th, you can lock the bootloader.
Thank you for your answer!
Since I read that locking the bootloader would delete data from the phone, I feel like it would be easier to wait for the security update to try installing anything right?
Yes, you are right. Good idea.
I should have mentioned the data loss by locking the bootloader.
It doesn’t recognize adb shell.
Did you enabled “adb” in recovery ?
Or better, enabled “USB debugging” in android → settings → system → developper options ?
Yes, the /e/ builds include needed firmware parts relative to the targeted android version
e-4.1-a15 is expected for the end of July…
I enabled usb debugging and restarted the phone to recovery mode.
No I didn’t see this one.
The phone was in recovery mode.
Should it be e/OS ?
Hi! Thank you very much for this comprehensive guide and for your replies.
My FP6 was running the latest Android 16 version, with the security update from 05/07/2026. I understand that I definitely should not relock the bootloader, so that’s clear.
I therefore tried using the OS Installer directly, as it seemed simpler. When I reached the final step, the OS Installer congratulated me, but the phone remained stuck in the bootloader. Selecting Start does not launch Murena; instead, it just brings me back to the bootloader.
It seems that it installed the A15 version (which would not be surprising, then?), as the bootloader displays:
Bootloader version – FP6.QREL.15.176.0
I don’t know if I’m missing a step or if this has already happened to someone else. The phone is still unlocked, fortunately.
After looking around a bit on their forum, but not being completely sure what I’m doing, it seems that I should try the manual installation instead (still without touching the bootloader locking function), but I would like to get confirmation before proceeding.
Hello, thanks to you I successively updated my FP3+ 
.
I had some difficulties in unlocking the bootloader as the ./fastboot commands only gave back a < waiting for any device >. The solution was to use <sudo ./fastboot flashing unlock>.
Merci beaucoup pour le guide!
I did it, I installed e/OS on my fairphone 6+ and it works very well. All apps are working well; banking apps and governmental apps have no issues with the degoogled system, just had to lock the bootloader again. Thanks to the ease of the installation procedure and the perfect guide and all the good comments in this community forum. Big thank you to all involved developers, the community and everybody else.
Keep up the great work!
I’m a bit lost with the terminology for the security patches:
- The last FP3+ release notes indicate a Security patch level (May 2026)
- My freshly installed e/OS 4.2-a15 indicates Android security update (August 2026) and Vendor security patch level (April 2026)
Which of the 2 previous terms should I take into account to determine the e/OS security date? Is it August or April 
?
Is it safe to lock the bootloader? Or should I wait for the next upgrade?
this one is relevant
The SPL is only relevant on devices with anti-rollback protection, because it can brick your device.
This guide helped to fix my problem 'adb devices no permissions (user in plugdev group; udev rules missing) and add my user in the plugdev group.