So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
espy1988 said:
So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
Click to expand...
Click to collapse
I have the same problem on my PC. I would plug in the phone and my mouse would stop working. No tethering app installed or anything.
Anyway, I just tried the ports on the back of the PC and those worked. Try a port closer to the MB
I've tried all my ports. It's still not recognized.
Check the cable and power source. Be sure cable is with good quality. I hade the same issue. I fixed it with original HTC cable and back panel USB from my deskop computer. Front USB of desktop computers often are not enough to power that consumption.
After updating to Froyo it started working again. Thanks though. I still have no clue what caused it.
Bumping to confirm, I found this thread after getting the same error. I had tried several of the USB ports on my computer but after reading this tried the 2 I hadn't yet, they both worked. Not sure why only those work now, but they do work.
Hope this helps someone.
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Vibrant UnBrickable Mod
The same thing is happening to my Vibrant. Tried Rooting and installing various ROMs and it is still "Not Recognized". Tried all ports on all PCs (4) and Laptops (1) and non of them work. espy1988, how did you upgrade to Froyo 2.2 if you could not connect to PC and Kies? This used to work without an issue.
Thanks
Tombias said:
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Click to expand...
Click to collapse
Like said above u might need to be debricked.
seems like ur phone is hard bricked.
---------- Post added at 04:33 AM ---------- Previous post was at 04:26 AM ----------
have u tried Odin back to stock using Odin or hemidal ?
I have the same problem now. I have had my Vibrant for over a year never with an issue. I have Odined it back to JFD dozens of times but now it will not recognize the usb device.
I have GB bootloaders, but never a problem before. When changing Roms I usually Odin back to JFD first and start clean.
My problem started with the phone getting stuck in landscape mode. I was running a 2.3.4 GB rom Sensation. I reflashed a few times but whenever a restored anything from Titanium it would revert back to landscape only. I decided to go back to a 2.2 rom and plugged in the phone to Odin and it was not recognized, also not as a mass storage device, no go. I used Samba to copy a 2.2 rom, Trigger, to the phone and flashed from there. The phone is good now except the computer still won't recognize it. I can use Samba to access the SDCard but I hate not being able to use Odin if things go south. Tried all usb ports and a new cable, no go. Really wierd.
Looking for suggestions......
If you're still under warranty claim it & send it.
Had same problem. There is no fix short of replacing USB port.
I found my problem. It was dirty/corroded usb port. I carefully cleaned it out (took a few times) and it's all functioning again. I also cleaned the contacts on my original usb cord and it is working again also.
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
jnusz said:
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
Click to expand...
Click to collapse
Have you tried installing the installing/re-installing the Samsung drivers (LINK), using another USB cable, or even another computer? I just want to make sure you've tried it all before attempting to do a hardware mod.
Anyhow, you can find a link to the unbrickable mod and other hardware mods in the "Official XDA Vibrant Bible Thread", under the "MODS/SCRIPTS" section (LINK).
Mine is the cable btw. My wife has a GSII and I was able to use her cable.
I previously rooted my phone without difficulty. Using titanium backup and an number of other apps that required superuser/root acess. I am now trying to flash a Froyo rom. I had upgraded the home PC to a win 7 Pro (64 bit) machine and for some reason I can not get USB drivers to work. I have download drivers from several different threads. SOme fail to load while others seem to install. The Fascinate is recognized but not the modem and I can not get odin to see the device in software download mode.
Any thoughts?
Your best test of whether drivers are installed properly is to install adb and do 'adb devices'. If one shows up in the list you are installed correctly.
You may have an incorrect driver installed. The best place to download these is Samsung directly. If all else fails you can try a different computer and/or heimdall instead of odin.
Swyped w/ XDA App. A clean tie attracts the soup of the day.
get the drivers from samsung, or one of the noob threads, and be sure u mount then first go to setting/applications, make sure unknown sources is checks, and then go to development and make sure usb debugging is checked, then plug it in, and on ur phone u should get an option in notification bar that says transfer files.. click on it.. and then click mount.. n try again.. u should have to do this at least once on every phone to get the drivers properly installed.
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
Hi all
I have installed Kies and the USB driver from the Samsung site. When i connect my tablet Win XP pings and says hardward found etc, but then the ping sounds again and i get MTP device error detected. The drive does not show up in My Computer Ive tried several drivers from google and none have worked. Tried the install driver option in Kies and same result. I get the yellow icon in device manager saying MTP driver not found. Its very annoying...
Ive read that XP cant support high power devices and patch is being worked on. But wanted to check if anyone knows whats wrong and has a solution please?
Go to samsung website.
Download the Samusung Kies and install it (it includes samsung device usb drivers)
once this is installed you can connect the Tab and it will be recognized as a phone with a USB storage.
http://www.samsung.com/us/support/downloads/GT-P7510MAVXAB
go to the software.
and download the Kies for windows.
If that still does not work try downloading the actual total Samsung USB driver installation file found here
"http://down.kr.samsungmobile.com/uploadimg/service/support/download/anycall/sw/SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I installed latest version of Kies in my Windows 7 Professional 64bits (UAC disabled, install was "ran as admin")
In the end of the installation process, Windows shows a balloon saying it is installing the driver for the device (note that there is no phone connected to the computer at that moment), but it fails saying that it could not find the driver for the device.
After installation finishes, I can connect the phone, open and use Kies normally, but if I go to Windows device manager, in the "Other devices" branch, it still lists an "Unknown device".
Any idea about how to solve this? I already searched the forum, but could not find anything that worked for me.
Thanks!
PS: I'm using the original USB cable from Samsung.
As long as you are able to connect and work via Kies just leave it. Just check how many people are having problem with Kies, you should consider yourself lucky that you don't have a connection problem
Regards.
Leave your phone plugged in and do a windows update. It should find the missing drivers.
You can find the drivers inside the dir where kies was installed, alternatively a copy is stored on my 4shared, link in my sig.
You can try installing the drivers and see if that helps.
Kies is a huge PITA, you may need to swap USB port and uninstall/reinstal for it to get its act together.
Thanks all who answered.
Unfortunately, Windows Update can't find any driver (already had tried that), and also asking to update the driver and setting it to search in the Kies driver directory has no effect either.