Solved! Grayscreen after factory reset(REMOVE TAPE FROM SENSOR)
Another title might be: Stuck on "choose profile" screen as my controllers are not recognized, after changing the batteries. update: it seems like after the last step I did to troubleshoot below where the latest software was updated onto my Meta 3, something changed with the functionality of being able to put tape over the sensor above the lenses, like between the eyebrows. I did this to keep the headset on particularly when I was putting it on and off my elderly parents when I could not cast, to assist them with their experience more quickly. This still works on my other M3 that has not had the newest software update pushed yet. Also, for what it's worth, I have a new pair of really chunky eyeglasses and when I put those on they also blocked the sensor in the same way the tape had, and I got the backlit gray screen. I really hope my rabbit hole helps somebody! meta, I implore you to please leave this post just in case it does. & for what it's worth, when I did successfully complete the factory reset, my controllers were automatically recognized without having to pair them again or anything. original: Changed the OEM rechargeable batteries on my controllers with another set of OEM rechargeable batteries. No big deal, right? No way this can brick my device. Then, tried to log on the headset but got stuck in the screen where you select a profile, as I couldn't use my controllers. (Though I could hard press the meta button and recenter the screen). I have NO third party accessories. My battery is in the 90s, excluding the elite strap. The app could not connect to the headset so I couldn't wipe the device (factory reset) from here. I did however make sure my phone is on the typical wifi network. My bluetooth is on. Sometimes it shows as a connected bluetooth device on my iPhone, but when it does, there's no circle i button next to Connected where you can then hit "forget device." Tried restarting by hitting power button for 30 seconds. I see the logo, then a backlit black screen. Tried restarting by hitting volume down and power button until the special screen pops up. I tried all of the following sequentially, with plenty of time in between each, which again brought me to the backlit black screen. Factory reset Power off Boot device Sideload update Followed your directions to another user with this problem with the original cable to my computer. I selected my device to connect. I get the error message: Connection Failed. Error claiming interface: Ensure no other tabs are accessing the device and that local ADB isn't connected. If needed, run 'adb kill-server' and 'adb detach' in the terminal and retry connect. Gonna be honest, no idea what this means. I went to the command prompt and entered it and obviously, it's not the right thing. So for s&g I went to the Task Manager and killed the background process called adb.exe (32 bit) So this was right!? I then tried again and I got further in the process tree, and got to Recovery software installation complete. Comically with a "continnue" [sic] button. Update successful. Removed device. Tried to start it up, nogo. Hit the power+volume down to get to choices screen, selected Factory Reset. Backlit black screen. I bought an extended warranty on this but I am completely beside myself. What's going on, how do I fix this asap? Thank you.
Rift S Sensor check fail - not resolved by common fixes
Hi, can't seem to find anything recent regarding this issue. Used my Rift S until about 6 months ago. Always worked fine. Did a clean win 11 install on my PC since then and recently decided to hook up the Rift S again. Now i can't get through setup because it fails the sensor check. I have tried every solution i was able to find online (powered USB hub, plugging in DP port after USB, Camera access, reinstalling Rift S drivers through Device manager, etc) and nothing has worked. Meta won't let me open a ticket with them because it doesn't recognize my serial number, I have a feeling the older hardware isnt listed . Some of the public tickets relating to those issues pop up during google searches but trying to open up those ends up on meta's support home page with an error saying the content either doesn't exist or is restricted to me. Most of what I could find online pertains to issues people where having when certain patches where released back in 2019 or 2020. Some of the fixes found online involved forcing a roll back on the firmware of the headset but i couldn't follow through because the app has changed since those years. They reported that their firmware was potentially corrupted during an automatic update and rolling back then re updating had fixed their otherwise "bricked" rift headset. It made sense to me since one of the coinciding factors here is that the software appears changed (oculus to metalink) between my last usage and i'm assuming it might have involved some firmware update. One thing i can mention is that plugging it in any of my PC ports will show up in device manager as Rift S without any errors but Device manager will also show a failed "Unknown USB device (Port Reset Failed)". I can unplug and delete the failed device and the Rift S device, plug the rift again and both will show again so they are clearly linked and not some other peripheral that happen to be connected to my PC. I plugged the rift in an external powered USB Hub, not the PCI E type, no failed devices show up in manager, only the Rift S but i still doesn't pass the sensor check. My cable is physically in perfect condition, I've reseated both ends a few times just to clear that up too. My entire VR experience was always seated (Elite Dangerous) so the cable has endured little stress from roomscale experiences (I don't have any room to even attempt more than a cockpit experience). Skipping setup and putting on the headset only shows 3 dots and my controllers. The controllers are unable to move and stacked together at the floor regardless of their physical location but fiddling with them will show fingers moving(is that normal since we skipped setup or is it experiencing a double issue) I've come across people reporting 3 dots as its own issue. After posting on Reddit, MetaStoreSupport suggested I post here to get some technical help from their team. Anyone can come up with something else or did it just brick itself randomly without being used ? For reference, it has about 200 hours of total use across 4 years which isn't much at all. Thanks.