Can not uncheck OEM unlocking FP5

Installation Help
1

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
  • the command fastboot flashing lock give me this
➜ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [  0.000s]
Finished. Total time: 0.000s
➜  fastboot flashing lock
FAILED (remote: '       Device already : locked!')
fastboot: error: Command failed

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

2

appear aurora can not install apps too

3

looking at the gitlab instruction
I should be able to uncheck OEM Unlocking?

At the end, accept or decline bootloader relocking; if yes, boot, and in developer settings uncheck “OEM unlocking”

4

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.

1 Like
5

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 :wink:

6

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.

7

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

8

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?

9

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

10

Hi. I don’t know what FRP is. I will neeed browse the web :wink:
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.

11

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

1 Like
12

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é.

13

Makes it harder to flash a stolen device

14

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

1 Like