Was your bootloader actually unlocked still but was has no “unlock ability” anymore? Or were you “locked / couldn’t boot / couldn’t unlock”? With @HisDudeness I was assuming (yup, gets us all in trouble 
) that if he is unlocked he should be able to issue commands of some sorts?
Sorry for my absence. You understood it correctly, my bootloader is currently unlocked but the unlocking ability returns 0, so I wouldn’t be able to unlock it again should it get locked, particularly in a corrupt state, so right now I’m not flashing again. Stock ROM is currently installed.
Unless flashing iodé would help me get the unlocking ability back, although I read that flashing is not recommended while unlocking ability is 0. Until now the bootloader never locked itself on its own, but I guess that’s not a guarantee something won’t go wrong the next time.
Well yes it isn’t bad to be cautious! But if you do not lock on installing iodéOS I don’t think there is a risk: a broken install will not lock it, you install again. So just don’t lock until you see that you can relock ?
Ok, I can now confirm flashing iodé gives me back the ability to unlock, but I don’t feel this safe. My problem occurs when I’m going from FPOS to iodé, meaning that I am coming from a “0” unlock ability state. If I flash iodé from FPOS, lock the bootloader and end up in a corrupted state, I would risk a hard brick, since my unlock_state was 0 just before and I can’t test it until I boot iodé for the first time, get USB debugging back and reboot into bootloader.
Don’t know why I’m getting this problem right now, before I had flashing ability 1 even on FPOS.
Right now I’ve flashed the oldest FPOS version I could get (FP5-VT2P) and my bootloader version is FP5.VT2P.C.089.20260311, the same as the latest version of iodé if I’m not mistaken.
Question: can I instead flash an older version of iodé to get both an older security patch AND unlocking ability, and then try to flash the latest version and lock the bootloader?
1 Like
I have to slightly correct myself. I can check unlock ability in real time, even after flashing, before first boot. When, after flashing is done, the dialog asks me whether or not to lock the bootloader, the phone still responds to fastboot commands, and flashing iodé from FPOS (unlock_ability 0) the unlock_ability immediately returns 1. However, flashing iodé 7.4 and then 7.5 didn’t solve my problem, as the phone got corrupted again. I’m keeping FP5 VT2P and wait for iodé’s next version, hoping this will be my turning point.
I’m confused on the process you are following. Flashing 7.4 would be a “rollback” right (and then locking will soft brick as you see)? I don’t think if you “roll back then roll forward” it counts as “not rolling back” ??
Just what I feared haha
It was just a desperate move as I don’t seem to have any alternative. I’ll wait for the next version to ship with a newer security patch, in the meantime I’m using an old Zenfone 8 Flip.
Just a doubt: right now I have VT2P on, but I easily may have had VT2Q at some point. If the latest version ever had applies for the security patch, does it mean I’m updated to VT2Q’s one despite all the subsequent moves I have? Or does what is displayed in the settings under “Security patch version” count? Just to know if I’ll have any chance with 7.6 once it rolls out.
Not certain. BUT if you are on FPOS VT2P now, why didn’t direct 7.5 install work as it is also VT2P?
My comment before was that iodéOS 7.4 was pre-VT2P so FPOS VT2P to iodéOS 7.4 (pre-VT2P) was an issue, but I didn’t understand why not try VT2P FPOS direct to iodéOS 7.5 (VT2P)?
I don’t fully remember anymore, but I think when I tried from VT2P 7.5 wasn’t out yet, latest version was 7.4.
Anyway, I think I read downgrading FPOS version went downgrade patch version, is that correct? Given I’ve at some point had VT2Q installed, my patch version will forever be VT2Q, and I’ll have ARB (Anti-Rollback) issue, right? Should I flash VT2Q and stick with it untill a newer iodé with a more recent patch comes out, then try?
Commits · LineageOS/android_device_fairphone_FP5 · GitHub shows they have the VT2R patch included, I am checking with Vincent to confirm that 7.6 should include it, even though I don’t yet see it referenced in our commits: Commits · v7-staging · os / public / devices / fairphone / device_fairphone_FP5 · GitLab
Oh, great! So I just have to wait for 7.6 to come out for FP5 and then I can make a tentative. Since the latest version I’ve ever had installed was VT2Q, I shouldn’t have ARB problem, or any other bricking due to older security patch. I’ll keep my fingers crossed!
1 Like
Just to prepare in advance (since I feel like I only have one shot until the security patch gets cemented in the new version and I have to wait for yet another version before trying again without triggering ARB again), I’ve read on another post it’s not recommended to lock the bootloader back immediately after flashing, when prompted by the phone, but instead boot into the new OS once and then lock it. Can you confirm this?
Afaik:
When you boot the new OS once, you can verify that it boots (not triggering ARB). Plus you can check that “OEM unlocking” is still active, so if something fails with locking, you are still able to unlock.
(You don’t need to set up everything in the OS, just see if it boots. Because when you lock, userdata get’s deleted anyway.)
1 Like
If you are wanting to get to iodéOS, why not disable FPOS automatic updates? Then you can try as many times as you want with the iodéOS build that will have the same SPL. And you can even try many days in a row and not be rushed to “get this done asap before another update prevents it again”.
hi all, i was having the same issue and can confirm that i was now able to relock the bootloader with 7.6 version that was released today. hooray.
2 Likes
Nono, that’s not what I said, that wasn’t my concern. Practically everything automatic is disabled in my devices, especially updates. My concern was mainly from something going awry from the system somehow not liking even a security patch coincidence, hence having a better shoot when I’m upgrading, but it’s probably just superstition on my part. Anyway, I just saw 7.6 was released, I’ll cross my fingers and let you know.
Did you boot once first or lock immediately when prompted at the end of the installation process?
I couldn’t resist and I made a try. I’m happy to say I was able to close the bootloader without any problem. A message saying a different operating system is installed shows up at boot, asking to press the power button to continue, but Revolut app works without any problem. Thanks everyone for your time and help, and the teams developing iodé and porting it to FP5. It will take time to set everything up in my phone, but until now all the problems I had with the stock OS seems to be solved perfectly!
1 Like
And it didn’t work with unlocked bootloader? Apps should be tricked anyways that the bootloader is locked.