Hello @alkahan, Welcome to the /e/ users forum.
Yes, you are in good situation to relock.
(downgrade sock OS was unnecessary but not bad)
1 Like
I try to relock, but get_unlock_ability is 0
# ./bin-linux-x86/fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
# ./bin-linux-x86/fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.001s]
Finished. Total time: 0.001
to be able to get get_unlock_ability=1 I need to reinstall Fairphone ROM. I reinstall It but get_unlock_ability is still 0 and the option in Android is grey out.
and from the command line:
./bin-linux-x86/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I am stuck.
Found the solution with the help of Can't flash stock FP4 ROM - #12 by hirnsushi - Fairphone 4 - Fairphone Community Forum
get_unlock_ability is reseted to 0 when Android boot. After flashing with Fairphone image, get_unlock_ability is set to 1.
I follow these steps :
flash with Fairphone ROM. keep volume - pressed to not boot to Android, but boot in boot menu.
flash with the last eOS ROM. keep volume - pressed to not boot to Android, but boot in boot menu.
check actual state:
./bin-linux-x86/fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
# ./bin-linux-x86/fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.001s]
Finished. Total time: 0.001s
lock critical partitions
# ./bin-linux-x86/fastboot flashing lock_critical
OKAY [ 0.030s]
Finished. Total time: 0.030s
Approve with volume + then power
keep volume - pressed to boot menu. check current state :
# ./bin-linux-x86/fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.002s]
Finished. Total time: 0.002s
./bin-linux-x86/fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY \[ 0.001s\]
Finished. Total time: 0.001s
lock bootloader
# ./bin-linux-x86/fastboot flashing lock
OKAY \[ 0.030s\]
Finished. Total time: 0.030s
2 Likes
Hello everyone,
I just got my FP6 today! After doing the most basic functionality checks and the available OTA (mistake) I speedran to the online Installer. → It ended up bootlooping…
While that was going I was researching the how to lock the bootloader and came across this restriction with the patch levels. I didn’t care to check even which (official Fairphone) Android Version the the phone updated to. Not to mention which patch level that was.
Now I have to assume it was FP6.QREL.16.69.0 with patch level 2026-05-05.
Thankfully flashing e/os through fastboot went perfect so I’m on v3.7.3-a15 with patch level 2026-05-01. I guess I’ll have to wait for the next release with a hopefully later patch level. 
Locking the bootloader would wipe the data off the phone again, right? So I won’t be doing much with my shiny new FP6 until the next release comes around… maybe some tests
Should have done my research…
2 Likes
/e/OS v4.0 release date : 2026-06-11 with expected A.S.U. 2026-06-01
2 Likes
Yes.
hi i was redirected to here after making a post looking for help.
Info from my post: I got a fairphone 6 without the e/os, wanted to switch to that and used the webinstaller on windows 11 after updating my phone. That worked pretty ok until after the very last step and the phone is now stuck in “FastBoot Mode” regardless of which option i select. holding down the power button doesn’t shut it down either just repeatedly tries to boot and then gets back to fastboot.
The device state is listed as unlocked and i didn’t see any pop ups or messages. I did get a “muerna” screen when it first started to boot back up tho. My phone doesn’t seem show up in the device manager under “other devices”. i installed all the optional driver thingies that looked phone related already.
After looking in the forum for a bit i saw a post with a similar problem to mine and the person was advised to download platformtools and open the terminal in there to run “./fastboot oem device-info” and “./fastboot flashing get_unlock_ability“. “./fastboot oem device-info” comes back as:
$ ./fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.002s]
Finished. Total time: 0.002s
but “./fastboot flashing get_unlock_ability” comes back as:
$ ./fastboot flashing get_unlocked_ability
fastboot: usage: unknown ‘flashing’ command get_unlocked_ability
there’s no 1 or 0. Do i go ahead and try the things the guides lists in the return = 0 option or do i have to do something else? I really don’t wanna accidentally make it worse
i’m really bad at tech so please use as easy terminology and steps as you can, i’m rly sorry for the inconvenience ;-;
Please provide the output of fastboot --version.
You are successfully executing commands on a command line/ terminal, so you can safely consider it not to be so bad and on a good trajectory upwards 
.
2 Likes