check if you still have
./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
and
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
I must disagree on the statement saying that the current security patch date must be âolderâ that the one of the system that will be installed 
I am sorry but this is wrong, not only the official instructions state that if both dates are the same then it is fine, but I have also verified this in practice: same date is fine. It is important because this case happens quite often.
It is really preferable to send back people to the official instructions than trying to redo them ourselves only to make mistakes and propagate wrong information. I totally agree that in many cases (non-fairphone isntructions) are unsufficient or even wrong, Lineage OS has often better instructions, but in the case of Fairphones /e/ OS instructions are fine. We are all trying to correct those official instructions (thanks to you a lot of the time ) letâs continue in that direction.
There are still risks to brick a device or get stuck in the middle for non experienced people so it is also important not to understate those risks. If people are unsure of their ability to follow the manual instructions, then it is always better for them and for Fairphone and for murena to direct them towards pre-installed phones of the web-shop. I guess that murena would be happy not to have had so many bricked fairphone cases in the last two years.
Well, you mean that the current instructions are wrong, it could be but as said, I did install and relock once a system on security patch with same date and it worked well as per the current instructions.
So it would be better to transfer those comments to the topic dedicated to fairphone 5 &6 instructions improvement so that other people can confirm or not that there is something wrong in the current official instructions and in the mean time we leave people refer to the official instructions and avoid saying the older current safety patch date is strictly needed.
on Fairphone forum they say that booting in normal mode after install a custom android and before relocking will switch the unlock_ability to 0
The bigger issue is this:
Everyday someone is on the Forum the web installer doesnât show the red box or anything similar to warn about rollback. That is the problem we should address (and I did with some tag or what it is called) and try to get better documented. Often the web installer becomes for users who wanna take the âeasy non tech savy wayâ and then they have to get to know so much without preperation
Yes you are right this is a big issue.
I have seen that they recently improved the web installer for fairphones by adding a message about installing the proper driver first and also how to get the unlock code from fairphone, but it does still miss an automatic check on the safety patch date or else a manual warning.
Letâs add a comment in the dedicated forum topic and ping the proper person (Manoj?)
Not by me but created 9 months agoâŚ
Edit: I couldnât find where I have asked for it but the gitlab issue says enough I would say
I had read that it would be possible if both security patches had the same date. However, since I donât know the security date of the previous OS, I canât be sure about that (other than the status check Piero mentions).
If i had known this would cause a problem, I had waited some more before installing /e/OS/. But since I had already installed /e/OS/ on a Fairphone 3, I presumed that using the installer would be the safest way for me with my lack of installing manually.
Anyhow, I will check after the update. If all lights are green, I will attempt to lock and report back.
So, after I was able to update /e/OS/ a couple of days ago, I decided to try and lock the bootloader.
I have not been successful so far because I ran into some trouble I had not encountered before:
Using USB Debugging, I am not able to fully connect the FP6 to my desktop:
I guess most of you will not be able to read Dutch, so let me translate it for you. At the top there is a section for management. When I tap managed by connected device, it takes a long time for anything happens and then finally it says âcan not switchâ.
In the terminal I get this message:
But when I check my file manager (Nemo), I am able to access the FP6:
What can I do? Wait for another update for the connection issue to be solved? Is there anything more that can be done on the phone to make the connection?
adb commands works when device is booted in normal mode or recovery mode
when
fastboot commands works when device is booted in bootloader mode
I tried using the commands when in FastBoot Mode, but I get the same message: waiting for any device.
try to unplug â replug ?
I tried, but nothing changes.
Okay, now I plugged the cable in the back of the desktop and now something changed. I know that it was recommended somewhere, but before that made no difference.
Now it says:
./fastboot oem device-info
< waiting for any device >
(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
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
very good position !
how did you get that ? did you do something special ?
I donât know if I did something special. I updated /e/OS/ and then followed the steps you provided.
I was able to lock the bootloader without the phone getting bricked now 
Thank you very much for your help!
This topic was automatically closed after 90 days. New replies are no longer allowed.
