Hi! I installed /e/OS on my Fairphone 6 yesterday and have had a lot of issues regarding app installation.
After installing /e/OS 3.1.2-a15-20250903521531-official-FP6, I locked the bootloader again, as instructed on the official install guide. https://doc.e.foundation/devices/FP6/install
I confirmed it is locked with fasboot oem device-info (verity mode is true but I don’t think it is relevant). In the developer options, OEM unlocking is on and it is impossible to turn it off. It goes back to the previous page when I try, sometimes giving a crash error.
Yesterday, I installed apps from the App Lounge, but after a while it stopped working. It would do nothing after hitting ‘install’ and it would not update any of the installed apps. Deleting cache and data of the App Lounge made no difference. F-Droid would download the files and then give a ‘Can’t install packages while in secure FRP’ error message. Since then, I did a factory reset in Recovery mode. I have been able to install F-Droid and Aurora Store after that. F-Droid still gives the same error, Aurora fails too and even installing an apk from the file system doesn’t work. Both alternative stores have all the necessary authorizations.
I can’t revert back to the original Fairphone OS as the security patch of the last release is older than the one on this /e/OS release. The Fairphone (Gen. 6) Release Notes
Factory Reset Protection (FRP) happens when there is a Google account left on the device before /e/OS is installed.
There is another case recently resolved which you might read. You will have issues to think about regarding Android SPL. Perhaps check out how it went here /e/os FRP locked after flash from stock android
Hi, indeed that was the problem. I followed the steps from that thread and it worked, except fastboot flashing get_unlock_ability gives 0, so I booted with the bootloader unlocked. My guess is that the simple way to lock again is to wait for the next official /e/OS release with a newer security patch, flash it on the device and then fastboot flashing lock and fastboot flashing lock_critical without rebooting into the OS between the two. Is my assumption correct?
It is supposed to be equal now (/e/OS 3.1.2 SPL 2025-08-01) but it still gives 0. I don’t understand why.
I thought I needed to flash the next build with a newer SPL, but if I understand correctly, I can update the regular way, in the OS, and get the same result.
I’ve just flashed the last release of the official image (IMG-e-3.1.2-a15-20250903521531-official-FP6 at this time) and went in fastboot mode directly without booting the phone into the OS. fastboot flashing get_unlock_ability still is 0. It is not possible that the SPL would not be equal compared to what is was when the bootloader was locked, so I can’t explain it.
You are asking for “get unlock ability” on an unlocked phone. So as I understand it from the links I gave, this points to “device state” more than anti-rollback. That command does not actually query the roll back index.
This has been an issue previously and it crops up online quite often. There are a number of other posts linked to mine and @olli0371’s on this subject maybe one of those would shed a slightly different light.
Hey, i solved this get_unlock_ability 0 by flashing latest FPos, but dont boot, go straight back to bootloader and get_unlock_ability should be 1! The trick for me was to not boot /e/os 3.1.2 after flashing before locking, reflashing /e/os did not help with get_unlock_ability in my case, only after FPos flash. But you can flash it again after FPos and it shouls still be 1.
I had no problem flashing FPos even tho the SPL was older… However do it at your own risk.
If I boot, the OEM unlocking option is greyed out and on. According to hirnsushi’s instructions the state of “get_unlock_ability” should have been 1 after flashing the device and going to fastboot without booting into the OS first.
But then in this post he says that basically it doesn’t concern me? I would not try to lock the bootloader now though.
Ok, I get it! Even though my bootloader was last locked with an SPL newer than the one of the last release of FPOS, I guess if I don’t lock the bootloader it doesn’t matter while FPOS is on there, it doesn’t matter.
So the steps are
Boot in fastboot
Flash FPOS and go back to fastboot at the end
Check “get_unlock_ability” (should be 1)
Flash /e/OS and go back to fastboot at the end
Check “get_unlock_ability” (should be 1)
Lock if state is 1 (maybe not the critical partition as it seems to be useless)
Waiting for an update of FPOS with an SPL equal or newer to 2025-08-01 (in my case) is safer though.
The alternative is to leave the bootloader unlocked, because in my testing I have not found an app that doesn’t work because of it.
Yes! You got it, also, im not sure how FRP was removed for me but i did boot FPos once to log in with google account and then delete it, but it probably did nothing.
These were my steps
Running FPos
Flashed /e/os 3.1.1 community
Locked bootloader without booting first
Realized FRP was on because i forgot to log out of google account
Unlocked bootloader
Flashed FPos, booted, logged into account and then deleted it
Flashed /e/os 3.1.2 official and checked get_unlock_ability which was 1, booted once to check SPL and FRP
Reboot to fastboot and check get_unlocl_ability which now was 0
Flashed FPos, reboot to fastboot, get_unlock_ability = 1
Flashed /e/os 3.1.2 official, get_unlock_ability still 1, locked bootloader
And i think its a good idea to wait ,i was contemplating aswell but im simply too inpatient and took the risk, ive actually been very lucky so far, I even locked my bootloader once with lower SPL index, the partition became corrupt but i went back to fastboot and flashed again with no issues.
Out of curiosity, can you set any lock screen password? I was not avle to while FRP was on.
These steps worked, my bootloader is now locked. Everything is solved. Thank you and aibd for your help!
I had the same problem as you with FRP and I solved it the same way as you. I had to log in FairPhone OS and I deleted the PIN code and the Google account (both may not be necessary). As it is required to boot into the OS to do so, the “get_unlock_ability” state reverts to 0. All of this is very counterintuitive and should be at least mentioned in the install guide. It’s neither Fairphone or the e Foundation’s fault if Android is the OS of nightmares, but it’s an issue many users who value their privacy and want to save a buck by installing /e/OS themselves could face.
Continuing from Feedback for v3.1.4 - #35 by czarny1975 where I replied to your question about method to return to FairphoneOS to undo an FRP issue where your proposal included
I think that will not be critical to your decision
… and same date is ok … Fairphone Android without lock is ignored.
You asked me by DM
I feel such questions are better answered in open forum.
The proposal will include unlock your currently locked, very newly installed e 3.1.4 - community - FP5. So you unlock, all data is lost.
As long as you do not propose to lock FairphoneOS the install is not expected to trigger anti-rollback.
(It is possible that the install script might complain about the actual build date, in which case you would see an error like date A is ahead of date B, cannot proceed but as I understand that is not seen with Fairphone as this is a Fastboot ROM install.)
so if I won’t lock bootloader I can install Android with SPL dated before SPL of last installed OS? In this case install factory OS to repair google account issue and then install /e/OS and then lock the phone?
I’d like to install official when it appear - till then I won’t lock the device, but…
I can’t rollback to factory - I am not able to OEM unlock in developer settings. when I try to turn this option on, I am asked if I really want to do this and answering yes brings me back to System settings, OEM unlock stays turned off…
Is there a way to unlock bootloader without this option turned off?
