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] No OS installed

I have
SM-G900P UD
SW: ND2
Last rom.MOAR v2.0
from within TWRP, I wiped internal storage, not knowing it would wipe EVERYTHING, it then said no os installed. I have searched and can only find a stock image on sam mobile, but it downloads at like 15kb/s then fails after a few hours. Does anyone know where i can find the image elsewhere?
I also cannot enter twrp after i reset it, BUT i can get into download mode. So i am a bit stuck now. Odin cannot be used without usb debugging right?

/
Ki11ian said:
I have
SM-G900P UD
SW: ND2
Last rom.MOAR v2.0
from within TWRP, I wiped internal storage, not knowing it would wipe EVERYTHING, it then said no os installed. I have searched and can only find a stock image on sam mobile, but it downloads at like 15kb/s then fails after a few hours. Does anyone know where i can find the image elsewhere?
I also cannot enter twrp after i reset it, BUT i can get into download mode. So i am a bit stuck now. Odin cannot be used without usb debugging right?
Click to expand...
Click to collapse
You can push a rom to the phone in recovery if you have the /android-sdk/platform-tools/ installed. In CMD type: adb push namerom.zip /sdcard/. Or sideload a rom in recovery in the sideload option, place the rom in the platform-tools folder and in cmd type: adb sideload namerom.zip. First reflash TWRP with Odin off course.

gee2012 said:
/
You can push a rom to the phone in recovery if you have the /android-sdk/platform-tools/ installed. In CMD type: adb push namerom.zip /sdcard/. Or sideload a rom in recovery in the sideload option, place the rom in the platform-tools folder and in cmd type: adb sideload namerom.zip. First reflash TWRP with Odin off course.
Click to expand...
Click to collapse
But recovery is not there anymore, download mode is all i can go to, otherwise is just sits at the 'Samsung S5 powered by android' screen forever

Ki11ian said:
But recovery is not there anymore, download mode is all i can go to, otherwise is just sits at the 'Samsung S5 powered by android' screen forever
Click to expand...
Click to collapse
Flash a custom recovery with Odin in downloadmode as i explained in the first post and then use adb sideload in recovery mode.

gee2012 said:
Flash a custom recovery with Odin in downloadmode as i explained in the first post and then use adb sideload in recovery mode.
Click to expand...
Click to collapse
I'm having to same problem as the first person except when I try to flash the stock firmware through ODIN, it keeps failing. Can you help?

cdickerson1185 said:
I'm having to same problem as the first person except when I try to flash the stock firmware through ODIN, it keeps failing. Can you help?
Click to expand...
Click to collapse
Make sure the correct drivers are installed and terminate KIES in windows task manager before you flash with Odin.

gee2012 said:
Make sure the correct drivers are installed and terminate KIES in windows task manager before you flash with Odin.
Click to expand...
Click to collapse
Alright, so I killed kies through windows task manager but odin is still failing. i keep getting this same message:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900PVPU1ANE5_1750661_REV00_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I just want to restore to stock, my device might be soft-bricked. I'm no sure

cdickerson1185 said:
Alright, so I killed kies through windows task manager but odin is still failing. i keep getting this same message:
I just want to restore to stock, my device might be soft-bricked. I'm no sure
Click to expand...
Click to collapse
Just flash phillzz recovery in odin.
Root your device with the latest supersu.zip (google it)
Get a micro sd
Put from your pc any android rom on your sd card
Flash as instructions from other rok developer.
Then you are at a custom rom
From there on
Download stock firmware from samsung
Flash using odin.
Then you should get back on stock again
Sent from my klte using XDA Free mobile app

This happens to me I have twrp installed and I want root and custom rom its t mobile also but do I just put supersu zip on micro sd card and custom rom then boot into twrp and install both? Help Please

For those having this issue check this :
http://forum.xda-developers.com/showthread.php?t=3326344
Sent from my SM-G900F using XDA Free mobile app

[Q] How to Root on G900FXXU1BNL7 5.0?

Hello I was trying to root my G900F that is currently running Lollipop BNL7 with CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug but Failed at the end of the process. Had to restore stock G900FXXU1BNL7 to get phone back working.
Try it two times always fails at the end.
Any other method or have to wait for updated version of CF-Auto?
Does G900FXXU1BNL7 is rootable?
Is there a way to downgrade to 4.4 safely as I try already and end up in nightmare and dont have EFS backup that is why I want to root first.?
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

egejo said:
Hello I was trying to root my G900F that is currently running Lollipop BNL7
Click to expand...
Click to collapse
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.

Reactivation lock
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think you already enable (Reactivation lock) from setting --> security
Just uncheck the option and i hope it will work fine

Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
lingowistico said:
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Click to expand...
Click to collapse

egejo said:
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
Click to expand...
Click to collapse
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.

i cant install recovery mode on bnl7 . Tried it whole day and all i get is stock recovery mode.
Help ?

lingowistico said:
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
Click to expand...
Click to collapse
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Lastly to let you know that now I'm in Stock G900FXXU1ANCE, dowgraded from BLN7 to BLN2, then ANJ1 and then ANCE. On all of them I have been trying to root or put a custom recovery, used CF-Auto-Root-klte-kltexx-smg900f, openrecovery-twrp-2.8.1.0-klte or philz_touch_6.57.8-klte with same results always Failing Odin at the end of process... The thing I notice is that always it shown on the dowload mode screen
"QUALCOMM SECURE BOOT: ENABLED (CSB)"
Even after downgrade, could these be the issue?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...

egejo said:
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
Click to expand...
Click to collapse
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762

pnr2020 said:
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
Click to expand...
Click to collapse
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?

egejo said:
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Click to expand...
Click to collapse
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root

lingowistico said:
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
Click to expand...
Click to collapse
I cant flash any custom recovery at all it always fails and softbricks the phone... Looks like these G900F is now bootloader Locked...
If so samsung is now selling them from factory locked not just ATT versions...

egejo said:
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
Click to expand...
Click to collapse
dont know to be honest mine only 2 weeks old from uk was on BTU but now on polish version

egejo said:
Looks like these G900F is now bootloader Locked...
Click to expand...
Click to collapse
I don't think so, everything works fine for me..

i also cant install recovery but i dont get soft bricks , just normal stock recovery mode all over.

"qualcomm secure boot: Enabled (csb)
hello everyone
if you got error in odin when flash any custom recovery just deactivate reactivation lock from setting>security.

[Q] Odin FAIL - N910U / From Hong Kong 4.4.4 to Taiwan 5.0.1 ROM

Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?

gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4

Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)

I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system

stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"

gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox

I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse

stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.

a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk

stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..

gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)

stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.

Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.

@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered

Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]

Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else

gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user

Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?

gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes

How do you even flash the hidden.img,ext4 files through odin?

[Q] -CM- What to update to

Hi guys, I have a Samsung Galaxy S4 from Canada, specifically Rogers. The phone is currently on the CM11 Nightly ROM. (I can check specifically which nightly, my phone is just backing up at the moment so I can't see!)
I have this problem, which is, when the phone automatically locks or I myself lock it, the radio signal completely drops. Sometimes the signal will come back, but to get it back for sure is to turn the phone on airplane mode then off again. It is annoying because when the phone is locked for a while, it will receive signal at some point. During that time I'll get a call and it'll ring but once the screen turns on the signal will drop, also dropping the call. I have a slight understanding that it could be a problem with the phone's radio firmware?
Now that you guys have an understanding about my problem, this is what I am hoping to accomplish. I want to update the phones ROM, as it is probably old, along with the proper fix to the phone's radio firmware. How do i go about doing this? The kind of ROM that I want is something in between stable version and nightly (not nightly as I think nightly was the one that caused my radio problem), I think that's SNAPSHOT M12? Please correct me if I am wrong. I would rather not lose any of my data but if I have to then I will but please do guide me because I am scared to lose any of my data.
Thank you guys for reading my long post, I hope my English and grammar is fine! I look forward to hearing from you guys!

The current version of Cyanogenmod is 12.1 (Android 5.1.1). The two release channels for 12.1 are nightlies and snapshots. As of yet there has been no CM12.1 snapshot I'm aware of, meaning all CM12.1 ROMs are nightlies.
You haven't said what version of the stock ROM you had before moving to CM11, but if the radio is too old, you'll want to update it. You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.

Thanks for the reply!
Strephon Alkhalikoi said:
You haven't said what version of the stock ROM you had before moving to CM11
Click to expand...
Click to collapse
I don't know how to answer this, It's been quite a long time since I moved to CM11. Basically what I did was, when I bought the phone I went home and installed CM11 on it, haha.
Strephon Alkhalikoi said:
You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
Click to expand...
Click to collapse
I am quite confused, sorry. What I'm doing right now is I'm downloading the newest radio firmware from the link you have given me. After that I'm going to follow the instructions of:
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
That will fix my radio problems?
Now to update my ROM. This is where I am mostly confused. In your opinion, should I stick with CM11 Nightly? Can I somehow go from nightly to a more stable version like cm11 snapshot m12? Should I update to CM12? Will my phone keep up with the CM12 ROM?
Strephon Alkhalikoi said:
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Click to expand...
Click to collapse
Sorry I will keep that in mind! Mind you, I carefully chose this and looked at all my other options. I didn't see the AT&T forum to fit because AT&T is in the United States and my carrier is in Canada, I just didn't want to have problems with anything else

Guys, I think i screwed up.... So when i downloaded that firmware from Sammobile. I flashed it with ODIN and made sure re-partition was not checked. Everything looked fine and when my phone rebooted (its still rebooting at the moment) the welcome screen was the default "samsung" splash screen, not the Cyanogen Mod . I thought this method was only going to flash the phone's modem, not the ROM too
EDIT:
No....my worst nightmare came true .........NO!!!!
So my phone finished rebooting and its just a black screen. All I can see is the status bar at the top right that displays the WiFi signal and the Phone's network signal and the battery. Okay so I figured something out. When the phone is locked and I press the Home button, Battery Doctor's charging wallscreen shows up, meaning my device wasn't wiped ? When I tried to unlock from Battery Doctor's charging screen, it would just show the black screen with just the status bar .... PLEASE HELP ME !!!

It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.

Strephon Alkhalikoi said:
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Click to expand...
Click to collapse
D'awww Well I guess a clean slate isn't so bad. I backed up my text messsages and my photo's should be backed up onto the google drive anyways. I don't know if you saw my edited post but the UI is not loading. Its just showing the status bar at the top right (signal, wifi signal, battery).
Thanks.

If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
EDIT: ROM installs don't wipe data when done through Odin unless you tell Odin to partition the device. Thus you'd need a factory reset to ensure Touchwiz works. But where you're going to put Cyanogenmod on, don't worry about Touchwiz.

Strephon Alkhalikoi said:
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
Click to expand...
Click to collapse
The problem is, I can't. There's nothing there on the phone. Its just a black screen. Unless, thats what you meant.
I tried searching for a CM 12.1 Canadian version and I found this thread. http://forum.cyanogenmod.org/topic/104233-jfltesgh-i337m/
apparently theres no canadian version of the CM 12.1
what should I do ?

Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.

Strephon Alkhalikoi said:
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Click to expand...
Click to collapse
Thanks for the replies! I'm sorry if im asking for too much but could you please confirm that this is the right one? link
So, I don't need to root? how can i verify that my phone is still rooted? If my phone is still rooted, I download Canadian Galaxy S4 SGH-i337M (Bell, Rogers, Telus) – CWM Recovery v6.0.4.4
Then flash that with Odin ?
edit: I think I know why this failed miserably....On Odin V3.10.6 I clicked "AP" for some reason, when I was flashing the firmware. Could that be the problem? If so, is there a fix ? i can't access my phones SD card .

Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.

i just installed cm-12.1-20150625-NIGHTLY-jfltexx on my s4 with cm-12.1-20150623-NIGHTLY-jfltexx but there is a problem with the phone functions. It can't make any call. .it do not find my sim card!! Same thing with cm-12.1-20150624-NIGHTLY . The last one that works is 20150623 . Is there anyone that can confirm my problem?

Strephon Alkhalikoi said:
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
Click to expand...
Click to collapse
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.

flipboi15 said:
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
Click to expand...
Click to collapse
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.

Lennyz1988 said:
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Click to expand...
Click to collapse
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!

Flashing CM is easy. It doesn't require root access because this phone has no bootloader lock. Download a custom recovery with TAR file format, install drivers, go to the download mode of your phone, connect your phone to your computer, and use Odin to flash the recovery. Then copy CM zip file to a SD card and flash it in recovery. That's all!?
For recovery I recommend TWRP: teamw.in
If you've installed Kies you should have drivers on your computer. Otherwise install Kies or only drivers if you can find them on Samsung official website.

flipboi15 said:
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Use a different usb port / different usb cable.

Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.

flipboi15 said:
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
Click to expand...
Click to collapse
Try redownloading the .zip file. Maybe it's corrupt.

So after trying to install the ROM in TWRP and failing. I couldn't load up the phone anymore, it got stuck at the Samsung Logo screen. I am now re-flashing I337MVLUGOC4 - 5.0.1 Lollipop.
edit:
So at the moment, my phone is working fine on stock rom. I redownloaded the CM-12.1 optimized. I moved it into my SD card. I need to know if there are certain steps I need to do to get this right. These are the steps I took the first time.
Rebooted into TWRP recovery mode, then clicked install then I navigated to the CM-12.1 ROM zip and swiped to install.
Was I supposed to wipe anything? The only time I wiped(the default wipe in twrp) was after I installed the 5.0.1 Lollipop firmware. By the way, i noticed that my phone's internal memory is almost full, it only has 2GB of 9.69GB left in the internal. I checked it out and all my old files were still there!