Fairphone 6 bootloader relocking gone wrong

Hello guys, installing IodeOS with adb and fastboot was going well, i had the fairphone rebooting and the prompt for bootloader relocking showing…
i did’nt want to lock it right now but i got confused with the button and i did what i did not want : relocking right away and now i have seen a corrupt screen showing and the bootloader is in locked mode…
so did i bricked it ? Is there a way to unbrick it since i have the bootloader looping and i can’t even start fast boot or recovery mode …

What i don’t understand is that security patch from iode seems to be fairly newer than the factory one from fairphone OS, how could this happen ? :cry:

Rzi

Where the dialog appeared? How that dialog looks like? OEM-Lock is another thing than bootloader unlock.

The vendor patch was newer? Are you sure you haven’t confused the patch with the platform patch?

Hello Dwainzwerg thank you for your reply

Just right after the OS install, the FP6 rebooted, then i saw a dialog with the same aspect than the bootloader (something like this https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Fwww.thecustomdroid.com%2Fwp-content%2Fuploads%2F2020%2F10%2FUnlock-Bootloader-OnePlus-8T-Confirmation.jpg&f=1&nofb=1&ipt=cb78cdcc010bf4d72cee4ae9dadee2ca634aee6fc3adb957807d1185be715dad )

i’m sorry but it’s possible, i thought that the default fairphone OS could only be older than the iode OS 7.1 which was released few weeks ago ..

Also i figured that my phone is in deed in fastboot mode (like this https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Fdroidwin.com%2Fwp-content%2Fuploads%2F2023%2F10%2Ffastboot-mode-Your-Device-is-Corrupt.jpg&f=1&nofb=1&ipt=94c65ff24458ff363eb1eabbff5ec8cc20ea1ee8feb2cc6d275a596880be34c1 )

So i unlocked the bootloader again, but i don’t know what to do next :frowning:

Also if it helps i got this :

.\fastboot.exe flashing get_unlock_ability

(bootloader) get_unlock_ability: 1
OKAY [ 0.001s]
Finished. Total time: 0.001s

Good news. If you can unlock it again (and did) then there is no brick here. If you can start Recovery from the bootloader, then go in and do a factory reset. If that doesn’t give you a booting phone, then I suggest a re-attempt at flashing and post back any output you get.

1 Like

unfortunatly, there is something i don’t understand here : even if i try to reboot from a command “fastboot reboot recovery” I still land on fastboot home page (https://xiaomitime.com/wp-content/uploads/2023/05/Fastboot-mode-OnePlus.jpg)

Also i can launch the flash-all script but it’s stuck at the very beginning :

.\flash-all.bat
Erasing ‘avb_custom_key’ OKAY [ 0.009s]
Finished. Total time: 0.015s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending ‘avb_custom_key’ (1 KB)

and it idles for ages and ages …

thank’s again for your help :slight_smile:

I think this just indicates that your recovery image is not installed correctly.

About the main issue, I would suggest reflashing to FairphoneOS and then re-trying.

Notes:

  • To be safe flash the November build (our newest images should match the SPL but just to make it safe let’s get a “not quite the newest” release from Fairphone).
  • After install FPOS, to be safe make sure that “Allow OEM Unlocking” is enabled in Developer Options before installing iodéOS.
  • To be safe, do not relock bootloader with FPOS or iodéOS install. After iodéOS install, make sure everything works, then lock it with fastboot flashing lock from fastboot (this will wipe out any custom setup so don’t spent any time configuring it).

You can see a lot of “belt and suspenders” approach to this guidance. It normally isn’t all necessary but since you have faced some issues let’s make sure your end result is a usable iodéOS install!

2 Likes

Thank’s Rik, i think this is the right things to do indeed.

However, I now struggle with the fairphone OS manual install since the fairphone software give us to install FPOS is crashing 90% of the time and the last 10% it does not detect my FP6 even if i know it’s detectable because i have a powershell windows on the side and fastboot devices works.

I’ll take it to the fairphone forums since i’m already so thankfull of your help i don’t want to bother you this much x)

I’ll link the fairphone forum topic here if it’s ok though

we will make it work somehow, i’m sure !

1 Like

Please do. I am sure others will benefit to understand this better as there have been different issues on FP4, FP5, and FP6 to get things installed and running well.

It was a long journey but i’m know back on FPOS @rik !

So now i can proceed to not screw it this time, i’ll update on the second iodeOS install, just so you know i installed FP6.QREL.15.151.0 the fairphone november build !

So the issue persist, i’m glad i could install iodeOS and make it work without bootloader locking, but even if i make sure that i check “Allow OEM Unlocking” and “USB debugging” the phone still land in untrusted mode when i reboot on fastboot and do fastboot flashing lock

I used FP6.QREL.15.151.0 (November Build) and on Iode OS i downloaded iode-7.1-20260116-FP6-fastboot.zip from one day ago

I think i’m still missing something about the SPL you mentionned