Skip to main content
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
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
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. πŸ™

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.

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

 

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.

Honored Contributor
July 14, 2026

RageCast​ Software updates are not bricking Quest 2 headsets purposely, a lot of buddies locally have the Q2 for years with no problems. But obviously you do have an issue. I won't go on about factory reset, using the Meta Software Update tool etc, as I'm sure you have tried that. However the Quest 2 is not new and it's possible something has broken. If you're in the US you can try https://www.fixmyoculus.com/

They repair Quest headsets at reasonable price and even send you a free shipping label. If you're not in the US you could try to find local 3rd party repair services where you are. 

New Participant
July 15, 2026

I am not in the US, but thanks for the tip anyway.
My original headset developed a stick drift problem in one of the controllers which made me avoid using it entirely for months until I finally decided to return it to the store I purchased it from a week before it's warranty went out. They said the process would take a while as they need to send it cross boarder to Meta directly. I was expecting for them to just repair the current controller or replace it, but when they got back to me in a couple of months I received an entirely new "refurbished" headset along with new controllers.

This "new" headset has had less than 50 hours of usage and according to the support representative it was under warranty until December 2025. It has never been dropped, hit or anything like that. When I turned it on 2 weeks ago at the day of my original comment it was working completely fine, meaning it could not be a hardware issue. I decided to update it and once the headset reset it is now completely unusable.

Needless to say I am having the same issue OP is having after the same update that created their issue. I would assume that it's not likely both our headsets had the same hardware issue at the same time after the same software update.