Faulty sensor?

[Nala 0]

Hi everyone! 

 

I bought a couple of Meta Quest 3 controllers and with them, the seller added the headset as it was broken. This is what I know about it, according to the previous owner: Meta gifted the unit (a developer version, brand new) to him, but it arrived broken (not detecting the controllers). Then Meta just sent him a new unit, never claiming the defective one.

 

When I received it, it had a very old firmware (don't remember the version, didn't write it down). When turning the headset on, you could see the default environment and the instructions to pair the headset starting by turning the controllers on, but the unit was unable to detect the controllers.

I updated then the firmware (gradually, first older versions and finally the newest) using ADB commands, apparently with success:

 

 

 

Now I got a BSOD, I can hear the music from the initial setup, but can't see anything on the screen except if I press the volume buttons (I can see the volume bar) or if I try to turn it off, I can see then the turning off menu. The white dot over it it's fixed, it doesn't follow the head movements as it should.

 

After reading in different forums and watching some videos, I think that maybe one of the sensors is faulty, but I don't have any idea of which one. Physically, the unit is impeccable, no cracks, no dents, nothing that could give a hint.

I've seen QUAS has an option to see the temperature of the sensors, but only for Quest 2.

 

I've tried the QUAS function to disable all sensors, now when I turn the unit on, I see the black screen with a message saying: "Press the power button to enable cameras and microphone", but can't do anything else.

 

Any idea on how to determine (if that's the issue) the faulty sensor? Is there any way of sending my WiFi network and password to the headset to complete the pairing process using ADB commands?

 

Obviously, as it has already been replaced, contacting Meta is simply out of the question.

 

Thanks in advanced.

 

[Varset 279]

Hi! Thank you for detail description of problems.

First, you can try to use Meta Quest Developr Hub for connect to WiFi on headset.

Then, you can use Quas for restart shell in headset, these options are Testing menu (item number E) and there is option for start Virtual Environment.

 

Also, try to reboot headset three times (!) via option Boot Device in Bootloader menu. You can use item number 4 in Quas for reboot headset to Bootloader.

 

Try to search "black screen" in this section:

https://vrcomm.ru/forums/forum/1-обсуждение-vr-устройств/

[Varset 279]

This problem also can be because system files too old. They update independendly ftom firmware. Try to update headset over web service Meta Software Update Tool.

[Nala 0]

On 7/10/2025 at 12:53 AM, Varset said:

This problem also can be because system files are too old. They update independently ftom firmware. Try to update headset over web service Meta Software Update Tool.

 

Thanks for all your help

Following your indications, this is the first thing I've tried, and the headset has been successfully be updated using Meta's website.

 

On 7/10/2025 at 12:03 AM, Varset said:

Hi! Thank you for detail description of problems.

First, you can try to use Meta Quest Developr Hub for connect to WiFi on headset.

Then, you can use Quas for restart shell in headset, these options are Testing menu (item number E) and there is option for start Virtual Environment.

 

Also, try to reboot headset three times (!) via option Boot Device in Bootloader menu. You can use item number 4 in Quas for reboot headset to Bootloader.

 

Try to search "black screen" in this section:

https://vrcomm.ru/forums/forum/1-обследование-вр- системы/

 

With  Meta Quest Developer Hub, I've been able to setup WiFi on the headset, but then the program ask to complete the first set-up on the headset, and that step is pairing the controllers.

Regarding that part, I can briefly see on the headset the image with the instructions to pair the controllers, I see that image for 2-3 seconds and then the screen goes black. 

I connected to a USB hub, and I get a message saying to format it. On top of the message, there's a white dot that is supposed to move when you move your head, but it doesn't move at all. This is why I think it might be a faulty sensor.

 

I can also cast, but the screen goes black also on the phone right when it goes black on the headset. (see video attached).

 

Since I could connect to WiFi with Meta Quest Developer Hub, I can now see the headset on the Meta phone app. It connects to the headset, but when going into "Headset settings" (to activate developer's mode or pairing the controllers), it only shows "Continue setup" and "Factory Reset" options. If I select "Continue setup", I get a message saying "Headset update in progress", but it's supposed to be updated.

 

QUAS tells "ECHO" is disabled (not sure what it means) and that Developer Mode is not enabled. When trying to restart the headset shell (A or B) I get an error, maybe because I can't enable developer's mode.

 

And also tried to reboot the headset 3 times, but with no luck.

 

I am reading now other posts here by searching "black screen", see if I can try anything else.

 

Quest 3 cast.7z

Изменено 17 июля, 2025 пользователем Nala