Database Users

The end of my S4? (Brick/dead) - Help..

Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated

lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.

donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH

lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.

lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression

samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!

lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe

@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.

@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.

lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware

samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??

lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.

samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!

[Q] Help, Odin stuck at system.img.ext4

Tbh, i found lots threads with the same problem but i couldn't solved mine.... anyway im on SM-9005
Story behind
I was trying to flash Lollipop 5.0 Stock ROM(using ODIN 3.09) [email protected]
and i gotten a huge red FAIL. somehow i manage to get myself to download mode again so without thinking twice i simply flash 4.4.2 stock ROM.
Succeed! but i gotten stuck at Samsung logo, this is where i regretted that i didn't wipe my data,etc via CWM but instead of that i went re-flash the same 4.4.2 stock ROM and now forever stuck at system.img.ext4.....
i tried flash CWM and wipe things up, does not work..
highly appreciate if someone would help me solve this :crying:
p/s.please pardon my english, its not my native tongue language.

elSpade said:
Tbh, i found lots threads with the same problem but i couldn't solved mine.... anyway im on SM-9005
Story behind
I was trying to flash Lollipop 5.0 Stock ROM(using ODIN 3.09) [email protected]
and i gotten a huge red FAIL. somehow i manage to get myself to download mode again so without thinking twice i simply flash 4.4.2 stock ROM.
Succeed! but i gotten stuck at Samsung logo, this is where i regretted that i didn't wipe my data,etc via CWM but instead of that i went re-flash the same 4.4.2 stock ROM and now forever stuck at system.img.ext4.....
i tried flash CWM and wipe things up, does not work..
highly appreciate if someone would help me solve this :crying:
p/s.please pardon my english, its not my native tongue language.
Click to expand...
Click to collapse
First thing - can you get back into Download mode?
If so take out battery and leave things for a while. Then when you put battery back in, hold down the DL mode keys and enter DL. Then connect phone to computer and in Odin, flash your Stock v5
You could also DL the Odin-flashable version of CWM or TWRP and flash that before you restart. (untick the Reboot option in Odin BEFORE you flash the firmware)

Journyman16 said:
First thing - can you get back into Download mode?
If so take out battery and leave things for a while. Then when you put battery back in, hold down the DL mode keys and enter DL. Then connect phone to computer and in Odin, flash your Stock v5
You could also DL the Odin-flashable version of CWM or TWRP and flash that before you restart. (untick the Reboot option in Odin BEFORE you flash the firmware)
Click to expand...
Click to collapse
Yes i can go to DL Mode, and when i flashed Stock v5, got stuck mid way
this is what on my ODIN (tried both 3.07 and 3.09)
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNH1_N9005OLBGNH1_N9005XXUGNH1_HOME.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
btw usually i left the PIT empty, but there's some thread suggested it, i try both. still stuck

elSpade said:
Yes i can go to DL Mode, and when i flashed Stock v5, got stuck mid way
this is what on my ODIN (tried both 3.07 and 3.09)
...
btw usually i left the PIT empty, but there's some thread suggested it, i try both. still stuck
Click to expand...
Click to collapse
What phone do you have?
Do you know which region it is from?
I think that firmware is Austria and some of the Asian phones seem to have different partitions.
Also have you tried re-downloading the file - sometimes zips get corrupted.

Journyman16 said:
What phone do you have?
Do you know which region it is from?
I think that firmware is Austria and some of the Asian phones seem to have different partitions.
Also have you tried re-downloading the file - sometimes zips get corrupted.
Click to expand...
Click to collapse
i bought from Malaysia? Asian that is.
i tried Hong Kong firmware, same problem but i have not tried re-download the HK Firmware, i try re-dl but might takes about 2hours

elSpade said:
i bought from Malaysia? Asian that is.
i tried Hong Kong firmware, same problem but i have not tried re-download the HK Firmware, i try re-dl but might takes about 2hours
Click to expand...
Click to collapse
While you wait, search Q&A for 'boot loop odin' and have a read...

trying to uninstall cyanogen mod to go to stock

Hey I am trying to uninstall cyanogen mod on my galaxy s4 so that I can return it to stock to sell it. I was following this guide techbeasts.com/how-to-unroot-samsung-galaxy-s4-all-versions/
I downloaded my firmware off of samsungs site the newest firmware available for my phone. I tried to restore it and it gave me an error about xmitdata fail so I had to unplug the phone and try again. Now if I try and boot up the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. If I try and reflash it in odin I get this far now and it freezes...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOH1_I337MOYAGOH1_I337MVLUGOH1_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> aboot.mbn
any ideas please? and thankyou!

Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.

audit13 said:
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
Click to expand...
Click to collapse
Sorry should have put that behind my battery it says sgh-i337m

Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.

audit13 said:
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
Click to expand...
Click to collapse
yes original cable, it doesn't error it just freezes there. in Download mode it says this:
Odin Mode
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-Config-Lsb: 0x30
Secure Download: Enable
Write Protection: Enable
eMMC Burst Mode enabled
I downloaded my firmware from sammobile.com and looked up the SGH-I337M and chose the one for Fido Canada as that is what I have

Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.

audit13 said:
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
Click to expand...
Click to collapse
I have tried different port and I don't have another cable, and does that mean I could download like a bell firmware and try that instead?
or is there a way that reinstalling cyanogenmod would fix it and somehow wipe my personal info? that's all I really need to do

Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?

audit13 said:
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
Click to expand...
Click to collapse
Ok downloading now to try, but ya its freezes the progress bar on phone doesn't move and the Odin app just sits there at aboot.mbn

I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.

audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
ya I downloaded latest firmware.... and phone encrypted I don't no....

Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.

audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
audit13 said:
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
Click to expand...
Click to collapse
I will try this now and post back...
I don't think this is good stuck with this....
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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> recovery.img

Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?

audit13 said:
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
Click to expand...
Click to collapse
yes, that was while trying twrp, I managed to borrow another cable and got the firmware installed it said passed but phone gets stuck during boot up, I installed twrp now what shall I do install cyanogen again?

If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.

audit13 said:
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
Click to expand...
Click to collapse
I did a factory wipe and rebooted and it froze ive tried 3 or 4 times now it is upgrading 29/89 will post back if it works..
got it booted up and now its asking for set up, I appreciate your patience and help very much

Flash stock again but do not check anything except f.reset time, flash stock rom, when you see the word pass in the status window, remove USB cable, remove battery and wait 5 seconds, replace battery, boot into recovery, factory wipe, reboot.

thanks ill do that if I have a problem, for now phone is up and running and ready for use

That's great news. I guess all you needed was a different USB cable. I find the s4 to be very picky about USB cables when using Odin.

Reflashing stock rom

I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.

mrnice10033 said:
I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.
Click to expand...
Click to collapse
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
unfortunatly, I've tried this multiple times and still cannot get it out of the boot loop. I'm not booting back into recovery but rather to the Samsung logo now.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
I've done this as well with no success.

And if you are not waiting for the necessary time you need to load the system? .. since after installing the stock you have to leave this in the samsung logo about 10 to 20 minutes at least

One thing to note is that you should be flashing AP, BL, CP, and CSC, and not the HOME package only (not sure if your variant has it in the first place!). Also, ensure that the "NAND Erase All" option is ticked before performing the flash.

thank you, I have not tried ticking nand flash before but I will try it.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
This is what I'm seeing on Odin
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.

mrnice10033 said:
This is what I'm seeing on Odin
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.
Click to expand...
Click to collapse
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!

https://drive.google.com/drive/folders/0B8346PsUO8X8cUE1QkZMOGI2SmM?usp=sharing
Try this!

Rizzed said:
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!
Click to expand...
Click to collapse
Thank you so much. I appreciate it.

Soft Bricked S4

*****************Thread can be closed as issue has been resolved*****************
I think I have soft bricked my phone.
I tried this tutorial and everything went according to the instructions except that the wifi couldn't be turned on.
So I opened a thread asking for help regarding my wifi, I was advised to flash a custom ROM (Android 5.0.1 Lollipop SDK 21) thru TWRP but I must have done something wrong because the phone was stuck in Android System Recovery.
Then I was advised to flash the original firmware thru Odin (Android 4.2.2) and that's where I think the brick happened.
The phone can go into download mode but there is a gray line that says "Write protection: Enable" and everything I try to flash thru Odin gives the same fail error:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Urgent help is much appreciated as I have no other phone and I have been incommunicated for a week+ now
UPDATE:
I just tried to go into Android System Recovery just now it worked! I swear I wasn't able to. It says on top:
LRX22C.I337UCSGOK3 (I was on NB1, where could have this come from?)
And has a couple extra options I had never seen before (last 3 or 4 from the list:
reboot system now (tried it and gets stuck on Samsung logo)
apply update from ADB
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Enable cp logging
Disable cp logging
At the end of the recovery screen there are 2 lines in red:
failed to mount "/system" (Invalid Argument)
E: failed to mount /system (Invalid Argument)

What is the model # in download mode?

audit13 said:
What is the model # in download mode?
Click to expand...
Click to collapse
It says:
Product Name: SGH-I337
PS: Sorry I didn't specify because I thought this forum section was only that model.

The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​

audit13 said:
The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​
Click to expand...
Click to collapse
Mine is not the "M" version.
What am I supposed to get from those notes? Are you suggesting I follow the steps in that thread?
I'm not too technical, but I can follow steps.

If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)

What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
I am on NB1, will try this tru Odin and will report back.

StoneyJSG said:
What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.
Click to expand...
Click to collapse
Is the bootloader that one at the top of the Android System Recovery? If so, mine says:
LRX22C.I337UCSGOK3

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
It seems that I already had tried this because when I extracted the file it had to be replaced on my Desktop. Anyways I tried it again and it said the same thing:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

UPDATE:
Somehow I can go into recovery now and it says LRX22C.I337UCSGOK3 and unable to mount /system. Please refer to first post for complete info about this.

Publish the Odin log of possible.
You tried using different usb cables and usb ports?

audit13 said:
Publish the Odin log of possible.
You tried using different usb cables and usb ports?
Click to expand...
Click to collapse
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.

Holy_Purple said:
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.
Click to expand...
Click to collapse
OMG! I tried a new cable and it went thru!!! I cannot believe my eyes! and the wifi is working!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> non-hlos.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.

StoneyJSG said:
You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.
Click to expand...
Click to collapse
Thanks for the info! I won't be messing with my phone any more, haha :victory:

Glad you got it fixed
I always have a few Samsung cables on hand for flashing.