Skip to main content
Deformityy
Inspiring
November 24, 2025
Solved

After factory reset for troubleshooting I can't pair back to meta app it's stuck

  • November 24, 2025
  • 13 replies
  • 2151 views

Devices having issues (meta quest 2) (Samsung galaxy s23 ultra) 

 

I did a factory reset as was recommended to fix the problem of being stuck at 90% when trying to stream to phone. 

I did a factory reset for being stuck at the pairing screen so I went back to boot menu did another reset then did a side loader update and issue was not fixed. 

On my meta app my headset is still registered so I can't input the code to pair the headset again. I have Uninstalled and reinstalled several times and as well cleared the cache and data in the app. I have restarted my phone and my blue tooth.

When I try and pair a new device I get stuck at "allow permissions" but I have given this  app every single permission. I go to manage profiles and am given error 1675012. 

Now, I try and go another way by accessing my account on the website and it says no device is found or registered with this account for some unknown reason but it's still connected through my meta app. 

I have a warranty that is still valid and transaction history. I have looked into how to fulfill my warranty but as a device isn't registered on the website it seems I can not do it. It seems as if this whole process is connivingly convoluted on purpose to inundate people through excessive confusing menus. 

Screenshots will be included of the error screens

 

    Best answer by Deformityy

    I HAVE FOUND A SOLUTION. 

    I did an array of troubleshooting, nothing was working the engineers just offered my warranty as they could not help. 

    1. turned the quest off
    2. (phone) Turned off all locations mobile Data then restarted phone
    3. Turned airplane mode on 
    4. Turned quest back on
    5. (phone) turned airplane off turned everything back on, location wifi everything 
    6. Went to pair a new device and was able to get past the blue screen permissions prompt 
    7. Paired a new device and it automatically detected the code from the headset 

    All Fixed including I can now stream gameplay to my phone again

    13 replies

    MetaStoreHelp
    MetaStoreHelp
    Community Manager
    November 24, 2025

    Hi there Deformityy,

     

    We've just come across your post regarding the pairing issue you are currently having with your Meta Quest 2 headset. We know how eager you are to get back into the world of VR, so we thought we'd lend you a hand.

     

    Thank you so much for all of the troubleshooting steps you have attempted so far, including uninstalling and reinstalling the Meta Horizon mobile app, but please attempt the following steps:

     

    • Ensure phone and headset are connected to the same network, on the same frequency
    • Ensure that "precise location" and "nearby devices" permissions are allowed for the Meta Horizon mobile app by checking the phone's settings
    • Remove any unsupported third-party accessories that may affect communication (such as headset covers, etc.)
    • Try pairing from another device (iOS and Android)
    • Try connecting from another Wi-Fi network

    Should the issue persist after having followed all of the steps, then please get in touch via private message. To do so, please select our name to get to our profile page, or click here. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

     

    We look forward to hearing from you! 

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    DeformityyAuthor
    Inspiring
    November 24, 2025

    I clearly stated that I had tried all of these steps many times already and included Screenshots of my permissions giving the app full access. 

    I do not have another device to use to connect to. 

    Please read the entire post, as I stated above the pairing prompt will not show up as the device is still technically recognized on the app. 

    I will send a direct private message stating the same as this is NOT a solution. 

      MetaStoreHelp
      MetaStoreHelp
      Community Manager
      November 24, 2025

      We really appreciate you having sent us a private message and we will respond to it shortly! 

      If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
      DeformityyAuthor
      Inspiring
      November 24, 2025

      This post had been transferred to their dedicated email support team. I will post on this submission the solution if it is resolved. 

        DeformityyAuthor
        Inspiring
        November 26, 2025

        Update: this issue has not been resolved and it was put on hold pending review by their engineers. That was 2 days ago. They say they will uphold my warranty and I hope they keep their word if this can't be fixed. 

        DeformityyAuthor
        Inspiring
        November 30, 2025

        This topic has still not been fixed. 

        hibyte
        New Participant
        December 3, 2025

        Same issue on my Galaxy S22÷ and my Galaxy S24+. My son's iPhone12 pairs fine with same headset/app version. All apps/firmware on everything is up to date as of today. All permissions required are allowed for the app. 

        I'm wondering if the app is trying to, at some point, validate the permissions using the old app name "Oculus" instead of the new "Meta Horizon" (see error msg in image below). I got this error by reversing the permissions and then hitting the "continue" button again.  If this is what is truly happening...please DM on my bug bounty reward ;)

         

         

         

        DeformityyAuthorAnswer
        Inspiring
        December 3, 2025

        I HAVE FOUND A SOLUTION. 

        I did an array of troubleshooting, nothing was working the engineers just offered my warranty as they could not help. 

        1. turned the quest off
        2. (phone) Turned off all locations mobile Data then restarted phone
        3. Turned airplane mode on 
        4. Turned quest back on
        5. (phone) turned airplane off turned everything back on, location wifi everything 
        6. Went to pair a new device and was able to get past the blue screen permissions prompt 
        7. Paired a new device and it automatically detected the code from the headset 

        All Fixed including I can now stream gameplay to my phone again

          Maccyb123
          Honored Contributor
          December 3, 2025

          Good to know!! 👍👍👍👍👍👍

            Terms & ConditionsAccessibility statement