Drivers won't install

desertgal wrote:
> Paul wrote:
>> desertgal wrote:
>>> Paul wrote:
>>>> desertgal wrote:
>>>>> Paul wrote:
>>>>>> desertgal wrote:
>>>>>>
>>>>>>> The thing is, neither phone shows in device manager because XP
>>>>>>> never installs the drivers for the phone, just the one for the
>>>>>>> usb data cable & it uses the built in XP driver. XP doesn't even
>>>>>>> "see" the phone so the add hardware wizard never runs, it only
>>>>>>> "sees" the usb data cable.
>>>>>>>
>>>>>>> The phone has never showed in device manager as anything, it just
>>>>>>> isn't there cause XP is blocking the install.
>>>>>>>
>>>>>>> I have BitPim & that's what I've always used to transfer files to
>>>>>>> & from the phone. As you said, no software will work if XP won't
>>>>>>> install the phone drivers.
>>>>>>>
>>>>>>
>>>>>> Get out UVCView and copy/paste the info from the phone.
>>>>>>
>>>>>> Paul
>>>>> Hope this is what you need. It doesn't show the phone at all, just
>>>>> the data cable.
>>>>>
>>>>>
>>>>> English product name: "USB Data Cable"
>>>>>
>>>>> ConnectionStatus: Current Config
>>>>> Value: 0x01 -> Device Bus Speed: Low
>>>>> Device Address: 0x01
>>>>> Open Pipes: 2
>>>>>
>>>>> ===>Endpoint Descriptor<===
>>>>> bLength: 0x07
>>>>> bDescriptorType: 0x05
>>>>> bEndpointAddress: 0x81 -> Direction: IN -
>>>>> EndpointID: 1
>>>>> bmAttributes: 0x03 -> Interrupt Transfer Type
>>>>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>>>>> Video Class
>>>>> bInterval: 0x0A
>>>>>
>>>>> ===>Endpoint Descriptor<===
>>>>> bLength: 0x07
>>>>> bDescriptorType: 0x05
>>>>> bEndpointAddress: 0x02 -> Direction: OUT -
>>>>> EndpointID: 2
>>>>> bmAttributes: 0x03 -> Interrupt Transfer Type
>>>>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>>>>> Video Class
>>>>> bInterval: 0x0A
>>>>>
>>>>> ===>Device Descriptor<===
>>>>> bLength: 0x12
>>>>> bDescriptorType: 0x01
>>>>> bcdUSB: 0x0100
>>>>> bDeviceClass: 0xFF -> This is a Vendor
>>>>> Specific Device
>>>>> bDeviceSubClass: 0xFF
>>>>> bDeviceProtocol: 0x00
>>>>> bMaxPacketSize0: 0x08 = ( Bytes
>>>>> idVendor: 0x0DF7 = Mobile Action Technology
>>>>> Inc.
>>>>> idProduct: 0x0800
>>>>> bcdDevice: 0x0000
>>>>> iManufacturer: 0x01
>>>>> English (United States) "MobileAction Technology Inc."
>>>>> iProduct: 0x02
>>>>> English (United States) "USB Data Cable"
>>>>> iSerialNumber: 0x00
>>>>> bNumConfigurations: 0x01
>>>>>
>>>>> ===>Configuration Descriptor<===
>>>>> bLength: 0x09
>>>>> bDescriptorType: 0x02
>>>>> wTotalLength: 0x0029 -> Validated
>>>>> bNumInterfaces: 0x01
>>>>> bConfigurationValue: 0x01
>>>>> iConfiguration: 0x04
>>>>> *!*ERROR: no String Descriptor for index 4!
>>>>> bmAttributes: 0x80 -> Bus Powered
>>>>> MaxPower: 0x32 = 100 mA
>>>>>
>>>>> ===>Interface Descriptor<===
>>>>> bLength: 0x09
>>>>> bDescriptorType: 0x04
>>>>> bInterfaceNumber: 0x00
>>>>> bAlternateSetting: 0x00
>>>>> bNumEndpoints: 0x02
>>>>> bInterfaceClass: 0xFF -> Vendor Specific Device
>>>>> bInterfaceSubClass: 0xFF
>>>>> *!*CAUTION: This appears to be an invalid bInterfaceSubClass
>>>>> bInterfaceProtocol: 0xFF
>>>>> *!*WARNING: must be set to PC_PROTOCOL_UNDEFINED 0 for this class
>>>>> iInterface: 0x00
>>>>> *!*ERROR: 0xFF is the prerelease USB Video Class ID
>>>>>
>>>>> ===>HID Descriptor<===
>>>>> bLength: 0x09
>>>>> bDescriptorType: 0x21
>>>>> bcdHID: 0x0100
>>>>> bCountryCode: 0x00
>>>>> bNumDescriptors: 0x01
>>>>> bDescriptorType: 0x22
>>>>> wDescriptorLength: 0x0025
>>>>>
>>>>> ===>Endpoint Descriptor<===
>>>>> bLength: 0x07
>>>>> bDescriptorType: 0x05
>>>>> bEndpointAddress: 0x81 -> Direction: IN -
>>>>> EndpointID: 1
>>>>> bmAttributes: 0x03 -> Interrupt Transfer Type
>>>>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>>>>> Video Class
>>>>> bInterval: 0x0A
>>>>>
>>>>> ===>Endpoint Descriptor<===
>>>>> bLength: 0x07
>>>>> bDescriptorType: 0x05
>>>>> bEndpointAddress: 0x02 -> Direction: OUT -
>>>>> EndpointID: 2
>>>>> bmAttributes: 0x03 -> Interrupt Transfer Type
>>>>> wMaxPacketSize: 0x0008 = Invalid bus speed for USB
>>>>> Video Class
>>>>> bInterval: 0x0A
>>>>
>>>> The fact that the data cable ID is still showing, means the
>>>> driver can't contact the phone for some reason. Or that
>>>> particular Mobile Action driver doesn't recognize a VX5400 phone
>>>> and know what to do with it.
>>>>
>>>> *******
>>>>
>>>> OK, I'm confused. I thought a "data cable" was just a passive
>>>> USB cable, with the connector on one end selected based
>>>> on the phone. Sometimes the phone connector has multiple
>>>> functions, with more than USB wires on it (audio for headphones?).
>>>> Which is why there is more than one model of passive USB cable.
>>>> The phone end may have more pins than are necessary for USB.
>>>>
>>>> (Examples for LG phones)
>>>>
>>>> [URL="http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0"]http://www.buywirelessnow.com/lg/do/search/searchProduct?search=data+cable&x=0&y=0[/URL]
>>>>
>>>>
>>>> Now, I found this interesting. It turns out the Mobile Action is some
>>>> kind of bridge device. If the Mobile Action driver was working
>>>> on your computer, the USB ID apparently magically changes. And
>>>> if it is a bridge, perhaps UVCView cannot see the phone as a result.
>>>>
>>>> [URL="http://www.natox.be/ma8280p/"]http://www.natox.be/ma8280p/[/URL]
>>>>
>>>> I can't tell now, what protocol is on the other end of that cable.
>>>> Why have a bridge, when USB works perfectly well ? It implies
>>>> the phone is not actually USB.
>>>>
>>>> Does this mean your data cable has malfunctioned ? Or does it
>>>> imply that both phones are failing to meet their end of the
>>>> protocol, whatever it is ?
>>>>
>>>> I presume the Mobile Action driver has to figure out what USB ID
>>>> to fake, such that the proper USB ID is returned for the other
>>>> software to use. So the Mobile Action driver must query the phone
>>>> some how, to figure that out. Then the Mobile Action does a
>>>> USB bus reset, after which, the new USB identity is shown to
>>>> the computer. Then, whatever software is relying on seeing an
>>>> LG phone identity, should work.
>>>>
>>>> It makes me wonder, whether some other interconnection method
>>>> might work instead. Like, if the phone really was USB, would
>>>> connecting the phone directly with a passive cable work ?
>>>>
>>>> [URL="http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1"]http://www.amazon.com/Mobile-Action-Cable-Software-Motorola/product-reviews/B0009817ZA/ref=cm_rdp_hist_hdr_cm_cr_acr_txt?ie=UTF8&showViewpoints=1[/URL]
>>>>
>>>>
>>>> When I look through the Mobile Action FAQ collection, there is
>>>> mention of a "Prolific USB to serial" cable. Which suggests
>>>> at least one of the Mobile Action cables is just a USB to
>>>> serial (RS232) protocol.
>>>>
>>>> [URL="http://global.mobileaction.com/support/support_Faq.jsp"]http://global.mobileaction.com/support/support_Faq.jsp[/URL]
>>>>
>>>> What is the Mobile Action model number of the data cable ?
>>>>
>>>> In this cell phone adapter schematic, it appears the phone
>>>> uses a logic level interface, rather than true
>>>> bipolar RS232 levels. So maybe the thing really is weird,
>>>> and needs adaptation.
>>>>
>>>> [URL="http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif"]http://web.archive.org/web/20071013073846/http://pinouts.ru/images/cable_cell.gif[/URL]
>>>>
>>>>
>>>> Post the Mobile Action model number, so I can try and find it
>>>> on their site.
>>>>
>>>> Paul
>>> The cable is specific to the phone model, the number on the cable is
>>> MA-8072P. I've used it before with no problem until XP was
>>> reinstalled. The plug on the phone end is small & flat, not square
>>> like a regular usb. The software I have for the phone is updated for
>>> the VX5400 & downloaded from the MA site.
>>
>> OK, things I'd look for.
>>
>> 1) Go back to setupapi.log and check for VEN 0DF7 and DEV 0800
>> and see what is going on. Look for error messages or something
>> abnormal.
>>
>> 2) Give this a try, and see if anything extra shows up.
>>
>> "Device Manager does not display devices that are not
>> connected to the Windows XP-based computer"
>>
>> [URL="http://support.microsoft.com/kb/315539"]http://support.microsoft.com/kb/315539[/URL]
>>
>> 3) There is a procedure for cleaning up the USB stack, but
>> I'm not sure at this point, whether that is going to help
>> or not. This is done in Safe Mode (press F8 at boot).
>>
>>
>> [URL="http://www.usbman.com/Guides/Cleanup%20Device%20Manager%20Safe%20Mode.htm"]http://www.usbman.com/Guides/Cleanup%20Device%20Manager%20Safe%20Mode.htm[/URL]
>>
>> I'd prefer to have a look around in Device Manager first, to see what is
>> hanging around from previous efforts.
>>
>> Paul
> Ok, first off I went to the mobile action site & did a search for the
> phone &/or cable, nothing showed up.
>
> This AM I checked device manager & there is one unknown device showing
> up in the usb ports. UVCView shows this message for the unknown device:
>
> ---===>Device Information<===---
>
> ConnectionStatus: FailedEnumeration
> Current Config Value: 0x00 -> Device Bus Speed: Low
> Device Address: 0x00
> Open Pipes: 0
> *!*ERROR: No open pipes!
>
> ===>Device Descriptor<===
> *!*ERROR: bLength of 0 incorrect, should be 18
> bLength: 0x00
> bDescriptorType: 0x00
> bcdUSB: 0x0000
> bDeviceClass: 0x00
> *!*ERROR: Device enumeration failure
>
>
> This is on Port6 which is where the phone used to be recognized. I'm
> sure nothing is in the same port since I got the pc back after having XP
> reinstalled so I have no idea what is plugged in to that port now.
>

Try another port. "No open pipes" = "not working for sure".
You can't make any progress, unless the config is visible again.

With USB devices, driver installation is one of two possibilities.
Either you're supposed to install the drivers *before* the device
is plugged in for the first time. Or you're supposed to install
the drivers *after* the device is plugged in. The product
documentation should say which option they prefer.

The reason for that, is to prevent automatic driver installation,
of something inappropriate.

In your case, the device has a unique ID, of VEN 0DF7 and DEV 0800.
Your original trace, showing "Vendor Specific Device" was probably
intended to prevent the data cable from being automatically
identified, if it was plugged in before a driver was installed.
So Windows shouldn't have used a USB standard protocol stack with
the data cable. The Mobile Action driver could then work its
magic, and change the VEN/DEV and likely the InterfaceClass.

For a driver, scroll to the bottom of this page.

[URL="http://usa.mobileaction.com/download/download1.jsp?phoneBrand=8&modelID=588"]http://usa.mobileaction.com/download/download1.jsp?phoneBrand=8&modelID=588[/URL]

MA - 8072P USB Cable Device Driver & Modem Driver

[URL="http://ds.mobileaction.com/CDMA/USB/PureModem/ModemSetup_Pure-CDMA_V95.exe"]http://ds.mobileaction.com/CDMA/USB/PureModem/ModemSetup_Pure-CDMA_V95.exe[/URL]

HTH,
Paul
 >> Stay informed about: Drivers won't install