SMHUB OS - Update & Restore Methods

IMPORTANT NOTIFICATION FOR USERS WITH "BRICKED" DEVICES

Some users experienced a "bricked" device after updating over any method (Type-C / SD-Card or through the web UI). This issue appeared because of U-Boot changes introduced in version 0.2.0, when the Robust Auto-Update Controller ("RAUC") was introduced.
Users who experienced that were able to recover their "bricked" device by flashing back 0.1.2 via Type-C (because it did not contain the new RAUC changes) and then updating directly to a 0.3.x version via Type-C.

Below is a simple explanation of what happened and how it was fixed.

When the device turns on, the very first piece of software that runs is called U-Boot. You can think of it like the “starter” or boot manager of the device. Before anything else loads, U-Boot reads some settings (called “environment variables”) from the internal storage (the MMC). These settings tell it how to start the system.

At some point, RAUC (stands for "Robust Auto-Update Controller" - the Linux update system on SMHUB) accidentally damaged/corrupted those settings. When U-Boot tried to read them, it got confused and didn't know how to continue booting properly, and the device failed to boot - which looked like it was “bricked.” (for regular start, or for Type-C/SD-Card updates).

What Was Changed:

To prevent this from ever happening again, we made two fixes:
1. Automatically reset U-Boot's settings whenever they are detected as corrupted. In simple terms: If U-Boot sees that its configuration is broken, instead of crashing or getting stuck, it will throw away the bad settings and restore working default settings - before any damage happens.
2. We also corrected how RAUC marks a software update as “successful.” It will now only do that after an update actually happens, instead of doing it on every boot. The old behavior is likely what caused the corruption.

Simple Analogy:
- Imagine a PC that reads its BIOS settings when it powers on.
- If the BIOS settings get corrupted, the PC might not start.
- The fix is to detect the bad BIOS settings and automatically reset to “factory defaults” so the computer can continue to boot normally.
This is exactly what we are doing here, but for an embedded device.

The good news: starting from SMHUB-OS v0.3.2, the fix is now built-in. You can simply update and recover your device via Type-C / SD-Card.
(See details below https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1)

Your device is now:
- More robust
- Self-recovering
- Protected from this type of failure in the future

---

Your SMHUB can be updated or restored in three different ways:

1. OTA (recommended) – simple updates directly from the Web Interface

2. Type-C Cable – full recovery if the device doesn’t boot via computer

3. SD-Card – full recovery if the device doesn’t boot without copmuter (more reliable)

Below is a quick overview to help you choose the right method 👇

---

🟢 1. Regular Update — OTA (Over-the-Air)

The easiest and safest method for normal updates.

How:
Web Interface → Settings → Updates & Restore → Check for Updates

What happens:
SMHUB downloads and installs the newest version automatically.

✅ Simple — no cables, no drivers
✅ Keeps your data and settings
⚠️ Works only if your system boots normally

---

⚡ 2. Restore via Type-C Cable

Good when OTA fails or you need a clean reinstall.

How:
Connect SMHUB to your PC → Download firmware → run flashing script (flash.bat)  https://smlight.tech/support/manuals/books/smhub/page/updaterestore-using-type-c 

✅ Shows progress on screen
✅ Quick and easy if drivers/cable are OK
⚠️ May fail if USB drivers aren’t installed or cable is poor
💡 If this fails -  use SD-Card method below

IMPORTANT: If the flashing process does not start, please disconnect POE and other Add-ons (4G/Z-Wave)

---

💽 3. Restore via SD-Card (Full Recovery Method)

Use this if your SMHUB is “bricked” or not responding at all.

How:
Copy 3 files (emmc.img, fip.bin, partition_gpt.xml) to a FAT32 SD card → insert into SMHUB → power on → wait ~5 min → power off → remove card → power on again
https://smlight.tech/support/manuals/books/smhub/page/updaterestore-using-sd-card 

✅ Works even if device doesn’t boot
✅ No drivers, no software, no cables
✅ Visible progress - just wait patiently
⚠️ Remove SD before next boot (otherwise it will flash again)

IMPORTANT: If the flashing process does not start, please disconnect POE and other Add-ons (4G/Z-Wave)

---

🧭 Which method should I use?

---

In short:
🔹 Use OTA for normal updates.
🔹 Use Type-C if you need to reinstall.
🔹 Use SD-Card to fully recover a non-booting device.