Hello,
So recently my Samsung Galaxy S7 phone has got back from being unlocked in a repair shop... When I got the phone back though, everytime I try to start it red writing pops up during boot saying 'Custom Binary blocked by FRP Lock' before shutting off...
I have tried:
Code:
1-Flashing a ROM using Odin
2-Unlocking the phone's bootloader
3-Using a load of google searches
4-Installing third-party apps
5-Installing stock firmware through SD card
None of the above worked, since the person that unlocked the phone seemed to have re-locked the boot loader after they finished...
Does anyone know any other solution?
Flash rom again and select nand erase all in options tab
AKawaiiSylveon said:
Hello,
So recently my Samsung Galaxy S7 phone has got back from being unlocked in a repair shop... When I got the phone back though, everytime I try to start it red writing pops up during boot saying 'Custom Binary blocked by FRP Lock' before shutting off...
I have tried:
Code:
1-Flashing a ROM using Odin
2-Unlocking the phone's bootloader
3-Using a load of google searches
4-Installing third-party apps
5-Installing stock firmware through SD card
None of the above worked, since the person that unlocked the phone seemed to have re-locked the boot loader after they finished...
Does anyone know any other solution?
Click to expand...
Click to collapse
give this a whirl
http://www.samsungsfour.com/tutoria...ock-on-samsung-galaxy-android-smartphone.html
Youdoofus said:
give this a whirl
http://www.samsungsfour.com/tutoria...ock-on-samsung-galaxy-android-smartphone.html
Click to expand...
Click to collapse
hey can you help me i have tried all of these options including yours and no luck also this isnt the first time i have had this happen to me
Related
After around 5-6 hours this morning/afternoon, I've officially given up on fixing this on my own, and I've all but accepted my device to be a $600 paperweight.
I decided to make one last attempt at saving it by posting for help.
Problem: My phone has a feature called "FRP" (Factory Restore Protection), which is tied to one's Google account. Basically, if you have a Google Account on the phone, it locks the phone to any custom binary/custom OS/whatever.
Once I realized this, in order to root my phone, I went in and removed my Google accounts. Sure enough, this disabled the FRP Lock, and I was able to root my device.
After rooting my device, I re-added my Google accounts and went about my business for the next couple of weeks or so.
Just this morning, my phone was having issues charging, so I decided it'd be a good idea to give my phone a reboot. Big problem. It turns out I simply haven't ever turned off my phone since I rooted it. On top of that, I didn't think the FRP Lock would apply to booting the phone, I thought it only affected flashing new firmware. I was wrong.
After my phone turned off, red text appears at the top of the screen: "Custom binary blocked by FRP Lock".
This is the problem. It simply cannot boot. Because it cannot boot, I cannot remove the Google accounts to disable the lock and resolve the problem. Because the lock can't be disabled, I can't flash the phone's original firmware, because FRP Lock will stop anything and everything I try to do.
---
Goodbye 1k+ photos on phone... And, well, goodbye *phone*.
Unless someone has any helpful thoughts! And that's why I'm here.
tl;dr: Soft bricked phone due to FRP Lock. Not able to restore original firmware, factory restore, or boot into phone's operating system.
Important: The phone turns on, and I have access to the recovery menu as well as "Download Mode"
---
What I have tried:
Factory restoring through the recovery menu, doesn't have any effect
Flashing stock firmware through Odin (Nand write failure)
Flashing a custom recovery environment (TWRP) through Odin (FRP Lock blocked this flash)
ADB and Fastboot cannot recognize the device
Tried to use Kies 3 and Smart Switch to "re-initialize" my OS or something. Both failed, saying that my phone wasn't compatible, and that my serial number was invalid (it was, in fact, correct)
---
And I probably did more things that I simply don't remember. The point here is that I've done everything, and literally everything has failed for one reason or another.
I feel like it is a possibility that if I attempted another stock ROM, then I might be able to avoid the Nand Write Failure. But again, I don't know, and I've almost accepted that I need to start looking for cheap alternative phones.
Thanks in advance, I really hope that this can be fixed one way or another. I'd be sad to see my photos disappear, but if it was the only way for my phone to work again, I could live with it.
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
I thought about doing that, but I have no way of wiping the phone. What do you suggest?
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Cosmic Blue said:
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
Click to expand...
Click to collapse
I am not running a custom recovery OS, there is no Advanced section. :s
Yarraque said:
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Click to expand...
Click to collapse
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Purlek said:
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Click to expand...
Click to collapse
Go to the developer settings and unlock "oem unlock" thing. Try again.
Yarraque said:
Go to the developer settings and unlock "oem unlock" thing. Try again.
Click to expand...
Click to collapse
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Purlek said:
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Click to expand...
Click to collapse
Oh nice to hear ^^
Samsung FRP
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
Would this work with the Samsung Account Factory Reset Protection?
I have a brand new G930F. I completed the setup process and got all my apps and settings configured.
I would like to root it, but when I try to flash chainfire's auto-root in ODIN, I get the message:
"Custom Binary (Recovery) blocked from FRP lock".
At which point I have to hold power till it dies and restart it.
I'm not bricked or anything, I just can't flash the rooter. Any ideas?
LysolPionex said:
I have a brand new G930F. I completed the setup process and got all my apps and settings configured.
I would like to root it, but when I try to flash chainfire's auto-root in ODIN, I get the message:
"Custom Binary (Recovery) blocked from FRP lock".
At which point I have to hold power till it dies and restart it.
I'm not bricked or anything, I just can't flash the rooter. Any ideas?
Click to expand...
Click to collapse
There are a few people who offer to turn it off remotely, but they're unclear when I ask if it would require wiping my phone.
LysolPionex said:
I have a brand new G930F. I completed the setup process and got all my apps and settings configured.
I would like to root it, but when I try to flash chainfire's auto-root in ODIN, I get the message:
"Custom Binary (Recovery) blocked from FRP lock".
At which point I have to hold power till it dies and restart it.
I'm not bricked or anything, I just can't flash the rooter. Any ideas?
Click to expand...
Click to collapse
You forgot the enable oem unlock in developer settings?
brotbuexe said:
You forgot the enable oem unlock in developer settings?
Click to expand...
Click to collapse
I never knew about it! Gonna try this right now!! Thanks!
Thank you! It worked!
Hi all my g955f has oem lock. Can't enable it. Can't boot into system. Tried to flash twrp but says oem blocked custom binary. It was turned on but friend (who is quite cluey) turned it on by accident.
I have combination file for g955f
Can see ish debbing turned on. No oem unlock in combination file. So really stuck any help please
Just flash stock, then fix it. Your friend (Or you, if you're lying) probably has no idea what they're doing.
Lol I did delete efs folder a whole ago my friend did get it back. I did get my imei back. I showed him then he turned off OEM lock. The egg! So I have flashed stock. Can't flash dm verity file because won't flash custom binary because of lock
Harrrd said:
Hi all my g955f has oem lock. Can't enable it. Can't boot into system. Tried to flash twrp but says oem blocked custom binary. It was turned on but friend (who is quite cluey) turned it on by accident.
I have combination file for g955f
Can see ish debbing turned on. No oem unlock in combination file. So really stuck any help please
Click to expand...
Click to collapse
I had exact same problem...took it to Samsung...cost me £290 for a new board.
Had to pay coz warranty void coz i rooted it.
Matt
this is how I fix the problem.
if you have FRP Lock as well then remove FRP by combination file.
after remove FR, P the phone will still ask for WIFI during reboot
downgrade the phone firmware to G955FXXU1AQCA_OXM1AQCA.zip if possible
flash the lower version firmware
if you got boot error then do hard reset
after finish reboot
go to settings to reset the phone again (not hard reset)
you will remove the Knox problem.
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Huzalio said:
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Click to expand...
Click to collapse
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cache, factory reset, then reboot device.
cooltt said:
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cach, factory rest, reboot device.
Click to expand...
Click to collapse
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Huzalio said:
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Click to expand...
Click to collapse
Mate keep trying you have to be really quick when it goes off to quickly press volume up
cooltt said:
Mate keep trying you have to be really quick when it goes off to quickly press volume up
Click to expand...
Click to collapse
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Huzalio said:
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Click to expand...
Click to collapse
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
cooltt said:
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
Click to expand...
Click to collapse
Yeah did exactly that switched to the combo before it showed anything no succes.
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
Not sure what's wrong with it then
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Ulf3000 said:
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Click to expand...
Click to collapse
able to confirm to enter download modus
Huzalio said:
able to confirm to enter download modus
Click to expand...
Click to collapse
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
cooltt said:
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
Click to expand...
Click to collapse
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Huzalio said:
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Click to expand...
Click to collapse
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
cooltt said:
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
Click to expand...
Click to collapse
Okay i see.
Do you somehow have a good tutorial?
Huzalio said:
Okay i see.
Do you somehow have a good tutorial?
Click to expand...
Click to collapse
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Ulf3000 said:
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Click to expand...
Click to collapse
sadly no succes :/
Huzalio said:
sadly no succes :/
Click to expand...
Click to collapse
I think it's obvious you don't know what your doing, no offence. Everything that's been suggested should work with no problems. You are better off taking it to a Samsung centre to fix it. I doubt anyone will be able to help you here.
unbricking with the factory binary
This method is not for the faint of heart; it involves downloading 1) the factory binary for your phone, and 2) the correct firmware for your phone (which you can find at sammobile). I don't know if it will fix your particular problem but if everything else has failed, it's worth a try. You will basically be taking your phone back to its state when it was first set up at Samsung factory, before the firmware for your region was installed. I used this to get past a drk imei error, it's worth taking a look. Anyone else who knows more than me, please weigh in on what you think about it.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
So I have a Samsung Galaxy s7 930T I was trying to root/custom rom it so I can have 930U firmware. I kept getting failed in Odin I assume because im getting the error "check fail : recovery" in bootloader. I did OEM Unlock, the phone is unlocked it self. So I tried to do multiple things and now the only thing thats happening to the phone is its stuck on "System updating" then turns off and goes back to that screen on a loop. Please help
FawkHTC said:
So I have a Samsung Galaxy s7 930T I was trying to root/custom rom it so I can have 930U firmware. I kept getting failed in Odin I assume because im getting the error "check fail : recovery" in bootloader. I did OEM Unlock, the phone is unlocked it self. So I tried to do multiple things and now the only thing thats happening to the phone is its stuck on "System updating" then turns off and goes back to that screen on a loop. Please help
Click to expand...
Click to collapse
Install the firmware that was on it before you tried to root and start again. Read the guides carefully and ensure they are upto date.
Hold volume down+home+power, the phone will eventually boot into download mode.
cooltt said:
Install the firmware that was on it before you tried to root and start again. Read the guides carefully and ensure they are upto date.
Hold volume down+home+power, the phone will eventually boot into download mode.
Click to expand...
Click to collapse
I cant seem to find an actual guide to help me fix these errors I been having, I am doing it to the T I do know that but I keep getting Odin failures when trying to do anything and I feel its cause my Bootloader is locked I just dont know how to unlock the boot loader. I did OEM unlock, tried to do that .img thing but that keeps failing so now im stuck lol
FawkHTC said:
I cant seem to find an actual guide to help me fix these errors I been having, I am doing it to the T I do know that but I keep getting Odin failures when trying to do anything and I feel its cause my Bootloader is locked I just dont know how to unlock the boot loader. I did OEM unlock, tried to do that .img thing but that keeps failing so now im stuck lol
Click to expand...
Click to collapse
You can't unlock the bootloader on the 930T, you can only root it. Maybe try flashing the current T mobile firmware in Odin to get your phone up and running again.