OTA ZIP update not installing on Zebra devices — deliver and apply with Esper

Android

When pushing an OTA ZIP update to a Zebra Android device through Esper, the file is delivered to the device but the update does not install automatically. Esper Content Management handles file delivery only — a separate step using Zebra's own tooling is required to trigger installation.

Why this happens

Esper Content Management is a file delivery mechanism. It transfers files to a defined path on the device but does not execute or install them. Zebra's OS update process requires a separate trigger — such as StageNow, OEMConfig, or ADB — to read the delivered ZIP and apply it to the device partition.

Before you begin

Obtain the OTA update ZIP file from Zebra or your internal build pipeline.
Confirm you have access to the Esper Console with sufficient permissions to use Content Management.
Verify target devices have enough free storage for the ZIP file before transfer.
Note the exact destination path required by Zebra for your device model and OS version — typically /sdcard/, but confirm in Zebra's documentation.

Step 1: Check for native OS update support

In the Esper Console, navigate to Devices & Groups → [Device Name] → OS Updates.
If an OS update option is available for your Zebra model, use that flow instead of Content Management — it is a single-step process that handles both delivery and installation.
If no native update option appears, continue to Step 2.

Step 2: Upload and deliver the OTA ZIP

In the Esper Console, navigate to Content Management in the left-side navigation panel.
Click Upload File and select your OTA ZIP file.
Set the destination folder path to the location Zebra's OTA mechanism expects — for most Zebra devices this is /sdcard/. Using the wrong path will prevent Zebra's tools from locating the file in the next step.
Select the target device or group.
Initiate the transfer and wait until the Console shows the file as successfully delivered before proceeding.

Step 3: Trigger installation using Zebra's tooling

Choose the method that matches your device configuration:

Zebra StageNow or OEMConfig: Create or update a profile that points to the delivered file path and apply the OS update action.
Device built-in OS Update utility: On the device, open the Enterprise Reset or OS Update utility, browse to the transferred ZIP file, and confirm installation.
ADB: If ADB access is available and permitted on the device, run Zebra's recommended sideload command:
```
adb shell
```
Then follow the OEM-specific command for your device model as documented by Zebra.

Step 4: Verify the update completed

Verify: In the Esper Console, navigate to Devices & Groups → [Device Name] → Device Info and confirm the OS build number matches the version included in the OTA ZIP. This value should update within a few minutes of the device rebooting after installation.

Troubleshooting

File transfer fails or the file does not appear on the device

Check available storage on the device before retrying — Content Management cannot deliver a file to a device with insufficient free space.
Confirm the destination path is writable and exactly matches the path Zebra's OTA mechanism expects.
If the ZIP file exceeds Content Management upload size limits, host the file on an accessible internal server and download it to the device using a script or managed browser.

Zebra's OTA utility does not recognize the transferred ZIP

Verify the file was placed in the exact directory Zebra's OTA mechanism reads from — the correct path varies by device model and OS version. Consult Zebra's developer documentation for your specific combination.
Confirm the ZIP file is not corrupted by comparing its checksum against the value provided by Zebra.

Transfer fails across multiple devices in the same group

Check the Activity Feed in the Esper Console for error details that may indicate a connectivity or configuration issue affecting the group.
Verify that devices in the group share the same storage path configuration before retrying.

If this doesn't resolve it

If file delivery continues to fail or Zebra's tooling does not apply the update after following these steps, contact Esper Support. When reaching out, include the following:

Zebra device model and current OS build number
The exact destination path used in Content Management
A screenshot or export of the Activity Feed showing the failed transfer
The Zebra tool or method used to attempt installation, and any error message displayed

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.