Notaquest

enabling adb on a meta quest (which is just a weird phone btw) is PAINFUL! you have to get the slow meta horizon app, create an organization, verify it by adding an authenticator or USING YOUR CREDIT CARD and finally, being able to enable a thing androids could do in like 8 taps for years. it doesn't have to be a quest to enable adb. meta still made it a quest for me to make this work for you, and it's gonna suck, but it'll suck less than the normal way. i have uploaded 2 images of forks for meta verification, i will update this message if it works and i can do oauth. update: it did not. you can use the tampermonkey script to automate it or use devtools and grab a cookie. i'm very sorry. this seems to work better on mobile than on pc. tested on android with google chrome. you may need to quickly accept a pairing confirmation on the device and headset. the tampermonkey script cannot be ran on Android Chrome since it doesn't support extensions. you can use firefox for it and swap to Chrome later, use a browser that supports bluetooth and extensions, or do it on a pc first and swap later. firefox is not supported for bluetooth :(

i apologize for you having to give me the token, this isn't something you should need to do to own your device, but sadly, it is required. you can check the html (human friendly code), and you can log network requests from the site. the only place it goes it to is my site with a proxy to meta. yeah, i know what you're thinking if you get what that means. the token goes to my site. i need to for this to work, i'm sorry, there's a thing below explaining the code. i know i can't prove it, but it's safe. if you're really paranoid, reset your password or log out of the page you got the token from to invalidate the token. if i stole your token i wouldn't be telling you to do this. you can even check if it logs into your account before you reset it.

currently only tested on meta quest 3 but should work on other devices. make a gitea issue (link at the bottom) if it doesn't work for any reason.

why does this use a proxy?

meta's api blocks requests from websites (CORS). the proxy forwards your request to graph.oculus.com and nothing else. nothing is stored or logged. you can view the live worker source code or check the network tab yourself. the code is a literal quine program, if i change it, it will change.

what is the point?

normally, enabling ADB on your meta headset, is a PAIN to do, like the amount of work rooting a normal phone takes if you're lucky. which is still bad. you need to create a meta organization, and then verify your account. verifying means a few options: enabling an authenticator app for signing in, or using a credit card and putting a temporary hold on it. that's for enabling the ability to control a device you bought. and not even full access to it. this site lets you enable it without any of that. the only annoying part is the meta token, which sadly i don't think i can bypass. better than nothing i guess?

but i can't access devtools on my phone!

do the tampermonkey script on firefox/a browser on mobile with extension support and swap to one with bluetooth after! or do the following if you can do devtools on a pc but don't wanna do tampermonkey: at the bottom click the generate token qr code button. this will give you a qr code. scan it on your phone and go to the link. it will be prefilled with your token so you don't need to type it :)

what is tampermonkey and how do i get it?

tampermonkey is an extension which lets you install scripts to modify what websites do, such as automatically grabbing cookies when going to a site! which is exactly what this site uses it for. if you can, this is the best way to get a token.

tampermonkey website
chrome (+chromium based browsers) extension
firefox (+firefox based browsers) extension
automated method (tampermonkey required)

  2. after clicking install, click the get token automatically button, which will open a new notaquest tab with your token prefilled.

  4. feel free to uninstall the tampermonkey script afterwards.

manual method (no tampermonkey)
  1. Log into developers.meta.com/horizon/manage/
  2. Press F12 to open developer tools
  3. Application -> Cookies -> click the site
  4. Find oc_ac_at, double-click the value, copy it
  5. Paste it below





report an issue here
view the source here
a project by owenfeldman.com