Everything else either updates specific system components or restores content you chose to keep.
A standard firmware update does not remove anything you put on the device. Your apps, your containers, your configuration and your data are untouched, and the Debian packages you installed are still installed afterwards — though still installed is not the same as unchanged: see “If your own software depends on the platform” below.
Everything else either updates specific system components or restores content you chose to keep.
And one thing to do every time, before any update: create a backup. The device does not create one for you automatically — your most recent manual backup is your rollback point.
Four ways to deliver an update. The package type, never the path, decides what happens.
Web UI | Command line | RCMS |
USB stick |
Firmware update The standard field update. Installs in place: no re-flash, no wipe. Nothing removed | Full-image install Re-flashes the base OS by USB, with physical access. Erased, containers included | Clone restore Replaces the whole software state; becomes the new factory baseline. Replaced by the clone |
You can deliver an update to a RobustOS Pro device four ways: the Web UI, the command line, RCMS (remote fleet management), or a USB stick. The delivery path does not decide what happens to your device — the package you apply does.
How it arrives — doesn't matter4 paths Web UI browser Command line SSH RCMS fleet management USB stick physical access |
↓ package in↑ status & logs out |
ROBUSTEL EG5120 RobustOS Pro 2.4.x |
↓ outcome decided by↑ never by the path |
What it carries — decides everything3 types Firmware update removes nothing you added Full-image install starts the device over Clone restore replaces state · becomes baseline |
There are three package types, and they behave very differently:
| Package type | What it does | Your packages, apps, containers, configuration, data |
|---|---|---|
| 1. Firmware update (the standard field update) | Installs the Robustel system components that come with that release, in place. No re-flash, no wipe. Not every release carries a new kernel; the release notes say whether one does. | Nothing removed. |
| 2. Full-image install | Re-flashes the base operating system and erases everything you added on top of it. Performed via USB, with physical access to the device. | Erased — containers included. |
| 3. Clone restore | Replaces the device's entire software state with a prepared "golden image" clone. The clone also becomes the device's new factory baseline. | Replaced by the clone's content. |
When this document says "an update keeps X" or "an install erases Y," it always means one of these three package types — regardless of whether it arrived over the Web UI, USB, the command line, or RCMS.
Every operation, every part of the device. The three you meet most:
| Operation | What happens |
|---|---|
| Firmware update | Apps, containers, configuration, data, backups: kept. Your Debian packages: not removed. Robustel components and kernel: replaced. |
| Snapshot restore | Your packages, apps, configuration and data: replaced by the snapshot. Containers: kept. |
| Factory reset | Returned to the factory baseline; configuration to defaults. On-device backups: erased. |
The tables below cover every operation that changes software state on a 2.4.x device, and every part of the device it could affect.
How to read the entries:
apt installs use, so it can change a package version even though it removes nothing.The columns:
| Firmware update | Full-image install | Clone restore | Package operations | Snapshot restore | Automatic failback | Factory reset | RST button | |
|---|---|---|---|---|---|---|---|---|
| Debian packages you installed | Not removed | Erased | Replaced | Replaced ¹ | Replaced | Replaced | Reset | Reset |
| Apps (App Center) | Kept | Erased | Replaced | Replaced ¹ | Replaced | Replaced | Reset | Reset |
| Containers (Docker) | Kept | Erased ² | Replaced | Kept | Kept ³ | Replaced | Reset | Reset |
| Device configuration | Kept | Reset to defaults | Replaced | Kept | Replaced | Replaced | Reset to defaults | Reset to defaults |
| User data & logs | Kept | Erased | Replaced | Kept | Replaced | Replaced | Reset | Reset |
| Backups & snapshots on the device | Kept ⁴ | Erased | Erased | Kept | Erased | Kept ⁵ | Erased | Erased |
| RCMS cloud connection | Kept | Erased ⁶ | Replaced | Kept | Replaced | Replaced | Erased ⁶ | Erased ⁶ |
¹ Package operations change the packages and apps you tell them to — that is their job. There is no automatic rollback of a package operation, so treat package changes with the same care as updates: back up first.
² A full-image install erases containers along with everything else you installed — copy container data off the device, or capture it in a clone package, before a full-image install.
³ Snapshots do not include containers — a snapshot restore leaves your containers as they are.
⁴ The device never creates a backup automatically — not even before an update. Whatever backup you created last is your rollback point. Make one before every update.
⁵ Automatic failback restores your last backup and keeps it afterwards — it is not consumed.
⁶ If the device is enrolled in RCMS, it re-registers automatically after a reset or re-image — its cloud identity is derived from its serial number — provided RCMS is still enabled. A reset to defaults switches the RCMS agent off; re-enable it and the device re-registers by serial number, with no re-enrollment.
| Firmware update | Full-image install | Clone restore | Package operations | Snapshot restore | Automatic failback | Factory reset | RST button | |
|---|---|---|---|---|---|---|---|---|
| Boot software (bootloader) | Kept | Replaced ⁷ | Replaced | Kept | Kept | Replaced | Replaced | Replaced |
| Kernel | Replaced | Replaced | Replaced | Kept | Replaced | Replaced | Replaced | Replaced |
| Base operating system | Kept | Replaced | Replaced ⁸ | Kept | Kept | Kept | Kept | Kept ⁹ |
| Factory pre-installed software | Kept | Replaced | Replaced | Kept | Kept | Kept | Kept | Kept |
| Robustel system components | Replaced | Replaced | Replaced | Kept ¹⁰ | Replaced | Replaced | Reset | Reset |
| Cellular modem firmware | Kept ¹¹ | Kept | Kept | Kept | Kept | Kept | Kept | Kept |
| WiFi/Bluetooth firmware | Kept ¹² | Replaced | Replaced | Kept | Kept | Kept | Kept | Kept |
| Factory baseline (your "factory state") | Kept | Erased ¹³ | Replaced ¹⁴ | Kept | Kept | Kept | Kept ¹⁵ | Kept |
⁷ The bootloader is replaced only if the image carries a different bootloader version.
⁸ Skipped if the clone was built from the same base OS version the device is already running.
⁹ The RST button restores the factory baseline; it does not re-flash the base operating system.
¹⁰ Robustel system components arrive only inside the three package types above — never through a regular package operation.
¹¹ Cellular modem firmware is never part of an operating-system update. It is updated only by its own dedicated, vendor-provided firmware package.
¹² WiFi/Bluetooth firmware ships with the operating system and is refreshed when the base OS is. On some models it is also included in the standard firmware update package and refreshed then — see the model notes in What's on Your Device.
¹³ A fresh factory baseline is generated from the new image the next time the device boots.
¹⁴ The clone becomes the device's new factory baseline — from then on, "factory state" means the clone.
¹⁵ The factory baseline is what a factory reset restores from — the reset uses it, it does not change it.
A standard firmware update installs the Robustel system components that come with the release. Not every release carries a new kernel — when one does, the kernel is replaced too. Nothing you installed is removed — but that is not the same as unaffected, in two ways. Your software comes back up on a platform that has changed underneath it. And the update installs its own packages into the same package database your own apt installs use, so a package version can change even though nothing is deleted.
What a routine update does not do is move you to a different kernel version. Your kernel line is set by your device's hardware platform and its RobustOS Pro generation — not by the individual release. RobustOS Pro keeps the same kernel line for the whole of a major version: security fixes are backported into that line rather than delivered by moving you onto a new kernel version. A different kernel generation arrives with a major-version migration (2.x to 3.x), which is a migration, not a field update. Because the line follows the hardware, two different models on the same RobustOS Pro version can show different kernel versions — that is expected, not a mismatch.
Validate a new release against your own software on one device before rolling it out to the fleet, and read its release notes. If a specific kernel or package version matters to you, record the versions you depend on and check them after that first update.
A full-image install and a clone restore replace the base operating system as well — but both also erase or replace everything you installed on top of it, so on those paths your software is being put back in place regardless.
These are constant across every operation in the tables above — updates, installs, restores, and resets:
The Cybersecurity Version shown on the Dashboard (System Information panel) names the security-certification baseline the installed firmware was certified against. It is part of the firmware itself, not a value kept on the device, so no operation changes it on its own. It changes only when you install firmware certified against a newer baseline, or restore a clone built from one. It does not change when individual fixes are installed. ¹⁶
¹⁶ This means the Cybersecurity Version is not a patch level. To see what fixes a release contains, check its release notes.
"Reset" means returned to the factory baseline, whatever your unit's baseline contains.
Standard unit A fresh device with default settings and no customer software. | Custom factory image Your company's intended delivery state, not an empty one. | After a clone restore Every later factory reset returns to the clone. |
"Reset" in the tables means: returned to the factory baseline — whatever your unit's baseline contains.
You can check which baseline your unit carries from the command line (/etc/version-clone is present on units carrying a custom or cloned image). It is not currently shown in the web interface.
Two things, every time.
1 The device does not do this automatically. It is the rollback point for automatic recovery too. | 2 Know the package type Firmware update, full-image install or clone restore. Unsure? Check its documentation first. |
1. Create a backup. The device does not do this automatically. Your last manual backup is the rollback point for the automatic recovery, too — a fresh backup means recovery lands you somewhere recent, not weeks back.
2. Know which package type you are applying. A firmware update removes nothing you installed (though a package version can change — see the promise table above); a full-image install starts the device over; a clone restore replaces everything with the clone. If you are unsure which type a file is, check its documentation before applying it.
Updating Your Device How to perform each update, and downgrading. | When Something Goes Wrong What to do when an update fails. |
| Next · step 8 of 13Updating your device →How to perform each kind of update, including your own software. |