Is it safe to lock my FP6 bootloader?

Hi all!

I read about anti-rollback on the forum and in the documentation. I think I’m in the clear, but I’d like to double-check that I’ve got it right since it seems horribly common to end up with a bricked Fairphone. As I didn’t find any nice commands or scripts to double-check this myself, I’m asking for a second pair of eyes to go through what I’m doing.

I had my FP6 sitting unused from October with Fairphone’s OS. I ran the necessary VoLTE and VoWifi tests before running the web installer. I avoided the system upgrades that were offered. The bootloader version was FP6.QREL.15.148.0 while it was still locked. (I wish I took a picture of the system info before unlocking, but it’s too late now.)

The currently installed /e/ version is 3.3-a15-20251210556408-official-FP6 with Android security update December 1, 2025. Vendor security patch is August 5, 2025. Curiously, it seems like the bootloader has been rolled back to FP6.QREL.15.138.0. This seems suspicious, but I haven’t read that anti-rollback cared about this, so I assume it’s ok.

If anyone can confirm that I’m ok to re-lock my bootloader, I would be very grateful.

Hello @fatboot, Welcome to the /e/ users forum.

look like you are in good conditions to relock…

2 Likes

Thanks for the confirmation. I went on with the instructions for locking the bootloader, but after giving the fastboot flashing lock_critical command, the phone rebooted all the way to the welcome screen before I was able to give the fastboot flashing lock command. Can I reboot back to fastboot and run the second command, or should I go through the setup and change some settings first?

I noticed that the bootloader re-locking instruction on Fairphone’s support site has this extra step that /e/ documentation is missing:

Hold the Volume down button immediately as your Fairphone reboots to return to fastboot mode.

However, that instruction is not helpful either since the ship has sailed.

I found this post which says that rebooting directly back to fastboot for the second lock command worked fine. I’ve also read about checking the state with get_unlock_ability command before locking, but I’m unsure if that’s relevant here.

Once again, thanks for any responses.

1 Like

Yes you can and you have to. You locked the first part and then the device reboots, properly into the OS. Then you can turn off and use buttons to get again into fastboot

2 Likes

Thanks, I did just that and faced no issues.

Sorry to bother you but i cant get my head around this rollback thingy.

Fastboot says my bootloader is 15.138.0

Android security patch say 1 December 2025

I have installed IMG-e-3.3-a15-20251210556408-official-FP6.zip

Build number is BP1A250505-005

Build date is 10 December 2025

this is related to /e/ build

this is related to IMG-e-3.3-a15-20251210556408-official-FP6
the latest version released FairphoneOS for this device had Android security patch from 5 November 2025

so, you are right to relock the bootloader

[HOWTO] a Clear Guide to install "IMG-e-builds" when /e/ web installer fails