Skip to main content
Glynimal
New Participant
August 15, 2026
Question

SOS loop on Meta quest 2 left controller

  • August 15, 2026
  • 7 replies
  • 130 views

Another post, another disappointed customer.

 

I have two left controllers stuck on SOS loop, tried meta support they all suggest unpair and repair.

Take the battery out for 24-48 hours, unpair on the horizon app. Hard reboot the headset, load headset in boot mode. Use a brand new alkaline battery into controller and pair via the horizon app and leave for 20 minutes to try and resolve firmware issue.

I did all of that with no change, and just told out of warranty you will have to buy a new one. Or they may offer you a “out of warranty replacement for £49.99”.

 

If this was stick drift or physical damage I would understand. But it is not. It is corrupted firmware from Meta. Much like when they bricked people’s headsets with a software update. Customers should not have to pay to replace something that Meta has broken.

      7 replies

      PPB36
      New Participant
      August 26, 2026

      I have the same issue but the waranty is still on the go...have trouble to have response from meta

        steve40
        steve40
        Honored Contributor
        August 26, 2026

        It is corrupted firmware from Meta

        If that was the case, everyone's controllers would get bricked, which they haven't.

          GlynimalAuthor
          New Participant
          August 26, 2026

          Interesting, how would you describe the fault then?

          Also in the past when the headsets got bricked by metas update, it didn’t happen to “everyone” but it happened to a lot of people. So I’m not entirely convinced it happens to everyone or no one?

          Maccyb123
          Honored Contributor
          August 26, 2026

          Glynimal Use your imagination. Imagine if some people had an interruption to their WiFi signal while an update is downloading. It happens quite a lot. This can cause a faulty update. This is the main reason that just some people have a problem, but most people don't. steve_40 is right, if it was a Meta fault we would all have it. Use your powers of deduction Sherlock. Or maybe you're Dr. Watson? 

           

           

          Maccyb123
          Honored Contributor
          August 26, 2026

          If the software is corrupted from Meta, nobody with a Quest 2 would have a working left controller. This isn't the case so your theory is wrong. 

          Did you try connecting your headset to the USB port on your PC and running the Meta software update tool which can repair a janky download?

          Here's the link. https://www.meta.com/en-gb/help/quest/software_update/

          Go here on your PC after you connect the headset and run it. It might fix it. 

           

            herve76
            Participant
            August 26, 2026

            My left Touch Pro controller disconnects/reconnects every ~10 seconds after updating to the latest OS, making it unusable — same as several other threads here (1369940, 1259627, 1337529, 1184642). I pulled adb logs from the headset and found the actual cause:

             

            - The controller's radio is fine — the Wi-Fi link connects cleanly every cycle (handshake + DHCP ACKed).

            - Version check passes (otaRequired=0, no update needed).

            - But GkSync — the headset pushing config to the controller — fails every single cycle. ~10s later a watchdog drops the controller (disconnected detached update-required), then it reconnects and loops forever.

            - Over 90s: my left controller = 8 GkSync failures / 7 disconnects; right controller, same headset = 0 and 0.

            - The only hardware difference: broken left is HW revision 0x30, working right is 0x31. Same firmware on both.

             

            It's not a dead radio and not reset-fixable — I tried controller factory reset (X+Menu), unpair/re-pair, Wi-Fi reset, and a full headset factory reset. No change. It's recurred across OS versions, always "solved" only by replacement.

             

            If you're affected, please reply with:

            1. Controller hardware revision (0x30? 0x31?) — small label in the battery area, or in the headset's controller settings.
            2. Left or right controller.
            3. Did it start right after an update?

             

            If we're all on 0x30, this is a software regression Meta can fix.
            Also filed on the Developer Feedback Center with full logs.

            https://communityforums.atmeta.com/discussions/PairingConnection/quest-pro-controller-disconnect-loop-after-update-%E2%80%94-root-cause-rev-0x30-gksync/1381361/replies/1381383?emcs_t=S2h8ZW1haWx8YWNjZXB0X2FzX3NvbHV0aW9uX3JlbWluZGVyfE1UOVRNTEpGU0tZR0YxfC0xfE9USEVSU3xoSw

              steve40
              steve40
              Honored Contributor
              August 26, 2026

              That's not the "SOS loop" issue the OP has, though.

                Terms & ConditionsAccessibility statement