cancel
Showing results for 
Search instead for 
Did you mean: 

USB VID/PID of my Quest 2 do not match drivers from oculus - can not use ADB

f_thomas
Level 2

I can not manage to install the ADB drivers. My Quest 2 appears under "Other devices" in the Windows device manager instead of under "Oculus Device" (after plugging it into a Win 8.1 PC, on which the Oculus ADB Drivers 2.0 are installed):

 

Other Devices

  - ADB Interface (yellow exclamation mark)
  - XRSP Interface (yellow exclamation mark)

 

The ADB device of my quest 2 has VID_2833 / PID_0186 and the XRSP device has VID_2833 / PID_0186. When I
allow the connection in the Quest, XRSP goes away and ADB is now VID_2833 / PID_0183. In other words, the Product ID changes from 186 to 183?! I verified that the same PID change happens on my Win 10 media PC.

 

If I install the Oculus ADB Drivers 2.0-Device manually (Device Manager, menu "Action/Add legace hardware", choosing "android_winusb.inf" in the final steps), then this device appears in the device manager:

 

Oculus Device

  Oculus ADB Interface (yellow exclamation mark).

 

It has VID_2833 / PID_0086. I assume that is the PID my Quest 2 should have. So why does mine has a different product ID?

 

I also have a Go. When I plug that in, it shows up correctly under Oculus Device:

 

Oculus Device

  Oculus Composite ADB Interface (NO yellow exclamation mark).

 

The Go has VID_2833 and PID_0083. Everything works with that one.

 

Can it be the cable? I don't think so because that works fine when copying large files to the Quest. I have the 3m cable USB A / C from Kiwi.

 

Can it be the driver? The package is from 2019. That was before the Quest 2 was released. Is there a newer one?

1 REPLY 1

f_thomas
Level 2

Solved: After manually changing the PIDs in "android_winusb.inf" file with a text editor and forcing Windows to accept unsigned drivers (painful processs; see revryl.com/2013/08/06/install-unsigned-drivers/; I had to press F7 blindly because my monitor output was not initialized at that point in the boot process), ADB works. I must have gotten the wrong driver package or has oculus recently changed the PID and not yet updated the drivers?! I changed these lines in "android_winusb.inf" from ...

 

%SingleAdbInterface% = USB_Install, USB\VID_2833&PID_0086
%CompositeAdbInterface% = USB_Install, USB\VID_2833&PID_0083&MI_01

 

to ...

 

%SingleAdbInterface% = USB_Install, USB\VID_2833&PID_0186&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2833&PID_0183&MI_02

 

These two blocks appear twice in the inf file: under [Google.NTx86] and under [Google.NTamd64]. I did get the hardware IDs (USB\VID_2833&PID_0183&MI_02 and USB\VID_2833&PID_0186&MI_01) from the details page of the devices that appear in the device manager when my Quest 2 is plugged in.