Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #34156
| Newsgroups | comp.mobile.android, uk.comp.homebuilt, microsoft.public.windowsxp.general |
|---|---|
| Subject | Re: How to reinstall Android driver on WinXP? |
| From | pamela <invalid@nospam.com> |
| References | <XnsA67E58905350FD4AM2@8.17.249.104> <nquab9$687$1@dont-email.me> <XnsA67F762BDB7A6D4AM2@216.151.153.167> <nr13ku$k18$1@dont-email.me> |
| Date | 2016-09-12 21:39 +0100 |
| Message-ID | <XnsA681DC54ABC6CD4AM2@216.151.153.44> (permalink) |
| Organization | Unlimited download news at news.astraweb.com |
Cross-posted to 3 groups.
On 15:00 10 Sep 2016, Paul wrote:
> pamela wrote:
>> On 13:35 9 Sep 2016, Paul wrote:
>>
>>> pamela wrote:
>>>> How can I re-install an Android driver on WinXP?
>>>>
>>>> In the past, I've attached my Kit Kat tablet (Hudl 2) to XP
>>>> without any problem. The tablet shows up as an extra drive
>>>> in XP and basic file transfer can be done.
>>>>
>>>> Recently, I attached the tablet and this time XP tried to
>>>> reinstall the driver. XP correctly detected an Android
>>>> device was attached and that an MTP driver was needed. but
>>>> the re-installation failed with the message: "Cannot Install
>>>> This Hardware ... A service installation section in this INF
>>>> is invalid". Now in Device Manager there's now a yellow
>>>> question mark over the Android driver and the driver details
>>>> say: "No driver files are required or have been loaded for
>>>> this device".
>>>>
>>>> I guess the driver is still on the XP system somewhere. How
>>>> can I re-assign it to the Android entry in Device Manager?
>>>>
>>>> Is there a way I can get the old driver assigned to Android
>>>> in XP's device manager without installing some mega pack of
>>>> Microsoft drivers such as something I found on the web called
>>>> "MTP Porting Kit Setup". Whatever that it. My XP is heavily
>>>> customised over 10 years and can be a bit fragile when
>>>> applying packs like this.
>>>>
>>>
>>> I don't have any MTP devices here to experiment with.
>>> So all I can point at, is "materials".
>>>
>>> The purpose of posts like this, is to give you "search terms"
>>> or "breadcrumbs". As without a device to experiment with,
>>> it might be difficult to identify any extra steps needed.
>>>
>>> The drivers are actually in Windows Media Player installer
>>> kit. The MTP Porting Kit (I have three copies on disk here),
>>> on one of them I added the word "useless" to the file name.
>>> And an examination today confirms this. I can't see a damn
>>> thing of interest in there. Maybe some earlier version of the
>>> Kit actually had a driver. I don't see a driver in the version
>>> I've got. WMP11 should be a good source. (Note - WMP itself
>>> likes to validate that the OS is genuine, so expect some
>>> blow-back from using this. When doing "experiments" on
>>> your computer, you should have a recent backup of C:
>>> at your disposal!!!)
>>>
>>> *******
>>>
>>> I happen to have this on disk already as well.
>>>
>>> wmp11-windowsxp-x86-enu.exe Date Published:
>>> 2010-06-22
>>> File Size:
>>> 25,740,256
>>> bytes
>>>
>>> https://www.microsoft.com/en-ca/download/windows-media-
>>> player-det
>>> ails.aspx?751be11f-ede8-5a0c-058c-2ee190a24fa6=
>>> True&a03ffa40-ca8b
>>> -4f73-0358-c191d75a7468=True
>>>
>>> Using 7ZIP (7-zip.org), I can see wmfdist11.exe inside it.
>>> Which could be extracted, or by using "Open inside" you
>>> can get the stuff out of the inside of it.
>>>
>>> An interesting file in there is wpdmtp.inf . Unlike a lot of
>>> files of INF type that Microsoft writes, it doesn't have the
>>> name of the file inside the header of the file. Which implies
>>> the file does not get renamed in C:\Windows\INF when
>>> installed. It should still have that name. You probably
>>> already have that file in your INF (hidden) folder. You can
>>> adjust the File Explorer viewing properties, to make the
>>> folder visible.
>>>
>>> If the Android in Device Manager with the yellow mark is still
>>> there, you could "Update driver" and point it at wpdmtp.inf
>>> perhaps.
>>>
>>> [SNIP INF FILE CONTENTS]
>>> ****************************************
>>>
>>> So while the Samsung package is 16,007,072 bytes in size, it
>>> still manages to have a dependency on outside resources
>>> (wpdmtp.inf). For that part at least, it's a kind of "stub
>>> installer". The folder also has a ton of other stuff, so the
>>> package solves more than just an MTP issue.
>>>
>>> And this is the info Microsoft provides to developers.
>>>
>>> "The MTP Setup Information (.inf) File"
>>>
>>> https://msdn.microsoft.com/en-
>>> us/library/windows/hardware/ff59768
>>> 7(v=vs.85).aspx
>>>
>>> By searching for the specific Android device you've got,
>>> perhaps you can determine any device specific things
>>> that need to be done.
>>>
>>> I haven't a clue how the AddService thing could be
>>> throwing an error. There isn't likely to be a typo
>>> in there.
>>>
>>> [SNIP LOG]
>>>
>>> Paul
>>
>> I tried updating the Android driver using "wpdmtf.inf" from my
>> hard drive.
>>
>> However, XP says that my INF file doesn't list my hardware and
>> refuses to proceed.
>>
>> Do I need a more up to date "wpdmtf.inf"? I tried to get it
>> here but the link doesn't provide the file.
>>
>> http://www.infdump.com/download-inf-
>> files_new.php/inffiles/W/wpdmtp
>> .inf/5.2.0.0/download.html
>>
>> I don't want to install MTP Porting Kits or Windows Media
>> Player tools which some people refer to.
>
> In this example, you can see someone hack their wpdmtp.inf file
> and add an identity string to get their mobile device to be
> detected.
>
> http://forum.xda-developers.com/showthread.php?t=1291293
>
> c:\windows\inf\wpdmtp.inf
>
> ;Device is identified by Microsoft OS descriptor
> ;If your device does not support it, use specific VID & PID
> for identification ;
> [Generic.NTx86]
> %GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
> %GenericMTP.DeviceDesc%=MTP, USB\VID_413C&PID_B10B&MI_00
> <--- hacked added line ;
> [Generic.NTamd64]
> %GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
> %GenericMTP.DeviceDesc%=MTP, USB\VID_413C&PID_B10B&MI_00
> <--- hacked added line
>
> You can use USBTreeView, to get more information about the
> Android device, and get values for VID and PID. They are
> four character hex strings.
>
> http://www.uwe-sieber.de/usbtreeview_e.html
>
> In the sample picture here, you can see the "Device ID" field
> is rich in numbers for the purpose.
>
> http://www.uwe-sieber.de/gif/usbtreeview_1.png
>
> Using the field you find in USBTreeView that
> looks like this - "VID_413C&PID_B10B" , you may be
> able to do a Google search and see someone else hacking
> their wpdmtp.inf for the purpose. If you're worried
> about the exact syntax.
>
> Paul
I downloaded USBtreeview and saw an exclamation mark on one of the
ports in the tree on the left side.
Below is the text of what USBtreeview reports for that port. I
notice there are one or two parts which say "error". In particular
it says for DriverKeyName: ERROR_FILE_NOT_FOUND
Seems a pretty substantial error. But what to do?
##################### START ###########################
================= USB Port1 ============
Connection Status : 0x01 (Device is connected)
Port Chain : 4-1
PortAttributes : 0x00000002 (Shared USB2)
=================== USB Device =======================
DriverKeyName : ERROR_FILE_NOT_FOUND
---------------- Connection Information ---------------
Connection Index : 0x01 (1)
Connection Status : 0x01 (DeviceConnected)
Current Config Value : 0x00
Device Address : 0x01 (1)
Is Hub : 0x00 (no)
Number Of Open Pipes : 0x00 (0)
Device Bus Speed : 0x02 (High-Speed)
------------------ Device Descriptor ------------------
bLength : 0x12 (18 bytes)
bDescriptorType : 0x01 (Device Descriptor)
bcdUSB : 0x210 (USB Version 2.10)
bDeviceClass : 0x00 (defined by the interface
descriptors)
bDeviceSubClass : 0x00
bDeviceProtocol : 0x00
bMaxPacketSize0 : 0x40 (64 bytes)
idVendor : 0x1D4D (Pegatron Corporation)
idProduct : 0x504A
bcdDevice : 0xFFFF
iManufacturer : 0x02 (String Descriptor 2)
Language 0x0409 : "Android"
iProduct : 0x03 (String Descriptor 3)
Language 0x0409 : "Android"
iSerialNumber : 0x04 (String Descriptor 4)
Language 0x0409 : "171214PE5063000"
bNumConfigurations : 0x01
------------------ String Descriptors -----------------
------ String Descriptor 0 ------
bLength : 0x04 (4 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language ID[0] : 0x0409 (English - United States)
------ String Descriptor 2 ------
bLength : 0x10 (16 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "Android"
------ String Descriptor 3 ------
bLength : 0x10 (16 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "Android"
------ String Descriptor 4 ------
bLength : 0x20 (32 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "171214PE5063000"
------ String Descriptor 5 ------
bLength : 0x08 (8 bytes)
bDescriptorType : 0x03 (String Descriptor)
Language 0x0409 : "MTP"
--- MSFT String Descriptor 0xEE --
bLength : 0x12 (18 bytes)
bDescriptorType : 0x03 (String Descriptor)
qwSignature Lang 0x0409 : "MSFT100"
bMS_VendorCode : 0x01
bPad : 0x00
---------------- Configuration Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x02 (Configuration Descriptor)
wTotalLength : 0x002C (44 bytes)
bNumInterfaces : 0x01
bConfigurationValue : 0x01
iConfiguration : 0x00 (No String Descriptor)
bmAttributes : 0x80
D7: Reserved, set 1 : 0x01
D6: Self Powered : 0x00 (no)
D5: Remote Wakeup : 0x00 (no)
D4..0: Reserved, set 0 : 0x00
MaxPower : 0xFA (500 mA)
------------------- OTG Descriptor --------------------
bLength : 0x05 (5 bytes)
bDescriptorType : 0x09
bmAttributes : 0x00*!*ERROR bmAttributes bits 2-7 are
reserved (should be 0)
---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x00
bAlternateSetting : 0x00
bNumEndpoints : 0x03 (3 Endpoints)
bInterfaceClass : 0xFF (Vendor Specific)
bInterfaceSubClass : 0xFF
bInterfaceProtocol : 0x00
iInterface : 0x05 (String Descriptor 5)
Language 0x0409 : "MTP"
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x82 (Direction=IN EndpointID=2)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x0200 (max 512 bytes)
bInterval : 0x00 (never NAKs)
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x01 (Direction=OUT EndpointID=1)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x0200 (max 512 bytes)
bInterval : 0x00 (never NAKs)
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x83 (Direction=IN EndpointID=3)
bmAttributes : 0x03 (TransferType=Interrupt)
wMaxPacketSize : 0x001C
Bits 15..13 : 0x00 (reserved, must be zero)
Bits 12..11 : 0x00 (0 additional transactions per
microframe -> allows 1..1024 bytes per packet)
Bits 10..0 : 0x1C (28 bytes per packet)
bInterval : 0x06 (6 ms)
---------- Other Speed Configuration Descriptor -----------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x07 (Other_speed_configuration
Descriptor)
wTotalLength : 0x002C (44 bytes)
bNumInterfaces : 0x01
bConfigurationValue : 0x01
iConfiguration : 0x00 (No String Descriptor)
bmAttributes : 0x80
D7: Reserved, set 1 : 0x01
D6: Self Powered : 0x00 (no)
D5: Remote Wakeup : 0x00 (no)
D4..0: Reserved, set 0 : 0x00
MaxPower : 0xFA (500 mA)
------------------- OTG Descriptor --------------------
bLength : 0x05 (5 bytes)
bDescriptorType : 0x09
bmAttributes : 0x00*!*ERROR bmAttributes bits 2-7 are
reserved (should be 0)
---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x00
bAlternateSetting : 0x00
bNumEndpoints : 0x03 (3 Endpoints)
bInterfaceClass : 0xFF (Vendor Specific)
bInterfaceSubClass : 0xFF
bInterfaceProtocol : 0x00
iInterface : 0x05 (String Descriptor 5)
Language 0x0409 : "MTP"
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x82 (Direction=IN EndpointID=2)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x0040 (max 64 bytes)
bInterval : 0x00 (never NAKs)
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x01 (Direction=OUT EndpointID=1)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x0040 (max 64 bytes)
bInterval : 0x00 (never NAKs)
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x83 (Direction=IN EndpointID=3)
bmAttributes : 0x03 (TransferType=Interrupt)
wMaxPacketSize : 0x001C
Bits 15..13 : 0x00 (reserved, must be zero)
Bits 12..11 : 0x00 (0 additional transactions per
microframe -> allows 1..1024 bytes per packet)
Bits 10..0 : 0x1C (28 bytes per packet)
bInterval : 0x06 (6 ms)
---------- Binary Object Store (BOS) Descriptor -----------
bLength : 0x05 (5 bytes)
bDescriptorType : 0x0F (Binary Object Store)
wTotalLength : 0x0016 (22 bytes)
bNumDeviceCaps : 0x02
------------- USB 2.0 Extension Descriptor ------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x10 (Device Capability Descriptor)
bDevCapabilityType : 0x02 (USB 2.0 Extension)
bmAttributes : 0x02
LPMCapable : 1 (Link Power Management protocol is
supported)
BESLAndAlternateHIRD : 0 (BESL & Alternate HIRD definitions
are not supported)
BaselineBESLValid : 0 (not valid)
DeepBESLValid : 0 (not valid)
BaselineBESL : 0
DeepBESL : 0
----- SuperSpeed USB Device Capability Descriptor -----
bLength : 0x0A (10 bytes)
bDescriptorType : 0x10 (Device Capability Descriptor)
bDevCapabilityType : 0x03 (SuperSpeed USB Device Capability)
bmAttributes : 0x00
Bit 0 Reserved : 0x00
Bit 1 LTM Capable : 0x00 (no)
Bit 7:2 Reserved : 0x00
wSpeedsSupported : 0x0F (Low-Speed, Full-Speed, High-
Speed, SuperSpeed)
bFunctionalitySupport : 0x01 (lowest speed with all the
functionality is 'Full-Speed')
bU1DevExitLat : 0x01 (less than 1 盜)
wU2DevExitLat : 0x01F4 (less than 500 盜)
##################### FINISH ###########################
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-09 08:42 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-09 08:35 -0400
Re: How to reinstall Android driver on WinXP? "J. P. Gilliver (John)" <G6JPG@soft255.demon.co.uk> - 2016-09-10 10:27 +0100
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-10 11:37 +0100
Re: How to reinstall Android driver on WinXP? Rob Morley <nospam@ntlworld.com> - 2016-09-10 14:33 +0100
Re: How to reinstall Android driver on WinXP? Arno Welzel <usenet@arnowelzel.de> - 2016-09-15 08:36 +0200
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-15 09:16 -0400
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-10 10:00 -0400
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-12 21:35 +0100
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-12 21:39 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-12 20:00 -0400
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-13 12:54 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-13 11:24 -0400
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-11-23 15:32 +0000
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-11-23 17:00 -0500
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-12 21:47 +0100
Re: How to reinstall Android driver on WinXP? Mike Tomlinson <mike@jasper.org.uk> - 2016-09-10 17:27 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-10 14:01 -0400
Re: How to reinstall Android driver on WinXP? Daniel James <daniel@me.invalid> - 2016-09-11 14:49 +0100
Re: How to reinstall Android driver on WinXP? Chronos <usenet@chronos.org.uk> - 2016-09-12 10:41 +0100
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-12 21:49 +0100
Re: How to reinstall Android driver on WinXP? Robin <rbw0@hotmail.com> - 2016-09-10 22:26 +0100
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-12 21:33 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-12 20:12 -0400
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-09-13 13:02 +0100
Re: How to reinstall Android driver on WinXP? Paul <nospam@needed.invalid> - 2016-09-13 11:36 -0400
Re: How to reinstall Android driver on WinXP? Arno Welzel <usenet@arnowelzel.de> - 2016-09-15 08:36 +0200
Re: How to reinstall Android driver on WinXP? Gene Malvern <gmalvern@demon.co.uk> - 2016-11-22 15:26 -0700
Re: How to reinstall Android driver on WinXP? pamela <invalid@nospam.com> - 2016-11-23 15:24 +0000
Re: How to reinstall Android driver on WinXP? Gene Malvern <gmalvern@demon.co.uk> - 2016-11-23 13:47 -0700
Re: How to reinstall Android driver on WinXP? "Bill in Co" <surly_curmudgeon@earthlink.net> - 2016-11-23 14:40 -0700
Re: How to reinstall Android driver on WinXP? Gene Malvern <gmalvern@demon.co.uk> - 2016-11-23 15:32 -0700
Re: How to reinstall Android driver on WinXP? Gene Malvern <gmalvern@demon.co.uk> - 2016-11-23 15:49 -0700
csiph-web