Almost every failure on this board is fixed by an erase and a re-flash — the chip is very hard to permanently hurt. Find your symptom below, or read the lot before you start; it's a short list.
Find your symptom. Jump to the fix.
The four failures that cover ~95% of support mail — in the order they usually happen.
The flasher can't find my device
Almost always a charge-only USB-C cable — it has no data lines. Then, in order:
- Try a known-good data cable — one that has transferred files to a phone
- Plug directly into the computer — avoid hubs and docks
- Make sure you're in Chrome or Edge — Firefox, Safari and phones can't do USB serial
- On older Windows machines, install the CP210x driver from Silicon Labs
The chip keeps connecting and disconnecting every 1–2 seconds
That's a boot-loop — normal for a blank or broken flash, and the one-click flasher is built for it: it waits for the chip, forces it back into flash mode and keeps retrying for up to 90 seconds, hands-free.
Driving a manual tool instead? Hold BOOT + RST together ~2 seconds, release RST while holding BOOT, then release BOOT. When the onboard LED goes dark, reconnect.
Flashed fine — but the ZimaCube WiFi never appears
Wait first — the first boot after a full erase can take 60–90 seconds to start broadcasting. Then power-cycle the whole ZimaCube.
Still silent after two minutes? Reconnect USB, open the flasher and press Flash again — a clean erase-and-rewrite clears corrupted NVS and fixes it.
The dashboard won't load from my phone
Checklist, in order:
- Make sure you're actually on the
ZimaCubeWiFi — not your home network. Phones love to hop back. - Use http://zimacube.local or http://172.16.1.1 — not https
- Disable "smart WiFi" / auto-switch for this network — some phones leave WiFi with no internet
- Remember the first boot can take up to 90 seconds
Asked and answered.
Is flashing risky?
Small but real. A failed or interrupted flash can temporarily brick the ESP32 — which is almost always fixed by erasing and re-flashing. Thousands of people flash ESP32s daily; the tool is made by Espressif, the company that makes the chip. You can always go back to stock firmware. Nothing is permanent.
Do I need the cable at all?
Usually not. If your 7th Bay still boots its stock firmware (or Vantic), the WiFi route updates it from the device's own page at http://zimacube.local or http://172.16.1.1 — no cable, any browser, ~15 seconds. The USB cable is only for a blank/broken flash, or if the device never broadcasts its WiFi.
Does Vantic collect anything?
No. The chip has no route to the internet — it can't phone home even if it wanted to. No accounts, no telemetry, no ads. The dashboard lives entirely on your device, on your network.
The firmware is a community project, and the device's own pages make it easy to see exactly what it serves.
Can I flash more than one 7th Bay?
Yes — each module is flashed independently. Join each one's ZimaCube WiFi one at a time while flashing (they broadcast the same name), or use the USB route per module. Everything else works the same.
How do updates reach me once Vantic is installed?
Over the air. When a new version drops, grab the .bin from the flasher page (or the dashboard links to it) and upload it on the dashboard's Update Firmware tab — ~15 seconds, no cable, and your settings survive. You'll never need the USB cable again unless something goes truly sideways — in which case this page is waiting.
The flasher can't find my device
Almost always a charge-only USB-C cable — it has no data lines. Then, in order:
- Try a known-good data cable (one that has transferred files to a phone)
- Plug directly into the computer — avoid hubs and docks
- Make sure you're in Chrome or Edge — Firefox, Safari and phones can't do USB serial
- Older Windows machines may need the CP210x driver from Silicon Labs
The chip keeps connecting and disconnecting every 1–2 seconds
The chip is boot-looping — normal for a blank or broken flash. The one-click flasher deals with this itself: it waits for the chip, forces it back into flash mode and keeps retrying for up to 90 seconds. If you're using a manual tool instead, force bootloader mode: hold BOOT + RST together ~2 seconds, release RST while still holding BOOT, then release BOOT. When the onboard LED turns off, reconnect and it should hold steady.
Flashed successfully but the ZimaCube WiFi never appears
Wait first — the first boot after a full erase can take 60–90 seconds to start broadcasting. Then power-cycle the ZimaCube. If it's still silent after 2 minutes, reconnect the USB-C cable, open the flasher and press Flash again — a clean erase-and-rewrite clears corrupted NVS and fixes it.
The dashboard won't load from my phone
Checklist, in order:
- Make sure you're actually on the
ZimaCubeWiFi, not your home network - Use http://zimacube.local or http://172.16.1.1 — not https
- Some phones auto-leave WiFi with no internet — disable "smart WiFi" / auto-switch for this network
- First boot can take up to 90 seconds — be patient before assuming it's broken
How do I go back to the stock firmware?
One click. Connect the chip with the flasher, pick IceWhaleTech stock instead of Vantic, and press Flash — the stock images are included on the page. Prefer the original hands-on method? The full return-to-stock guide walks through the manual esptool-js process step by step. Vantic makes no permanent changes — ever.
Still stuck?
I answer personally — usually same day. Include what step you're on, the exact error, your OS and browser, and the cable you're using — that's 90% of the debugging already done.
Or start again from a clean slate.
The one-click flasher erases, writes and verifies in about five minutes — it recovers chips that look dead, and it can put the stock firmware back just as easily.