Short answer: Specify the required boot-integrity policy for the exact image and update path for Android PDA Barcode Scanners. An Android version number alone does not establish the signing root or locked state. Check the proposed shipping build and its supported update and recovery procedure.
Separate image integrity from application behavior
Android Verified Boot checks a chain of trusted software components during boot. Its implementation and rollback protection depend on the device build. It does not establish that a business application is authorized or that a captured barcode reached the right record.
Keep app-key protection separate too. Hardware-backed key checks concern a particular application key, while this decision concerns the operating-system image and trust chain.
Make the required state explicit
Record the exact device variant, firmware image, Android release, patch level, required signing root and locked state. Decide who controls any custom signing root and which service images may be used. A locked device with a custom root may not meet a policy requiring the manufacturer’s built-in root.
Ask the supplier how it identifies an authorized update and what happens after a board replacement or service-image installation. Keep the required re-enrollment and application checks with that repair procedure. Evidence from a different regional image is insufficient.
Test normal boot and a supported update
On a designated sample, record the starting build and the supplier-supported evidence of boot state. If the project requires remote attestation and the device supports it, use a trusted verifier with a fresh challenge and relevant root-of-trust fields.
Install an authorized test update through the documented method. Confirm the resulting boot state and the application’s handling of unfinished work. Boot success does not show that the warehouse transaction was recovered. Preserve the image identity and outcome for each step.
Use documented recovery on test hardware
Exercise only the supplier’s supported recovery procedure on a non-production sample. Android’s boot-flow reference explains how rollback metadata can affect previous slots. Do not assume that an earlier image remains usable.
Lock-state changes can wipe data. Do not unlock a live business device for a demonstration or improvise a bypass after a failed check. Request a repeatable explanation when evidence is missing. Send the image policy, application build and work-recovery requirement through Contact to evaluate the exact supplied configuration.
Device options for this task
Compare AIDC GO HX-21 and AIDC GO HX-27 for Android handheld work. Ask for the boot-state and update documentation for the offered firmware before selecting a configuration for a security policy.