Database Users

S7 Edge - Custom Binary block by FRP Lock

Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!

Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk

Thanks for the reply,
Sorry but I'm new. How do i do that?

pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold

Model : SM-G935FD
Country : Singapore

frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?

AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.

I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz

https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.

djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.

I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery

Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!

Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.

Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.

maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?

Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.

anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?

There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app

Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone

FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.

[A3 2016] Recover data from FRP Lock bootloop?

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 device’s 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.

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB

(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!

Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?

Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.

JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.

https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965

JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.

Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.

https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.

I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.

zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.

JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously

Good luck.

Deleted

Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.

JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...

sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.

sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you

Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082

Bricked Phone - Failed to mount system error & FRP lock.

Hi all 0/
I'm creating this post because well I have a bricked phone (I know, another bricked phone thread) and am asking if anybody can help or point me in the directions of help.
P
The Problem
So my phone failed to install the latest security update that was released in September; just gave me the update failed error on reboot. I ignored this for a month as it didn't bother me but it started to get progressively more buggy, random crashes then random restarts then google play services just stopped working. This point I looked into it and the internet told me to use smartswitch to apply the update (which I assumed to be the problem at the time). Smartswitch couldn't update it which through it into emergency recovery mode. Smartswitch was then blocked by FRP lock when I tried to use emergency recovery mode.
I then tried by use Odin to flash stock firmware, which FRP lock blocked. Now i'm stuck as I can't flash anything with odin or use smartswitch so am stuck with either download mode of emergency recovery page.
I have extracted and reflashed all the sys.img flash expect system which has allowed me to boot to recovery but have the error
DM verity failed
E/ failed to mount system (invalid argument)
All the fixes for dm verity failed system, frp lock etc don't work as i think i have a combination of problems
Neither have I found a post that describes this problem anywhere
Thank you very much for reading

If you can boot the phone do you know the google email and password to remove the fpr?

godkingofcanada said:
If you can boot the phone do you know the google email and password to remove the fpr?
Click to expand...
Click to collapse
Yes I do, which is the most annoying part!

Skyscripter said:
Yes I do, which is the most annoying part!
Click to expand...
Click to collapse
Don't use Odin, use the actual Samsung app smart switch and factory restore/emergency mode restore option.

godkingofcanada said:
Don't use Odin, use the actual Samsung app smart switch and factory restore/emergency mode restore option.
Click to expand...
Click to collapse
That's what I originally tired and it gets blocked by the frp lock

Skyscripter said:
That's what I originally tired and it gets blocked by the frp lock
Click to expand...
Click to collapse
The fpr lock isn't supposed to block you from installing official factory firmware. But it has to be the exact firmware. It should install and then ask for your gmail

godkingofcanada said:
The fpr lock isn't supposed to block you from installing official factory firmware. But it has to be the exact firmware. It should install and then ask for your gmail
Click to expand...
Click to collapse
That's what I thought, but when I've tried to use smart switch it blocks me, and every version of firmware I've found with odin it blocks. How can I find out which firmware my phone was on before it bricked its self? or do you think its a case of trying many?
assuming smartswitch is unable to find the firmware that i need is there any way of telling it which version to flash?

Skyscripter said:
That's what I thought, but when I've tried to use smart switch it blocks me, and every version of firmware I've found with odin it blocks. How can I find out which firmware my phone was on before it bricked its self? or do you think its a case of trying many?
assuming smartswitch is unable to find the firmware that i need is there any way of telling it which version to flash?
Click to expand...
Click to collapse
Smartswitch can't flash it because whatever crapped out changed the device ID or some info it looks to for authentication. I had that happen once. After a fw flash my phone changed from SM-G928W8 to G928F and smart switch wouldn't touch it. So what I had to do was find the exact match, you need to know what carrier your phone came from to get the model for firmware, like t mobile or Verizon, and then get that version, I think nougat or mm would work but our device shipped with mm. Odin will work but it the fw has to match the device. Then once it boots your gmail info is needed.

godkingofcanada said:
Smartswitch can't flash it because whatever crapped out changed the device ID or some info it looks to for authentication. I had that happen once. After a fw flash my phone changed from SM-G928W8 to G928F and smart switch wouldn't touch it. So what I had to do was find the exact match, you need to know what carrier your phone came from to get the model for firmware, like t mobile or Verizon, and then get that version, I think nougat or mm would work but our device shipped with mm. Odin will work but it the fw has to match the device. Then once it boots your gmail info is needed.
Click to expand...
Click to collapse
Okay I think I understand, so i need the exact firmware it was on before it crapped out, otherwise it will think i'm trying to flash new firmware an frp lock stops it right? My phone came unlocked in the UK., will i just have to try many different versions in hope one works?
Noob question, what does fw flash stand for?
Thanks so much for answering my questions : )

Sm-t280 frp locked binary

So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help

Why don't you try a backup in TWRP?

Reinstalling the stock firmware with Odin won't wipe the device.

slop_me said:
So long story short I was intoxicated and for some reason disabled OEM in debugging then sometime later I restarted my tablet to get the frp binary locked. It has a custom rom with twrp I absolutely need the data off of this tablet and the only way I see is to reinstall the default os through Odin but that wipes the device I need a method to get the data off of the tablet or a method to bypass frp entirely it would be mighty appreciated if I could have some help
Click to expand...
Click to collapse
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock.. Download Mode is accessable but won't initialize when trying to flash stock firmware. Binary 4 FRP Unlock file was accepted and flashed in by Odin3. Stock firmware installs afterwards.
Version 2. Device is stuck in bootloop. "Custom Binaries Blocked by FRP Lock" appears on Logo screen. Recovery and Download Modes are so far, useless. Binary 4 FRP Unlock used, no positive results. Binary U 4 used. Positive result. Stock firmware flashed in afterwards.
Version 3. "Custom Binaries Blocked by FRP Lock" appears on Download Mode which either stalls right after or fails to initialize. Binary 4 FRP Unlock and Binary U 4 yeild no positive results. (This ones on it's way to me).
Version 4. "Custom Binaries Blocked by FRP Lock appears on Recovery Mode. Download Mode useless. I'm currently following this one.
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock" which I couldn't yet find.

Casper Young said:
It's difficult to say if you can keep your data. The binary FRP lock is quite different that the average FRP lock that's associated with the Google sign in. Usually whenever you trip the binary lock it's because some firmware was installed such as a Root or a ROM that was flawed or invalid. It's an overstacking of binaries and therefore you get a "Custom Binaries Blocked by FRP Lock" notification. I've had this problem on another varient of the Tab A, the Galaxy Tab A6 SM-T580. I have found about four diferent variations of this. You may not have turned off OEM because in Binary lock it will act like you have. Possible reason to think that is the way it acts in Download Mode where you can't seem to flash anything especially the official firmware. Sound familiar?
Version 1. If you try to go to Recovery you get redirected to a screen similar to the Download Mode. In the upper left are red lettered "Custom Binaries Blocked by FRP Lock..
Solution: I don't know if the one I have will work, they may be device specific. Research for a "SM-T280 Binary 4 FRP Unlock"
But I couldn't find one.
Here's my post, it may help.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.

ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.

Casper Young said:
I hate to argue with you but that wasn't so easy with mine. While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. Trial and error followed. The solve was first I had to flash in the Binary FRP Unlock and then I could flash in the firmware. With another device the owner tried the Binary Frp Unlock which didn't fix it. Later he flashed in the U4 Binary and that worked for him. I passed the info along to some others in the same predicament and it helped them. So I don't know what to tell you but what you're stating is not always applicable.
Click to expand...
Click to collapse
Trust me, I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device.
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset.
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware.
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.

ashyx said:
Trust me, [not happening!]I have 3 of these devices. I've bricked them, frp locked them every possible way during development for this device. [Well, umm. No, you haven't. And take a wild guess how many devices I have, like that matters.]
The T580 is a different device and may be more difficult to bypass if and only if FRP has kicked in because of a device reset. [Everytime you turn off the device it resets.]
However for EVERY Samsung device that has simply had non stock software installed the only fix that's required is to install the stock firmware. [You obviously have difficulties comprehending that I said otherwise]
This is the case on all the Samsung devices I own and I have quite a few from lollipop to Pie.
Click to expand...
Click to collapse
Wow, you're on a roll ain't ya? Hey ASHYX, dont misjudge me because of my stats you see here. Over a decade ago I was stacking ROMs into my HTC-G1. 3 decades ago I was an Electrical Engineer and Sonar Operator in the Navy. Let me tell you point blank, you're mistaken! Normally you would think you can just flash in stock OTA firmware into the device via Odin3 and you get to return to normal. Well that wasn't the solve for this. This was a new one to me also. If you think you're so right on what you say I'll be more than happy to point you in the direction of some XDA visitors, two of which are still Binary FRP locked. You can try telling them what you just told me and they'll probably call you a blooming idiot. No offense but you could try reading it properly which might help.
I said, [QOUTE] " While in Binary FRP lock I, along with a few others that have the SM-T580 or the SM-T585 couldn't use Download Mode to flash in the official stock firmware. [END QOUTE]
Take my word for it, the method you stated was already tried AND DID NOT WORK!
If you want to insist you're all that, here ya go, these people need your expertise in development
https://forum.xda-developers.com/ga...frp-locked-t3772512/post80420061#post80420061

Data loss when flashing stock firmware.
ashyx said:
Reinstalling the stock firmware with Odin won't wipe the device.
Click to expand...
Click to collapse
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.

Casper Young said:
That depends on which stock firmware you're using. Typically what you get OTA (over the air) is the same as the 4File Official Stock Firmware. These are the 4 files that go into each section when using Odin3 to flash firmware. BL is for the Bootloader which controls security, start-up and recovery. AP is Android Partitioning, CP is Cellular Processor. Now let's talk about the CSC. file. The 4File contains two CSC files, one is listed as HOME CSC. If you flash the CSC file you will lose your App data. If you flash the HOME CSC you do not lose your App data.
Click to expand...
Click to collapse
ashyx said:
Nothing needs to be done except install the stock firmware.
The device hasn't been reset so no need for any kind of bypass.
FRP has kicked in purely because unsigned software is installed.
Replace the unsigned software with stock and it'll boot just fine. Data fully intact.
Click to expand...
Click to collapse
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3

slop_me said:
Thank you for confirming I won't loss any data upon installing the original ROM I did just have a custom ROM installed I was super concerned that I would lose all the data upon installing the original ROM thank you so much <3
Click to expand...
Click to collapse
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.

ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Yeah it was just stock lollipop with a root. Will that cause an issue or am I good to continue?

ashyx said:
Depends on which custom rom you had installed? If it's stock based on lollipop then you should be fine. If its lineage then it may not boot without a data wipe.
Click to expand...
Click to collapse
Props to you thanks for the knowledge it worked flawlessly I mean kinda half way through it did say erasing and I kinda **** the bed and got scared because I really needed the data off of there but my man you are right just flashing stock ROM worked flawlessly everywhere online says it will wipe the device but it didn't. Thank you so much for your fantastic help <3