Resolving "Signature verification failed error 21" During USB OTA Updates
Audience: Elo and Zebra Customers
Article type: Public Procedure
Symptom
When attempting to apply an Over-the-Air (OTA) firmware update via USB on an Android-based device (such as an Elo Backpack), the installation process fails in the Android Recovery screen and aborts with verification error messages.
Graphic Representation of Error Screen Logs:
Root Cause Analysis
This error indicates that the update.zip payload is cryptographically invalid or has lost structural integrity. The EOCD (End of Central Directory) marker error explicitly indicates that the file structure of the zip is truncated, corrupted, or otherwise unreadable. This blocks the system from performing its mandatory signature check, triggering error code 21 as a security countermeasure to protect the device from system bricking.
This is commonly caused by:
- Faulty USB Flash Drive: Defective flash storage blocks (bad sectors) or unstable controllers corrupt the payload during local file transfer.
- Incomplete Download: The OTA package was interrupted or corrupted while downloading from the portal.
- Incorrect Target Image: The payload's security certificates mismatch the BSP firmware on the physical hardware revision.
Step-by-Step Resolution
- Purge Local Files: Delete the previous
update.zipfrom both the host computer and the USB drive to prevent accidental reuse. - Download Clean Firmware Payload: Re-download the official OTA package from the Elo Customer Support Portal. If MD5/SHA-256 hashes are provided on the site, verify the local file integrity via command-line utilities (e.g., using
CertUtil -hashfile update.zip SHA256on Windows). - Prepare a New USB Flash Drive: Switch to a different, high-quality USB flash drive. Format the drive cleanly with the FAT32 file system.
- Transfer Payload: Copy the newly downloaded
update.zipdirectly into the root directory of the USB drive (do not extract the ZIP container). - Safely Eject and Mount: Safely eject the USB flash drive from the host PC, insert it into the USB-A interface on the Elo Backpack, and proceed with the installation process via the Android Recovery console.
- Use Alternative Storage Media: If verification errors persist across multiple USB drives, attempt the update using an alternative physical medium. Cleanly format a high-quality MicroSD card to FAT32, copy the
update.zipto its root directory, and select the option to apply the update from the SD card in the recovery menu.
💾 1. Selecting the Right SD Card Size
To ensure a seamless update process, we highly recommend using a Micro SD card with a capacity of 32GB or smaller.
- Cards ≤ 32GB: Can be formatted to FAT32 quickly and directly using the native Windows Formatting Tool.
- Cards > 32GB: Native Windows formatting tools do not support partitioning volumes larger than 32GB into FAT32 (Windows defaults larger cards to exFAT or NTFS, which are unsupported by the bootloader).
🔧 2. Formatting Instructions
Option A: Using Standard Windows Tools (For SD cards 32GB or smaller)
- Insert the Micro SD card into your computer's card reader.
- Open File Explorer and navigate to This PC.
- Right-click on your SD card drive and select Format...
- Under File System, select FAT32 from the dropdown menu.
- Leave allocation unit size at default, check Quick Format, and click Start.
Option B: Using Third-Party Utilities (Required for SD cards larger than 32GB)
If you must use an SD card larger than 32GB, you will need to utilize a third-party utility to bypass native Windows volume limits and force a FAT32 format:
- Download and open a trusted formatting utility such as Rufus or the FAT32 Format GUI.
- Select your target SD card device carefully.
- Ensure the target boot selection is set to "Non-bootable" or "FreeDOS" (depending on the utility layout) and set the file system output to FAT32.
- Click Start / Format to apply the changes.
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article