I have a Samsung J320V or J36V which is on the Verizon network. I really want to root it to unlock the full potential of my phone and I understand it will void my warranty but I'll go ahead and do it anyway. When I follow the steps to root I get stuck at the Odin part which I have to click start and the TWRP file installs on my phone. But it fails and I get this message on my phone "SECURE BOOT FAIL RECOVERY"! I've looked everywhere for a solution but none of them work and I also enabled USB DEBUGGING and OEM UNLOCK. I also couldn't disable REACTIVATION LOCK because the feature is not on my phone and I also removed my Google account and Samsung account. If anyone could help you would be the real MVP and I would really really really appreciate it from the bottom of my heart! Even if you saw my post and can't help still thank you for taking time out of YOUR day and looking at my problem!
XpertSource said:
I have a Samsung J320V or J36V which is on the Verizon network. I really want to root it to unlock the full potential of my phone and I understand it will void my warranty but I'll go ahead and do it anyway. When I follow the steps to root I get stuck at the Odin part which I have to click start and the TWRP file installs on my phone. But it fails and I get this message on my phone "SECURE BOOT FAIL RECOVERY"! I've looked everywhere for a solution but none of them work and I also enabled USB DEBUGGING and OEM UNLOCK. I also couldn't disable REACTIVATION LOCK because the feature is not on my phone and I also removed my Google account and Samsung account. If anyone could help you would be the real MVP and I would really really really appreciate it from the bottom of my heart! Even if you saw my post and can't help still thank you for taking time out of YOUR day and looking at my problem!
Click to expand...
Click to collapse
Greetings and welcome to assist. I can see you have already asked this question here
http://forum.xda-developers.com/showthread.php?t=3497140
and here
http://forum.xda-developers.com/showthread.php?t=3435514
so I will close this one up. Please just make the one thread in future
Good Luck
Sawdoctor
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.
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
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.
I bought a second-hand galaxy S10e that was advertised as being stuck on a boot loop. I fixed the boot loop by flashing with a stock firmware, but was greeted with an frp lock that I triggered in the process. I contacted the seller about it, but he said he bought it second hand himself and has no way of contacting the original owner. I've tried a couple things and thought this through, and I decided to ask here whether I missed anything.
First, is it possible to read the google email associated with the frp lock from the device in order to contact the last logged in owner? that would make this a lot easier if I could ask them to unlock it for me.
I assume this isn't possible, since I couldn't find anything about it. what are my other options? while recovering from the boot loop, I flashed a very recent firmware, so all of the 'frp bypass' tricks I see advertised don't work. I also wasn't able to flash a combination file.
Does anyone have any experience with this, and any ideas I could still try? Bought the phone for my wife, and I'd hate to see her angry :|
Solved with the help of @hainguyenthao
thank you!
drafthorsey said:
Solved with the help of @hainguyenthao
thank you!
Click to expand...
Click to collapse
Can you elaborate on how you achieved this? So I and others can follow the procedure too?