I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Blackion said:
I got S7 SM-G930L with a port Rom from S8 (https://forum.xda-developers.com/s7-edge/development/rom-s8-port-s7-s7-edge-ambasadii-t3619548). When I power on the phone I get a message: Custom binary blocked by FRP Lock.
I would like to get rid of the FRP Lock without losing my data.
I saw a video https://www.youtube.com/watch?v=VdAhu45UPsU According to the comments 40% lost their data and 60% didn't.
Could you please advise how to make sure that my data won't be lost?
Click to expand...
Click to collapse
If there's an option for OEM Unlock in developer settings enable that to disable FRP
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
reflash the stock fw using odin
Not sure
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Blackion said:
I was said that because I'm using a port of S8 on S7, after I'll reflash stock ROM the data might be lost due to differences of memory formats.
Is it true?
Click to expand...
Click to collapse
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Blackion said:
But how do I boot my phone? Now I'm getting a red message: Custom binary blocked by FRP Lock and the phone is not booting past that. It will not even let me in TWRP.
Click to expand...
Click to collapse
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
corvasce03 said:
(sorry for the english but i'm italian) hi. i have the same problem, can you help me? i root my phone and after i unroot, but now the phone don't boot, it say custom binary blocked by frp, i understand that my bootloader is lock by oem, there is a way to unlock by odin or others method? i can't have access to recovery and the phone don't boot, what can i do?
Click to expand...
Click to collapse
I used smartswitch when I encountered frp lock
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
1eStar said:
If you haven't backed up your data, it will be lost.
When you get yourself back out of this mess, don't touch that OEM unlock toggle again...
Click to expand...
Click to collapse
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
kiwigi said:
@1eStar
Firstly I have a question regarding the OEM unlock as I just came out of the FRP Lock. Do I turn on OEM unlock or does it have to be turned off? Last time I had this FRP Lock was a year ago though did it again(the mistake with the OEM unlock) as I had forgotten it(Lots of grey hair)
Just don't know if it has to be on or off?
Secondly I have managed to come out of it(so far , hopefully) without wiping data with this guide
Click to expand...
Click to collapse
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
corvasce03 said:
To unlock your device by frp lock you must flash the stock firmware when you are in bootloader mode you see custom binary blocked by frp,if you try to flash a random firmware(always of your device) the operation may not be a good end and device say an error with this:
Knumber) Snumber) Bnumber)
When you go to download the stock firmware you must see the "code" Of the firmware with write the same S or B number
If you Don't understand see the 10th post of this thread
https://forum.xda-developers.com/galaxy-s8+/help/custom-binary-blocked-frp-lock-regular-t3745085
Click to expand...
Click to collapse
@corvasce03
Thanks.
I think I got back allright except this here and I used exactly the same stock(file) as a year ago
Someone Help My Soul!!!
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Cirphrank said:
Guys, I'm scared to death on letting my phone reboot, I have been told to never let my phone restart unless my google account has been removed, can someone please explain how this FRP block really works?
Am I at risk at every given point of phone restart for real?
Click to expand...
Click to collapse
It stops someone stealing your phone, wiping it, installing new firmware and using it as if it was new. If you know the gmail and password you put on the phone to access the play store then you just need to re-enter it after the phone restarts. FRP will only kick in if you have flashed new firmware to the phone.
I have a new firmware flashed on the phone.
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Cirphrank said:
And I'm using a new gmail with is, not some one July bro used on it.
What am I to do now? I have developer settings OEM unlock toggled on already.
Click to expand...
Click to collapse
I'm not sure what you mean. If you have a Google account on the phone that you know the email and password to, then just reboot the phone. FRP lock will only activate if you flash new firmware to the phone without removing the Google account first.
Your device should only have 1 Google account registered on the device which let's you access Play store etc. If there is more than one, you need to delete the ones you don't know the email and password to.
Okay...
Oh, okay, now I am getting the rationale.
Albeit, when I flashed in the new custom firmware, it started give me the undo changes by restarting your phone notification, like it did the first time ever that I got the lock. I didn't click it, activated an app that discarded the notification rather.
Now it makes me doubt if I had really removed my mail before flashing the phone.
hey
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
stasikkk777 said:
i have got the same problem. when i deleted xposed installer, my device rebooted. every time i try to turn it on, it says in top left corner 'custom binary blocked by frp lock'. i tried 3 diff rom to flash, no succes. i tried to acces twrp (my device is rooted) but again no succes. can you guys help me?
i have a G930F
thanks.
Click to expand...
Click to collapse
Yeah you've messed it up by not signing out of account before unistalling xposed. When you say 3 different rom's do you mean stock or custom?
Even in this state you should be able to flash a stock rom to the device with Odin and it will ask you to type the google email and password after boot.
Always turn off FRP lock before modifying the phone, it's a really annoying feature.
Related
So recently I have gotten a Note5 , which my friend has had sitting around and I bought it off him but he had forgotten his home password. So I did a Factory Reset but didn't know his old email and now I have tried bypassing the FRP method but none seem to work. It would be very grateful if someone can help me and.......... Also would flashing it back to its original image 5.1.1 help delete the FRP LoCK? :crying::
Turn on OEM Unlock in Developer Options...
sinisin said:
Turn on OEM Unlock in Developer Options...
Click to expand...
Click to collapse
How can he do that if he cant get past frp lock?
I am curious myself to see how thTs done
isn't that there's a way to bypass it by connecting phone to computer and run sidesync on the computer?
....
Not sure if this method still works but that's how I bypassed a samsung core prime last month.
Also you need to list what methods you used so others can see what you used and see if they have any new ideas.
He needs to restore a back up, or reflash a stock tar. There are literally 10 threads on this. FRP only shows up when someone who has rooted turns off OEM Unlock. I know, cuz I did. Flashing stock tar or a backup will either allow the software to bypass the lock, or restore software that has OEM Unlock turned on..
I have looked around for a long time but I can't find a solution to my problem.
When I try to root or install a custom ROM to my phone I get bootloop because of the FRP lock.
I have read that the only way to get around this is to log out of your Google account and never sign in but then I will lose a lot of features.
Is there really no way to root a Samsung Galaxy S7 with Google services enabled?
And is there any way of getting rid of the FRP lock without logging out off your Google account?
Any help is much appreciated!
Have you enabled OEM unlock in developer options?
*Detection* said:
Have you enabled OEM unlock in developer options?
Click to expand...
Click to collapse
Yes, I have, TWRP recovery also works fine.
Couldn't you just sign out, install, then sign back in? What would you lose by signing out that wouldn't come back when you sign in again?
Beanvee7 said:
Couldn't you just sign out, install, then sign back in? What would you lose by signing out that wouldn't come back when you sign in again?
Click to expand...
Click to collapse
I have already tried that, it works fine until I login to Google again. Then, if I restart the phone it goes into bootloop because FRP lock has been re-enabled.
byCorza said:
I have already tried that, it works fine until I login to Google again. Then, if I restart the phone it goes into bootloop because FRP lock has been re-enabled.
Click to expand...
Click to collapse
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
*Detection* said:
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
Click to expand...
Click to collapse
FRP lock appears when the bootloader changes. But I will try one more time with deactivating Google Services and signing out now just to be sure and report back. :good:
*Detection* said:
Never ever heard of this happening before, it obviously doesn't usually happen otherwise XDA would be full of people with the same problem... FRP lock should only appear if you try to reset the device from recovery without signing out first
Click to expand...
Click to collapse
Okey, I signed out of Google and Samsung, went into download mode and followed the exact guide here https://forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
Now I am stuck in bootloop again and it says in the top right corner: "Kernel is not seandroid enforcing" .
When I go into download mode again it still says: "FRP LOCK: OFF"
And as usual the only way I have been able to fix this is by flashing back to stock ROM.
Full Download mode info:
PRODYCT NAME: SM-G930F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
WARRANTY VOID: 1 (0X0203)
byCorza said:
Okey, I signed out of Google and Samsung, went into download mode and followed the exact guide here https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Now I am stuck in bootloop again and it says in the top right corner: "Kernel is not seandroid enforcing" .
When I go into download mode again it still says: "FRP LOCK: OFF"
And as usual the only way I have been able to fix this is by flashing back to stock ROM.
Full Download mode info:
PRODYCT NAME: SM-G930F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
WARRANTY VOID: 1 (0X0203)
Click to expand...
Click to collapse
That's for the Verizon S7, snapdragon, yours is the International Exynos S7
You're flashing the wrong files, use G930F files
SOLVED
I tried to flash different files for root without any help, so I decided to flash the Superman ROM which comes with root. I could actually boot now but OEM-unlock disappeared from the developer options.
I then had to enable OEM unlock somehow so i did:
Code:
> adb reboot bootloader
> sudo fastboot oem unlock
Now everything works perfect.
Hi,
I have a few questions about the FRP lock and the OEM lock on the Galaxy s6 running Nougat. I hope someone can help as I've not been able to find answers to questions this specific.
Ok, so, my first question is does the Galaxy s6 even have an OEM unlock option? If so, is it enabled by default?
Quick story before the other questions. I flashed TWRP and the sorts onto my s6 but decided to go back to stock and so flashed the stock firmware from sammobile through odin mode. After doing so I assumed the stock recovery would be restored and the phone would be as good as new right? As in all the FRP and OEM lock security features would be restored?
However, I did some research and found out that you can flash the stock firmware AGAIN as long as the firmware was signed by samsung even if OEM unlock is not checked.
My last question would be if someone was to use odin mode to flash the stock firmware, which is freely available, would the phone not ask for the previous Google account which was signed in on the device?
Hope is wasn't too hard to understand, I'm typing on my old S3 mini as I lost my s6 which is the reason I can't go and test this myself.
Thanks in advance
- There's no OEM lock on S6 (at least on international models). So, there is no OEM unlock option.
- If the bootable images (kernel and recovery) on your phone is Samsung signed, you can use FRP.
- If you want to revert the device to completely stock, I recommed that you should install a 4-part firmware.
- If FRP lock is not enabled on your device, phone won't ask anything about Google account (or Samsung account).
forumber2 said:
- There's no OEM lock on S6 (at least on international models). So, there is no OEM unlock option.
- If the bootable images (kernel and recovery) on your phone is Samsung signed, you can use FRP.
- If you want to revert the device to completely stock, I recommed that you should install a 4-part firmware.
- If FRP lock is not enabled on your device, phone won't ask anything about Google account (or Samsung account).
Click to expand...
Click to collapse
Hi,
Thanks for the informative reply. I have just one more question.
If I had enabled FRP through the Samsung Pass settings with my Samsung account and then I was to flash stock firmware on to the phone, would the Samsung FRP lock prevent the user from using the device by asking for the email and password or would the new firmware get rid of any of the security measures put in place?
I understand the FRP lock files are stored on a hidden partition not wipeable through the stock recovery however considering signed firmwares are freely available it would seem to me that the FRP lock would be deemed useless if anyone could just do that.
I guess my final question would be do signed firmwares downloaded online and flashed over the existing firmware wipe the FRP lock partition of the phone?
Thanks again for your reply
Haroon786 said:
Hi,
Thanks for the informative reply. I have just one more question.
If I had enabled FRP through the Samsung Pass settings with my Samsung account and then I was to flash stock firmware on to the phone, would the Samsung FRP lock prevent the user from using the device by asking for the email and password or would the new firmware get rid of any of the security measures put in place?
I understand the FRP lock files are stored on a hidden partition not wipeable through the stock recovery however considering signed firmwares are freely available it would seem to me that the FRP lock would be deemed useless if anyone could just do that.
I guess my final question would be do signed firmwares downloaded online and flashed over the existing firmware wipe the FRP lock partition of the phone?
Thanks again for your reply
Click to expand...
Click to collapse
Phone will ask Samsung or Google account only if you wipe the data (we assume that FRP lock has been enabled before wiping the data).
If you don't wipe the data while flashing any firmware while installing (or the firmware you try to flash doesn't wipe the data), phone won't ask you anything.
And, if FRP lock enabled on the device, bootloader will deny to boot (or flash) the unsigned kernel or recovery.
There's no way to wipe FRP lock via Odin.
So, we can say that FRP lock is pretty secure.
Yeah
But u can easy **** with samsung when u flash stock 5.0 with odin and on pc have sidesync or someting like that samsung suck because with that tutorial u can bypass frp really easy
JirkaPirkl said:
But u can easy **** with samsung when u flash stock 5.0 with odin and on pc have sidesync or someting like that samsung suck because with that tutorial u can bypass frp really easy
Click to expand...
Click to collapse
:/
well here's hoping a typical phone thief doesn't know how to do that....
Quick question though, can an S6 be factory restored if the user only used the phone's PIN from the lock screen to the factory reset option in the settings app? Or would you be prompted to use your fingerprint? I read somewhere that factory restoring a device through the settings app disables the innate android FRP but i don't know if it's also the case with Samsung reactivation lock which is supposedly similar to FRP.
Thanks for the replies I appreciate it
Read on the way out from house !!!
Sorry for my bad but im now on the way but 1 yeah u will need maybe fingerprint for turn off reactivation ( frp) but first when u lost your phone use samsung accound on the browser for track lock etc 2 for factory reset u need only turn off phone and go to the recovery mode
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
JimbakBoomA said:
I have a samsung on7, SM-G600FY
I installed TWRP on it and rooted it. It worked perfectly fine, with no issues whatsoever.
However, i later disabled the OEM unlock option in developer options and a week(ish) later i switched off my phone. On trying to turn it on, i get a screen with an exclamation with the following on the top of the screen:
[WHITE] CUSTOM BINARY BLOCKED BY FRP.
[RED] SECURE FAIL : KERNEL
I think this is due to oem being locked, which is not allowing the OS to load, maybe?
Is there any way to enable it via CMD on the computer? Thanks
Click to expand...
Click to collapse
i looked it further and due to the oem lock, it seems to be more hardware related than software? How can i flash/program the processor..?
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Hi7m3up said:
Im 99% sure you need to download the firmware from sammobile and flash it with odin i don't think there are any other options other than that,
Maybe someone else could "chip in" to clarify it ?
Once you get your phone up and running again it's worth mentioning that when rooting you have to have "allow the device to be OEM unlocked" to the switched on position or you will just trip the FRP again
Click to expand...
Click to collapse
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
JimbakBoomA said:
well, i tried using odin to try and reflash the twrp again, but it failed and i got a tiny message on the phone screen that frp blocked it.
I don't believe that i will be able to flash the custom rom either, if my phone isn't allowing it...?
By the way, is it possible for you to share the link? I would like to give that a try too. Thanks!
Click to expand...
Click to collapse
Go to https://www.sammobile.com download the correct firmware for your phone (important that it is the right firmware for your model) If your phone is unlocked to any network then it doesnt matter which country he firmware is from if your phone is locked to a specific carrier then you will need to make sure that the firmware you download is for your country and your carrier . You will need to register with sammobile but it's free download your firmware and flash using the most up to date odin you can get ,,you can find plenty of tutorials on how to do this using your search engine ..Dont worry if you dont manage the first go you can always try again. if you do all that right then your phone will boot normally after that . Be patient it can take 10-15 mins sometimes to flash then the first boot of your phone can take a while too..
Make sure usb debugging is on and most importantly that this time keep enable oem unlock at the switched on position (allow the device to be oem unlocked) or you will only trip the FRP and have to flash firrmware again
Your firmware package is around 2 gig so it will take a while to download and flash
make sure usb debugging is on also
Most of the time, I can bypass the frp on a galaxy s7 with no issues. I simply flash combination, use frp hard unlocker 3.0 provided by hardreset, then flash factory firmware. My problem lies with some devices only bootlooping once the factory firmware has been flashed. I can go in and flash the combination file with no issues, but I'm just tying to figure out what would cause this and how to get past it. Thanks for any info you may have.
VELEGIS said:
Most of the time, I can bypass the frp on a galaxy s7 with no issues. I simply flash combination, use frp hard unlocker 3.0 provided by hardreset, then flash factory firmware. My problem lies with some devices only bootlooping once the factory firmware has been flashed. I can go in and flash the combination file with no issues, but I'm just tying to figure out what would cause this and how to get past it. Thanks for any info you may have.
Click to expand...
Click to collapse
The firmware being updated and blocking the old FRP bypass method.
cooltt said:
The firmware being updated and blocking the old FRP bypass method.
Click to expand...
Click to collapse
Can you elaborate? thanks.
VELEGIS said:
Can you elaborate? thanks.
Click to expand...
Click to collapse
Sure,
So the whole point of FRP lock is to stop lost / stolen phones being factory reset and used again. However when you modify you may forget to turn it off (not a problem if you know email and password) then when the phone starts up with fresh firmware the FRP kicks in and you are locked out.
Others found an exploit to get round the FRP lock, combination rom's etc but with every new firmware update the exploit is closed and it no longer works. You have to wait until someone finds a new way around FRP lock for your specific device and since the S7 is now getting old, no one is bothered fixing the FRP lock problem anymore.
The easy solution is to always remove the google account before modifiying the device.
cooltt said:
Sure,
So the whole point of FRP lock is to stop lost / stolen phones being factory reset and used again. However when you modify you may forget to turn it off (not a problem if you know email and password) then when the phone starts up with fresh firmware the FRP kicks in and you are locked out.
Others found an exploit to get round the FRP lock, combination rom's etc but with every new firmware update the exploit is closed and it no longer works. You have to wait until someone finds a new way around FRP lock for your specific device and since the S7 is now getting old, no one is bothered fixing the FRP lock problem anymore.
The easy solution is to always remove the google account before modifiying the device.
Click to expand...
Click to collapse
I knew as much, I work for a company that buys electronics in bulk from places such as amazon or asurion for this very reason, the people who owned the devices and returned/sold them to these companies had not removed their google account. My job is to remove the frp as well as refurbish these devices for resale and so far i've had great success doing this. However, I've got a few devices every so often that fail to bypass. Are you suggesting that I should use as low of a binary as possible when doing frp bypasses? I believe these devices had binary 7. Combination flashed fine, linked up to adb and removed the frp lock, then when i flashed the stock firmware it would just bootloop. My goal is to maximize the amount of devices we can sell overall so any bit of information helps. Thanks.
I should also mention that I was taking note of the csc code before starting this process.