Firmware & downloads
Last updated 2026-06-15
A running log of the firmware images I've flashed on my rCell 100 units, what changed, and how I verify and apply them. I keep local copies so a reflash doesn't depend on the site being up, but you should pull official images for your own hardware.
Placeholder downloads. The download links on this page point at # / local placeholders on purpose — this is a personal notes site, not a redistribution mirror. Version numbers and dates are illustrative.
Version changelog
Newest first. "Applied" is when I rolled it onto my own units.
| Version | Date | Applied | Notes |
|---|---|---|---|
| 5.3.4 | 2026-06-10 | 2026-06-15 | Maintenance. Fixed a rare cellular re-attach stall after tower handover; NTP now retries more sensibly on a cold boot; security backports. My "won't stay up" gremlin is gone since this one. |
| 5.3.1 | 2026-04-02 | 2026-04-20 | Adds per-SIM data-usage counters in the dashboard; SNMP OIDs for signal metrics; minor UI cleanup. Watchdog revert-hold option exposed in the UI (was CLI-only). |
| 5.2.8 | 2026-01-15 | 2026-02-01 | Security roll-up; TLS library bump; fixes a DHCP lease renewal edge case on the LAN. Recommended baseline before jumping to 5.3.x. |
| 5.2.3 | 2025-10-28 | 2025-11-10 | New band-lock UI; improved AUX/diversity handling in weak signal; assorted logging improvements. |
| 5.1.9 | 2025-07-19 | — | Skipped on my units. Notable for adding the outbound VPN client wizard; some users reported a reboot-loop on older hardware revs, so I waited. |
Flashing via the web UI
Straightforward, but do it on the bench or over a rock-solid LAN link — never mid-flash over a flaky cellular session.
- Back up config first (Administration → Save/Restore → Download configuration). Firmware updates usually preserve settings, but assume nothing.
- Download the correct image for your exact model and hardware rev. Verify the checksum (below) before uploading.
- Go to Administration → Firmware Upgrade, choose the
.bin, and start. - Leave it alone. The Status LED will blink through the apply and the unit reboots itself. A flash + reboot is usually 3–6 minutes. Do not cut power.
- After reboot, confirm the new version on the dashboard and spot-check cellular attach and your forwards/tunnel.
Match the image to the hardware. Loading an image built for a different radio variant or hardware rev is the fastest way to brick one of these. When in doubt, don't.
Verify the checksum
Every image should have a published SHA-256. Confirm the file you downloaded matches before flashing:
# Linux / macOS
$ sha256sum rcell100-5.3.4.bin
3f9a2c7b1e64d0a8c5f21b9e7d34a6f0c8b1e2d4a6f8091b2c3d4e5f60718293 rcell100-5.3.4.bin
# compare against the published value, or verify a checksum file:
$ sha256sum -c rcell100-5.3.4.bin.sha256
rcell100-5.3.4.bin: OK# Windows (PowerShell)
PS> Get-FileHash .\rcell100-5.3.4.bin -Algorithm SHA256If the hash doesn't match, the download is corrupt or tampered — delete it and fetch again. Never flash an image whose checksum you couldn't verify.
Downloads
Illustrative entries — links are placeholders on this personal site.
BINrcell100-5.3.4.binFirmware 5.3.4 · current recommended BINrcell100-5.2.8.binFirmware 5.2.8 · prior baseline TXTrcell100-5.3.4.bin.sha256Checksum file for the current image PDFrcell100-datasheet.pdfSpec sheet — bands, power, environmental (reference copy) PDFrcell100-user-guide.pdfMy annotated user guide notesRollback
If a new image misbehaves, you can flash the previous .bin the same way — downgrades are just another firmware upload on these units. Restore your saved config afterwards if the downgrade reset anything. This is exactly why I keep the last two images and a dated config backup on hand; a bad update at a remote site is otherwise a long drive.