Kies connectivity problem explained by Samsung.

Im having the same issues with my samsung galexy google nexus GT-i9250, while i try to connect it with my pc (win7 64bit), it keeps me waiting for long time showing "connecting....". Also I installed the driver successfully but the issue still same...plugged in to usb 2 as well.. Pls help..
My device doesnt carry an external SD slot, only 16GB Built in flash..
 
Big Timmeh's suggestion worked.

i ran Kies as an administrator.

GT-3500 2.3.6
Windows7 Home Premium 64-bit
 
I fixed my Sprint's Galaxy SII connectivity issues by going to the Kies website. I downloaded the program for Xp Pro 32 bit. Installed it and everything works fine, was able to transfer photos,videos, and some songs over. Even let me delete from my PC to the phone. I used the USB cable when i did all this. Took awhile for Kies to load... but well worth it. I can even use my easytether app, to get internet on my desktop. For those having issues, try this option. Worked for me.
 
Kies fails and crashes on 3 windows 7 64 bit machines and a Mac OSX 10.8 laptop.
Then after 30-50 seconds a message box appears asking for code, upon entering code it crashes.
and sometimes windows explorer can see the folders in the S3 but not the ext sd card or sd card or the files in the folders.
really strange because i could see all the files when not using kies.
 
There are really two different connectivity issues that are going on. The Kies issue is actually secondary to the BIG problem of the missing hardware ID error that comes up on some machines. On one of my machines, I can plug my phone in, and Windows picks it up EVERY time. That machine has an AMD 890G chipset. The other is a laptop with a NVIDIA chipset in it, and that one requires the "diagnose connection problems" to reinstall the drivers, which GENERALLY lets the machine see the phone ONCE, but if I unplug the phone and plug it back in, "Missing ID" is back.

This problem is more critical than the normal Kies issue since it indicates driver issues that are preventing Windows from properly talking to the phone.

For the Kies not running, or crashing, just go to java.com: Java + You and download the latest version of Java for your machine. You may also want to install the latest Java 6 version. 32 bit is needed for most browsers, but if you have 64 bit Windows, try installing the 64 bit version of Java as well, both 6 and 7.

A new Kies version just came out as well: 2.5.0.12104_15 that also seems quite a bit faster than previous versions.
 
A new Kies version just came out as well: 2.5.0.12104_15 that also seems quite a bit faster than previous versions.

I was going to say this... I loaded that version up last night and it solved my issues. I run Win 7 64 bit at the house. I was getting the "not a compatible device" error.
 
I bought my Samsung Galaxy S in November 2010. The first few times, it connected with the Kies on the CD which came in the packet. But once I started upgrading the Kies, it never connected again. I rolled back to the old Kies, but it was still not connecting.
It connects well with KIES AIR, but you cannot upgrade the firmware or download the Calendar.
All my Contacts in the phone disappeared twice and after the first time it happened, I took the precaution of saving all my Contacts to Google.
But my Samsung Galaxy Tab always connects to Kies and recenly I upgraded the Firmware also.
I used to recommend Samsung to other people and many including my brothers and cousins bought them and are cusrsing me now.
:(
 
I struggled through this for weeks, then inadvertently found a simple solution. Connect the phone before opening Kies. When prompted select open folders to view files (or whatever it says). Minimize that window, open Kies, and it will find and connect to the phone and card just fine. At least this has worked for me everytime.
 
It took me two and a half days to finally get the JB installed via Kies. Now that it's downloaded, My S3 has a butt load of issues.
Including messages stating that TouchWiz has stopped... Also, some unknown app called NQ security(which apparently snuck in during the process)keeps preventing me from doing any online searches.... Seriously??? Samsung has told me to perform a factory reset and then go through the arduous process of re-installing JB-AGAIN!
This totally smacks of mediocrity.....
I also blame AT&T for not allowing an OTA install.
 
First Samsung mobile connected ONCE and never again! I have downloaded the latest update of Kies and tried to connect my new Tab 2 several times without success. Useless!:(
 
It took me two and a half days to finally get the JB installed via Kies. Now that it's downloaded, My S3 has a butt load of issues.
Including messages stating that TouchWiz has stopped... Also, some unknown app called NQ security(which apparently snuck in during the process)keeps preventing me from doing any online searches.... Seriously??? Samsung has told me to perform a factory reset and then go through the arduous process of re-installing JB-AGAIN!
This totally smacks of mediocrity.....
I also blame AT&T for not allowing an OTA install.

A couple years ago, an OTA of a major update got botched and AT&T had to deal with thousands of returns and exchanges of bricked phones. They've been gun-shy about allowing major OTA upgrades since.

And as far as your issues, remember, these phones are like computers now. Sometimes new parts of an OS don't play nice with remnant settings created under an older OS. The fix is to do a clean install...which, in the case of a cell phone, is to perform a factory reset after the upgrade. It sucks to set everything up again, but it is often necessary to correct the incompatibilities that arise from an update. A factory reset should clear up most, if not all of your issues.
 
I had the same issues as everyone above. Drivers failing to install, kies not recognizing my phone. I went to best buy and bought a new usb cable came home and it worked perfectly. Strange to think it could be something as simple as that. Might be worth a try for some of you.

Sent from my SAMSUNG-SGH-I747 using Android Central Forums
 
I struggled through this for weeks, then inadvertently found a simple solution. Connect the phone before opening Kies. When prompted select open folders to view files (or whatever it says). Minimize that window, open Kies, and it will find and connect to the phone and card just fine. At least this has worked for me everytime.

Genius! I had the same problems as everyone else here, tried your tip and it worked perfect. *boggle*
 
Talk about frustrating .....................
I have tried all the suggestions in this thread - still cannot get the computer to connect to my S3.
For the longest time, the computer wouldn't even SEE the S3. Solution to THAT issue was to do a battery pull.
As an ATT user, I don't understand why ATT fails to do an OTA with the JB update.
Stopped at the ATT store today; the two reps I spoke with had never even heard of Kies or JB. Very helpful ... not.
Does anyone know the status of the JB ATT OTA? Is it just rolling out slowly? Or will ATT ever roll it out JB OTA?

Update:

Some progress, but no joy:

Somehow, now the computer both sees the S3 and connects to it. Kies then shows the JB update. But when I click the choice to begin the upgrade, Kies freezes.

I have the latest version of Java.

Computer is Windows 7, 32-bit.

Most of what I have read about Kies is negative; there seem to be few reports of success updating S3 firmware (to JB) using Kies.

Any suggestions before I give up on Kies?
 
Last edited:
Hi all. Seems this is a problem with the S3. I have been trying for a month or two now, and have given up. If you have any good ideas that a "normal" user can use, I would appreciate them. But for now I think the hype is just that, and I'm afraid I will not be able to sync the phone and the laptop.
 
Uninstall antivirus on the S3, and turn off the firewall on the computer for that issue. Also, make sure you have 2GB of free hard drive space on the computer, just to make sure there is space to extract the install image.

Talk about frustrating .....................
I have tried all the suggestions in this thread - still cannot get the computer to connect to my S3.
For the longest time, the computer wouldn't even SEE the S3. Solution to THAT issue was to do a battery pull.
As an ATT user, I don't understand why ATT fails to do an OTA with the JB update.
Stopped at the ATT store today; the two reps I spoke with had never even heard of Kies or JB. Very helpful ... not.
Does anyone know the status of the JB ATT OTA? Is it just rolling out slowly? Or will ATT ever roll it out JB OTA?

Update:

Some progress, but no joy:

Somehow, now the computer both sees the S3 and connects to it. Kies then shows the JB update. But when I click the choice to begin the upgrade, Kies freezes.

I have the latest version of Java.

Computer is Windows 7, 32-bit.

Most of what I have read about Kies is negative; there seem to be few reports of success updating S3 firmware (to JB) using Kies.

Any suggestions before I give up on Kies?
 
Hey there,

just been trawling the net like everyone else as I too hit this same issue. I've found a solution that worked for me and have taken the time to register on this forum just to post a solution in the hope it helps... it applied to a Canon powershot camera!... but worked just as well, even if the registry setting didn't match up exactly.

Solution here: SOLVED:Windows Mobile-based device and Canon Powershot cameras showing code 19 and MTP USB Device failed.

Basically, delete the reg setting it asks for (if you have it - I guess if you don't you won't have the same issue).

=================================
It is suggested to have a look at the following registry. Make a backup of it and remove the Upperfilters setting:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{EEC5AD98-8080-425F-922A-DABF3DE3F69A}
?Upperfilters? = klfltdrv
=================================

I had the Upperfilters setting, it had a different string but as soon as I removed and reconnected, it worked instantly. Truly hope it helps others out too...

Daniel Burns
www.facebook.com/aligntech
 
I just bought a S3 yesterday and have been fighting with Kies all day. It seems to stick at the "Connecting..." part. Also, Windows 7 never really formally installed the device driver for my phone, as far as I recall.

I have noticed that the USB input on the phone is VERY sensitive. I'm not sure if it's the phone input or the USB cable itself but I can put a little pressure on it and the phone disconnects (I can hear the USB disconnect noise). This obviously causes Kies to not recognize the phone even more than normal.

Is my phone's USB input faulty? Should I be taking it back to the AT&T store today?
 
I tried ALL of the tips and tricks, just like the last time I updated my phone. Still nothing. MTP device drivers will not load, wont work on either Win 7 x64 machines I have, and one is a new build/OS load and one it worked on before...foolishly I updated Kies and now it will not work any longer.

Kies is probably the worst software I have been forced to use, period. And I work with hundreds of software titles every week.

Kies = Junk
 
Well the first entry in this thread was December 2012 yet here we are on the 18th August 2013 and we are STILL having horrendous problems not only with updating firmware on phones but just with updating Kies software. It has taken me over an hour to update Kies and I haven't YET started to try and update the firmware on my wifes Galaxy S I9000.

I cannot believe how useless this piece of software is nor how a company that produces the Galaxy S, S2, S3 and S4 can have produced Kies!!!!!!

No I don't believe them when they blame it on the number of updates, other mobile phone companies seem to cope so why can't they.

If they're not careful everyone will turn to ODIN and Custom ROMs................at least they work, are up to date and take only minutes to flash.