before my answer The whole process depends on your personal situation, so when you migrate to /e/ and which Android Version was installed before you start the process! You need to check the security patch level of the Android Version from Fairphone against the one provided by /e/.
In my case, i installed the latest Android version provided by Fairphone early March and migrated the FP4 only a few hours afterwards, which was not the best idea as we know today. The /e/ version i used, had therefore an older security patch level than the latest Fairphone standard Android release for the FP4. Now e-0-23 was provided with an updated Android security patch level and therefore i was able to lock the bootloader again.
So it was like that
4.March i got my FP4 as standard Fairphone modell
6.March - installation of FP4 standard Android update => security patch level Feb 22
6.March - now I migrated to /e/, using 0-21 => security patch level is old, most likely Jan 22
=> boot loop when locking the bootloader
Late March - install e-0-22 = security ptach level still Jan 22 => still too old
21.Apr - install OTA update e-0-23, having March security patches
=> now i tried and was successful, locking the bootloader
I installed the 0-23 as normal OTA, NOT a fresh install! Just with that update nothing was deleted oir wiped!
Afterwards i booted into fastboot again and locked the bootloader. Because of that locking of the bootloader the phone got wiped.
Thanks a lot @Maximilian . This exactly explains what I needed.
It looks like I’m in the same situation as you. I’m currently using e-0.21, with the critical section still unlocked (otherwise I’m stuck in the bootloader loop). I’m about to install e-0.23 OTA. According to your post, I should be able to lock the critical section without getting stuck in the bootloader loop. Fingers crossed!
For the information of others: I also found this related conversation on the fairphone forum:
Just one more point here. I am very much sure, i did the fastboot flashing lock_critical even with the wrong security patch level. In this case, i got a WARNING only, but I could resume boot process.
Only when i did the fastboot flashing lock i was stuck in the boot loop. Not sure if there is some second aspect to the whole story.
And as @piero outlined, there might be different builds as well. However i used the stable build, provided via the install page: /e/ image ROM download
I’m also sure that fastboot flashing lock might create the corrupted device and not the command fastboot flashing lock_critical.
If you want to be sure then install the latest version, start the system and check that “OEM unlock” is enabled in developer settings. If it is then there’s imho no risk that you can brick your FP4.
Hi,
I’ve encountered the same f… issue and had a 30 minutes panic, I have to admit.
Now, I’ve been able to get out of this loop by reinstalling /e/OS not from the easy installer (it does not detect the phone anymore) but via command line. It worked perfectly and I’m back with my re-freshly installed /e/OS 1.14
sigh!
Caution: The FP4 comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information
good thing the phone is not actually bricked (a reason I thought the security patch level was not the issue ; I figured a build from late October would include a patch from earlier on, guess I was wrong)
When can I expect security patch from 2023-10-05 to be available in /e/ ?
image booted fine, after locking AND unlocking I could not get out of the loop. flashed previously tried T version, boots OK, leaving bootloader unlocked for now.