Database Users

[Q] ODIN fails i337m - bricked - HELP

Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!

Hey have you tried re-flashing the original bell rom? Or did you have a backup? I haven't bricked my s4 but I bricked my S3 multiple times and I ended up bringing it back with a basic ATT rom before getting the rom I wanted to work.
So first try flashing your original stock rom (if you have it or go to your backup)
Next step try an ATT stock rom.
If that doesn't fix it, someone more experienced will have to chime in.
mfreeman3769 said:
Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!
Click to expand...
Click to collapse

Odin fails due to the firmware
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!

Try this: launch Samsung Kies and go to Tools -> Firmware Upgrade and Initialization.
I tied it (my phone work now) but i have always the same trouble with ODIN (nothing can't put in except CF-AUTO-ROOT don't tell me fail)

mfreeman3769 said:
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!
Click to expand...
Click to collapse
You might want to check which bootloader you are on, you can do this through terminal on the the phone (instructions burried somewhere in one of the threads) or download Phone INFO from the play store, it will display which bootloader you are on. Once you know that, see if you can find a thread (search) on downgrading from 4.3 to 4.2

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html

frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.

Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...

frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )

Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)

Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?

yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.

Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.

)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country

frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**

hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...

Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem

It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.

Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

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.

[HELP] Device is dead!

Please help me i have make downgrade form 4.4.2 to 4.2.2
but after goto download mode see
PRODUCT Name : GT-i9500
CURRENT BINERY : CUSTOM
SYSTEM STATUS : CUSTOME
KNOX WARRANTY VOIO: 1
RP SWREV : A3
then i ask say need flash other rom i goto flash other rom but there error on phone and ODIN
phone is show massage abort
SW REV Invalid Magic Strings
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md 5 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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
why this massage ? and firmware not want flash
i use odin 3.7 and 3.9
i use other other firmware
ir's show massage on phone
SW REV Check FAIL DEVICE:3 , Binary :2
i see this post http://forum.xda-developers.com/showpost.php?p=50893851&postcount=27
and i flow the step
but phone now not open
only i can open download mode and recovery mode
how i can get back my phone please help

no one want help me

EgyMan said:
no one want help me
Click to expand...
Click to collapse
I was advising u in last thread that downgrade was bad idea. Do you begin to understand the consequences? You have a beatiful paperweight :highfive:

Joku1981 said:
I was advising u in last thread that downgrade was bad idea. Do you begin to understand the consequences? You have a beatiful paperweight :highfive:
Click to expand...
Click to collapse
Are you a hilarious true for me
but there question for you < why u say it's stupid ida for who make downgrade from 4.4.2
and it's make bugs for all ppl ?
can you explain ?
i was fix my problem i flash custom ROM and i flash stock rom again and it's working

normaly you can not downgrade from 4.4.2 to 4.2.2 .
think this is the fault of the newbootloader

EgyMan said:
Are you a hilarious true for me
but there question for you < why u say it's stupid ida for who make downgrade from 4.4.2
and it's make bugs for all ppl ?
can you explain ?
i was fix my problem i flash custom ROM and i flash stock rom again and it's working
Click to expand...
Click to collapse
Yes? and your IMEI? and your CSC?
*EDIT: Its not question of bugs. It's question of differences btw old/new bootloaders.

joku1981 said:
yes? And your imei? And your csc?
*edit: Its not question of bugs. It's question of differences btw old/new bootloaders.
Click to expand...
Click to collapse
ap : I9500xxubmh1
cp : I9500xxubmg9
csc i9500ojvbmh2
i want know what is differences between old/new bootloader

i brick my samsung s4 sgh i337

hello everyone i am new here.
i have come here because i was trying to install a new recovery twrp to be exact. while i was installing it apeared a messge it said: the recovery has been installed correctly would you like to restart your mobile? and i restared my mobile and then it shown a message it said: system software not authorized by at&t has been found on your phone. at that time i had installed android lollipop 5.0.1 and it was rooted and i just wanted to re-install lollipop again by odin but knox and bootloader was enable so i cant reinstall the rom again and it seem like i have bricked my mobile..
help me please.

SGH-i337 is an AT&T phone which has a locked bootloader. If you have old bootloader like MDL you could use the loki exploit when you install the TWRP. What is your bootloader version?
I do not think there is a odin flashable lollipop full firmware exist. The last full firmware released for i337 is NB1 (kitkat). After that there is only incremental OTA upgrade to lollipop.

can i downgrade to kikkat?
i dont know what kind of bootloader i have. but odin is always fail when i try to apply the firmware... let me post a screemcapture!
can i dowgrade via ota... because i have tried to intall lollipop by ota but there is always an error! unpacking the package!

either samsung kies doesnt detect my mobile and i cant not enter to recovery mode because it says that firmware upgrade encountered an issue. please select recovery mode in kies and try again.

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The ROM you are trying to flash has a bootloader that is older than the bootloader on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.
Look here for a possible solution: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642

my mobile was running lollipop 5.0.1 and how can i get the latest version?

thank you it works hehe i am so thankful with you...
arigatou..