Cart

$0.00

November 11, 2026

MeshCore Firmware Update: Web Flasher vs OTA Without Bricking

How do you do a MeshCore firmware update without bricking your node? Use the web flasher over USB for any node you can hold in your hand, and save over-the-air (OTA) updates for repeaters you can't reach. Back up your settings first, and test a new release on a spare board before it goes on the roof.

The same rules work for Meshtastic, and we cover both below. Around Bryan–College Station, Brazos Valley Mesh runs MeshCore on the USA/Canada (Recommended) preset, and the hard part of updating isn't the flash itself. It's the trip up the ladder when a rooftop repeater doesn't come back. Everything here was checked against the MeshCore FAQ, the MeshCore blog, the Meshtastic flashing docs, and the Meshtastic Android firmware guide on Oct 29, 2026. Where the advice is ours and not the project's, we say so.

Quick answer

Node on your desk or in your pocket: plug it in over USB and use the MeshCore web flasher or the Meshtastic web flasher. This is the safest path, because if something goes wrong, the board is right there.

Repeater on a roof or mast: MeshCore can update it over the air. nRF52 boards like the RAK4631 and Heltec T114 update over Bluetooth from your phone, and ESP32 boards like the Heltec V3 update over a Wi-Fi hotspot the repeater creates.

Before any update: save your settings, read the release notes, and use a USB cable that carries data, not just power.

Before a rooftop update: run the new release on a spare node for a few days first. That's our rule, not the projects'.

Step 1: Back up before you flash

An update usually keeps your settings, but "usually" isn't a plan.

  • MeshCore companion: in the MeshCore app, open Settings (the gear icon) and use Export Settings, then Select All. The MeshCore FAQ uses this export before a factory reset, and it works just as well before an update.
  • MeshCore repeater or room server: write down its name, admin password, location, and radio settings. If you set it up from config.meshcore.io or the flasher console, you'll want those values again if it ever needs a clean install.
  • Meshtastic: the Meshtastic docs say a full reinstall on an ESP32 wipes the device, and that you can export your configuration with the Meshtastic command line tool first and load it back after. The Android app's own checklist also says to note your settings, because they may reset on major version changes.

Also update the phone app before or alongside the firmware. The Meshtastic Android guide lists this in its pre-update checklist, and MeshCore features like the 1.18 companion command line need a matching app version, as our MeshCore 1.18 update post explains.

Step 2: Read the release notes

Every release has notes, and they tell you whether there's a reason to rush. For MeshCore, the current release is 1.18.0, published Oct 15, 2026. For Meshtastic, the newest non-alpha release on GitHub is still 2.7.26, and the 2.8 builds are alphas. Our Meshtastic 2.8 update post walks through whether that one is worth it.

Pick the right file for your board and role. Meshtastic's docs warn that flashing the wrong board's firmware can look like it worked and still leave the device unresponsive, and on MeshCore a repeater build and a companion build do different jobs. If you're not sure which role a board should run, our repeater vs companion vs room server guide explains each one.

Step 3: Update over USB with the web flasher

This is the method both projects point new users to.

  1. Attach the antenna first. Meshtastic's flashing docs warn not to power a radio on without its antenna, because it can damage the radio chip.
  2. Use a desktop browser that supports it. Meshtastic's flasher needs Chrome or Edge. MeshCore's FAQ describes its flasher on a computer running Chrome.
  3. Plug in with a data cable. The Meshtastic docs call for a USB data cable. A charge-only cable carries power but no data, so the computer won't see the board.
  4. Pick your board, role, and version, and flash. On nRF52 boards, the Meshtastic docs also describe a drag-and-drop method: double-press the reset button, a USB drive appears, and you copy the `.uf2` file onto it.
  5. Don't unplug until it's done. The Meshtastic Android guide warns that interrupting an update can leave the node unable to boot.

MeshCore ESP32 boards and the two file types. If you download MeshCore firmware for an ESP32 board like the Heltec V3 instead of flashing in the browser, the MeshCore FAQ explains the difference. The non-merged `.bin` keeps the existing Bluetooth pairings. The merged `.bin` overwrites everything, including the bootloader and Bluetooth pairings, but keeps your configuration.

Step 4: Updating a repeater over the air (MeshCore)

OTA is what makes a rooftop repeater practical, and it's also where updates are most likely to fail. Meshtastic's own OTA page puts it plainly: OTA updates "come with an increased risk of failure," and a failed one can leave the device in a non-working state that needs physical access to fix.

nRF52 repeaters and room servers (RAK, Heltec T114, Seeed XIAO and others). These are the steps from the MeshCore FAQ and the MeshCore blog's OTA guide:

  1. On the MeshCore web flasher, pick your board and role, and download the .zip version of the firmware to your phone.
  2. Install Nordic's nRF Device Firmware Update app (search for "nrf dfu" in the app store).
  3. In the MeshCore app, log in to the repeater with admin rights, open the Command Line, and type `start ota`. You should see an `OK` reply.
  4. In the DFU app's settings, the MeshCore blog recommends turning Packet receipts notification on, setting Number of packets to 8 (the MeshCore FAQ suggests 10 for RAK boards; 8 works too), turning Disable resume on, and turning Force scanning on. (On Android, it also says to turn Request high MTU off.)
  5. Select the .zip, pick the repeater, and start the upload. The FAQ says it can take a few minutes.
  6. When it's done, log back in and run `ver` to confirm the new version. The blog also says to check the clock with `clock` and fix it with `clock sync` if it's wrong.

If it stalls, the MeshCore blog says to send `reboot` and try again. The FAQ adds that toggling Bluetooth, rebooting your phone, or forgetting and re-pairing the board can help.

ESP32 repeaters (Heltec V3 and similar). The MeshCore FAQ says to download the non-merged `.bin`, log in to the repeater with admin rights, and send `start ota`. The repeater then starts a Wi-Fi hotspot named MeshCore OTA. Join it from your phone or laptop, open `http://192.168.4.1/update` in a browser, and upload the file. You have to be within Wi-Fi range of the repeater for this, which on a tall mast can mean standing close to it.

Companions. The MeshCore FAQ says a companion must already be running companion firmware 1.15 or newer to update over the air. Since a companion is usually in your hand anyway, USB is the simpler choice.

Step 5: Install the OTAFIX bootloader before the repeater goes up

This is the single best thing you can do for an nRF52 repeater, and it has to happen on the bench, over USB.

The MeshCore FAQ "strongly" recommends the OTAFIX bootloader. According to the MeshCore blog, it falls back to OTA update mode if an update fails, so you can try again over the air instead of climbing up to fix it, and it makes OTA updates significantly faster. The MeshCore FAQ lists supported boards that include the RAK4631, Heltec T114, SenseCAP T1000-E, Wio Tracker L1, and Seeed XIAO nRF52840. Meshtastic now maintains its own version as the Meshtastic nRF52 Bootloader (formerly OTAFIX), and its docs say it makes Bluetooth OTA updates faster and more reliable.

To install it, the MeshCore blog says to pick your device and the Repeater role on the MeshCore web flasher, where a download link for the bootloader appears in a highlighted banner. Put the board in USB drive mode (on most nRF52 boards, double-press reset). On a Seeed XIAO nRF52840, open `INFO_UF2.TXT` on the drive first. If the Board-ID says Sense, use the SENSE version of the bootloader. Then copy the `update-xxxx.uf2` file onto the drive and let it reboot. To check it worked, put the board back in USB drive mode, open `INFO_UF2.TXT`, and look for OTAFIX in the version line.

One caution from the Meshtastic docs: bootloader files are board-specific, and the wrong one can brick a board, especially with command-line tools that don't check. Stick to the file the flasher or the bootloader's release page offers for your exact board.

Step 6: Updating Meshtastic over the air

The Meshtastic apps can update supported nodes themselves.

  • Android: connect to the node, open its settings, and under Advanced tap Firmware Update. The entry only appears for nodes that can take an over-the-air update. The guide covers Bluetooth OTA for supported radios, and an ESP32 connected over your network can take a Wi-Fi update instead. Its checklist recommends a battery above 50%.
  • iPhone and iPad: the Meshtastic docs say the app can update OTA-capable nodes from Settings, then Firmware Updates. They also note that iPhone auto-lock can interrupt a Bluetooth upload, so keep the screen awake.

If the app says a Bluetooth update couldn't be finished, the Android guide says to follow the instruction it gives: connect the radio to a computer over USB and re-flash it with the vendor's serial DFU tool. A stock nRF bootloader can't reliably finish an interrupted over-the-air update. Otherwise, the fix for a radio that won't boot is USB and the web flasher.

Step 7: Test on a spare first

This is our advice, not the projects', and it's the one that saves the most ladder trips. Flash the new release onto a spare node on your bench, run it alongside the rest of the mesh for a few days, then update the companions you carry, and update the high repeaters last. If something about the new release doesn't sit right with your setup, you'll find out on a board you can unplug.

A spare doesn't need to be fancy. The Heltec V4 at Rokland was $26.97 and in stock when we checked on Oct 29, 2026, and it runs either firmware. If your repeaters are RAK boards, a matching spare like the RAKwireless Mini Meshtastic starter kit at Rokland ($31.97, in stock on Oct 29) lets you rehearse the exact OTA steps first. Despite the name, the RAK4631 in that kit runs MeshCore too. Our first MeshCore node under $70 guide compares more beginner boards.

Step 8: Check it after the update

  • Version: on MeshCore, run `ver` on a repeater. On Meshtastic Android, check Currently Installed on the Firmware Update screen.
  • Radio settings: make sure the node is still on the USA/Canada preset for MeshCore, or the same preset as your Meshtastic mesh.
  • Clock: MeshCore repeaters can be set with `clock sync`.
  • A real message: send a test on Public, the way our first MeshCore message guide shows.

If a repeater stops showing up over Bluetooth after you set it up, that's normal for MeshCore repeaters. Our guide to managing a MeshCore repeater covers USB setup and remote login over LoRa.

If it won't boot

Don't panic. Most "bricked" nodes are just stuck in the bootloader.

  • nRF52 boards: double-press reset to get the USB drive back, then flash again. The Meshtastic docs note that stale data from older versions can cause a crash loop on nRF52 boards, and a factory erase fixes it. The Meshtastic web flasher can do that erase.
  • MeshCore boards you can't connect to: the MeshCore FAQ's fix is to open the web flasher, pick your device, use Enter DFU mode, then Erase Flash, then Flash!. You may have to remove the old Bluetooth pairing from your phone afterward.
  • MeshCore rescue mode: since firmware 1.7.0, boards with a user button (some RAK boards and the T114) can enter a command line rescue mode if you hold the button within 8 seconds of boot, according to the MeshCore FAQ. Then use the console on the web flasher.

Where Brazos Valley Mesh fits

Rooftop repeaters carry everyone's messages across Bryan–College Station, so a failed update there isn't just one person's problem. Our rooftop repeater write-up explains why those high sites matter. If you host a repeater with us and aren't comfortable doing an OTA update, reach out before you try. We'd rather walk through it together than lose the site for a weekend.

If you're still deciding which firmware to run in the first place, our MeshCore vs Meshtastic comparison explains why we chose MeshCore locally. The two don't talk to each other on the air, so pick one per node.

FAQ

How do I do a MeshCore firmware update safely?

Back up your settings, then update over USB with the MeshCore web flasher for any node you can reach. Use OTA only for repeaters you can't reach, and test a new release on a spare node first.

Can I update a MeshCore repeater over the air?

Yes. nRF52 repeaters update over Bluetooth with the nRF Device Firmware Update app after you send `start ota`. ESP32 repeaters start a MeshCore OTA Wi-Fi hotspot instead, and you upload the non-merged `.bin` at `http://192.168.4.1/update`.

What is the OTAFIX bootloader, and do I need it?

It's an improved bootloader for nRF52 boards. If an OTA update fails, it falls back to update mode so you can try again over the air. The MeshCore FAQ strongly recommends it, so install it before a repeater goes on the roof.

Will a firmware update erase my settings?

A normal update usually keeps them, but a full reinstall or factory erase does not. Export your MeshCore companion settings or your Meshtastic configuration first, because major Meshtastic versions may reset settings.

Which browser do I need for the web flasher?

Meshtastic's flasher needs Chrome or Edge on a computer. MeshCore's FAQ describes its flasher in Chrome.

My node won't boot after an update. Is it bricked?

Probably not. On nRF52 boards, double-press reset to get the USB drive back and flash again. MeshCore's flasher also has Enter DFU mode and Erase Flash buttons for a clean reinstall.

Getting on the Brazos Valley mesh

If you'd rather skip flashing entirely, our Pocket Mesh Node is a RAK19003 companion with an external 915 MHz antenna, flashed with MeshCore or Meshtastic, your choice. If you're joining us around Bryan–College Station, we recommend MeshCore. Buying gear anywhere is fine. Buying from the Brazos Valley Mesh shop funds the local mesh, since proceeds go into repeaters and rooftop work around the valley.

Related

Read next

More from the neighborhood, close to this subject.

MeshCore 1.18: Should You Update?

October 27, 2026

MeshCore 1.18 Update: Should You Upgrade Your Node Yet?

Should you install MeshCore 1.18? Update if your board got a fix or you want the companion CLI. Leave Remote CLI off; do rooftop repeaters last.

MeshCore vs Meshtastic

October 8, 2026

MeshCore vs Meshtastic: Which LoRa Mesh Should You Run?

Pick MeshCore if your town is building rooftop repeaters, or Meshtastic if your group roams with no fixed sites. Here is why we run MeshCore.

Node Not Showing Up?

October 19, 2026

Meshtastic Node Not Showing Up? Why You Can Still Send

No nodes in your Meshtastic or MeshCore list? You can still send. Here's what has to match for others to hear you, and why DMs need a key first.