Database Users

SGS4 won't boot....

Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx

vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?

thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.

vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85

All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.

vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work

yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?

vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.

still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...

vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.

no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help

vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> 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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium

First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx

this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app

bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.

Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app

Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol

DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.

vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it

ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!

[Q] Modem Upgrade Problem

When upgrading to the new 4.4.2 of my I9505 I had to flash the new Bootloader and Modem XXUFNA5.
I flashed the boot loader, but when I tried to flash the Modem with Odin 3.09 I got stuck. The Phone is booting and working fine but I can't make calls. I downloaded the modem file (h GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUEMJ5.tar) from several sources and flashed them without success. I tried to flash other modems and roms also without success. The things I can flash with odin is the Bootloader and CWM.
Anybody has an Idea what to do because I run out of them.
Thanks

lubluchka said:
When upgrading to the new 4.4.2 of my I9505 I had to flash the new Bootloader and Modem XXUFNA5.
I flashed the boot loader, but when I tried to flash the Modem with Odin 3.09 I got stuck. The Phone is booting and working fine but I can't make calls. I downloaded the modem file (h GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUEMJ5.tar) from several sources and flashed them without success. I tried to flash other modems and roms also without success. The things I can flash with odin is the Bootloader and CWM.
Anybody has an Idea what to do because I run out of them.
Thanks
Click to expand...
Click to collapse
Download and extract this file and flash it via odin by selecting Phone/CP. Have a nice day.

Repulsa said:
Download and extract this file and flash it via odin by selecting Phone/CP. Have a nice day.
Click to expand...
Click to collapse
Thank you for your reply, however I had the result:
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying:

lubluchka said:
Thank you for your reply, however I had the result:
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying:
Click to expand...
Click to collapse
Since you already have a newbootloader since after flashing the 4.4.2 leak bootloader then feel free to flash a stock 4.4.2 leak again and you need to follow this ,
INSTRUCTIONS download https://mega.co.nz/#!rIJxHTRB!ZxMSDwtDsVBD5Aw-jt9DvRiKuyEm8hdjW7Mv9eriNiI . Remember flashing this wont let you dowgrade into 4.3 stock Official rom.and your warranty is now voided.
- Extract (unzip) the firmware file
- Download Odin3 v3.09
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart 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 AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to AP
- Add BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to BL
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!

Repulsa said:
Since you already have a newbootloader since after flashing the 4.4.2 leak bootloader then feel free to flash a stock 4.4.2 leak again and you need to follow this ,
INSTRUCTIONS download https://mega.co.nz/#!rIJxHTRB!ZxMSDwtDsVBD5Aw-jt9DvRiKuyEm8hdjW7Mv9eriNiI . Remember flashing this wont let you dowgrade into 4.3 stock Official rom.and your warranty is now voided.
- Extract (unzip) the firmware file
- Download Odin3 v3.09
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart 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 AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to AP
- Add BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to BL
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Click to expand...
Click to collapse
Thank you for taking the time to help me.
I already downloaded this file and tried to flash it. However I am getting the same result. After flashing the BL and when Odin starts to flash the AP file I get stuck!
It is the first time something like this happens to me and I can't figure out why the flash of anything other than the BL is failing. No clue whatsoever

lubluchka said:
Thank you for taking the time to help me.
I already downloaded this file and tried to flash it. However I am getting the same result. After flashing the BL and when Odin starts to flash the AP file I get stuck!
It is the first time something like this happens to me and I can't figure out why the flash of anything other than the BL is failing. No clue whatsoever
Click to expand...
Click to collapse
Try to boot into recovery (Power+Volumeup) do a wipe cache and factory reset after reboot quickly hold and press Power+volumedown in order to reboot download mode and try to select this files in odin and select the right place ap/cp/csc connect your cables to Pc/phone and press start. , im not really sure why is your phone is not allowing to flash any modem. but give this a try.
Add AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 to AP
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MU LTI_CERT.tar.md5 to CSC

Repulsa said:
Try to boot into recovery (Power+Volumeup) do a wipe cache and factory reset after reboot quickly hold and press Power+volumedown in order to reboot download mode and try to select this files in odin and select the right place ap/cp/csc connect your cables to Pc/phone and press start. , im not really sure why is your phone is not allowing to flash any modem. but give this a try.
Add AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 to AP
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MU LTI_CERT.tar.md5 to CSC
Click to expand...
Click to collapse
I just did what you told me and here is what I got:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

lubluchka said:
I just did what you told me and here is what I got:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Make sure kies is not running in background
Try changing ports
Use diffnt cable

Repulsa said:
Make sure kies is not running in background
Try changing ports
Use diffnt cable
Click to expand...
Click to collapse
I changed ports, cables computers....
It is really a puzzle!

Note 3 SM-N9005 Firmware Issue & Device Recognised As 'Samsung GT-S5690'

Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone

Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..

hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?

Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?

hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?

Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?

When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..

hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone

Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.

I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).

xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.

xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.

madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone

Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.

please help sorta bricked

I still have TWRP running but I cant install anything from the micro-sd card. Before I started I used twrp for a backup it showed that it made a backup well I trusted it and didn't go look on sd card to see if it was there my mistake its not there, then I tried going with another rom I downloaded Super_S4_Odexed_NAE_v1.5.zip well it wasn't working so then i downloaded Stock-MDL-Stable-spr-TW.zip( its supposed to help for the rom downloaded) and loaded it on my sd card with my pc well i put micro-sd card in phone and it wont read it so I can install with twrp I also tried odin with stock mdl.tar and it fails, so what I need to know is how to start over with wipe and get something i need so it will read at boot up( do i need a bootloader?)and my files from sd card it reads all but my downloaded zip files
my system is a Sprint Samsung Galaxy S4
original stock was L720VPUAMDC.tar
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Flash back MDC tar, it's the best base.
Sent from my SM-N900P

dr.faramroze said:
Flash back MDC tar, it's the best base.
Sent from my SM-N900P
Click to expand...
Click to collapse
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Have you tried heimdall or one click unbrick tool
Howiewowie said:
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried heimdall or the one click unbrick tool? One click unbrick is based on heimdall. Please try this. http://forum.xda-developers.com/showthread.php?t=1153310

ashikrobi said:
Have you tried heimdall or the one click unbrick tool? One click unbrick is based on heimdall. Please try this. http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
it does not read my Samsung it does not show in the list and I do have drivers installed on my pc

Howiewowie said:
it does not read my Samsung it does not show in the list and I do have drivers installed on my pc
Click to expand...
Click to collapse
Download heimdall package. You will get driver in that package.

ashikrobi said:
Download heimdall package. You will get driver in that package.
Click to expand...
Click to collapse
it fails to install the driver i tried everything on resolution center also

Howiewowie said:
it fails to install the driver i tried everything on resolution center also
Click to expand...
Click to collapse
I have got this but it wont boot up
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.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)

Howiewowie said:
I have got this but it wont boot up
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltespr-jfltespr-sphl720.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.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)
Click to expand...
Click to collapse
Were you successful flashing the stock rom? If yes, try factory reset from recovery. You said you failed to install heimdall driver. What is the problem? Please try to run one click unbrick tool. It's easy and will guide you. You need java to use it.

ashikrobi said:
Were you successful flashing the stock rom? If yes, try factory reset from recovery. You said you failed to install heimdall driver. What is the problem? Please try to run one click unbrick tool. It's easy and will guide you. You need java to use it.
Click to expand...
Click to collapse
I was not successful flashing stock rom look above my root rom flash it failed and how can it install the unbrick tool when pc doesn't read my phone when I know my samsung drivers are on the hdd it will not even show it listed on other devices

Howiewowie said:
I was not successful flashing stock rom look above my root rom flash it failed and how can it install the unbrick tool when pc doesn't read my phone when I know my samsung drivers are on the hdd it will not even show it listed on other devices
Click to expand...
Click to collapse
Can you please upload screenshots? I do not understand, your screenshot shows odin detects your device. What really happens when you connect your device to pc?
Have you tried ##3424# menu to enable samsung diag port? Is it requesting to install qhsusb_dload driver when you connect it to pc?

i still don't get why you can't install from SD card. are you saying TWRP isn't reading from the SD card? have you tried a different memory card? because you could of just updated the recovery to a different recovery. from my experience, CWM seems to be the most dependable recovery to use.
in any case, i don't understand what you mean your PC won't detect the phone if you're able to use odin..
one other suggestion is to try using adb push to push a files from your pc directly to the phone memory. here's how to do it http://forum.xda-developers.com/showthread.php?t=2266638

Howiewowie said:
I still have TWRP running but I cant install anything from the micro-sd card. Before I started I used twrp for a backup it showed that it made a backup well I trusted it and didn't go look on sd card to see if it was there my mistake its not there, then I tried going with another rom I downloaded Super_S4_Odexed_NAE_v1.5.zip well it wasn't working so then i downloaded Stock-MDL-Stable-spr-TW.zip( its supposed to help for the rom downloaded) and loaded it on my sd card with my pc well i put micro-sd card in phone and it wont read it so I can install with twrp I also tried odin with stock mdl.tar and it fails, so what I need to know is how to start over with wipe and get something i need so it will read at boot up( do i need a bootloader?)and my files from sd card it reads all but my downloaded zip files
my system is a Sprint Samsung Galaxy S4
original stock was L720VPUAMDC.tar
I get this from Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
edit:
Are you running Odin 1.85 or 3.09?
Are you running Odin as administrator?
The computer does see your phone, so that isn't the issue.
What version of Stock S4 were you running prior to flashing Super_s4?
If it was KitKat 4.4 then you'll need to download stock 4.4 from samsung, you cannot downgrade back to 4.2 or 4.3 if your phone came as stock 4.4, sorry.
When you are booting to download mode, are you doing it from a full powered off state? Make sure the phone is fully powered down, even pull the battery and let it sit for a minute or two before you boot to download mode.
What version of twrp did you flash? Versions older than 2.7.0.1 have problems flashing kitkat roms. As an earlier poster suggested, go get CWM 6.0.4.4 (IIRC) or the newest Philz touch and try flashing from that.
Do you have a card reader and a micro-sd to sd adapter you can use on your pc, or maybe a USB-OTG adapter? If so, make sure whatever ROM you want to flash is on the root of the SD card. I have both, and I keep an old spare 2GB micro sd formatted ex-fat that I can quickly format again and copy any ROM to if I need to flash, and if that doesn't work or I can't find it, I have a USB-OTG cable and I'll use any thumb drive I may have sitting around to copy a ROM and flash that way.

wilzard said:
edit:
Are you running Odin 1.85 or 3.09?
Are you running Odin as administrator?
The computer does see your phone, so that isn't the issue.
What version of Stock S4 were you running prior to flashing Super_s4?
If it was KitKat 4.4 then you'll need to download stock 4.4 from samsung, you cannot downgrade back to 4.2 or 4.3 if your phone came as stock 4.4, sorry.
When you are booting to download mode, are you doing it from a full powered off state? Make sure the phone is fully powered down, even pull the battery and let it sit for a minute or two before you boot to download mode.
What version of twrp did you flash? Versions older than 2.7.0.1 have problems flashing kitkat roms. As an earlier poster suggested, go get CWM 6.0.4.4 (IIRC) or the newest Philz touch and try flashing from that.
Do you have a card reader and a micro-sd to sd adapter you can use on your pc, or maybe a USB-OTG adapter? If so, make sure whatever ROM you want to flash is on the root of the SD card. I have both, and I keep an old spare 2GB micro sd formatted ex-fat that I can quickly format again and copy any ROM to if I need to flash, and if that doesn't work or I can't find it, I have a USB-OTG cable and I'll use any thumb drive I may have sitting around to copy a ROM and flash that way.
Click to expand...
Click to collapse
its ok now I took my SGS4 back to Sprint they said they cant figure it out so they are giving me a brand new S4 my phone kinda burned out the screen was turning green on boot up well my insurance covered it thanks for the help

Yeah, he wasn't on MDC. The fail point he was getting meant he already had the knox bootloader.

[Q] Requesting a PIT file for SM-T530NU

I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui

sakui23 said:
I've done everything to restore to stock firmware. I used odin-v3.10.6 and Kies 3. They both stop at 4%. My firmware is T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip. But I can flash TWRP-2.8.7 via Odin just fine. But I am running out of ideas.
T530NUUEU1BOE5_T530NUXAR1BOE5_HOME.tar.md5 (2,225,735,835 bytes)
MD5: 5358d7e9247803a164d9a8cbc713bc55
T530NUUEU1BOE5_T530NUXAR1BOE5_XAR.zip (1,351,979,593 bytes)
MD5: 5c910ca3b4599971669cddf445fef8dc
This is why I'm requesting a PIT file or another solution.
Thanks
Sakui
Click to expand...
Click to collapse
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file

thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui

sakui23 said:
Some reason TWRP-v2.8.7 can't mount /system when I do a wipe. Is there a way to do it manually and wipe it myself?
Thanks
Sakui
Click to expand...
Click to collapse
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .

thisisapoorusernamechoice said:
Try taking off the .md5 extension, or try the Canadian Firmware file, or try KitKat instead.
Also try doing a factory reset in recovery before flashing the firmware file
Click to expand...
Click to collapse
I tried everything you said and I got no where. TWRP complained that the file system was read only.

repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
I'm trying it right now. I'm just confused why Odin stops at system.img.ext4. Is the partition corrupt because its read only? But I installed a custom ROM (BlissPOP) and it worked fine.

sakui23 said:
I tried everything you said and I got no where. TWRP complained that the file system was read only.
Click to expand...
Click to collapse
In TWRP 2870 you need uncheck checkbox on Mount button

repey6 said:
If you want you always can to use service firmware for your device from here http://forum.xda-developers.com/showpost.php?p=61896173&postcount=1 .
This firmware include pit-file .
Click to expand...
Click to collapse
Service firmware [SM-T530NUUEU1BOE5_XAR_SERVICE_LP.zip] didn't work. It stopped at 4% again. But I have 5.0.1 and not 4.4. TWRP won't let me check "system" under mount.

It stopped at 4% again
Click to expand...
Click to collapse
What is 4% ? Where ? I dont understand this .

repey6 said:
What is 4% ? Where ? I dont understand this .
Click to expand...
Click to collapse
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.

sakui23 said:
That's where Kies 3 stopped at. It stops in system.img.ext4 [Odin-v3.10.6] at the beginning of it. But it does process it but very little of it.
Click to expand...
Click to collapse
Why Kies . Close it . Use only Odin with him guide . Go to dounload mode . Connect to PC . In Odin download unpack service firmware (BL , AP , CSC ) to their button . And start . Please copy Odin log to me .

Odin v1.85
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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> 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.

Stop Kies and delete from processes . Stop antivirus .

sakui23 said:
Odin v1.85
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_XAR_T530NUXAR1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.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> 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The newer version don't spit out an error. Just sits there.
Click to expand...
Click to collapse
Correct, kies is awful don't use it. Also use Odin v3.10 or 3.09, not 1.85

Boy, do I feel very stupid...
It was the cords. I had 2 extension USB cords attached to the cord for the Tab 4 and used a different USB port.
Now, the service and the regular firmware works now.
Thanks for everything.
Sakui