Deploying OEM Firmware OTA Updates (e.g., Azulle) Through Esper: Methods and Phased Rollout

Android

This article explains how to deploy OEM firmware updates (such as Azulle firmware) to your device fleet through Esper. You'll learn two methods for distributing firmware updates and how to implement a phased rollout strategy across your Development, QA, and Production environments.

Before you begin

Contact your OEM (for example, Azulle) and confirm which of the following formats they used to deliver the firmware update:

• A downloadable firmware package file (ZIP or OTA image file)
• A standard OS update through the device's native OTA update channel

This determines which deployment path you'll use in the Esper Console. You should also verify that the firmware update resolves the issue you're addressing (for example, a "Draw over apps" boot problem) before deploying to production devices.

Method 1: Deploy an OEM-provided firmware package file

Use this method if your OEM delivered the firmware as a downloadable package file (ZIP or OTA image).

1. Obtain the firmware package file directly from your OEM.
2. In the Esper Console, navigate to Devices & Groups → OS Updates.
3. Upload the OEM firmware package file.
4. Create or identify a dedicated device group for your first rollout phase. For example, create a "Development" group containing pilot devices.
5. Target the firmware deployment at the Development group and initiate the push.
6. Monitor device status by navigating to Devices & Groups → [Device Name] → Device Details. Confirm that the firmware version has updated and the issue no longer occurs after the devices reboot.
7. After validating the update in Development, repeat steps 4–6 for your QA group.
8. After validating in QA, repeat steps 4–6 for your Production group.
9. Verify that the installed firmware version on all updated devices matches the version supplied by your OEM.

Method 2: Deploy a standard OS update via the OTA channel

Use this method if your OEM delivers the firmware through the device's native OTA update channel.

1. In the Esper Console, navigate to Devices & Groups → OS Updates or Blueprint → Compliance Policy for the target group.
2. Enable OS update management and configure it to allow or trigger the update for your target group.
3. Apply the update policy to your Development device group first.
4. Confirm that devices receive and apply the update. Check Device Details to verify the updated OS and firmware version.
5. After validating in Development, apply the update policy to your QA group.
6. After validating in QA, apply the update policy to your Production group.
7. Verify that the firmware version matches your OEM's supplied version and that the issue no longer occurs on updated devices.

If the firmware package isn't supported

If the Esper OS Update upload tool doesn't support the firmware package format (for example, an unsupported file type or signing format), contact Esper Support. Provide the firmware package metadata and your OEM's documentation so our team can assess compatibility.

If devices don't receive the update

If devices in your target group don't receive or apply the update after you push it, contact Esper Support with details about which devices were affected and the device group you targeted.

Still need help?

If you encounter issues deploying your firmware update or need guidance on phased rollout strategies for your specific environment, submit a support ticket. Our team is here to help.