FM1 UnbrickerUnbrick my FM-1
Unbrick my FM-1

Black screen? Your FM‑1 is almost certainly fixable.

When an FM-1 goes dark after an update, it's scary, but it is very rarely broken for good. Its chip has a that no update can erase. This guide explains what happened in plain words, then walks you through bringing it back, one step at a time. No programming knowledge needed.

  • Free and open source
  • Backs up everything first
  • Checks every byte it writes
Step back for a second

What's inside your FM‑1

Everything your FM-1 knows lives in a tiny memory chip, a bit like a notebook with four sections. Tap each section to see what it holds.

start of the memoryend (1 MB in total)
And one thing that is not in the notebook: the rescue mode. It's built into the chip itself when the chip is made, in permanent memory called . Nothing can change it, not an update, not a bad install, not this tool. When things go wrong, the rescue mode is still there, and that's how every fix on this page gets in. On a computer it shows up as a USB drive called WL82 UBOOT1.00.
How FM-1s get "bricked"

Why it breaks, and how the fix works

"Bricked" just means the FM-1 won't start, so it's as useful as a brick. There are three common ways it happens. Pick one and press play: each square is a small piece of the memory.

■ Bootloadertiny, but the FM-1 can't start without it
■ Firmwarethe program
■ Your stuffsettings, sounds, songs
    Which official firmware?

    V15, V16, and why it matters

    M-VAVE now ships V16 (October 2026) and no longer offers V15 for download. V16 is a big update, and it also arranges the memory differently. Most custom firmwares were built on top of V15.

    start of the memoryend (1 MB)

    Switch between the two and watch the colours move: V16's firmware is longer, and it keeps its settings, sequences, Bluetooth data and presets in different places than V15. Positions are approximate.

    To rescue a bricked FM‑1: use V15

    It's the version the rescue tool can fully check, it works with every route on this page (the Transporter included), and it's the base most custom firmwares expect.

    ⬇ Download V15

    From the FM1Backups repository (the Firmware Hub also keeps it). Wherever it comes from, the tool checks the file's and refuses anything that isn't the genuine V15.

    Want V16? Install it once it works

    Once your FM-1 starts again, update to V16 with M-VAVE's own updater, on a full battery. Or put V16 on directly with the Bootloader fix, which writes all of it, its own bootloader included.

    The normal USB fix and the Transporter refuse V16: they can only write as far as V15's firmware goes, and half a firmware would not start.

    Custom firmware? Check its base

    Most custom firmwares were made to be installed over V15. Installing one over V16, or going back and forth, can leave presets, sounds or fonts garbled: each firmware finds the others' leftovers, or finds its own data overwritten. See Garbled presets, sounds or fonts.

    Find my fix

    Answer a few questions, get your steps

    Three or four questions. If you're not sure about an answer, there's always an "I'm not sure" option.

    Step by step

    The guides

    Tick each step as you go: this page remembers where you were if you come back.

    USB fix: put the firmware back

    About 15 minutesNo extra partsWindows, Mac or Linux

    For an FM-1 with a black screen that shows up on the computer as WL82 UBOOT1.00. This is the most common fix.

    1. Get these ready

      • The FM-1, charged.
      • A USB cable that carries data. Some cables only charge; if nothing shows up later, try another cable.
      • A Windows 10 or 11 computer.
      • A Mac with macOS 11 or newer (Apple silicon or Intel), and your Mac password.
      • A Linux computer or a Raspberry Pi.
      • An internet connection (only for the setup).
    2. Install Python (free)

      Python is the program that runs the rescue tool. Download it from python.org/downloads and run the installer. On the first screen, tick "Add python.exe to PATH", then click Install Now.

    3. Check that Python is there

      Open the Terminal app (Applications → Utilities) and type:

      python3 --version

      Anything from Python 3.9 up is fine. If your Mac offers to install the "command line developer tools" instead, click Install, wait, and try again. Or install Python from python.org.

    4. Check that Python is there

      Most Linux systems and Raspberry Pi OS already have it. Open a terminal and type:

      python3 --version

      Anything from Python 3.9 up is fine.

    5. Download the rescue tool

      ⬇ Download the tool (ZIP)

      Open your Downloads folder, right-click MvaveFM1Unbricker-main.zip, choose Extract All…, then Extract. You now have a folder with a file called fm1_unbrick.py inside.

      Your Mac unzips it in Downloads by itself (if not, double-click it). You now have a folder MvaveFM1Unbricker-main with fm1_unbrick.py inside.

      Unzip it in your Downloads folder (double-click it, or unzip MvaveFM1Unbricker-main.zip). You now have a folder MvaveFM1Unbricker-main with fm1_unbrick.py inside.

    6. Get the official V15 firmware

      M-VAVE no longer offers V15, but a copy is kept here:

      ⬇ Download V15-FM-1.fwsc

      Move it into the same folder as fm1_unbrick.py. Keep its name, V15-FM-1.fwsc: the commands below use it (if your browser saved it as V15-FM-1 (1).fwsc, rename it).

      i

      The tool recognises the official V15 file by its and refuses a damaged or fake one, so it doesn't matter where you got it.

      !

      Only have V16 from M-VAVE's site? This fix refuses it on purpose: V16's firmware is longer than what this fix writes. Use V15 here and update to V16 afterwards, or use the Bootloader fix, which can write V16 completely. Why?

    7. Connect the FM‑1

      Switch the FM-1 on (the screen stays black, that's expected) and plug it straight into the computer, not through a USB hub or dock.

      !

      If Windows asks to format a disk, click Cancel. That "disk" is the FM-1's rescue mode. Never format it.

      !

      If your Mac says the disk is not readable, click Ignore, never Initialize. That "disk" is the FM-1's rescue mode.

    8. Open PowerShell as administrator

      Open a terminal

      Open Terminal

      Right-click the Start button and choose Terminal (Admin) or Windows PowerShell (Admin). Click Yes when Windows asks. "Admin" matters: the tool needs it to talk to the FM-1.

      Open the Terminal app. You'll type a few commands; the tool will ask for your password when it needs it.

      Open the Terminal app. You'll type a few commands; when one asks for your Password, type your Mac password (nothing shows while you type, that's normal) and press Enter.

      Then go into the tool's folder. Copy this, paste it in the window and press Enter:

      cd "$HOME\Downloads\MvaveFM1Unbricker-main\MvaveFM1Unbricker-main"
      cd ~/Downloads/MvaveFM1Unbricker-main
      cd ~/Downloads/MvaveFM1Unbricker-main
      i

      "Cannot find path"? Your folder is somewhere else. Open the folder that contains fm1_unbrick.py in File Explorer, click its address bar, copy it, and type cd ", paste, ", Enter.

      "No such file or directory"? Type cd (with a space), drag the folder that contains fm1_unbrick.py into the terminal window, and press Enter.

    9. Set up the tool (once)

      This downloads the helper that talks to the FM-1's chip. It takes a minute.

      py fm1_unbrick.py setup
      python3 -m venv .venv
      .venv/bin/python fm1_unbrick.py setup
      python3 -m venv .venv
      .venv/bin/python fm1_unbrick.py setup
    10. Run the fix

      py fm1_unbrick.py restore V15-FM-1.fwsc
      sudo modprobe sg
      sudo .venv/bin/python fm1_unbrick.py restore V15-FM-1.fwsc
      sudo .venv/bin/python fm1_unbrick.py restore V15-FM-1.fwsc
      !

      On a Mac, be quick. macOS lets the FM-1 slip out of rescue mode after about half a minute, so run this soon after plugging it in. If your FM-1 still starts a firmware (it isn't dark), this one line asks for your password first, then sends it into rescue mode and starts the fix at once:

      sudo -v && .venv/bin/python fm1_unbrick.py softkey --yes && sudo .venv/bin/python fm1_unbrick.py restore V15-FM-1.fwsc

      The tool checks it's talking to an FM-1, then reads the whole memory twice and saves a backup in the backups folder. Then it shows what it's about to do and asks you to confirm:

      What you'll see (shortened)Backup OK backups/fm1-recovery-…/full-flash-before.bin About to WRITE the FM-1 flash: package V15-FM-1.fwsc identity FM-1_015 = official M-VAVE V15 (sha256 verified) Type WRITE to continue (anything else cancels):

      Type WRITE in capitals and press Enter. It writes, then reads everything back to check it. Don't unplug anything while it works.

    11. Restart the FM‑1

      When it says Done:

      1. Unplug the USB cable.
      2. Switch the FM-1 off.
      3. Wait 5 seconds.
      4. Switch it on. 🎉

      Keep the backups folder. If you used a custom firmware (Felucca, ChoralRoot…), your songs and settings from before are in it.

      i

      Still black after a fix that said Done? Then the firmware wasn't the problem: the probably is. Go to the Bootloader fix.

    Bootloader fix: put everything back, bootloader included

    About 15 minutesNo extra partsWindows, Mac or Linux

    For an FM-1 whose (the "boot head") was replaced or damaged, for example after installing a different bootloader with M-Flasher, that now won't start. It must still show up as WL82 UBOOT1.00.

    It's also the way to put V16 on directly: it writes the whole firmware from the file, with that version's own bootloader.

    !

    This is the newest part of the tool (November 2026). It has been tested on simulated hardware and real memory dumps. Take the "look first" step below, and keep the backup it makes.

    1. Do steps 1 to 7 of the USB fix first

      Same preparation: Python, the tool, the firmware file V15-FM-1.fwsc, the FM-1 plugged in, the terminal open in the tool's folder, and setup done. Open the USB fix.

    2. Look first (changes nothing)

      This makes a backup and shows what would change, then stops:

      py fm1_unbrick.py full-restore V15-FM-1.fwsc --plan-only
      sudo .venv/bin/python fm1_unbrick.py full-restore V15-FM-1.fwsc --plan-only
      sudo .venv/bin/python fm1_unbrick.py full-restore V15-FM-1.fwsc --plan-only

      Look for the line about the bootloader ("boot head on the unit now"). If it says it's not the stock one, this fix is for you.

    3. Run the full fix

      py fm1_unbrick.py full-restore V15-FM-1.fwsc
      sudo .venv/bin/python fm1_unbrick.py full-restore V15-FM-1.fwsc
      sudo .venv/bin/python fm1_unbrick.py full-restore V15-FM-1.fwsc

      It puts back the stock bootloader and the stock firmware. Your settings and sounds stay as they are. Type FULL when asked. It writes the bootloader last and checks every byte.

      Using V16 instead? Download V16-FM-1.fwsc (or get it from M-VAVE), put it in the folder and use its name in place of V15-FM-1.fwsc. The tool recognises the genuine V16 and its bootloader by their fingerprints too.

      !

      Keep the FM-1 plugged in until it says Done. If it's interrupted while writing the bootloader, the FM-1 won't start until you run the same command again.

    4. Restart the FM‑1

      Unplug, switch off, wait 5 seconds, switch on.

    5. Got a full backup? You can use it instead

      If you have a full 1 MB backup of your FM-1 from before the problem (M-Flasher and this tool both make one), the fix can put back everything from it, factory sounds included:

      py fm1_unbrick.py full-restore --image my-backup.bin
      sudo .venv/bin/python fm1_unbrick.py full-restore --image my-backup.bin
      sudo .venv/bin/python fm1_unbrick.py full-restore --image my-backup.bin

      Replace my-backup.bin with your file's name. Your FM-1's own Bluetooth identity is kept unless you add --include-unit-data (only do that with a backup of this same FM-1).

      If the tool says the bootloader in your file "is not the stock V15 or V16 bootloader" and you know it's the right one (for example m-bootloader, from your own backup), add --other-head.

    Dark, no USB at all: the Transporter

    About an hour2 small parts, about $15Mac, Windows or Linux

    For an FM-1 that shows nothing on the computer, in any mode, with any cable. A tiny board (the FM-1 Transporter, by Leo Kuroshita) knocks on the chip's rescue mode from the outside. No soldering. It works with a Mac, Windows or Linux.

    i

    The Transporter puts the firmware back. It can't rewrite the : if that's your problem, see the Bootloader fix.

    1. Buy the two parts

      • Seeed Studio XIAO RP2040, with pins already soldered. It must be the RP2040, not the RP2350.
      • A USB-C to 4-pin "Dupont" pigtail: a USB-C plug with four loose wires (red, white, green, black).
      • A normal USB-C data cable for the board.

      Prefer photos of every step? Unbrick the FM1 for Dummies walks through this same route on Windows, with the similar RP2040-Zero board (its pins 0 and 1 take the place of D6 and D7).

      Charge the FM-1 fully: it runs on its battery during all of this.

    2. Get Python, the tool and the firmware

      On a Mac, Python 3 comes with Apple's command line tools: open Terminal and type python3 --version; if it offers to install the tools, accept. Or get it from python.org.

      Install Python from python.org/downloads (tick "Add python.exe to PATH").

      ⬇ Download the tool (ZIP) and unzip it. Put the official V15 firmware in the same folder: download V15-FM-1.fwsc. The wizard finds it by itself.

      It has to be V15: the Transporter can't write as far as V16's firmware goes. Update to V16 afterwards if you like.

    3. Set up (once)

      Open a terminal in the tool's folder (as in the USB fix) and run:

      python3 fm1_transporter_recover.py setup
      py fm1_transporter_recover.py setup

      It prepares the board's software and installs what it needs. No compiling.

    4. Start the wizard and follow it

      python3 fm1_transporter_recover.py wizard
      py fm1_transporter_recover.py wizard

      The wizard tells you when to plug in the board, how to wire it and when to switch the FM-1 on. Switch the FM-1 on only when it says so. The wiring is three wires:

      XIAO RP2040 its USB-C goes to the computer D6 D7 GND red: tape it off, not connected green = D+ white = D− black = GND USB-C plug into the FM-1

      D6 and D7 are the two pins farthest from the board's USB-C connector, one on each side. Swapping the green and white wires damages nothing: the FM-1 just isn't found, so swap them and try again.

    5. Confirm and let it work

      The wizard reads the whole memory twice and saves it, shows what it will change, and asks you to type WRITE. Then it rewrites only the damaged parts and checks every byte.

    6. Restart the FM‑1

      Switch the FM-1 off, remove the three wires, switch it on. It starts the official firmware. You can then install any other firmware the normal way, on a full battery.

    Garbled presets, sounds or fonts

    Try step 1 first: 1 minuteSteps 2 and 3 need a backup

    Your FM-1 starts, but preset names are garbage, sounds are wrong or out of tune, or the text on screen looks broken. It's not a brick. It usually happens after going from a custom firmware, or from V16, back to V15 (or the other way round). There are two causes:

    • Leftovers. The previous firmware left its own data in the settings area, and the new one reads it as its own settings.
    • Overwritten factory data. Some firmwares, and V16 itself, rewrite the area that holds the factory presets, sounds and fonts. Installing a firmware never puts that area back: only a backup can.
    1. Use the FM‑1's own reset

      On the FM-1, open System → Reset Patches. For many people that's all it takes.

    2. Have a backup from before? Put everything back

      The cleanest fix: if you (or M-Flasher, or this tool) made a full backup of this FM-1 while it was fine, restore it. That brings back the firmware it had then, its presets, sounds, fonts and settings, exactly. It's the Bootloader fix with your backup file:

      py fm1_unbrick.py full-restore --image my-backup.bin --include-unit-data

      Windows, in an administrator terminal; on a Mac or Linux use sudo .venv/bin/python instead of py. Only use --include-unit-data with a backup of this FM-1.

    3. No backup of your own? Use a factory one

      There's a full backup of a brand-new FM-1, read before anything was ever installed on it. Restoring it puts your FM-1 back the way it left the factory: its firmware, factory presets, sounds and fonts, and clean settings. Your own Bluetooth identity is kept.

      py fm1_unbrick.py full-restore --image fm1-transporter-dump-20261017-001153.bin

      It erases what's on the FM-1 now (songs, your own presets): the tool backs everything up first. This backup comes from an FM-1 with the older memory chip (see New chip & Firmware Lock).

    4. Settings leftovers only? Reset the settings area

      If presets are scrambled on V15 but sounds and fonts are fine, the tool can put just the settings area back to factory state. It needs a backup of a factory-fresh FM-1: use this factory settings file (from a new FM-1, read before anything was installed on it).

      With the FM-1 on its normal screen, this switches it into rescue mode (works on a Mac too):

      py fm1_unbrick.py softkey

      Then, in an administrator terminal (see the USB fix):

      py fm1_unbrick.py repair-settings --factory fm1-factory-settings-only.bin

      Type REPAIR when asked. It only touches the settings areas, and your backup keeps everything it removes. Then unplug, switch off, wait 5 seconds, switch on, and do System → Reset Patches once more.

      On a Mac or Linux, in Terminal, run it all in one go: sudo -v && .venv/bin/python fm1_unbrick.py softkey --yes && sudo .venv/bin/python fm1_unbrick.py repair-settings --factory fm1-factory-settings-only.bin

    New memory chip & Firmware Lock

    FM-1s sold from autumn 2026About 20 minutes

    FM-1s sold from autumn 2026 have a different memory chip than the first ones (a UCUN UC25HQ80, ID 0xB36014, instead of a Puya, ID 0x856014). Many firmwares written before it don't recognise it. Nothing is broken, but on a new FM-1 such a firmware can:

    • lose your saves when you switch off, or show a save error;
    • refuse updates, so its installer can't replace it and you're stuck on it. People call this Firmware Lock.

    The rescue mode is in the chip itself and works the same on both, and this tool supports both chips. So a locked FM-1 can always be brought back.

    1. Which chip does yours have?

      Units sold from autumn 2026 usually have the new one; those are the units with the M-VAVE logo on the front. To be sure:

      • M-Flasher shows it under Device info: 0xB36014 (new) or 0x856014 (old).
      • Or, with the FM-1 in rescue mode (step 2), this tool's py fm1_unbrick.py info prints Flash ID.
    2. Stuck? Get into rescue mode

      The locked firmware won't let installers in, so go around it. Try these in order:

      • From the browser, nothing to install: on the Firmware Hub's Rescue box, in Chrome or Edge, use step 1, "Send the FM-1 to its bootloader".
      • With this tool (any computer, Mac included), the FM-1 running and plugged in: py fm1_unbrick.py softkey (on a Mac or Linux: python3 fm1_unbrick.py softkey, after setup).
      • With M-Flasher: its DOWNLOAD MODE button.
      • From the keys: many Felucca-based firmwares (Felucca, SLOOP…) go there if you hold OCT− and OCT+ for 5 seconds. Others have their own combination: check the firmware's page.
      • Nothing works, or nothing shows up on USB: the Transporter always gets in.

      It worked if a drive called WL82 UBOOT1.00 appears (Windows may offer to format it: Cancel; a Mac says it's unreadable: Ignore). The screen may stay as it was. That's normal.

    3. Put the official firmware back

      Now follow the USB fix from its step 1, with V15. It works on Windows, Mac and Linux. On a Mac, start the fix within about half a minute of the FM-1 entering rescue mode: the USB fix has a one-line command for that.

    4. Next time: check before you install

      • On a new-chip FM-1, only install firmware that supports it: the Firmware Hub has a "Saves on newer FM-1s" filter.
      • Back up the whole memory first (M-Flasher's backup, or this tool's backup command in rescue mode). With a backup, nothing is ever lost.

    Prefer reading it all in one place? The technical details are in the README. There's also a community guide, FM1 Unbricking For Dummies.

    Trying custom firmware

    180 firmwares, one FM‑1: try them safely

    The Firmware Hub lists around 180 firmwares for the FM-1, made by different people. Each one can arrange the memory its own way, keep its data in different places, and support the new memory chip or not. Most were built to be installed over V15.

    Try before you flash

    RemoteFM1: try firmwares without installing them

    The safest install is the one you don't do. RemoteFM1 is a firmware you put on your FM-1 once. After that, the firmwares themselves run on your computer, phone or tablet, and your FM-1 becomes their keyboard, knobs and screen. Switching firmware is a click, not a flash, so there's nothing to brick and nothing left behind in your FM-1's memory.

    • Install it once with its web installer (Chrome or Edge, USB). Back up first, as with any install.
    • Pick a firmware at remotefm1.com (about 160 of them) and choose Play on my FM-1. There are also apps for iPhone, iPad and Android, and a Mac plugin. The sound plays on that device.
    • No FM-1 handy? Most firmwares also play right on the page, with your keyboard, mouse or a MIDI keyboard.
    • On its own, RemoteFM1 is still an instrument: a DX7-style synth, a MIDI controller and a looper.

    Found one you love? Then install that firmware for real, using the habits below. M-VAVE's own firmware can't run this way; to go back to it, install V15 or V16 as usual.

    When you do install a firmware for real, a few habits make it safe:

    💾

    Back up first, every time

    A full backup (M-Flasher, or this tool's backup) is the one thing that can put everything back: firmware, presets, sounds, fonts and songs.

    🧩

    Check new-chip support

    On an FM-1 from autumn 2026, pick firmware marked "Saves on newer FM-1s", or you may lose saves or get locked in.

    🔋

    Full battery, good cable

    Most bricks are installs that got cut off. Charge fully, plug straight into the computer, keep it awake, and don't touch anything until it says it's finished.

    ↩️

    Know your way back

    From a working FM-1: the hub's "Back to official V15" button. From a stuck one: this site's fix finder. To get your exact old setup back: your backup.

    🎛️

    Expect leftovers

    Switching between firmwares (or between V15 and V16) can leave presets, sounds or fonts garbled. That's fixable: see Garbled presets & sounds.

    📖

    Read its page

    Each firmware has its own way into its update mode, its own key combinations, and sometimes its own notes about going back. A minute of reading saves an evening.

    Is it safe?

    What the tool does to protect your FM‑1

    It was written to be careful first. Here's what happens before, during and after it changes anything.

    🔍

    Checks it's an FM‑1

    It reads the chip's ID and stops if it doesn't match an FM-1 exactly.

    💾

    Backs up everything, twice

    It reads the whole memory two times, compares the two, and saves a backup before writing anything. If the two reads differ, it stops: that means the cable is unreliable.

    🧾

    Checks the firmware file

    It recognises the official file by its fingerprint and refuses one that's damaged or isn't what it claims to be.

    ✍️

    Asks before writing

    It shows exactly what it will change and waits for you to type a word like WRITE. Anything else cancels.

    🎯

    Touches only what's needed

    The normal fix never touches the bootloader or your settings. Every change goes through one safety check in the code.

    ✅

    Checks every byte

    After writing, it reads everything back and compares. If something's off, it tries once more, then tells you clearly what to do.

    !

    The one golden rule: if the tool ever says "Do NOT power off", leave the FM-1 switched on and plugged in, and run the same command again (another cable or USB port helps). The FM-1 stays in rescue mode as long as it's on.

    Questions

    Common questions

    Do I need to know programming?

    No. You'll copy and paste a few commands, exactly as shown, and type one word to confirm. The tool does the rest and tells you what's happening.

    Could this make things worse?

    It's designed not to. It makes a full backup first, checks that it's an FM-1, checks the firmware file, and verifies everything it writes. The rescue mode itself can't be damaged by any of this, so you can always try again.

    Will I lose my songs and settings?

    The normal fix only rewrites the firmware, not your settings. And the backup it makes before writing holds everything, songs and sounds included. Keep the backups folder. (If you used Felucca or ChoralRoot, the official firmware may later overwrite the area where they kept projects: they're still in the backup.)

    Is this made by M-VAVE?

    No. It's an unofficial, free, open-source community project, built on the recovery steps people worked out on r/MVaveFM1. Use it at your own risk.

    Does it work on a Mac?

    Yes, since November 2026. On a Mac the tool needs your password (sudo), because only an administrator can take the FM-1 away from macOS's disk driver. M-Flasher needs the same. Start the fix soon after the FM-1 enters rescue mode: macOS lets it slip back out after about half a minute. The USB fix has a one-line command that handles that.

    Windows asked me to format a disk. What do I do?

    Click Cancel. That "disk" is the FM-1's rescue mode. Never format it.

    The tool says "the two backup reads DIFFER"

    Nothing was written. The USB connection isn't reliable: use another data cable, another USB port, and plug the FM-1 straight into the computer, not into a hub.

    The tool says the firmware is "already" there, but it's still black

    Then the firmware isn't the problem. The usual causes are the (see the Bootloader fix) or leftovers from a custom firmware. Ask in the community and attach the folder from backups.

    Which firmware should I put on it?

    To rescue it: the official V15 (download). Once the FM-1 works again, install whatever you like the normal way (V16 from M-VAVE, or a custom firmware), on a full battery, with the computer kept awake.

    Why V15 and not V16?

    V16 is newer, but its firmware is longer and the memory is arranged differently. The normal USB fix and the Transporter can only write as far as V15's firmware goes, so they refuse V16 rather than write half of it. The Bootloader fix can write V16 completely. And most custom firmwares expect V15 underneath. More on V15 and V16.

    Where do I get V15 now that M-VAVE only offers V16?

    From the FM1Backups repository (direct download) or the Firmware Hub. The tool checks its fingerprint, so a damaged or fake file is refused.

    Can I try custom firmwares without installing each one?

    Yes: install RemoteFM1 once, then run firmwares from remotefm1.com or its apps with your FM-1 as the panel. Switching is a click. See Trying custom firmware.

    My FM-1 is new and saves disappear, or I can't install anything else

    That's the new memory chip with a firmware that doesn't know it: see New chip & Firmware Lock.

    How do I avoid this next time?

    Most bricks come from an update that was cut off. Before updating: charge the FM-1 fully, use a good data cable straight into the computer, stop the computer from going to sleep, and don't touch anything until the update says it's finished.