We are tracking a similar issue with another developer. We currently think it is related to jumping too many version of the OS at once.
To note, this process above is not a workaround and is documented here. However, we are doing further testing to see if when a device is updated using the prescribed process, the reboot behavior is reduced/resolved
- Rollback devices to 1.1.0 (check the "factory reset option, only during this step. Please leave unchecked for steps 2-4)
- Update 1.1.0 to 1.2.0
- Update 1.2.0 to 1.5.0
- Update 1.5.0 to 1.9.0
A future version of MLHub will help guide users through the update paths.