I just got my Galaxy S2 yesterday, and I'm trying to get the appropriate drivers installed on my PC so that I can go about rooting it.
If I just connect my phone to the USB port, I see a new Portable Device, "GT-I9100", and I can browse that to see my phone's filesystem.
But Kies fails to connect to the phone (It just sits there saying "Connecting..."), and if I look in Device Manager I see, under "Other Devices", a device called "CDC Serial", which doesn't have a driver installed.
I've tried un-installing and re-installing Kies which, according to my web searches should install the driver, but it makes no difference.
I understand this driver is a prerequisite for being able to run Odin and root my phone.
I've searched this forum and Googled my question and have yet to find an answer to my problem.
I'm running Win7 64-bit.
Anyone got any ideas?
Did you install Kies on your pc? I had a similar problem yesterday but solved it after downloading Samsung Kies from www.samsung.com and it worked perfectly.
You need to download Kies manually onto your pc in order for Kies on your phone to detect and connect to your PC.
Yes I installed Kies, which is why I mentioned "I've tried un-installing and re-installing Kies"
That was the solution I'd found by Googling, but it had no effect on the problem.
Are you using 64-bit win7? I'm wondering if that's relevant to my problem.
am using Win Vista...
hmm.. sorry mate.. can't really advise u... cause I am just a noob like you.. Lol.. good luck with that~!
davedontmind said:
I just got my Galaxy S2 yesterday, and I'm trying to get the appropriate drivers installed on my PC so that I can go about rooting it.
If I just connect my phone to the USB port, I see a new Portable Device, "GT-I9100", and I can browse that to see my phone's filesystem.
But Kies fails to connect to the phone (It just sits there saying "Connecting..."), and if I look in Device Manager I see, under "Other Devices", a device called "CDC Serial", which doesn't have a driver installed.
I've tried un-installing and re-installing Kies which, according to my web searches should install the driver, but it makes no difference.
I understand this driver is a prerequisite for being able to run Odin and root my phone.
I've searched this forum and Googled my question and have yet to find an answer to my problem.
I'm running Win7 64-bit.
Anyone got any ideas?
Click to expand...
Click to collapse
I've been facing the exact same problem on my system (Win 7) as well (Thankfully I updated my phone firmware while I was on older version of Kies so Phone is up to date <I'm using the Indian version of the Galaxy S II. PHONE: I9100DDKE4>, however the CDC Serial driver issue started as soon as I updated Kies).
I tried downloading a driver set from the internet for Samsung Galaxy S, - but that didn't work either.
I had earlier updated Kies using the Kies updater itself and thought that might be causing the issue, so, I downloaded the .exe of the new Kies from the Samsung support website and installed it again - unfortunately, this didn't work either and the CDC error remains.
I also tried using different USB ports to connect my phone - again - no luck.
I will try some more troubleshooting once I get home from work and will let you know if anything works out.
In case you are able to figure a way out - please do share the resolution steps.
Tried and failed. Haven't even got Kies on my PC any more. If you are going to root and use custom ROMS then just use Odin. Can't really see any use for Kies.
@davedontmind,
Something simple , but, go into settings/applications/development and make sure usb debugging is UNTICKED. Kies wont connect to the phone if you have it ticked. Also, dont run odin and kies at the same time.
Sent from my GT-P1000 using XDA Premium App
Hmm, I am having Win7 64-bit. I also had the same problem with CDC Serial and Samsung_Android being in the unidentified devices in the device manager. Then I downloaded and installed Kies. After that connected S2 with USB Debugging checked (enabled), the drivers began installing on their own from Windows update. Now I have a 'Samsung Android Phone' as a device and 'Samsung Android ADB Interface' under it.
Hope this helps.
choose reinstall drivers throught kies solved fo me !
I had the same issue, and even choosing to reinstall drivers from within kies didn't work, but if u browse to program files and look for the kies folder there should be a folder called usb drivers with an exe in, run this and all should work fine.
Sent from my GT-I9100 using XDA App
Possible solution CDC Driver and Keis Connecting Spin
I've been fighting with this off and on all today.
I have had no joy with the downloads of the drivers at all (the all seemed to error out on install). I am using Windows 7 (32 and 64 bit).
I found a mention somewhere else about "USB Composite Device" being detected as part of the install chain. Sorry, I can't remember where, but it sent me down a path of thought. They were right, it does get detected.
The KEY thing is that THIS is wrong and it then causes all the other problems I believe.
It should be a "SAMSUNG Mobile USB Composite Device"!
If you change this to correct device (and you might need to make it something else to force it to go to the net and get it) it will then find the others correctly too (although you might have to unplug and plug in a few times).
BTW, CDC becomes a "SAMSUNG Mobile USB Modem" and the MTP becomes "GT-I9100".
And then everything is right with the world (and Keis seems to find my phone!!).
And now finally I can go to bed happy .
Gavin
wardy666 said:
I had the same issue, and even choosing to reinstall drivers from within kies didn't work, but if u browse to program files and look for the kies folder there should be a folder called usb drivers with an exe in, run this and all should work fine.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Man..i`ve been trying to solve this retard problem for like the last 10 hours..and ur small tip saved my ass just now.. Thanks alot
You dont need to install Keis to get the drivers (win7). As Gavin stated the device will be listed as a USB composite device (under Universal Serial Bus Controllers) , just right click and update drivers on the composite device and it will then change to SAMSUNG Mobile USB Composite Device. Your phone will then be listed as a SAMSUNG Andoid Phone higher up with a subtree giving an adb interface.
Phone in USB debug Mode
Plug in USB
Windows 7 searched for drivers (none found)
Control panel -> device manager
Universal Serial Bus Controllers -> USB Composite device
Right Click -> Update Driver Software (net connection needed)
Do the above step for each USB Composite device if you do not know which one to update.
psc001 said:
You dont need to install Keis to get the drivers (win7). As Gavin stated the device will be listed as a USB composite device (under Universal Serial Bus Controllers) , just right click and update drivers on the composite device and it will then change to SAMSUNG Mobile USB Composite Device. Your phone will then be listed as a SAMSUNG Andoid Phone higher up with a subtree giving an adb interface.
Phone in USB debug Mode
Plug in USB
Windows 7 searched for drivers (none found)
Control panel -> device manager
Universal Serial Bus Controllers -> USB Composite device
Right Click -> Update Driver Software (net connection needed)
Do the above step for each USB Composite device if you do not know which one to update.
Click to expand...
Click to collapse
Still nothing.
No driver found
cdc serial error.hardware drivers not found error
please install Kies updated version manually as it contains hardware drivers for all samsung models.it worked for me.
mr_bravery said:
I've been fighting with this off and on all today.
I have had no joy with the downloads of the drivers at all (the all seemed to error out on install). I am using Windows 7 (32 and 64 bit).
I found a mention somewhere else about "USB Composite Device" being detected as part of the install chain. Sorry, I can't remember where, but it sent me down a path of thought. They were right, it does get detected.
The KEY thing is that THIS is wrong and it then causes all the other problems I believe.
It should be a "SAMSUNG Mobile USB Composite Device"!
If you change this to correct device (and you might need to make it something else to force it to go to the net and get it) it will then find the others correctly too (although you might have to unplug and plug in a few times).
BTW, CDC becomes a "SAMSUNG Mobile USB Modem" and the MTP becomes "GT-I9100".
And then everything is right with the world (and Keis seems to find my phone!!).
And now finally I can go to bed happy .
Gavin
Click to expand...
Click to collapse
i can confirm that this worked for me - cheers gavin !
i just worked my way through the USB Composite Devices that were listed under device manager, choosing to Update Driver Software then Search Automatically For Updated Driver Software and one of them turned out to be my phone.
psc001 said:
You dont need to install Keis to get the drivers (win7). As Gavin stated the device will be listed as a USB composite device (under Universal Serial Bus Controllers) , just right click and update drivers on the composite device and it will then change to SAMSUNG Mobile USB Composite Device. Your phone will then be listed as a SAMSUNG Andoid Phone higher up with a subtree giving an adb interface.
Phone in USB debug Mode
Plug in USB
Windows 7 searched for drivers (none found)
Control panel -> device manager
Universal Serial Bus Controllers -> USB Composite device
Right Click -> Update Driver Software (net connection needed)
Do the above step for each USB Composite device if you do not know which one to update.
Click to expand...
Click to collapse
This worked like a freaking charm.
psc001 said:
You dont need to install Keis to get the drivers (win7). As Gavin stated the device will be listed as a USB composite device (under Universal Serial Bus Controllers) , just right click and update drivers on the composite device and it will then change to SAMSUNG Mobile USB Composite Device. Your phone will then be listed as a SAMSUNG Andoid Phone higher up with a subtree giving an adb interface.
Phone in USB debug Mode
Plug in USB
Windows 7 searched for drivers (none found)
Control panel -> device manager
Universal Serial Bus Controllers -> USB Composite device
Right Click -> Update Driver Software (net connection needed)
Do the above step for each USB Composite device if you do not know which one to update.
Click to expand...
Click to collapse
I can confirm that this works for XP64 with the only change being that "device manager" is under "System". Thanks for giving the obvious (in hindsight) answer. MS had the drivers we needed!!!
I was actually looking this up for a band-aid fix for the 10.1!!!! Worked like a charm.
mr_bravery said:
I've been fighting with this off and on all today.
I have had no joy with the downloads of the drivers at all (the all seemed to error out on install). I am using Windows 7 (32 and 64 bit).
I found a mention somewhere else about "USB Composite Device" being detected as part of the install chain. Sorry, I can't remember where, but it sent me down a path of thought. They were right, it does get detected.
The KEY thing is that THIS is wrong and it then causes all the other problems I believe.
It should be a "SAMSUNG Mobile USB Composite Device"!
If you change this to correct device (and you might need to make it something else to force it to go to the net and get it) it will then find the others correctly too (although you might have to unplug and plug in a few times).
BTW, CDC becomes a "SAMSUNG Mobile USB Modem" and the MTP becomes "GT-I9100".
And then everything is right with the world (and Keis seems to find my phone!!).
And now finally I can go to bed happy .
Gavin
Click to expand...
Click to collapse
Oh my god!! I have been looking for the a solution for this problem for over a day and finally this suggestion solved the issue!!
Thanks a lot for your help!!!
Thanks psc001. It really solved issue. Here's what i did.
Phone in USB debug Mode
Plug in USB
Windows 7 searched for drivers (none found)
Control Panel -->Device Manager
Universal Serial Bus Controllers -> USB Composite device
Right Click -> Update Driver Software (net connection needed)
PLUS
CDC serial or CDC ......modem something anything with CDC Right Click -> Update Driver Software (net connection needed)
samsung MTP... do the same ,...Right Click -> Update Driver Software (net connection needed)
now disconnect phone and reconnect.
now open Kies.
Thanks
Hello Everyone,
I've been searching the interwebs for the last few days trying to find out where I download a compiled driver, or a way to compile my own for my Acer a500 tablet.
Here's my specs:
Tablet:
Model: A500 (rooted)
Android: 4.0.3(ICS)
Kernel: 2.6.39.4+
USB Ethernet Adapter:
Model: Trendnet TU2-ET100
Chipset: ASIX AX88772
Driver: v4.4 (Android 1,2,3,4)
I have found LOADS of compiled drivers for Android 3.2.x, but nothing for 4.0.x This is my first tablet and I just bought it yesterday, so I'm trying to learn as much as I can about it, please forgive me if I seem noobish here, i am.. I have already downloaded the latest ASIX driver (v4.4) from the chipset manufacturer, but when I try to compile it with the "make command" I get a return that it is not a recognized command.
I have also read multiple times that the Android OS already has ASIX drivers embedded, however when I plug my adapter into the USB slot I do not see any lights illuminate. I attempted to provide the adapter with dhcp in terminal, using;
Code:
dhcpcd eth0
setprop net.dns1 8.8.8.8
setprop net.dns2 8.8.4.4
I don't get any error messages, but nothing is happening either.
I decided to check the device after plugging it in by using dmesg, it reported the following:
Code:
usb 1-1: new high speed USB device number 5 using tegra-ehci
usb 1-1: New USB device found, idVendor=0b95, idProduct=7720
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: AX88x72A
usb 1-1: Manufacturer: ASIX Elec. Corp.
usb 1-1: SerialNumber: 0BAA93
What do I need to do to get this USB Adapter to work?
Fervid said:
I've been searching the interwebs for the last few days trying to find out where I download a compiled driver, or a way to compile my own for my Acer a500 tablet.
Click to expand...
Click to collapse
Just updating this.
After spending the amount of time I did trying to find a solution. I ended up giving up and rolling back my a500 to Android 3.2.1 Now using the appropriate asix.ko driver for my kernal the external usb adapter works perfectly. I guess I will just have to hold off on upgrading to ICS until its had the chance to be in the market for a bit longer.
Ferv.
I just found a way to do this for the Samsung Galaxy S3, documented here: http://forum.xda-developers.com/showthread.php?p=37548841#post37548841
Hope that helps point you in the right direction...
Hi,
I am using nexus 4 and updated to latest version of android 4.4.4
And just after updating my soft keys stopped working I had no clue what should be done.
So i thought of formatting it But my nexus wont connect to my laptop it says device descriptor failed with code 43 on Device manager of windows.
This USB issue is surely not because of update.Because my USB was not recognized when i was using 4.2 also I have tried on windows 7 and windows 8 also.All says the same code error.
I am FED up trying on the WINDOWS SIDE(taking out battery,usb power off and etc etc) and ANDROID SIDE(installing adb,installing drivers from wugfresh steps and etc etc)
I am not getting how to proceed.Because nothing is helping me out.My nexus do not connect to my lenovo laptop.... anyone help me please
poorNexus4User said:
Hi,
I am using nexus 4 and updated to latest version of android 4.4.4
And just after updating my soft keys stopped working I had no clue what should be done.
So i thought of formatting it But my nexus wont connect to my laptop it says device descriptor failed with code 43 on Device manager of windows.
This USB issue is surely not because of update.Because my USB was not recognized when i was using 4.2 also I have tried on windows 7 and windows 8 also.All says the same code error.
I am FED up trying on the WINDOWS SIDE(taking out battery,usb power off and etc etc) and ANDROID SIDE(installing adb,installing drivers from wugfresh steps and etc etc)
I am not getting how to proceed.Because nothing is helping me out.My nexus do not connect to my lenovo laptop.... anyone help me please
Click to expand...
Click to collapse
do you want to connect for development? are you having problems with drivers (if you go to Device Manager is it showing driver problems)?
frangulyan.dev said:
do you want to connect for development? are you having problems with drivers (if you go to Device Manager is it showing driver problems)?
Click to expand...
Click to collapse
Thanks for responding.
I do not want to do any development actually.
I just want to flash my phone.But the biggest problem is i am not able to connect it via usb.I can see other phone in my same laptop.
I have tried changing USB and have tried connecting it with other win7,win8 systems.
It just says device descriptor request failed.Nothing else in the device manager.Just that yellow mark at device descriptor request failed with code 43.
I really need someones help.My phone is of no use now.
Thanks
poorNexus4User said:
Hi,
I am using nexus 4 and updated to latest version of android 4.4.4
And just after updating my soft keys stopped working I had no clue what should be done.
So i thought of formatting it But my nexus wont connect to my laptop it says device descriptor failed with code 43 on Device manager of windows.
This USB issue is surely not because of update.Because my USB was not recognized when i was using 4.2 also I have tried on windows 7 and windows 8 also.All says the same code error.
I am FED up trying on the WINDOWS SIDE(taking out battery,usb power off and etc etc) and ANDROID SIDE(installing adb,installing drivers from wugfresh steps and etc etc)
I am not getting how to proceed.Because nothing is helping me out.My nexus do not connect to my lenovo laptop.... anyone help me please
Click to expand...
Click to collapse
install vmware player or virtual box. and in it install windows seven in it.
jahanzaib khan said:
install vmware player or virtual box. and in it install windows seven in it.
Click to expand...
Click to collapse
I am asking for a solution not a dumb advice.
Activate Developer Mode and tick on USB debugging , hope this will help u.