Trusted Zero Client cannot receive OTA update

Below are the steps to fix the issue, along with information on how to identify the device is in a known error state for OTA updates. 

We have a factory provisioner fix for this issue, but this will only resolve the issue for newly provisioned units. Units in the field may require below solution. In our lab, we were able to reproduce this issue 1 out of 10 times. None of the original units shipped in 24.03 had this issue, so an unknown change occurred in the factory to increase the failure rate.

Case:

1. An OTA Update is issued to a device that has never been OTA updated before.
2. The device is online and receives the update.
3. The device issues a Reboot notification in the UI.
4. After reboot, update, and back on the Trusted Zero Client UI, checking the About page in the top right corner shows the device is on the same version and did not update.
5. If this occurs, check the logs to see if the unit is in a known error state:
   1. Open Settings -> Logs and click the View Logs button.
   2. Navigate to the logs folder on the left column and open kern.log.
   3. Check the line containing BOOT_IMAGE if it begins with BOOT_IMAGE=/1/ instead of BOOT_IMAGE=/0/, then the device is in a known error state.

Solution:

Perform a manual firmware rollback:

1. Ensure the device is powered off.
2. Power up the device, then interrupt power when the Anyware logo appears.
3. Repeat step #2 three times.
4. After powering up the device for the fourth time, check the logs:
   1. Open Settings -> Logs and click the View Logs button
   2. Navigate to the logs folder on the left column and open kern.log
   3. Check that the line containing BOOT_IMAGE. It should now begin with BOOT_IMAGE=/0/ instead of BOOT_IMAGE=/1/.
5. Push the OTA update to the device again.
6. The reboot notification will appear after the OTA download completes.
7. After reboot, and install, when the UI comes back up check the About page.
8. It can take a few seconds for the version to update in the UI, but it should now display the correct version after some time.

After above steps are performed, the device self-heals and can no longer enter this error state. Subsequent OTA updates will allow any BOOT_IMAGE type.