Meshtastic-Android/docs/et-rEE/user/firmware.md

title, parent, nav_order, last_updated, description, aliases

title	parent	nav_order	last_updated	description	aliases
Püsivara värskendus	Kasutusjuhend	13	2026-09-06	Raadio püsivara uuendamine sinihamba ​​või USB kaudu – OTA protsess, versioonikanalid, lennueelsed kontrollid ja taastamine.	püsivara värskendus ota püsivarauuendus

Püsivara värskendus

Hoia oma Meshtastic raadio ajakohasena uusima püsivaraga, et saada uusi funktsioone, veaparandusi ja turvalisuse täiustusi.

Kontrollin värskendust

1. Ava ühendatud raadio konfiguratsioon ja puuduta jaotises Täpsemalt valikut Püsivara värskendus. The entry appears only for OTA-capable radios.
2. Rakendus kontrollib saadaolevaid püsivara versioone.
3. Saadaval olevad värskendused näitavad versiooninumbrit ja muudatuste logi kokkuvõtet.

Värskendamise meetod

OTA (Over-The-Air) sinihamba abil

Kõige levinum värskendamisviis Androidi kasutajate seas:

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

1. Veendu, et raadio on sinihamba ​​kaudu ühendatud.
2. Mine püsivara värskenduse lehele.
3. Vali soovitud püsivara versioon.
4. 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.
5. Oota, kuni värskendus on lõppenud – ära katkesta ühendust värskenduse ajal.

Tühjendada seade uuendamise käigus

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	Puhastab seadme välkmälu täielikult ja paigaldab seejärel valitud püsivara nullist.

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:

1. Connect to the radio over the network (see Connections).
2. Open the Firmware Update screen and pick a version.
3. 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.

Rakendusesisene USB värskendus

Kui raadio on ühendatud USB/jadaühenduse (mitte sinihamba) kaudu, pakub püsivara värskendamise ekraan USB failiedastust. Rakendus taaskäivitab seadme DFU-režiimis ja seejärel palub süsteemifailide valija abil salvestada .uf2-fail seadme DFU kettale. See valik kuvatakse ainult USB/jadaühenduse korral – see pole sinihamba ​​kaudu saadaval.

ℹ️ 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. Failina pakutavat alglaadur update-....uf2 saab installida selle kettale kopeerimise teel; nii töötabki rakenduse enda alglaaduri uuendamine. 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.

Rakendus loeb valitud kettalt faili INFO_UF2.TXT, et veenduda, kas see on tõepoolest seadme uuendusketas ja enne millegi kirjutamist plaat tuvastada.

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.

Muud püsivarauuenduse valikud

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

• Kasuta Meshtastic Web Flasherit
• Või arvutil Meshtastic CLI tööriist

Versioonikanalid

Kanal	Kirjeldus
Stabiilne	Soovitatav enamusele kasutajatele; testitud versioonid
Alfa	Eelvaateversioonid; võivad sisaldada vigu
Lokaalne	Püsivarauuenda ise valitud püsivara failga, allalaetud versiooni asemel

Eelvärskenduse kontrollnimekiri

Enne uuendamist:

• Aku > 50%
• Stabiilne sinihamba ühendus
• Pane tähele oma praeguseid seadeid (need võivad oluliste versioonimuudatuste korral lähtestuda)
• Check the release notes for breaking changes
• Update the Meshtastic app itself, before or alongside firmware updates, to ensure compatibility

Eelvärskendus

Pärast püsivara kirjutamist kontrollib rakendus värskendust ja ootab, kuni seade taas võrku lülitub:

Kui värskendus õnnestub:

• The radio reboots automatically
• The Bluetooth connection re-establishes
• Veendu, et seaded on puutumatud
• Kontrolli uut versiooni püsivara värskenduse ekraanil jaotises Praegu paigaldatud – see kuvatakse ka sõlme üksikasjade lehel ja ühenduste ekraanil

Veaotsing

Värskendus on ummikus

Kui värskendus näib olevat hangunud:

• 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.

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:

1. Try connecting via USB to a computer
2. Kasuta veebi püsivarauuendust taaste/DFU režiimis
3. Püsivarauuenda teadaolevalt toimiva püsivara versiooniga
4. Seadmepõhiste taastamissammude kohta vaata Meshtastic Discordist

Compatibility Warnings

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

Püsivara versioon	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.

Seotud teemad

• Ühendused — ühenduse loomine pärast püsivara värskendamist
• Püsivara uuendamise juhend — täielik püsivara uuendamise juhend meshtastic.org lehel
• Toetatud seadmed — ühilduvate raadiote täielik loetelu on leitav aadressilt meshtastic.org
• KKK — meshtastic.org sageli esitatavad küsimused