Firmware and backups
What a firmware update on the Axe-Fx II actually changes, what it leaves alone, and the backup that means none of it can cost you anything.
It does not erase your presets
Customised presets survive a firmware update. That is the easy half of the answer.
It can change how they sound
Updates revise amp models. A preset is a list of settings, so a preset built on a model that changed will sound like the new model afterwards. This is what the release notes are for, and why they are worth reading before rather than after.
Saving after an update can lock a preset to that version
The one that costs people something. Once you re-save a preset on new firmware, it may no longer load on the old firmware. A backup taken before the update is the only route back, which is why the backup and the update are one procedure rather than two.
It does not update the factory presets
New factory presets show up sometimes, but as a separate download you install yourself — through Fractal-Bot, the same way as firmware. A firmware update on its own leaves them where they were.
Old presets are the one real compatibility wall
Presets are generally forward compatible — an old preset loads under newer firmware, though it may not sound as intended. There is one documented exception, and it bites people who buy a used unit: because of space in the Mark I/II boot ROM, firmware newer than Quantum 3.03 will not load presets that were last saved before firmware 15.0. The route through is to load and re-save those presets under an intermediate version such as Quantum 3.0 first.
The part that makes everything else safe
Fractal-Bot handles the computer route, and the Axe-Fx II has a second route the newer units do not: an internal FLASH ROM that stores banks and settings on the unit itself.
- 1
Back up the presets and the SYSTEM with Fractal-Bot
The SYSTEM backup carries your global parameters and your Global Blocks along with the Setup menu's settings, so it is not optional if you have leaned on either.
- 2
And use the onboard backup, which needs no computer
UTILITY : PRESET has BACKUP and RESTORE entries writing to internal FLASH ROM. Every model can store SYSTEM settings this way; the original and Mark II can also store preset banks — A is 0–127, B is 128–255, C is 256–383 — and a bank takes under ten seconds. The XL and XL+ do the SYSTEM only.
- 3
Its best property: firmware updates do not touch it
The contents of that FLASH ROM are not overwritten or modified by a firmware update, or by loading presets, banks or a system file from a computer backup. It is the one copy that survives everything except you deliberately overwriting it.
- 4
Name the folder by date
Fractal-Bot asks where to put the files, so decide in advance. The convention Fractal recommend, and that touring techs use, is yymmdd — 260829, then the unit's name. Sorting by name then sorts by date.
- 5
Write down the firmware version
Keep a text file next to the backup saying which firmware was installed when it was made. This sounds fussy until the day you need to know whether a backup will load — and since presets saved on newer firmware may not open on older, that day comes.
Doing the update
Fractal-Bot, and a backup before any major update.
- 1
Quit everything else first
Close the editor, any DAW, and anything else touching audio or MIDI. They will fight Fractal-Bot for the connection.
- 2
Download and unzip, but do not double-click the firmware
The archive holds documents as well as the firmware itself, which is a SysEx (.syx) file. Extract it somewhere you can find again and leave it alone — double-clicking a .syx hands it to whatever else on your machine claims that extension. Fractal-Bot will ask you where it is.
- 3
Read the release notes
They say what changed and warn you about anything you need to know first. If you are skipping several versions at once — which is allowed, any version to any version — read the notes for the versions in between too. They ship with every release.
- 4
Then run Fractal-Bot
Three steps, self-explanatory, with the instructions built into the app. Windows needs a driver first, from the downloads page for your unit; macOS does not.
Restoring is not the same shape as backing up
Backing up is automated. Restoring is not — you send each file from the backup set over individually, waiting for one to finish before starting the next. If a System file is one of them, reboot the unit immediately afterwards. Fractal-Bot will remind you, but people miss it.
Do not do this over 5-pin MIDI
Backing up and dumping are not supported over MIDI at all. You can send files to the unit that way, but the transfer rate makes it a genuinely bad idea. Use USB.
If an update fails, try again before you panic
If the unit still boots, simply repeat the update. If it keeps failing, delete the download and fetch it again — a truncated file looks exactly like a broken unit. A different USB port or cable is the next thing to try.
The onboard backup has no undo
Both BACKUP and RESTORE to FLASH ROM are permanent. Backing up irrevocably overwrites whatever was in that slot; restoring irrevocably overwrites what is on the unit. And never interrupt either one — do not unplug or power off mid-operation, or you can corrupt the data you were protecting.
The XL and XL+ can rescue themselves; the earlier units cannot
If an XL or XL+ will not boot after a failed update, hold both Page buttons while powering off and on. It boots into a failsafe update mode showing "Version 0.00", and you update normally from Fractal-Bot — but do not run any of the ENTER functions on that page, which can lose data. The original and Mark II have no equivalent, and need support.