Database Users

[Q] Downloading Pit file with heimdall Galaxy S5

Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!

Luca518 said:
Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!
Click to expand...
Click to collapse
Is your phone root? If so, you can extract the Pit file directly right on your phone.

vndnguyen said:
Is your phone root? If so, you can extract the Pit file directly right on your phone.
Click to expand...
Click to collapse
No its not i need the pit file to flash it back to a earlier version so i can root it

..

fffft said:
You didn't give us enough context to discern the nature of your problem. But at a guess it's a Mac configuration issue.
In any event, you need to give us a lot more information. Or root your phone and extract your PIT file directly. Or perhaps find it in the forums here - again impossible to say as you gave us no particulars as to what S5 model you have, your carrier or anything else.
http://forum.xda-developers.com/showthread.php?t=2737448
.
Click to expand...
Click to collapse
I have a Galaxy S5 Verizon 9000v model

..

I have this same problem. I can't root my s5 because I dont have windows in PC. Why? I wana use JOdin but we dont have any pit file working with it. I wana use heimdall but it doesn't work with S5. So...
Somebody find working Method of root S5 without windows OS.?

fffft said:
That still isn't nearly enough information. To start, there is no 9000v model. But assuming that you really meant a sm-g900v model. Yes details do matter there is a 9006v model as well and other very similar model numbers. And further assuming that your phone is a 16 GB, then the PIT file you need has long been posted in this forum. Look in my post history or do a search.
Cheers
.
Click to expand...
Click to collapse
yes i do have a sm-g900v model sorry i wasn't clear i will check your post history thanks for your help

..

Luca518 said:
Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!
Click to expand...
Click to collapse
most likely related to this problem:
https://github.com/Benjamin-Dobell/Heimdall/pull/225
https://github.com/Benjamin-Dobell/Heimdall/issues/209

Can't Install CWM with Heimdall

I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?

fajrero said:
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
Click to expand...
Click to collapse
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk

Rakuu said:
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?

fajrero said:
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?
Click to expand...
Click to collapse
EDIT: I appologize, i didnt reread my reply, heres the link to thread i waa referring to http://forum.xda-developers.com/galaxy-s5/help/unofficial-linux-support-thread-t2832106
Sent from my SM-G900A using Tapatalk

I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?

fajrero said:
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
Click to expand...
Click to collapse
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk

Rakuu said:
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.

fajrero said:
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
Click to expand...
Click to collapse
Same as my last post, havent used it so i wouldnt know. Also if you do softbrick youll need to get heimdall working or find a windows computer, which honestly, you can beat around the bush sith apps and stuff but at the end of the day i think youll need to use heimdall or odin.
Sent from my SM-G900A using Tapatalk

I went through the TWRP installation with the installer from the Play store, installing the latest version of TWRP. Just as it got to the step for the actual installation, it crashed...
So, I try to reboot into recovery, and I'm greeted by these words: "RECOVERY IS NOT SEANDROID ENFORCING. Set Warranty Bit: recovery". My heart sinks, but then I see the Team Win splashscreen come up, and I'm in TWRP. I tap the Reboot button, and it boots back into Android. Everything seems to be fine, aside from the crash during installation and this mysterious error.
I'd like to install Cyanogen, but I prefer deciphering this error first. From what I've been reading, most of the people getting this error have bricked their phones. Maybe I just got lucky? What is this error, and should I worry about it?

[Q] heimdall can't flash at&t galaxy s4?

I have a galaxy s4 (i337) that is running the 4.4.2 os. I'm trying to downgrade to 4.2.2 due to the SIM issues... the phone will throw the "SIM card removed" error about ten times in a day and force a reboot, then not even register the SIM and stay in emergency mode. i'm fairly certain this is a software issue because i have the exact same model phone running 4.2.2 and have had absolutely 0 SIM errors.
that being said, i have a mac running 10.10.1 and the heimdall 1.4 for mac (i have also tried this with 1.3.1 after hearing that the latest was buggy. it didn't work either). i have tried using the heimdall interface and terminal to flash the stock files. However, it gives me the "failed to confirm end of file transfer sequence" every time... here's the text that pops up in terminal:
sudo heimdall flash --RECOVERY /Users/RaesMac/Desktop/I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar/recovery.img
Password:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
this is my first attempt at flashing a phone, and i really just want to get it over with so i can give the damn thing back to my partner (who is currently using my old iphone 4, poor guy). i'm not sure if there's just something i'm missing or if it's just not going to work.
so, i come seeking the wisdom of the gurus who reside within this forum. what can i do?
P.S.
the files i downloaded to flash are in a .tar folder titled I337UCUAMDB_ I337ATTAMDB_I337UCUAMDB_HOME .tar"
do i need the -AMDL version for this? i have no idea what the difference is, only that there are two options to download.

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

icefireinsanity said:
I have a galaxy s4 (i337) that is running the 4.4.2 os. I'm trying to downgrade to 4.2.2 due to the SIM issues... the phone will throw the "SIM card removed" error about ten times in a day and force a reboot, then not even register the SIM and stay in emergency mode. i'm fairly certain this is a software issue because i have the exact same model phone running 4.2.2 and have had absolutely 0 SIM errors.
that being said, i have a mac running 10.10.1 and the heimdall 1.4 for mac (i have also tried this with 1.3.1 after hearing that the latest was buggy. it didn't work either). i have tried using the heimdall interface and terminal to flash the stock files. However, it gives me the "failed to confirm end of file transfer sequence" every time... here's the text that pops up in terminal:
sudo heimdall flash --RECOVERY /Users/RaesMac/Desktop/I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar/recovery.img
Password:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
this is my first attempt at flashing a phone, and i really just want to get it over with so i can give the damn thing back to my partner (who is currently using my old iphone 4, poor guy). i'm not sure if there's just something i'm missing or if it's just not going to work.
so, i come seeking the wisdom of the gurus who reside within this forum. what can i do?
P.S.
the files i downloaded to flash are in a .tar folder titled I337UCUAMDB_ I337ATTAMDB_I337UCUAMDB_HOME .tar"
do i need the -AMDL version for this? i have no idea what the difference is, only that there are two options to download.
Click to expand...
Click to collapse
It's failing because you can't downgrade from 4.4.4 to 4.2.2. It has nothing to do with heimdal.
Sent from my Nexus 5 using XDA Free mobile app

So I'm just stuck with a gimpy phone?

icefireinsanity said:
So I'm just stuck with a gimpy phone?
Click to expand...
Click to collapse
If you think it's a software issue try flashing the nb1 tar file in heimdall. http://forum.xda-developers.com/showthread.php?p=56453100
But, you're not the only one with this problem and there is no consistent fix http://forum.xda-developers.com/showthread.php?p=58228851
Sent from my Nexus 5 using XDA Free mobile app

[Q] Galaxy S4 - Heimdall gets stuck at "Initialising protocol..."

Hi
Phone: Samsung Galaxy GT-i9500 (International). Currently sitting on stock everything.
Years ago, I was able to successfully flash my Galaxy S2 with Cyanogenmod. I really don't know what else to try now with this S4.
Please bear with me. I know this question has been asked before but I've tried all the solutions that have been posted and I've also spent a lot of time trying other methods of rooting my phone with no success.
I started off following the instructions on wiki.cyanogenmod.org/w/Install_CM_for_i9500 to install Cyanogenmod. I have also tried other instructions for using ODIN.
Things that have been posted as solutions that I've tried:
Plugging the phone in the back USB ports instead of front USB
Plugging the phone into different USB ports
Using a different USB cable
Both Heimdall 1.4RC2 and 1.4.0-win32
Tried the various combinations of upper/lowercase --recovery --RECOVERY etc
WinUSB, libusb0 and libusbk drivers provided by Heimdall's zadig.exe
Using Odin3 v1.85
Using Odin3 v3.07
Tried KingoApp
When I tried using KingoApp it sat for about half an hour running through various exploits and not succeeding. Then eventually it said that the final thing it could try was to reboot into Download mode. I let it do that and the phone got stuck in exactly the same place that Heimdall and ODIN gets stuck. Namely the screen shows the following but no blue bar ever appears or fills up:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
RP SWREV: A3
Downloading...
Do not turn off target!!
Click to expand...
Click to collapse
cygwin md5 check said:
$ md5sum recovery.img
4fbc482479f4d91c619be8dbb79cdb84 *recovery.img
Click to expand...
Click to collapse
cmd log said:
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall.exe version
v1.4.0
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
--urlsnip--
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
--urlsnip--
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Click to expand...
Click to collapse
I really don't know what else to try at this point. Can someone please give some suggestions or point in me in the right direction?

Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/galaxy-s4
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/galaxy-s4/help
Good luck!

So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
https://builds.casual-dev.com/jodin3/
You don't need Kingoroot. It doesnt even work anymore anyway.

Lennyz1988 said:
So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
You don't need Kingoroot. It doesnt even work anymore anyway.
Click to expand...
Click to collapse
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.

Nobody Hates Firemen said:
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.
Click to expand...
Click to collapse
Odin should work though.

Lennyz1988 said:
Odin should work though.
Click to expand...
Click to collapse
It doesn't though. I don't get any error message which makes this very difficult to investigate. It just doesn't start transferring the recovery.
I just tried using towelroot v3 and got a message, "This phone isn't currently supported" - even though Galaxy S4 is supposedly supported. I wonder if I have some weird variant model.
It says the following in the about screen:
Model number: GT-I9500
Android version: 4.4.2
Baseband version: I9500XXUGNF6
Kernel version: 3.4.5-2434847 / [email protected] #1 / Wed Aug 6 16:24:19 KST 2014
Build number: KOT49H.I9500XXUGNH2
SE for Android status: Enforcing / SEPF_GT-I9500_4.4.2_0024 / Wed Aug 6 16:24:19 KST 2014

You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.

Lennyz1988 said:
You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.
Click to expand...
Click to collapse
CF-root worked, thank you! Used the one at download.chainfire.eu/326/CF-Root1/CF-Auto-Root-ja3g-ja3gxx-gti9500.zip?retrieve_file=1
I'm not running VM or anything. It frikken sucks that the instructions on Cyanogenmod aren't up to date And also sucks that every other site I went to with instructions doesn't mention that they're outdated root methods. The price of being a noob...
Thanks for showing me the way.

[Q] Odin failed after trying to flash stock, and Kies thinks I have a diff device?!

Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!

KyleLinden said:
Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!
Click to expand...
Click to collapse
You have a friend with a real PC?
Also, what error is Odin giving...and I'd use 3.09 rather than 3.07.
Sent from my Note 3 via Tapatalk

Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried a different USB cable or port?

KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk

Interesting, makes sense. Will seek out a real Windows machine and try the new ports/cable and report back. You're right about the tar.md5 file extension, but that's what seems to generate in the dialog panel when I use the aforementioned stock ROM file.
Thanks for advice so far.

donc113 said:
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
the indidual partitions boot, recovery, system within the .tar are .img files so that is not the problem.

Easter Day miracle.. I took out my old laptop, reinstalled a copy of windows 7, moved the stock ROM and the pit file I found to a USB drive, used the OEM cable, installed all drivers available for Samsung mobile devices, rebooted, and finally Odin was happy with me and decided to flash stock! Phones fixed! Thanks everybody.