"Flashing your device from the browser: a calm guide for first-timers"
Flashing your device from the browser: a calm guide for first-timers
If you've just ordered a Heltec V3 node or a StealthDeck and someone told you to "flash it from your browser", you may be picturing something involving cables, terminals, and a real chance of turning your new gadget into a paperweight. The reality is friendlier. Flashing just means writing the device's software into its memory — like installing an operating system, except it takes about ninety seconds and there's an installer that does the thinking for you.
This page walks through exactly what happens, using our flasher at /flash, in order.
What you need
Three things, no more:
- Your device and its USB-C cable. Here's the first trap, and it claims more victims than any software problem: many USB-C cables are charge-only. They carry power but no data. If your computer shows no sign of noticing the board, swap cables before you doubt yourself or the device. The cable that came in the box with your phone usually works.
- A computer or Android phone running the right browser. The flasher needs a browser feature called Web Serial — a way for a web page to talk directly to a device plugged into USB. That means Chrome, Edge or Opera on desktop, or Chrome 148 or newer on Android. That's the whole list, one line, as promised.
- About two minutes and a table you can put things on.
If you're on Firefox, Safari or an iPhone, those browsers simply don't offer Web Serial — no error on your part, it's just not in them. The flash page will tell you so, and you have an escape hatch: the same page offers plain .bin downloads (the firmware files themselves) that you can install with a small command-line tool called esptool. That path is fiddlier and we won't pretend otherwise, but the files are identical. And whichever way the firmware got onto the chip, you can check it afterwards on our firmware verification page.
A word before you start: what "bricking" actually means
The nightmare scenario, "bricking", is permanently breaking the device so no software can ever reach it again. It's vanishingly rare with these boards, and here's why: the ESP32 chip at the heart of your device has a small built-in installer of its own, burned in at the factory, that flash tools use to talk to it. Flashing new software cannot overwrite that built-in installer. Worst realistic case is that you flash the wrong firmware, it doesn't boot, and you flash a different one. The device has opinions but no memory of the failure.
So: you're not defusing anything. You're plugging in a board and letting a web page copy a file onto it.
Step by step
1. Open the flash page and find your device
Go to /flash. You'll see a compatibility matrix — devices down the side, firmware options across the top. Find the row for your board (Heltec V3, Cardputer, StealthDeck Lite or Pro, or the ESP32 starter kit) and the column for the software you want — Meshtastic for a mesh node, for instance. Cells marked "Flash now" have an installer behind them. Cells marked "—" mean the upstream project doesn't publish a build for that exact board, and we don't fake one — we'd rather show you a dash than a button that writes something wrong.
If your browser can't flash, the page tells you at the top and the manual .bin links sit next to the buttons for that reason.
2. Plug in the board and click Connect
With the device plugged into USB, click the install button (or Connect). Your browser will pop up a small chooser listing the serial ports it can see — that's the browser's security doing its job, asking you which device on your desk it may talk to. Pick the new one. It usually has a name mentioning USB or serial. If the list is empty, that's almost always the charge-only cable from earlier, or a board that needs its help button held down (more on that below).
The browser will also ask you to confirm permission for the site to open that port. Permission is per-device, per-site, and you can revoke it any time.
3. Let it install
Now the installer takes over. It puts the chip into its special download mode, writes the firmware, and checks what it wrote against what it meant to write — the same verification a professional tool does, just running in your browser. You'll see a progress bar. It runs in the neighbourhood of a minute or two. Resist the urge to unplug the device mid-install; pulling the cable while it writes is the one genuinely bad thing you can do here, and even that usually just means running the installer again.
One honest note from the flash page itself: if your board is second-hand and had other software on it, tick "erase device" in the installer so leftovers from the old firmware don't confuse the new one. For a fresh purchase straight from us, you don't need it.
4. Unplug, replug, done
When the installer says it's finished, unplug the board and plug it back in — or press its reset button if it has one. This hard reset is what makes the new software start fresh rather than continuing in whatever half-state it woke up in. The device should boot into its new firmware: a Meshtastic node shows its name on a screen or advertises over Bluetooth, a StealthDeck shows its menu.
If nothing happens, don't panic — nothing is damaged. Hold the BOOT button (the small button labelled BOOT or G0 on the board) while pressing reset, then try the installer again. That forcibly puts the chip into download mode. It's the single most common fix, and after a successful flash you'll rarely need it again.
What's happening under the bonnet (one paragraph, skippable)
Everything the flasher needs — the installer code and the firmware files — is served from stealthoz.tech itself. Nothing is fetched from a third-party server, and nothing about your device is sent anywhere: the browser talks straight to the board over that USB cable, locally, on your machine. We're not watching, and there's no account involved. The firmware binaries are the same ones the upstream projects publish; we host our own copies so the flasher works even if someone else's server has a bad day. If you like knowing the hash of what's on your chip, that's what our firmware verification page and the build pipeline behind it are for.
Flashing again later
The same page is not a one-trick pony. Firmware updates for these projects come out regularly, and the routine never changes: plug in, click, wait, replug. You can also swap a device between firmware entirely — say, trying MeshCore on a Heltec V3 that started life on Meshtastic. The flasher writes whatever you choose and the old software is simply replaced. It's one of the quiet pleasures of this hardware: the device you bought is closer to a blank canvas than a sealed appliance.
Quick troubleshooting
- Browser says no Web Serial — switch to Chrome, Edge or Opera (desktop) or Chrome 148+ on Android, or use the manual
.binroute described above. - Port picker is empty or the board is invisible — try a different USB-C cable (charge-only cables are the usual culprit), a different USB socket, and check the board's power light.
- Install fails partway — hold BOOT while pressing reset, then run the installer again.
- Flashed but nothing on screen — unplug and replug once more; if it's still quiet, hold BOOT during the next attempt. Failing firmware boots are annoying but fixable by flashing again.
- Still stuck — contact us through the store. We test every unit before it ships, and we'd rather help than have you staring at a dark board.
That's the whole ceremony. Cable that carries data, browser that speaks serial, one click, one replug. Your device was built to be flashed — that's what makes it yours.