[Maybe I wrote it in the wrong sub-forum. I am adressing the support with my problem.]
before anyone asks, I already opened a support ticket 3 days ago and wait for the answer of the Oculus team but I wanna ask for your support and suggestions too.
I would describe myself as a very tech savvy user. I have been using the Oculus Quest for some time and have never had any issues with the device. I have not actively adjusted anything on the device or manually triggered any updates lately. I use the Oculus Quest for a few hours every couple of days and usually put it on standby with the power cord and wifi active.
A few days ago, I noticed that the display stayed on for hours in idle mode without my intervention. Possibly an automatic update was performed. I waited and a few hours later in the evening, due to the low brightness in the room, I noticed that the display was still lit, whereupon I had to turn the device off, fearing a burn-in of the display if I kept it on overnight. However, it was on for hours and any normal update would have been completed long ago. I then didn't use the device for a few days and didn't turn it back on.
Today I wanted to use the Oculus Quest again and tried to turn it on, however, it is stuck in a boot loop (static and motionless Oculus logo) and won't come out on its own. After about an hour, I turned the device off again and tried again, but to no avail.
I then felt compelled to perform a factory reset, which I did via the bootloader menu. After about half an hour, however, I ended up back in the bootloader menu and the Oculus Quest still does not turn itself back on. If I try to boot the Oculus Quest normally, nothing happens again.
Now I see no other way to boot my Oculus Quest again. The device seems defective or broken and I do not know the trigger. Probably something got corrupted during an automatic update and it thus bricked itself.
By the way, the developer mode of the Quest has always been active. Automatic updates were active. The software was original and unchanged. I haven't tried debugging via ADB yet and I wouldn't even know if anything could be done in this state.
Possibly an update via sideload would be possible, but there you would have to tell me if this would be possible, as I personally have not done this yet. However, I would trust myself to do it in principle.
Otherwise, I only see the possibility of sending the device in from here on and having it checked and repaired by Oculus, since I as a user can no longer do much to reanimate the device. After just under one and a half years of life, such a device, despite gentle use, should not yet go defective in my opinion.
This is the only thing I see after I did several tries of factory-reset.
I can also access the bootloader-menu (to try factory-reset or go into download-mode) but ADB is not working there and I cannot push any manual updates on the Quest. So I am stuck.
I would be very happy about any assistance from your side!
Thank you very much!
Solved! Go to Solution.
@TomCgcmfcCan you explain how I shall connect my phone with the Quest which is stuck in bootloader and can't even access it's own android-based operating system? Have you read what I wrote? The Quest is won't boot and thus won't be able to connect to any device. I already tried several factory-resets and they did not fix it.
If it would be that easy I wouldn't ask for help.
It would maybe help if anyone could explain to me how I can flash the OEM-rom via "emergency download mode" (EDM) because I think I could enter that mode. Updating/repairing the update manually via bootloader-menu is not working because ADB seems not to work properly. I can detect the Quest via "fastboot.exe" though (it shows the serial number and I can enter bootloader-menu and EDL via that program) but I don't know what to do then.
I guess they'll have to help me unbrick it step-by-step or i'll send it to RMA and they do it for me.