# Unable to relock the bootloader

**URL:** <https://community.iode.tech/t/unable-to-relock-the-bootloader/2457>\
**Category:** System and Apps\
**Created:** [24 March 2024 12:42 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457 "2024-03-24T12:42:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dutti](https://community.iode.tech/letter_avatar_proxy/v4/letter/d/e36b37/32.png) [@Dutti](https://community.iode.tech/u/Dutti)\
**Post date:** [24 March 2024 12:42 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457/1 "2024-03-24T12:42:13Z")

</div>

Device: Fairphone 5  
Installed OS version: 4.9-20240130

Hey, I just bought a fairphone 5 and decided to install iodé OS on it.

I followed this official guide:

> **[GitHub - iodeOS/ota](https://github.com/iodeOS/ota/?tab=readme-ov-file)**
>
> Contribute to iodeOS/ota development by creating an account on GitHub.

The automatic installer weirdly never worked for me, since it loses connection to the device when rebooting into fastboot.

The manual way works just fine for me.

What I encountered after trying to relock the bootloader is similar to the following post:

> **[Locking bootloader after installing Iodé 3.4?](https://forum.fairphone.com/t/locking-bootloader-after-installing-iode-3-4/94451)**
>
> Hi to all you experts out there! I tried to install the Iodé 3.4 Custom-ROM to my new Fairphone4 following the “official” instructions by Iodé found here (All files were downloaded from here) The installation went smoothly until step #12 where...

Behaviour after Installation:

Without locking the bootloader:  
It shows the warning, that the bootloader is still unlocked.  
Then it continues to boot into iodé OS just fine.  
When checking for OEM unlock, OEM unlock is active.

It seems I can use it just fine.

With locking the bootloader:  
It shows a message where it says “\<!\>  
Your device is corrupt. It can’t be trusted and will not boot”

When I re-unlock the bootloader and go through the whole process and after installation DONT relock the bootloader, the behaviour is the same as mentioned above.

I did not use the command “flashing unlock critical” and am not planning to do it.

My Questions are the following:

1. I don’t know if this bricks my device in the future, so is there a way to create a backup, so I can load it back when everything goes downhill?

2. You can order the Fairphone 5 with iodé OS preinstalled. I assume, that those devices don’t have this issue. If I’m correct: How are the iodé employees achieve it?

Thanks in Advance

Dutti

---

<div class="post-metadata">

**Author:** ![Lazarus](https://community.iode.tech/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lazarus](https://community.iode.tech/u/Lazarus)\
**Post date:** [11 September 2024 16:17 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457/2 "2024-09-11T16:17:25Z")

</div>

Same issue here. A FairPhone 4 thread at [FP4 - Unable to relock bootloader - #6 by vince31fr](https://community.iode.tech/t/fp4-unable-to-relock-bootloader/416/6) suggests installing an avb\_key to verify the OS, but I don’t know if a similar approach would fix the issue for FairPhone5, or if such a file exists.

---

<div class="post-metadata">

**Author:** ![vince31fr](https://community.iode.tech/user_avatar/community.iode.tech/vince31fr/32/13_2.png) [@vince31fr](https://community.iode.tech/u/vince31fr)\
**Post date:** [12 September 2024 10:15 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457/3 "2024-09-12T10:15:03Z")

</div>

Instructions on gitlab had not been updated for a while, that’s fixed. More recent versions exist for FP5 and FP4: the latest one is iodéOS 5.4, that you can find there :

> **[FP5 · master · ota / release · GitLab](https://gitlab.iode.tech/ota/release/-/tree/master/FP5)**
>
> GitLab Community Edition

> **[FP4 · master · ota / release · GitLab](https://gitlab.iode.tech/ota/release/-/tree/master/FP4)**
>
> GitLab Community Edition

The fastboot files contain the avb key needed to relock the bootloader. Relocking is proposed at the end of the flash process.

---

<div class="post-metadata">

**Author:** ![Dutti](https://community.iode.tech/letter_avatar_proxy/v4/letter/d/e36b37/32.png) [@Dutti](https://community.iode.tech/u/Dutti)\
**Post date:** [15 September 2024 10:15 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457/4 "2024-09-15T10:15:01Z")

</div>

So you are saying, upgrading to 5.4 and then trying to lock the bootloader won’t brick my phone as it did before?  
Has this been tested/confirmed as a valid solution?

---

<div class="post-metadata">

**Author:** ![Lazarus](https://community.iode.tech/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lazarus](https://community.iode.tech/u/Lazarus)\
**Post date:** [15 September 2024 18:23 UTC](https://community.iode.tech/t/unable-to-relock-the-bootloader/2457/5 "2024-09-15T18:23:26Z")

</div>

Also, do we need to overwrite the existing install to perform this, or can the key be installed with a different method?
