Related
Anyone knows how to go remove FRP lock with custom kernel and recovery? I cant boot into the OS nor in the recovery due to custom binary? Any way to get it unlocked or maybe get booted in the rom??? Help will be appreciated.
CANT EVEN FREAKING CHARGE MY PHONE DUE TO FRP LOCK!!!! WTF????
Will flashing stock rom fix it?
Be careful not to run your battery down or you won't even be able to flash your device with Odin. If I had enough battery left, I'd flash it with Odin right now.
Kh thanks. Worked. Phoned bricked when I had 100% battery.
AK1149 said:
Kh thanks. Worked. Phoned bricked when I had 100% battery.
Click to expand...
Click to collapse
what exactly did youdo to fix this?
Download stock ROM and flash using ODIN.
CafeKampuchia said:
Be careful not to run your battery down or you won't even be able to flash your device with Odin. If I had enough battery left, I'd flash it with Odin right now.
Click to expand...
Click to collapse
so when I flash the stock .. the OEM Unlock option should be ON or OFF ?? please help
That doesn't matter. Just flash it. It will work with official firmwares even with OEM Locked.
frp lock is not brick, its an setting you disabled in
developer options > OEM unlock,
the way to get past it its to flash offical firmwate trough odin and phone boot again, just enable OEM unlock again to root and keep it enabled
Can someone find a stock ROM for my tmobile version, model number G928W8. I have tried everything but when i flash it through Odin it fails.
Try starting download mode and use smartswitch and use the option to reinstall it
You can check sammobile they have a library of firmwares.
FRP Removal
Removed
the Doctor said:
Be careful not to run your battery down or you won't even be able to flash your device with Odin. If I had enough battery left, I'd flash it with Odin right now.
Click to expand...
Click to collapse
hey please help me i bought a samsung note5 T-mobil about 3 weeks ago it give me this msg (custom pinary blocked by frp lock ) and turn of i try to flashed it with odin and kies 3 but didnt work still nothing what should i do :crying:
HELP! Custom binary blocked by FRP Lock
So I flashed a tar to root my samsung galaxy on5 in Odin, recovered and added SuperSu everything was working fine till i turned off developer mode since i was i THOUGHT done with the procedures. rebooted and NOTHING but a RED msg stating "custom binary blocked by FRP.
It Wont turn on, it Wont go back into recovery mode AND I cannot discover it when i plug it via usb to computer.
WTF?? How do I get it Working?
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.
need urgent help really.
my phone has been rooted and has twrp installed for months now with no issues, all of a sudden my phone rebooted to the samsung logo screen with the mentioned error message. i have no idea how and why this error has occured but my phone wont boot to system. i really dont want flash stock firmware as i havent backed things up, is there a way to fix this issue with out doing a full wipe?
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
robhug said:
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
Click to expand...
Click to collapse
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
sofir786 said:
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
Click to expand...
Click to collapse
yes hopefully cloud is our new god ^^ yes its annoying I agree but its also a great feeling to begin with a clean phone like new after a reset , and I have also a crappy download speed so yes its a pain to download 4gb , and even better when its corrupted and need to download agin good luck with your device
Hey guys I need help.
My phone got bricked as you said (I accidentally turned off OEM unlock on my rooted phone) so I tried to flash stock firmware, but odin fails and on my phone it says (sw rev. check fail. device:3 binary:2). Plz help!
My phone: S8+
FIRMWARE: CRF7
FRP LOCK: ON
OEM LOCK: ON
Just had the very same problem meself ?
Thank god for Odin and https://updato.com/
Bt like previous posters says its like havin a new phone apart from samsung pay not working
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
nattyniz said:
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
Click to expand...
Click to collapse
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
spawnlives said:
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
Click to expand...
Click to collapse
That helped. Flashing the right version worked just fine.
Thanks!!
FRP lock
Hi people,
I got the "FRP lock" on my Samsung S8 SM-G950F(Exynos) and tried to flash Stock Oreo but when I press start Odin say PASS but recovery won't start.
please help
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Mark Nyombi said:
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Click to expand...
Click to collapse
can you get a pic of the screen youre talking about?
Hello guys i rooted my S8+ G-955F and i turned off usb debugging and ome lock
And i have android 9 installed on my device, i tried all the way but for nothink , any help please
All,
Before I throw this in the bin (which would be a hellavu shame!!) I thought I would quickly see if I am missing something obvious.....
I bought an unlocked device (previously on vodafone - from the apps i saw) SM-G901F from ebay.. I enabled developer tools, and tried to flash TRWP (but it never took ... on each reboot, the stock recovery would appear ... I read countless threads that you needed to not reboot (which I tried to no avail) ... i then read a thread that the bootloader may be locked, and followed a guide to try and fastboot unlock it (fastboot never found it but ... This is where it all went wrong .. I lost the ability to boot into the recovery and the phone boot loops infinitely ... however I can still get to download
I tried the downloaded a complete official firmware and tried to flash using Odin .. this was successful, BUT again the phone continues to bootloop.
I then managed to flash Clockwork mod onto it, to deleted the caches, etc ... but again bootloop
Finally I tried to wipe the phone and load lineageos (through CWM) ... Again all said it was successful ... but bootloop...
I think I might have knackered the phone when i went near the bootloader? Yess ... Im a muppet!!
I have tried 1000 different approaches .. odin/firmware (various) ... all seems to install fine .. but bootloop
Im out of ideas .. Is the bin the only thing now?
Thanks
Morning. I would appreciate any opinions iona please.
Thanks
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
JTec11 said:
Okay guys, I've got the S7 edge (SM G935F) Exynos var.
I restarted my phone yesterday, it hasn't been rooted or anything and it got stuck in a boot loop. Then I got the common 'blue light of death' with the black screen, rendering it useless.
Whilst in this state, I can't force restart the phone or enter recovery / DL mode.
The battery finally drained and I've flashed new (stock) firmware through ODIN. Still the same outcome.
I figured I could root and get a custom rom to maybe work however I have the FRP lock issue so I can't flash TWRP.
I'm open to any ideas, anythings worth a try at this point lmao, last phone I rooted was my S5 so a little out of touch with it all.
Cheers
Click to expand...
Click to collapse
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
xTweeBy said:
I had the same issue for about a week now, luckily i didnt have the frp lock on, but I have tried everything possible from downgrading to upgrading to flashing a custom rom : everything seems to just fail in every way possible and youll always end up with the blue light of death as you call it. I came to the conclusion that this isnt a software related issue , it is more than a hardware issue related to the s7 edge... I ended up forgetting about it after all ... Good luck !
Click to expand...
Click to collapse
Love a good Samsung lmao, thanks for your reply