Quote:
Originally Posted by Renate
Ok, it's time to dive in. Do you know UsbView.exe? It's here: https://www.ftdichip.com/Support/Uti...crosoftUSBView
Figure out which location on the left side of the screen which is your port.
Just plug/unplug whatever and look for changes.
Make your Lumi go to fastboot.
Look in the right side of the screen for Class/Subclass/Protocol of ff/42/03 that's fastboot.
Code:
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0xFF
bInterfaceSubClass: 0x42
bInterfaceProtocol: 0x03
Then look up at the top:
Code:
Device Descriptor:
bcdUSB: 0x0310
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x09 (9)
idVendor: 0x18D1
idProduct: 0xD00D
Edit: And it should also say this:
Check the VID/PID (idVendor/idProduct). Do they show up in UsbLog nice in green?
If not, find it in Zadig and load a new driver.
Does fastboot getvar all work? (It should spit out 100 lines). |
I was delayed by other work, but I am back now.
I have found the Lumi2 in USBview.
Code:
Device Descriptor:
bcdUSB: 0x0320
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x09 (9)
idVendor: 0x18D1
idProduct: 0x4EE2
bcdDevice: 0x0419
iManufacturer: 0x01
0x0409: "QUALCOMM"
iProduct: 0x02
0x0409: "BENGAL-IDP _SN:A2C376A9"
Code:
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x03
bInterfaceClass: 0xFF
bInterfaceSubClass: 0xFF
bInterfaceProtocol: 0x00
iInterface: 0x05
0x0409: "MTP"
iSerialNumber: 0x03
0x0409: "16E91C12"
bNumConfigurations: 0x01
The utilty Usblog shows the "Location/ID" as 16E91C12.
VID: 18d1 (also 0000, 05c6)
PID: 4ee2 (also 4ee7, 0004, 9008)
Under "Name," there are multiple events from today, some of which have the following two IDs:
Code:
BENGAL-IDP _SN:A2C376A9
Code:
QUSB_BULK_CID:041C_SN:A2C376A9
However, I still am not able to issue any command "fastboot" in the ADB folder:
Code:
C:\>fastboot getvar
< waiting for any device >