The ID when in fastboot mode is constant, but otherwise it seems to depend on the OS running, even though it should be constant as well as long as we're talking about the same phone model, in this case Xperia E3. I suspect a conflict happened due to an old entry having a different compatible ID (adb vs fastboot and the fact that fastboot ID is missing from winusb.inf), but the same vendor and device ID. ![]() That problem requiring re-install was actually encountered when putting the phone in fastboot mode. Vendor ID is always VID_0FCE, as should be. ![]() Depending on the software currently running on the phone, hardware ID differs, so who knows which is the "right" one. I use Win10 versions 18 on my two machines. Thanks, I didn't look in system winusb.inf and manufacturer supplied INF must have been downloaded from Windows Update, placing the entry in Device Manager that usually appears under Universal Serial Bus devices under a different category, so I didn't realize it was already supported out-of-the-box.
0 Comments
Leave a Reply. |