Tetherxp.inf Download

0 views
Skip to first unread message

Violette Ransone

unread,
Aug 3, 2024, 5:09:01 PM8/3/24
to pidkillcricir

(These instructions were written specifically for the MOTO G and the link to the included driver is for the MOTO G; however, the basic instructions should work for creating a driver for a different Android device)

Got a new MOTO G phone a few weeks ago. Started playing around with allowing my laptop to use the cell phone as a wireless connection. When I tried to turn on USB Tethering, my XP laptop needed a driver for an RDNIS device.

Plug your phone into your computer, enable tethering, and you should get the Found New Hardware window. Go to the device manager and in Other Devices you will see the RNDIS driver with a question mark before it.

the advice was vital. I used it to connect a Samsung s4 mini to windows xp with service pack 3. I edited the tetherxp.inf file by over typing the HTC sapphire entry and substituting the VID and PID codes as you have detailed. I could not find any other details but yours on how to do this. You might consider changing the title of your blog to all android phones, so it comes up on general searches. I believe your advice would work for all android phones using windows xp. There are a lot of people with this tethering problem on android forums getting no useful answer.

So I turned to Google and found multiple posts suggesting to download a tetherxp.inf file and simply use that to install the drivers which apparently are already available in a standard Windows XP installation.

In the old Android release R10.3.x for i.MX5x, I had followed the user guide instructions to install the USB driver and am able to setup the ADB connection successfully. Unfortunately, for the same PC, the ADB fails to detect my i.MX6SL EVK which is using R13.5. Updating the Android SDK tools cannot help.

The reason is the new Android device is using a different USB VID from the old release. So, to solve this problem, we need to update the ADB configuration to scan for the new vendor ID. Below are the steps to update the ADB configuration for Windows PC. These steps (and the steps for Linux PC as well) can also be found in the R10,3.x user guide.

3. Unpack the Freescale Android USB win driver "android_usb_fsl.zip" in your Android BSP release package. If you can't find this file in your current package, please get the R10.3.x release for i.MX5x and unpack it.

4. File "tetherxp.inf" in the unpacked "android_usb_fsl" may not be the updated one if the "android_usb_fsl.zip" is extracted from an old release. So, please overwrite the file "tetherxp.inf" in unpacked "android_usb_fsl.zip" by the new "tetherxp.inf" in your current Android BSP release.

6. Connect the Android Device into PC, uninstall your old driver named "Android Phone" in the device manager, then re-install driver by scanning and locating .inf file under the directory you unpack the android_usb_fsl.zip manually.

Sometimes, following the above procedure still cannot get the ADB work. In such case, you have to uninstall the Android Composite ADB Interface device, remove the "Android Phone" driver package (oemxx.inf) from Windows and start all over again. More information about using command prompt utility "pnputil.exe" to remove the driver package can be found at Remove a Driver Package from the Driver Store.

I tried to use the android_usb_fsl.zip from R10.3 as well as R10.4 but driver installation fails with errror "The folder you specified doesn't contain compatible software driver for your device. If the folder contains a driver, make sure it is designed to with Windows for x64-based systems".

I have tried using other universal usb driver, rebooting PC , connect/disconnect USB , followed steps listed in this thread as well as Android FAQ document for SABRE platform. The Developer options Stay Awake and USB debugging are enabled on the tablet.

I would recommend uninstalling - make sure the *.dll drivers are deleted (no in the WINDOWS directory) then update you're .ini and re-install. I've seen once when the 'incorrect' version is installed - the .dll's are not replaced when uninstalling or subsequent installing the correct drivers. So nothing ever changes.

We are using our own VID/PID and our own serial number for imx6 based android device, ADB is working with updated VID/PID value in myandroid and able to detect from linux O/S and fail to detect from windows 7 PC after updating VID/PID android_winusb.inf file and using freescale android_usb_fsl driver folder.

I just recovered from an issue similar to yours whereby I HAD adb devices report correctly then suddenly no longer - all the while "Android Phone" was correct and all mods had been completed to provide initial adb operation.

I discovered that the adb_usb.ini file had somehow been updated/changed/recovered back to the original, i.e. without the 0x15A2. I re-updated this file AGAIN - and my device is located and reported as normal. I'm not sure who/what/why this .ini file I had updated with 0x15A2 was changed back the original. But I never thought to double check until I was at wits end (wondering why it worked then stopped working). Perhaps this is also your case. I suggest you double-check all the mod you did to make sure they are all still in place! you may need to uninstall and re-install the driver on any (re)change.

Been trying for two days to connect adb via USB from my Mx51 BBG (updated to R10.4) to my WinXP. My older rev R9.3 connects fine. I have executed through every step (5 times) to no avail. In Device Manager I continue to get a ?-Other devices: ?-!-MX51 BBG Android ...wizard cannot find the necessary software.

I am sorry I don't have the MX51 and MX53 board now so I can't check this myself. Based on my experience with R10.3 on MX50, the ADB connection should be setup correctly by following the instructions in the user guide.

4. Double check the USB VID and PID of this R10.4 device if it is not 0x15A2 and 0x0C02 respectively, please add a new entry using this PID and VID to the android_winusb,inf in "android_usb_fsl" and retry.

Finally, please note that the option "Settings->Applications->Development -> Stay awake" should be checked or else the device will enter suspend mode due to lack of user activity and ADB will automatically disable.

If your are using windows xp. YOU will NEED to update to SP 3. If you have sp 3 then u download the tetherxp.inf file. there is no way to tether new phones such as LG G Stylo phone on a windows xp running sp (service pack) 2 the information above came from microsoft website. Feel free to search the website.

The reason your phones are not working is because the inf file only has information on Google Nexus, HTC Sapphire, Motorola Sholes. If you dont have these phones you will have to find the driver for your phone or edit the inf file to add your phone (dont do this if you have no idea what youre doing). You can open the inf file and view the list yourself in wordpad or another program and see for yourselves.

i did everything as instructed. the file install is in the notepad file.. i browse and want to select the file that i put in a folder, but the installation in unsuccessful saying that it is not the right configuration. what should i do now

I too tried connecting it folowing the above steps. But my xp new hardware setup doesnt ask for exact location of the saved config file and hence tries searching in the path provided.
And it fails to find this (tetherxp) file then.

Also i am actually trying to connect the laptop to internet through the phone wifi. As in my phone is connected to the wifi and the laptop is connected to the phone via usb cable. Can i access internet through the laptop? Is that possible?

c80f0f1006
Reply all
Reply to author
Forward
0 new messages