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 
.
3 Likes
Bonjour Piero
Je galère au tout début de l’installation. J’ai bien paramétré mon téléphone pour la détection mais je pense que le fait de le connecter en USB à mon iMac via un hub (il n’y a plus que deux ports USB-C partout maintenant) doit vraisemblablement être à l’origine de la non-détection.
Est-ce que tu aurais une solution s’il te plait?
Merci
Bon Jour,
Le cable pourrait être fautif…
quelle est la réponse de ton mac a cette question :
(Si installé correctement)
fastboot --version
ou
(Si pas installé)
cd ~/Downloads/platform-tools
./fastboot --version
2 Likes
Merci du retour Piero
Il s’avère en effet que rien n’était installé sur mon iMac (ce qui est fait maintenant : fastboot version 37.0.0-14910828), mais toujours rien. Donc en plus de l’adaptateur usb c → usb a, j’ai aussi acheté un câble usb 3.2
Iiiiinch Allah, ça devrait être bon après ça. Encore désolé, suis un gros noob 
fastboot devices
Hi Piero!
Unfortunately I discovered your Safe Guide too late! 
’Cause you’re absolutely right: The Web Installer could’nt identify my FP5 (No compatible equipment detected) and the installing instructions on Smartphone Selector are imbuvable.
My first idea was to test the installation on my old Samsung A12 … but you know that story.
What was going on with the FP5?
Using MML commands in the terminal, I received a response from the smartphone for both ADB and Fastboot (I had previously installed Fastboot and ADB on my laptop, enabled USB debugging on the smartphone, and disabled the OEM lock). The fact that installing Git Bash was necessary was also an obstacle.
After unlocking the Bootloader, my smartphone entered a state that could be described as a one-way street with no return. No further actions are possible: a welcome screen saying “Hello!” is displayed - giving me three options: changing language, adjustments for impaired persons and Start.
Start switches to WLAN settings.
So how I get back to the beginning to start with your Safe Guide?
BR, RSilber
Because you already allowed OEM unlock
I think booting the device in Bootloader / Fastboot mode is a good starting point.
Did you removed previous Gogol account in Gogol/FairphoneOS ?
No, I did’nt. What kind of account is that?
How to do this?
Notebook and FP5 don’t see eachother. (adb devices, fastboot devices)
But the phone can be called and voice connection is possible.
Yes, the android system have been reseted as a never used device.
Go through the setup wizzard, as usual answering NO where it is possible and uncheck all possible box.
Boot to “normal” system mode,
Re-enable “developer Options”, “USB debbugging” and check “allow OEM unlock” is not greyed and still enabled.
Note your installed “Android Security Update”
.
Boot in bootloader mode
Run
fastboot devices
Then follow the guide.
.
Log out all account (like Google or Gmail…) registred on the phone before starting the installation.
Bonjour Piero
Désolé d’encore déranger avec mon installation. Le problème venait du port USB du Fairphone. Une fois changé, tout fonctionne.
Malheureusement, je suis bloqué à la connexion du Bootloader.
Lorsque je sélectionne “Restart Bootloader”, je tombe sur l’écran Fairphone et l’écran Start.
La connexion ne se fait ni sur l’écran restart bootloader, ni sur l’écran start ni lorsque le téléphone est rédémarré.
Le téléphone n’est d’ailleurs plus détecté même si j’ai les options développeur, le débogage USB toujours activés.
J’ai viré tous les comptes Google avant l’installation.
Je n’ai rien en fastboot devicesDésolé….
Thanks for the speedy answer Piero. My fastboot version is 37.0.0-14910828
But I get nothing when I check the communication to the device, which is duely connected and recognised in the USB info of the system 
When I check the bootloader status, I get : < waiting for any device >
So :
Fastboot fonctionality :
fastboot version 37.0.0-14910828
Installed as /opt/homebrew/bin/fastboot
Communication to the device : nothing
guillaume@imac-de-guillaume1 ~ % fastboot devices
guillaume@imac-de-guillaume1 ~ %
Bootloader status :
guillaume@imac-de-guillaume1 ~ % fastboot flashing get_unlock_ability
< waiting for any device >
guillaume@imac-de-guillaume1 ~ % fastboot oem device-info
< waiting for any device >
It seems that I can’t manage to “unlock” the bootloader
Again, sorry for the trouble
Look like a cable or USB port issue