Database Users

[Q] BRICKED [SGH-I337M] USING - CF-Auto-Root [CANADIAN MODELS ONLY]

So I followed this thread exactly, for my rogers I337M
[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY]
http://forum.xda-developers.com/showthread.php?t=2293800&highlight=cf+auto+root
and after I started ODIN after selecting the .tar.md5
I got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
And in it says fail on ODIN. And now when I boot up I can't get to my stock OS
only to a screen where it says, "Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I Can't use my S4 any more . I was wondering if it was because I had a locked bootloader, but the I337M varient should be unlocked right?
I also had the new MG1 firmware before I tried all this, but I saw alot of other MG1 users used this method.
PLEASE HELP, I would be forever grateful.

Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?

scott14719 said:
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
Click to expand...
Click to collapse
Completely sure.

Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10

mymusicathome said:
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
Click to expand...
Click to collapse
ok so I got the latest firmware for my device.
Build Date: 01.07.2013 -> Region: RWC (Canada (Rogers)) PDA: I337MVLUAMG1 Changelist: 897376 Android: 4.2.2
I got it from this thread
http://forum.xda-developers.com/showthread.php?t=2269304&highlight=flash+stock+firmware
I got back into the download mode (VOLDOWN/HOME/PWR) with the android icon where it says. "Downloading... Do not turn off target!!" plugged in my device got into odin put the stock firmware in PDA and ran then got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
and my device still doesn't work.

Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.

jd1639 said:
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
Click to expand...
Click to collapse
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?

I really have no idea what to do.. I have 1 year warranty left with this phone, and me trying to CF-Auto root was the only thing I've done that could have voided my warranty, but it failed and now that I'm stuck would I still be okay if I took it in for warranty?

PromyD said:
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
Click to expand...
Click to collapse
Try it on a different computer.

jd1639 said:
Try it on a different computer.
Click to expand...
Click to collapse
agreed. or at least a different usb port. are you using the cable that came with your device? i'm assuming you had usb debugging switched on.

So i've tried it on another computer, but since my device is in download mode it doesn't install any samsung drivers to properly identify and read the S4, so it doesn't work. Can anyone please give me some direct links to download the proper usb drivers on windows for my S4.

http://lmgtfy.com/?q=samsung+galaxy+s4+drivers

Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx

Lo
PromyD said:
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Click to expand...
Click to collapse
You're welcome. Glad to have helped. It's good you got your phone working again.
Ps, nvm

SGH I337M Bricked as well
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!

Copy a rooted i337M rom to your SD card. Boot into recovery , wipe and flash.
Sent from my SGH-I337M using XDA Premium 4 mobile app

I cannot boot into recovery.

Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting

OverclockDaS4 said:
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Click to expand...
Click to collapse
Take a deep breath, and try another cable. I find a large portion of flash errors are caused by junky usb cables. If that fails, try another usb port and another pc entirely, if possible. Let us know some more info, someone has already asked, more details the better. Good luck.
Sent from my SGH-I337M

pyrexid said:
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
Click to expand...
Click to collapse
Knox does trip if you root.... not sure there is any method that doesn't...... guess if its important... do some research.. I couldn't find one when I did mine... used CF-auto..... on i337m

[Q] Boot error

Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.

chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
If u hv nandroid backup. Try restoring it. It will return u to last stable condition of your phone

re: flash stock firmware
chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!

Tried everything
Misterjunky said:
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!
Click to expand...
Click to collapse
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.

chemarko said:
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.
Click to expand...
Click to collapse
C`mon guys HELP PLEASE

[HELP] Please
chemarko said:
C`mon guys HELP PLEASE
Click to expand...
Click to collapse
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When add re-partition
> Added!!
<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> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)

chemarko said:
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When add re-partition
> Added!!
<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> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?

DefyUser89 said:
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?
Click to expand...
Click to collapse
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader

chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?

chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
Repulsa said:
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?
Click to expand...
Click to collapse
Oh yes! I forget, I installed FNA1 not FNA5 and i could come back to 4.3 because FNA1 dont have new bootloader... I rode that FNA5 have new bootloader and u can go back to 4.3.
The best choice is how said @Repulsa , U must install FNA5 and after install Philz-touch, CWM or TWR and install any 4.4.2
I hope that we helped to you! :good:
Regards,

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.

[Q] ODIN fails when trying to install stock rom, HALP MI

So I've tried to revert back to the stock ROM using ODIN at it always fails right at the very end. Here's what ODIN says in its message box;
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANL1_G900FOJV1AOA1_G900FXXU1ANG8_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> 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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
After rebooting from the fail it gives a screen saying "Firmware upgrade encountered an issue" and I can't open recovery but I can get into download mode again. I'm using an SM-G900F. Please help, I'm not a fan of £350 paperweights.

Flash the correct PIT file with the stock ROM
Easy to find with a quick Google

*Detection* said:
Flash the correct PIT file with the stock ROM
Easy to find with a quick Google
Click to expand...
Click to collapse
I've looked before but I've never managed to find one for my model, maybe I'm just dumb and not looking in the right place. Also I've heard that PIT files can potentially brick your phone so I'm a little hesitant

Well from the looks of the ROM name you're trying to flash, it's a G900F
PIT file is very easy to find for that model
http://bfy.tw/UmS
EDIT -
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2

*Detection* said:
Well from the looks of the ROM name you're trying to flash, it's a G900F
PIT file is very easy to find for that model
http://bfy.tw/UmS
EDIT -
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Click to expand...
Click to collapse
You're a saint mate, thank you so much, I used the 16gb 900f pit from the link you gave alongside one of the ROMs in your signature and its back to working order

Nice one

*Detection* said:
Nice one
Click to expand...
Click to collapse
Hello, i recently got a used s5 running 5.0 lollipop Poland latest build. I tried to root it and install customer recovery but was met with that recovery is seandroid enforcing something error. I looked on google found a workout to pull the battery out as soon as Odin finishes flashing Root. The situation is that i have rooted the phone and have also installed TWRP but when i press power +vol up + home to enter recovery it still does display that seandroid error for 3,4 seconds and then boots into recovery.....and i am not able to root my device normally (without pulling battery immediately). My question is that if i download that PIT file from the link you gave and flash it with odin will it delete my EFS or modem folder? ...will all these issues be resolved if i flash S5 16 GB pit file?

[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