Bricked Fairphone 5 by re-locking bootloader after flashing /e/OS

Hello all,

i have bought a new Fairphone 5 from a German reseller, unlocked the bootloader, flashed the Official Version of /e/OS. This is the Image I used: **IMG-e-3.3-a15-20251210556408-official-FP5.zip

I have made sure that the Android 15 Firmware I flashed had a Security-patch level that is under the one of /e/ OS

The Android firmware I flashed was “**FP5.VT2F.C.065” and has a security patch Level of 05th October 2025.
The /e/OS Image has a patch level of 2025-12-01 (01st December 2025)

I have re-locked the bootloader and have made the terrible mistake of not executing `fastboot oem get_unlock_ability` to see if it was 1 (re-lockable) or 0 (not re-lockable).
I have bricked my device and I cannot execute `fastboot oem allow-flashing` because of it being in a locked state.

I want to send it in to Cordon so that they can flash the Phone using EDL mode and their firehose loader (the loader is not publicly available due to it being intellectual property of Qualcomm).

Can I send the phone in without having to wait for Fairphone support to reply or will that get rejected?

Thank you very much for your help!

Please use the Repair page to get the proces of sending it to Cordon started.
Or use the chat of Fairphone on working days 10:00 - 12:00 CET.

3 Likes

Thank you very much for the pointer! I have opened a Ticket on the repair page.

Hi,

Few monthes ago, I had a similar trouble even if the cause is not the same : Bootloader locking command seems to be done but

It has been fixed througt adb and Magisk.

Hello,

I have just read through the entire post you linked, congrats that you’ve managed to unlock the critical regions of your bootloader again.

When I ran `fastboot flashing lock_critical` I also didn’t catch the phone to go into the bootloader again, didn’t think that it would reset the `unlock_ability` to 0 :frowning: . Your solution doesn’t apply to my case as I cannot boot into my phones system. I cannot unlock the bootloader because it does not let me. I fell victim to myself and Qualcomms anti-consumer practices (them not having the EDL firehose loader publicly available!)

Oh well, it is what it is. I bought the Fairphone 5 because of its unmatched repairability, software support, Linux support, custom ROM support and the fact that it has USB-C 3.0 with DP altmode! I have looked at many phones and haven’t seen a one that better fit my requirements.

The Support has replied on Monday 12:33 CET this week. I replied that I’d like the address of the french repair-center and payment information, I have replied by using the reply function within the email program, is that the right way to reply? The support has not replied back since I replied (Monday ~ 18:00 CET) and I do not want to create a new ticket.

Hi,

this is what I get in my emails from the CS

to write back to us, you can reply to this message or find your request online

I would assume replying via email should work absolutely fine, but you could also log in to the support account and check your ticket history.

Hi! I can query the repairstatus when I put in my ticket ID, is that also the place where I can see the message history?

Not sure.

Tracking the repair - if that is what you meant - looks like that, and is hosted at the troubleshooting portal

Tracing the tickets looks like that, and is hosted at the support.fairphone.com

Apologies for my horrible mouse-writing :slight_smile:

1 Like

Yes, tracking repairs is what I meant. Thank you for the ticket-tracking link!

1 Like

Cordon got my Fairphone 5 on Wednesday, 21.01.2026 at 11:29 MEZ. They sent me a case ticket to track, but when I click the link “My Repair follow-up” I get to a site where I have to put in my:

  • Case number (the number from Cordons E-Mail, I think)
  • IMEI / serial number (I put in my IMEI here, should I have also put in my serial number?)
  • Customer reference / RMA / Insurance claim number (The “RMA No:” from the Cordon return voucher)
  • Tracking number (UPS tracking number from the UPS shipment that goes onto the parcel)

The site throws:

  • Your after-sales files : 0
  • The search returned no after-sales files

I probably did something wrong or put in wrong data?

After Cordon started repairing my device at 9:51 MEZ today, I already tried again afterwards and got the same error/warning.

Really awesome that Cordon is this fast though.