Two days old FP 6, bricked after a short e/os evaluation and rollback to Android similar as described by others here. While technically my fault, it is hard to understand the lack of recoverability from this mishap - especially for a device ambitiously named “fair phone”.
The well-intended experiment failed, back to iOS.
The same thing happened to me as you. I had a 3-day-old Fairphone 6. I wanted to go back to the stock ROM because the camera wasn’t working properly. I was very surprised by the brick. I read the instructions, as each phone model has different details sometimes. I was lucky enough not to sell a Motorola Edge 60 Fusion.
Just to clarify … the OEM unlock switch was disabled, the option was not greyed out?
And was this in /e/OS before reverting, or was this in Fairphone’s Android OS after reverting but before relocking?
And if the switch was disabled, it sounds like you didn’t enable it again before relocking? (Because of the message saying the bootloader is unlocked?)
I wonder if these turn out to be get_unlock_ability: 0 brickings.
Yes same story than you 3-day-old Fairphone 6… I can still rely on my old fairphone 3. loved fairphone hope the problem will be solved by command line or return to flash 
received Fairphone Android OS → installed e/os 3.0.2 → back to Fairphone Android OS was ok (and then I locked the bootloader and the device said ROM corrupted - device locked)
When I was on eOs, I had OEM unlock enabled. I rebooted into fastboot, unlocked the bootloader (OEM unlock enabled), and installed the rollback. It rebooted normally and the system booted into stock ROM. I re-enabled developer options and the OEM unlock icon was already grayed out and disabled! With no way to activate it, I got a message saying the boot was already unlocked. I booted into fastboot to close it, and it didn’t reboot anymore… HardBrick
Upside of all this imbroglio is, we might get the firehose leaked so that we can solve all this at the community/personal level.
@Alon_Brandt … more detail for investigating the issue:
Doesnt that sound similar to the FP4 Bootloader bug 
Which would mean dont lock after booting into the system and check get unlock ability is 1 before locking
@hirnsushi as you was the one who understands the FP4 bug best, should it be switched to disabled or stay enabled? I dont remember completely?
I don’t know what bug FP4 had. I checked the OEM unlock option in the developer options. I found it very strange that it was grayed out and disabled, yet at the same time it told me the boot was unlocked. So I continued from the Shell with the lock, which caused the brick. There’s no command that makes it easy to unbrick. Isn’t there?
As the bootloader was unlocked its normal its greyed out. I’m not sure if the disabled state is normal.
On all phones of any brand, the OEM unlock option may be grayed out when the boot is unlocked. But the option will always be enabled. But hey, that’s not important to me right now. The most important thing is that there’s no solution to the problem at the moment.
For you its maybe not important, however it is very important in general to understand whats wrong with the bootloader, the FPOS script or whatever and not all comments are addressed to you personally 
Just in case anybody reads this before attempting to relock the bootloader after reverting to Fairphone’s Android OS …
In case you installed /e/OS on your FP6:
Don’t try to revert to Fairphone’s Android OS for the moment, as you currently risk bricking your device when doing this, and as of now it isn’t clear why this happens!
What is clear is that you shouldn’t revert from the upcoming /e/OS 3.0.4 with the June security patch level to any Fairphone Android OS with May security patch level (see Fairphone’s release notes for this), because this would trigger Android rollback protection.
But /e/OS 3.0.2 was confirmed to have May security patch level, so this shouldn’t be the cause for the current brickings.
If you want to help to get to the bottom of this:
When in fastboot mode, run the command fastboot flashing get_unlock_ability before attempting to relock the bootloader.
Don’t relock the bootloader if the result of the command is 0!
Please report here if you get 0 as a result!
First try to get the OEM unlock setting enabled again in the Android Developer options and only try to relock the bootloader if back in fastboot mode the result of fastboot flashing get_unlock_ability is 1!
Please report successful relocking here (if you still dared relocking, brave soul)!
Just one rookie question: all these bricking issues only happen if you relock the bootloader, not if you leave the bootloader unlocked. Right? If the bootloader is unlocked, you can install any version of an OS, even if the security patch level is older…but what you should not do is try to relock the bootloader (for now). Is that correct?
Yes thats correct, bricking it when the bootloader stays unlocked is not impossible I guess, however rather rare
Add me to the list of n00bs that tried out /e/os, decided against it and bricked their brand new FP6 by assuming
Release date: 25 June 2025
implied
Security patch level: June 2025
Some info that might help identifying the culprit:
After I installed /e/OS and not locking anything, the OEM-unlock-switch was grayed out (and turned on). However, just now I noticed that this is not the case anymore, I can toggle it (ain’t gonna try). All I did in the meantime was flashing APatch-boot.img and installing an app or 2. Maybe it means nothing but it’s kinda weird that the behavior is not consistent, isn’t it?.
By the way, the /e/OS updater provides a beta-update to version 3.0.4, here’s a link in case someone can make use of it: e-3.0.4-a15-20250708507307-official-FP6.zip
You are ore still on e/OS and not FPOS correct?
So thats how it should be I think.
Now your FP is also rooted. Not sure why and how ths can be related or not.
It seems that I am in the same pickle as all of you. Tried out e/OS and ended up not liking it too much. So switched back to stock FP6: FP6.QREL.15.91.0.20250606204727_VS15-factory.
Then checked if the phone was booting into the setup screen, that worked. Reloaded into fastboot and locked the phone.
Now I’m stuck in the fastboot menu stating DEVICE STATE - locked.
fastboot flashing get_unlock_ability returns 0.
So I guess I’m stuck, and only way is to have it reset by support by sending it back?
Yesterday I also created a support request ticked, but no reply yet. Is there a faster way to get information on how to return your phone to get it fixed?
Yes thats the way to go. Make it clear that this should happen on their costs. Only way to speed up support is to get hold on them during online chat opening hours
@Alon_Brandt please acknowledge this issue and take preventive actions
