Database Users

Soft bricked phone, no os, can't flash with odin

Summary: I tried to root my 4.4.2 S4 using an incompatible method by mistake. The phone now has no OS and I am having trouble flashing the stock firmware. When the phone powers on, I see "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The following describes the state the phone was in before the problems occurred...
Model: SGH-I337
Model name: GALAXY S4
Country: USA (AT&T)
Version: Android 4.2.2
Product Code: ATT
PDA: I337UCUAMDL
CSC: I337ATTAMDL
MODEM: I337UCUAMDL
Drivers were properly installed. I had both the Samsung and ADB interface drivers properly installed.
The knitty gritty...
This all started when I attempted to root the phone using djrbliss Saferoot method. Due to there being so many versions of the S4, I misinterpreted the post by djrbliss. Apparently, this method is not compatible with 4.4.2. I attempted to run the .bat file for this method, it hung indefinitely and I killed it. I rebooted the phone and began experiencing issues with my data network. I assumed at this point that the modem had been messed up.
After my failure with Saferoot, I tried to flash back to stock and fix the modem using the files in this thread. I believe some of these files were written successfully, but not all of them because after I booted into Windows, drivers were automatically installed for MSM8960 (snapdragon processor), Samsung Mobile USB CDC Compsite device, Serial gadget driver, Samsung modem.
I tried flashing the I337UCUAMDL firmware but it wouldn't write either.
As a last desperate resort I tried to use Kies to restore the firmware but it wouldn't automatically detect the device so I tried to initiate it manually using the device serial number. The application stopped responding and then the phone had no OS at all.
I am desperately in need of help and will offer a reward (to be sent via paypal) to anyone that can help me.

1. I supose u want keep ur warranty.
2. Go to STOCK RECOVERY (button home + button up + Power button) (like 1st pic)
3. You will see some options there (Wipe all -> wipe data/factory reset + wipe cache partition)
4. Reboot ur phone in DOWNLOAD MODE
5. Open Odin 3.09
6. Flash the firmware u have again -> I337UCUAMDL (like in the 2nd pic attached)
7. Tell me how it works.

Joku1981 said:
1. I supose u want keep ur warranty.
2. Go to STOCK RECOVERY (button home + button up + Power button) (like 1st pic)
3. You will see some options there (Wipe all -> wipe data/factory reset + wipe cache partition)
4. Reboot ur phone in DOWNLOAD MODE
5. Open Odin 3.09
6. Flash the firmware u have again -> I337UCUAMDL (like in the 2nd pic attached)
7. Tell me how it works.
Click to expand...
Click to collapse
I traded for it locally so I could care less about the warranty. I think I may have broken the recovery image because I can't get it to boot into recovery, but I can get it to boot into download mode. Is there any other way to clear the cache?
Thanks for your help.

goose90proof said:
I traded for it locally so I could care less about the warranty. I think I may have broken the recovery image because I can't get it to boot into recovery, but I can get it to boot into download mode. Is there any other way to clear the cache?
Thanks for your help.
Click to expand...
Click to collapse
You will have to flash custom recovery then but this supose lose the warranty.
*EDIT: Before this step, better try to flash the firmware u had before in DOWNLOAD MODE by ODIN

Joku1981 said:
You will have to flash custom recovery then but this supose lose the warranty.
*EDIT: Before this step, better try to flash the firmware u had before
Click to expand...
Click to collapse
Ok so flash clockwork or teamwin right?
I've tried flashing the firmware in every way I could. I'm about to leave work and head home so I will try this soon. If I can get this thing working I won't forget that you were the first to respond when I'm handing out donations.

goose90proof said:
Ok so flash clockwork or teamwin right?
I've tried flashing the firmware in every way I could. I'm about to leave work and head home so I will try this soon. If I can get this thing working I won't forget that you were the first to respond when I'm handing out donations.
Click to expand...
Click to collapse
Exactly you will have to flash one of the 2. I recommend u TWRP (teamwin) -> HERE (flash this file like it was a firmware through ODIN)

his easenga
Joku1981 said:
Exactly you will have to flash one of the 2. I recommend u TWRP (teamwin) -> HERE (flash this file like it was a firmware through ODIN)
Click to expand...
Click to collapse
I was able to successfully flash teamwin recovery and now I'm able to boot into the damaged os (still no modem), but I can't flash the 4.2.2 firmware. It still fails at authentication when attempting to write.
Here's the output from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

goose90proof said:
I was able to successfully flash teamwin recovery and now I'm able to boot into the damaged os (still no modem), but I can't flash the 4.2.2 firmware. It still fails at authentication when attempting to write.
Here's the output from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Show us your download mode screen or tell us what you read in upper left corner. Do you see anything like "warranty bit" or "konx" and a hex number like 0x0 or 0x1? If so, you won't be able to flash a 4.2.2 rom neither your factory rom, you should try newest rom.
Enviado desde mi GT-I9500 usando Tapatalk 2

jaswinky said:
Show us your download mode screen or tell us what you read in upper left corner. Do you see anything like "warranty bit" or "konx" and a hex number like 0x0 or 0x1? If so, you won't be able to flash a 4.2.2 rom neither your factory rom, you should try newest rom.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
It says...
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Official
KNOX Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode enabled
Can someone link a ROM I can use? At this point I just want the modem working again. :/

This normally happens when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc.
The phone can be revived by flashing a pit file to repartition the emmc in order so it can be written to.
1. Download this file and you will have a .pit file which you put in the tab marked PIT in Odin -> HERE
2. Next make sure > r partition, f /reset, and auto reboot are ticked in options in Odin.
3. Next put the STOCK ROM in the tab marked PDA/AP, hit start and start the flashing process.
4. When finished the phone should reboot and start up.

goose90proof said:
It says...
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Official
KNOX Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode enabled
Can someone link a ROM I can use? At this point I just want the modem working again. :/
Click to expand...
Click to collapse
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2

jaswinky said:
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
Problem is that phone i337 only have android 4.2.2 in SamMobile :highfive:
*EDIT: How u have CUSTOM RECOVERY installed. I recommend u flash THIS if you think @jaswinky is right

jaswinky said:
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
It could help if you post the name of the file you wrongly flashed to root. I assume you have att version i337 and not Canadian i337M version (is it right?) , so you will not find a Knox bootloader enabled rom (4.3 or 4.4) in sammobile. But as I see, if you successful flashed a i337M bootloader into your i337, you should be able to repeat it again with a full rom. Maybe you want search in the forum for the i337 and i337M ROM compatibility...
EDIT: Try first the last rom posted by joku1981 in the last post.
Enviado desde mi GT-I9500 usando Tapatalk 2

jaswinky said:
It could help if you post the name of the file you wrongly flashed to root. I assume you have att version i337 and not Canadian i337M version (is it right?) , so you will not find a Knox bootloader enabled rom (4.3 or 4.4) in sammobile. But as I see, if you successful flashed a i337M bootloader into your i337, you should be able to repeat it again with a full rom. Maybe you want search in the forum for the i337 and i337M ROM compatibility...
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I have the US version. I'm not actually with AT&T. I'm with a 3rd party carrier called StraightTalk that simply uses AT&T sim cards and operates on the same network. I have not flashed any Canadian ROMS. The first ROM I tried to flash was a 4.3 ROM. I don't have the file anymore so I don't have the name, but I do know it was 4.3. My thinking at the time was that I didn't need to go all the way back to 4.2 to root the phone, but I obviously made an error in my judgement there. This is the thread I got the root method from that originally screwed up the device (and I'm assuming my APN).
Let me update you guys on the current situation... The phone is now working. Ever since I flashed the teamwin recovery image to the phone I was able to boot into the phone. I'm assuming that at some point I damaged the recovery image and the phone wouldn't boot without it.
I also found that my APN for straighttalk (3rd party carrier) was deleted so I reset that and now I can connect to the data network.
I still want to root the phone if it is possible!

Ty so much :highfive:. Better if u use this method: HERE. Your model is in the list "Tested and worked for". Its very easy process, i think u will have rooted in few minutes. Hi5

goose90proof said:
I have the US version. I'm not actually with AT&T. I'm with a 3rd party carrier called StraightTalk that simply uses AT&T sim cards and operates on the same network. I have not flashed any Canadian ROMS. The first ROM I tried to flash was a 4.3 ROM. I don't have the file anymore so I don't have the name, but I do know it was 4.3. My thinking at the time was that I didn't need to go all the way back to 4.2 to root the phone, but I obviously made an error in my judgement there. This is the thread I got the root method from that originally screwed up the device (and I'm assuming my APN).
Let me update you guys on the current situation... The phone is now working. Ever since I flashed the teamwin recovery image to the phone I was able to boot into the phone. I'm assuming that at some point I damaged the recovery image and the phone wouldn't boot without it.
I also found that my APN for straighttalk (3rd party carrier) was deleted so I reset that and now I can connect to the data network.
I still want to root the phone if it is possible!
Click to expand...
Click to collapse
So you are now in a 4.2.2 rom with the 4.3 bootloader? Or you have 4.3 or 4.4.2 rom? I only know 2 root methods, phil recovery and cfautoroot (this doesn't change your recovery but just temporally), a bit cleaner, but in your situation i wouldn't like to advice you a root method. If you try one, try it on your own risk...
Enviado desde mi GT-I9500 usando Tapatalk 2

Joku1981 said:
Ty so much :highfive:. Better if u use this method: HERE. Your model is in the list "Tested and worked for". Its very easy process, i think u will have rooted in few minutes. Hi5
Click to expand...
Click to collapse
I will give it a try.
jaswinky said:
So you are now in a 4.2.2 rom with the 4.3 bootloader? Or you have 4.3 or 4.4.2 rom? I only know 2 root methods, phil recovery and cfautoroot (this doesn't change your recovery but just temporally), a bit cleaner, but in your situation i wouldn't like to advice you a root method. If you try one, try it on your own risk...
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
No, I'm still where I started (4.4.2). Odin was never able to successfully flash a different rom. It failed everytime. This phone is at 4.4.2 from a legit OTA update so I guess I'm stuck here. Now to root it with 4.4.2

goose90proof said:
I will give it a try.
No, I'm still where I started (4.4.2). Odin was never able to successfully flash a different rom. It failed everytime. This phone is at 4.4.2 from a legit OTA update so I guess I'm stuck here. Now to root it with 4.4.2
Click to expand...
Click to collapse
If you are in 4.4.2, Saferoot not works.
*EDIT: Your model no is rootable with CF-Auto-Root. How im reading:
SGH-i337 -> AT&T: Bootloader locked, do not use CF-Auto-Root on it :/

Joku1981 said:
If you are in 4.4.2, Saferoot not works.
Click to expand...
Click to collapse
Yeah I didn't see that the first time I did it. I'm a bit dyslexic and the first time I read the version number wrong. Are there no root methods available to me at this time?

goose90proof said:
Yeah I didn't see that the first time I did it. I'm a bit dyslexic and the first time I read the version number wrong. Are there no root methods available to me at this time?
Click to expand...
Click to collapse
No is possible root it:
This update contains a new bootloader due to which downgrading to previous stock firmwares WILL NOT BE POSSIBLE.
As of yet, root CAN NOT be retained or acquired on this build (I337UCUFNB1).
Warranty may be void of your device if you follow the procedures given on this page.
You only are responsible for your device. We won’t be liable if any damage occurs to your device and/or its components.
Be relaxed and enjoy ur phone completely official. Hi5

return to kitkat problem

did anyone try to comeback (910C)lolipop (new poland stock rom COJ5) to kitkat (4.4.4) via odin
in Turkish forum some guy tried to comeback ,but he did not success it.I told him what I know about this.
he also used 4 parts rom and pit files ,one part rom and pit files,firstly try to kitkat bootloader via odin etc.etc but he said no,no,no
some guys are saying,now samsung has prevent to return kitkat from COJ5 ,is that true or not
we need alternatives way

hi,still no any idea
guys,I thing samsung putted a bootloader lock to return to kitkat even 5.0.1.
I tried to both of them ,but result no succesed it. that is way ,whom want to return to comeback to kitkat and 5.0.1 bootloader ,they will meet this lock. maybe you want to use miui rom like me .what will I do

I bought a new Note 4 N910G Indian version with LP 5.01. Loaded a custom Rom, Dr.Ketan ROM 5.0.1 after rooting. Got Xposed working but still didnt like it. I then downgraded to Stock Kitkat 4.4.4 from Sammobile site with ODIN. Rooted after loading TWRP again. (Root got disabled on downgrading so had to reroot SuperSu). Loaded Xposed. Everything working smoothly. Only one issue is Lockscreen Widgets which even Xposed is not able to bypass when the phone has PIN or Pattern lock but very happy now. Quite similar to my JB Note 3 N9005 which is what I wanted.

pelase help, any idea, suggestion,etc.
what should I do ,what can I do

i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.

theleftykid said:
i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.
Click to expand...
Click to collapse
do you mean try to change the kernel(kitkat)to return kitkat

mudur1998 said:
pelase help, any idea, suggestion,etc.
what should I do ,what can I do
Click to expand...
Click to collapse
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.

niceguy1430 said:
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.
Click to expand...
Click to collapse
that is good idea I will try it,firstly format evrything in twrp and after that try to flash rom with odin .I know my rom is correct rom.
I will report it

sorry ,no result,one part rom,four part roms,with pit and without pit .
before start I wiped everything in twrp

now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom

mudur1998 said:
now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom
Click to expand...
Click to collapse
any logs on odin?

kerbiii said:
any logs on odin?
Click to expand...
Click to collapse
knox warranty void 1
ap survey 2
sw rev.check fail device 2 binary 1
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> _(N910CXXU1COI4_4files_5.1.1_TUR_Factory_Firmware)(like that I do not rememeber but it is my own firmware) HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried kitkat but have no more odin logs

Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.

niceguy1430 said:
Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.
Click to expand...
Click to collapse
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4

Same problem
I am having the same problem, please advise the solution
please text on Whatsapp +966553270134

mudur1998 said:
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4
Click to expand...
Click to collapse
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW

kerbiii said:
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW
Click to expand...
Click to collapse
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4

mudur1998 said:
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4
Click to expand...
Click to collapse
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again

kerbiii said:
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again
Click to expand...
Click to collapse
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no

mudur1998 said:
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no
Click to expand...
Click to collapse
what im trying to say is, try to flash 5.1.1. custom rom first and from there downgrade to kitkat. have you done trying that?

Sprint S5 Soft-Bricked after trying to install Chainfire Drivers

Hi, I tried to install chainfire on my new S5 after just rooting it and now it's softbricked. I tried flashing the stock firmware after this and I get an error message. Probably a newbie mistake, but I can't seem to get it to work. I have TWRP recovery currently installed.
Heres the error message after trying to install the stock firmware, also have the same problem when trying to use one-click methods.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1BOA6_G900PSPT1BOA6_G900PVPU1BOA6_HOME.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thank you.

Tried just Factory resetting from TWRP?

*Detection* said:
Tried just Factory resetting from TWRP?
Click to expand...
Click to collapse
Yeah, but it just seems to be stuck in the samsung loading screen still.

At a guess, you were already on Lollipop, and that ROM you are trying to flash is older than the version you were running?
Seen this a lot the last couple of weeks with this model S5, not found a solution yet
Try grabbing the latest ROM version from sammobile .com, see if that will flash
Alternatively - grab a custom ROM, wipe everything (system, data & caches), and flash that from TWRP
EDIT - Or from TWRP, go to the file manager, and try and undo whatever it was you did to brick it, (ie: remove the chainfire files from the OS)

*Detection* said:
At a guess, you were already on Lollipop, and that ROM you are trying to flash is older than the version you were running?
Seen this a lot the last couple of weeks with this model S5, not found a solution yet
Try grabbing the latest ROM version from sammobile .com, see if that will flash
Alternatively - grab a custom ROM, wipe everything (system, data & caches), and flash that from TWRP
EDIT - Or from TWRP, go to the file manager, and try and undo whatever it was you did to brick it, (ie: remove the chainfire files from the OS)
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/43152/G900PVPU1BOA6_G900PSPT1BOA6_SPR/ <--- Ok i'm pretty sure this is the one i had already downloaded.

Squege said:
<--- Ok i'm pretty sure this is the one i had already downloaded.
Click to expand...
Click to collapse
Links to sammobile are banned here, you have to link them without them being a link if you get my drift
That ROM you linked is from Jan 2015
This one is from Dec 2015 (2 months old)
G900PVPU3BOK4

*Detection* said:
Links to sammobile are banned here, you have to link them without them being a link if you get my drift
That ROM you linked is from Jan 2015
This one is from Dec 2015 (2 months old)
G900PVPU3BOK4
Click to expand...
Click to collapse
Ohh ok, and my bad. Would you happen to know when the latest version of the stock rom was released?
Alternatively, if I wanted to try a custom ROM what would my best bet be for the g900p?

That is the latest stock for your S5
Some reason the dates are different on the main screen vs the download, but Nov/Dec 2015 anyway
Model SM-G900P
Model name GALAXY S5
Country Spint (cdma)
Version Android 5.0
Changelist 4781399
Build date Tue, 10 Nov 2015 07:37:35 +0000
Product code SPR
PDA G900PVPU3BOK4
CSC G900PSPT3BOK4
Not sure about compatibility of custom ROMs for the G900P, but you could have a look around the CM13 thread, ask in there
http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-13-0-android-6-0-t3237502
There's a list of supported device 'types' not models, so might need a bit of googling

*Detection* said:
That is the latest stock for your S5
Some reason the dates are different on the main screen vs the download, but Nov/Dec 2015 anyway
Model SM-G900P
Model name GALAXY S5
Country Spint (cdma)
Version Android 5.0
Changelist 4781399
Build date Tue, 10 Nov 2015 07:37:35 +0000
Product code SPR
PDA G900PVPU3BOK4
CSC G900PSPT3BOK4
Not sure about compatibility of custom ROMs for the G900P, but you could have a look around the CM13 thread, ask in there
http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-13-0-android-6-0-t3237502
There's a list of supported device 'types' not models, so might need a bit of googling
Click to expand...
Click to collapse
Ok, another thing is could i just run it through Odin? or would i need to have an external SD? because i don't think ill be able to get the file over to the internal SD in it's current condition.

Squege said:
Ok, another thing is could i just run it through Odin? or would i need to have an external SD? because i don't think ill be able to get the file over to the internal SD in it's current condition.
Click to expand...
Click to collapse
ODIN is only for Stock Samsung ROMs. you have to flash Custom from either Internal or External (MicroSD) storage & TWRP / Custom recovery
Make sure not to wipe Internal if you copy it to there though
And yea, it looks like the bootloader is the issue, trying to downgrade to earlier versions of Lollipop with the G900P
http://forum.xda-developers.com/spr...nt/od3-stock-tar-file-odin-flashable-t3128657
I will warn you alot of people are saying once they upgraded to this bootloader they couldnt get OA6 roms to flash so beware.

*Detection* said:
ODIN is only for Stock Samsung ROMs. you have to flash Custom from either Internal or External (MicroSD) storage & TWRP / Custom recovery
Make sure not to wipe Internal if you copy it to there though
And yea, it looks like the bootloader is the issue, trying to downgrade to earlier versions of Lollipop with the G900P
http://forum.xda-developers.com/spr...nt/od3-stock-tar-file-odin-flashable-t3128657
I will warn you alot of people are saying once they upgraded to this bootloader they couldnt get OA6 roms to flash so beware.
Click to expand...
Click to collapse
Ok so if I were to flash this rom, and I just wanted to keep it at stock. would it be the newest version? Because once i fix it i don't plan on flashing it or downgrading for the time being.

Squege said:
Ok so if I were to flash this rom, and I just wanted to keep it at stock. would it be the newest version? Because once i fix it i don't plan on flashing it or downgrading for the time being.
Click to expand...
Click to collapse
All ROMs on sammobile are stock - the newest version, is the one you can see with the most recent date, which for your phone, is G900PVPU3BOK4

Newbie Help ! Flash i337 ATT To stock then to Android 7

Ok ive never messed with android before, and have spent hours n hours etc reading and trying things... and have failed ;(
Tried to play with TWRP or whatever etc... that didnt work
Ive got a S4 ATT i337 that is on 4.2.2 it has some custom FW on it and its UNLOCKED.
I was using this a while back on TMOBILE so it IS unlocked (from AT&T)...
Ive tried to boot into recovery to SET IT BACK to STOCK (1st) then (so I could put it on 7.1)
I get a ATTENTION message that appears and says: System software not authorized by AT&T has been found on your phone. Please turn off and goto the nearest at&t store... (not happing haha)
I Have found the original FW for my ATT I337...
If anyone can help me in simple english of HOW to etc It would be a big xmas present to me !!!
Thanks in advance

Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.

Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
audit13 said:
Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.
Click to expand...
Click to collapse

Transam98 said:
Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
Click to expand...
Click to collapse
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.

Stoney: Thanks for the reply... So I got the terminal an it replied I337UCUAMF3...
Can you tell me the next step ?
(Ill google and get SAFE STRAP)....
what file would I use with safestrap ? Can I still put Android 7.1 on this ?
Thanks in advance !!
StoneyJSG said:
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.
Click to expand...
Click to collapse

If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.

understandable ! Thanks for the info !!
So I have android 4.2.2 on it now (remember at&t i337 S4)....
is there a newer ROM like android 5 or 6 I can put onto it ? (stock ?)
I DID get safestrap and installed that
audit13 said:
If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.
Click to expand...
Click to collapse

Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519

well I screwed up LOL ;(
I did a backup of my ROM with safestrap (its on the SD Card) and tried to write the file and now phone is stuck on attention yellow symbol ;(
I CAN boot into the DOWNLOADING but odin just sits there ;(
I guess phone now = garbage ;(
audit13 said:
Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519
Click to expand...
Click to collapse

does the phone appear as a com port in Odin? You're using the original Samsung USB cable?

the phone DOES appear in odin
Im using a motorla cable but does still fully work....
I also can get the phone into DL mode (pwr down,home,power)
and it WILL take a Download....
when it boots up it does says SAMSUNG and CUSTOM and a UNLOCKED Padlock...
But I guess I cant find the correct files ;( as it always goes to the attention from att detected blah blah blah software....
Id just be happy to get this to the newest ATT Stock FW and then unlock it I believe it is called 4.4.2 and im on 4.2
or IF it exists would be nice to get to at least 5.0 to use android auto
audit13 said:
does the phone appear as a com port in Odin? You're using the original Samsung USB cable?
Click to expand...
Click to collapse

Did you try flashing a stock rom from sammobile.com?

Ive downloaded : I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
(from sammobile)... 2.49Gb
but rememeber my bootloader says (ends in MF3) and the only TWO on sammobile are MDL and MDB..
but of course the file name has MDB in it..... I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
I loaded it in Odin3 (run as admin) and clicked AP and loaded it there, and it fails:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Id really love to get this going If you or someone can help/make suggestions for me to try as im pulling my hair out ;(
audit13 said:
Did you try flashing a stock rom from sammobile.com?
Click to expand...
Click to collapse

Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814

is there anything I can do ? It DID have a custom rom on it (well when it starts booting it says CUSTOM and has a padlock unlocked) and it was also unlocked (not stuck to at&t)... but now im just stuck with that attention logo ;(
audit13 said:
Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse

I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?

I believe it was somewhat a stock firmware, nothing looked "fancy" compared to a regular at&t firmware but it was DEF unlocked as I used to have a tmobile sim in it ....
but it still boots up with SAMSUNG and a unlocked padlock and then the samsung ring animation, then the AT&T logo, now it just boots u the samsung unlock "custom" and then to the yellow exclamation point about non at&t software.
audit13 said:
I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?
Click to expand...
Click to collapse

Were you able to try the methods outlined in the referenced thread to revive and update the phone?

I tried them but none of them work
audit13 said:
Were you able to try the methods outlined in the referenced thread to revive and update the phone?
Click to expand...
Click to collapse

Samsung S4 SGH I337(Don't know the PDA it's running on) hangs on AT&T logo.

Dear All,
I have been reading many threads for a week before I decided to post a new thread here.
I am running in a big problem here with my S4 SGH-I337 which I have. I have never updated it with any version and it's hanging on it's ATT logo. I have tried all the factory and data reset options which I have come across on this forum, but the phone didn't come back to life.
Then I tried to flash it with Odin using I337UCUAMDB tar file(Since the phone is not working I couldn't find the PDA its running on), but it's failing saying FAIL! (Auth). Since I am doing it first time and I don't know much about flashing things, I am stuck out here. After doing some research I found that I should flash it with the PDA version matching to my phone but since my phone is not booting up I am not sure how can i find the PDA version for my phone. Even I have tried reaching to SAMSUNG's authorized center but they replied, as you are in INDIA and your phone was purchased when you were in USA, so we don't have that software to repair it. Please help me as I don't know what to do this phone now. Your help would be greatly appreciated.

Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.

StoneyJSG said:
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
Click to expand...
Click to collapse
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.

mahendra_bhawsar said:
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
Click to expand...
Click to collapse
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.

StoneyJSG said:
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
Click to expand...
Click to collapse
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.

Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?

mahendra_bhawsar said:
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Click to expand...
Click to collapse
I downloaded I337UCUAMDL firmware from http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip but when I flesh it using ODIN it says FAIL(!Auth). Here is the ODIN Log: <ID:0/004> Added!!
<ID:0/004> Removed!!
<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> Added!!
<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> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me what should I do in this case.

audit13 said:
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
Click to expand...
Click to collapse
Nope, It does not say anything about Knox in the download screen. I see model number(SGH-I337) on the hardware underneath the battery.
Thank You!

The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.

audit13 said:
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
Click to expand...
Click to collapse
I think I have purchased this cell phone back in Sept 2013, that time I believe AT&T had the following versions:
Build Date: 27.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDL Changelist: 453947 Android: 4.2.2
Build Date: 09.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDB Changelist: 440216 Android: 4.2.2
I tried both of them using both the ports of my laptop with different USB Cables(Original cable from Sony, Samsung and Moto G), but every time I got the same Odin Fail (!Auth) error. I am not sure whats the wrong here or what should I do to resolve this error and get the phone working.
Thank You!

What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?

audit13 said:
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
Click to expand...
Click to collapse
I think it was Android 4.2.2, this is what the download mode says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNAL LOCK: 0*0
KNOX WARRANTY VOID: 0*0
CSB-CONFIG-LSB: 0*30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thank You!

The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.

audit13 said:
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
Click to expand...
Click to collapse
Ohh I understand this now. But knox says 0*0 bit still it means it has a locked bootloader ? I think may be it was running on 4.3 before it crashed, may be I had got some update on 4.2.2 and that made it got updated on 4.3 which I didn't re-collect. What should I do now, which ROM you would suggest me to flash it with. Really appreciate your help.
Thank You!

If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221

audit13 said:
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
It has lots of ROMS and instructions to follow, I am a novice user in this so got confused what to do and what not. Even I don't know my current baseband version so unable to choose firmware or method to flash it in order to get it working. Any help from your side on this front ?
Thank You!

You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197

audit13 said:
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
Click to expand...
Click to collapse
My phone is in hanging state on boot loop won't be able to perform the steps mentioned on that link like : 1. Place the ROM onto your device (use either internal or ext-sdcard). etc... Any other suggestion please ?

You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.

audit13 said:
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
Click to expand...
Click to collapse
Great! Thanks I am trying to download it, it will take time since my network is a bit slow, will let you know if that works, hopefully it should.