Database Users

VISTA BUILD 5600 WITH WMDC

hello!
i just installed a fresh new copy of Windows Vista x86 Build 5600 and I've realized that Windows Mobile Device Center isn't installed.
I've searched and at Microsoft I've downloaded a file: drvupdate-x86.msi which appears on Control Panel as Windows Mobile Device Center Driver Update!
Well, It's not the program, is it??? I instalde Driver Update but I don't seem to install the Program at all!
I've searched on XDA and I've found some tips, which I've tried with no result!
Add Key to registry at HKLM\Software\Microsoft named WHOS. it's supposed when I plug USB cable to PC and Universal, appear on Windows upgrade saying there is a new upgrade available. Doesnt appear!
I've seen a topic saying:
"...Yes I have it working with both USB / BT :=)
Try this procedure.
1. Download this file.
http://www.download.windowsupdate.co...bc9 4587a.exe
2. Extract it using winrar.This will give you a file "wmupdate.msi"
3. Now be sure to logon to Vista as the built in admin and run "wmupdate.msi" and after that reboot and again login as built in admin, let it complete the install.
4.Login as your regular user, connect you phone and all should work:=)"
Downloaded the file and done all right but I dont seam to make it work!
I've ONCE installed WMDC with no errors but the device appeared "NOT CONNECTED".
Now, after a NEW fresh instalation, I cant even install WMDc!
Please help!
I would like to keep vista installed, but without sync there's no way!!!!
Deiota

Google Maps, Facebook and ADB

Hello All.
I've had my UK, T-Mobile G1 for quite a while now. I have rooted it and it is running the latest CyanogenMod recovery image and ROM. I also have Apps2SD set up on my 8GB SD card, on a 512MB ext partition. This was all working fine until the problems below occurred...
I'm having some problems with several apps and ADB.
My PC runs Windows 7, 64 bit, and I can't seem to find a driver for the G1's ADB. I'm probably being incredibly stupid, but I just can't find one. I have used one before on Vista, where I had to set some boot options, but I'm not too sure / happy about doing that on my nicely functioning Windows 7. And as my friend once said; "You mess around with windows, then windows will mess around with you"...
But, anyway, I can't seem to get ADB working, if someone could either send me a link to the drivers or guide me through it, I'd be grateful...
Also, it may be due to me running CyanogenMod, but if I try to update the Facebook app, it downloads the app, and then when it tries to install, gives me the error "Installation Unsuccessful - Incompatible Update".
And with the Google Maps app, it says "Installation unsuccessful - Package file was not signed correctly". This may be due to me trying to get the hacked version of the app to get the Google Maps Navigation working in the UK, but I couldn't get that to work, so I uninstalled it and Nav Launcher, and now when I try to update from the Market it gives me that error.
I've seen a guide online with ADB commands, but as I have no access to ADB, I'm a tad screwed. I've tried runnign the commands in the Terminal Emulator in the phone, which does approximately nothing whatsoever.
So, can anyone give me any guidance on any of my Android problems?
Thanks in advance - Ethan

To the best of my knowledge no one has successfully used ADB with Windows 7/64bit

jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Ah. Looks like I'll be reinstalling Ubuntu then for the ADB. Thank you for such a fast response.
- Ethan

jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Lies, I'm running windows 7 64bit and ADB works fine.

chris4500uk said:
Lies, I'm running windows 7 64bit and ADB works fine.
Click to expand...
Click to collapse
In that case, do you remember where you obtained the driver from? I would love a link, or a zip file or something...

I'm on Vista x64 SP2 and I can use ADB just fine. You just need to download the SDK and then get the USB driver through there. It used to come included, but now you need to use the ADV and SDK manager and download the drivers as an SDK Component through there.
After that, make sure your phone is set to USB Debugging mode and plug it in then point windows to the new drivers. If it doesn't want to install the new drivers, you might need to remove the old ones first. I had to use USB Deview (DL link at bottom of page) and removed all installed HTC drivers. After that I plugged my G1 back in, pointed it at the newly downloaded drivers and all was well.

I'm running adb/fastboot/android sdk on win7 64b ultimate. The drivers are included in the sdk download. Once you download the sdk, make sure you have java installed. (I had to install JRE and JDK to get it to work properly, not sure if this was needed) Anyhow, when you have the sdk downloaded, run the sdk setup program. Go to settings and check the box for force update (unsure of the exact terminology used there) then go to available updates and your drivers are the last option on the list.

[Request][Bounty] NextWindow Touchscreen Driver Install for Windows 8

***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)

Try locate the driver inside the System32 file on a Windows 7 computer then copy it to the Windows 8 computer, hit Update Driver and point it at the driver you just copied. Basically this is manually installing the driver without the .exe installer HP provided you (and gives the OS error). Almost all Windows 7 drivers work on Windows 8, just the package you use does not.
Right click My Computer > Properties > Hardware > Device Manager > Your Device > Right click it > Properties > Driver > Driver Details.
Click to expand...
Click to collapse

Try locate the driver inside the System32 file on a Windows 7 computer then copy it to the Windows 8 computer, hit Update Driver and point it at the driver you just copied. Basically this is manually installing the driver without the .exe installer HP provided you (and gives the OS error). Almost all Windows 7 drivers work on Windows 8, just the package you use does not.
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately that was a no go. Unless im not reading the driver names correctly I have copied them from on drive to the other and attempted to update it that way. Same results.
These were the drivers I copied and moved from System32
drivers\mshidkmdf.sys
drivers\NWTransLibV.sys
drivers\NWVoltron.sys
WdfCoInstaller01009.dll
Thanks for the input though.

ca2l3vin said:
Thanks for the advice. Unfortunately that was a no go. Unless im not reading the driver names correctly I have copied them from on drive to the other and attempted to update it that way. Same results.
These were the drivers I copied and moved from System32
drivers\mshidkmdf.sys
drivers\NWTransLibV.sys
drivers\NWVoltron.sys
WdfCoInstaller01009.dll
Thanks for the input though.
Click to expand...
Click to collapse
Maybe you could give a try at double driver (boozet.org)

Thanks for the reply. unfortunately it fails the install this way aswell.

you can try and modd the inf file i ont have the hw what you guys only i able to compare is the win 8 cp x64 and win 7 x64 amd radeon driver there are a lot difference

ca2l3vin said:
***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)
Click to expand...
Click to collapse
Hi I did not figure this out but i'm having the same problem, I found this solution on the microsoft website questions and answers. Pleasr let us know if this works for you. Thanks. I had tried that but the install would not start because it didn't see the OS as valid.
BUT I did get it to work by doing a restore to factory settings (Windows 7) and rerunning the Windows 8 install directly from http://windows.microsoft.com/en-US/windows-8/download and selecting to KEEP the installed apps and user files. On my failed Win8 install attempt I used a Windows 8 ISO file and selected to NOT keep any apps or user files.
Not sure which if the 2 changes made the difference but the touch screen works now in Win 8.

Ok, I tried this out and it does work. I have a hp 520-1031 and now my touch screen works with windows 8

So only way around from what I see is to install windows 7 first then run windows 8 as an update. Though this isn't the solution I was hoping for (as now I have to install windows 7 on a partition first then rerun the install for windows 8) I do thank you for your efforts and the bounty is yours Tragicwayz
you can PM me your information and by the end of next week your payment of $27 will be in your box (this is calculated from the time of your first post of the solution from the time I started the thread)
Thanks again

You are welcome, I have tried many solutions as well but could not get the touch screen working. I hope this helps others with their touchscreen.

I have a TS 7320 and the touchscreen driver for Windows 8 didn't work either. Next I installed Win7 x64 to get it running before upgrading to Win8.
Unfortunately, my device won't install the drivers from de HP website, nor from NextWindow. I looked at the INF file and there is a difference in the device id. My PC shows a 'REV_0008&MI_02' addition to the VENID and DEVID. Altering the INF file manually makes the install work, but the driver fails with error 10 (won't start)…
Any suggestions where to get a working driver for Windows 7 x64?
(I wiped the disk to install Win8, so no recovery disk/partition from HP )

moved to general

ca2l3vin said:
***IF THIS THREAD IS IN THE WRONG SECTION I WOULD APPRECIATE IT IF IT WERE MOVED TO THE CORRECT SECTION. I BELIEVE THIS IS CORRECT BUT I AM NOT SURE. IF ITS NOT MOVED THEN INFORM ME AND ILL POST IN CORRECT SECTION.***
Ok so here is my situation. I have a HP Touchsmart 520-1030 and I am wanting to use windows 8 with the touchscreen. That being said it appears that on both the Developer and Consumer release that the driver for it does not work well with Windows 8 even though it works fine on Windows 7 (I have it dual booted on seperate partitions).
So here is a description of what I have attempted so far.
Downloaded the Driver package from HP's Website and ran. Wouldnt install as gave OS version error.
So I ran in compatibility mode Windows 7 with admin permissions (also taken ownership). I get the same error about the OS version.
I then went to NextWindow's website and downloaded the original (older) drivers from there. It says its installed but does not work (device manager showing touchscreen with a ! on it.)
I then tried to update the driver in DM and search gives an error.
I then browsed to the installation folder of the drivers and it states cant find driver.
I then went back and compared it with windows 7 drivers and see the "touchscreen" driver is NextWindow Voltron Touchscreen. I then compared the Hardware IDs and sure enough they are the same ID's (I believe).
I then used a universal extractor and extracked the package for HP and NextWindow and attempted to manually update the driver through DM. It updates but I get an error with the HP packages (code:10 Device will not start) It shows correctly now but has ! next to the name
I rolled it back and updated with the NextWindow Drivers the same way. It installed successfully but when attempting to use the touchscreen no response. (also name is different NextWindow Multi-Touch Device)
so I rolled back and attemped to update manually without the extracted packages (using Windows Default ID's it has) I see one that states NextWindow and it seems to have the same information as the packages. I get the same errors.
So natrually now I see it seems to be the NextWindow Drivers are what is causing the problem. In doing research (reports on multiple forums) it appears that many all-in-one or overlaid monitor is having the same issue with the NextWindow Drivers. Now that being said I have seen what appears to be HP Touchsmart 610's running Windows 8 on youtube (developers build as the are older vids) and doubt that MS would have removed the drivers if they were working.
So the Bounty for me will start at $40 Dollars starting at the time of this post. Every 24 hours that this post remains unsolved I will dock $1 dollars from the total bounty (basically im looking for a quick solution not one after drivers have been redone by the NextWindow already.) If you can solve this its a quick $40 for just basically searching around and seeing something I couldnt figure out. This also may help ALOT of people that have All-in-ones as these drivers are made for multiple PC's with touchscreen devices (8 manufactuers total such as Sony, Lenovo, HP, ect.)
Good Luck (and I prefer to pay via Paypal to make things easy.)
Click to expand...
Click to collapse
Why offer a bounty if you are not going to pay it.

So the solution is to upgrade from Win 7?
sounds more like a work around to me.
If it were me id mod the drivers, within the INF file for the drivers you downloaded it will state which OS versions are excepted. all you have to do is make Win 8s version an excepted version, then point the INF to the win 7 driver its self, usually the driver folder may contain drivers for several versions of windows if it doesn't the its just a case of adding win 8s version number to it.

Modifing the inf file and re-sign it.
Maybe you should follow the steps that I did to install Windows 7 display driver, but do it for the multi-touch driver. Since I can't provide a link, do a web seach for "running-angry-birds-on-the-build-samsung-tablet-with-windows-8-consumer-preview"
Alon.

Solution mate.. seems stupid but works!! Last posts on this..
http://h30434.www3.hp.com/t5/TouchSmart-PC/Windows-8/td-p/1314493/page/3

Trying to get the multitouch working. Downloaded these drivers from nextwindow http://www.nextwindow.com/nextwindow_support/windriver.html
The driver had no effect on the multitouch, so it's still single touch...
Does someone have a clue how to get multitouch working?

Solution !
Here's what you need to do to get Multitouch working on a HP Touchsmart 520 under Windows 8:
1.) download Intel Graphics Beta driver from downloadcenter.intel.com
2.) install the latest Voltron driver from HP driver base.
This isn't very stable unfortunately (screen freezes from time2time).
But it's the requested solution (4 the time being).
Cheers

No solution !
michaelreuss said:
Here's what you need to do to get Multitouch working on a HP Touchsmart 520 under Windows 8:
1.) download Intel Graphics Beta driver from downloadcenter.intel.com
2.) install the latest Voltron driver from HP driver base.
This isn't very stable unfortunately (screen freezes from time2time).
But it's the requested solution (4 the time being).
Cheers
Click to expand...
Click to collapse
Crap ! I have to correct myself. Due to the bugginess I reinstalled Win8. Now the Touchscreen driver won't install any more, no matter what display driver I use.
WTF ?

[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.

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.

Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.

WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip

Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.

Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?

For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.

The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?

Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.

Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards

Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards