I just installed E/os of my new FP6. I used the web installer via my mac. All looked just fine. The installer on the web said is is successfully installed. I did get to see the Murena splash screen on the phone, but now it keeps coming back in the bootloader menu. When I select start, it shows me briefly the fairphone andriod splash screen, but quickly comes back into the bootloader screen.
I did check the android security level on the phone (october 5 2025) and according to the recovery documentation, this should be the latest.
I seem to be stuck here. All help is much appreciated.
Regards, Matt
quick update: I managed to recover the original Andriod/Fairphone installationā¦
Thanks for the reply. I should just wait for an update from E/os before I can successfully apply the E/os version?
Just curious, why is this not clearly mentioned when installing?
Where can I find which version of E/os supports my FP6?
If you had zero warning then this is a horrendous oversight but might explain the bad results experienced by many contributors to hashtag eosinstaller.
If I understand correctly that the device has happily returned to the Fairphone OS you can collect the Android SPL from your device, then ensure that you only install /e/OS with an Android SPL in advance (or equal) to that. The release due next week is expected to satisfy this but please double check this yourself, and be aware if using the eos-installer is that is updated too.
A recovery is usually not very difiicult, the users also donāt know how to actually do that. Same reason they choose for the web installer.
@Manoj Please, I can imagine that a developer might need to change something in the web installer to create a warning about Rollback regarding security patches, if there is a quicker way it would great. This post is like the 3rd post I see this week with the same issue (latest version of Android is not best regarding security patches sighā¦), if it is any how possible to create sort of a landing page like there used to be with the easy-installer where users see a rollback warning or any warning at all before they start opening the link to /e/OS Installer, that would be great. Users who want to use (/e/OS Installer they donāt read the manual instructions to read about Rollback
Your message is clear: it must be OLDER. Messages are a bit conflicting, as it was also mentioned by @aibd that it could be equal.
Iāll keep an eye on the release and will try again.
Also would like to give a big shout out to the developer who made the roll-back possible. Worked like a charm! Just had to figure out how to run the .command file as a newby. But it worked.
IMHO: installing E/os should be easy and available for all kinds of users. Making it easy and approachable with the web installer should lead to more people using it.
that is true in theory, but in practic it donāt happen,
StockOS include SPL date refering to the fifth (2025-10-05) when /e/OS include date refering to the first day of the month (2025-10-01).
the 4 days diff (same month) will not brick your device, but will prevent it to boot and you will have to unlock again and reinstall the system without locking to recover a working device.
the guide is intented for users with no android flashing skill, so to avoid complications, i choose to simplify, and indicate āolderā.
As i did not lock the device, did not know I had to, or shouldnāt? I downloaded the latest version of e/os from /e/OS official FP6 download
I followed the instruction (apart from unlocking the device, as it was still unlocked) Also the OEM lock was removed previously) I ran the sh script as mentioned, and by the looks of it, successfully installed e/os. I got to see the murena splash screen, it started the setup proces, which i was able to complete (had an issue not being able to signin to my murena account, it kept coming back stating my username/password was incorrect. I noticed the email address was changed from @murena.iomure@e.emaila.io to @e.email.. Anyway, I skipped the setup of an account and got to see the e/os home screen with the apps. SUCCESS, or so I thought. I rebooted the phone and got a message that the device was still unlocked. So, in fastboot mode, i ran the commands for locking the device. After the first lock I got the message āthe phone is curruptā (sorry forgot to capture the exact messageā.
After locking the device using the second command in the install guide, the phone reboots, but does not startup any more. I briefly get to see the andriod faifphone splash screen. It seems it is again ābrickedā and stuck in the bootloader.
Will update this far to long forum post later as I will now try to return the phone back to its original fairphone android versionā¦
i am affraid you are in the worst situation,
try to unlock,
but i think you will have to return the device to Fairphone and pay 60ā¬ for unbrick itā¦
Ask for unlock by copy this command and paste it in the terminal :
./fastboot flashing unlock
Approve with volume + then power
The device proceed with a factory reset, and automatically reboots
Reboot again into bootloader
Unlock critical by copy this command and paste it in the terminal :
./fastboot flashing unlock_critical
Approve with volume + then power
The device proceeds with a factory reset, and automatically reboots
