Related
so heres the deal, ive read the forum with all the instructions how to downgrade from dk28 back to di18. i even did it on my epic a month ago because i missed my gps. on my phone it worked the first try. no problems whatsoever. so now im trying to do the same with my girlfriends phone and its refusing to work. it either stops at initializing or geting pit. ive been at this for an hour now. any ideas?
Dont use the pit file. You don't need it for flashing tar files. Just put the tar file in PDA and make sure only reboot is checked and hit start.
zombiematt said:
so heres the deal, ive read the forum with all the instructions how to downgrade from dk28 back to di18. i even did it on my epic a month ago because i missed my gps. on my phone it worked the first try. no problems whatsoever. so now im trying to do the same with my girlfriends phone and its refusing to work. it either stops at initializing or geting pit. ive been at this for an hour now. any ideas?
Click to expand...
Click to collapse
Have you tried the three different versions of odin out there? 1.0 1.3 and 1.6 somethin? 1.6 has the highest success rate for me. Also you don't need the pit but it shouldn't affect it's ability to complete if you do use it. Also if you're trying to odin back to di18 don't use the di18 extended, it's very finnicky. Just try the pure stock di18 files from noobnl's post in dev section.
When I use ODIN with my phone I need to make sure the PDA file doesn't have the MD5 tag at the end of the zip file. So naturally when I went to flash my gf's Samsung Mesmerize I took the tag off her tar file also. Made Odin crash repeatedly across different versions. When I finally realized I needed MD5 at the end of the file ODIN flashed the phone on the first try.
Lesson of the story is that ODIN is finnicky. Try different things like: Different USB ports, restarting computer before using it, and playing with different PIT files (don't quote me on the PIT thing, I've used different ones with no ill effects). Try changing the zip file to just .zip or .zip.md5 just to make sure it isn't something simple like that.
1greek4u said:
and playing with different PIT files (don't quote me on the PIT thing, I've used different ones with no ill effects).
Click to expand...
Click to collapse
Pit is specific to build. It tells the phone where to flash what... Following this advice *could* have very detrimental effects .....
Swyped from my *Epic*
Thanks for clearing that up.
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
I had that happened before with odin 1.2. Updated to 1.7 and everything worked afterward.
Sent from my SGH-T959 using XDA App
yeah used both versions
sometimes using a different computer solves the problem for me.
Had this happen too. In my case switching to a USB port in the back of my PC rather than one of the ports on the front of my PC case fixed the issue. Try Odin'ing with your other USB ports?
Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help
having same problem
I'm having the same problem. What is a corrupted JFD file and how do I fix it?
Ran into the same issue. I checked "Phone Bootloader Update" in odin 1.82 and it finally worked. Not sure why, but I'll take it.
Bandage said:
Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help
Click to expand...
Click to collapse
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...
^ check my signature for going back to stock thread. If you have an operational phone, you should be good with my guide.
ccole22653 said:
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...
Click to expand...
Click to collapse
Its the .tar file used for pda sometimes it gets damaged when you download it just need to redownload it
Sent from my SGH-T959 using XDA App
Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
I finally found what the problem was, my stock tar file was not completely downloaded and was 180MB vs 291MB what it should have been. Redownloaded, tried again and it worked perfect. To those that still have the problem, try re downloading the files instead of trying the same one over and over, worked for me ;-)
hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.
blemish31 said:
hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.
Click to expand...
Click to collapse
I have been having the same problem here. I am only able to enter download mode, my phone won´t boot, not even cwm.
I have been trying to install a new rom via Odin but it gets stuck at factoryfs.rfs , I have tried everything even all said in this thread it still wont work. Also tried checked and downloaded several times the files as you mentioned.
Please, if anyone knows what else to try.
PS: I also tried installing other roms rather than darkys resurrection and they would all get stuck in some point during the installation via Odin, really wierd, please help!!!
Dude, you'd be better off starting a new thread in the Q&A section.
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.
dpaul007 said:
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.
Click to expand...
Click to collapse
Actually if you read up on DarkyRom, the Darky team makes Odin .tar's of their base roms. So yes you can Odin a custom rom. It's actually easy to make a Odin tar ball of any Samsung TWiz based rom on your phone.
Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
What files are you flashing?? Are you flashing with or without a .pit?
Here is a guide from XDA for Flashing. Its easy to follow and ive never had an issue with it. Good Luck.
http://forum.xda-developers.com/showthread.php?t=1307637
I just plugged my usb into the back and i got past it. sat for the last 2 hours troubleshooting.....
Hey everyone,
trying to put the EB13 stuff on my phone, and I'm stuck at the ODIN part.
I've used ODIN before and never had any problems...
now everytime I try to upload anything to the phone, I'm failing right after param.lfs. The error I get is complete(write) operation failed
I tried putting it in the phone section instead of PDA, but I'm getting the same error.
like I said, i've used it before so I doubt it's driver related?
any help?
I also tried another USB port (com 6, and com 8)
i was experiencing this (still am)
i ended up having to taking it in to sprint store they put EB13 on it for me w/o saying anything lol but most likely cable as everyone has said stock cable is bad quality
I tried 2 diff cables and 2 diff computers now...
Still getting the same failure...
Try redownloading the tar file somewhere else.
Sent From My Evo Killer!
musclehead84 said:
Try redownloading the tar file somewhere else.
Sent From My Evo Killer!
Click to expand...
Click to collapse
None of them work, including all the older ones I had that were working last time I used
Yep exact same boat as me
make sure you cant boot into recovery/get past sammy screen
delete everything off of your sd card then take it into sprint they'll fix it for you.
I might have to take it back to bestbuy if anything.
I just tried again (without the battery in the phone this time) and it went past and I'm stuck at like 99%...
I'm trying to upload the EB13 ODIN, and it's stuck at modem.bin, which is like the last thign it installs... I"m pretty pissed...
had the exact same problem, with ODIN and with the Official Samsung flasher from their site.
tried different cables etc... nothing
Ended up removing all the drivers, reinstalling the drivers
Moved cable to one of the rear ports on the computer and boom worked the first time.
Since then I've seen several people who had problems with their front ports but worked from the rear ports.
now I'm stuck at the modem... I can't install past modem.bin which is the last thing.
the phone actually booted up, but no signal obviously...
razorseal said:
now I'm stuck at the modem... I can't install past modem.bin which is the last thing.
the phone actually booted up, but no signal obviously...
Click to expand...
Click to collapse
Try installing the modem separately.
Another less realized problem is power. I always use a computer with network grade power. If you have ever monitored the utility power you would know why your computer does odd things.
Sent from Bonsai 3.0.1
Something I've tried before when getting problems using is odin is taking the ".md5" off the end of the "SPH-D700-EB13-8Gb-REL.tar.md5." Placed it in PDA without the .md5 and then put the PIT file in. I did that with the DK28 release though, so not sure if there would be a difference with EB13. However, the EB13 tar with CWM3 and root built in and the PIT worked fine for me first time through.
taking out the battery and letting it run off the USB did the trick. very weird
I love you razorseal.
I couldnt get passed param.ifs for hours, taking the battery out worked for me too~
I have this problem constantly.
What I do is remove the cable and battery for approximately 30 seconds and hold the power buttons to remove any leftover charge from capacitors. Reinsert the battery and put the phone back in download mode and plug it up and try again. That usually brings up my success rate from like 20 to 80 percent.
Sent from my SPH-D700 using Tapatalk
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03
SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03
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.