Firmware flash failed

Firmware flash failed

Symptom

A firmware update aborted partway through. The device reboots into an error state, shows a recovery screen, or no longer responds on the network. The vendor UI may display “upgrade failed” or a flashing status LED.

Danger

Do not power-cycle a device that is still writing firmware. Losing power mid-write bricks the flash chip. Wait at least 10 minutes before you assume the process is stuck.

Likely causes

1. Not enough free space on the device for the staging image.
2. Power lost during flashing (PoE brownout, tripped breaker, someone unplugged the switch).
3. Firmware image checksum does not match — the download was truncated or corrupted.
4. Wrong firmware package for the CPU or hardware revision (for example, armv7 image on an aarch64 board).

Fix

If space ran out

1. Sign in to the device web UI (or serial console).
2. Clear log partitions, old firmware backups, or uploaded snapshots.
3. Re-download the firmware from the vendor and retry. Confirm the posted size is smaller than the free space you cleared.

If power was lost

1. Wait 10 minutes. Some devices retry from the staged image after a boot loop.
2. If the device stays unresponsive, boot from the recovery partition (see the vendor manual for the button combination, often hold-reset-while-power-on for 10 seconds).
3. From recovery, re-flash using the stock image over TFTP or USB.

If the checksum is wrong

1. Re-download the firmware. Compare the SHA-256 to the vendor’s published hash before flashing.
2. Do not use a browser download that was interrupted. Use curl or wget with resume disabled to get a clean copy.

If the package is for the wrong hardware

1. Read the exact model and hardware revision from the sticker on the device.
2. Download the package matching that revision. Vendors often ship separate images per SoC.
3. Do not flash across revisions even if the web UI accepts the file.

Last resort: SD card reflash

If recovery fails and the device has an SD slot, most gateway and camera vendors publish a bootable SD image:

1. Write the vendor’s recovery image to a fresh SD card with Etcher or dd.
2. Insert the card, hold the recovery button, power on. The device flashes from SD.
3. Remove the card once the status LED goes solid.

Caution

A mid-flash failure on a device without a recovery partition and without an SD slot may require RMA. Do not attempt to desolder or reprogram the flash chip in the field.

Verify

1. The device boots to its normal status (solid LED, web UI responds).
2. The firmware version reported in the UI matches the intended build.
3. The device reports healthy in NovaVMS within 2 minutes.

If none of this worked

• Collect the pre-flash log from the vendor UI (or serial console dump).
• Photograph the hardware revision sticker and status LEDs.
• Open an RMA with the vendor if the device cannot return to recovery.
• See also: Gateway will not pair with the cloud.