韌體更新

保持 Meshtastic 無線電裝置的韌體為最新版本，以取得新功能、錯誤修正與安全性改善。

檢查更新

Open the connected radio’s configuration and, under Advanced, tap Firmware Update. The entry appears only for OTA-capable radios.
應用程式將檢查可用的韌體版本。
如有可用更新將顯示版本號碼與更新記錄摘要。

更新方式

OTA（無線空中下載）透過藍牙

Android 使用者最常用的更新方式：

⚠️ Warning: Interrupting a firmware update can leave the radio unable to boot. Keep the phone nearby and both devices powered until the update completes.

請確認您的無線電裝置已透過藍牙連線。
前往韌體更新畫面。
選取所需的韌體版本。
Tap Update. An Update Warning dialog lists the pre-flight checks — read it, then tap I know what I’m doing. to start. This dialog appears for every update method, including Wi-Fi OTA, USB, and a local firmware file.
請等待更新完成 — 更新期間請勿中斷連線。

While the update downloads, uploads or verifies, you can tap Play Chirpy Hop to play a short runner game: tap to jump, swipe down to crouch. The update’s progress stays visible above the game, and back returns to the update screen. When the update finishes or fails, the game stops and offers Back to update. Your best score is kept on this device.

Firmware checking for updates

Erase device during update

Where the app offers it, an Erase device during update checkbox appears next to the update button. It is a per-update opt-in and is never remembered.

Method	What erasing does
BLE / Wi-Fi OTA	Factory-resets the device once the update is verified. All settings and Bluetooth pairing are removed.
USB	Wipes the device’s flash completely, then installs the selected firmware from scratch.

It is not offered for a local firmware file, during a recovery update, on USB devices whose board does not support the erase step, or over USB in the desktop app — the USB erase runs the Android-only maintenance sequence below. Afterwards the device needs setting up — and pairing — again.

OTA via Wi-Fi (network-connected ESP32)

When an ESP32 radio is connected over the network rather than Bluetooth, the app offers Wi-Fi OTA, which pushes the same update over TCP:

Connect to the radio over the network (see Connections).
Open the Firmware Update screen and pick a version.
Tap Update. Keep the radio and phone on the same network for the whole transfer.

Wi-Fi OTA takes the ESP32 -update.bin image rather than the .uf2 a USB update uses; the app selects the right artifact for you.

In-App USB Update

When your radio is connected over USB/serial (rather than Bluetooth), the Firmware Update screen offers USB File Transfer. The app reboots the device into DFU mode, then prompts you to save the .uf2 file to the device’s DFU drive using the system file picker. This option appears only on a USB/serial connection — it is not available over Bluetooth.

ℹ️ Note: A vendor nRF bootloader supplied as a .zip (e.g. RAK WisBlock RAK4631) has to be flashed with a serial DFU tool such as adafruit-nrfutil — copying that .zip to the drive won’t work. A bootloader supplied as an update-....uf2 can be installed by copying it to the drive; that is how the app’s own bootloader upgrade works. The app surfaces a hint when the serial-only route applies.

Factory Erase and Bootloader Upgrade

On a USB/serial connection, nRF52 and RP2040 devices can be wiped as part of an update — that is the Erase device during update opt-in described earlier on this page. nRF52 devices additionally offer Upgrade bootloader where an upgraded bootloader is published for the board; RP2040 devices run no Adafruit bootloader, so they never see it.

Both are Android-only. They depend on Android’s update-drive checks, so the desktop app does not show them — use the Web Flasher there instead.

Select a firmware version before either one: the app hides both until a release is chosen, because the firmware is reinstalled after the device is wiped or the new bootloader is written.

Both a USB erase and a bootloader upgrade write two files in turn, so you are asked to select the device’s update drive twice: once for the erase or bootloader image, then again for the firmware.

The app reads INFO_UF2.TXT from the drive you select to confirm it really is the device’s update drive and to identify the board before writing anything.

For a bootloader upgrade, the app also reads the installed bootloader version from INFO_UF2.TXT and shows it next to the latest release before writing anything. The running firmware doesn’t report its bootloader, so the installed version appears only once the device has restarted into update mode, never on the firmware screen while connected. If the two match, the bootloader is left as it is and the app moves straight on to reinstalling the firmware. Otherwise choose Upgrade bootloader to write it, or Skip to reinstall the firmware without changing it.

On nRF52 the app must already know which Bluetooth stack your device uses before it starts, because it can’t read the bootloader until the device has rebooted. If it can’t confirm the stack, it refuses to erase and points you at the Web Flasher instead. In the Web Flasher, choosing the wrong Bluetooth stack can leave the radio recoverable only with a hardware programmer.

Once the drive is readable, how an nRF52 device is erased depends on its bootloader:

Newer bootloaders erase themselves. A bootloader that advertises factory-erase support in INFO_UF2.TXT (newer OTAFIX bootloaders) takes a single, board-agnostic erase file. The bootloader wipes your settings, channels, keys and the stored node list itself, leaves the installed firmware in place, and comes back as an update drive a second or two later for the firmware file. There is no Bluetooth-stack choice to get wrong on this path.
Older bootloaders need a Bluetooth-stack-specific erase. On these the app writes a small erase program matched to your device’s Bluetooth stack, then starts it over the serial port. If the drive reports a different stack than expected, the app refuses rather than guessing.

The app picks the path from what the drive reports; you don’t choose it.

Other Flashing Options

For recovery or when neither OTA nor in-app USB is available:

請使用〔Meshtastic 網頁燒錄工具〕(https://flasher.meshtastic.org)
或在桌面版使用〔Meshtastic CLI 工具〕(https://meshtastic.org/docs/getting-started/flashing-firmware)

版本頻道

頻道	描述說明
穩定版	建議大多數使用者採用；已測試的正式版本
Alpha 測試版	預覽版本；可能包含錯誤
本機檔案	Flash a firmware file you select yourself, instead of a downloaded release

更新前檢查清單

更新前請確認：

電量 > 50%
藍牙連線穩定
記錄目前的設定（主要版本更新時可能會重設）
查看版本說明中是否有重大變更
Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility

更新後

After the firmware is written, the app verifies the update and waits for the device to come back online:

Verifying update and waiting for the device to reconnect

Once the update succeeds:

The radio reboots automatically
The Bluetooth connection re-establishes
確認您的設定完整無缺
Confirm the new version under Currently Installed on the Firmware Update screen — it’s also shown on the node’s detail page and the Connections screen

Firmware update success

故障排除

更新卡住

若更新似乎停滯不動：

Give it a minute. After writing the image the app waits up to 60 seconds for the radio to come back and report its new version, so a pause at the verify step is expected.
If it is still stuck after that, power-cycle the radio.
Attempt the update again.

The message Verification timed out. Device did not reconnect in time. means the image was written but the radio did not come back within that window — power-cycle it and check the version under Currently Installed before re-running the update.

Firmware update error

Radio Won’t Boot After Update

If the app told you the Bluetooth update could not be finished, follow the instruction it gave: connect the radio to a computer over USB and re-flash it with the vendor’s serial DFU tool, such as adafruit-nrfutil. A stock nRF bootloader cannot reliably complete an interrupted over-the-air update.

Otherwise, if your radio fails to boot:

請嘗試透過 USB 連接至電腦
在復原／DFU 模式下使用網頁燒錄工具
燒錄已知可正常運作的韌體版本
前往 Meshtastic Discord 查詢特定裝置的復原步驟

相容性警告

On connecting, the app compares the radio’s firmware against two thresholds and reacts differently to each:

韌體版本	What you see	What happens
Below 2.3.15	Firmware update required.	The app disconnects from the radio. It does not operate against firmware this old.
2.3.15 up to, but not including, 2.5.14	Firmware Update Recommended.	Advisory only — dismiss it and carry on. The dialog names the latest stable release.
2.5.14 or newer	Nothing	—

A version string the app cannot parse is ignored rather than treated as too old, so a transient read never disconnects a working radio.