Database Users

ADB Drivers for XP

Searched everywhere... couldn't find anything.
The drivers for ADB must be different for windows xp... no? When trying to use the the .inf file for the drivers from the package in the windows vista/7 thread, I get the following message:
The specified location does not contain information about your hardware
Click to expand...
Click to collapse
I looked around for a different XP driver package but couldn't find one. Everythings up and running great on my home box running windows 7... but I'd like to get all set up here at work on the XP box as well.
Any help much appreciated. Thanks!

As far as I know Moto only has 2 sets of drivers tha twork on any version of windows. You jus thave to make sure you have the right set depensing on the OS. They have them separarte at 32bit or 64bit.
Anywhoo I have used both sets from this link and have no trouble. Reason I say that is at work my comp is still XP, but at home the laptop is Win7 64bit
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers

sadly... same result with those drivers. get the following message when trying to use the .inf files with those packages:
The specified location does not contain information about your hardware
Click to expand...
Click to collapse

byproxy said:
sadly... same result with those drivers. get the following message when trying to use the .inf files with those packages:
Click to expand...
Click to collapse
Don't try using the *.inf. Install the app, then go to programs in XP and run the Moto driver installation to clean, then clean and reinstall and you should be good to go. Personally in all my experience I've never had good luck pointing to the *.inf

thanks for the info. tried that and again... no dice. it sucks, but i guess it's not a huge deal. i can adb in from my win7 box no problem. would just be nice to know i could do it from this xp box as well.
oh well! thanks anyway for trying to help though!

This just makes no sense. Be tha tas it may try this link out and grab the drivers they have posted there and see if it does the trick.
http://alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167

will2live said:
This just makes no sense. Be tha tas it may try this link out and grab the drivers they have posted there and see if it does the trick.
http://alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167
Click to expand...
Click to collapse
ya... i agree. i could see the drivers not working, but the message saying that the file doesn't even have info on my device is just weird.
the drivers in that post are the first ones i tried. they worked great on my win7 box at home... but same message here on the XP box.

yea it is odd t osay the least. and the even more weird part is I have 2 comps setup with the same OS's you have and don't have the trouble. there has got to be something corrupted or casuing the XP box to not work right for whatever reason.
One suggestion I'd have is to compeltely uninstall the drivers. then grab a copy od CCleaner which is free mind you and run the registry scan to clear up unneeded crap left behind. I'd run it a couple of times until nothing else shows up on the list. Once done reboot the comp and then try the drivers again and see what you get. Ccleaner does a grea tjob of cleaning up the registry and I've used it many times for friends trying to clean things up for them when they have issues.

byproxy said:
Searched everywhere... couldn't find anything.
The drivers for ADB must be different for windows xp... no? When trying to use the the .inf file for the drivers from the package in the windows vista/7 thread, I get the following message:
I looked around for a different XP driver package but couldn't find one. Everythings up and running great on my home box running windows 7... but I'd like to get all set up here at work on the XP box as well.
Any help much appreciated. Thanks!
Click to expand...
Click to collapse
In order to get adb you need android sdk files which are located here... Android SDK

dr154 said:
In order to get adb you need android sdk files which are located here... Android SDK
Click to expand...
Click to collapse
have sdk installed already. i was running my dinc off of the XP box before i got the DX... so sdk is already installed and ready to go.
i'll try a full driver clean-out tomorrow (if i have time) and see if that might work. it's just odd that the .inf file isn't registering with windows as being associated with the phone. seems to me that if it was a problem with an already installed driver, the new driver just wouldn't work after installed. the problem here is that i can't even get XP to accept the .inf file as one that works with the phone.
anyway... will play around with it tomorrow as time permits (after all... the xp box is my work machine. lol).
thanks gents for the input.

I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.

Insta said:
I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.
Click to expand...
Click to collapse
You're awesome dude.. I was having this problem and these steps worked perfectly for me!

showson1 said:
You're awesome dude.. I was having this problem and these steps worked perfectly for me!
Click to expand...
Click to collapse
Glad it worked for you.

Insta said:
Glad it worked for you.
Click to expand...
Click to collapse
Worked for me too. You're a rock star. Thanks a ton for the help!!
FYI for others... the hardware ID's change for each of the USB connection modes. I just saved as two separate .inf files... one for charge only and one for mass storage mode.
Anyway, awesome instructions. Thanks again!

Insta. Can I be the father of your children? I love you that much..... haha!

Ok...that was freakin amazing!!!! I was busting my head all day at work trying to figure out why it wouldnt work.
Thanks so much!!

Also wanted to add my thanks, worked for me too.

THX
Nice work.

Insta said:
I had the same issue with my work pc which is xp pro. If you pm me ill give you the process to fix your problem when I get into work tomorrow. -Insta
Sent from my Droid X using XDA App
Update:
Now I'm at my PC so I can just write this out for you.
1. Plug in phone to PC. Set to charge only. Make sure USB Debugging is turned on. (Need help with these steps? Ask.)
2. Right click on My Computer and go to Manage.
3. Click on Device Manager.
4. Right click on Motorola ADB Interface and go to Properties.
5. Go to the details tab and make sure hardware IDs is selected in the dropdown.
6. Download the ADBDriver_v3_Google.zip from here: alldroid.org/Default.aspx?tabid=40&g=posts&m=5167&#post5167 (Member forever but first time post lol cant give link)
7. Extract the zip file somewhere easily found.
8. Go to the usb_driver directory extracted from the zip and open android_winusb.inf with a text editor
9. Under the Moto Sholes edit the driver hardware ID after USB\ to match that of what your hardware ID is from step 5.
10. Save and close the .inf
11. Update the driver specifying the new .inf you created. (Need help? Ask.)
12. Repeat steps as necessary to install ADB drivers for Storage Card mode.
I've added pictures to try to help explain what needs to be the same.
PM me if you have any problems with this and I'll be glad to assist you with your driver.
Click to expand...
Click to collapse
Awesome! Did the trick for me as well!
I have a HTC Desire, if someone else need it, here is the lines to add to the file if you have Desire:
[Google.NTx86]
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01
or
[Google.NTamd64]
;HTC Desire
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C87&MI_01

Insta I can really use some help. I was so glad to find this thread and prayed it would work. I tried your instructions to the t but maybe i didnt understand something. when i went to update the drivers and pointed windows to the edited inf file it gave me an error saying the folder you specified doesnt contain a compatible driver blah blah. UGHHHH If only you could hear me screaming I HATE WINDOWS!!! Ok calm now, sorry for that. Please let me know what im doing wrong. Thanks

[help] cant get fastboot driver working

I just got a dell streak and I am trying to install the fastboot drivers in windows xp. I boot the phone into fastboot and select the fastboot option. Then I wait 10 seconds and plug in the usb cable into the streak. The computer tried to install the driver and I go to device manager, right click, update driver and try to manually install the driver, but when I select google, inc the only drive that i have available is android composite adb interface. I dont get the option for android boot loader interface. I must be doing something wrong.
On my dell streak screen it says wait for usb fastboot detect. after 10 seconds it still says this. is it suppose to say fastboot or is that after you install the drivers?
Ive spent all night and cant seem to get windows to recognize my streak in fastboot. Now when I plug the streak in on the wait for usb fastboot detect my streak shows up in windows as 'usb device'. it doenst even show up as android device, just usb device.
I really hope someone can help me.

I think it has to do with my android_winusb.inf. Can someone open their android_winusb.inf and copy/paste it here? I have this string in mine:
; Dell Mini5
%SingleAdbInterface% = USB_Install, USB\VID_413C&PID_B007
%CompositeAdbInterface% = USB_Install, USB\VID_413C&PID_B007&MI_01
I am guessing there should be a %SingleBootLoaderInterface% string in there also that would allow the bootloader driver to show up when i try to manually select the drivers.

Looks like you have not got the drivers installed download the dell suite from dell look around the forum their is a way to tell u how to find the drivers on ur PC. If u cannot do it or no one has posted how to do it when I am at the PC later I will tell u
Sent from my Dell Streak using XDA App

Yes the dell pc suite is installed. I installed the one that was on my streaks internal card and I also tried one from dells site. I also followed the guide to manually install the drivers but shipping will the boot loader driver wont show up. Ive tried pointing windows to the dell programs folder to look for the driver as well.
Sent from my Dell Streak using XDA App

Can someone who has fastboot working please paste the text inside their android_winusb.inf so I can get the correct codes.for the streak?
Sent from my Dell Streak using XDA App

I could never get mine to work in fast boot either. I was not able to send commands through fast boot. It took me days to figure out how to get my Streak running 2.2 but I did and without FB.
Now I am having constant problems with my Streak rebooting and was advised to go back to 1.6 and start all over

Well no luck so far and nobody has posted what I believe will solve my problem. I just had to exchange my streak because of a dead pixel. I would like to get this working hopefully someone can help.
Sent from my Dell Streak using XDA App

Another solution if you still cant find the drivers Go to device manager Right click Android 1.0 Select Update Driver Software Select Browse my computer.... Select Let me pick Select All Hardware Scroll down to Google INC Select Bootloader and you should be good to go

I did that already. Doesnt show the bootloader driver. That is the problem. Only shows the composite adb driver.
Sent from my Dell Streak using XDA App

When I tried searching, Google never showed anywhere and that was after waiting for a few minutes for it to appear.
It was/is so frustrating! The instructions are easy to follow but when a pc doesn't give the optioons listed in the instructions, its irritating. I would still like to be able to do it the way everyone one does but I cannot get it to work that way.
Sent from my Dell Streak using XDA App

ok here is what worked for me..... Make sure you have the dell software installed - Then go to fastboot on the streak wait 10 seconds plug it in - don't worry about installing the drivers when the popup stuff comes up - go to device manager - there should be that caution crap next to the android device - right click on it to update the driver - chose pick from list - you will see android something and android phone (click on android phone) something will popup saying it ain't right blah blah blah - push continue and ok and let it install - look at your phone it should be in fastboot mode and Flash till your heart's Happy

Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf

Laaf2005 said:
Ok everyone keeps telling me to do what I have already tried. Can someone go to their C:\Program Files\Dell\PC Suite\Drv folder and open the file android_winusb.inf in notepad and paste it here for me? Someone who has a working fastboot.
And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf
Click to expand...
Click to collapse
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?

"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.

rnj79 said:
Curious if you and I are having identical problems... My Streak does show fastboot_mode on its white screen but when I try to run commands from my pc- it doesn't work (i.e. waiting for device, etc.) Also I get those two same driver options as you. At this very minute, I am connected in debug mode and under my device manger I have "ADB Interface>Android Composite ADB Interface"
Is this what your pc shows?
Click to expand...
Click to collapse
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.

rnj79 said:
"And for anyone suggesting to manually install the drivers I have already done that and there is no option for bootloader driver, just composite adb driver and interface adb driver which when I use either one do not work for fastboot. When I type fastboot devices it doesnt show my streak and if i type fastboot reboot it just says waiting for device so those 2 drivers will not work. Either the pc suite doesnt have the fastboot drivers or something is wrong with my android_winusb.inf"
The only files I have in that folder are .dll files. I have no .inf files.
Click to expand...
Click to collapse
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.

Laaf2005 said:
Yes it is. And its not the correct driver. You need adb bootloader driver.
If someone cant post the android_winusb.inf can someone put their dell into fastboot mode then go to device manager in windows and find the android phone device, right click and select properties. Then to go details and tell me what it says under device id. That will help me a bunch and I may be able to get it working. If so I will post how for anyone having this issue.
Click to expand...
Click to collapse
I'm just like you! I cannot find the bootloader driver. Surely it can't be just the two of us with this stupid issue?

Laaf2005 said:
Are you sure you didnt go into the i386 folder? the inf file is located one folder up. I have .dll's in my C:\Program Files\Dell\PC Suite\Drv\i386 but if you go back to the parent folder Drv then you should see a .inf file. Its ok though because if you are having the same problem I am your .inf wont help. I need it from someone who has fastboot working.
Click to expand...
Click to collapse
I have no .inf files in the DRV folder. The only folder in that is i386 otherwise, the DRV folder is empty. Obviously I'm not going to be of any help to you but at least I know I am not alone and am not crazy- thats the part that helps

Well I dont know why its empty, but I have a .inf in my folder. its for basically telling your computer which streak drivers you have available and in the file it only lists adb composite driver with the id for the driver. All I need is for someone to post the device id of the bootloader driver so i can try adding it. Or if someone can post the drivers here.

I beleive i have the same priblem, there is no way i can install android fastboot, ive tried the pc suite, manual random drivers from the internet and nothing, so annoying
Arya
Sent from my Dell Streak using XDA App

[Q] ADB not recognizing, please help

Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.

If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk

neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb

corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App

Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)

So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk

Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben

Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2

What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000

METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.

I'm going to test in my desktop this weekend to check if it works with it.

I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.

I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA

Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf

I got my i9000 recognized using the latest drives from the Google sdk

That‘s great

http://ics.samsung-updates.com/addons/usb_driver.zip

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)

USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me

The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !

these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.

I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

Vega clone USB drivers problem (and bootloop)

Ok so i was running Vegabean beta6 on my ntt smartbook pad umts but it didn't work well so i thought ill install CM10.1 Build 15 rom.
And now im stuck on bootloop. After couple hours i have finally get into nvflash mode. But the real problem is that i can't install drivers.
Im runing on win 8 32bit and its still saying "unknown device"
I tried to install it manually, (Device manager-> Update software drivers -> pick path -> tegra tab 10 usb drivers)
But i keep geting "Windows can't install device 'Unknown device' "
I tried also this http://www.craftedge.com/tutorials/driver_install_windows8/driver_install_win8.html
But it didnt help, still have the same information.
Anyone know what to do? How to install them? Or how to flash my tablet...
Thanks for any help
And sorry for my english Hope u understood me

As I have noticed there are two kinds of USB drivers for this tablet.
Strange enough I need one kind for installation under WinXP and other kind for installation under 64bit Win7 (they were not interchangable!).
In driver's folders "amd64" and "i386" they both have the same content, but they totally differ in driver's root folder.
One has only "NvidiaUsb.inf" and the other has: androidwinusb86.cat, androidwinusba64.cat, android_winusb.inf and source.properties.
I know I got one from MoDaCo: http://www.modaco.com/topic/331467-...-rom-for-the-advent-vega-with-online-kitchen/
Or if you don't want to download that 97MB file you have here only the needed zip file: http://www.wuala.com/Cosmichyrax/Programas/ANDROID/r1-tegrausbdrivers-modaco.zip/
And the other from this site (it's the site for my POV tablet):
http://downloads.pointofview-online.com/Drivers/10 inch Tablet PC Firmware TAB-TEGRA-10-1 upgrade/
And the needed file is called "Tegra Tab 10 USB Driver.zip".
Both links found thru Google!

yani2000 said:
As I have noticed there are two kinds of USB drivers for this tablet.
Strange enough I need one kind for installation under WinXP and other kind for installation under 64bit Win7 (they were not interchangable!).
In driver's folders "amd64" and "i386" they both have the same content, but they totally differ in driver's root folder.
One has only "NvidiaUsb.inf" and the other has: androidwinusb86.cat, androidwinusba64.cat, android_winusb.inf and source.properties.
I know I got one from MoDaCo: http://www.modaco.com/topic/331467-...-rom-for-the-advent-vega-with-online-kitchen/
Or if you don't want to download that 97MB file you have here only the needed zip file: http://www.wuala.com/Cosmichyrax/Programas/ANDROID/r1-tegrausbdrivers-modaco.zip/
And the other from this site (it's the site for my POV tablet):
http://downloads.pointofview-online.com/Drivers/10 inch Tablet PC Firmware TAB-TEGRA-10-1 upgrade/
And the needed file is called "Tegra Tab 10 USB Driver.zip".
Both links found thru Google!
Click to expand...
Click to collapse
I have them both Its not the problem with drivers, but with installing them actually...

Slisky said:
I have them both Its not the problem with drivers, but with installing them actually...
Click to expand...
Click to collapse
Have you tried AUDI?