Windows XP, with sdk developers kit, and the motorola USB drivers.
It works via fastboot and i can flash. Once i reboot my xoom and it comes to the lock screen, adb remount informes me device not found.
I do a adb get-state and it's unknown.
My XP machine sees the xoom as it boots up, then pops the driver install wizzard, but can't locate a driver. I have pointed it to "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" as well as the c:\Program Files\Motorola folder with no success.
Keep in Mind before that on this computer, with the xoom booted i had this issue of it not finding a driver....but when i used the dev kit and was able to flash, i didn't realize once the xoom booted i wouldn't be able to use adb any longer.
Was updating bigdogrush's kernel. I did my origional flash from my home windows 7 comptuer.
any advice would be appreciated.
Found in the moto community forums a similair thread and it stated you had to install Windows Media 11 for the MTP update. Sure enough that worked.
Related
Is anyone having problems with adb and vista?
When I start the adb shell I can type about 2 or 3 commands and then it stops responding. When I type the 3rd command or so instead of it going back to # at the command prompt it just goes to the next line with out a prompt.
Also when this happens I go to task manager and try to shut down the adb.exe but it won't I have to reboot my computer.
I have a laptop and a usb keyboard when I start have the problems with adb my key board wont work ether. So I have tried it with out the usb key board but have the same problem.
I have also tried running adb and xp compatible but still have the same problem. Is there anything else I can use other than adb?
I am having problems as well. I flashed my custom boot image yesterday and now today it is saying that it cannot find my device. It has worked since December and then today, nothing. In Need of Help.
What version of vista are you using??,,, additionally this should be moved to the "Dream" Section
I have Ultimate x64, have no issues. I assume you have the proper drivers as you can do a couple commands, yes??
Vista 32 Ultimate here and I've never had an issue. Go to the Device Manager and see what it shows when ADB stops working. Sounds like your USB controllers are taking a ****.
I'm using vista 32 bit. I think I'm haveing a usb conflict.
Sorry for posting in the wrong forum
I have Ultimate x64 and no problems.
I had a problem with the driver that was configured to G1. Maybe..
I have Vista Home Premium x64. On Vista SP1 I had no problems. After upgrading to SP2 the adb will connect once and in Eclipse I can get a few commands through, then it hangs. After that I cannot kill the adb process, nor get any response from an adb command.
When I roll back to SP1 it works again. Though under SP1 it is still not completely stable, however it is always possible to kill the adb process and connect the device again.
Hi there... totally new to the Andriod world and am stuck on trying to upgrade the firmware. I am running Windows 7 64 bit and the devices says that it is installed correctly yet when I run "adb devices" it gives me and error stating "command not recognized....? any idea's?
Rogers device....
do you have your sdk setup correctly? do you have the sdk tools folder in your path?
you can find out by typing path
you should see
C:\android\tools as one of the entries....
windows is telling you that the adb command is not found.
i have the same issue. running windows 7 64bit and adb doesnt find the device. the phone doesnt show up in the device manager either, but it told me that it installed correctly when i first plugged it in.
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Phoenix4848 said:
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Click to expand...
Click to collapse
AARRGGHH! Windows and its damn' driver problems! First did you disable driver verification? If not Google it. Then install MoDaCo's drivers using the Windows GUI tools (IIRC you get there from Device Manager). If all that doesn't "take", my best advice is to wipe all trace of Windows off your computer and install a sane operating system. Too radical a fix? OK, your funeral, but here's a halfway fix: download this Puppy Linux live-CD .iso that I've doctored with Fastboot and ADB binaries, and burn it to a CD.
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Make sure you know how to burn a CD from a .iso file. The end result will have files and folders, not just a single .iso file on it. It's a bootable CD, so you guessed it, boot your PC to the CD. Don't try to run it in a VM, it won't work. Click on the terminal icon on the desktop and you have a box that looks and acts like the Windows DOS box; the OS commands are somewhat different but the fastboot and adb ones are exactly the same. In fact the terminal is the same as the one in Android, and since both devices are Linux now, driver problems disappear!
Do whatever dastardly deeds you want to the MOJO with Fastboot or ADB, eject the Linux disc, reboot--and as far as your PC is concerned, it never happened. The live-CD won't leave a trace unless you specifically tell it to.
Most of the tutorials on this MOJO forum give commands like "fastboot-linux flash twrp(version), this is MoDaCo's version of Fastboot. I put this live-CD together using Google's binaries so that command would look like "fastboot flash twrp(version). Keep in mind that with the MOJO the device ID string is mandatory; see the TWRP recovery thread for details, but you can't just send "fastboot devices", it won't work, you must send fastboot -i 0x0738 devices, or go straight to flashing or booting.
Well I don't know if I just cleared the waters some or just stirred it up more, but good luck and I hope I helped a little anyway!
This was how I was able to install my drivers on my Win 7.
Assuming that you've downloaded the superboot-mmm file and you've extracted to your C: drive:
1. Go to Devices and Printers under Control Panel
2. Right Click on the Fastboot device, and click on Properties
3. Click on the Driver tab, and click on Update Driver (or click on Properties)
4. Click on Browse My Computer For Driver Software (manually)
5. Browse the following location (or copy and paste this: C:\r3-mojo-superboot-mmm\windows.driver)
6. Select Next
7. The driver will be installed
If you now replug the MOJO, you should be able to see Madcatz ADB Interface under Hardware Tab when you click Properties
Source: my blog
Hope it helps.
Yes! Thank you
Yes, the problem was I was going a folder too deep in selecting the driver from the device manager. Thank you.
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