Fairphone 6 unbrick: Trapped in fastboot mode with locked bootloader and corrupted stock ROM

[piero-e]

@FPbonn

Did you check the SPL before locking the bootloader ?

Caution: Your phone has a security feature called anti-rollback protection. This prevents installing older software versions once a newer one is installed. If you try to install an older software version while your bootloader is locked, you may trigger an anti-rollback error and brick your device.

See Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”

unclear formulation, my contribution :

@piero

If you plan to relock the bootloader after the installlation

this is not mandatoty, and only available with Official version, why relocking ?

Most important thing to take care about is the “android Security Update" aka "Security Patch Level” date (SPL) included in the installed Operating System on your device
at time of the unlock.

new version on witch you want to relock the bootloader, must included a NEWER (or the same) “android Security Update" aka "Security Patch Level” date (SPL),

otherwise you risk to change your device into Brick.

will be updated soon here :
A clear guide to install /e/OS on your Fairphone

[remdew]

Hello all,

I was really enjoying my faiprhone 6 and I tried to install Murena OS. Installation was fast and easy but I had some annoying problems in Murena with my apps. So, I decided to go back to FPOS and after all the manipulations the phone is lock… And even in command line it’s impossible to have anything else than fastboot menu… I have try to unlock the phone on my linux laptop in command line but no solution. What can i do ?

Thanks everyone !!!

[Lidwien]

I am afraid you have bricked your phone.
Have a look at this thread about a bricked phone.

[remdew]

I am just so annoyed and sad about the situation… If there is some examples where somebodies have reflashed the phone by a repair store it should be great ! I have buy the phone from a big arket store and I don’t know if they will understand the problem

[yvmuell]

I moved your topic here.

You have to contact Fairphone, only their repair center can help you. Maybe just use the repair portal, when possible,

Important for the future in case you want flash anything, always
check the SPL and ensure you never install an older one when you want to relock the bootloader.

[Marschbauer]

Hi!

I understand the problem and the associated risks. I’m currently in the same situation, wanting to flash my Fairphone 6 from /e/OS back to stock Android. Unfortunately, I only recently installed the latest /e/OS OTA update, which means I have a SPL of February 1, 2026. Fairphone Android currently has an SPL of December 5, 2025.

My question is: Why is Fairphone so far behind?

And how can I find out when the next update is coming?

[yvmuell]

@Marschbauer

My question is: Why is Fairphone so far behind?

Thats off-topic here so kindly dont discuss here as we users can only speculate.

@Marschbauer

And how can I find out when the next update is coming?

Check the forum, updates are published here once available. As they just published some Android 16 marketing I assume it will be soon, maybe this week

[Gerard_Farrell]

in the same boat. nothing to do except send it in for re flashing. the locking section on the website has now a large “warning” in red at the top which was not there when i flashed my phone. Support wants me to pay $30-40 to unflash it, which I believe is unfair, as i followed the instructions on the page.

[M4rk]

I was running /e/OS since I got this phone. But it always bothered me that so much stuff was not working. Like Android Auto. That did start working a few weeks ago, and just a few days ago stopped working again.

So I was done. I wanted to go back to stock, so I followed:

• https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone and
• https://support.fairphone.com/hc/en-us/articles/10492476238865-How-to-unlock-and-re-lock-the-bootloader

But after the very last step (all previous steps where fine), I got a “corrupt phone, cannot ever boot” message. I can’t remember the exact wording, it was gone pretty quickly and now the phone does not want to go past “fastboot”. I can use the volume keys to select other options, like recovery, but they all end up returning to this fastboot screen.

I cannot even turn it off, even that returns to fastboot.

So I created a ticket, hoping I can get Fairphone to fix this. But this is not a great experience.

I’ve been in IT for 45 years, I flashed numerous ROMS, from pixels to nexusmod But this was the first time when purely following the steps, I got a bricked phone in return

So there you go, cautionary tale.

Added info:
Downloads | 1 ❱ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.002s]
Finished. Total time: 0.002s

[urs_lesse]

If you can make the time slot (working days 10:00-12:00 Amsterdam time), contacting Fairphone about this via their LiveChat might speed up the procedure. Mentioning that your phone is bricked might simplify the explaining part. Recently, unbricking a Fairphone via their repair contractor Cordon in France cost something in the 50 Euro range (everything included).

You probably heard about the anti-rollback “protection” that Google built into Android a couple of Android versions back. If not: Installing an Android version with lower security patch level and then locking the bootloader is what triggers this.

[M4rk]

Which means the /e/os version was newer than the official Fairphone rom I downloaded today?

FP6.QREL.16.48.0 / Release Date: 16 March 2026 android 16

But the /e/os version I had was A15 (official) . So the Fairphone official was a whole android version later, so I figured I was safe. Guess not.

[M4rk]

Thanks for the info though, I’ll surely use it.!

[urs_lesse]

Unfortunately the release date is not the important date. It’s the security patch level date. Fairphone’s latest “Android OS” has a 5 February 2026 SPL, while Murena’s latest /e/OS version 3.6 has a March 2026 SPL.

[M4rk]

Aaaaah, I should have just waited a few months with the final locking step. I would have been allright. #sigh

[M4rk]

Dear @Fairphone, maybe you should update the website with that bit of information:

• Works regardless of what version you are on, and can be used to downgrade to an older version (for example: Android 13 → Android 11).
  Keep in mind: If you install an OS with an older security patch level than your previous OS, locking the bootloader might brick your device (more information).

The way it is worded here, was the reason why I though that “going up” in Android version meant I was going to be safe.

[yvmuell]

While @fairphone does not exist, thats already mentioned several times on the page from your link above

Warning!

• If you install an OS with an older security patch level than your previous OS, locking the bootloader might brick your device. Make sure the security patch level is the same or newer before re-locking.

And

If you install an OS with an older security patch level than your previous OS, Android’s roll-back protection might brick your device when locking the bootloader. Make sure the security patch level is the same or newer before re-locking.

[M4rk]

“@fairphone” was just an automatic tick we have on the internet these days

And yes, I should have read it better. But. my point is: It’s easy to think “Oh I’m going from A15 to A16, so I should be safe”. Silly me. This new system tripped me up. And I think that paragraph could be worded a little better / safer. That’s all. Not blaming anyone, just trying to help future “me’s “ from doing the same