Skip to main content
New Participant
January 11, 2024
Solved

Quest 3 ADB permissions

  • January 11, 2024
  • 8 replies
  • 10427 views

Hello!

I recently upgraded from Quest 2 to Quest 3.

But my MQDH Custom Buttons to grab logs & bugreport don't work anymore.

I don't seem to have any permissions on the headset via `adb`

I can see the device with `adb devices`;

I can shell into the device with `adb shell`

But whenever I tried to pull a file or use `cat` I get a permission denied error on all the files in my

sdcard/Android/ ... folders.

 

Any advice would be much appreciated!

 

Joel

Best answer by spolglase

Joel, this is the exact same issue we are having.   The fix ended up being an engine change to how file permissions gets applied when the Unreal application makes new files on device.  The change was suggested in this post by Norman3D: https://developer.oculus.com/first-access/forums/quest/posts/7188174094527160/

 

Basically this is the engine change: https://i.imgur.com/dfznYEl.png

Apparently this is only an issue in the Unreal 4 flavor of the Oculus Unreal engine and is fixed in the Unreal 5 version.

8 replies

New Participant
January 11, 2024

I should mention I am working on an Unreal Engine project using the Oculus 4.27 branch

spolglaseAnswer
Participant
February 27, 2024

Joel, this is the exact same issue we are having.   The fix ended up being an engine change to how file permissions gets applied when the Unreal application makes new files on device.  The change was suggested in this post by Norman3D: https://developer.oculus.com/first-access/forums/quest/posts/7188174094527160/

 

Basically this is the engine change: https://i.imgur.com/dfznYEl.png

Apparently this is only an issue in the Unreal 4 flavor of the Oculus Unreal engine and is fixed in the Unreal 5 version.

Participant
September 2, 2025

๐Ÿ’เนเธฃเธ‡เนƒเธˆ

Participant
February 9, 2024

Hey Joel.  We've been having the same issue.  I created a similar post for the same issue here: https://developer.oculus.com/first-access/forums/quest/posts/7462453453765888/

New Participant
February 22, 2024

Hi Joel, I am experiencing the same issue. The device is detected but failed to receive any adb commands. Have you resolved it?

New Participant
February 25, 2024

I had the same problem and this post was the solution:

https://communityforums.atmeta.com/t5/Quest-Development/Quest-doesn-t-ask-to-give-USB-permissions-in-dev-mode/m-p/746541/highlight/true#M499

 

Killing the server with

adb kill-server

and starting one as sudo with

sudo adb start-server

made the device go from "no permissions" to "unauthorized", and I was able to authorize the system inside the headset.

New Participant
March 4, 2024

spolglase's linked fix did the trick. Needed to add group permissions in `AndroidPlatformFile.cpp`.

Thank you spolglase, and thank you to everyone who took the time to offer suggestions.

Participant
September 2, 2025

 ๐Ÿ›œWi-fi