Hi @ID_AA_Carmack, do you have any news on this matter?
Hi @ID_AA_Carmack, do you have any news on this matter?
@magnetic_tape The companion app is not required, you can put the device into fastboot mode and flash it from there. The instructions are in the docs, something like holding the volume down button while powering it on.
@ID_AA_Carmack Thanks for your feedback. Flashing isn't the issue here. It's just that the unlocked firmware is still asking for pairing with the app upon starting it for the first time, thus defeating the initial purpose of making the headset still useful in 20 years
@ID_AA_Carmack Not that we are entitled to have a truly unlocked build or anything, I for one am grateful for your effort and I'm merely pointing that there could be some more tweaking to do for this build to match the announced goal of preventing technological obsolescence of the Oculus Go
@ID_AA_Carmack (just to recap: the companion app isn't needed to flash the unlocked build you're perfectly right on that, but the firmware still ask for it for a pairing upon first boot. I've tested it on both a shrink-wrapped Oculus Go and a factory reset one)
@magnetic_tape There is a way around that, let me dig it up next week.
@magnetic_tape If you can adb into the device after flashing the OS, this may do the job: adb root adb shell am startservice -a nux.ota.SKIP_NUX -n com.oculus.nux.ota/.NuxOtaIntentService
@ID_AA_Carmack @magnetic_tape Hi John, I recently picked up an Oculus Go due to the unlocked build. I do have adb by default on the unlocked build. The com.oculus.nux.ota package isn't installed on that build. I think the pairing screen is built into com.oculus.vrshell because if I disable that it goes black.
@Deadman_Android @magnetic_tape Do you know if your headset had previously been put into developer mode? @magnetic_tape -- the Go you flashed with the unlocked build definitely does not let you 'adb shell' into it?
@Deadman_Android @magnetic_tape I also got these suggestions: You could try the following commands from the bootloader menu: fastboot oem set-retail-device 0 or fastboot oem set-enable-adb-on-retail 1 But if the nux disable doesn't work, that may not help even if you do get adb.
@ID_AA_Carmack @Deadman_Android Thank. Fastbook oem unlock command finally worked thus adb root and adb shell are working so I can confirm that the unlocked build enables adb. The pairing screen isn't skippable thought so this still is an issue but if it's embedded into vrshell there isn't much you can do.