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

[Q] At&t samsung galaxy s4 i337 not booting into os

Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.

AlwaysBeen said:
Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.
Click to expand...
Click to collapse
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
<ID:0/003> Added!!
<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..
<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..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing

AlwaysBeen said:
<ID:0/003> Added!!
<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..
<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..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing
Click to expand...
Click to collapse
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Which file do I exactly download from this link?

AlwaysBeen said:
Which file do I exactly download from this link?
Click to expand...
Click to collapse
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970

bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
I really appreciate the registering just to help me out! Do i load the pit file with the MF3 tars? Or before?

bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED

AlwaysBeen said:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED
Click to expand...
Click to collapse
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:

kevp75 said:
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:
Click to expand...
Click to collapse
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.

MatthewPresley said:
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.
Click to expand...
Click to collapse
yeah... tried all that.
Stock Rooted NC1 ROM
Sent from my A110 using Tapatalk

Stuck in a boot loop even after flashing to stock from odin.

I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.

I'm in the same situation exactly. At the moment I'm trying to download UK 5.1 to play with odin once again.

did you manage to fix it?

BettlePimp said:
I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
Click to expand...
Click to collapse
It looks like your problem is that you forgot to turn off the samsung activation lock before flashing. If you forgot what that is see this I have not used this feature on my phone; however, I would suggest wiping with odin then flash the official stock ROM for your phone that you previously had on it when it did work, hopefully it will boot then login to you samsung account when it asks you about the reactivation lock. There are some activation lock bypass methods out there if you do a quick google search. Hopefully this will point you in the right direction.

The reactivation lock is indeed on. "Reactivation Lock(KK): On"
I have no way of turning it off since I'm stuck in a boot loop no matter what firmware I flash through Odin.
Any other suggestions?

I have same problem on my SM-910H
This problem was after updating 5.1.1 and isntallind micro-sd card (128gb)
In 4-5 days after this, bootloop began.
I deisntalled micro sd, checked it in computer for mistakes, fixed it and after this phone worked fine.
Today same problem, but when I deisntall micro-sd my problem does not go away.
I downgraded phone to 4.4 - does not help
Data wipe, cache wipe etc - does not help...
Waiting for solution from proffesionals (
update^
I've found 4 file Factory firware and tried to falsh it
What does Odin say:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary 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> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<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> NAND Write Start!!
<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

Do this, it worked for me. In ODIN, just AP/PDA Autoroot md5 file. It will not be successful and you will get "FAILED" message. Disconnect the phone from PC, pull out battery. Reinsert the battery and boot.

The same happened to me.

To all with this problem. My history:
1. Suddenly my stock device go in bootloop
2. Tried to flash it with official software it does not help
3. Tried to flash it with 3 or 4 file service firmware - did not help
4. Service center (not official, that was service center of my internet market) falshed it with some firmware and sad do not update it. It helped for 2 days.
5. They replaced the motherboard. Only this can help.
So, if you have bootloop in your stock device - try to falsh it with firmware if it does not help - take it to service center and say that they do not spent their and your time and change device or mother board.
Now its ok, working fine.
Wrote it because I spent a lot of time to repair it and maby it will help to some one.

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.

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.