Skip to main content
BBigG
Up and Coming
October 3, 2019

ADB device list empty

Hey there,
when I came back to work this morning, I found both of my
Quests unable to be listed under adb devices. I tried Mac and Win but
the list won't get populated.
In difference to yesterday I realised
that every time I connect a Quest to a computer the Quest will ask to
confirm: "Allow Access to Data. The connected device will be able to
access files on this headset." This wasn't there before remains come
back every time.

I am unable to side load any builds which is kind of a show stopper.

    37 replies

    Show previous replies
    TamToucan
    Inspiring
    November 12, 2019
    Thanks. I'll try that tonight and hopefully get it working. One thing I will say regarding the problem is my previous work was with a fairly well known fitness watch (now discontinued) and I used to help people on the forums with their watch suddenly not being detected by windows. The watch didn't even use a special driver, it was literally the generic driver used for keyboards and mice. Once Windows had decided it didn't recognize the watch the only way I found to recover was I wrote a program to remove all device registry entries for our company. That way it was like plugging the watch in for the first time again.

    We never found out just what was actually going on, so to be fair to Oculus I don't think it's entirely their problem, though they could probably come up with a solution to recover once it does break.
    vrinter
    New Participant
    November 14, 2019
    One additional case that I've had multiple times (but inconsistent) is that I install the XRSP driver in normal mode on the Quest. Then I change to developer mode and the Quest disappears from Windows Explorer. I start up Unreal Engine 4, which checks for Android devices to run stuff on. Then the Quest pops up in the Windows Explorer and is accessible for file transfer and deploying.
    eleister
    New Participant
    November 27, 2019
     @NinjaGaijin Can someone please help with this?  I have read through all of these posts, tried uninstalling and reinstalling updating drivers, turning developer mode on/off, etc. etc. and my Quest will not build from Unity 2019 1.5.  Everything worked perfectly for months and now after this firmware update - nothing.  I have lost so much time!  Please direct me to a solution!

    My Quest shows as connected to Unity in the build window.  Shows in my devices as "quest" and when I start the build, changes to MTP.  I've gone into device control and tried to update according to instructions posted by others above, but my machine does not have the same options. Running Windows 10 and my app is running off of an iPhone. 
    substatica
    substatica
    New Participant
    December 31, 2019
    Very frustrating. On Windows 8.1, I was able to install the Oculus Bootloader driver showing up under Samsung Android Device with Developer Mode off, then after enabling Developer Mode I was able to install the Oculus ADB device -- but now the XRSP Interface shows under USB Devices and the only driver I can set is WinUsb, it won't allow any other device selection and finds nothing compatible in the INF.
    IdoWhy
    New Participant
    December 30, 2020
    I know I'm a bit late but this is literally annoying. Basically, I have everything here but the adb interface doesn't have the option to choose oculus drivers when i press update.
    futureforest
    New Participant
    February 6, 2023

    adb devices isn't working for me now on a quest pro with mac os x. It worked before. Android File Transfer opens. Developer mode is enabled both on the device and my phone. But adb devices doesn't return any results. It worked one time, then I tried to find the device in Chrome and a few seconds later it was gone. I tried swapping USB cables also. FML

    futureforest
    New Participant
    February 7, 2023

    I was able to get 'adb devices' working again by installing Meta Quest Developer Hub, then using it to install the Oculus ADB drivers.

    Terms & ConditionsAccessibility statement