I am attempting to put a new OS on my Fairphone 4 that came loaded with /e/ . When I go to toggle the OEM unlock option it prompts me to enter my pin and then just gives me a pop up that says “Allow OEM Unlocking?” with a cancel and enable button. There’s no option to input an unlock code (and I am unable to unlock in flashboot if I do select “Enable”). I’ve tried factory resetting and hitting toggle both with a SIM card in and out of the device. Any ideas on how to fix this?
Are you connected to some internet (wifi, data) while you try it?
Did you disabled "SIM card PIN " and “Phone Boot PIN” ?
Did you obtain your bootloader unlock code from Fairphone ?
Which command is giving which error message exactly in fastboot mode?
Yes, the phone was connected to the internet.
I don’t receive an error message. After sending the unlock command while in fastboot mode nothing happens.
I did obtain that code before starting. I did not disable either of those, should I try that?
Which OS are you using on the computer?
Does the fastboot devices command recognise your phone in fastboot mode, or does it give a blank line?
If Windows + blank line, this usually would hint at missing drivers for fastboot mode … I'm stuck at step 6 of unlocking the bootloader on my FP5 - #5 by AnotherElk
I remember this as a prerequite when switching OS
I think about it because you said :
and not my unlock code…
If you are running Fairphone’s stock rom, you have to enter a code at this point which you have to request from Fairphone.
/e/ is different: here you have to enter your device pin/password/pattern - whatever you have set as device unlock option.
If the possibility to enter your unlock pin does not show up for whatever reason, you can disable it by setting your screen lock option to none.
Without screen lock, you should be able to toggle the OEM unlock switch directly.
Good Luck!
This is the answer I was looking for, thank you! I’ll try again when I get home.
This solved my problem, thank you! w1900’s comment answered what I was originally asking, but that was not the actual problem it seems