cancel
Showing results for 
Search instead for 
Did you mean: 

did Oculus Developer Hub just brick my Quest 2?

JoeS2018
Protege
I've been using and developing on my Quest 2 since I received it in October.  Never had a problem.  Today I decided to try Oculus Developer Hub, mainly to ease installation of OVR Metrics (which, note, I have not actually done yet).

But as soon as I plugged in my device while ODH was running, the screen in the headset went black.  I've rebooted several times (by holding the power button, using adb restart, or using the Restart button in ODH), and it starts to boot normally — I see the Oculus logo — and then it goes completely black again.  No amount of waiting brings it to life.

Disconnecting ODH and using adb logcat, I see it is stuck in a cycle of:

10-22 17:39:27.637 15271 15362 I [OAO] ShellOverlayApp: BlockingLaunch: Awaiting User Identity.
10-22 17:39:28.135 15271 15362 I chatty : uid=10020 com.oculus.vrshell:Overlay identical 49 lines
10-22 17:39:28.145 15271 15362 I [OAO] ShellOverlayApp: BlockingLaunch: Awaiting User Identity.
10-22 17:39:28.148 865 6719 I [CT] : CONSTELLATION:IMU_STATUS: 6e22d15e22cf1e77: [FusionTracked=0.848, OutputTracked=0.848, OutputValid=0.848] [AccelSat=0.000, GyroSat=0.000]
10-22 17:39:28.155 15271 15362 I [OAO] ShellOverlayApp: BlockingLaunch: Awaiting User Identity.

So at the moment my Quest 2 is an expensive strap-on brick, and I'm obviously not getting any development work done.

How do I make it stop "awaiting user identity"?  I guess a factory reset is the next thing to try, but that seems extreme.  Any other options?
0 REPLIES 0