Can't Connect To Android Phone

WinXP SP3
Moto G Power (2022)
Windows Media Player 11
MTPPK 12
Motorola_Mobile_Drivers_v6.4.0_32bit.msi
Moto_Diag_Drivers

I’m starting to wonder if the software out there to enable connecting my Motorola G Power Android phone is simply not compatible with XP. So far, I have yet to see the phones storage drives show up in File Manager.

There are many sites offering the same USB Drivers for this phone. Most of the sites say the drivers are compatible with Windows XP SP3 or higher, while far less sites that offer the exact same file D/L say the divers require Vista or above.

When ever I tried installing a given *.msi file I saw no difference in Device Manager of a new object being added. When I plug the phone into a USB port, the “Found New Hardware” wizard pops up, but installation always failed. I’ve tried letting it search, and pointing to various drivers that I’ve downloaded, but that didn’t help.

People commenting on this claimed that Windows Media Player 11 needs to be installed, which was already present. Other comments said that the MS “Mobile Transfer Protocol Pack” needs to be installed, which I re-installed. I had forgotten about the fact that I had previously installed this for an older Android phone, which was also a PITA to get connected. When I ran the MTPPK file I chose the “Repair” option.

Rebooting after this, and then removing and re-installing the Motorola supplied drivers, and then rebooting again, I finally saw a new device added to Device Manager after I plugged the phone into a USB port. A new category (Portable Devices) was there, with “Moto G Power (2022)” under it, which had the yellow exclamation mark. The “Found New Hardware” experience also happened and led to nowhere.

So then, using the Hardware ID, I looked again for the correct driver to Update that device and get rid of the yellow exclamation mark…. No joy. The ones I found I suspect are all for a 64bit machine.

Hardware ID = USB\VID_22B8&PID_2E82\2D2227X69D

Resolves to:

Vendor (22b8) = Motorola PCS

Description (2e82) = XT1541 [Moto G 3rd Gen]

No matter what I tried to update that driver, I got a message saying I’m trying to update something that doesn’t exist. When I disconnect the phone from the PC, the "Portable Devices" in Device Manager disappears.

The only thing I have not tied yet is installing “MotorolaDeviceManager_2.5.4.exe” which I had also D/L. I really don’t want to install a suite of software when I should be able to connect via USB just like most devices.

BTW, when I reboot the same machine into Linux Mint 19.3 (which is also no longer supported), and plug the phone in, everything connects and I can transfer files easy. So the problem is not hardware related.

I’ve spent enough time trying to figure this out myself, so it’s time to punt. If you kids can see something I did wrong, please lemme know.

Thanks,
Wolf
 

Attachments

  • MotoDvrFail.jpg
    MotoDvrFail.jpg
    84.7 KB · Views: 150
If you try to update driver and let you choose a driver to install. Select let me pick from a list of devices. Check if you can use the mass storage device driver. Maybe that one can work.
 
I have a couple old computers with Windows XP. I have a Samsung S21 phone. I found old USB drivers on Softpedia for Samsung USB drivers for Windows XP. After I installed the driver there was still a problem in the Device Manager but a Samsung Mobile USB Composite device appeared.

Note: to work your phone screen must be unlocked. Also, you also have to check the phone because you might have to grant permission for access from your computer.

USB1.jpg


I could double-click on the device in the File Manager and browse the files on my phone.

USB2.jpg


The problem with Windows XP is that newer drivers will probably not work. I found a Motorola USB driver at Softmedia for Windows XP:

Motorola USB Driver 5.4.0

USB3.jpg
 
Tried a bunch of different drivers and methods again, including the one you linked to above. Also installed the "Motorola Device Manager" suite.... nothing works.
 
Tried a bunch of different drivers and methods again, including the one you linked to above. Also installed the "Motorola Device Manager" suite.... nothing works.
Did you see anything in the Device Manager? After I toggled the transfer/charging mode on the phone an Other device showed up on the Windows Device Manager. The phone didn't show up in the File Manager until I installed the USB driver in Windows XP. I could then copy files.

When you first connect the phone to the PC did you see any notifications on the phone?
The first one should be about the USB mode. It might have to be changed to file transfer instead of charging
There is a notification on the phone to allow the connection. Did you see that and select Allow?
The last thing is that your screen has to be unlocked to see any files on the PC.
 
When I connect the phone via USB cable, the phone always makes a tone and then the dialog opens asking if I want to use the connection for file xfer, or share pictures. (same thing?).

My phone screen is never locked. File Manager has NEVER YET displayed a new device being connected. On the other hand, once connected the "Found New Hardware" (Moto G Power) routine always pops up on XP, and then fails to install any software to support what it found. (MTP Device).

With some drivers installed, I have seen "Portable Device" show up in Device Manager, and with others I've seen a new "Network Adapter" added to the list. I've never seen any other additions there. The new additions always have the yellow exclamation mark, with no way of finding an upgrade driver to get rid of it.

I've tried pointing directly to the MSI driver file used to do the install, and to directories filled up with every Motorola Driver I could D/L, but the "OK" button remains greyed out.... so it doesn't like anything I'm handing it.
 
SOLVED:

After some more looking around, I stumbled across a web page this morning that ended up leading me to a fix.


In my case, the solution was not the same as described in the article. I already had Media Player 11 installed, and the 7 files listed (for renaming) were present on my system, but I couldn't find any sort of "Wudf*Inst.log" file. Also, instead of running my copy of the "wmp11-windowsxp-x86-enu" (Media Player Setup) file, I simply extracted the contents to a Temp directory. Then I renamed the 7 files as described, and then ran the "umdf.exe" file in the Temp directory.

After confirming I could now attach my Android phone to the system and have it detected and connected for file Xfer, I got curious about what changes were made to the system. As it turned out, the replacement files for those 7 that had been renamed were about 10 years older, and all of them were a different file size as well. Those 7 files which had been previously installed were dated 3-9-2016, while the working replacements were stamped 9-28-2006. I also found copies of the non-working files in a "Service Pack" directory under "\Windows".

At the end of the article the author claims that no other drivers or software are really necessary. I already had Motorola drivers installed, along with the MS-mtppk12.exe, and NetframeWork 4, and I see no reason to remove them just yet.
 
Dude, I'm shocked you got it working, congratulations! I gave up on MTP a decade ago after having similar frustration as you, so I learned to always use ADB or FTP into androids.
 
Dude, I'm shocked you got it working, congratulations! I gave up on MTP a decade ago after having similar frustration as you, so I learned to always use ADB or FTP into androids.
Don't know what ADB is, and I consider FTP kinda iffy these days unless you get into the router settings to designate and/or deny access to certain ports (if you want to be a server), so for over a year now I've just been booting into Linux when ever I needed to access the Android file system. Small PITA, but worked.

Thing is, I had the Android connect working a few years back with an older phone. The antenna went south on that device so I had to buy a new one and have been struggling with the connection ever since. Kinda weird that it took replacing files with much older versions to get the newer device to connect!
 
Android Debug Bridge, it's another universal standard that lets you transfer files to/from phones via USB. Wireless ADB is a thing but not supported on all devices. ADB is also what you enable before you send rooting (or package uninstall) commands from a computer to a phone, but Google has locked down ADB much more today than in earlier versions. Yeah FTP can be a pain but you only have to forward ports if you want to access it from outside your LAN. Since both my computer and phone connect to the same wifi router, it works fine. I use FTP server on the phone because it's quicker and easier to navigate file systems on a computer.
 
Back
Top