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.

[SOLVED (Factory Reset)] Failed Root Attempt - Will not boot past SAMSUNG boot logo

As the title implies, I've failed in my attempt to root my S7 Edge. I can access the custom download tool as well as the TWRP tool that I installed via Odin. However, I have no SD card and my attempts to use ADB have been unsuccessful. Right now I am looking for an option to reset my device to factory settings. I don't care about my previous data, as this is a relatively new phone. However, I believe my warranty is voided, and that is why I am posting here.
What are my options at this point? If it helps, a micro SD is arriving via Amazon tomorrow afternoon. Ultimately, I'd like to be able to install a custom ROM or root my existing Nougat that I started with (my original intention).
As for how the process may have failed, the tutorial I watched didn't seem to make it clear that I had to enable USB debugging. I enabled OEM Unlock, but not USB Debugging. Any help would be greatly appreciated. :good:
EDIT: Smart Switch does not support the device for emergency recovery. I really think I messed up my phone
EDIT 2: After suddenly disconnecting during the download process of a fresh firmware via sammobile, I restarted the device to reach an error screen telling me to use Smart Switch Emergency recovery. However, my device was not supported. Following a guide online, I clicked on the More tab at the top right corner of the Smart Switch program and chose "Emergency software recovery and initialization". I entered the relevant information for my device and the recovery process began (fingers crossed). After it has completed, I am now once again booting my factory firmware. I'll leave this post here because I couldn't find a similar post on the first couple pages of the forum or with the search function.
Now, can anyone direct me to a proper beginners' guide to rooting the S7 Edge? I'm fresh off of iOS, which I've used and been jailbreaking for the past nine years. I thought it would only slightly more complex, but I see due to the many different versions of the same device, rooting can be quite tricky.
Edit 3: New question which I can't find the answer to anywhere... Do you need an SD card to root? I'm resetting my phone for the second time now. Got a boot loop after using ADB sideloader to install supersu.

Where did you get the stock firmware? I have the unlocked sm-g935u... made an unbelievable stupid mistake and my three day old s7 edge is partly functional (only bare essentials), but whatever I did before wasn't wiped when I did a factory wipe so my phone thinks it's rooted even though it most certainly is not. (And many features and apps won't work bc of it. )
I can't find anything useful about theNougat firmware. I'm really desperate. My company bought me this and i broke it within a week. :'(

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

My divice is dying!!!

Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.

manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
Anyway, I'm in Vietnam.
Click to expand...
Click to collapse
Do a data format, then install anything.

justboryata said:
Do a data format, then install anything.
Click to expand...
Click to collapse
How to flash something when bootloader is locked? Anyway, that's not point, I can flash via testpoint method, the point is why I can't use 8.1 and can I take my IMEI back, thanks!

manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
Click to expand...
Click to collapse
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it

billis2020 said:
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
Click to expand...
Click to collapse
I can buy a new one with the cost to replace to the whole mainboard. In fact, I accept the thing that I can't use SIM anymore, I just don't know why I can't upgrade to 8.1 or higher

Help: My LG H990 DS only enters Fastboot and now the device changes to US996

Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...

Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope

aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs

cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...

I ended up flashing whole rom again and everything is back to normal