I recently decided to install e/os on my oneplus 7 pro. The install was painless until I tried to enter a pin and got the infamous “Screen Lock has already been changed.” which has been an issue for fairphone and oppo devices in the past.
After a duckduckgo search I became aware I needed to restore the prior os, setup the same pin, link the same google account then remove the google account and turn off the screen lock. I followed these instruction…twice. The second time I let it stay on the rom (crdroid which I was using previously without issue) for around 15 minutes to ensure it had time to do whatever before removing the account and screen lock.
Factory reset after each attempt for both os’s. I reinstalled eos once again and received the exact same error. Ok, that has exhausted the available info on duckduckgo other than to “link your google account on the new os” which is done via microg but obviously that is not sufficient.
So what do I try next to get my oneplus 7 pro running eos with a screen lock? I’m certainly glad I tested on this device before making a change on my primary device. The os looked very promising and I found apps such as sayboard (voice ime), dicio (voice assistant) etc to fill in parts that were strangely missing. Solid Explorer would not recognize it was paid for so I install Mixplorer as an alternative. Hoping this issue can be resolved and I’ve done my due diligence to try to find the solution.
Before install of /e/ you must remove all Google accounts, passwords, screenlocks or PINs.
The experience of others with Factory Reset Protection has hashtag frp.
Usually to return to original Google Android, and ensure all such secrets are undone is sufficient. (i guess it will include all accounts in the Settings > Accounts area exposed on original OS.)
It seems to me possible that FRP is working differently in a15. Back in the day manufacturers had the ability to prevent any reinstall at all but many manufacturers didn’t deploy it.
Just a guess, maybe this FRP preexisted your CRDroid install while causing no problem there ??
This phone went from oxygenos to a few pixel like custom rom’s from xda to crdroid and finally e/os. None of them had any issue with the screen lock even when I didn’t install gapps on them. I added the account and then fully removed it confirming nothing related to google showed in account including payment methods. I then set the pin lock to none. Not sure what more I could do to meet the criteria for frp. I also searched the forum for frp related issues and read the threads prior to posting with no other suggested methods than those already done. If worse comes to worse I supposed I could use crdroid with microg. Both crdroid and e/os were the a16 builds.
Thanks for the response. I’ll think on that fix but sadly I think I’m just going back to crdroid which was working well for me. e/os looked very nice but just didn’t work in my particular situation and I’ve spent enough time searching and trying to get around the issue.