Forum Discussion

gtinnguy's avatar
gtinnguy
Honored Guest
1 month ago

Quest 3 Stuck on Boot Screen

Like the title says. Stuck on the logo screen. Have tried many factory resets. The problem doesn't appear to have to do with proximity sensor, as I've seen suggested elsewhere, because the headset is providing audible tones when I put it on and off. I've also tried to use the developer hub and while it says it's connected by bluetooth, I can't get it to connect to wifi. I was hoping for developer hub to work.

Any ideas? Thanks

2 Replies

  • gtinnguy's avatar
    gtinnguy
    Honored Guest
    30 days ago

    Thank you, Steve. I will clean it with a swab and make sure the silicon cover is not interfering with it. 

  • steve_40's avatar
    steve_40
    Honored Visionary
    1 month ago

    A proximity‑sensor failure is still the most common real‑world cause of a Quest 3 that boots to logo and never progresses - even if the headset makes tones when you put it on. The tones only prove the headset detects state changes (e.g. the headset can detect physical movement), not that the sensor is functioning correctly for the OS boot sequence.

    Even though you hear tones, the Quest 3 can still fail to boot because:

    • The OS requires a valid, continuous proximity‑sensor signal to complete the boot sequence.
    • A weak, corroded, or partially failing sensor can still trigger tones but fail during the boot process.
    • Repair shops report this exact symptom pattern as the most common failure mode. FixMyOculus explicitly states that a stuck boot/black screen with audio is almost always a failed proximity sensor requiring replacement - not software, not resets.

     

    What you have already tried (and why it doesn’t rule out sensor failure)

    • Factory resets. These don't bypass the sensor. If the sensor is bad, the OS never finishes loading.
    • Audible tones when putting the headset on. This only means the hardware interrupt fires. It does not mean the sensor is providing the correct continuous signal the OS needs.
    • Developer Hub connects via Bluetooth but not Wi‑Fi. This is consistent with a headset that never completes boot - Wi‑Fi services don’t start until after the OS loads.