@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 Thank you very much for getting back on this matter. On a shink-wrapped Oculus Go headset (or a factory reset one), adb isn't enabled by default (as reported in x.com/magnetic_tape/…) so the commands cannot work. [1/6]
@ID_AA_Carmack Thank you very much for getting back on this matter. On a shink-wrapped Oculus Go headset (or a factory reset one), adb isn't enabled by default (as reported in x.com/magnetic_tape/…) so the commands cannot work. [1/6]
@ID_AA_Carmack On a shink-wrapped Oculus Go there's 2 ways to access adb: 1) pair the headset (with an app which be gone in 20 years) to go to developer menu to enable adb) 2) access the "enable sideloading update" menu by holding volume down and power buttons 🧵 [2/6]
@ID_AA_Carmack The 1st option (app) won't be available in 20 years from now if we're realistic Here's the result of the aforementioned commands from the sideload menu (only way to get adb access on a shink-wrapped Oculus go 20 years from now, remember we don't have access to the app) : 🧵[3/6]
@ID_AA_Carmack $ adb devices List of devices attached 1KWP*********6sideload $ adb root adb: unable to connect for root: closed $ adb shell am startservice -a nux.ota.SKIP_NUX -n com.oculus.nux.ota/.NuxOtaIntentService error: closed 🧵 [4/6]
@magnetic_tape So ADB is not available after booting the flashed OS and it is sitting at the pairing screen? There is no chance of rebuilding anything in Shell, but if it is impossible to get to ADB, I'll see if we can somehow get that on-by-default.
@ID_AA_Carmack That's right, ADB isn't available after booting the flashed OS (unlocked build) while sitting at the pairing screen. A new build with adb debugging enabled by default will be a good middle ground if the aforementioned commands can bypass the pairing screen.