Develop Bugs

Just upgraded to Kies 2.1.0...Is Kies terrible for everyone or just me

I tried to use the previous version of kies to upgrade my gs2 but it never worked. Update would be from:
[KF3/phone:ke7/csc:KD1] to [KI4/phone:KI1/csc:kh2]
Which I'm sure is a big step forward as I haven't been able to update forever. I thought that once I updated Kies I'd finally be able to update my phone. Now when I connect my s2 and hit update firmware, as soon as it asks to backup it loses the connection to the s2. I've reinstalled drivers twice to no avail.
Does Kies just blow as a software or am I doing something wrong.

Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.

^ I so much agree to that post.
Kies never worked for me, not even when my SGS II was used with the stock rom that shipped with it. While there was an update out for quite a long time (> 1 month) it still was showing my version as being current.
Odin is so much better or just as simple: flashing from CWM.

husaam said:
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
Click to expand...
Click to collapse
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
edit: Do I need to root* my s2 to use odin?

aDroidtoRemember said:
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
Click to expand...
Click to collapse
It's actually quite simply. Most ROMS come with only one file. That can be flashed via PDA. Do NOT, I repeat, do NOT, I repeat once again, do NOT, and again: do NOT! tick ANY option in ODIN, unless stated specifically in the ROM's instructions and even then tripple check that you're really about to flash a SGS II firmware.
So as long as you get the right firmware, do not tick anything and just flash it via PDA you should be quite safe. There's always a minimal risk, even if you do everything right but it's very very small.

Try This!
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit

Looking at Odin for the first time can be a bit confusing. Once you know the score tho its very easy and quick. Flashing intras files for example is a complete doddle as it's 1 tar file
Sent from my GT-I9100 using xda premium

Nyssa1104 said:
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Click to expand...
Click to collapse
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?

Once you get your head around Odin, its a piece of cake.
Look for Intratech's Official i9100 Firmwares thread in the Original Android Development section, you'll find everything you could possibly need in there (instructions, firmwares etc)

aDroidtoRemember said:
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Click to expand...
Click to collapse
OK Odin is easy just read the Q&A

link pls...

i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware

Since nobody answered yet... No u don't needa root to get Odin work
Sent from my GT-I9100 using Tapatalk

i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App

mertakb said:
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
you're are correct for 2.0.3 but the new 2.1 is totally screwed up, crashed my windows even

Gavin.csy said:
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Click to expand...
Click to collapse
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.

janderk said:
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
Click to expand...
Click to collapse
do you have the link for the download, i still find 2.0.3 only, nothing directly 2.1

Windows 7pro (32bit) absolutely none of the problems listed here or on other threads (regardless of stock/custom anything) but.. Odin is easy if you follow instructions and seems much more reliable (see intratechs thread in dev section for instructions)
Sent from my GT-I9100 using xda premium

It finally worked for me, i don't know what happened why it suddenly decided to work/
One difference i noticed is i got a notification 'Samsung Modem succesfully installed' which i did not get for the past 2 hours of restarting,uninstalling ,installing. It just suddenly came when i connected the phone
Kies is really crazy as hell

I think you may just have to turn off your anti-virus/firewall software while you update. It worked for me.

Can't Odin from FB27!

Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
[update]
This is likely a windows problem, not a problem with FB27. Sorry for causing any panic

few questions
what version of odin/are you using the self-extracting auto odin back?
http://forum.xda-developers.com/showthread.php?t=1433101
have you removed the kies/samsung drivers, then reinstalled? if you're having problems and it's related to the drivers (which it may be), sometimes you have to remove not just reinstall.
also, have you tried a different usb cord? sounds stupid i know, but they get **** stuck in the ends, or otherwise damaged, and cause weird issues in situations like this but otherwise work fine.
i just odined back last night using the package in the thread above, and it worked fine.

Just to make sure, you do have samsung kies installed, right? You need their drivers.

exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
From your post you're trying to do the odin all in one self extractor... have you tried just using odin to flash the EL29 stock recovery repack and then flash through CWM from there?
http://forum.xda-developers.com/showthread.php?t=1390393&highlight=rogue
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5

exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.

Use another cable besides samsungs crappy pos
Sent from my SPH-D710 using Tapatalk

Also try a simple reboot. Sometimes if I run sfhub's one click then Odin I have to reboot in between but only sometimes
Sent from my Nexus S 4G using xda premium

sfhub said:
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Click to expand...
Click to collapse
I have used EL29, EG30 of yours several times without any problems sfhub. I don't know why I occasionally need to reboot in between one click and regular Odin but its no big deal. 90% of the time I dont
Sent from my Nexus S 4G using xda premium

exabrial said:
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
Click to expand...
Click to collapse
According to Microsoft, code 42 means there is a problem with multiple instances of the driver and the solution is a reboot (as John pointed out)
My theory as to why it is happening is there is a problem either in the USB driver or in ODIN OneClick with shutting down the USB bus when the flash is done, so next time you run it there is already an instance. Another possibility is if you use different USB ports on the computer between sessions, then the USB driver might get confused and keep multiple instances.
http://support.microsoft.com/kb/310123
Code 42
Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer.
Click to expand...
Click to collapse

Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.

exabrial said:
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
Click to expand...
Click to collapse
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium

JohnCorleone said:
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same as my initial post. I'm currently at work Just trying to develop a POA.

According to MSFT, the error code 42 is not a problem with driver installation. It is a problem at runtime with multiple instances of the driver.
Did a reboot not work? Perhaps there are problems with the driver in the 64-bit and 32-bit locations?

I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.

exabrial said:
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
Click to expand...
Click to collapse
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.

I'm not at all experienced with Mobil ODIN, but wouldn't it be possible to forego the computer completely to get back to EL29?

It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.

sfhub said:
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
Click to expand...
Click to collapse
True, but he doesn't sound soft bricked, which is why the thought crossed my mind.

sfhub said:
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
Click to expand...
Click to collapse
It's quite alright, I appreciate the help. I followed the directions in that post, and am getting the same problem... It is windows7 64bit. basically, installed the drivers to C:\Program Files (x86)\Samsung\USB Drivers
I guess I'll try mobile Odin... windows hasn't improved any over the last 10 years I see.

Can someone help me I have the same problem it happened to me about a week ago when i tried flashing one of calk's rom and then all i know is that triangle disappeared from the samsung animation and then my computer will not recognize it.I've looked here and google and cannot find a solution!!!PLEASE help me!!I've noticed people with similar problems but no help.
Also I got mobile odin and tried to unroot but I am afriad I wont be able to root again since it will not discover my device.

[Q] Rooting Help? USB Not Working In Download Mode

I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?

Did you wait a couple of minutes between steps 3 and 4 before giving up. I just re-did this last night; I didn't time it but my PC must have taken a minute to show COM to be ready to start Odin on the stock tar.
I was also having USB driver issues and reinstalled. My PC has been having USB issues in general with Windows 8.1 updates; had to uninstall and reinstall the same PC generic USB driver. Circa 2009 era PC needs an overhaul or replacement.
BTW, if you're using an older CF Auto root, CF went back to Odin 3.07 and updated to superSU v2.45

I did, because I was unsure what was going on. This is only the second time I've rooted a phone, so I was unsure what would happen if I pulled the battery. I think I waited about 20 minutes while looking online to figure out what was going on.
I'm not sure what you mean by an older version. I downloaded the version for my phone from chainfire.eu

http://redirect.disqus.com/url?url=...&thread=3459253652&zone=thread&area=discovery
http://redirect.disqus.com/url?url=...&thread=3443914612&zone=thread&area=discovery
Some questions I should have asked earlier: USB debugging enabled? Using USB 2.0? Tried different USB cables?

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
PS. Did you use Kingo to root your note 4? I might give it a try.

No, I just posted links for the thoroughness of checks. I used CF Auto root. Good luck.

Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh

I'm thinking the MTP might be the issue, but I don't seem to have a MSD option on my note 4?

Any more ideas?

What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.

faile486 said:
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Click to expand...
Click to collapse
Press volume up to confirm download mode?

rawintellect said:
Press volume up to confirm download mode?
Click to expand...
Click to collapse
Yes, that has to be done to get to download mode? I'm at the screen where it says 'Downloading...Do not turn of the target!!'

faile486 said:
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
Click to expand...
Click to collapse
I'm sorry but I don't recall seeing this reply because I don't understand it now. I may have overlooked it?
Are you saying the phone appears to download but boot loops? You should see success and 0 failures prior to auto boot. Is that the CF Auto root flash in Odin or another Odin flash like recovery or stock tar? If that's happening, did you try to pull battery and delete cache and dalvik cache in recovery? Is the phone semi bricked or just not rooted? Can you Odin the recovery tar for TWRP recovery? If so, you could just flash the superSU zip file in TWRP.
http://download.chainfire.eu/supersu
Another suggestion, if you're getting anywhere with Odin, you should close and reopen Odin if doing multiple flashes. Close after each flash; i.e., power down, flash stock tar, close Odin, open Odin, flash CF Auto root, close Odin, flash recovery (download mode steps omitted since you know that already).
Again, someone might could help with detailed setup details and steps taken. Sorry if I'm not following well; I'd like to help, if possible.

samep said:
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
Click to expand...
Click to collapse
I'm using Windows 7. Using another PC is a good idea, I'll try that.

faile486 said:
I'm using Windows 7. Using another PC is a good idea, I'll try that.
Click to expand...
Click to collapse
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.

samep said:
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
Click to expand...
Click to collapse
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)

faile486 said:
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
Click to expand...
Click to collapse
Glad to see you among the rooted in Sprint Note 4 XDA. Hopefully your solution can be repeated for future updates. Lollipop well be here some day.

Does Kingo root Trip Knox?
Sent from my SM-N910P using XDA Free mobile app

**SOLVED** Any/All ODIN flashes FAIL!

SOLVED: see post #5 & #8
I've been trying to root my T807T and everyone with one on the forums here has reported that all T805 stuff works just fine on it.
I have installed USB drivers, USB Debugging set to on. Been using Odin 3.07 as well as 3.09.
I tried multiple USB ports and two computers and a whole lot of different wires (including original ones).
I disabled my Anti-virus and do not have Kies installed.
I am not a newbie to flashing and have been rooting Samsungs since the first Galaxy S Vibrant all those years ago. I have never seen anything like this.
Everything I try to flash in Odin comes up with FAIL! after about halfway through flashing. I can restart my tablet and everything works fine, but this is making it impossible to root.
FAIL occurs right after "NAND Write"
Any/all help is very much appreciated. If anyone is NYC local and can give it a shot, that'd be great.
Thanks everyone.

I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?

DUHAsianSKILLZ said:
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
Click to expand...
Click to collapse
I've read that thread before, not the same issue. But thanks for the heads up nevertheless

postulio said:
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
Click to expand...
Click to collapse
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.

I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.

DUHAsianSKILLZ said:
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
Click to expand...
Click to collapse
no go.

postulio said:
no go.
Click to expand...
Click to collapse
Does your tar have .md5 at the end of the filename? I think it should fail earlier if this is the problem but maybe its not being properly verified? Its just a shot in the dark but try removing the .md5 if its there and just flash the straight .tar file. Or retry download maybe you got a corrupt copy.
Sent from my Nexus 7 using XDA Free mobile app

Ripx88 said:
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
Click to expand...
Click to collapse
HAHAHAHA BINGO!!!!
woooo!
cfautoroot: BAM! worked first try.
everybody dance.
Thank you very much for this genius tidbit. I must've enabled it the first day I got the tablet and forgot all about it as It's never been an option on any of my other devices.
Huge thanks to both of you guys for bending over backwards trying to find a solution as to why the flashing wasn't working. Now we know.
Pretty clever of Samsung to hide an Odin flash lockout switch within the actual OS (as opposed to recovery).

Unknown Device connection to pc

All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.

Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?

tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.

And you've removed all drivers to android and lg for it.

secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.

Which version of windows are you running? On both desktop and laptop???

secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.

Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?

secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.

I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.

secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.

I have this phone at least for another year. So at least someone out here is still willing to help.

secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..

Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.

secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.