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.

Stuck on bootloop with dm-verity fail and FRP lock

This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!

Use the original usb cable and use Smartswitch recovery, on the back is your serial number you need. And then keep on trying in Smartswitch, it took me a while but it worked and could restore my S6 to stock. And fixed Knox and the FRP lock. And I also tried everything but Smartswitch recovery saved my phone.
Sent from my SM-G928F using XDA-Developers mobile app

SOLVED
Hello, I after countless attempts with firmware that seemed to stock it did not work I SOLVED downloading the firmware directly from the Samsung server using "SAMFIRM" and then flash it with ODIN.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647

CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help

Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.

vooks said:
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
Click to expand...
Click to collapse
nazreen nasaruddin said:
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Click to expand...
Click to collapse
Here's the thing. I had a guy help me fix the FRP problem. And even he had some trouble doing so. And this was done last year, so I only kind of remember how he helped fixed it and I can't guarantee your guys' issue will be fixed if you follow my steps. And you guys may have to know the email and password associated with the phone. I took care of the dm-verity issue on my own afterwards.
Again, I THINK these steps may work, so please don't get mad if these steps don't work. if you guys can, try to flash TWRP or a custom kernel (via ODIN). I know you guys may be having the same problem, but try it out first. If you can't, try finding a combination file for your device (yes, combination file. On Google, search for "[model number] combination file" and download it). Afterwards, flash it to your phone via ODIN. This will allow the phone to boot up, but it's functionality will be very limited. Now, I think this is where you'll be able to login to Google in the settings and the FRP problem will be fixed, IIRC. If you can't login or don't have the details, there's not really much more I can help out with since I believe this is what fixed my problem (really fuzzy memory, sorry). Try rebooting and flashing TWRP again. The combination file itself may have fixed the issue.
If the above fixed the frp problem, GREAT! You should now be able to flash TWRP via ODIN. When you flash TWRP, the dm-verity problem should be fixed, as well. But now your phone needs a ROM and custom kernel. So now find the ones you want. Your phone should be working now!
If for whatever reason your phone still won't work, let me know. I may have another solution.

CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.

godkingofcanada said:
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
Click to expand...
Click to collapse
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.

CrazyTechnoBoy said:
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
Click to expand...
Click to collapse
you make me calm, cause i think combination file will save my phone which also i encountering the same like what you encountered before. and now i've read this post that you solved by flashing the combination file. i'm still waiting for my combination file cause i have binary 5 official rom while the combination files that i found is binary 4.
thanks!

Samsung FRP Bypass

Hi, I'm a total noob on this but I don't know where to start to looking for an answer.
My girlfriend went on vacation (from Chile) to the united states, her mother gave her a cell phone (her cell phone at that moment) an almost new Samsung Galaxy S7 Edge (SM-G935P) from the Sprint Network.
Before returning to Chile the cell phone was unlocked (or so they said at Spring), so here in Chile she put her local carrier SIM but the cell phone never recognized the Sim Card.
So she hard reset the cell phone. Everything went well until he had to enter the original Gmail account for the cell phone. Her mother did not remember the password so after som trial and error, they manged to reset the Google Account. But now when I try to enter de Gmail and password give me this error: Unable to sign in device due to a recent password change. try again in 24 hours, I have waited more than 24 hours and still can't activate the account.
The cell phone is still showing at her known devices in her mother's Gmail account, and the password is correct but I can't by pass the Gmail Activation, I was reading that I can downgrade to a firmware that allowed me to by pass the Samsung FRP but I don't know wich firmware I can use.
Can someone plase guide me how can I activate this cell phone.
Thank you!

edit: You were right I apologize.
If you want to get your password then whoever knows the best information will need to tell google over the phone what that information was when initially set up...birthdays, time of creation,etc-when they ask and %100 will ask. If she/you don't know it..you may never get it back... but calling their --> Customer Support <-- is your best option.

For s7 edge Android 7.0
So I found a way to bypass Google frp on Android 7.0 for the s7 edge and couple other model, it's an old way but modified. First enter into the Google account login screen where it says verify your account. All you do is simply over load it with characters. Tyler a bunch misc letters and number until you have a long good string then begine select all copy paste do this until your phone seem like it going to freeze up. I did it until it took about 2-5 mins to go through. Doing this will send you to a screen says error something went wrong. Hit enternor continue and if you notice this time when it goes back to verify your account the screen should have a black background at the top where's your notifacatioons are . Repeat 2-3-4 times overloading it and getting the error message I'm not sure exactly how many time think it suffers a on phone and Android build I just know once isn't enough to do it so do it a fewbtime it'll take awhile to get the first error but after that you should have the character line copies and ready to paste. After a couple time hit back arrow on your phone clear to where it ask to select language or start screen and emergency call if done correctly it should now give you the accessibility menu also enter into the accessibility option and modify your set up. Mess with stuff a little be careful with setting up universal switches as you can really mess yourself up. At some point in time you should be able to get your notification menu to drop down and open. When this happens hit the little setting menu button long click it and it should shortcut you to system settings. Bypassing for temporarily. Set up your setting and movie your app permissions as much as possible. Now the trick is getting my Knox downloaded open and set up on your phone. Once you do this make sure you click on both my Knox and regular device administration for know to have some control and make sure you say yes for Knox to be able to reset wipe your phone . After device administration is set and that all done go to your pc or another phone tablet whatever and log into know online and you hold re your phone connected on it white a button that says wipe this phone. Click it make sure the phone has Wi-Fi or service connected and wait for phone to wipe this should reset frp and Google verification back to being a new phone. There ya go merry Christmas

Is this fix legit?^^

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
Fцck no it ain't legit. Dude probably got baked & strung up that nonsense to laugh at folks who tried it. You could string up a petrabyte worth of miscellaneous characters so long that your phone would be permanently frozen... & you wouldn't get an error message to pop up, let alone one that would change your notification bar background color or whatever else he said
☆KØŁØЯΛĐØ☆

Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
No, It's not.
I still can not remove the Samsung FRP, I've tryed all the methods I found online, but still nothing.

S7 & S7 Edge FRP [SOLVED]
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Hi ☆KØŁØЯΛĐØ☆, I think I ****ed up.
I follow your instructions, but after the first step (flashing boot.tar) the phone whent on a endless reboot.
Please can you help me.

☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?

jazzdglass said:
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?
Click to expand...
Click to collapse
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?

keiichitroncio said:
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?
Click to expand...
Click to collapse
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.

jazzdglass said:
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.
Click to expand...
Click to collapse
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you

keiichitroncio said:
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you
Click to expand...
Click to collapse
Just downgrade to marshmallow.. Try PJ2.. I used that. Flash the boot file provided, run Qualcomm.bat via adb.. Then flash again 6.0.1... If phone reboot after flash boot file, you'll have to be very fast, after phone boot to welcome screen, before it reboots, keep running the Qualcomm.bat till u see adb recognize device. It will say error. About phone storage. Just ignore. It has been unlocked

Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ

☆KØŁØЯΛĐØ☆ said:
Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ
Click to expand...
Click to collapse
Do you happen to have the exynos adb bypass code?

OMFG this freaking worked!!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
You sir are a genius. I tip my hat to you.... The only method out of....pretty much the entire internet...that actually works. To all other modders, if you follow the instructions carefully, this will work. Thank again man.:good::good::good:

I have a G935V that is stuck with FRP. I reset my password today and then happened to try to flash a new ROM (didnt know about FRP at the time).
Been trying this all day, but cant get the S7 & S7 Edge QUALCOMM.bat to run on the phone... a flashed back to MM and the Boot.rar pushes fine, but when the phone gets to the welcome screen its like my computer doesn't recognize the phone is connected. Any ideas?

This worked great on my VZW s7 (just had to get the right VZW firmware)...
@KjK89, you have to run the .bat file before the welcome screen. I basically kept running it over and over during boot and it took before th welcome screen.

Check my post about SAMSUNG S7 Nougat 7.0 frp remove

Thanks So much, the only thing that actually worked!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Anybody looking for a fix for Galaxy S7 and S7 Edge Factory Reset Protection Bypass needs to follow these steps and you'll get past this pesky protection.
The only step that wasn't clear was this:
- Flash the boot.tar file that corresponds with your device (enables ADB)
On Odin you have to choose the boot.tar file corresponding to your model number. This is done by selecting the BL button and only that one then in Odin click Start. This might be clear for veterans to flashing phones with new firmwares but it wasn't clear for me, being the n00b that I am. Thanks again. This worked great!

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

[issue found][archived] FRP / OEM locked device that won't start OS

Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log

Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .