adb drivers in Win7 64

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
I have no problem connecting my Epic 4G Touch to a WinXP system with adb.

On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.

I can mount the device just fine for transferring files. But I need adb for software development.
 

tdunham

Recognized Contributor
Jun 21, 2008
13,686
36,462
0
TampaBay
I have no problem connecting my Epic 4G Touch to a WinXP system with adb.

On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.

I can mount the device just fine for transferring files. But I need adb for software development.
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
 
  • Like
Reactions: j1mmyc

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."

Were you using 64-bit Win7?
 

barnacles10

Retired Recognized Developer
Mar 25, 2010
4,257
1,317
0
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."

Were you using 64-bit Win7?
Uninstall all your drivers from device manager and start fresh. Only install the driver.exe from samsungs support page. Once that is installed plug your phone in and let it run through the drivers before you try anything else.

If your computer isn't recognizing your phone in the first place then it's not a problem with adb, its the drivers, so start there.
 

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
OK, so I uninstalled KIES and the drivers.

I then tried to install the drivers. No go: The installer continues to fail, with the progress bar at around 80-90%. I experimented with running the installer as administrator, installing off of \Program Files (x86) and off of \SAMSUNG, instead of the default \Program Files, and still no go.

I then re-installed KIES, turned off debug in the phone, and plugged it in. Win7 installed a driver for the phone and all was well.

I then unplugged the phone, turned on debug, and plugged it back it. Now Win7 installed the following drivers:
Code:
 USB Composite Device
 USB Mass Storage Device
 Android  UMS Composite USB Device (two of these!)
and said they're ready to use. But it also tried to install:
Code:
 CDC Serial
 SAMSUNG_Android
and it gave "Driver not found" for these.

And "adb devices" lists nothing.

To make sure adb works fine I then plugged in a Kindle Fire. Windows set up the drivers for it and it showed up in "adb devices" just fine.
 

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
I still can't get it working.

I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.

The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?

I even tried turning off Windows' driver signature checks. Didn't help.

Does anybody have this working 64-bit Win7?
 

garwynn

Retired Forum Moderator / Inactive Recognized Deve
Jul 30, 2011
5,182
8,589
0
NE Ohio
www.extra-life.org
I still can't get it working.

I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.

The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?

I even tried turning off Windows' driver signature checks. Didn't help.

Does anybody have this working 64-bit Win7?
Have it working - and did remember I have Kies installed.
Maybe I downloaded both the separate driver and Kies?

USB Driver Link:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe

Kies Link:
http://org.downloadcenter.samsung.c...0111012045653670/KiesPC_2.0.3.11082_152_4.exe

Know I have problem still with Kies... but I can use ODIN without issues.
 

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
Finally got it!

I can't really explain how I did it, as there was a lot of trial and error and I wasn't keeping notes. But the basic trick was to right click in device manager on the unknown SAMSUNG_Android device, choose Update Driver, choose "Let me pick", choose "Have disk", point to the "SAMSUNG\USB Drivers\25_escape" folder from the KIES installation, and then choose "Samsung Mobile USB Composite Device".

You may then get another unknown device, which using the same method you set to ADB. I did a bunch of stuff in different ways, trying to match different drivers from the 25_escape folder to different devices, until it finally worked.
 
  • Like
Reactions: i2mirage

asuderma

Member
Apr 19, 2012
12
2
0
Golden
Same issue, solved twice

I have had similar problems in win7 64bit twice now. I got it working once, then ended up reinstalling windows for other reasons. I then had the same problem when trying to install cm9alpha3.

Both times it took a strange combination of installing the drivers manually, plugging in the phone, etc. to get it working. The best advice I have for others is to keep trying.

Also, it seems that Kies almost never gets it right. I personally don't even keep it installed.
 

PanchoPlanet

Senior Member
Oct 15, 2011
3,896
984
0
Crooklyn
I posted a guide on how I got this working.

adb works, but I still can't connect to KIES.
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.

Edit
It is rumoured that Kies w will only recognize stock roms.
Pp.
Sent from my tofu plasma converter.
 
Last edited:

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.

Edit
It is rumoured that Kies w will only recognize stock roms.
I am on stock EL29, no root.

It worked once on my WinXP system, but now it doesn't work on either the WinXP or Win7 system.
 

arpruss

Senior Member
Jul 3, 2010
847
413
0
pruss.mobi
Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.
 

hinnn

Senior Member
Jul 18, 2012
440
97
58
Sydney
i021.net
Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.
hi, I have same issue with you now, can you teach me how to solve it? thanks.

WIN7 x64 with GT-I9300
 

philipjmurphy

New member
Oct 18, 2010
1
0
0
Chrome DevTools Inspect working again :)

2015-05-28_161316.png

I couldn't get Chrome Dev Tools to remote debug (chrome://inspect) until I installed the "Android Composite ADB Interface" (just picked the latest version). See screenshot attached (taken before I installed correct driver).

1. To install I right-clicked on the "SAMSUNG_Android" driver under "Other Devices" in the Device Manager.
2. "Update Driver Software..."
3. "Browse my computer for driver software"
4. "Let me pick from a list of device drivers on my computer"
5. Select "Samsung Android Phone"
6. Select "Android Composite ADB Interface Version" (latest one)
7. Ignore warning that Windows does not know if this driver is compatible.

At this point, I saw the "Trust this device" message come up on the Samsung phone :)

Thanks for the help. This was really killing me as I had tried everything including installing the official drivers from Samsung's site (developer.samsung.com/technical-doc/view.do?v=T000000117)

Note: I don't have Windows Kies installed and I am using Windows 7 x64 OS. Also note that this does not fix the "CDC Serial" error, however, this is not required for remote debugging over USB.
 
Last edited: