Forum Discussion

SamuelG7V's avatar
SamuelG7V
Honored Guest
21 days ago

Meta Quest 2 boots, shows Meta logo, then screen goes black (controllers work, no headset tracking)

My Meta Quest 2 turns on normally, shows the Meta logo, and I can hear the system/menu sounds, but after a few seconds the display goes completely black.
Important: the headset does NOT power off — it stays on, only the screen goes black.

The controllers work fine (I can hear UI sounds when pressing buttons), but the headset itself has no motion tracking. Moving the headset does nothing. The issue happens every time.

Exact symptoms:

  • Boots normally and shows the Meta logo.
  • After a few seconds: permanent black screen, but the device stays powered on.
  • System/menu sounds continue playing.
  • Controllers work normally.
  • Headset has no tracking (no movement detected).
  • No visible damage to cameras or the shell.

What I’ve already tried:

  • Forced reboot (Power + Volume Down).
  • Entered bootloader menu (it works) and rebooted from there.
  • Factory reset.
  • Installed update from meta via USB C.
  • No visible physical damage or impacts.
  • Tried different chargers/cables to rule out power issues.
  • Tried replacing the motherboard and with a know good working motherboard it still has the same issues.
  • Tried to enable Dev mode on the horizon app but it won't let me (It turns back off if I toggle the switch).

Additional context:

The display stops working while the system keeps running in the background. I assume a hardware fault but I don't know what else could cause this, I’d like to confirm whether this could be related to a failed update or corrupted firmware too but if I tried to enable Dev mode on the horizon app to us the ADB console but it won't let me (It turns back off if I toggle the switch).

Any help from the community or Meta Support would be greatly appreciated.

9 Replies

  • steve_40's avatar
    steve_40
    Expert Trustee

    Did this start happening right after a software update? Make sure your proximity sensor is not obstructed. If you put any tape over it, remove the tape. Make sure the faceplate is not obstructing the sensor. Then, if you still get the black screen, the headset might still be updating itself, so take off the headset and wait about 10 minutes then put it back on. I just got the v83 update earlier today, and after restarting, I got a black screen for about 5 minutes then suddenly the passthrough appeared with the UI menus, and everything was OK again.

    • Maccyb123's avatar
      Maccyb123
      Trustee

      Snap steve_40 I just got it too, and the 6 people I know locally just got it....which is a first! Seems to be working fine, noticed my environments which were looking a bit low res after v81 have drastically improved. Happy about that. Saw one post where someone complained about not being able to filter installed, uninstalled, hidden and updating apps. I can see it and my friends can see it. Do you still have the option? 

      • steve_40's avatar
        steve_40
        Expert Trustee

        Yes, I still have all the filter options. The environments look much better, but I'm not sure if the res has been increased, or if it was something else. In the last version, it felt like the IPD distance was slightly off or something, and it made my eyes feel a bit uncomfortable. The settings menu has been reorganized a bit, and I have two new Experimental settings: Temporal dimming and Positional time warp. The latter setting did not appear until I powered the headset off and on. I have Meta AI, but without the AI. I can activate it, and it recognizes my speech, but then it just beeps and does nothing 🙃. I still don't have Navigator 🤣. I can anchor apps, but it's kind of clunky and needs further refinement. I can only anchor 3 apps at a time, and if I resize an anchored app, it forgets the new size after switching to passthrough and back 🤭. Also, if an app is anchored, the 'focus view' button disappears. The weird glitch that I was having with the profile menu disappearing after waking from sleep seems to have been fixed since the last couple of updates 🙂.