I want to install /e/OS on my Fairphone 4. As I’ve understood the Security Patch Level of the OS I’m installing should be more recent than that currently on the phone. My current SPL is March 2025, and so I should be ok if i select the most recent version of /e/OS 3.0.1 with SPL June 2025 right? (IMG-e-3.0.1-a14-20250607498722-official-FP4.zip)
But, if for some reason and heaven forbid, I need to go back to stock OS which is Google Android 13 for the FP4, will I risk not being able to re-lock the bootloader coming from /e/OS Android 14? Or is the Android version number not critical in this respect?
If Android SPL has been locked into phone in FairphoneOS or /e/OS by locking bootloader then this value in the Index cannot be rolled back.
If you are only testing /e/OS you might consider not to lock /e/OS then you can go back without worries.
I would suggest you write down or grab a screenshot of Settings > About phone > Android version > Android SPL (also Vendor SPL but not related to the locking issue) on any locked system on the phone before you make changes.
Thank you @piero and @aibd , that is very good to know.
I agree the Install /e/OS on a Fairphone FP4 - “FP4” page does say May 2025, but on the linked page /e/OS build downloads the latest is June 7’th and the second latest is 21’st March. Perhaps the instructions page should be updated or rather not mention SPL dates at all?
I did consider not locking after installing /e/OS, but my testing involves banking apps, so I expect to have to, right?
@aibd , right you are. I assumed this important information was part of the filename for each build.
Two more questions;
Will the web installer allow to lock the bootloader or is the manual approach needed for that?
What is the significance of “Vendor SPL”? Is it “Google Play system update” under Settings > About phone > Android version? (Quotation marks as it is a translation, it’s the one below Android SPL).
It depends on the banking app. Some don’t check anything. Some check for unlocked bootloader, rooting, or Android version, or any combination of those things. I would try the app and see if it complains before doing anything else.
There are a few banking apps won’t allow any non-OEM version of Android so you could run into that right off and there’s nothing you can do about it. Well at least I’ve not heard of anyone spoofing the Android version to get past that.