I can solve this by just keeping the bootloader unlocked. Then everything works fine and I can boot into iodeOS. But this is less secure.
The issue does not seem to be that the vendor’s update version is too old. iodeOS tells me that the vendor level is 5th on June, while iodeOS’ update level is 1st of July. Am I reading this incorrectly? Is there a way to lock the bootloader?
What matters is the vendor patch level before you installed iode.
When you where on FPOS FP5.VT2Y.C.108 you had vendor patch level July 5th.
Maybe you can quote the exact error message, then we can see if you hit RBP (downgrade of vendor patch level), FRP (didn’t log out of google account) or something with flashing went wrong.
Thanks for your response. Then it’s possible that I was on the 5th of July level before (the phone was up-to-date before). Is there a way to work around? Just waiting till iodeOS publishes a version after July 5th, then update iodeOS and lock the bootloader then? (If yes, when does iodeOS usually publish the updates? As relocking wipes data I can’t really use the phone in that period)
To get that error, I would have to break it again, and to be honest it always feels a bit risky even though I was able to get it working again
The last two updates came in the middle of the month, but only the devs know
Exactly.
Fair point. As Iode works with unlocked bootloader, flashing error is very low. The only remaining other blocking point is when you were logged in with your Google Account before flashing.
