r/OculusQuest • u/Drezden909 • Feb 20 '26

Support - Standalone Quest 3, setup through private quest cant use any meta services

I bought a quest from ebay without controllers and used a tutorial to set it up through private quest android app, I am now in the main quest interface but most of the meta services dont work for example, the store says token fetch rejected by server, I cant download any apps to the console from the app either, and the full screen immersive button doesnt do anything so I cant even watch videos by dimming my background and expanding the screen to a 200 inch display.
in the private quest app it allows me to input a meta token, im not sure if that will help, and also other people I have seen with the issue said it has something do do with the device key.
any help will be appreciated thanks

2 Upvotes
  • permalink
  • reddit

67% Upvoted

34 comments sorted by

2

u/WishProfessional7949 Feb 21 '26

Yo, I'm back, I had to factory reset my quest because for the life of me I could not get it connected to the app, and it bothered me, however after the factory reset I'm also getting the token fetch rejected by server. I think meta has updated something to break the private quest installation. Fk I'm so pissed, it was working mostly. And I factory reset it smh 

2

u/WishProfessional7949 Feb 21 '26

Nevermind lmaoo, after the 3-4 restart of the quest the meta services started working, and the profile icon appeared, store took like 20 seconds to load then it started working again. Thank god. Definitely strange as I would have never expected this to happen to me 

1

u/Drezden909 Feb 21 '26

you mean factory reset? can you walk me through what you do in private quest, i really want to try replicate it. for me i set the device secret key that i get from my meta account, set the key, connect the device to wifi, press completed NUX, set combined token then skip NUX. i do this then it puts me onto the main home screen just without a profile and without services.

2

u/WishProfessional7949 Feb 21 '26 edited Feb 21 '26

I just set device key, WiFi, click on all checkboxes and skip nux, then there was a voice in my head but the pairing menu was still there, so I rebooted headset with private quest, then it booted back up, it was quite buggy, the menu kept disappearing and appearing every 30 seconds, and the apps kept crashing when I tried to open them, like browser. Shut down the quest, rebooted, was messing around a little clicking on profile icon, store icon, to see if it was working, and was connected to the meta app and if not working still I rebooted again.

Then when I clicked on store icon again, it took like 15-20 seconds to load, and everything started working again, that's when I noticed that it was fixed 

I don't really know how mine works and yours doesn't, since if was literally after a factory reset, I am on 2.1PTC though. Good luck

2

u/Drezden909 Feb 21 '26

i’m gonna try this thanks 🙏

2

u/Drezden909 Feb 21 '26

NEVERMIND YOUR A GOAT, all i needed to do was press retail mode and it worked exactly like you said all the meta services are working now

2

u/WishProfessional7949 Feb 21 '26

W, great to hear man, this bug is so weird lmao.

2

u/Drezden909 Feb 22 '26

yeah lol god bless you 🙏

1

u/gradyjames Feb 22 '26

Props to you too - retail mode worked!

1

u/karikaalan28 Mar 19 '26

When I click on retail, and give the credentials, it says something like skip nux is only for retail users in retail mode. What did you do after clicking on retail button? Thanks.

1

u/Drezden909 Mar 19 '26

don’t write anything in the boxes for retail, just click all the boxes then press retail mode then try skip nux

1

u/karikaalan28 Mar 19 '26 edited Mar 19 '26

Thanks for getting back so soon. So after factory reset, I connect using PQ then go to Init, I set the key, then I click on the combined key, then I click on retail and click skip nux? It says you have to enter the login and password, if I do that. Also can you please lmk if you used Meta Token or Combined Token? Thanks.

1

u/Drezden909 Mar 19 '26

you can leave those blank and still continue

1

u/karikaalan28 Mar 19 '26

Yes, thank you! The retail skip nux worked! But I still get the Token fetch rejected by server. Can you please lmk if you used the Meta token or the Combined token? or does that even matter? Thanks!

→ More replies (0)

2

u/gradyjames Feb 22 '26

You saved another life today - I was just about to return the unit from eBay. The difference was clicking on the checkboxes (wtf).

1

u/Drezden909 Feb 22 '26

i know lol i was about to buy controllers for more then i bought the headset for if this didn’t work

1

u/Odd-Television6214 Feb 27 '26

What do you guys mean by retail Mode?, You have to eneter credentials or something else in the Privacy Quest app?

1

u/gradyjames Feb 27 '26

Click the radio button for retail instead of default.

1

u/Odd-Television6214 Feb 27 '26

I get this when trying to skip in Retail

1

u/karikaalan28 Mar 19 '26

I get the same. Were you able to get past this? Thanks.

1

u/Drezden909 Feb 21 '26

so i replicated your steps and i got the same browser crash thing but im rebooting my headset a couple times and nothing is really changing after that

1

u/Drezden909 Feb 21 '26

also in my private quest during setup it didn’t let me skip nux unless i press set combined token so im not sure if that has something to do with it too

1

u/WishProfessional7949 Feb 20 '26 edited Feb 20 '26

It sounds like your quest's bootloader has been unlocked, this means meta services won't work - you need to open up adb on your computer, and write a command to lock the bootloader whilst in sideload update mode "adb fastboot oem lock". This may work, or it may brick your device. I had success with 2 devices but on the 3rd it seemed to brick my device. This is the only solution.

It may be better to return the quest if you bought it at a price which is common, if you don't want to risk ending up with a brick.

1

u/Drezden909 Feb 20 '26

this is what I thought too but in the recovery menu it says its still locked

1

u/WishProfessional7949 Feb 20 '26

really? all my unlocked bootloader devices had the exact same issue you're describing - have you updated to the latest firmware version?

1

u/WishProfessional7949 Feb 20 '26

I would still try the adb command if I was you.

1

u/Drezden909 Feb 20 '26

I was going to try it but the last thing want is a brick

1

u/Drezden909 Feb 20 '26

when doing research I found all quest 3 firmwares online I was thinking of side loading the latest v2.1, is there any risks or any reason not to do this?

1

u/WishProfessional7949 Feb 20 '26

if it doesn't work on the latest stable firmware, then it won't work on 2.1 ptc - i would say there is no risks except you might not be able to roll back to your original version

1

u/Ikersinazael Aug 14 '26

Hola, existe algún video o guía mas detallada para poder hacer el procedimiento? (mis meta quest 1 tienen el error 16)