ODIN3 FAILED All threads completed. (succeed 0 / failed 1)

[WastedPenguinz]

So basically i went into Download Mode, USB Debugging Enabled it was a ***** to get the computer to recognize it but once it did, and everything was working i got this

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

Following this tut:
http://forums.androidcentral.com/t-...13815-how-root-t-galaxy-s3-sprint-forums.html

i have a Galaxy s3 AT&T but unlocked and using it with T-Mobile

First time rooting, please be gentle

 

[Golfdriver97]

So basically i went into Download Mode, USB Debugging Enabled it was a ***** to get the computer to recognize it but once it did, and everything was working i got this

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

Following this tut:
http://forums.androidcentral.com/t-...13815-how-root-t-galaxy-s3-sprint-forums.html

i have a Galaxy s3 AT&T but unlocked and using it with T-Mobile

First time rooting, please be gentle

Rooting this device may be rather difficult. You are using a phone that was originally programmed for AT&T. Now it's on T-Mo, so that may make a difference. However, you can try this: How to Root U.S. and Canada Galaxy S3 AT&T, T-Mobile, Sprint/US Ceullar! [Fail-Proof][Noob-Proof] | Galaxy S3 Root

I rooted using this method, but like I said, due to the complex nature of your situation, it may not work. Follow the video, jot down all the steps, take your time, and if you have any questions, ask.

 

[Ndovu]

I do not want to start a new thread because my problem is identical except that I am using Samsung S4 Mini i9195 and Odin3. Results I get are below. Please help as I am at my wit's end.

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCNEA_I9195VFRCNE4_I9195XXUCNEA_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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

 

[seanbr0wn]

I'm also having this problem with a Galaxy S5 but I am trying to go from BTU version (which is the only 900F version that i could flash successfully with Odin 3.9 / 3.10) to the EE carrier version as this version allows wifi calling but the flash stops at hidden.img.ext4 as above and Odin reports the flash as FAIL. Knoxx is showing 0X1 (2). I've tried to PIT using Odin (according to xda and several other posts this seems to be the only way) and that didn't work either. My reactivation lock is off and usb debugging in devoloper options is on.

Any advice PLEASE