I forgot to log out of my Google account… /e/os is now frp locked and i cant install side loaded apps or set pin code for lock screen. /e/os spl is ahead of FPos so im scared of reverting and removing frp! Technically it should be no problem as long as i dont lock the bootloader right?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Im gonna flash FPos with spl July when i get home and login to Google, i WONT lock the bootloader, if i succed then flash /e/os again, wish me luck
Is correct as long as you didn’t ever re-lock the bootloader. The anti-rollback index is set at the value when you last unlocked the phone.
Edit. This wording applies to an unlocked phone. So more generally the roll-back index is set by the ROM installed and locked. That index remains set at unlock.
Don’t you have your password for your google account then?
I do, but to my knowledge a rom with Google play services or some kind of lower level stuff are needed, i dont think microg is sufficient
Awwww, i did lock it… Fastboot reports it as locked, however OEM unlocking cant be disabled in developer options. Thx for saving me some time tho, il just wait until FPos gets updated… xD
It is also important to doublecheck the security patch dates, should the person return to stock rom.
@ph1utt3r please note this. I recommend to take a screenshot of Android SPL from Settings > About phone > Android version > Android (update level or aka) SPL. You cannot rely on my tips if you have no record of the actual dates recorded in locked state.
… but surly you would want to unlock and remove FRP and Google account ??
You were right in so far as you do have some flexibility in the unlocked state
Of course! I remember the patch dates
So unlocking now would set trigger at 1 August, and flashing FPos with SPL 05 July now would trigger anti-rollback, before even locking the bootloader, correct? Or have i misunderstood somehow?
I have flashed and locked this device with /e/os with SPL date earlier than previously installed FPos which was locked + unlocked, the flash went fine( as in no errors but i never actually booted ) and after locking bootloader was corrupt, now i cant say for sure if it was the locking or flash of the ROM…
Was there no clue of FRP before you locked the bootloader?
Now if you unlock the bootloader, you will need the Google password. Correct ??
Say this works. Now you believe you have to be on stock android in order to remove the Google A/C?
Fair enough, you can install the “July SPL build” of FairphoneOS. You can hopefully remove the account. Now reinstall e-3.1.1 is ok and relock is expected ok at the end only.
Just talking it through; is this how it is ??
I had no signs of FRP on FPos, and i locked the bootloader before ever booting /e/os 3.1.1 after flashing, first sign was under initial setup, setting PIN-code for lockscreen resulted is weird behaviour and a little box popped up “Screen lock was already changed. Try again with the new screen lock”, and when trying to install F-droid apps, box pops up telling me phone is FRP enabled. This is how i realized my mistake.
I presume nothing particular will happen if i unlock bootloader now, but i wont try until tomorrow since i need my banking apps for bus tickets!
Yes, i believe so, stock android would prompt me to login during initial setup to remove the FRP
Yeah, install July SPL, boot into unlocked bootloader FPos and remove google account, enable OEM unlock, install 3.1.1, lock boot and voila, hopefully
Ive done it! All is good, but i wont be able to lock my bootloader! FRP is gone, but get_unlock_ability is 0, this happened as soon as i booted into the /e/os 3.1.2 with unlocked bootloader to check the SPL, OEM unlock switch is disabled and greyed out but states in small text that OEM unlock is already enabled! Ive tried reflashing and returning to fastboot without booting /e/os but get_unlock_ability remains 0, i feel like this is why alot of people have bricked their phones.
What do i do now lol, do i have to live with unlocked bootloader…?
< Flashed FPos once again, did not boot, flashed /e/os 3.1.2, did not boot, get_flashing_unlock 1, locked the bootloader ^_–☆ >
No just another bit of magic … perhaps start here Installed 3.0.2 official and tried to lock bootloader - #5 by aibd and the following explanation by @olli0371
I successfully locked the bootloader now! I dont think i will be flashing any bootloader in the next decade or so, and thank you so much for guiding me!
Hello ph1utt3r,
I have a similar problem. After installing e/os FRP security triggered.
I’m not sure to understand how can I get rid of it. Can you guide me ?
Am I correct if I go :
1- Revert back to stock Fairphone os
2- Remove google account
3- Reinstall e/os
I posted a topic here explaning my situation.
Thanks
OK I did revert to FPos, connect and disconnect my google account, reinstall e/os and every thing seems OK!