Category filter
How to deploy OS updates on Android devices?
The Update OS remote action in Hexnode UEM allows IT administrators to remotely push system firmware and security patches to managed Android devices to ensure organizational security and application compatibility.
Why Deploy Android OS Updates Remotely?
Remote OS deployment mitigates security risks associated with outdated firmware, such as unpatched vulnerabilities and bugs. It ensures that critical enterprise applications function correctly and that all endpoints across the fleet maintain a consistent, secure software environment.
- Security Patching: Resolves security bugs and vulnerabilities found in earlier OS versions.
- App Compatibility: Ensures enterprise-grade software runs on supported OS versions.
- Operational Efficiency: Eliminates the need for physical device access to perform system upgrades.
- Centralized Management: Updates can be targeted to specific devices, users, or entire groups from a single console.
Prerequisites and Critical Safety
Before initiating an update, ensure the target devices meet the following specific hardware and software criteria:
| Requirement | Specification |
|---|---|
| OS Version | Android 5.0 or higher. |
| Device Configuration | Custom ROM configured devices. |
| System Agent | Hexnode System Agent app must be in the /system/priv-app directory. |
| Signature | Firmware must be signed by the OEM vendor. |
To avoid bricking the device, verify that the firmware package is bootable via Android Debug Bridge (ADB) sideload before uploading the Update file URL.
Step-by-Step Guide: Enforcing OS Updates
Administrators can initiate updates for the entire fleet or specific individual endpoints.
1. Bulk Deployment (Multiple Devices/Groups)
- Log in to the Hexnode UEM portal.
- Navigate to the Manage tab.
- In the Devices sub-tab, select the target Android devices.
Note:
You can also select Users, Device Groups, User Groups, or Directory Services.
- Click on Actions > Updates and select Update OS.
- Configure the update parameters:
- Update file URL: Enter the direct download link for the firmware.
- File hash: Provide the MD5 hash of the update ZIP file (used as a checksum to verify data integrity).
- Select the installation method:
- Automatically install the update: Installs the update silently without user interaction.
- Prompt user to install the update: Allows the user to initiate the installation on the device.
- Click Update.
2. Individual Device Deployment
- Navigate to the Manage tab.
- Click on the specific device name to open the Device Summary page.
- Select Actions > Updates > Update OS.
- Enter the Update file URL and the File hash.
- Choose between Automatically install the update or Prompt user to install the update.
- Click Update.
Troubleshooting Guides
| Problem | Resolution |
|---|---|
| Update fails verification / Hash mismatch | Ensure the MD5 hash provided matches the ZIP file exactly. You can obtain this using OS-dependent terminal commands or third-party hashing tools. |
| Device is “Bricked” or fails to boot | This usually occurs if the package was not bootable via ADB sideload. Ensure the firmware is OEM-signed and verified for the specific hardware model. |
| Update not reaching the device | Verify the device is Online. If the device is behind a firewall, ensure the Update file URL is accessible from the device’s local network. |
| “Update OS” action is missing | Confirm the device is running Android 5.0+ and that the Hexnode System Agent is correctly installed as a privileged system app. |
Frequently Asked Questions (FAQs)
What is a File Hash and why is it required?
A File Hash (Hexnode specifically uses the MD5 hash) is a fixed-length string that acts as a digital fingerprint for the ZIP file. It serves as a checksum to ensure the file was not corrupted or altered during the download process.
Can standard consumer Android devices be updated?
The remote Update OS action for Android specifically requires custom ROM configured devices with the Hexnode System Agent pre-installed in the privileged system directory. Standard consumer devices may not support this specific remote action.
Is user intervention required for the update?
Not necessarily. If the administrator selects Automatically install the update, the process happens silently. User intervention is only required if the Prompt user to install the update option is enabled.
Does Hexnode host the update ZIP file?
No. Administrators must provide a valid Update file URL where the ZIP package is hosted. This should be a direct link accessible by the target devices.
