An update on installing /e/OS on my new Fairphone (early Dec 2025).
Originally, I followed the Murena provided guide to replace my Fairphone Android 15 by /e/OS and everything seemed to go perfectly fine - only thing I did not quite understand was that I could not set the screenlock code. Simply just skipping that step seemed to cause no additional problems.
However, after installing FDroid, it would not allow me to install any apps (not even my favourite Binary Eye app for scanning bar codes⌠Installation would mention a problem with secure FTR that I could not make much sense off - did I not just root the phone and replace the OS?!
After trying a number of things and almost getting stuck in a bootlock (âŚ) I finally came to understand that my problem is the same as that reported for the FP5 in this topic (with this solution).
How to resolve the problem:
Follow the basic steps from the topic linked above:
I suspect that trying the official build on a Fairphone that has not been purchased from Murena directly (with /e/OS pre-installed, so you probably do not need it) will fail because of missing keys or something like that - but I have not tested this elaborately.
I donât think. I know . Did you never read the installation instructions?
Almost everything is documented. Only exception, your case you had .
Read the instructions once before you attempt it. A hint I can give you allready, check the security patch from the flashing you did with the FairphoneOS (Stock Android). Maymbe you will have to wait until 3.3 with December security patch
These builds are currently only available on the Murena smartphones
(With a line explaining that means âpurchased from the shopâ.)
Inconsistencies like these make it hard to distinguish between current and outdated instructions.
Thanks for the hint BTW. If my Fairphone OS version has patch level 05 October 2025; the instructions say Security patch: 2025-10-01, I will assume the specific day is important and waitâŚ
It only explains that the devices which are sold have a official build and only thoose. I know lot of readers think this applies to only bought on their store⌠If they did not want people to install âofficialâ builds why put it on displayâŚ?
Donât know what you mean but maybe I am already too long on this train
I find no reference to secure FTR in a quick search online.
I only ask as this has caused some concern to others and I would like to confirm if or that you are referring to FRP, Factory Reset Protection, frp. If yes, I think having FRP in the title will help to guide others with a similar problem.
In about 3 days, the official v3.3 should be out (if no major bug appears), since community is available. Official trails couple days to be stopped as mentioned major bugsâŚ
I had the same problem yesterday, with the official build, and lost some time to find how to fix that (and lost time to fix it because itâs quite long to follow all these stepsâŚ). I think the guide should mention this: sign out of your Google account before switching to /e/OS.
. Did you never read the installation instructions?
