I’m Kai, a user from Taiwan, currently on FP4, for 2.5 years or so. As I recently learned some stuff about OS and related topics, I’ve been thinking about installing LineageOS. Plus I really hate that the Google search bar blocking the top row of the launcher after updated Android 13.
The LineageOS and Fairphone websites give good manuals on how to unlock bootloader and flash, but there are some details I wanted to know before I start, you know, just to be safe that everything goes well and is reversible. I couldn’t find information elsewhere. So I really need some experiences on the following questions.
What do I do if stuck in a bootloop? (It’s not Samsung that I’ve got Odin.)
How do I return to Stock ROM on a running GSI?
Do I get to relock bootloader if I downgrade to Android 12 or switch back to Stock from a GSI that has higher android version? I heard about the roll-back protection whilst flashing an OS with older security patch.
Simple descriptions on steps and solutions can be understood. Any advice is appreciated.
Since LineageOS doesn’t support bootloader relocking you generally shouldn’t end up in an unrecoverable situation, unless you lock the bootloader of course, don’t (at least for Lineage)
Not sure, never used GSIs, but if you follow the regular Lineage installation instructions you won’t end up with a GSI just a regular installation. Getting back to stock then just involves flashing the factory images. If you want to lock the bootloader again you have to check that the factory images are on the same security patch level or higher than the LOS version you had installed.
GSIs are mostly meant as a development tool, if you don’t have a specific reason to use them you’ll generally want to avoid them if possible.
If your device is currently running A13, downgrading to A12 and locking the bootloader will brick it. If the LineageOS version you had installed had a higher SPL than the factory images you installed afterwards, and you lock the bootloader, that will brick it.
These cases are recoverable from if you make sure to always check fastboot flashing get_unlock_ability before locking the bootloader.
As long as you don’t lock the bootloader you can install whatever you want (within reason, ROMs set the security patch level, nothing is stopping me from creating one that has a SPL somewhere in 2030, which would make it impossible for you to lock the bootloader with factory images until then, fun…).
If locking the bootloader is something you need, you might want to go with something like /e/OS or iodéOS, which actually support that.
Thank you. I’ve done my studies, and found out that fastboot mode doesn’t disappear after flashing a custom ROM. So I guess it’s reversible as long as bootloader remains unlocked, even if it goes bootloop (also unlikely). Also, I‘ve read the posts about iodéOS and /e/OS. So maybe I’ll go with iodéOS. It’s a fork and the UI looks close enough.
Another reason I want to relock bootloader is that I may need to have MDM installed on it in the foreseeable future (policy for my work). Not sure if an unlocked bootloader matter and don’t feel like taking a risk. I’ll guess it doen’t as long as I don’t really install Magisk? It feels somehow weird since it seems not hard to gain root access and “be superior” to MDM and maybe silence it or something.
MDM will likely require a locked bootloader, depending on the apps used it might also require proper Google Play Services (i.e. staying on stock). Locking the bootloader wipes the phone, if you know you might need it lock it from the start, unless you enjoy setting up the phone.
While gaining root might not be hard, hiding root in a way that circumvents root-detection in apps can be. You also won’t be able to lock the bootloader in that case (unless you build it yourself / find a ROM with root included), which quite a few apps check for.
If you need it for work I personally wouldn’t root it (I stopped rooting my devices in general).
If you go with iodéOS keep in mind that the security patch level has to match if you want to relock the bootloader. Currently you should be in the clear since the factory images and the latest iodé 6.7 are on the same version, that might not always be the case so look out for that (but since Fairphone doesn’t release new versions anyway that’s rarely an issue these days )
You are right. I don’t know how the apps I use (and MDM) interact with MicroG. I should test first on some other device. It’s okay though if I can’t have MDM on iodéOS. I have other spare phones for this purpose. Thank you for the detailed information.
If your main concern is the UI of the launcher, then just try another launcher. I can recommend Nova Launcher, I’ve used it for years. Much more flexibility, and easy to organise when you have a lot of apps.
That is not the main concern, but may solve some current inconvenience. I figured that risking a phone on MDM is not a good idea so maybe I’ll switch to iodéOS later than the “MDM phase“. I used nova launcher on my Tab (with root). It’s nice but details alter with different versions and sometimes I just can’t find the exact function I’m looking for. I haven’t tried it on FP4 yet. Will give it a shot.
)