Error when connecting a headset to a new Meta account

[Roei_Tzoref]

Has anyone encountered an error when after trying to link the oculus quest 2 HMD through a META account? I  get a message to enter a code in meta.com\device but it gives the error.

I performed the whole registration process in the meta website, it logs in fine in the oculus app in desktop/mobile, but in the HMD it asks me to enter a code generated from the website (meta,com\device), and when I enter it - it gives an "account linked" message in website and HMD and right after that I get a message"an error occurred"

I am connected with a link cable.

here's a recording of what happens:

*Edit:
eventually after months of back and forth emails with meta support which was kind but led to nothing, and after I did a factory reset like all suggested - the situation got WORSE! the headset was useless and didn't even pass the initial setup screen because it was unable to pair with my mobile phone. oculus support suggested I send the headset to them (which would be a PITA because I do not live in a supported country). luckily a local VR lab here in my country was able to do a software update/reset with an some kind of a dev external software/hardware. and now the situation got resolved.

[trmkl]

hey there! i managed to get my bricked headset with the same issue as the OP in working order and if you'd like assistance, DM me in my profile o/

also to anyone reading: Meta staff are completely untrained and useless and will only push the replacement option without even trying any other alternatives so if your issue wasn't solved in the first two or three e-mails, there's no point in beating a dead horse so the best option is to stop wasting your time and try other alternatives.

[trmkl]

it's been three months and i'm not sure if you're still having the issue but i managed to get it fixed, if you'd like assistance, feel free to reach out to me in my profile's DMs and i'll run you through o/

[Choleni]

Hey @trmkl 🙂

If you have a working solution, it would be great if you just post it here and share it with other users.

[trmkl]

-- / / -- READ FOR FIX -- / / --

posting for public awareness, I had the exact same problem as the OP and the following is what fixed it for me:

First of all, obligatory mention that Meta support is USELESS and didn't contribute to nothing in my struggle to get my bricked headset working again

--------------------------------------------------------

with that out of the way, here's what you'll need:

• a bricked headset that won't pair, making it completely useless
• any working computer with bluetooth, be it a laptop or a desktop with any kind of bluetooth USB adapter
• a Oculus Quest developer account
• a Mobile phone for two Two-Factor Authentication to enable the developer account

now to get to work! (btw underlined text are links)

 1 - Factory reset your headset (if you don't know how, look it up)

 2 - Proceed as normal through the initial setup, when you reach the pair screen, try to pair as normal, it is NOT supposed to work as your headset is bricked but just to be sure, do it to confirm you're in the same place as me 

pic rel what you got used to seeing

3 - Create a Oculus Developer account, be it by converting your existing account to a developer one or by creating a brand new account.

After its creation, you need to enable Two-Factor Authentication in order for the account to work (there should be a message Infront of you right after creating an account)

4 - Download and install Oculus Developer Hub and log on with your Developer account

5 - In the Developer Hub, go to Device Manager and click the blue button Set up New Device

6 - Proceed as normal, make sure your headset is turned on and it should appear, now all you have to do is pair with it and in theory it should work! yay

Some notes from my experience: 

Trying to connect to a organization account in the headset led to nothing, i would only get an instant message "An error occurred, please try again" upon clicking the generate new code button (pic rel)

When i did this, after factory reseting my Headset, i hadn't gone further than connecting to a Wi-fi network. i factory reset my headset, picked a language, stopped right after the Wi-fi connect screen and then did the developer hub thing, which led to an error in step 6 where after clicking next on my computer, it kept loading for a while and gave a weird error but right after i went back to my headset, connected to the wi-fi to try again but with it connected to the internet and when i reached the phone code pair screen, it was already paired and i only had to wait for the updates to download so i guess it worked? not sure if i had to do this with the internet connected to my headset or not but hey, it works!

As a non-english speaker i did what i could to try and explain step-by-step what got it fixed for me, using the tutorial on this Youtube video https://youtu.be/mc2JwbtoMBc.

If this works or if you need any help with it, please do let me know!

again, #@$! Meta/Facebook and overall corporations, they don't care about you nor what you think, they refuse to help you with problem they create and expect you to just consume their product so shareholders can earn .0001 cents more.

[nils606.38690]

hello, i have the same problem of device code error which it has become annoyingly persistent.

when i try to generate the device code, there is a error popping up which it says in dutch "meld je aan op een computer of telefoon met je zakelijke emailadres" is by now is becoming enough for me. can you fix this problem immediately? i am missing on vrchat, and please do not disconnect my reply from what your agents have done after i send my transcript over to the help service desk. with regards nils606

[Chundvar]

Hey there @nils606.38690! I definitely recommend reaching out to MetaQuestSupport in PMs. You can do that clicking the profile link and then selecting "Send a message."

[nils606.38690]

the same error happened to me and meta hasn't resolved it.

i think meta doesn't want or isn't willing to solve this problem.

i still hope the meta staff solve this problem.