OEM-Entsperrung lässt sich nicht aktivieren!

[piero]

from @ steadfasterX
well it is actually not a fix but a workaround. if the user has rooted the device it can be “fixed” by the user himself but afaik AXP.OS (Pro) is the only custom OS allowing to lock a rooted device.
the custom OS dev can implement the above workaround like this . you can also find 2 FP threads about that topic leading to the magisk workaround

i don’t know what to do with that, other than it should be integrate into /e/ build process :

build/Scripts/Common/OEM_unlock.sh at 5e7fbe5bfdcefd65e4d4f7d9c0ec1b1574217178

also a related workaround : Trapped in fastboot mode with locked bootloader and corrupted custom ROM - #101 by hirnsushi - Fairphone 4 - Fairphone Community Forum

@hirnsushi

I managed to set get_unlock_ability back to 1 again (with an unlocked bootloader, don’t get your hopes up) by using Magisks resetprop…

adb shell su -c 'resetprop ro.boot.flash.locked 1'

…and switching the OEM toggle in developer settings back to on.
Magisk for the rescue again

We should advise people to check fastboot flashing get_unlock_ability before locking the bootloader.
It’s a bit of a hassle having to set up Magisk just to reset that flag, but beats bricking the phone. Maybe there’s another way to fix this

@piero

fastboot flashing get_unlock_ability

if the return is 1

→ you will be able to relock

if the return is 0

→ locking should be feasible, BUT you will not be able to unlock again in the future…
→ it is advised to

• reboot and re-enable Developer Options, USB debugging and allow OEM unlocking . (to get =1),
  or
• reinstall FairphoneOS and re-enable Developer Options, USB debugging and allow OEM unlocking . (to get =1), and then reinstall /e/OS.