Before you flash
Custom firmware can turn a device into a different instrument. It is usually written by independent developers, comes without a warranty and may void yours.
What to check first
- 1
Save your work first
Back up projects, samples and patches to a computer. New firmware can reset or rewrite what is stored on the device.
- 2
Find the way back
Check how to return to the stock firmware before you start, and keep a copy of the official file if the maker offers one.
- 3
Match your exact hardware
Firmware is written for a specific model, and sometimes a specific hardware revision or stock version. A close match isn't enough.
- 4
Read the known issues
Look at the project's open issues and latest release notes. They tell you what is broken today.
- 5
Don't interrupt an install
Use a reliable USB cable, keep the device powered, and leave it alone until the installer says it has finished.
- 6
Avoid the night before a gig
New firmware can be unstable. Try it when you have time to fix things.
What you'll find on Overdub
- Firmware
- Replaces the software your device runs, so it behaves like a different instrument.
- Mods
- Adds features to the stock software, usually by patching it or running beside it.
- Tools
- Runs on your computer or phone: editors, emulators, installers and sample managers.
- Dev kits
- A starting point for people who write their own firmware.
- Research
- Notes and reverse engineering. Useful to developers, not something you install.
How to read a project page
Details like the install method and “way back to stock” are read automatically from each project's README. They can be wrong or out of date, so treat them as a starting point and confirm them in the project's own instructions. Stars show how many people noticed a project, not whether it is safe.
Free to download isn't the same as free to use
A project being public doesn't mean you can do anything you like with it. A licence sets out what's allowed, and this matters most if you plan to share a project, build on it, sell it or use it commercially.
- Open source licences
- Licences like MIT and GPL let people use, change and share a project, with conditions. You usually have to keep the author's credit, and the GPL requires you to share your changes if you pass on a modified version.
- Custom terms
- Some authors write their own rules, and these can be stricter. They may ban commercial use, selling or changes, or only allow personal use. We show this notice whenever we can't identify a standard licence, so read the actual terms.
- No licence found
- We rely on GitHub to detect licences, and it can miss one that's only mentioned in a README. If a project really has no licence, the author keeps all rights by default, even though you can see it on GitHub. Check its files, or ask the author, before you reuse, share or sell it.
- Other people's parts
- Stock firmware, ROMs and samples often belong to someone else. A project's licence doesn't give you rights to those, which is why many projects ask you to supply your own copies.
This is a general guide, not legal advice. If in doubt, read the licence or ask the author.
Glossary
- Firmware
- The software built into a device. It decides what the buttons do and what the device can play.
- Stock
- The official firmware from the manufacturer.
- Flashing
- Writing new firmware onto a device.
- Bricking
- A failed install that leaves a device unresponsive. Many devices have a recovery mode, but not all of them do.
- Fork
- A copy of a project that someone changes and develops separately.
- Open source
- The code is published under a licence that lets others use and change it. Check the project's licence for the terms.