Hello everyone,
I’ve just installed E /OS on my fairphone 6 configured etc … BUT I didn’t noticed the PIN code / Fingerprint didn’t work. I see some issues about a previous google account on the stock OS but I m not sure to understand. Actually everything work fine except this and it’s very annoying. I lock my bootloader with the version 3.3-a15. Someone can guide me please ?
If y’all need other informations, tell me
Hello @tonguechaude, Welcome to the /e/ users forum.
does it say something like “already enable” ?
.
if yes, look like you didn’t saw the warning,
and solution should be to unlock e-3.3, install FairphoneOS, remove the screen lock,
reinstall e-3.3 or e-3.4, then relock the bootloader.
does it say something like “already enable” ?
Yes exactly !
You are right I didn’t follow your tutorial … I’m a bit afraid about brick it, if I flash my e os now with a SPL 1/12/2025 to install latest fairphone OS with a spl 05 November 2025 I think it would be bad for me (FP6 become Brick6OS)
So I only need to remove the screen lock like my password or is it bind to my google account and I need to configure FpOS with the google account to erase it after ?
Thank’s a lot for your time and sorry if I’m asking dumb question.
not if you keep the booloader unlocked.
depends if you had or not a connected Gogol account on this phone in the past… yes.
Thank you so much !!
In the future can I lock the bootloader again ?
Okay great thank you for your time !!
I have fixed the issue with your help, Now I can use the fingerprint and use password BUT!!!
❯ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.001s]
Finished. Total time: 0.001s
I dont know why honestly …
i am currently investiging on that…
it is corelate to the “allow OEM unlock” feature in settings → System → Developer Options,
is it disable ?
are you able to enable it ?
Are you able to restore FairphoneOS and boot on it ?
(To get unlock_ability to 1)
then, enable “USB debugging” and “allow OEM unlock” is needed even already unlocked
(I think it is what you missed..)
Have you shown us output of
fastboot oem device-info
Are you able to restore FairphoneOS and boot on it ?
(To get unlock_ability to 1)
Honestly actually it’s work very well, except some stuff I need to fix like android auto etc .
The only things it’s annoying is banking app. I’m not sure I want to reinstall everything a third time
As far as I remember when I checked the “OEM unlock” was grayed out on fairphone too.
my fear is if you lock with get_unlock_ability: 0, you may not be able to unlock anymore…
Is it primordial to relock the bootloader ?
Or if i’m waiting for an update this value can change ?
you can experiment by yourself,
but from what i have understood by also following the Fairphone Forum, only FairphoneOS is able to switch unlock_ability to 1
Understand, Thank you so much for your time !
Same issue here, only I did relock the bootloader… I am trying to get Fairphone to help me out with some recovery tools.
Hello @Timber2000, Welcome to the /e/ users forum.
Are you able to unlock again ?
Short answer: no.
Long answer:
fastboot flashing get_unlock_ability returns 0 (unlock blocked)
Settings app crashes when toggling OEM unlock with error: java.lang.SecurityException: FRP is active
However, Android settings show: oem_unlock_allowed=1 and oem_unlock_enabled=1
What I’ve tried:
Factory reset via recovery
Factory reset via settings
Logging in and out with original Google account via microG
Setting OEM unlock flags via ADB
Loading a rooted boot image, but was unable to
Restoring software via recovery update, but was unable to
Local update to the rom I installed via settings, but was unable to
All without success
