09-02-2022 11:44 AM - last edited on 09-26-2022 08:34 AM by Ryanality
I just recently sent my quest 2 and controllers back to be replaced but the refurbished quest 2 controllers that was sent to me won't connect to the refurbished quest 2 headset that was sent to me so my headset is stuck in the paring initial setup screen. I tried linking my headset to my app to set up controllers that way but no matter how many times I tried to pair it putting the pair code in it won't pair up. I have factory reset several times. I have reinstalled the app already a few times. Yes my location and bluetooth is on. I have already been through setting this up with my old quest 2 that I sent back with no problems. I don't understand how I was sent a refurbished quest 2 and controllers that can not even set up. Please help me fix this or let me get a replacement that works.
Solved! Go to Solution.
09-15-2022 08:23 AM
Support told me yesterday that this issue is due to changes to allow meta accounts without needing a Facebook account.
I don’t see why that would stop you at the controller pairing screen, though.
I have asked for a callback next week for update.
09-16-2022 07:31 AM - edited 09-16-2022 07:44 AM
Well, support sent me an email with steps to try.
It worked for me as it updates the software to a point that lets the phone app complete setup and you can pair controllers from the app that gets you past the pairing screen in headset.
So, if you have a PC, here are the steps:
09-16-2022 07:54 AM
Working, you're a star!
But **bleep** Meta for not communicating/solves this.
09-16-2022 11:00 AM
can you do this with a Mac ?
09-16-2022 11:43 AM
I did, same steps and you download mac-version of platform-tools.
09-17-2022 06:08 AM
need some help how to do it cause im on the command part and its not working
09-17-2022 07:25 AM
Do you mean “adb sideload update.zip”?
What happens, not starting to upload or error message or what?
09-17-2022 07:31 AM
yeah
09-17-2022 07:32 AM
the .\adb works but everything else wont
09-17-2022 07:40 AM
it says "the command adb was not found, but does exist in the current location. Window powershell does not load commands from the current location by default. if you trust this command, instead type: ".\adb". see "get-help about_command_precedence" for more details"