Problem on Fairphone 5 - cannot setup password/pin/pattern

[monstrencage]

Hi people,

I’m a new user, and I’m trying to setup /e/os on my fp5. I’ve followed the steps in the official page.

Now (almost) everything is working. The one exception, which turns out to be pretty important for several apps that I want, is the mechanism to set up the screen lock code.

If I choose anything other that swipe or none, i.e. pattern, pin, or password, I get the message “Screen lock was already changed. Try again with the new screen lock.“, and the parameter is unchanged (meaning still either none or swipe, as it was before).

I’ve already tried the obvious things:

1. turning it off and then on again;
2. same thing, but in “safe mode”
3. resetting it to factory settings via the “erase all data” button.

I don’t know what else I can do.

If anyone has any idea on how to solve this I’d be very grateful

[aibd]

This sounds like Factory Reset Protection, other threads with the issue have hashtag frp.

This happens when a Google account, passwords or PINs remain on the device since before the /e/OS install.

Hopefully you have not relocked the Bootloader ??

The fix is to roll back to Fairphone Android, remove anything pertinent (avoiding any locking) and try again.

https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone

[piero]

@Manoj, @AudeM the lack of pertinent informations in official documentation on that subject
generate to much forum activity in my taste (also imagine that not all concerned peoples create an account here)
this is working for the idea that custom OS is only for geek…

[Manoj]

@piero

the lack of pertinent informations in official documentation on that subject

The FP5 device page has a Roll Back to stock link which points to the same page as linked above.

[piero]

@piero

to much forum activity in my taste

we are talking about missing informations

@piero

Remove all Gogol accounts, screen lock or SIM lock from the device.
before the OS switch…

that leads to feature not working frp

@piero

piero : 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.
…
user : I’m a bit afraid about brick it,
…
piero : not if you keep the booloader unlocked.
…
user : Okay great thank you for your time !!
I have fixed the issue with your help, Now I can use the fingerprint and use password

.

and false information (for the second month at minus)

displayed 4 days before the release that leads to bricked devices

@piero-e

@piero-e

After having installed /e/OS, and after the successful reboot into it, I checked my unlock_ability in fastboot, and it returned a 1. Further following instructions on the /e/OS website, I booted into fastboot again, issued the two commands fastboot flashing lock_critical and fastboot flashing lock and rebooted only to see a message that my phone was corrupt and would not boot.

I booted back into fastboot and did fastbook flashing unlockand fastboot flashing unlock_critical, and it seems to have worked, since the fastboot screen says "DEVICE STATE - unlocked.

@fonfan

On the e/OS/ download website it said SPL 2026-01-01.

it will be for e-3.4-a15 that is already out from “community branch”, but will be released soon from “official branch”

this one was lucky :

@fonfan

@fonfan

Thank you for all you r answers. From what you say I can safely conclude that I have involuntarily bricked my phone. I have flashed /e/OS 3.3 onto my phone. I have no idea how something like this can happen at all: I swear an oath that when I followed that link on the FP5 /e/OS install page (see screenshot obove) stating that what I would find was on SPL 2026-01-01 I found to .zip archives of /e/OS 3.3 with suspicious file names as for the SPL dates. I trusted the info on the preceding page, however, thinking that they know what they are doing.

And after having read your posts, I went there again, and lo and behold: all of a sudden there were three .zip archives, the top one being 3.4!

I am downloading it at present, and I will try to flash this onto the phone now. Hopefully this will work. My Fastboot output is as follows, which looks good to me: