ML2 OS version:
I don't remember the version number but believe it was the third option from the bottom.
Error messages from logs (syntax-highlighting is supported via Markdown):
I can't access compute pack.
Machine's operating system
Windows 10 Pro build 19045.2130.
Is device secure or unsecure
Unsecure (loaner device from early access program).
Does your compute pack get recognized by ML Hub , 'adb devices', or 'fastboot devices'?
- ML Hub
- No (was connecting before compute pack got stuck in fastboot mode)
- 'adb devices'
- No (returns empty list)
- 'fastboot devices'
Yes (displays serial number)
I've been stuck for a long time with hardware issues. My issues are similar to the once described in this thread Issues setting up the device - Hardware Troubleshooting - Magic Leap 2 Developer Forums
After upgrading to Oct release, the controller was "dead" and making beeping noises. I proceeded to downgrade one version at the time, when I had reached the second to the last version in the hub, the update seemed successful as I was able to pair the controller and the "controller connected" was displayed in the headset, however, there was no controller cursor similar to what's described in this post Issues setting up the device - Hardware Troubleshooting - Magic Leap 2 Developer Forums.
I then proceeded to upgrade to the next version, hoping that would fix things, but the update "timed out while waiting for device to reboot" (or similar message). This has happened several times before, but unlike before, this time the device is stuck in fastboot mode (flashing 3 LEDs followed by 2 LEDs).
I tried hard reset (hold power button for 20+ seconds) but it is still in fastboot mode when starting device.
I then proceeded to try to factory reset using adb, but the device is not returned with 'adb devices', just an empty list.
Hoping someone can advise on how I can get out of fastboot mode?