I got curious and asked myself about a challenge: inf file identifying and setting up the device to be driven using winusb.sys. Though by default settings, OS might still see fit to download "drivers" from Windows Update, even though no specialized driver is usually involved since it's all just about the. It's good that at least for ADB mode, it works out of the box either way. Is there a "S1Boot Fastboot" device at 'Universal Serial Bus devices'? Manufacturer: WinUsb Device / Model: ADB Device 'Let me pick from a list of available drivers on my computer', 'Update Driver', 'Browse my computer for driver software', Verify the Compatible Id "USB\Class_ff&SubClass_42&Prot_03" Is there a "S1Boot Fastboot" device with a yellow question mark? Run device manager, goto "Other devices". The manufacuter so0109adb.inf file uses the same driver and settings for ADB and fastboot mode.ĪDB and fastboot is a generic Android feature.īack to Windows 10 default files. Most likely you used this one in the past. Just to confirm, there are XP and later manufaturer drivers. If I encounter that problem again with fastboot mode requiring driver re-install, maybe I can just add the USB\Class_FF&SubClass_42&Prot_01 ID to the CompatibleIDs value under device key in registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in hope to prevent it in the future. Manually installing ADB Device through update wizard in Device Manager while phone is in fastboot mode also works and makes it visible to fastboot utility. I also added USB\Class_FF&SubClass_42&Prot_01 ID to the list of Prevent installation of devices that match any of these devices ID group policy, so the OS won't try "updating" them. I did some cleaning up in Device Manager and removed two drivers that were downloaded from Windows Update for ADB, so now I have phone's entries under Universal Serial Bus devices, not under some custom categories like before. 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 kommentar(er)
