And a good day to you, sirs! I installed iodé on my Fairphone 5 because the stock OS made it clunky, heavy and power hungry. I’m loving it on the first try however, since I had to unlock the bootloader in order to install it, Revolut won’t let me use their app unless I close it back.
I’ve read official guides and posts, however the result seems to be always the same: the system gets corrupt and won’t boot, thankfully bringing me at least in fastboot mode allowing me to flash the ROM back on and restore my phone. However, starting from scratch for the fifth time having to configure my phone back and install my apps is getting quite tiring. In addition, the fact I was able to get it back on track so far isn’t a guarantee that I will be that lucky the next time, and I fear bricking my phone.
Reading online, the problem might be the Android security patch not being the latest one, but I downloaded the latest fastboot version and tried to relock the same day. I’ve opted in for the beta updates and installed the latest, should I try now? Is there a way to know the best moment to make a shot?
To explain in detail what I did, after unlocking the bootloader (I got a code from the FairPhone website using my Slot 1 IMEI and Serial to activate OEM unlocking in the developer options, rebooted in bootloader mode with adb, checked everything was alright with flashing get_unlock_ability, unlocked the bootloader in itself with flashing unlock and the critical partitions with flashing unlock_critical) and flashing the ROM (using the flash_all.sh script from the extracted zip), I booted into my new system choosing “Do not lock the bootloader” in the dialog, left the unlock OEM option on, booted back in bootloader mode and then made the opposite steps (checked I still had the ability to unlock with flashing get_unlock_ability, relocked the critical partitions and then the bootloader). However, whether or not I choose “Lock the bootloader” in the next dialog, upon reboot I get the corruption message which tells me the phone cannot boot. What am I doing wrong?
@HisDudeness
installing iodéOS via flash-all.bat/flash-all.sh has proven to be a safe method. At the end of the installatin process, relocking the bootloader is offered. This should be run before the first reboot when it is ensured that the system is ready for it (fastboot flashing get_unlock_ability).
Note: Subsequent re-locking doesn’t always work for me.
Unfortunately, choosing the bootloader lock option after the flashing brought me again in the “corrupt” state, forcing me to unlock back and flash the system again. It’s worth noting that in my bootloader screen I read BOOTLOADER VERSION - FP5.VT2P.C.089.20260311. Is this the cause? My bootloader version is different from the one you wrote, and refers to a date 10 days after the security patch you mentioned. Should I wait for the next release and try my luck again?
Forgive me if that’s a stupid question, but does that mean I have to flash back the stock image before making an attempt to flash iodé and lock the bootloader back?
@HisDudeness
Yes, exactly, but extreme caution is required!!! You should first check whether an FP5 firmware rollback is allowed!
If it’s not allowed because FairPhone blocks downgrading firmware (as Samsung likes to do), then you’ll have to wait until iode tech adjusts its iodéOS.
If you try to roll back the FP5 firmware even though it is not allowed, you will brick your FP5 in a nasty way.
Thanks! I’ll wait for the right moment because I need a definitive system which will allow me to set up my phone once and for all. I tried downloading the new package (7.5-20260506) but had no luck. I’ll now try going from the stock ROM (current has 05/04/2026 security patch). However I was not able to determine iodé’s patch date. How can I tell which one is it? The zip does not have the META-INF/com/android/metadata file…
Great, now I’m getting a new problem. OEM unlocking is greyed out because the bootloader is already unlocked, but get_unlocking_ability gives me 0. I’ve looked various posts on Fairphone forum but not one gives a precise solution. I’ve erased avb_custom_key and I’m trying flashing the stock ROM again in order not to boot into it after flashing, but I don’t think that will solve my problem.
As an update, I was able to get unlocking_ability back to 1, contrarily to what I feared. I then proceeded to flash iodé 7.5-20260506 after stock ROM, which showed bootloader version 20260330. However, I still got my system corrupted, and bootloader version shown after is 20260311, which could be the source of my problem. I thought the newest package would have a more recent date, but that does not seem to be the case. How can I know on my own when would be a correct moment to try again?
@HisDudeness
First, I recommend that you make sure that the FP5 runs 100% correctly with the FairPhone firmware again (undamaged). If necessary, you must lock the bootloader again with the FP5 firmware and then unlock it again. Only when the system is running properly again should you consider the next step - installing a CustomROM.
I would install LineageOS 23.2 first. This ROM is very stable. This would guarantee that your FP5 works flawlessly with a CustomROM. Switching from LineageOS to iodéOS is easy to do - if iodéOS 7.x is compliant with your FP5 firmware. Please ask @rik and the chief developer @vince31fr about this.
Don’t forget fastboot erase avb_custom_keyif you return to Stock firmware..
Thank you for your patience and constant help. So, going directly from stock to iodé is not recommended? So far, I’ve switched between the two around a dozen times trying to have my FP5 running iodé with closed bootloader. It works perfectly with both, the only problem being my inability to lock the bootloader back.
I’m getting a wild idea… would flashing a previous version of the stock ROM, with an older security patch, before flashing iodé solve the issue, or instead risk breaking everything?
Run and allow me to lock the bootloader without corruption? I can’t find that version to download, however FP5.VT2P.C.089 is available on the Fairphone webiste, which has 05 March 2026 Security Patch (I can’t find iodé’s security patch information, however the fastboot screen tells me 20260311 bootloader when installing the latest review; if the dates indicate the same thing I should have some possibilities of achieving what I seek).
Unfortunately, Revolut may not be working regardless of actually locking the bootloader or not. I see recent reports it stopped working but don’t have more details. Usually, as I understand, apps don’t see whether your device is actually locked or unlocked because microG should report locked regardless.
Now to some other comments as well:
Possibly the “corrupt won’t boot” after attempting to lock would need a Factory Reset in Recovery? I have seen this occasionally, but I am in the USA and thus don’t have access to a Fairphone But that would be my first try is simply do the data reset after the error. Or to reinstall and lock at the end of process.
IF YOU went back to stock FairphoneOS build make absolutely certain that you have “Allow OEM Unlocking” enabled before attempting to flash iodéOS! Not doing this has led several to hard brick: they do not lock at the end the FPOS install since they plan to immediately install iodéOS. But part of the FPOS install disables allow_oem_unlock. So the bootloader is unlocked but they don’t have ability to re-unlock again. Then they install iodéOS and lock at the end of the process but experience some issue, and then they have a hard brick: it won’t boot, but it can’t be unlocked again.
Damn, I’m stuck. My unlock ability is 0, erasing the avb key does nothing, and the OEM unlock option is greyed out (as it tells me bootloader is already unlocked). Right now, I have the stock ROM installed, and I can’t seem to get back unlocking ability. Any ideas?
Hi,
At the moment, Revolut does work on my FP5 with the bootloader unlocked. Sometimes Revolut stops working after an update, but then starts working again after the next update. Openbank, N26 and Wise always work for me with the bootloader unlocked.
But that would be my first try is simply do the data reset after the error. Or to reinstall and lock at the end of process.