Trapped in fastboot mode with locked bootloader and corrupted custom ROM

You need an unlocked bootloader to flash anything to your phone stock FPOS or custom ROM doesn’t make a difference. The biggest :triangular_flag_on_post: is if get_unlock_ability=0 after flashing a ROM, if that happens definitely don’t lock the bootloader!

It’s been confirmed that the Fairphone devs are still working on a fix for whatever causes phones to brick, but as you mentioned there hasn’t been a update to the factory images in quite some time.
Maybe Fairphone are using Valve Time internally? :man_shrugging: :smirk:

2 Likes

Oh of course, silly me. The last phone I had I kept with the bootloader unlocked, so I never tried to see whether you could flash a factory image through fastboot with a locked bootloader on a custom rom.

Ahaha, yes indeed, it seems they are on a different temporal wavelength for this one!

Jetzt hat es mich auch erwischt. :cry:
Keine Chance im locked Bootloader das FP4 wieder zum laufen zu bringen. Das FP4 lief bis vor paar Tagen tadellos mit /e/OS. Mein Mädchen kam dann auf die Idee das mit der Google-Version alles “bequemer” ist. :man_facepalming: Hatte mit meinem alten FP4 (128GB) ja auch paar Probleme wegen den Slots, das konnte ich aber beheben.
Jetzt geht garnichts mehr.
Und die Warnung bezüglich “corrupt” hatte ich auch nicht.
Hat von euch schon jemand eine Idee oder Lösung ohne das Telefon zu FP einzuschicken?

Transl.:

Now it’s got me too. :cry:
No chance to get the FP4 running again in the locked bootloader. The FP4 was running fine with /e/OS until a few days ago. My girl then came up with the idea that with the Google version everything is “more comfortable”. :man_facepalming: I had some problems with my old FP4 (128GB) because of the slots, but I could fix that.
Now nothing works.
And the warning regarding “corrupt” I also did not have.
Does anyone of you have an idea or solution without sending the phone to FP?

Wenn Du das unlock-Kommando vom bootloader nicht akzeptiert wird, dann ist höchstwahrscheinlich OEM unlock deaktiviert (ist meiner Erfahrung nach auch der Standard, wenn du von /e/OS auf FPOS wechselst). Dann habe ich bisher von keiner Alternative zum Einsenden gehört. Da jetzt ja aber FPOS installiert ist (und nur nicht mehr hochfährt) stehen vermutlich die Chancen relativ gut, dass es auf Garantie läuft…

EDIT: hattest du den bootloader direkt nach der Installation wieder gesperrt - oder erst nach dem Hochfahren und Prüfen, ob es eine noch neuere Update-Version gibt? Es hält sich weiter das (vielleicht wahre) “Gerücht”, dass das Problem dann auftreten kann, wenn du von einem neueren Patchlevel auf einen älteren wechselst…

1 Like

Hallo Volker.
Die Installation (Stock-Rom) war fertig und ich wollte den Bootloader wegen der Warnmeldung sperren und dann die neuen Updates über die Einstellungen installieren.
Dazu kam es aber garnicht erst. Ganz “normal” über die Console gelockt und auf dem FP4 bestätigt. Dann war Feierabend und nur noch der Fastboot Modus und Locked.
Das Gerät wird über fastboot devices erkannt, aber alle Eingaben enden mit not allowed bzw not in locked mode :cry:

Ja, tut mir leid, aber ich bin mir ziemlich sicher, dass es in diesem Fall nur hilft, den Support zu kontaktieren… :frowning:

Hallo @Volker ,
habe ich Samstag bereits gemacht, bis jetzt ohne relevante Rückmeldung :angry:
Ticket (automatisiert) habe ich, aber wie dort empfohlen mal anzurufen ist nicht möglich, keiner erreichbar, später versuchen :-1:

Habe gesehen das es einen “Negativ-Support-Thread” gibt, und werden den mal auffrischen :wink:

Da gibt es einige und der support braucht halt min ne Woche zur Zeit, normalerweise steht das auch in der Mailantwort. Jetzt schon auf dem Support rum zu hacken wäre vermutlich etwas verfrüht. In dem Fall kann man auch sagen, irgendwie selbst verschuldet, da du ja prinzipiell um das Problem wusstest und unfair jetzt sofort Abhilfe zu fordern.

Wenn du geschrieben hättest “selber Schuld ein FP zu kaufen” , hätte ich damit leben können.
Nach 4 FPs und einigen gerooteten Galaxys, kann ich deinen Vorwurf leider nur “wegschmunzeln” :wink:
Und meine kurze Schilderung des Problems (welches ja durchaus bekannt ist) und der Frage wo ich das Telefon hinschicken soll, bedarf wohl auch keiner über 3-tägigen “Würfelrunde”.
Habe noch mal per Mail nachgehakt,… schaumermal.

PS: Nur falls jemand auf die Idee kommt mir eine Adresse zu schicken,… nachher ist das Telefon weg und ich selber Schuld :wink:

So, long story short: I was messing around with my FP4, trying to root stock FPOS by flashing a Magisk-patched boot image. Worked fine, but in my hubris I re-locked the bootloader without realizing that my latest flashing had reset OEM Unlocking to disabled and now I have a sustainably-produced brick.

  • When booting, it says “Your device is corrupted. It cannot be trusted and it will not boot”
  • Bootloader is locked
  • I can access Fastboot mode, but OEM Unlocking was disabled so I can’t use Fastboot mode for anything
  • Trying to access recovery just sends me right back to Fastboot mode

I’ve been searching the web and everything points to this being a hard brick, so I’ve already contacted FP support waiting to hear what it will cost in order for them to re-flash things at their facilities, but while waiting to hear back from them, I figured I might as well try my luck here at the forums in case somebody has discovered a magic way to unbrick an FP4 with a locked bootloader (I read up on the EDL Qualcomm Firehose strategy, but AFAICS it only works for FP3).

I moved your post to this existing (there are more in the forum but think this is the most informative) although it was initially about e/OS. So far there is no other way than waiting for support and send it to the repair center. They charge 30€ for this (should Cordon try to charge more do not accept and get back to support).

2 Likes

Just for the record, if you are in a similar situation again:
Don’t ever lock your bootloader with Magisk installed! Modified partitions and a locked bootloader are mutually exclusive.

Oh and welcome to the community :wave: hopefully your future experiences with the FP4 are a lot less paperweight like (and you don’t have to fight through the usual Cordon shenanigans) :crossed_fingers:

1 Like

God day fellow Fairphone users.
Recently I purchased a Fairphone 4 (Black, 128G), I followed the instructions on the CalyxOS website and the FP instructions on how to unlock the bootloader. The exact steps I took were:

  1. Follow the Fairphone setup and install latest update.
  2. Allow OEM unlocking using the code obtand enable USB debugging.
  3. Ran “fastboot flashing unlock” and “fastboot flashing unlock_critical”.
  4. Ran CalyxOS’s “./flash-all.sh”.
  5. Booted into CalyxOS, followed the setup and re-enabled USB debugging.
  6. Ran “fastboot flashing lock”
    After re-locking the bootloader I was no longer able to boot into CalyxOS and the phone would only display the “FAIRPHONE” splash screen and reboot. It never went further than that.
    USB debugging is still enable, so I can see the phone under “fastboot” devices, and I can boot into the bootloader and into the recovery menu.
    The phone does not show up in ADB. I fear this issue may be due to Google’s ant-rollback protection.
    The main article I followed is

I have already contacted support, but have yet to receive an answer. Has anyone else experienced these issues? Is there any known fix?
Thank you in advance!

Welcome to the community :wave:

I’ve moved your post to this existing topic, where users with similar problems gather to mourn their bricked devices :see_no_evil:

Your only way forward is to wait for support to react (try calling to speed things up, if they have reopened the phone lines already), send your phone to Cordon for repair, don’t accept their usual 600 € estimate, talk to Fairphone again and get your repaired phone back for 0 - 30 €.

I wish I could offer you better news, sorry :roll_eyes:

Edit: I don’t want to get your hopes up, but could you please check fastboot flashing get_unlock_ability :crossed_fingers: (didn’t see that in your description and you might never know)

Edit 2:

Wait, so you can still boot into Recovery? Maybe I’ve judged your situation too quickly…
Have you tried a factory reset?

3 Likes

I’ve tried “Wipe data/factory reset” in the “Android Recovery” menu. The phone is stuck in the same boot-loop as before.
“fastboot flashing get_unlock_ability” returns: “(bootloader) get_unlock_ability: 0”.

That’s not looking good, sorry.
Support will have to handle that.

3 Likes

Hello, have you tried bootloader unlock again ?
After booting you get the bootloader warning, but the phone works again (normally).
The corrupt warning comes from the security level when you install a lower level than the existing one.
Got my repaired FP4 back, installed /e/ (IMG-e- 0.23-r) bootloader lock and bäääm, . . . corrupt warning :scream:
Then remembered the security patch story, bootloader unlock again and flashed the current/ new IMG. And it now runs normally even in locked mode. :sweat_smile:
I think the problem is when you want to reset or take out the battery because of the error message, for example, and disconnect from the computer. Then the debug mode is interrupted and nothing works. :-1:

So do not remove the USB cable as long as there is still hope !!!

I was able to simply unlock the bootloader again and flash the current IMG.
Just luck or problem found, … I do not know, but will not reproduce this in any case. :wink:
I can only recommend not to install the oldest version of the alternative OS.
The e-0.22-r of /e/ is no longer officially available and now the e-0.23-r is making trouble.
I am certainly not the last to notice this :roll_eyes:

Good luck with the support :+1:

Can’t unlock the bootloader if you don’t have the ability to unlock the bootloader :point_down:

3 Likes

Yes, that makes sense.
That was ever with mine before the repair also so.
But @brickman comes / came at least still in the recovery menu
My contribution should also be a help / possibility for those who still come. :wink:

I think the difference in your case that you installed /e/ and not CalyxOS as in the meantime /e/OS defaults to OEM unlocked when manually installed… (imho for good reasons…).

2 Likes