Hi,
Sorry to hear that happened to you,
Just to be clear the thing that made your device brick was that you tried to lock the bootloader after you booted stock OS.
Had you locked the bootloader before booting to stock OS the first time, it would have worked ok.
Also try and check the get flashing ability flag before locking. It could have helped you avoid the mistake.
But this situation can be recovered using their repair partners.
Have a nice weekend
1 Like
Oh ok I did not know that, thanks for the information. I’ll keep that in mind Incase I try something similar in the future
I just send a request to Fairphone and am going to send my phone to their partner for repair.
But good to know what the problem was.
Have a nice weekend you too
Thanks. I sent a repair request although the reason sadly isn’t a direct option.
(Still I described to problem obv.) Hopefully the process will work and won’t take too long
It might have worked depending on SPLs
1 Like
3 posts were split to a new topic: FP6 unresponsive after locking critical
Hi everyone,
I’m honestly nervous right now. I finally saved enough money to buy a Fairphone because I love the mission and what this community stands for. I found a Fairphone 6 second-hand and was thrilled — it even came with /e/OS, which I wanted to try!
After testing it for a bit, I decided to flash the official Android ROM. Everything worked — until I locked the bootloader. Now the phone says the ROM is corrupted, and it won’t boot at all. 
I submitted a support ticket immediately, but it’s been 6 days without a reply, and I really need a working phone ASAP. I’m scared I’ll have to spend more money I don’t have, or that shipping/repair will be too expensive.
Has anyone gone through this? Is there anything I can try right now to unbrick it, or at least make it usable until Fairphone Support replies?
Thanks so much for any advice — I’m desperate to get my Fairphone back up and running!
Hello and welcome
you may try the repair portal - Here’s how you can repair your Fairphone device yourself.
However, you mentioned getting a FP6 second-hand and with e/OS so I am not sure who is the proper addressee of your claim.
https://support.fairphone.com/hc/en-us/articles/14487777708946-Warranty-with-an-Alternative-OS
1 Like
I moved your post here, regarding unbricking options, see above, I fear there is no way other than waiting for support. Even without warranty it should be possible for them to unbrick, when you have something to proof its not stolen. It should cost around 50€. So try either the portal, however I guess that issues is not amongst the pre-selected options, or the live chat, and dont mention you have a ticket.
4 Likes
Honestly reading how many people(ok in the grand scheme of things not that many) this has happened to it would be cool if Fairphone added some warnings on the install android manually guide, about when and how to relock the bootloader correctly.
Hi,
That indicates that you booted for the first time and then tried to lock bootloader. Fatal mistake. The first boot turns off OEM unlocking and you can’t lock after that.
It’s a shame that this risk is not written in big bold red letters everywhere with instructions to lock the bootloader. Happens regularly @anon76468197
I’m so sorry but it’s not going to get fixed rapidly. If you need a phone just use your previous one or borrow from someone.
1 Like
In the same boat as everyone else here. Following…
Sorry, but this is plainly wrong. Please read all the details above (or here if even more details are needed).
It’s correct that the first boot turns off OEM unlocking. But you still can lock the bootloader successfully if by flasing you didn’t do a downgrade (of the patch level). What you can not do in this case is repair (unlock again) the phone in case you did a downgrade and the phone no longer boots.
(Still I’d not recommend to relock a bootloader with OEM unlocking disabled if you’re not 100% sure no downgrade has happened by flashing the OS!)
Really? Let me get this straight
You flash a brand new version of stock, don’t lock, but boot for the first time.
OEM unlocking is turned off.
When you get into fastboot, it will most probably return a get_flashing_ability=0
Did we not conclude that it means you shouldn’t lock?
1 Like
Yes, we did, this is completely right.
But to keep it correct there’s the IMHO relevant difference between “can’t” and “shouldn’t”.
You can if you’re absolutely sure your flashing was no downgrade.
You shouldn’t if you’re not 100% sure.
Hope this clarifies it. 
1 Like
8 posts were merged into an existing topic: Guide to bootlader and bricking [2025] – Discussion
Hi, in the same boat too.
I can’t understand the official Fairphone relocking procedure has not been updated to prevent this situation.
I’m trying to explain to them that I’m stuck because of their faulty procedure, but they just offer to unlock it at my expense. I don’t find that very Fair. To be continued…
1 Like
Fairphone refuses to take the case in warranty, because I installed /e/OS before re-installing Android.
I praised them again to update the bootloader procedure to stop trapping other users. We will see if they are responsive in any way.
My experience is very disappointing.
1 Like
You unlock the bootloader at your own risk. You are responsible of everything you do after that. You accepted multiple warnings and you ought to do your due diligence at each step.
I understand that it’s confusing and frustrating but don’t put it on the manufacturer.
You best bet is still to foot the bill, sorry.
1 Like
So did you ensure to not flash an older SPL? Because of you did, I still think you did not do anything wrong and FPs instructions are not sufficient.
That is unfortionate, however the repair is not that expensive comparibly if they charge you at all depending on whether it falls into the warranty. Just contact the repair portal directly