Recovery

Get your M-VAVE FM-1 back to stock

Start at the first step and only move down when it does not work. If a write was interrupted while the unit was writing its firmware, you may need steps 3 or 4.

  1. Step 1: Run the updater again

    If the unit still shows its update screen, the loader is intact. Reconnect the USB data cable and run the same installer again from the start. Do not unplug the unit while a write is in progress.

  2. Step 2: Use the firmware's own rescue

    Some firmwares document a key combination held at power-on. SLOOP and the firmwares built on it (sloopDX, zp12, FM-1 Doom) start in USB rescue when you hold OCT− alone while switching on. Groove OS boots stock firmware until the next power-on when you hold OCT− and OCT+. Check the listing's rescue line before you install.

    • SLOOP: Hold OCT− alone while switching on to start in USB rescue.
    • sloopDX: Hold OCT− alone while switching on to start in USB rescue.
    • zp12: Hold OCT− alone while switching on to start in USB rescue.
    • Groove OS: Hold OCT− and OCT+ while switching on to boot stock firmware until the next power-on.
    • FM-1 Doom: Hold OCT− alone while switching on to start in USB rescue.

  3. Step 3: Restore stock firmware

    Download V15 from M-VAVE yourself and install it with M-VAVE's M-UPGRADE tool. Several authors' installers can also put V15 back. Maru never hosts or redistributes M-VAVE firmware.

  4. Step 4: ROM recovery with a dongle

    If the unit no longer reaches its updater, the chip's ROM boot mode can still read and rewrite the flash through a small USB dongle. This needs some hardware skill. The community tools below do it; Maru hosts none of them.

  5. Step 5: Ask for help

    Write down which firmware and version you installed, which step it stopped in and what the screen shows, then ask the firmware's author through their repository or page. Leave out personal data.

What is known and unknown

The M-VAVE FM-1 has no recovery button and keeps one firmware at a time. No safe behaviour after an interrupted write has been shown, so treat an interrupted install as possibly needing ROM recovery. Maru has not yet run a recovery on its own unit; this ladder collects what authors and the community document.