Hello,
I wanted to try Iode on my FP5, so I followed the installation via the installer.
Then when the installation was done and the phone was asking me if I wanted to relock the bootloader, as the installer was telling me “you can do it”, well so I did.
the phone work fine, but:
I can not set a password/pin/etc, it error with “screen lock was already changed. try again with the new screenlock”. Looking on the internet, it appear to be linked to a not locked bootloader, so curious I checked and:
in developper option, the OEM unlocking option is on, tapping on it just make the dev setting page crash. (so I can not uncheck it)
but booting the phone in the bootscreen (idk how its actually named, but the menu you’re getting with power + volume down) tell me that the bootloader is locked
so I am very puzzled what is going on here
another issue I have is that I am not able to install any external apk? f-droid worked fine, but trying to install protonmail or magisk (as at first I was like “oh well if bootloader is still locked, ima root then”) just give me “app not installed”, and that is from Iode browser or File
Hi. I have not been able to lock my FP5 after installation. I am assuming it is because the safety patch if of the same date than the FP stock android.
I just updated to iodé 6.7, which has a more recent safety patch. I will try to lock it tomorrow and I will post the outcome here.
Hi,
I’ve installed the last update too.
The FP5 bootloader was already unlock.
But in developer option, it’s appearing lock.
Quite strange.
I would like to re-lock the bootloader with fastboot but I’m afraid of bricking it one more time
unlocking the bootloader with fastboot flashing unlock still gives me the “screen lock was already changed. try again with the new screenlock” error. I’ll try to reinstall Iode from scratch as something is clearly wrong.
nope even a manual from scratch install following these instruction still give me this error that is with bootloader locked or not
can not set a lockscreen, can not disable OEM unlocking when bootloader is locked, can not install apk
oooookay
trying to install an apk in insular gave me a bit more information
my phone is in FRP according to it
Is there any way to disable that? I did not recall enabling this feature before but apparently I did?
Welp installing back stock fairphone rom to yeet FRP
hopping that the fact it have older security patch wont be a problem
quite anoying, the installer should have instruction on how to disable it before doing any install
Hi. I don’t know what FRP is. I will neeed browse the web
On my side, I have been able to lock again my bootloader, after updating to 6.7
Everything work well, unlocked or locked.
Please, do note the spoofing profile for FP5 in Aurora is not robust. You might need to change it back and forth in case you get the error an app is not compatible. More info at: Majority of apps not available for Fairphone (#1374) · Issues · Aurora OSS / AuroraStore · GitLab
Hope your issue is now over.
FRP is the service that lock your phone if you reset it without removing the google accounts on the phone
I had one account left on it that I was using for google play that I forgor to remove before unlocking the bootloader.
interestingly enough, using the flashing tool from Fairphone disable FRP without having to relog into a google account.
but yes can confirm now it work fine, locked or unlocked
Wow, I haven’t heard of this (needing to remove Google account before reflashing), that seems quite insidious, what is even the reason I can’t imagine, but what a headache! Thanks for explaining.
About your other errors, they did seem to correspond to not having the correct stock build before flashing iodé.
About your other errors, they did seem to correspond to not having the correct stock build before flashing iodé.
all the issues I had was due to the FRP, only reason it was half broken is due to lack of google play (as with them it would have directly asked for google account, without any way to continue setup). f-droid was working due to it privileged extension
to add to petefoth comment, it’s not necessarily about flashing a stolen device, it’s just about resetting a stolen device. As you can do so via ADB without an unlocked bootloader
actually an open bootloader was apparently enough for fairphone flasher to remove the FRP without loggin to google.
Other than that, great rom, just subbed to premium
Hy,
I’ve readed some of the other chats, but this is the closest to my problem.
Here in the chat is a lot written I’ve learned within the last days…
I’ve tried to flash a Pixel 5 with the installer and all worked fine, or looks like…
And during set up, what is written above:
can’t set display lock “screen lock was already changed. try again with the new screen-lock”
can’t install apps without any given reason (download worked, install failed)
I tried to install F Droid - and by luck I got a hint about what is going on “can’t install while in secure FRP”.
After reading a bit I wonder, I could do other than directly being asked to set up my google account. Mal writes the answer about missing google play.
I locked on with both previously connected google accounts but this did not reset the FRP )-:
I’ve had had linked a further account, by google family link, on the phone, this I can’t link without family link what I can’t install.
I can’t set OEM Mode, like Mal writes: settings is crashing.
This works only when I try to install Iode again, when I hit OEM is open, in the installer, and it is not, I’ve been asked to do so on the boot screen on the phone and than the installer goes ahead.
Deleting all google accounts from the device and delating the phone from the list “known devices” before redoing the install didn’t help.
Closing the boot loader or letting it open after installation didn’t change anything.
Any idea I can try – actually I’m lost?
Any hint what to think about programs to reset FRP?
Sorry for the issues but if you trigger “FRP” by re-locking the bootloader but not previously removing any logged in Google accounts from the prior system then it may need to be sent to Google for service
For “fully Google’d installs” if FRP is triggered, you can attempt to login to Google with the same account on the new install and it may unset it. But I don’t think that microG has support for that. You could try to login to microG with the Google account that was on the device previously, maybe it works?
But if you are in FRP mode which prevents the bootloader from being unlocked again for re-flashing, there isn’t anything else that can be done
The main problem was that I put my phone in FRP Secure Mode.
This happens when there is a google account logged in on the phone BEFOR and DURING you update to Iode.
To avoid this:
Remove all biometrical unlocks (fingerprints etc.)
All further display protection
All google accounts logged in on the phone
Reset to factory
Than go ahead with the installation as described.
=> Maybe this tip could be stated in the described pre conditions of the installer.
How I came out of FRP?
This ONLY works when you KNOW the details on the google account and the display protection that was on the phone while installing Iode.
The „problem“ is that Iode installs to less google to come out of this FRP, by the foreseen way of google, even when you know all above mentioned details.
So what did I do, I installed lineage os from a different source and some google packs, manually by hand.
Than I reached the google foreseen procedure to get rid of FRP.
Once that was done, I did everything described in the „pre conditions“ above.
How did you install LineageOS as an intermediary step? Wasn’t your bootloader locked and unable to be unlocked again? I am a bit confused by this comment:
Hy Rik,
yes, as mentioned further above in this chat, you are not able to open OEM Mode, either app crashes or it is like you hit the „back button“ on your phone.
But when you try to install, also with the Iode installer, and you ignore „I’ve opened OEM Mode“ when you are asked during the process, than the phone reboots and you can enter boot mode and follow further on in the inst.
With the inst. manual from lineage os it also worked in this mode and by installing „mind the gap“ from „git hub“ as an addition after installing lineage you can come to the point to get rid of FRP.
Than, as soon as the phone asked you for an internet connection you come to the point to log in with the old google account. This comes before you are asked to enter a display protection, what you can’t set in FRP.
But if you do, in my case, it was reopened again.
Ps. In the inst. Man. From lineage, the thing with removing google first is mentioned
Second the really do NOT recommend to relock the boot loader after installing. That is the reason why I try with iode.
Cases became more where apps do not work, because of the open boot.
I hope it is getting better now, actually I’m still struggling be reactivate my eSim.
Third thing more: In the Sim Card manager, it is statet, that the phone (Pixel 5 redfin) has TWO physical Sim slots!
Thats wrong! One physical and one additional eSim.
Fourth: When you log on with google, the security question „we detected an log on on following device, was it you, sometimes detects a Pixel 5 and sometimes a Pixel XL
So your bootloader must have still been unlocked (but you also had FRP)?
microG reports your bootloader locked regardless of if it is actually locked or not I am not saying all your apps will work, they may be checking for “Google Device level Play Integrity” which microG can’t pass regardless of if the bootloader is locked or not
Yes that would be a good warning I will make an issue on that.
This is due to microG “spoofing” your device for privacy (“feature” not a “bug” )
I am not saying all your apps will work, they may be checking for “Google Device level Play Integrity” which microG can’t pass regardless of if the bootloader is locked or not