Database Users

[Q] Galaxy S4 (SGH-I337) Soft-bricked after extensive research

A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!

AhellHound said:
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
Click to expand...
Click to collapse
Use Odin 3.07 Download the MF3 Firmware from https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE And put all the extracted files in the correct spot

compucanton said:
Use Odin 3.07 Download the MF3 Firmware from (your link) And put all the extracted files in the correct spot
Click to expand...
Click to collapse
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

AhellHound said:
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone's status on the top right when in download mode is as followed:
Code:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURSRT MODE enabled

I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.

Nurmi_CEO said:
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Click to expand...
Click to collapse
No

For future reference as posted in both the SS development thread and QA Thread OPs, Cyanogen and the like is not compatible with SS
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Also, if you are unable to restore with Odin and the MF3 files, I suggest mobitechvideos. They can possibly J-tag it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

HELP NEEDED! soft brick at&T s4 i337
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!

gtrijoe said:
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
Click to expand...
Click to collapse
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Dude, you totally saved me. I soft bricked my galaxy s4 and tried everything to get it back up. couldnt get anything to take on it. Until I found this and I pushed it through via Odin 3.07 in the PDA slot. It took and I am back up. Much thanks my man

Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?

morphius2036 said:
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
Click to expand...
Click to collapse
There's a nb1 tar file in the general forum. Use that.
Sent from my Nexus 5 using XDA Free mobile app

I screwed up flashing with odin. Plz halp!

SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.

T1geR086 said:
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
Click to expand...
Click to collapse
What did you flash, firmware wise? What are you trying to flash?

I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.

T1geR086 said:
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
Click to expand...
Click to collapse
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app

ickedmel said:
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried re downloading:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
HEROQLTE_USA_VZW.pit Tried several more times.
Errors:
"re-partition operation has failed" nearly immediately after start of ODIN flash every time.
On boot attempts it does "erase" and "System Update", reboots and comes up in Android Recovery with "Supported API: 3" and "dm-verity verification failed..."
If someone could point me I don't mind learning and figuring it out, but yeah....tad frusterated so I'm gonna smoke some cancer lol brb.

Are you using the modified odin? The original one wont work. The modified one is in the root guide.

Do what he suggests. Use the modified Odin. If that does not work try swapping cables, computers, etc...

craazy82013 said:
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Click to expand...
Click to collapse
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Will try again.
Flash BL AP CP CSC, or BL AP CP CSC +pit or AP CP CSC?
Want to make sure I at least get this right.

T1geR086 said:
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Click to expand...
Click to collapse
Does the phone even boot? USB debugging on?

craazy82013 said:
Does the phone even boot? USB debugging on?
Click to expand...
Click to collapse
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.

T1geR086 said:
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
Click to expand...
Click to collapse
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.

craazy82013 said:
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
Click to expand...
Click to collapse
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.

T1geR086 said:
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
Click to expand...
Click to collapse
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother

craazy82013 said:
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
Click to expand...
Click to collapse
Not trying to be short. Sorry if it came off that way. I appreciate hitting up a dev. I've been rather fixated on fixing this...*phone detox itch*

New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.

T1geR086 said:
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auth error instead of re-partition failure.
Click to expand...
Click to collapse
What version of Odin are you using?

Illogi.xbone said:
What version of Odin are you using?
Click to expand...
Click to collapse
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)

Try using Odin 3.14

T1geR086 said:
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Click to expand...
Click to collapse
Dont think you can downgrade ph1. Bootloader supposedly changed. There is a faster download in the forum. Way faster. http://downloadmirror.co/29Uj/G930VVRU2APE1_G930VVZW2APE1_VZW.zip<br />

Illogi.xbone said:
Try using Odin 3.14
Click to expand...
Click to collapse
Ty will try. Best place to find that? Odin downloader lists odin3 3.11.2 as latest? Didn't see any 14 ending versions.

Bricked my phone after turning off "oem unlock"

I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?

halomaster said:
I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?
Click to expand...
Click to collapse
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk

Koognod said:
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I try to flash anything in Odin. Same results in both Odin 3.12.3 and 3.10.7
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Flashing latest firmware will solve this problem...
Or
Other you can try Z3X Box ...
There are many tutorial on youtube..

Was there no answer to this problem or some what of a outcome? I am having the same issues,odin log identical

i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?

fixed mine with this SM-G550T1 BRICK FRP BLOCK FIX
glennnall said:
i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?
Click to expand...
Click to collapse
The stock rom you have is the wrong version. i got the info and fixed mine here..
https://androidforums.com/threads/galaxy-on5-metropcs-t-mobile-stock-firmware.1140060/
then i got the software from:
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
the exact firmware for metropcs is:
Country/Region USA
Product Code TMK
OS Version Marshmallow (Android 6.0.1)
Release Date 23.03.2017
PDAG550T1UVU2AQC4
CSCG550T1TMK2AQC4
Phone G550T1UVU2AQC4
once downloaded and extracted it is self explanatory on where to place files in Odin (files are labeled for appropriate slots) hope this helps. mine was bricked for 2 weeks determination is the key to success.

SM-G550T1 boot loop "Custom binary is blocked by FRP Lock"

I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages below:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​

Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.

BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!

I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.

Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well

Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!

SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.

Galaxy a5 2017 odin fails at cm.bin tried 2 lots fmware

Hi, tried to flash my a5 sm-a520f from 7.0 to 6.0.1 everything seems fine then it fails after cm.bin i've tried using A520FXXU1APLL VOD United Kingdom (Vodafone). and A520FXXU2AQF5 XEU United Kingdom.
I've searched but can't find a definitive answer. Tried as others suggested by changing ports several times and downloaded a second lot of firmware both for my phone and get the same.
Any help please?
Thanks
Below is log from the last time.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.

So no one can help me?
I found out it's the bootloader and found posts about taking all the .bin files out before flashing but that would leave the whole of the BL file out which is like 4gb the bulk of the whole thing. I've tried 5 different UK roms. Tried using CSC instead of home_CSC and that time after sboot.bin in place of cm.bin there's param.bin and no cm. The phone does say odin mode at the top.
Found loads of posts saying because 7 has a different bootloader than 6 it can't be done but many people have done it successfully without a problem. Is there a way to flash it a different bootloader to downgrade to 6.0.1.
I have done a lot of searching about 15 hours worth but can't find the right solution.
I can't get into the phones settings because like a prat i did a factory reset without knowing the password for the email address. Bought the phone, got the login passwords/pattern so was able to use it but it still had sellers gmail and couldn't get in touch with the seller, still can't. Decided to do an frp unlock which i've done many times for people but never on android 7.0. Found out after trying all other methods i had to downgrade which brings me to this problem.
The phone never had/has the the usual startup logos for service providers so i don't know if that means it came without bloatware. I bought it network unlocked, he had it on o2. I've tried stock 6.0.1 firmware for o2, Voda, EE, XEU & BTU.
Please help, already receding don't want to make it worse!
Thanks

Hi. I guess you're on either A520FXXU3 or A520FXXU4 firmware., and that's why you won't be able to downgrade to any lower binary version. Normally it works fine to downgrade without the .bin files as you would still use the updated sboot and baseband ,but with older system files without any problems. All good for daily use, but not for frp reset.
Problem is that it won't help you to bypass frp because you still have the updated binary version.
What you need is a factory combination firmware with the same binary version that you have installed.
That would make it possible to flash it, enable oem unlock to remove the frp protection, then flash a full 4-file firmware with factory reset.

Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks

skg76 said:
Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks
Click to expand...
Click to collapse
Yes, afaik it should work.
Sent from my Moto G5 using Tapatalk

Did you manage to get this working? I can't find any decent links anywhere for the A520FXXU4ARA4 combination file, found one on pakfirmware but md5 was invalid and wouldnt accept in odin..

Sorry mate just seen your message. Yes it did work was a pain though, took a week. I think i found a link on boxwares.
link is here. clicking download leads to a fast google download.
https://shell.boxwares.com/Download.aspx?L=4474
If link is gone just google the combi and look for shell.boxwares link.
Afterwards i just used any u4 stock rom and it worked. Done like 30 phones with this method since.

Odin fail
Help!!
I have the same problem..i've tried everything even turned the anti virus off and nothing works..if i flash a different costum rom would it fix the problem or should i downgrade the firmware to nougat couse last version i had installed was oreo..