I recently decided to switch to e os on my Fairphone 5, Now a few weeks later I start thinking that this was a mistake for several reasons. I did search the help ad user queries but I could not get a consistent approach to solve my issues.
Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services
Welcome ā¦and sorry to hear.
But if you are here to get help you might want to be way more specific about the issues in question (?)
Yes. But every time I try to do this I get an error that as a new user I can only use two links in my post. Not sure what this means. If it refers to links to e os websites with documentation the I think these are needed as I want o be transparent.
Hereās a try without links, sorry:
outdated security patch: After some research I decided to use the e os installer available at Info about Fairphone FP5 - FP5. Given the warnings in other instructions on ensuring that the security patch versions match (ā¦linkā¦), I searched in the documentation of the e os installer to find out which security patch it comes with. As I did not find anything I continued with the installer assuming that it being an official, approve method contains the latest security patch or at least gives a warning if it is not the case. While the installation as such worked well, I now have not matching security patches. The implications of this I donāt really know but Iām reminded of potential problems every time I restart the phone when a warning appears that āāThe bootloader is unlocked and software integrity cannot be guaranteedā¦.ā
In 8 years of using the FP2 with LSPOSED and Magisk I got used to use apps that require root. Thus I decided to install Magisk on e os on my FP5. I followed the instructions at ā¦linkā¦ These are very clear but I failed for several reasons:
As I could not extract the boot.img from the FP5, I found it on the e os website, ā¦link or so I thougth. There it is only available for Android 14 while the latest official e os 3.0.1. is based on Android 13.
So tested whether I could install TWRP and get Magisk installed this way. There I followed the documentation provided by e os Install TWRP. This failed since either Fastboot mode is not working correctly with e os on the FP5. or because there is no recovery partition since fastboot flash recovery twrp-3.7.1_12-0-FP5.img fails with an error that that there is no recovery partition. While adb devices and fastboot devices work, fastboot getvar current-slot returns ābā. However, flash b twrp-3.7.1_12-0-FP5.img also fails.
Iām aware that I may be doing things wrong, even though I tried to follow instructions that are presented in the, what I believeā, official e os documentation. And any help or recommendation, such as to go back to the stock OS and restart from scratch or use installer, community or official build would be highly appreciated.
So ā¦ do you wish to have your FP5 bootlloader locked with /e/OS?
Did you keep evidence you can be certain of the Android SPL when you unlocked your phone immediately prior to /e/OS install?
Perhaps you could tell us your current build_version_string.
You can point us to what you are talking about by changing a hyperlink into preformatted text by means of backticks
```backtiks```
EG
https://doc.e.foundation/devices/FP5/install
This thread may help (??) (answered) Install /e/ on FP5 with newer Security Patches
ThatĀ“s normal behaviour as the forum is configured that way to avoid spam etc, But no worries, You get closer to the next ātrust-levelā with every postā¦ just keep posting and asking step by step.
Sorry I cannot help with your issues, theyĀ“re beyond my expertiseā¦ good luck!
I agree /e/ should publish the boot.img separately too for magiskers, but then, it isnāt a /e/ target group. You can either use lineages boot.img that has parity in android major or extract the boot.img from the /e/ ota payload.
Hi and thanks for the hints:
Iām not entirely sure of the consequences of an unlocked bootloader but given the warning that appears after each start up, Iām certainly concerned.
The build version is 3.0.1-t-20250606498724-official-FP5.
When I installed e os, the Android security patch was from 5 February 2025.
And yes, I found and read the thread (answered) Install /e/ on FP5 with newer Security Patches. Unfortunately, I could not find a clear advise there either.
And the links:
ā¦ the security patch versions match (https://doc.e.foundation/devices/FP5/install)
ā¦ I followed the instructions at https://topjohnwu.github.io/Magisk/install.html
ā¦boot.img from the FP5, I found it on the e os website, https://images.ecloud.global/stable/FP5/
I think this covers the ground quite well A discussion about bootloader locking/unlockingā¦ AKA I want to relock my bootloader, should I?
Is it a case of reading it more than once? You compare two dates ā¦ do they satisfy the requirements / rules ?
ā¦ Edit ā¦ or by āAdviceā did you mean do I or donāt I ?
Thanks. The link on A discussion about bootloader locking/unlockingā¦ AKA I want to relock my bootloader, should I? was extremely helpful to understand the issue and my concerns better. But regarding the discussion on security patches, the initial clarifications in this thread were clear ((answered) Install /e/ on FP5 with newer Security Patches - #2 by aibd) but then I got confused ((answered) Install /e/ on FP5 with newer Security Patches - #11 by piero) and thought Iād wait for the next version which was 3.0.1 that I installed but the security patches were still not matching. Finally, found myself on the same level as this post https://community.e.foundation/t/answered-install-e-on-fp5-with-newer-security-patches/66829/12. Confusing is further the issue that as far as I understand the web installer uses the official version that is based on Android 13 (thatās how I understand the information on my FP5 anyway e_FP5-user 13 TQ3A.230901.001 eng.root.20250606.154448) but at https://images.ecloud.global/stable/FP5/ it says Android 14.
So with a little help from e/OS + Android OS version names and numbers? - #3 by aibd we see your Android version is AOSP 13 (T) and of the Different Build Types you have official.
Then you look at /e/OS stable FP5 download ā¦ and see that A 13 and A14 official is available as
ā¦ but web installer chose A 13 (T) for you ā¦ I donāt know why that is.
If you are in any doubt about the Android SPL existing on your phone now it is seen
Settings > About phone > Android version > Android security update.
ā¦ I am not with you ā¦ matching what / why ??
They do not have to match. The security patch level of /e/ simply has to be more recent or at least match. /e/ 3.0.1-t has an SPL of May 2025. This is more recent than February 2025.
That means, you can lock your bootloader. Bear in mind that locking the bootloader wipes all user data from the device.
The web installer seems to go after the Version of /e/ that is available as OTA update/upgrade for existing devices. While there is an Android 14 Version of the official branch available, it is not yet tested and rolled out via OTA.
You can install /e/ 3.0.1-a14 manually if you wish vor wait for the OTA which will arrive eventually. You will lose all data on the device by flashing manually.
Hi and thanks for the link. Interestingly, I do not get options for Android 13.
So regarding my second problem installing Magisk for which I need a matching .img and solve the issue of the not detected recovery partition I need to wait for the next update until I can use the available zip.
Why the web installer chose Android13, I canāt tell. I never had an option to select. The phone however came with Android14. The comment by Profile - sophimae - /e/OS community suggest to me to wait for the next OTA update to avoid to setup from scratch again.
You have to click on Android 13 to open the full selection shown in my image
