Thanks for pointing that out @voorstad will have it added.
1 Like
According to the device page (Info about Fairphone FP5 - FP5) the 6/128 GB model is not supported (not listed). Based on the option to buy this variant and multiple installation reports the device page should be updated.
Thanks
1 Like
Hello,
I tried to install Murena /e/OS on a Fairphone 5 with the web installer though it failed for two reasons:
The web installer as well as the command line instructions do not mention that specific USB drivers must be installed on the PC to allow communication (especially in fastboot mode) between PC and telephone. Those drivers are offered automatically by windows as optional updates after connecting the phone to the PC for the first time. Lineage OS documentation does mention that for many telephones. This information is direly missing from the first steps of web installer.
Secondly, the web installer does not provide phone specific instructions to unable OEM unlock. This defeats the purpose of the “easy” web installer. We must include either a list of instructions for each different device in the first steps or start the phone detection before those generic steps and include the correct phone specific instructions for OEM unlock.
In the case of fairphone, we need a link to the official support page providing the unlock code.
The install guide assumes that the install is done in one go from start to locking the bootloader at the end, but for various reasons users sometimes think of locking the bootloader later.
Which leads to a documentation issue …
Could the respective warning from the unlocking section be repeated for the locking section? It’s missing there in the scenario when locking is considered for later.
2 Likes
I have a problem; I successfully installed murena on F¨P5, but I reboorted before locking the device, so now when I plug the phone and try adb get-state I get error: no devices/emulators found
How to have my device detected Locking the Bootloader
Once you have completed the above steps and before rebooting you can lock your Bootloader.
- Lock critical partition with the following command
fastboot flashing lock_criticalto runfastboot flashing lock…
Thanks!
Adb commands only works when device is in normal mode or in recovery mode, not in fastboot mode
Thank you so I simply had to press the volume- / start button to be in recovery mode, and it went well 
Yes so I had the same problem.
I followed the installer… but it didn’t relock the bootloader.
Every time rebooting, up came the warning that bootloader was unlocked and not to put sensitive data on your phone! Ha!!
So … you have to essentially redo the install because bootloader can only be locked before reboot.
For me I was lucky - I was in Fastboot mode and tried to reboot and the installer said the OS was corrupt [I thought oh b****s I have bricked my phone at this point] but NO, it gave me an option to reinstall e/OS.
When it finished, DO NOT SET UP the phone.
Go to you CMD Prompt (Win 10)
Ensure you have the latest adb tools installed - I didn’t and therefore the “fastboot flashing” command failed.
So you have to go into CMD (Win 10) and navigate to the folder you installed the Platform Tools.
Ensure your phone can be found. (“fastboot devices”)
Then I followed the “locking the bootloader” instructions:
Hope this helps.
The /e/OS installation instructions for Fairphone 5 have inconsistencies and abstractions that are enough to make me nervous about performing this install.
For example, it says
Boot into bootloader/fastboot mode.
Power OFF the device. Hold Power + Volume Down button combo simultaneously.
This is an intolerant procedure. The buttons have to be held down for a long time, I would guess about 10 seconds, but this isn’t mentioned. And if the buttons aren’t released at just the right moment – too early, too late, it doesn’t matter – the phone will boot normally. I had to try five times before I could get it to enter fastboot mode.
In a previous step, the instructions suggest
Reboot on fastboot by running the command in the PC console adb reboot bootloader
Does that not achieve the same result? The phone needs to be connected to the computer, so why not tell users to launch the bootloader from the command line and so have consistent instructions?
The instructions should be explicit and detailed. What does the bootloader screen look like? How do I know that I’ve done it correctly?
1 Like
The Security Patch Level noted here is wrong for the official build: Install /e/OS on a Fairphone FP5 - “FP5”
The SPL for the official build (3.0.2) is actually May 2025, not June 2025. This is crucial due to Anti-Rollback protection on FP5!
See screenshot for reference.
In the meantime 3.0.4-official was published at https://images.ecloud.global/official/FP5/ and has the June security patch level, so the install guide right now is correct.
1 Like
When updating /e/OS via Andoid settings, it would be nice to have a link to the update page. Just so that a user knows if there is something to consider before updating.
Also while I’m here, I’ve asked myself if I can update directly from v3.0.1 to 3.0.4 or if I have to do an update of 3.0.2 first. It would be nice to mention that in the doc’s.
This is probably not specific to FP5, but still it’s documentation.
https://doc.e.foundation/how-to-update-e
