# Booloader relock limbo on Fairphone 5 **URL:** \ **Category:** Installation Help\ **Tags:** Fairphone5\ **Created:** [14 December 2025 17:21 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394 "2025-12-14T17:21:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [14 December 2025 17:21 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/1 "2025-12-14T17:21:45Z")
Hi there! I had to roll back to stock android from IodeOS on my FP5 for some [testing](https://community.iode.tech/t/audio-volume-very-low-on-video-recordings/7395), but I didn’t realize that the security patch was older (October) than currently on IodeOS (November). Thus I couldn’t relock the bootloader due to the risks of bricking the phone. Now I’m done with my testing on stock and would like to install Iode again, but I’m afraid to relock on it either, since `fastboot flashing get_unlock_ability` returns a 0. **So my question is: is it safe to relock the bootloader on Iode since I didn’t lock it on stock, or should I wait for stock to be updated so I can first relock on it, and then install Iode as normal?** Reverting back to stock I had to `unlock_critical`, so that might bring issues, since the instructions tell you not to do that? ( [ota / ota · GitLab](https://gitlab.iode.tech/ota/ota#fp4-fp5) ) Cheers! ---
**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:** [15 December 2025 17:19 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/2 "2025-12-15T17:19:06Z")
It is probably good that you are checking, there have been recent issues with users [that trigger “FRP” that prevents the device from being able to be unlocked again](https://community.iode.tech/t/cant-unlock-eom-anymore-because-frp-is-not-flashed-ive-been-told/7282). Part of that issue stems from having `get_unlock_ability 0`, and also in not removing any registered Google Accounts from the phone before re-flashing. My recommendation is to make sure to enable `get_unlock_ability` from Developer Options, make sure to _not_ have any Google accounts registered on the phone, then flash but _do not lock the bootloader_ at this time. Then login to the phone, make sure that Developer Options still has “Enable OEM Unlocking” enabled and that everything else is as expected. Then if all looks good, go ahead and relock using `fastboot flashing lock` (which will wipe your `userdata` again so you will need to re-setup). ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [15 December 2025 19:27 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/3 "2025-12-15T19:27:30Z")
Alright thanks, this sounds good. Actually the new FP update came quicker than I thought it would (today), so I should be able to relock it on stock now. But then reflashing Iode would introduce an older security patch so that might be an issue again… So I’ll consider my options haha. ---
**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:** [16 December 2025 22:40 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/4 "2025-12-16T22:40:28Z")
If you keep it unlocked waiting for the next iodéOS update, then the patch level will allow re-locking (without any reinstallations). ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [17 December 2025 12:45 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/5 "2025-12-17T12:45:37Z")
Yeah that’s the best option right now. I tried relocking it on Iode now but couldn’t, so I’ll wait for the next update 👍 Thanks for the help! ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [8 January 2026 20:39 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/6 "2026-01-08T20:39:42Z")
For an update, I still couldn’t relock after the 7.1 update, or even after first reverting back to stock and then reinstalling Iode. I thought 7.1 would come with the same December 5th security patch as Fairphone’s stock package, but maybe that’s not right then? ---
**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:** [12 January 2026 20:55 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/7 "2026-01-12T20:55:28Z")
OK so you are now on iodéOS, but unlocked. FYI to be safe, I would confirm that “Allow OEM Unlocking” is enabled before attempting to relock. But then when you issue “fastboot flashing lock” it gives an error, or then is unbootable, or what happens? The 7.1 update should include the SPL you refer to. But there are some FP4 users who still report that when they relock it will end in a boot loop until it reverts to the prior installation (due to the “A/B” partition scheme). Maybe that is what you are facing too? ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [14 January 2026 07:38 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/8 "2026-01-14T07:38:35Z")
No actually I chose to stay on stock for now, I don’t like to idea of walking around with the bootloader unlocked. The issue was that I got the “device is corrupt” prompt when trying to do the `fastboot flashing lock`. I think I’ll just wait for 7.2 and see if that changes anything 🙏 ---
**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:** [14 January 2026 17:43 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/9 "2026-01-14T17:43:11Z")
> [@AnonOnion](#): > > I don’t like to idea of walking around with the bootloader unlocked I hear you, but personally I am still of the opinion that an unlocked bootloader only protects you from an “Evil Maid” (and even then I don’t know of any successful "evil maid’ exploits on Android): > In my understanding, [an unlocked bootloader is only a risk to an “evil maid attack”](https://community.iode.tech/t/moto-g32-locking-issue/5795/14) - your data is encrypted and safe unless your unlock pattern / pin is compromised. I am genuinely open to a simple explanation of how it is a credible risk for privacy concerns… admitting that yes deep-state-level actors may have ways to trigger an exploit, but is this just due to an unlocked bootloader or more likely to something else? > [@AnonOnion](#): > > I think I’ll just wait for 7.2 and see if that changes anything 🙏 But to the issue, yes I hope future builds will have this fixed. As noted, we have confirmed issues with the FP4 that may possibly be related to this: > **[That's not fair: Fairphone 4 owners report new update bricks their phone](https://www.androidauthority.com/fairphone-4-bricked-update-3627690/)** > > Fairphone has pulled a new software update for the Fairphone 4 after some owners suffered from bricked devices. Our developers note the following about a question of whether that above post is related to our issue of FP4 users with locked bootloaders not able to upgrade to `v7.x`: > yes, but the actual firmware is FP4.QREL.15.14.3… maybe there’s a problem with it too. Waiting for the new firmware FP4.SREL.15.14.4, not released on their website yet So possibly FP is rolling out firmware updates across the line to address some issues. When they do they will be incorporated in our next builds following their release. ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [14 January 2026 20:53 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/10 "2026-01-14T20:53:52Z")
Right, I’m not that knowledgeable about this stuff and have actually been wondering what kinds of exploit scenarios an unlocked bootloader opens up. Been mainly going with the common sentiment that it’s risky. But thanks again, I’ll keep waiting for the updates! ---
**Author:** ![klic](https://community.iode.tech/letter_avatar_proxy/v4/letter/k/6bbea6/32.png) [@klic](https://community.iode.tech/u/klic)\ **Post date:** [15 January 2026 06:51 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/11 "2026-01-15T06:51:47Z")
I think more important are apps one depends on (or thinks one will depend on…) won’t work because they detect the open bootloader. Whether all this security theater is of any value is a complete different topic, though ---
**Author:** ![fezzy](https://community.iode.tech/letter_avatar_proxy/v4/letter/f/e19adc/32.png) [@fezzy](https://community.iode.tech/u/fezzy)\ **Post date:** [15 January 2026 11:38 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/12 "2026-01-15T11:38:58Z")
Things could have changed, but last time I checked, anyone with physical access to a phone with an unlocked bootloader can use the USB to install malware that can bypass all security. When you enter your PIN after such a compromise, all your data can be leaked to the attacker. ---
**Author:** ![MissPiggy](https://community.iode.tech/user_avatar/community.iode.tech/misspiggy/32/2158_2.png) [@MissPiggy](https://community.iode.tech/u/MissPiggy)\ **Post date:** [15 January 2026 11:50 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/13 "2026-01-15T11:50:29Z")
> [@fezzy](#): > > can use the USB to install malware If I connect a USB cable to my smartphone, I need to type my PIN before I can set to “data transfer”. So without my PIN there is no possibility to install any malware. ---
**Author:** ![fezzy](https://community.iode.tech/letter_avatar_proxy/v4/letter/f/e19adc/32.png) [@fezzy](https://community.iode.tech/u/fezzy)\ **Post date:** [15 January 2026 13:20 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/14 "2026-01-15T13:20:15Z")
To my knowledge, a PIN is not needed to boot into bootloader mode. Though this could differ on different phone models. ---
**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:** [15 January 2026 17:34 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/15 "2026-01-15T17:34:53Z")
> [@fezzy](#): > > Things could have changed, but last time I checked, anyone with physical access to a phone with an unlocked bootloader can use the USB to install malware that can bypass all security. When you enter your PIN after such a compromise, all your data can be leaked to the attacker. What you describe is what an “evil maid attack” is, but I don’t know of such an ability to install in this way on Android. The system is read-only, if it is replaced it will not boot due to signature mismatches. The writable `userdata` partition is encrypted until user unlocks it. So where can they install such malware? ---
**Author:** ![fezzy](https://community.iode.tech/letter_avatar_proxy/v4/letter/f/e19adc/32.png) [@fezzy](https://community.iode.tech/u/fezzy)\ **Post date:** [15 January 2026 18:55 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/16 "2026-01-15T18:55:13Z")
> The system is read-only, if it is replaced it will not boot due to signature mismatches. Hm, which signature check are you referring to here? ---
**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:** [25 January 2026 00:19 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/17 "2026-01-25T00:19:48Z")
> [@fezzy](#): > > Hm, which signature check are you referring to here? Sorry I didn’t explain correctly and certainly what I have written previously is misleading. I had been thinking at the time during various `dirty flash` swaps between systems that have failed to boot for for me it was because even though the device was unlocked, it still possibly had some ability to detect the underlying system had changed and then prevent the ability to decrypt. But that was _late night triple thinking something and the last two layers of thinking were not formed correctly_. 🙂 So I don’t know why it is needed sometimes to “Factory Reset” if a dirty flash fails to boot, but I have seen that (for seemingly unrelated reasons). However, I was also under the impression that since the OTA process is able to perform a build signature verification and not allow the install if new new update has a different signature, that we would also be able to inspect if a current running system had a tampered with base, so that possibly from recovery or fastboot we could inspect the current system to see if it matches what we expect from upstream. But that isn’t the case (more _late night over thinking going on: are you detecting a trend? The answer is no over thinking past a certain time for me but how do we enforce that?_ 🙂 ) In summary, you are correct _ **if physical access to your device by a malicious actor is suspected** _ then to be certain you won’t be the next (or first 🙂 ) victim of an evil maid you would need to **reflash the device before you would login to it and thus decrypt `userdata`.** So in summary, a locked bootloader doesn’t better protect the data itself (this is the same as if it had an unlocked bootloader), but its does prevent booting _if the system_ is changed out from under you, effectively “confirming an evil maid visited” 🙂 We won’t know if the evail maid paid a visit if it doesn’t have a locked bootloader. Sorry again to be spreading misinformation previously. I do personally remain unworried that any evil maids will be visiting me but to each their own 🙂 ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [7 February 2026 11:55 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/19 "2026-02-07T11:55:06Z")
For an update, I just tried installing iode 7.2 and there still are issues. Now locking the bootloader just doesn’t allow booting into the os and just always gets stuck to fastboot. However, I was able to `lock_critical` without any issues, so I guess that’s progress! I remember that earlier when there was no issues locking the bootloader `unlock_critical` was not part of the install process. Why was it changed and could it have something to do with the current issues? ---
**Author:** ![AnonOnion](https://community.iode.tech/user_avatar/community.iode.tech/anononion/32/2227_2.png) [@AnonOnion](https://community.iode.tech/u/AnonOnion)\ **Post date:** [7 February 2026 11:55 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/20 "2026-02-07T11:55:57Z")
So there shouldn’t be any risks unless an attacker gets their hands on the device? ---
**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:** [9 February 2026 18:38 UTC](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394/21 "2026-02-09T18:38:58Z")
> [@AnonOnion](#): > > Why was it changed We now wipe the FRP (“Factory Reset Protection”) partition as part of installing iodéOS as there were multiple users that bricked their devices by not de-registering a Google Account on their prior installation before installing iodéOS. Once FRP is triggered, the bootloader is locked and it is not possible to unlock again. For Fairphones, FRP can’t be wiped without first issuing the `unlock_critical` command. To your issue of not being able to re-lock the bootloader after a clean 7.2 install, I had thought the developers indicated this should work, but may need a userdata reset (but this should have been part of the install process too). I’ll pass to them you were not able to relock as part of a clean install to a FP5. [Next page](https://community.iode.tech/t/booloader-relock-limbo-on-fairphone-5/7394.md?page=2)