Pushing OTA ZIP updates to Zebra Android devices via Esper Content Management

Android

Esper's Content Management feature lets you upload OTA ZIP files to your Zebra Android devices remotely. However, because Esper handles file delivery but not installation, you'll need to use Zebra's tools to apply the update after the file arrives on the device. This article walks you through the process.

Before you begin

• Obtain the OTA update ZIP file from Zebra or your internal build pipeline.
• Confirm you have access to the Esper Console.
• Ensure your target devices have adequate storage space for the ZIP file.

How to upload the OTA ZIP file

1. In the Esper Console, go to Content Management from the left-side navigation panel.
2. Click Upload File.
3. Select your OTA ZIP file.
4. Set the destination folder path on the device. For Zebra devices, this is typically /sdcard/ or the path specified in Zebra's documentation for your device model.
5. Select your target device or group.
6. Initiate the file transfer and monitor the transfer status in the Esper Console until the file shows as successfully delivered.

How to apply the update on your Zebra device

After the ZIP file is on your device, you must trigger the installation using Zebra's tools. Choose the method that matches your device configuration:

• Using Zebra StageNow or OEMConfig: Point the tool to the transferred file location and apply the update.
• Using the device's built-in Enterprise Reset or OS Update utility: Navigate to the utility on the device and select the transferred ZIP file to install.
• Using ADB (if available): Run the OEM's recommended sideload command via adb shell to initiate the update.

How to verify the update completed

1. In the Esper Console, go to Devices & Groups → select your device → Device Info.
2. Check the OS build number against the version you expected after the update.

Troubleshooting

File transfer failed or file doesn't appear on the device

• Check available storage on the device.
• Confirm the destination path is writable and matches Zebra's requirements exactly.
• If the file exceeds Content Management upload size limits, consider splitting the delivery or hosting the file externally and downloading it on the device via a script.

Zebra's OTA utility doesn't recognize the transferred ZIP

• Verify the file is in the exact directory required by Zebra's OTA mechanism (typically /sdcard/ or a partition-specific path defined in Zebra's documentation).
• Check Zebra's developer documentation for the correct staging path for your specific device model and OS version.

Content Management transfers are failing across multiple devices in the same group

Contact Esper Support for assistance.

Important notes

• This is a two-step process: Esper Content Management delivers the file only. Installation must be triggered separately using Zebra's tools or ADB.
• Check for native OS Update support: For some Zebra models, Esper offers native OS update integration. Go to Devices & Groups → select your device → OS Update to see if a more streamlined option is available.
• No rollback: Esper does not manage rollback of OTA updates. Validate the OTA package before deploying to production device groups.
• Works for other OEMs: This workflow applies to any OEM delivering OS updates as ZIP packages (Honeywell, Datalogic, etc.), not exclusively Zebra.

Related resources

• Uploading and Transferring Files via Content Management

Still need help?

If you've tried the steps above and still need assistance, submit a support ticket and include the device serial number, OTA ZIP filename, and the error or behavior you're experiencing.