# Back from de dead -\> the next episode of my journey to install iodeOS on FP6

**URL:** <https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208>\
**Category:** Installation Help\
**Tags:** Français, Fairphone6\
**Created:** [19 May 2026 12:48 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208 "2026-05-19T12:48:43Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![r4i](https://community.iode.tech/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@r4i](https://community.iode.tech/u/r4i)\
**Post date:** [19 May 2026 12:48 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/1 "2026-05-19T12:48:43Z")

</div>

Hello several month ago i tried and failed to install iodeOS on the fairphone 6. I opened a thread back then which is linked down here :

> [@Fairphone 6 bootloader relocking gone wrong](https://community.iode.tech/t/fairphone-6-bootloader-relocking-gone-wrong/7502/7):
>
> 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](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\_k…

I sought more answers on the Fairphone support forum, which is also linked below :

> **[Issues with custom ROM and rollback to FPos with the manual install software](https://forum.fairphone.com/t/issues-with-custom-rom-and-rollback-to-fpos-with-the-manual-install-software/129099/19)**
>
> Okay SO i have found the pattern i should follow to get the files uploading on my phone : Boot flash\_fp6\_factory on a CMD aside do fastboot.exe reboot fastboot then do it again on the flash\_fp6\_factory window, type YES The phone...

Then i dug a virtual hole and buried the fairphone for several month.

Today back from the dead, I did manage to install the FPOS from March → FP6.QREL.16.48.0.20260210142132\_WS15-factory (Security patch from 05 February 2026)

So i could boot into the fairphone, great success.

I made sure bootloader was unlocked, in developper option, it’s greyed out but seems to be unlock ( i did not relocked it myself.

As i read other thread like mine on this forum :

> [@FP6: Unable to lock bootloader](https://community.iode.tech/t/fp6-unable-to-lock-bootloader/8149/5):
>
> Hey there, I have been trying to relock the bootloader on my FP6 unsuccessfully for a while now and the message “Your device is corrupt, it can’t be trusted and will not boot” you received while you were trying to relock the bootloader is an indication that the FRP was triggered. I got mine triggered when I attempted to flash iodeOS 7.4 on a device running /e/OS. waiting a month and flashing iodeOS 7.5 on it did not solve the problem either. So using an LLM, I ran a troubleshooting session and …

I still have questions (sorry) :

1. It seems i can install last image from iodeOS for the FP6 → iode-7.5-20260506-FP6-fastboot.zip  
BUT is i’m still scared of the “device corrupt stuff” from a wrong SPL, how can i make sure that i can lock the bootloader ?
2. If we figure out it’s not possible at the moment because the SPL will not allow it, can i let it unlocked for the moment and then wait for 7.6 or 7.7 for the security patch to be greater and then relocking it confidently ? (losing my data in the process)

Thank’s for your help !

Also, i’m kind of familliar now with the security patch thing, but i might need more info on how my image and the security patch, interact with the SPL

r4i

---

<div class="post-metadata">

**Author:** ![mihi](https://community.iode.tech/letter_avatar_proxy/v4/letter/m/f04885/32.png) [@mihi](https://community.iode.tech/u/mihi)\
**Post date:** [19 May 2026 16:53 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/2 "2026-05-19T16:53:26Z")

</div>

Can I quickly sum up without reading every bit what might happend to know your current stance?

You tried to install iodeOS and the end result was when you locked the bootloader that the device was corrupt. Which is often because of SPL conflict. Now after severals months you installed stock OS and have february 2026 SPL. Is your bootloader currently locked?

If yes then I don’t see any problem since 7.5 has april 2026 SPL.

---

<div class="post-metadata">

**Author:** ![r4i](https://community.iode.tech/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@r4i](https://community.iode.tech/u/r4i)\
**Post date:** [20 May 2026 09:40 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/3 "2026-05-20T09:40:09Z")

</div>

Hello @mihi thank’s for the reply, your sum up is right on target, i have in deed february SPL on my OS, so i should be clear for bootloader relocking if i install iodeOS 7.5 is this right ?😃

---

<div class="post-metadata">

**Author:** ![r4i](https://community.iode.tech/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@r4i](https://community.iode.tech/u/r4i)\
**Post date:** [20 May 2026 12:14 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/4 "2026-05-20T12:14:50Z")

</div>

So, i installed the latest IodeOS and it’s all good, i’m so happy 🥳

---

<div class="post-metadata">

**Author:** ![rik](https://community.iode.tech/user_avatar/community.iode.tech/rik/32/1437_2.png) [@rik](https://community.iode.tech/u/rik)\
**Post date:** [20 May 2026 21:05 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/5 "2026-05-20T21:05:56Z")

</div>

Relocked?

---

<div class="post-metadata">

**Author:** ![r4i](https://community.iode.tech/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@r4i](https://community.iode.tech/u/r4i)\
**Post date:** [21 May 2026 08:22 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/6 "2026-05-21T08:22:27Z")

</div>

Yup 🙂 But as you can see in my other thread i have other OS issues now :

> [@Booting takes forever - stuck on iode splash screen](https://community.iode.tech/t/booting-takes-forever-stuck-on-iode-splash-screen/8216/2):
>
> I figured that i do not have sound, even if i connect a bluetooth speaker

---

<div class="post-metadata">

**Author:** ![CodeSalat](https://community.iode.tech/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@CodeSalat](https://community.iode.tech/u/CodeSalat)\
**Post date:** [21 May 2026 14:07 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/7 "2026-05-21T14:07:09Z")

</div>

This very much reads like the issue I was having: [Unable to flash FP6 - #4 by CodeSalat](https://community.iode.tech/t/unable-to-flash-fp6/8205/4)

---

<div class="post-metadata">

**Author:** ![r4i](https://community.iode.tech/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@r4i](https://community.iode.tech/u/r4i)\
**Post date:** [21 May 2026 16:52 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/8 "2026-05-21T16:52:29Z")

</div>

Hello, yeah you are right ! 🙂  
Do you know if i can do it now or should i want until newer spl to prevent corrupted device stuff ?  
(sorry i have PTSDs 😅 )

---

<div class="post-metadata">

**Author:** ![CodeSalat](https://community.iode.tech/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@CodeSalat](https://community.iode.tech/u/CodeSalat)\
**Post date:** [18 June 2026 12:42 UTC](https://community.iode.tech/t/back-from-de-dead-the-next-episode-of-my-journey-to-install-iodeos-on-fp6/8208/9 "2026-06-18T12:42:59Z")

</div>

To be honest, I only now came around locking the bootloader again 😃

OTA should still be running fine, so I don’t think this will be a problem? But this is the first time I am relocking the bootloader with a custom ROM, so there’s not much value in the information I can give 😃
