Caution: Ensure that you flash an image with a security patch level greater than the level of the existing security patch, Failure to do so will brick your device.
Since I already installed the (as of now) latest update on my device, my security patch level is not March 5th, while the latest stable release image of /e/ OS apparently dates to the 24th of Febuary.
Being the impatient person I am, I tried to find out when to expect the next release of /e/ and came across this open issue:
I understand the problem is triggered by the final step, where the bootloader is locked again, right?
One of the devs explicitly says
You will be able to lock your bootloader after flashing an upcoming release with a newer security patch level.
It should be ok with a over the air update but relocking the bootloader afterwards might force you to set everything up again.
So guess I’ll give that I try tonight.
What are the dangers of using a phone with the bootloader unlocked for a few weeks? I assume this mostly allows anyone to connect it to their PC and have full access or am I missing something REALLY bad, as in “remote exploit bad”?
If you’re reading this and are quite certain I’m heading for disaster, a little heads up would be nice.
I just installed /e/ OS successfully without bootloop by following the instructions of the official documentation, but simply skipping the paragraph “Locking the Bootloader”. So my bootloader is still unlocked, I see a warning at boot, but it boots just fine.
PS: I assume this is just normal behaviour, but when running the fastboot commands to unlock the bootloader, the phone rebooted a significant amount of times. It took several minutes, but it always managed to finish whatever it was doing and came back working. So as usual: Patience is key!
Maybe the system was trying one of the slots which was “unbootable”. So it tried to boot that about 6 times and changed to the other (bootable) slot then.
You can check that if you want by going to Fastboot mode and typing in fastboot getvar all and searching for unbootable slots (slot-unbootable).
On unlocking the bootloader I’ve just seen my device rebooting for clearing the data partition and rebooting again a second time after that.
I’m new here, as I received my Fairphone 2 days ago and installed /e/ almost immediately.
Just to keep you informed that as of yesterday with up-to-date software, bootloader issue is still there
Anyway, glad to have a functioning /e/ OS and a great FP4
As with @Azimoth , I was able to successfully install /e/OS on my new FP4. But I did NOT skip the last section and this was my undoing. I would rather see the warning that be stuck in the locked bootloader.
I think some steps are missing from the instructions…
@Volker I see the following with your suggestion
How were you able to switch into the bootable slot?
Which active slot is shown by fastboot getvar all?
You may try fastboot --set-active=b.
but maybe this command won’t work as you seem to have relocked your bootloader.
You may just try to boot several times and the phone should automatically switch to the other slot.
Did you already try to unlock the bootloader again by fastboot flashing unlock?