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

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] S4 Att Soft Bricked Help <ID:0/006> FAIL! (Auth)

Unfortunately when i purchased the S4 it already had the newest firmware on it and the locked bootloader so all i could do was root the device. I was planning on getting rid of it so i wanted to unroot and restore everything back to stock so i loaded up odin3 and tried but ended up soft bricking the phone somehow. I get the firmware upgrade encountered issue on the screen and tried to restore it via kies and it did not work. So i ended up going back to odin3 and loaded up everything in the MF3 TAR. Everything seemed to be going fine until the end i got this message.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Should i just junk this phone because it looks like even with the high bounty the bootloader will never be unlocked and what else can you do all suggestions would be appreciated thank you for your time
Should i get I337MK2_Combined_Odin_Tar.rar instead ? because that would be ok with the locked bootloader

FIXED use MK2
kriticalglitch said:
unfortunately when i purchased the s4 it already had the newest firmware on it and the locked bootloader so all i could do was root the device. I was planning on getting rid of it so i wanted to unroot and restore everything back to stock so i loaded up odin3 and tried but ended up soft bricking the phone somehow. I get the firmware upgrade encountered issue on the screen and tried to restore it via kies and it did not work. So i ended up going back to odin3 and loaded up everything in the mf3 tar. Everything seemed to be going fine until the end i got this message.
<id:0/006> added!!
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> platform_i337ucuamf3_812098_rev06_user_low_ship_multi_cert.tar.md5 is valid.
<osm> checking md5 finished sucessfully..
<osm> leave cs..
<id:0/006> odin v.3 engine (id:6)..
<id:0/006> file analysis..
<id:0/006> setupconnection..
<id:0/006> initialzation..
<id:0/006> get pit for mapping..
<id:0/006> firmware update start..
<id:0/006> singledownload.
<id:0/006> boot.img
<id:0/006> nand write start!!
<id:0/006> recovery.img
<id:0/006> persdata.img.ext4
<id:0/006> system.img.ext4
<id:0/006> fail! (auth)
<id:0/006>
<id:0/006> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1)
<id:0/006> removed!!
Should i just junk this phone because it looks like even with the high bounty the bootloader will never be unlocked and what else can you do all suggestions would be appreciated thank you for your time
should i get i337mk2_combined_odin_tar.rar instead ? Because that would be ok with the locked bootloader
Click to expand...
Click to collapse
use mk2 fixed

kriticalglitch said:
use mk2 fixed
Click to expand...
Click to collapse
There is over 30 amazing custom roms for mk2. And last night, making history, Kit Kat 4.4.2 is also an option with 2 fantastic custom roms posted thus far. I wouldn't junk the phone if I were you. Though other devices with unlocked boot loaders are great, nothing really beats the S4, well maybe the S5 but it's not out till next month. Here is the guide. Be sure to read thoroughly before you do anything. Good luck & also please thank the op in the threads.
http://forum.xda-developers.com/showthread.php?t=2616221

S4 GT-I9506 is stuck on Firmware upgrade encountered an issue

this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:

could anyone please help?? am going crazy over this spent 2 days researching and finding nothing

Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).

thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?

Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?

on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time

Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.

If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.

FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though

Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.

Gs5 verizon soft bricked! Urgent!

Hi,
I have a SAMSUNG GALAXY S5 VERIZON and I treid to restore it to its stock rom using ODIN.
I have used every version of odin and I keep getting the same message:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried multiple PC's multiple cables and multiple STOCK MD5 files.
I am Able to get to download mode and recovery boot.
I have tried almost every troubleshoot posted online so far.
On download screen I get SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1
URGENTLY NEED HELP!
Thanks guys

Need to know what build you were on before you attempted all of this. If you were on BOE1 or BOG5, you cannot ODIN back to a previous build. You will have to ODIN the same build you were on when you started this.

Most likely I had one of the two. I'll try to odin to same build.
My phone was on Android 5.1.1 stock.

YES! It worked. Thank you so much! I really appreciate taking the time to help me. Good to know people are still willing to help out!

Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out

Dark Karas said:
Hi I am having the same problem but I cannot find the stock file for 5.1 or 5.0.1. or whatever the newest version is if anyone could help out
Click to expand...
Click to collapse
Here you go. This is factory stock, it will locked your bootloader.
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527

I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.

Hollieanne said:
I am having the same issue as the OP but mine is 5.0 and was BOG5. Can you please help me fix it or explain to me how I can? I am a noobie at all of this.
Click to expand...
Click to collapse
If you're having the same problem, the solution is the same: Use Odin to flash the BOG5 system restore image that was linked in the post above yours.