I have a DK2 - Its broken. No RMA and no funds to buy myself a CV1.
I have been able to use Fraxuls patched OVRService file to run 0.4.1 - Wondering if anyone has a patched version of OVRServer to bypass the same error for 0.4.4 or above.
Or alternatively, has anyone managed to repair their HMD?
Wondering if anyone has managed to compile a custom firmware using the Open Source FW dump? It may be possible to return the correct value by default to get these faulty devices to some sort of life again.
After much pulling of hair on this I am able to see that the error is passed to the Oculus Config Tool from the ovrserver.exe with a Hex value of 0xFFFFFF060 (-4000), This was confirmed by looking at the SDK Notes on error codes.
My next line of action was to try and block that address from being called in the first instance but this brought back a message of HMD not detected (or something like that). I checked the registers and they constantly update with the same error code. I am wondering if I can find the address that stores the error code so I can patch that part with a success code instead.
Anyone any hints or tips on this?
I am also looking at the Firmware source with a view to making a custom firmware that removes the need for this check and drops in a success code by default.
I know its not a supported device, but better than ending up in landfill.
Still need help?
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
