Database Info

Please help, soft bricked my [US] [Sprint] Samsung Galaxy S6 SM-G920P

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?

[Q] Need help with FRP Lock PLEASE read me.

.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Odin Mode
Download Speed: Fast
Product name: SM-N920T
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warrenty Void: 1
AP Swrev: B:2 K:0 S:0
=========
Custom Binary (Recovery) BLOCKED by FAP Lock
.
Click to expand...
Click to collapse
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.

Thibor69 said:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Click to expand...
Click to collapse
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)

.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
josezr said:
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
Click to expand...
Click to collapse

Thibor69 said:
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
Click to expand...
Click to collapse
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE

josezr said:
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
Click to expand...
Click to collapse
Thank you so much my friend. I will try it and report back.
Cheers

Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.

I just rebooted with the developer options turned off on Friday. I was on ph1 firmware. Saw joeyv (spelling?) Deodexed stock rom with an option for an Odin installation. Did the installation through Odin and was back to stock. Odin flashed the kernel and tarp combo and was back up and running with root. No information was lost. For anyone else having this problem.
Sent from my SM-G935T using Tapatalk

Thank you JohnMonsour for taking the time to write all that. I will save it for future use if needed. BUT ... thanks to Josezr I got it fixed.
I was able to boot into download mode like I stated, but I just needed the correct firm to flash. They all failed until I tried
N920TUVS4DPH2_N920TTMB4DPH2_TMB.zip ( Thank you Josezr ).
I just flashed that file and Odin completed and phone rebooted to OS. So ALL IS GOOD. My only question now is ... inside the developer
options section ( in settings ) I have turned Developer options back ON but ... all the options that can be set ON or OFF are in the OFF
position and I am not sure which should be turned on. Can anyone please give me a quick run down on how they should be set .. like this:
stay awake on
next ones set to,
on
off
off
off
on
off
ect............
=======================
Debugging
=======================
on
on
off
ect........
=======================
Networking
=======================
on
off
off
ect........
It would sure help me. Thanks again to all 3 of you guys for helping.
Cheers

This is crazy I just ran into my phone becoming locked yesterday. T mobile sent me a update and my phone of course was set to auto update and my phone would do nothing it was a FRP LOCK. All I did was download odin and used this site to walk me through it all files are provided thanks to [ROM] [STOCK] N920TUVU3DPG1 | 6.0.1 | Deodexed | KNOX Free | 7.22.2016 by jovy23. At the bottum of the page is the download and also instruction to use odin. This was a life saver. LINK/ http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270. Copy and past everything you need to do to get out of a FRP Lock situation is in this tutorial. Thanks again Jovy23.

JohnMonsour said:
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
Click to expand...
Click to collapse
its so much wrong with this write up its not funny...for one his model number is sm-n920t second if he is in frp lock then he cant turn his phone off, i tried this method it doesnt work period

you can't turn your phone off?
Yeah actually you can hard reset it and then enter download mode....
Hold volume down the home button and power for like 10 seconds then when the screen turns black you quickly hold volume down, home, and power......
You might not be able to turn it off but you can still enter recovery and download mode.
You might not be able to get into recovery depending on how screwed up your phone is.
And kies3 version was the only one that would work with the above method, now kies has checks in place that checks your knox status and if you've tripped knox it won't work. I can rewrite the guide and link the proper kies if it's really necessary. But this is from 2016 so I am sure that I don't need a proper rewrite.
And at this point I'm pretty sure it might not even matter what version of kies is used it probably does all checks server-side. So this method is obsolete for an almost obsolete phone.
Sorry I didn't help you.

Potentially bricked S7 Flat? - Custom Binary Blocked by FRP Lock and Odin write fails

I bought a G930F from Amazon for use with my T-Mobile service, rooted it, and flashed a custom ROM (not sure exactly which one, but I have a folder named "CF-Auto-Root-herolte-heroltexx-smg930f") to it almost a year ago and everything was working just fine until this.
I was trying to get FRep (android macro/automation) working. It uses a setup tool on a PC that requires a connection and USB debugging enabled on the phone. When trying to run the setup I was getting errors about the socket/address already being in use so I'm not sure if it ever managed to do anything, but I saw a suggestion of rebooting my phone to fix the errors. In doing that I held down the power button, for my ROM's power options, chose reboot, went to the next reboot screen (maybe TWRP?) and chose the default reboot there.
When my phone tried to boot I got the Samsung Galaxy S7 logo with small red text of "Custom binary blocked by FRP lock". I'm still not entire sure what causes this (seems like a mismatch between having a custom ROM and some other setting). I'm wondering if the FRep setup tool somehow switched from OEM firmware protection flag. I booted into the download mode and tried to just reflash my old ROM, but even in the download mode I'm seeing "Custom binary (RECOVERY) blocked by FRP lock" with "NAND Write Start!!" then "Complete(Write) operation failed." in Odin3 logs.
I'm giving as much detail as I can because I'm not exactly sure which pieces are which. I've actually tried flashing the "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5" and "twrp-3.0.2-2-herolte.img.tar" files in the "AP" slot in Odin3 as I don't remember which file is for what, but both give errors on writing. I'm wondering if I shouldn't do custom ROMs in the future as I don't follow the scene long enough to learn all that I should in order to not mess things up.
Any help will be appreciated!
edit: I'm downloading a stock S7 ROM from sammobile, but I don't think Odin3 will be able to flash it anyways. Is there any way to use the PIT settings or something else to change the OEM protection piece?
edit2: After downloading a stock ROM I was able to flash it all with Odin3. I think only part of it would have been necessary (maybe just needed a new bootloader, not entirely sure about AP/CP/CSC fields in Odin3.) Got the phone working again, but now I've gotta remove some popup inducing malware that I think I got when downloading a stock ROM the link in the instructions here: https://forum.xda-developers.com/galaxy-s7/help/frp-boot-fix-sm-g930f-t3350149

need help with restore

ok had FRP lock been reading reading reading was told to flash sboot did restart phone then flashed boot.tar . restarted phone now I don't see FRP lock but get splash screen and up at top I get kernel rev check fail device 1 binary 0 . YOUTUBE videos are not in English so I am lost only thing I could make out so far is d/l new firm oj something its d/ling now. phone was rooted idk what happened to get lock just trying to get it back on android

S7 'Custom Binary blocked by FRP Lock'

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