Database Users

ADB Interface Error

Hi,
Trying to get my Nexus 7 connected to my laptop running Windows XP (32bit), SP3, to allow me to root it.
I've downloaded the Nexus Root Toolkit and I've tried installing all the different drivers from there (USB Debugging is OK), and even the Samsung drivers.
Every time, I get a error on the android ADB interface (can't install). I can't post a picture yet (need 10 posts on here), but I get the following in device manager:
Android Device
Nexus (!)
Other Devices
MTP (!)
Any ideas where I'm going wrong? I think I've read somewhere that XP is difficult to get communicating.
Cheers.

Oh, and it tries to install wdtCoinstaller01007 as standard for a driver.
Have also tried *01009

I have the same problem.
I guess the MTP while in debugging mode is not important

[Q] How to transfer files to Nexus 7?

Good day, normally when I plug-in my other Android Devices on PC, I'll see them on "My Computer" and can see the files like a normal drive, but with the Nexus 7 I get nothing, I also tried to install the Nexus 7 Toolkit for the drivers, but still can't access the files. I'm on 4.2.1 right now, anybody can help? Thanks in advance!

I installed the drivers from the 'Wugfresh nexus root toolkit', installed the android sdk, installed the pda.net app on the N7 and the win version of pda.net on the pc and then the connection worked. Some have had to go into 'device manager' on the pc and uninstall any reference to the nexus or unknown devices and connect again. Also, usb debugging should be on and you should set the n7 to mtp mode. It is almost always a driver issue.

If you want you can use even airdroid via Wi-Fi connection.
Inviato dal mio Nexus 7 con Tapatalk 2

The Nexus uses the MTP mode to connect to your computer. This mode works best on a recent Windows operating systems with Windows Media Player 13 or better. The Nexus will appear as a Device - usually Nexus7.
Just search this forum for MTP for help with Windows XP, Linux and Apple systems.

Will this work on Windows 7? I tried to check updates on Windows Media Player 12 and it says I already have the latest version, no device on My Computer for my Nexus 7..

Brickoy said:
Will this work on Windows 7? I tried to check updates on Windows Media Player 12 and it says I already have the latest version, no device on My Computer for my Nexus 7..
Click to expand...
Click to collapse
It should just work on a Windows 7 computer - it did on mine. Try turning the Nexus fully off, connecting it to the computer and then turning on the Nexus. I noticed mine updated some drivers when I did this.
Also try another USB cable as those do fail.

If you're looking to transfer stuff like music, video and ect. You can do that over wifi by using an app on the Google play store called airdroid. I use the very same app to transfer files.
Sent from my Nexus 7

I'm on Windows 7 Home 64 Bit, I tried turning it on while plugged on my laptop but still no luck. All my other android devices works fine, it's just the Nexus 7 that is problematic.. I also tried AirDroid, not so good with large files especially movies when I travel

Are you connected to the internet with your windows7 pc?
Maybe it can't download the necessary files/drivers?
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
Maybe this helps:
http://forum.xda-developers.com/showthread.php?t=1934306

Brickoy said:
I'm on Windows 7 Home 64 Bit, I tried turning it on while plugged on my laptop but still no luck. All my other android devices works fine, it's just the Nexus 7 that is problematic.. I also tried AirDroid, not so good with large files especially movies when I travel
Click to expand...
Click to collapse
Is "USB Debugging" off in settings - developer options? Maybe also leave developer options off for now.

I got USB Debugging off, I'm on 4.2.1. Still no luck.. I just use AirDroid now even though its very slow for me..

Well I just connected my Nexus 7 to my PC and straight away my PC asked me if I wanted to view Nexus 7 files.
My PC is running Windows 7 64 bit.
I am able to look what is in the Nexus and I am also able to add or delete files as I want - great. :good:

I solved my problem with transferring large files, I didn't realize it's very simple, instead of MTP I just chose PTP and Windows detected it as a portable device, tranferred files from my PC to the Nexus 7's DCIM folder. Unplug the USB then just move them anywhere on the device's storage using a file manager.. It's that simple..

Brickoy said:
Good day, normally when I plug-in my other Android Devices on PC, I'll see them on "My Computer" and can see the files like a normal drive, but with the Nexus 7 I get nothing, I also tried to install the Nexus 7 Toolkit for the drivers, but still can't access the files. I'm on 4.2.1 right now, anybody can help? Thanks in advance!
Click to expand...
Click to collapse
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!

Brickoy said:
I solved my problem with transferring large files, I didn't realize it's very simple, instead of MTP I just chose PTP and Windows detected it as a portable device, tranferred files from my PC to the Nexus 7's DCIM folder. Unplug the USB then just move them anywhere on the device's storage using a file manager.. It's that simple..
Click to expand...
Click to collapse
I found the same results after rooting my Nexus. Uninstalling WUGs toolkit and restarting restored the MTP mode and ADB also continues to work. This won't erase any backups you've made. If not WUGs maybe something else you've added is blocking the MTP mode.

Sorry I still can't figure it out. I am on stock rom, with root access. I have debug usb enabled. I can connect it as PTP or MTP....with PTP, the nexus 7 is displayed as 'nexus 7' and I can access the DCIM and picture cache folder (pretty useless....). With MTP, the device won't even be detected by windows. It will not search for drivers.
My target is to be able to write bigger files...I am speaking about 1 gigabyte or more. Through WiFi it would be a pain...if it is a picture or even a collection of a few hundreds megabytes....ok, I could do it, but sometimes I need to move GBs of things, and with wifi is obviously too slow....so how do I get to move this stuff via usb? I thought even copying from PC to usb stick, and then copying from stick to nexus (with usb host....stickmount or usb host or another app) would be even faster than doing everything via wifi, but it is just lame.
HELP!
edit: sorry I feel like I have an ipad (grrrr)...never had problems with other android devices

device manager
drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
drumtrucker, I think you're on to something here, but you meant "Device Manager" which may be found either in your start menu or by pressing windowsKey+r and typing "control" then hitting enter.
--dchriste

[Q] No MTP connection

When I connect my Nexus 10 to my Windows 7 computer, the only driver installed is the Android ADB Interface.
I don't get the MTP connection, and my tablet does not show under "My Computer".
On the Nexus 10, I have tried turning debugging on and off, and I tried deleting the driver from the device manager in Windows and reconnecting it and hoping it would re-detect and re-install, but still no go.
Can anyone help me to get the MTP connection working? I think it worked on the initial Android version 4.2, but after the Nexus 10 system updates, it stopped working.
Thank you

brandonyoung said:
When I connect my Nexus 10 to my Windows 7 computer, the only driver installed is the Android ADB Interface.
I don't get the MTP connection, and my tablet does not show under "My Computer".
On the Nexus 10, I have tried turning debugging on and off, and I tried deleting the driver from the device manager in Windows and reconnecting it and hoping it would re-detect and re-install, but still no go.
Can anyone help me to get the MTP connection working? I think it worked on the initial Android version 4.2, but after the Nexus 10 system updates, it stopped working.
Thank you
Click to expand...
Click to collapse
You shouldn't have problems if you are on 4.2.2 (as I see on your sign). Did you try unplugging and replugging the Nexus 10 or trying another usb port? As soon as you connect the n10 to the pc, drivers will automatically install and it will show up under my pc. Also, if you go to settings - storage, I think you'll see the option of mtp (once you connect it and the pc recognizes the tablet).
PD: Maybe you have issues with the drivers from your nexus phone? You shouldn't since they should be generic, but who knows...

http://www.microsoft.com/en-us/download/details.aspx?id=19153

lKBZl said:
You shouldn't have problems if you are on 4.2.2 (as I see on your sign). Did you try unplugging and replugging the Nexus 10 or trying another usb port? As soon as you connect the n10 to the pc, drivers will automatically install and it will show up under my pc. Also, if you go to settings - storage, I think you'll see the option of mtp (once you connect it and the pc recognizes the tablet).
PD: Maybe you have issues with the drivers from your nexus phone? You shouldn't since they should be generic, but who knows...
Click to expand...
Click to collapse
My phone connects fine. In the end, it looks like something broke in Windows. I did a clean install and it recognized my tablet again. But, I still don't know what broke it.

Back when I was on Windows, I did notice sometimes I'd have to uninstall the ADB driver completely for MTP to show properly. No idea why though.
Works great on Ubuntu though, right out of the box too on raring

[Q] Nexus 7 USB connectivity to Windows XP SP3

Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???

try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app

o82239 said:
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE

ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Sent from my Nexus 7 using xda app-developers app

:-/
Is there any justice for me in this bad bad world of octa-core processors and Razer Edge!!! :'(

ansh360 said:
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
Click to expand...
Click to collapse
??? It worked and it doesn't work ???
What worked?
Try to delete the precompiled inf-file 'C:\WINDOWS\inf\wpdmtp.pnf', edit the 'C:\WINDOWS\inf\wpdmtp.inf' (see link in the post in the top...), open the XP device-manager, right-click in the yellow '!' and 'update driver'...
twics said:
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Click to expand...
Click to collapse
Do you have edit the 'C:\WINDOWS\inf\wpdmtp.inf'?
Sent from my Nexus 7 using xda app-developers app

I had a lot of problems myself getting Windows XP to work with my Nexus 7 as well... eventually I discovered that installing the latest version of Windows Media Player fixed the problem.
I wrote up a post on this issue on another forum (Sorry, XDA - this was before I discovered you guys), back in December of last year.
Anyway, here is my original post...
http://www.nexus7nexus10.com/forum/nexus-7-help/2600-cannot-connect-pc-2.html#post36608
(Actually, this whole thread is worth reading.)
The only nuisance factor is having to remember to re-enable USB debugging (Titanium Backup needs USB debugging enabled, and complains if itsn't) AFTER I've run some MTP Windows XP related file backups (USB debugging needs to be disabled, or MTP won't work)...
....or at least that is my experience.
Hope this is of some use.
Rgrds,
Ged.

Hello guys,
I have the same issue on windows XP with Nexus 7. I tried everything what was suggested and nothing is working.
I have Windows XP SP3 with WMP11 and MTP porting kit installed as well. the device is recognized and driver is instaled fine. But it's not visible on "my computer" in MTP mode. I tried to turn on usb debugging and still device is invisible in windows explorer, the same is when usb debugging is turoned off.
When device is in PTP mode it appears in "my computer" and i'm able to browse it and see all pictures and photos.
How can i browse my device in MTP mode and copy files there? Please reply if anybody knows what to do to fix this issue.
Thank you.

ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.

Taowtp said:
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Click to expand...
Click to collapse
The above workaround was spot on, thanks

[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