Hey all!
Is there any way to implement anti-theft tech on the S5 that is resistant to a factory reset? Many apps are available to track a phone after it is stolen. However, all the thief needs to do is pull the battery to shut it off, pull, the sim card, power into factory reset and poof it's ready to be re-sold. Cerberus offers the best protection I've seen so far as it will survive a factory wipe if the phone has been rooted and a custom ROM loaded. However, even that can be worked around by flashing a custom ROM (which the thief may not know how to do).
Any suggestions? How do you guys handle anti-theft? Had 2 galaxy phones stolen over the past year so I'm looking for any and all advice here. Thanks in advance!
User0919
Enable "Reactivation Lock" in security settings, factory resetting the device forces the person to log into the Google account that was logged into when the lock was enabled, or they have no access to the device, even after resetting it
*Detection* said:
Enable "Reactivation Lock" in security settings, factory resetting the device forces the person to log into the Google account that was logged into when the lock was enabled, or they have no access to the device, even after resetting it
Click to expand...
Click to collapse
Re-activation lock only works when knox is 0x0 but that too can be bypassed by installing custom rom so...
I don't think there is the way. You have to pray that whoever will steal it is not an advanced user.
Reactivation lock does block custom recoveries as they use a custom binary. And if the user tries to flash through recovery they would need the user's google ID ( to unlock the reactivation lock). Though on other sources, it has come apparent that reactivation lock can be tricked (even in the latest lollipop bulid). As a extra measure you should password protect TWRP and encrypt ypur device to prevent any form of identity theft.
Yes it's very easy to break the user's lock screen since the information (cant remember either salt or hash, look up a Android Forensics blog) is stored in a database - settings.db and gesture.key . Someone could easily just delete the field for password.
http://resources.infosecinstitute.com/android-forensics/
there is no way or point in protecting phone to be stolen... if thief cant use or sell stolen phone will he give it back? no.. he will either crack it if this is possible or sell it for parts (screen, battery, casing).
Only reason to encrypt or lock a device is to protect personal data like photos.
My Samsung S5 (SM-G900F, 4.4) device has a fingerprint scanner to unlock the screen. It was working perfectly, but now it only asks for the alternative password, but I forgot it. I tried on the Google webpage to lock my phone, I hoped that the password given there will be overwrite the alternative password on the phone, but it said, that it found the phone already locked, so no need to use the password. I don't want to do a factory reset if it possible, how could I get the fingerprint scanner to be an option again, or somehow unlock the screen and use my phone?
This happened to me today in the morning on my S5 mini with stock OS. At first I typed in the correct alternative password, but it was not recognized. Latter I successfully (?) changed password with "Lock" option on Android Device Manager, and it didn't help either...
At the end I did a factory reset and lost all my data
Is this a common bug? Should we report it somewhere or something?
After too many failed fingerprint attempts, it will only ask for the password
Maybe someone else has been trying to access your phone
Factory reset to regain access if you don't know your alternative password (Probably a good idea to write that down)
*Detection* said:
After too many failed fingerprint attempts, it will only ask for the password
Maybe someone else has been trying to access your phone
Factory reset to regain access if you don't know your alternative password (Probably a good idea to write that down)
Click to expand...
Click to collapse
Yes, you are correct. I tested this again, and I think that, in the morning, I really used wrong password . And the first time I didn't notice the displayed info, about password already being set, on Android Device Manager site, when I tried to change the password.
Thanks for the replay
So I upgraded my G900V to Marshmallow and then did a factory reset after I verified it worked because I wanted to start fresh, but now the setup screen says "abnormal factory reset" and is asking for my Samsung Account credentials. When I try to sign in it says "processing failed" every time and won't go past the page...
What I have tried (all have failed):
1. resetting my Samsung Account password (twice now...)
2. a second factory reset
3. using find my mobile to unlock it
4. flashing the stock kitkat firmware (fail with odin)
5. flashing a custom recovery (fail with odin)
6. using the OTG cable method (nothing displays on the screen...)
7. using the sidesync method (nothing displays on the screen...)
8. Called Samsung Support 3 times:
-regular support # - told to call the accounts # during business hours
- accounts # - told that they would have it remotely unlocked by the next morning (of course they don't follow through)
-accounts # - given the runaround treatment for 1.5 hours until a supervisor in the returns department tells me there is nothing more they can do and don't have the capability to service it (apparently it's still under warranty even (not that it matters.....))
So does anyone know a work around? I would really like to get my phone functional again.
The phone is not stolen! If anyone wants proof I am happy to supply multiple clear photos of the phone itself and the imei number, which is clean.
I managed to bypassed it, created samsung account, phone works but i can`t set custom recovery, samsung support doesn`t help either. I have g900p.
exeg said:
I managed to bypassed it, created samsung account, phone works but i can`t set custom recovery, samsung support doesn`t help either. I have g900p.
Click to expand...
Click to collapse
Please tell me how I am willing to send a pic on the imei to prove the phone isn't stolen....
RipCityBassWorks said:
Please tell me how I am willing to send a pic on the imei to prove the phone isn't stolen....
Click to expand...
Click to collapse
In my case, before samsung account request , sprint asks to activate account, i clicked yes, then I entered epst settings, after that turned on debug and with the help of adb entered command to settings
exeg said:
In my case, before samsung account request , sprint asks to activate account, i clicked yes, then I entered epst settings, after that turned on debug and with the help of adb entered command to settings
Click to expand...
Click to collapse
Unfortunately mine doesn't have any option close to that. Lucky for me though I think Samsung came around, I tried submitting a repair request for a second time and this time I was approved and it will be covered under warranty.
exeg said:
In my case, before samsung account request , sprint asks to activate account, i clicked yes, then I entered epst settings, after that turned on debug and with the help of adb entered command to settings
Click to expand...
Click to collapse
I'm able to use the downgrade/OTG method to get access to the phone, but then I am in a situation where I can't turn off the Reactivation Lock, it just stays stuck on. What were the ADB commands that you used to turn it off? Thanks for your help.
fitzonthemark said:
I'm able to use the downgrade/OTG method to get access to the phone, but then I am in a situation where I can't turn off the Reactivation Lock, it just stays stuck on. What were the ADB commands that you used to turn it off? Thanks for your help.
Click to expand...
Click to collapse
I can`t turn it off. I even managed to create samsung account but after I enter password nothing happens
UPDATE:
so Samsung not only fixed the problem, but they also restored the phone to like new condition (it was in very beat up but no cracks condition previously) so I really have to give props to them for their amazing repair team. It took about a week total if anyone is wondering.
I have a new method to remove reactivation lock it is confirmed working. It works on Samsung eMMC and Toshiba eMMC.
http://forum.xda-developers.com/ver...ivation-lock-off-finally-stuck-t3433342/page1
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
As advised flash the stock firmware. DATA won't be affected.
ashyx said:
As advised flash the stock firmware. DATA won't be affected.
Click to expand...
Click to collapse
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
ScottHW said:
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
Click to expand...
Click to collapse
Searching for that question directly, it seems like flashing a ROM (e.g. stock firmware) will not directly erase user data; downloads, photos in DCIM, etc.
But, sounds like any user-installed apps will be erased (so any internally stored data would be lost).
And, data stored in system apps would be lost, too; e.g. tabs that were open in Chrome.
There's no way around the FRP lock, eh?
Here is Samsung's statement about FRP (Factory Reset Protection)
It describes the Google account "protection" features, but doesn't really describe how FRP lock leads to bootloops.
https://www.samsung.com/us/support/frp/
Factory Reset Protection (FRP) Feature
What is Device Protection, or Factory Reset Protection (FRP)?
Android devices provide built-in security features you can use to protect your device and information, including screen locks and data encryption. Data protection, or Factory Reset Protection (FRP), is a security feature on Android devices with Lollipop 5.1 and higher.
FRP is automatically activated when you set up a Google Account on your device. Once FRP is activated, it prevents use of a device after a factory data reset, until you log in using a Google username and password previously set up on the device.
How does FRP work?
When you perform a Factory Data Reset, all settings are returned to the factory default settings. All data is erased, including files and downloaded apps.
If you have a Google Account set up on the device, FRP is active. This means that after the reset, you'll be required to log in to the Google Account using the username and password. If you have multiple Google Accounts set up on the device, you can log in using any of the accounts.
If an unauthorized person tries to reset the device by another method, the device would still require log-in using the Google username and password. This means that if your device is lost or stolen, another person would not be able to reset it and use it.
What do I need to know about FRP?
If you want to reset your device to factory defaults, make sure you know your Google Account and password, because you'll need to log in at the end of the reset.
If you want to reset your device to factory defaults, but don't remember your Google username and/or password, you can do one of these:
Check your devices Account settings for your account name, and reset your password via the device or at www.google.com.
It can take 24 hours for the password reset to sync with all devices registered to the account.
Remove the account before you reset the device.
If you already reset your device, but don't remember your Google username and/or password, the device can't be used. In that case, you can do one of these:
If you know your Google username but can't remember the password, you can reset your password on the device, or at www.google.com. It can take up to 24 hours for a new password to sync with all registered devices. After 24 hours, you can try logging in to your phone with the new password.
If you have multiple Google Accounts, and you can't remember which Google Account you set up on your device, visit https://www.google.com/android/devicemanager.
Log in with your Google username and password and check the list of devices registered to the account. If you don't see the device listed on the account, it means the device is registered to a different account. Use the same process to check for devices linked to your other Google Accounts. When you find the registered account, use it to log in to your device.
If you can't remember any of your Google Account information, you can send your device, along with proof of purchase, to an authorized Samsung Service Center. Samsung has special tools to reset the phone to factory defaults with no protection enabled.
Click to expand...
Click to collapse
Looking for a Samsung Authorized Support Center, apparently there are ZERO listed around Omaha, NE.
http://support-us.samsung.com/cyber/locator/asc_locator.jsp
There must be ASC's somewhere; I'm hesitant to mail the phone away because I think the tech will just wipe it. The whole point is to maintain the data :-/
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
ScottHW said:
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
Click to expand...
Click to collapse
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
ashyx said:
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
Click to expand...
Click to collapse
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
ScottHW said:
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
Click to expand...
Click to collapse
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
ScottHW said:
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
Click to expand...
Click to collapse
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
n00b mistake
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Sh!t, sorry, boot.ing /= bootloader. Rookie mistake. #StillLearning
OK, so boot.img and recovery.img should both be contained within the AP component of stock firmware.
I can just flash those two, can't I?
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Is there any non-GUI way to toggle the OEM UNLOCK?
Bootloader? Download mode? Recovery? Fastboot? ADB?
I assume not, since that might be a "security" risk. And also, if there were, problems like this would have solutions posted mentioning how to do that.
Sh!!!!!!!t... I was thinking I would have screenshots of the exact build that's loaded on my phone. That way I can find the right stock firmware.
Seems those screenshots are still in the phone, didn't get moved to external memory
All I know for sure is it's Andorid 5.1.1, but that probably isn't specific enough to get the exact right boot and recovery images.
I intend to flash the boot.img and recovery.img to my phone. Hopefully, this will avoid any data loss, while clearing the FRP lock bootloop.
I got the stock firmware for Android 5.1.1 for my Galaxy A3 (2016) (SM-A310M) here:
https://www.sammobile.com/firmwares/galaxy-a3-/SM-A310M/TTT/download/A310MUBU2APE2/73991/
This set of instructions says to extract the .img file(s) to flash, then just .tar them up using 7zip, and flash it as AP in ODIN.
http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/
But... this one says to use Unified Android Toolkit, option ‘8’ (Create an Odin flashable tar), and then flash with ODIN.
https://skipsoft.net/flashing-a-single-partition-i-e-system/
Fortunately, I have a Galaxy A3 (2017) (SM-A320Y), which I was just about to upgrade to for my daily driver. It's blank, running Android 7.0, so it means I can test this process, see if data is preserved, with almost no risk to actual data. Got that firmware here:
https://www.sammobile.com/firmwares/SM-A320Y/COO/download/A320YDXU1BQH2/189605/
Ironically... I don't yet have a great method to intentionally trip the FRP lock bootloop
I think rooting and then unchecking OEM Unlock should do it (that's what wrecked my A310M)
FRP lock - Usb does not recognize
Hi, Everyone!
Sorry my english.
My problem is the same as yours.
however, after this frp lock message appeared, my phone goes into download mode, but the pc does not recognize any more. what can i do to get flash from the rom stock and solve the frp lock problem.
Help me, please!
Thank you all
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
FRP Custom binary Lock
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Blackion said:
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Click to expand...
Click to collapse
If they're both stock based firmware then you can just flash the stock S7 firmware. Data should remain untouched.
Hi
I am just stuck with the same problem. I have downloaded the latest Stock ROM. But unsure which options to select in ODIN and what files to select.
I presume only select AP. Also, hope I will not lose any data.
Please help me out.
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...