Related
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.
Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.
(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
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
pinkgeek said:
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
Click to expand...
Click to collapse
If you have Bootloader it can be fixed. Download the firmware from sammobile and put the files in the spot it says it is. PDA file will go to PDA etc.
Edit. Sorry forgot that PDA is the old Odin. Download the newer version v3.12 and put the AP files in the AP slot and the same with the CP file and CSC. You might wanna try leaving the BL file out as when I did mine it would only work if I didn't add BL.
I had quite the same thing. I rooted my S7 Edge abd installed Lineage, but I was not satisfied of it, so I decided to come back to stock ROM. This was impossible : flash with Odin, with TWRP, etc... All came to a bootloop or freeze when the phone booted.
And yesterday, after a new attempt, the phone booted and now, it works very well. I don't really understand what changed or what I did more, but it seems that your phone is not bricked. Try another Odin flash with forcing CSC maybe.
hello,
i managed to get the phone back to get in download mode. stock everything, no root whatsoever. my goal is to root my phone and i have experience doing so but i guess i was just unlucky this time.
i tried searching allover the internet for a fix, searching xda etc.
first off: my device is running oreo 8.0 and it's type is G950FX.
I want to downgrade to 7.0 because FRP lock is on, i did turn on oem lock before starting however i am unable to log in to my old google account connected to my phone.
when i try to flash any bootloader i get SW REV CHECK FAIL DEVICE 2, BINARY 1. i tried almost any trick in the book like downloading 7.0 from sammobile, flashing using odin.
the things i run into when flashing are:
1.can't flash the bootloader, probably because of frp lock.
2. when i don't flash the bootloader for 7.0 i get dm-verity error 0x2.
3. when i only flash 8.0 oreo pda & csc and then flash 7.0 pda on top i do get to boot but i get encryption interrupted error.
4. i am able to boot in 8.0 but can't get past the frp.
i'm out of answers, i really hope anyone can help me out of this situation as i want to use my phone.
Help is much appreciated!
edit: i tried flashing multiple versions of android 7.0 but i keep getting sw rev check fail bootloader device 2 binary 1
i basicly want to do this, a downgrade: https://forums.androidcentral.com/s...s8-plus/878062-how-downgrade-oreo-nougat.html
the problem is i didn't sign out of google or samsung accounts before resetting to factory
You can't. You have a new bootloader v2.
A simple search gives you this answer, if you have u2 and CRED bootloader installed you are stuck. No way to go back anymore.
i'm on u2 and CRED bootloader. i did search for this indeed but i didn't want to give up.
do you think there will be ever be a way to get back into my phone again?
If you have FRP lock good luck. I haven't seen a way yet.
I know it's been 5 months and you've probably either gotten rid of the phone or it's sitting in a dusty bin somewhere, but have you tried Galaxy Reaper? It's a pretty legit FRP bypass tool.
Edit: Scratch that. It's apparently been patched since I last knew it to work. Just wanted to double check, and sure enough..