hey there, stock os was bugging me about installing the august 5 security patch at 2 am, and so i did.
have i fluffed myself over with this?
i’m aware of there being a rollback index on phones and it resetting whenever you install a new update, are fairphones affected?
and if they are, is iodé up to date with fp5’s current stock (a15 august 5 security) so that installing iodé and relocking bootloader doesn’t brick my phone?
i’m not super knowledgeable on this stuff and don’t have money for another phone so go easy on me please
additionally i’d appreciate some guidance in regards to precautions i should take to have a smooth experience, for example i guess i should remove my google account from the phone before installing?
Yes, the v6.7 builds include August security patches. FYI, I think it would not brick if attempting to install an older version, it would just refuse to install and give a message about not being able to downgrade.
You phone will be totally wiped, I don’t see a need to remove your google account first. So, personally, I don’t think any custom guidance is needed. You will need to unlock the bootloader, which will wipe your device anyway before the iodé install can be done. (A security feature of Android is that whenever the bootloader is locked or unlocked, your userdata partition is wiped out)
Just to let you know
I installed Iodé right after last fairphone update (the launcher constantly crashing pushed me to do it), and was just fine.
about google account, exept if you’re certain that you disabled any feature that would trigger FRP (can’t recall the name, something like find my phone) I would indeed remove any google account.
If you don’t and the installation is semiborked due to it, flashing default rom back to it will disable FRP
is it normal for the installer to be seemingly stuck at “sending avb_custom_key (1kb)”? that’s right after a “warning: skip copying avb custom key image avb footer (partition size: 0, image size: 1032)”, it’s been like that for ~20 minutes now and i don’t know if it’s actually stuck.
if it’s the cable i’m using, can i safely stop the process somehow to replace it and restart it or something?
no matter what, i could not get avb_custom_key to flash. installer wouldn’t do it nor could i do it manually at all, because it just gets stuck on “sending ‘avb_custom_key’ (1 KB)” and nothing happens it seems
going back to stock and giving up as there’s no way i’d run an unlocked os
I am guessing you aren’t interested in testing anymore, but I wonder if the FP4/5 install guidance about checking get_unlock_ability from adb would show true or false?
It may be as you note the Aug 5 security patch you applied is preventing this now, but it would be informative.
I hope that we don’t give the impression that iodé is only for the experienced custom ROM enthusiast. Certainly the custom nature of ARM SOCs, Android security design, etc. makes it much more involved than flashing a Linux distro on an x86/64 PC though!