How to Upgrade Robustel Gateways from RobutOS V3.x to V5.5.x

How to Upgrade Robustel Gateways from RobutOS V3.x to V5.5.x

Overview

Upgrading older Robustel gateways (running V3.x) to the latest V5.5.x firmware unlocks new features and ensures EN18031 security compliance. Because V5.0 is a major system overhaul, you cannot jump directly to V5.5.x. This guide provides the exact sequential upgrade paths and steps to prevent device failure during the process.
💡 Strong Recommendation: Use RCMS for Upgrades We highly recommend using the Robustel Cloud Manager Service (RCMS) to perform these upgrades. It is the most convenient method and actively prevents manual configuration errors. When upgrading a device currently on V3.x, RCMS automatically locks the maximum available firmware option to V5.0. The V5.5.x target firmware will only appear in your selection menu after the V5.0 upgrade is successfully completed, completely eliminating the risk of skipping the milestone version.

What You'll Need

Hardware List:

  • 1 x Supported Robustel Gateway (e.g., R1510, R1511, R2010, R2011, R2110, R5020, or R3000LG).
  • 1 x PC with network access to the gateway or the RCMS platform.
  • Stable power supply (Do not power off during the upgrade).

Firmware & Compatibility:

  • Required firmware files downloaded locally (based on your specific path below).
  • Crucial Warning: Firmware V5.4.0 and higher do not support M1200, M1201, and R1500 models. Do not attempt this upgrade on those devices.

Step-by-Step Configuration Guide

Phase 1: Identify Your Upgrade Path

Find your device model below to determine the exact sequence of firmware files you must install.

Device Model

Required Upgrade Sequence

Standard Models (R1510, R1511, R2010, R2011, R2110)

V3.x → V5.0 → V5.5.x

R5020

V3.x → V3.1.8 (or higher) → V5.0 → V5.5.x

R3000LG

V3.x → V3.1.9 (or higher) → V5.0 → V5.5.x

(Note: If your goal is an EN18031-compliant version like V5.3.5, you still must install V5.0 first).

Phase 2: Backup Current Configuration

Never upgrade without a backup. If an error occurs, this file is required for recovery.

  1. Log in to the gateway's Web GUI.
  2. Navigate to System ->Profile.
  3. Click Export to save the configuration file locally.

Phase 3: Execute the Upgrade Sequence

Follow your specific path from Phase 1. Complete the steps below for each firmware file in your sequence, waiting for a full reboot between each step.

Method A: Via RCMS Platform (For V3.x to V5.0 only)

  1. Log in to RCMS and open the Device Management list.
  2. Select your target device.
  3. Click the Upgrade to ROS 5 button in the action menu.

  1. Select the V5.0 firmware and confirm. (Once on V5.x, use standard RCMS batch updates. Reference: How to Batch Upgrade Firmware via RCMS)

Method B: Via Local Web GUI (Standard Method for all versions)

  1. Log in to the gateway's Web GUI.
  2. Navigate to System -> Update -> Firmware Update.
  3. Select your next required firmware file and click Upgrade.
  4. Wait for the device to reboot completely before proceeding to the next file in your sequence.

Verification & Testing

To confirm the upgrade was successful and the system is stable:

  1. Log in to the Web GUI and navigate to Status -> System.
  2. Check the Firmware Version field to ensure it displays your target version (e.g., V5.5.1).

  1. Verify that your cellular WAN connection is active and transmitting data.

Troubleshooting / FAQ

Q: I have an M1200/R1500. Can I force an upgrade to V5.5.x?
A: No. Hardware limitations prevent these models from running V5.4.0 or higher. The upgrade will fail.

Q: Can I jump straight to the EN18031 compliant V5.3.5 firmware?
A: No. You must install a baseline V5.x firmware (like V5.0) before applying the EN18031 compliant version.
Q: What happens if I skip the sequence and try to upgrade a V3.x device directly to V5.5.x? Will it "brick" the device?
A: No, the system will prevent the action. If you attempt to upload a V5.5.x firmware directly to a V3.x device, the gateway will show a "Flash Failed" or "Invalid Firmware" error. This is because the V3.x kernel cannot recognize the structural changes in versions higher than V5.0. To successfully upgrade, you must follow the sequence: V3.x → V5.0 → V5.5.x. Using RCMS is highly recommended as it automatically hides incompatible versions to avoid this confusion.

Revision History

Version

Date

Author

Changes

1.0

2026-03-24

Hubery

Initial document creation.