Zebra MX XML-based OS conversion (Android 8 → 13 via ZCP) cannot be triggered remotely

Android

Title: Zebra CC6000 Android 8 to 13 upgrade — local ADB workaround via ZCP

When upgrading a Zebra CC6000 from Android 8 to Android 13 using a Zebra Conversion Package (ZCP), the conversion cannot be triggered remotely through the Esper Console and must be performed locally using ADB.

Why this happens

Zebra's OS conversion process relies on MX (Mobility Extensions) XML provisioning documents delivered to the device's MX layer. Esper does not currently support MXConfig delivery, which is the mechanism required to push these XML documents remotely. Until that support is available, the conversion must be initiated on the device directly via ADB.

What you need before you start

ADB installed on your computer and the device connected via USB
Android 13 OS files staged on the target device
A backup config XML generated from a reference device
ZCP.zip placed at /sdcard/ZCP.zip on the target device

Steps

Confirm all required files are on the device. Open an ADB shell and verify ZCP.zip is present at the correct path:
```
adb shell ls /sdcard/ZCP.zip
```
The conversion will fail silently if this file is missing or misplaced.
Deliver the MX provisioning XML to the device via ADB. Save the following XML to a file named zcp_convert.xml on your computer, then push it to the MX layer using your ADB toolchain or Zebra's StageNow utility:
```
<wap-provisioningdoc>
  <characteristic version="8.1" type="PowerMgr">
    <parm name="ResetAction" value="10" />
    <characteristic type="file-details">
      <parm name="ZipFile" value="/sdcard/ZCP.zip" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>
```
The ResetAction value="10" is the Zebra MX code that initiates a ZCP-based OS conversion. Do not change this value.
Wait for the device to complete the conversion. The device will reboot one or more times during this process. Do not disconnect the device or interrupt power until the device has fully restarted and reached the home screen.
Verify the OS version in the Esper Console. Navigate to Devices & Groups → [Device Name] → Device Info and confirm the OS Version field shows Android 13.

Verify: The device should appear in the Esper Console showing Android 13 under Devices & Groups → [Device Name] → Device Info → OS Version within a few minutes of the device coming back online after the reboot.

If this doesn't resolve it

If the conversion fails or the device does not come back online, collect the following before contacting Esper Support:

Device logs captured immediately after the failed attempt:
```
adb shell logcat -d > conversion_log.txt
```
Esper Agent version (visible in Devices & Groups → [Device Name] → Device Info)
Zebra MX version and BSP version from the device
The exact XML document used during the attempt
Any error messages shown in the Esper Console Activity Feed

Contact Esper Support with these details so the issue can be diagnosed accurately.

Still need help?

If you're unable to trigger Zebra MX XML-based OS conversions remotely through Esper, please submit a support ticket with details about your device model, current Android version, target OS version, and the specific Zebra MX commands you're attempting to execute.