Skip to main content
gwg399867
New Participant
June 14, 2026
Question

Quest 2 bricked after updating it to 2.4v

So I recently found my Quest 2 headset laying around on a case after not touching it for over 1-2 years, and I got in the mood to try VR again. It was working just fine, however, I noticed it wanted to me to update it, and so I updated it.

After updating however, it's now bricked, it's booting just fine but the main screen is now flickering between the gray thingy from the cameras and the main menu. The controllers also keep turning on and off and the headset seems to be heating up quite a bit.

I tried many things such as:

  • Updating firmware with ADB using the sideload update option
  • Updating the headset again using Meta's website
  • Factory restting

All of which had no success, so I really appreciate any help with this.

13 replies

Choleni
Choleni
Honored Contributor
June 14, 2026

gwg.399867​ 

my Quest 2 headset laying around on a case after not touching it for over 1-2 years, 

which probably means 30-40 missed firmware updates..... or even more🤪

Then you update to v2.4 and say , "this version bricked my headset"

Maybe the fact, that the headset wasn't updated regularly causes the trouble, not v2.4??🤔

Try factory resetting/restarting the headset again ..... maybe you are lucky and it'll work.

 

If not contact Meta support via email, chat or WhatsApp HERE

    gwg399867Author
    New Participant
    June 14, 2026

    I've tried factory resetting the headset many times by now


    I wonder if maybe if I sideloaded the updates I could get it fixed?

     

    Choleni
    Choleni
    Honored Contributor
    June 14, 2026

    gwg.399867​ 

    I wonder if maybe if I sideloaded the updates I could try and fix it?

    You said that you already tried that...... or do you mean to update to an earlier version first and then go upwards?

    This might have been worked if you had updated via sideload step by step in the first place

    I think, now it's too late for that option. You can't downgrade from the version you already on. 🙁

      RageCast
      New Participant
      June 30, 2026

      I am having this exact same issue. At least I know I am not the only one.
      I also had not used my quest for over a year, but I periodically turn it on to let it update. Last time I updated it was no longer than 3 months ago. Today I decided that I want to play something and turned it on and it launched just fine. Decided to update to the latest patch which resulted in the same issues as above.

      Already tried all options mentioned above and even tried manually sideloading older firmware from an archive. Nothing seems to fix the issue.

      If there are any updates on a potential resolution I would love to hear them.

      Maccyb123
      Honored Contributor
      June 30, 2026

      Choleni​  posted a link in this thread to contact someone at Meta.  Here it is again. Good luck! 

      https://www.meta.com/en-gb/help/support/?g1=5960237440706837&g2=26500769372871399&g3=none&et=none&sg=skip

       

        RageCast
        New Participant
        July 14, 2026

        Meta support basically told me that since my headset is out of warranty there's nothing they could do and I should just buy a new headset.
        I don't understand how they think I could make another purchase from them when they just push out an update bricking a device with 0 hardware issues, which was working perfectly fine before that update.
        This just means that I am not "buying" a Meta headset, I am just renting it for the timeframe of the warranty.

        If they had just dropped official support for the Quest 2 I at least would be left with a working headset instead of a paperweight.

        steve40
        steve40
        Honored Contributor
        July 15, 2026

        I just updated my daughter's Quest 3 to the latest build of v2.5.

        After the update, I could log into my primary profile and all looked good, but when I switched to my daughter's profile all I got was the grey passthrough screen. I could recenter the screen by pressing the menu button, and I could hear the menu-switching sound if I pressed the menu button, but no menus would appear.

        I restarted the headset 3 times, and fully powered it off and on twice, but nothing changed.

        I tried switching between profiles several times, my profile always worked perfectly, but my daughter's wouldn't load.

        So then I put the headset down for about 10 minutes, and then put it back on and tried switching profiles again. Suddenly, after switching from my profile back to my daughter's, I pressed the left menu button and the Loft menu appeared. After that, I was able to open Navigator and everything started working again 😅.

        So maybe you just need to let the headset sit for a while after some updates to let the headset settle in; maybe there were some updates still going on in the background or something 🤷‍♂️.

        USUALLY, when there is a pending software update, I will first fully power off the headset so it will upload all its app data to the cloud. Then I restart the headset and install the update. BUT this time, I just did the update immediately without doing the power/off/on first (and it had been days since the headset was last restarted). So maybe that's what caused the glitch. I think it's safest to restart the headset immediately before doing any update, so that the OS is "clean" without any possible memory corruption/glitches/etc.

          Choleni
          Choleni
          Honored Contributor
          July 15, 2026

          Interesting, thanks for that Steve.

          There was another user with the same issue on a child account.

          I've linked him to your post 🙂

          Child Profile Won't Load Anything | Meta Community Forums - 1377753

          I have not had that problem with my second account, although I never turn off my headset . 🙃

           

            Terms & ConditionsAccessibility statement