So, quick backstory. I have two PC's at home. A brand new win 7 64 bit laptop, and an older XP desktop. Neither will recognize my vibrant, and never have. At work, I have a win XP desktop, and I can connect the phone to that and use mass USB storage and move stuff around just fine, so I've gotten by in that regard in these 6 long months.
Then comes this #$%%^$#$ Froyo update. Who thought it would be easy?
I have downloaded kies on each machine. (As well as ODIN, but same issues.....computer/phone wont communicate). I cannot get my two home computers to connect to the phone, no matter what settings. BTW, I have rooted my phone with OCLF and subsequently un-rooted before trying any of the following. I have not flashed or updated the phone otherwise with any other software, other than what apps are available in the market.
I've tried
-USB Debugging on/off
-all 10 USB ports between the three PC's in all configurations
-deleted all USB drivers and restarted on both computers
-installed the appropriate drivers from samsung for each pc
-wasted 7 hours with samsung support troubleshooting to no avail
The USB cable is fine. The most promising progress is on my work PC, where I got Mini Kies going, connected and started the update, it finished decompressing the binary files, but then a USB not recognized warning pop up and kies kicked out the update.
I have installed, reinstalled the drivers for each system several times with samsung support. Nothing is working.
I don't know what else to do. This is the most frustrating experience in my life. Any suggestions or similar experiences that have been remedied?
I was having promblems also but eventually got it to work for me on an xp machine on stock jfd. It updated me to ji6 then I did the ka6 update when it was released. I gave up on my win7 system lol. Is your xp system 32bit or 64?
Sent from my SGH-T959 using XDA App
same here i have a win7 64 bit machine, i can connect to normal kies 1.51. i tried to update, it downloaded the files and just got stuck when it started putting it on the phone (luckily, it did not start the installation so i was okay).
mini kies shows that it recognizes my phone but crashes immediately after that.
i do not think the vibrant is supported by newer versions of kies, like 2.0.
I solved my problem by using my 32bit xp system.
edit: just FYI, i can connect to normal kies 1.51, sync my data and all that stuff. i also updated to ji6 thru normal kies, and I can transfer files and whatnot thru usb. I do not even think i needed to install the drivers manually
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
http://71.228.63.153/download/usb_drivers_GalaxyS_x64.zip
toeshot said:
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
http://71.228.63.153/download/usb_drivers_GalaxyS_x64.zip
Click to expand...
Click to collapse
I did the Same thing it worked for me as well
The only luck I've had is on a winXP 32 bit machine, but then it cuts off the installation when it suddenly says "USB Not Recognized" (despite, um, the fact that it recognized it at the beginning, otherwise I wouldn't have been able to initiate the update!)
I'll give those Win7 64 drivers a try at home, although I'm pretty sure I have downloaded the same ones in my quest for a solution.
Do you suggest plugging in the phone, then installing the drivers, or leaving the phone unconnected and restarting the computer then trying to connect, or ???? The biggest issue on the Win7 machine is the phone not communicating with it AT ALL. Not even showing up in device manager as unknown or anything.
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
SOLVED
I finally got it to work, after about 15 attempts! (on a win XP machine)
Here's what I did in case it will help someone else:
When I plugged in my phone, I saw two items in the USB list in device manager. One said "Samsung Android USB Composite Device" (internal SD?), and the other said "USB Mass Storage Device" (external SD?). In this configuration, I got kicked out of the install each time after it "decompressed the binary files".
So what I did on a hunch was go to the device manager and "update" the driver for the USB Mass storage device to the "ssadadb2.inf" file included in the Vibrant USB drivers available directly from Samsung's Vibrant page.
Selected "Samsung Kies" on the USB settings on the phone, turned on USB Debugging, opened Kies on the computer, plugged in the phone, and it did it's thing.
Only took 3 days to figure it out!
Yeah its been a hit or miss. I have win7 x64 on two laptops and my desktop. It works in the desktop and only one of the laptop and I installed the same drivers for all 3
Sent from my SGH-T959 using XDA App
toeshot said:
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
yeah it works for me too, i just installed these drivers and put usb debugging mode. upgrading just now. thanx
Click to expand...
Click to collapse
W/ WIN 7 64 Bit I upgraded my phone to Froyo.
I'm running win 7 SP1 64 bit.
Samsung told me that Kies mini and the driver is not compatible to 64 bit.
After some research this is what I have done and able to upgrad my phone to Froyo.
1. check the USB debugging.
- Samsung says to uncheck it. but if you do, you probably have MTP USB device error. So make sure your USB debugging is on.
2. After the you connect your phone, Samsung Kies Mini keeps crashing??
-Uninstall IE 9.
Solution is...
*Check the USB Debugging and Uninstall IE 9.
**Make your the battery is fully charged.
Connect phone
Start Kies Mini
I got so sick of Windows I switched to Ubuntu Linux. It's free and just as easy to use as windows. No crashes, no viruses, and it sets up as a dual boot so I can use windows when necessary.
Anyone else been having problems connecting to Kies?
Henco
Nope, worked fine for me first time. Make sure when you first install it you select Tools -> Install Driver. This will install the required USB driver on your system. It's not done automatically it seems.
Yes, Windows 7 x64. Worked on laptop no problem. Main PC. Same OS was a no go. Had a look around, it was to do with CDC driver not installing. This is related to the Samsung USB modem. Found separate Samsung USB drivers had been installed and were out of date and taking precedence over the new Kies install. Solution was to delete any thing Samsung related and start again. Voilà CDC installed just fine.
No problem on win 7 x64 with latest Kies .
jje
Fornowagain said:
Yes, Windows 7 x64. Worked on laptop no problem. Main PC. Same OS was a no go. Had a look around, it was to do with CDC driver not installing. This is related to the Samsung USB modem. Found separate Samsung USB drivers had been installed and were out of date and taking precedence over the new Kies install. Solution was to delete any thing Samsung related and start again. Voilà CDC installed just fine.
Click to expand...
Click to collapse
Windows 7 x64 here too. So what does anything Samsung include? So how do I prevent the out of date drivers taking precedence?
Henco
Found the problem, Kies won't work when in debugging mode.
I have tried everything but it keeps failing
ive been trying for over a week
i have updated my windows updates and im using windows vista
I have tried the USB debugging on and off but no matter what it begins installing but then it pops up on a speech bubble on my tray icon saying it failed
i have kies 2.0 installed and i have tried reinstalling many times
Have you installed Keis on your pc, you don't say if you have?
If you install it then the Sammy drivers will be installed as well, you can the uninstall Keis (not the drivers) if you wish.
Yes i hav kies 2.0 and it tries to install the drivers but fails
sumtyms it says my phone isnt compatible but it definite should be :s
Maybe try some of these tips:
http://forum.xda-developers.com/showthread.php?t=1189473&highlight=vista+drivers
Hi!
Anyone use Kies in Virtualbox? I tried with Win7 guest and WinXP guest on Linux host. Didn't works any of them. If I first connect my phone to the PC then found new hardware but the MTP driver can't be installed. Kies can't handle my phone. It tells me "Connecting..." but after a timeout it fails.
In native windows everythings works fine.
The newest Kies update can't be installed because of the installer craching during downloading the update files.
Any idea?
All the rooted users, here will shrug this off as a "who cares about Kies", but maybe this will save some frustration for others.
Last week I installed Samsung Kies on my Win7 64bit laptop and ever since then I have had nothing but problems with my system not loading correctly. My computer would get to the log in prompt but would not consistently get past the log in prompt. At first I thought it was a driver conflict with my Samsung USB driver as disabling this appeared to resolve the issue. Then today, when I rebooted, all my problems came back (I only reboot once a week or so). This time, removing the driver again via Safe mode didn't solve the problem as it had previously and after methodical trial and error I finally figured out that if I disabled (not delete) the Samsung USB driver and disabled the two Kies startup entries using Windows System Configuration in Safe Mode, I could get my system to load. Once I got in, I uninstalled Kies and all seems to be good again.
A quick search of Google indicates that others running Win7 64bit are also having issues with Kies.
==UPDATE==
Samsung tech support just confirmed to me that Kies does not currently work on Win7 64bit and that they are working on a fix. It would have been nice if they had put a warning on the software download page or made sure the installer refused to install Kies on 64bit Windows. It took hours of restarting to sleuth out the issue.