Database Users

Forgot unlock passsword - how to get rid of it?

SOLVED.
Greets.
A mate of mine forgot his unlock password the other day. At first I thought it was gonna be the same as with Galaxy S - just flash it or better yet do a wipe/factory reset in recovery and be rid of it - boy was I wrong... I tried everything I could come up with - flashing costum SW, different kernels from xda, older/newer original SW, CMW resets etc. - no luck at all.
So now I turn to you beloved XDA and ur techies - does anyone have any idea how we could reset our SGS2's so that this passwords would be gone aswell?
Solution:
Just spam random passwords (think it was 5 wrong) and then a message appears, that the SD card will be reset and a full wipe will be done - press OK and bang the phone boots normally.
In case anyone finds themselves in the same situation. You lose all your data ofcourse but the password is deleted and bang the phone works.

What password are you talking about, because a factory reset in recovery mode should do it.

I am talking about the screen lock with a password. Like I said nothing works... everytime I turn the phone on I get the "Confirm Password" screen thrown in my face

A ROM flash should definitely get rid of that, but I'm very surprised that a factory reset doesn't do it.

Like I said I tried flashing original roms (older and newer of KE2), costum roms (villian, litenin etc.), different kernels - the password is still here.

I'm stumped then mate. I've never had a lockscreen password persist from one ROM to another. I think household insurance and a brick may be the easiest way to remove it

Hehe ye I was not exactly exstatic about it either... I've been playing with roms etc. since my 1st android Samsung Galaxy (GT-I7500) and the one thing that was always persistant was "Software saves" - and now this with the SGS2...
I just tried the same on mine - set the password and flashed the official KF3 - got welcomed with the "Confirm Password" screen and just input my password that I set before and bang the phone finished with the software update and booted normally...
Thinking this thread would be better off in the development section in case anyone will have the time to look into where this stuff is stored and make a workaround (perhaps similar like the nv_data one for network unlock).

This is purely a guess and I haven't tried it on SGS2, but you could try flashing a ROM via Odin and ticking the option "Phone EFS clear". Not sure but this could wipe also the EMMC partition where I have heard the screen lock data is stored in. I won't take any responsibility on bricked phones or other problems though...
I only did try this on my wife's SGS and for it it did not do any harm.

Nightravenn said:
Thinking this thread would be better off in the development section in case anyone will have the time to look into where this stuff is stored and make a workaround (perhaps similar like the nv_data one for network unlock).
Click to expand...
Click to collapse
Tut tut matey. It's a question - it's already in the wrong forum

Heh my bad about the placement of the topic
@Pume EFS is actually where the calibration is stored aswell (which is different for every phone/IMEI/RF), but yes I did try it aswell heh, also tried the bootloader update option ticked on - same story still the damn PSD (Password screen of death?).

First you can try to disable the password via adb (in recovery) http://forum.xda-developers.com/showthread.php?t=1110307
If its not the right description you could try to format the data partition in recovery and then flash a new rom. No idea how smart that is on the galaxy s II but on the desire it was perfectly save. Last i believe this is a more common problem and there should be other threads around with solutions.
Sent from my Transformer TF101 using XDA Premium App

Nightravenn said:
Heh my bad about the placement of the topic
@Pume EFS is actually where the calibration is stored (which is different for every phone/IMEI/RF), altho yes I did try it aswell heh, also tried the bootloader update option ticked on - same story still the damn PSD (Password screen of death?).
Click to expand...
Click to collapse
Oh, good to know anyway. Damn I'm never gonna put a password on mine as I tend to forget even my own birthday

You could try that again(flash a rom) without your SIM card and maybe without your MicroSD. Maybe it syncs with data and get the password lock from there.

Are you sure the password isn't a PUK lock? Try booting the phone without a sim. If it works, then the password is restricting your use of the service by locking you out of the phone. To solve this you can do one of two things:
1. Get the Sim replaced
2. Call your provider for an unlock code and GET RID OF IT in the security settings under sim-lock
Hope that helped!

Actually I always flash roms without the SD card and SIM as I've come to realise some .pit's acutally repartition your SD card aswell thus erasing it - cheers for the post tho.
@TheGhost1233
You might be on to something with that actually but now I have another problem... for some reason everytime I want to go to recovery it shows that little yellow box (the usual one before going into recovery) and then back to the dumbass PSD. So I can't get ADB working now at all.

I almost don't want to post this hehe...
But ye found a solution - spammed random passwords (think it was 5 wrong) and then a message appeared, that the SD card will be reset and a full wipe will be done - pressed OK and bang the phone boots normally
In case anyone finds themselves in the same situation. You lose all your data ofcourse but the password is deleted and bang the phone works

I think this is anti-theft protection, at least your info is gonna be deleted if someone steals it

Android 6.0 Marshmallow Full Disk Encryption on Huawei P8 Lite

Before I write a long article I have questions.
Let's say, I want to encrypt my phone. When I hit the button "Encrypt phone" a green Android figure shows up for less than a second and the phone restart the first time showing the Huawei logo for a minute or less. Then the phone restart a second time and asking for the password.
Until this is clear, however is strange because to fast the encryption.
I booting up the phone and go to settings where I change the password I used to encrypt the phone. Restart the phone. Then the phone booting up without asking my password before boot!
Is this normal?
I go again to settings and disable screen lock and set it to NONE. Restart the phone. The phone booting up without asking any password.
This is safe?
My phone is still encrypted?
How I can set up the phone to ask me the password before booting up?
My build number is: ALE-L21C432B574
There is any software to test that the phone is encrypted or not?

AndroidSecurity said:
Before I write a long article I have questions.
Click to expand...
Click to collapse
So far so good. At least better than flaming everyone for security issues that not everyone has...
AndroidSecurity said:
Let's say, I want to encrypt my phone. When I hit the button "Encrypt phone" a green Android figure shows up for less than a second and the phone restart the first time showing the Huawei logo for a minute or less. Then the phone restart a second time and asking for the password.
Until this is clear, however is strange because to fast the encryption.
Click to expand...
Click to collapse
You're right that is indeed strange... Have you tried contacting Huawei to figure out whether B574 has any issues with the dm-crypt in the kernel? I cant check this for you because Huawei hasn't released their Kernel for MM at all.. Usually the encryption process takes more than an hour. At least for me it took that long.
AndroidSecurity said:
I booting up the phone and go to settings where I change the password I used to encrypt the phone. Restart the phone. Then the phone booting up without asking my password before boot!
Is this normal?
Click to expand...
Click to collapse
"On Android 5.1 and above, encryption doesn’t require​ a PIN or password, but it’s highly recommended since not having one would reduce the effectiveness of the encryption." Are you sure you set it up correctly? And was your phone rooted while encrypting? If yes I can tell you it may cause major issues like data loss or weird **** happening.
AndroidSecurity said:
I go again to settings and disable screen lock and set it to NONE. Restart the phone. The phone booting up without asking any password.
This is safe?
Click to expand...
Click to collapse
No! Why on earth would no screen lock be safe??
AndroidSecurity said:
My phone is still encrypted?
Click to expand...
Click to collapse
Probably but since anyone can unlock it, it is basically useless.
AndroidSecurity said:
How I can set up the phone to ask me the password before booting up?
Click to expand...
Click to collapse
System Settings > Security > Screen Lock > Pin or Pattern or Whatever you got > Secure Start Up: Yes
That was easy wasn't​ it?
AndroidSecurity said:
There is any software to test that the phone is encrypted or not?
Click to expand...
Click to collapse
If you are unsure about encryption try to plug in your phone to your PC without unlocking it first. Can you read the Data? > Not encrypted.

Decrypting loop after OTA update

Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...

jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs

shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.

jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs

shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...

Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.

benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs

benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.

To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.

benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?

I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.

Does anyone have OEM Unlock on the SM-J530G?

I've been trying for a long time to get OEM unlock with the Samsung Galaxy J5 Pro SM-J530 G variant. I've seen people unlocking the BL in the J730G, same exynos chip.
Here is what I have tried so far:
All date/time tricks
Factory reset
Flash Stock ROM
Waited 7 days
My last attempt made me give up and ask for help here... I completely flashed the most recent stock rom, wiped everything using the CSC file not the CSC-HOME, I did the start setup logging into samsung account and google account, after completing the start setup I inserted the SIM card otherwise that stupid start setup would consume 4G costing me $$$.
Waited for 168 hours with the device always on, and still no OEM UNLOCK, I mean what else can I do... there's almost nothing about this problem with this device here on XDA... I'm hoping someone with a SM-J530G and that had OEM Unlock could tell me what was the process to enable this option. Or what are my options here? Thx
And by the way, I've seen something called Miracle Box, but I dont want to use it since it does not look very legal, I think its meant for FRP bypass. I'm just an android user trying to root my personal device e.e

I'm having the same problem, I'm tired of this, never buying Samsung again. I tried all the things I searched on the internet for hours and nothing works, I do not want to wait 7 days, if you find a method of bypassing that actually works, please do tell me, I will do the same if I find one.
I'm so pissed.

I have good news for you my friend, and for everyone that is reading this. I tried many and more times the same procedure changing small things. I will try to write it out as best as I can so I can help some fellow buddies who've got the same problem.
1 - (As I had already everything backed up and got nothing to lose) Factory Format the device (I did it from the bootloader), hell, I even also cleared cache just for god's sake.
2 - Proceed to initiate Android, DON'T sign-in to any account (nor Samsung nor Google), don't change the date during installation, finish set-up.
3 - DON'T enable Developer's Mode yet. Change the date, I've set it for a month back just to be damn sure (disable automatic date-set). Now go to the Software Updates tab and disable auto-updates and manually check for updates, once done, re-boot.
4 - Once rebooted enable auto-date (that should correct the old date and replace it with the actual one) and re-do the manual check.
5 - Re-boot and enable Developer's Mode and hopefully, for the love of Ragnar Lothbrok, OEM Unlock should be there. I hope it is for all of you.
Hope it helped, good luck buddy/buddies!

Franz Enz said:
I have good news for you my friend, and for everyone that is reading this. I tried many and more times the same procedure changing small things. I will try to write it out as best as I can so I can help some fellow buddies who've got the same problem.
1 - (As I had already everything backed up and got nothing to lose) Factory Format the device (I did it from the bootloader), hell, I even also cleared cache just for god's sake.
2 - Proceed to initiate Android, DON'T sign-in to any account (nor Samsung nor Google), don't change the date during installation, finish set-up.
3 - DON'T enable Developer's Mode yet. Change the date, I've set it for a month back just to be damn sure (disable automatic date-set). Now go to the Software Updates tab and disable auto-updates and manually check for updates, once done, re-boot.
4 - Once rebooted enable auto-date (that should correct the old date and replace it with the actual one) and re-do the manual check.
5 - Re-boot and enable Developer's Mode and hopefully, for the love of Ragnar Lothbrok, OEM Unlock should be there. I hope it is for all of you.
Hope it helped, good luck buddy/buddies!
Click to expand...
Click to collapse
That is awesome! I'm going to try it tomorrow, I've been using the device doing my third 168 hours. If it fails again I will repeat everything like you did.
Thank you!!
Sent from my SM-J530G using XDA Labs

Another 168 hours wasted and I followed the trick above, it does not work it was patched with the august 2018 security patch, my device is running with the november 2018 security patch.
My frustration is beyond what I expected to experience with this device... I guess most people were able to activate this thing except me >.<

Enlighten me
When you keep it for 168 hours does the WiFi have to be on or is that not necessary

Sameer521 said:
When you keep it for 168 hours does the WiFi have to be on or is that not necessary
Click to expand...
Click to collapse
I tested with wifi always on and logged to google and samsung account so it could sync whatever it had to sync, still no success. I have no idea on how to meet the requirements to unlock the BL on this phone

scroll-lock said:
I tested with wifi always on and logged to google and samsung account so it could sync whatever it had to sync, still no success. I have no idea on how to meet the requirements to unlock the BL on this phone
Click to expand...
Click to collapse
Is their any other method for 2019.am at my wits end

OK I tried something and it worked to unlock the oem.
Have a Samsung account,then go to find my mobile website and press unlock.it did the trick for me.hipw it helps you as well

Firstly, i use miracle box and then i use samsung tools pro to "reboot" my device because when you unlock the bootloader there is a fail on the room.
here you have a video which could help you.

T580 - Suddently got FRP Lock after over 6 months of use. Any way to recover?

Hi Guys,
I have a couple T580 tablets for my kids, and we had just gotten a new one for Christmas that I set up. I THOUGHT I had done everything correctly, but the new tablet is giving me the FRP Lock suddenly.
Any idea how that could happen? Is there any way to recover the tablet or do I have to do a original rom flash?
Thanks

sjbayer3 said:
Hi Guys,
I have a couple T580 tablets for my kids, and we had just gotten a new one for Christmas that I set up. I THOUGHT I had done everything correctly, but the new tablet is giving me the FRP Lock suddenly.
Any idea how that could happen? Is there any way to recover the tablet or do I have to do a original rom flash?
Thanks
Click to expand...
Click to collapse
Somethings not right. You don't "suddenly get an FRP lock". An FRP lock occurs only after you "factory reset" the tablet and don't know the google account login. And that is only if you hadn't enabled "OEM" in "Developer options". What makes you think it is the "FRP lock"? And if it is locked, flashing a ROM with Odin won't help. You'll still need the google account info to access the tablet.

lewmur said:
Somethings not right. You don't "suddenly get an FRP lock". An FRP lock occurs only after you "factory reset" the tablet and don't know the google account login. And that is only if you hadn't enabled "OEM" in "Developer options". What makes you think it is the "FRP lock"? And if it is locked, flashing a ROM with Odin won't help. You'll still need the google account info to access the tablet.
Click to expand...
Click to collapse
Because this is what it says when I start the tablet...
https://i.imgur.com/u8PXyBD.png
I have a google account, and info, for the tablet. Not sure how I put it in when the boot process is blocked though...
My only thought is something happened with Magisk?

sjbayer3 said:
Because this is what it says when I start the tablet...
https://i.imgur.com/u8PXyBD.png
I have a google account, and info, for the tablet. Not sure how I put it in when the boot process is blocked though...
My only thought is something happened with Magisk?
Click to expand...
Click to collapse
Again, unless something has changed, which I doubt, that is not the way the FRP lock works. First of all, you said nothing about having a custom ROM installed. But even if you did, the FRP lock would NOT prevent the tablet from booting. It would merely ask for your google account info when it did boot. Have you tried booting into recovery and performing a factory reset?
edit: Let me explain what FRP means. In early versions of Android, if your phone/tablet were lost or stolen, anyone could bypass your "screen lock" simply by booting into recovery mode and perfoming a Factory Reset. So Google came up with the Factory Reset Prevention lock. So if someone tried to use the Factory Reset, the lock would demand the google account login and password to access the tablet. So if you wanted to sell your tablet, you either had to enable "Developer options" and then use that to "Enable OEM", prior to reseting the tablet or put in a google account whose info you could pass to the buyer, remove your real account, and then reset.
In any case, the tablet did NOT show the message you are getting. I've bought several T580s on eBay that WERE locked, and none of them gave that message. A locked tablet would still let you install stock ROMs with Odin, but the tablet would still ask for the google account info. But the way around that can be found in this forum.

lewmur said:
First of all, you said nothing about having a custom ROM installed.
Click to expand...
Click to collapse
I dont think I do, its stock rom, but Magisk is installed which I believe is not a custom rom.
lewmur said:
Have you tried booting into recovery and performing a factory reset? .
Click to expand...
Click to collapse
When I turn on the power, the screen comes on, and then says "Custom Binary blocked by FRP Lock" then the screen turns off. I have not tried a factory reset because I was hoping to find a solution without losing everything before I did something that could not be undone.
The only thing left is, I know samsung will (if detected) attempt to remove software. I wonder if it somehow tried to reset automatically and in so doing caused this.

A factory reset does not help in your case.
First option is: contact your person, who sell the phone. Because he must unlock this one in his Google settings.
The question is: how many times a wrong oe no account was insert, that the device doesn't start up till the possibility to insert the correct account.

sjbayer3 said:
I dont think I do, its stock rom, but Magisk is installed which I believe is not a custom rom.
When I turn on the power, the screen comes on, and then says "Custom Binary blocked by FRP Lock" then the screen turns off. I have not tried a factory reset because I was hoping to find a solution without losing everything before I did something that could not be undone.
The only thing left is, I know samsung will (if detected) attempt to remove software. I wonder if it somehow tried to reset automatically and in so doing caused this.
Click to expand...
Click to collapse
You don't lose everything with a Factory Reset and what you do lose should be easily recovered from your google account backup. And nothing else could be done that wouldn't also cause a reset.

mad0701 said:
A factory reset does not help in your case.
First option is: contact your person, who sell the phone. Because he must unlock this one in his Google settings.
The question is: how many times a wrong oe no account was insert, that the device doesn't start up till the possibility to insert the correct account.
Click to expand...
Click to collapse
No one sold me this phone, I bought it new. There is no unlock option. The phone doesnt event start booting, the screen turns on says the FRP lock, then turns off.

Ab FRP Lock said, that the phone is looked via a Google account.
In a normal case, you can only unlock the device, if you insert the correct Account with password.
I don't know.. maybe you have insert 3 time wrong credentials... why the device give your not the possibility to unlock the device.
Try an complete wipe / factory reset out of the recovery menu, so that the OS can start.
The lock isn't away, but maybe you have the possibility to insert the correct data.

In Download Mode here is what I see:
https://i.imgur.com/5eZ2YmH.png

Alright I just flashed the latest rom and that fixed it.
I now know a little bit about what is going on. When I got the tablet, I set it up for me. Then I discovered googles "family link" so I set it up again for my daughter.
Child accounts have FRP protection. I dont know what triggered it, but somehow it activated recently when it discovered magisk which I had installed some time back.
Now I am super irritated and over Family Link...