Forum Discussion
Can't push build to Quest through ADB
I'm having a lot of trouble pushing a build to my quest through the ADB cli. It works on one laptop I have but not another. The error I get says something about vendor keys not being set and the quest shows up as "Unauthorized" when I run "adb devices". I'm assuming from reading this thread (https://www.reddit.com/r/OculusQuest/comments/bux8ki/my_oculus_quest_wont_authorize_adb/) that I should be getting a pop-up in the quest asking to trust the computer but I haven't seen any. I've tried all of the suggested solutions short of a factory reset, which I would rather avoid (internet speed where I am is not the best and it takes a while to update). I hoping there's some more concrete way of triggering the handshake between the quest and the computer.
4 Replies
- Here someone mentioned temporarily disabling the unlock pattern fixed a similar issue for them:EDIT: I just saw that this was mentioned in the post you've linked as well and you've probably already tried that solution. Sorry about that.
- I've never had an unlock pattern set, so I never tried that.
- Anyone?
- @dcrouchelli Welcome to the Oculus Developer Forums!
Unfortunately, you may have to perform a factory reset on your device to get the USB debugging prompt to appear in your headset if it's no longer appearing:
1. Factory reset your Oculus Quest unit (https://support.oculus.com/298586437740040/)
2. Uninstall the companion app from your phone
3. Uninstall all devices related to Oculus (especially the ADB drivers) - you may want to utilize third-party solutions to help with this (USBDeview is a popular option).
Then, start the process all over from the beginning. Prior to plugging in your device into the PC, install the ADB drivers (https://developer.oculus.com/downloads/package/oculus-go-adb-drivers/), and then enable Developer Mode in the companion app.
