Advertisement

Camera Firmware Hacks Explained – How Card Loaders, Service Mode and Patched Firmware Work, and What Can Go Wrong

Camera Firmware Hacks Explained – How Card Loaders, Service Mode and Patched Firmware Work, and What Can Go Wrong

Before you install a community mod on your camera, the method matters more than the feature list. This explainer, the last part of our camera firmware hacks series, looks at the three ways current mods get into a camera, why every one of them is tied to one firmware version, how recovery works, and how to judge a project before you trust it with your gear.

In the previous parts of this series, I looked at fpSup on the SIGMA fp, the shutter-angle research on the Sony a7 IV, Wonder Lantern on the Nikon Z30, Magic Lantern and the new film-look projects on Canon DSLRs, and the Ricoh GR, Hasselblad X2D and FUJIFILM X70 mods. The projects differ a lot in what they add, but they fall into three technical groups. Understanding which group a mod belongs to tells you most of what you need to know about the risk.

One general point first. None of this is supported by the manufacturers, and several projects say plainly that modifying a camera may void the warranty. If a camera is your main working tool, my advice is simple: try mods on a second body, or not at all.

Method one: code loaded from the memory card

The safest group loads extra code from the memory card every time the camera starts and runs it in RAM, next to the manufacturer’s firmware. Magic Lantern on Canon DSLRs has worked like this since 2009, and fpSup on the SIGMA fp, GRKit on the Ricoh GR, FujiMod’s SD dual boot on the FUJIFILM X70 and Soup Engine and Film Roll on older Canons use the same principle. Take the card out, and the camera boots stock.

SIGMA fp record settings with the 3000 x 2000 open-gate option
The first open-gate build on the SIGMA fp added a 3000 x 2000 CinemaDNG option. Image credit: Vitali Li

How the code gets in differs. Magic Lantern needs a one-time flag that lets the camera boot from the card, which its installer sets. On the SIGMA fp, firmware Ver.5.02 already contains a factory shell that runs a script called AutoRun.txt from the card at startup, with no confirmation step, so fpSup uses that script as a loader. GRKit switches on the GR’s own SD script setting, which stays on.

There are two details to know. First, if a mod adds an entry to the camera’s own menus and you select it, the camera stores that choice in its normal settings. fpSup therefore tells users to set menus back to stock options before deleting the files, and Soup Engine warns that deleting Magic Lantern’s startup file while the boot flag is still on leaves a camera that will not start until the file is back. Second, “runs from the card” does not mean “cannot hang”. GRKit’s recovery guide describes what to do if the camera stops at startup: remove the battery and the card, and start the camera without it.

Method two: settings changed through a service mode

The Sony a7 IV research project uses a different route. Sony-PMCA-RE, an open-source tool by developer ma1co, switches the camera into Sony’s USB service mode, where stored settings can be read and written as numbered properties. Changing one of them switched the a7 IV to shutter angle. Nothing in the firmware is replaced, and writing the original value back restores the camera.

The risk here is less in the change itself and more in getting it wrong. The project’s procedure is strict for a reason: save a complete backup of the settings first, change one property at a time, cold-boot with the battery removed for ten seconds, test, and restore the original value before the next experiment. The project also documents that a stored value can be accepted and kept across reboots while still doing nothing, because a separate product rule in the firmware blocks the feature. A setting that sticks is not proof that a feature works.

Method three: patched firmware

The third group modifies the manufacturer’s firmware file and installs it through the camera’s normal update process. Wonder Lantern on the Nikon Z30, GR Mod and GR4-MonoUnlock on the Ricoh GR IV work like this. None of them ships the manufacturer’s firmware: you download the official file yourself, and a tool on your computer checks it and writes the patched version.

This is the group with the highest risk, and the developers say so. The GR4-MonoUnlock documentation states that if an update is interrupted or a firmware file cannot start, the camera may not reach the update function again and would need manufacturer service, although this did not happen in its tests. It also notes that an official update from the manufacturer removes the mod, because it replaces the whole firmware. GR Mod documents an earlier version that froze the camera because of a setting the official firmware could not read, and its current version resets such values on startup. Always keep the official firmware file, and check the steps for going back before you install anything.

This method is now spreading quickly across Nikon’s Z system. Wonder Lantern versions now exist for the original Z5 and Z6, and an independent lab version adds a first feature to the original Z7. A reader pointed us to the biggest one in the comments under our Z30 part: NikonFirmwarePatch for the Nikon Z8. Version 0.4.0 adds 8.3K open-gate N-RAW recording in 3:2 at up to 30p, ProRes HQ, 422, LT and Proxy, five H.265 bitrates, S-Log3 and Log3G10 recording, RAW pre-capture and pixel-shift merging in the camera. The developer reports only a limited test on a Z8 and warns that offline checks “cannot guarantee safe operation on a camera”. We look at it in more detail in a separate article.

Nikon Z8 frame size menu with 8.3K open-gate N-RAW options from NikonFirmwarePatch
NikonFirmwarePatch adds 8.3K open-gate N-RAW options to the Nikon Z8, shown in the emulator. Image credit: NikonFirmwarePatch

Why every mod needs one exact firmware version

All three groups depend on fixed memory addresses or exact file contents. fpSup works on fp firmware Ver.5.02 only. Wonder Lantern accepts one Z30 firmware file with one SHA-256 checksum. GR4-MonoUnlock refuses any file other than Ricoh’s GR IV 1.11, while GR Mod and GRKit add each new Ricoh version to their lists only after the developers have checked it. The Nikon Z8 shows what this means in practice: NikonFirmwarePatch accepts only Z8 firmware C 3.11, Nikon has replaced it with C 3.12 and taken down the C 3.11 download page, and the patch does not support C 3.12. So if you want to use a mod, do not install the manufacturer’s next update without checking, and if your camera already runs a newer firmware, the mod may simply not be available to you.

How to judge a project before you try it

After reading through many of these repositories, I see a few things that separate the careful projects from the rest. The good ones keep a table of what has been verified on a camera, what has been checked only in an emulator or in code, and what is untested, and they update it with every release. Wonder Lantern, fpSup, the Sony a7 IV project and GR4-MonoUnlock all do this. They name the exact camera and firmware, publish removal steps next to the install steps, and correct their own earlier claims in public when they turn out to be wrong.

There is one more point, which this series showed while I was writing it. A project on GitHub can disappear. Between my first research and the final check, the Hasselblad X2D toolkit went offline, and its research repository was reduced to a note that says public release has stopped at Hasselblad’s request. If you install any mod, keep your own copy of the tool, the official firmware, your backups and the removal steps, so that you can still go back to stock if the project page is gone.

The role of AI deserves a separate warning. Several developers say openly that AI assistants helped them decompile firmware, and fpSup even publishes instruction files for AI assistants. Its developer also writes: “My AI has made many mistakes, and some of them may still be in my research notes or Skills.” In my opinion, that applies to every project in this series. AI makes it faster to find something in a firmware file, but only a test on a real camera shows that a clip records cleanly from start to end. For video in particular, test long takes, check every frame of a few clips on a computer, and never use a mod for the first time on a paid job.

When the manufacturer opens the door

There is an official version of all this, and it is worth a look. GoPro’s Labs program, which we covered at its launch in 2020, offers experimental firmware that adds features controlled by QR codes, all off by default, and GoPro Labs on GitHub lists current builds for cameras up to the MISSION 1 series. On the other side, apps like OpenPocketCine add monitoring tools such as waveforms and false color to DJI Osmo cameras through a reverse-engineered control link, without touching the camera firmware. Even that project tells users to check that recording starts and stops on the camera body until they trust the link, which is good advice for every tool in this series. (Camera manufacturers, a GoPro Labs-style program for older bodies would take a lot of the risk out of this, for you and for your customers.)

GoPro Labs QR codes next to a GoPro camera
GoPro Labs controls the camera with QR codes. Image credit: CineD

Our readers clearly want something like this. Under our Sony a7 IV part, a reader asked Sony for official shutter angle on Alpha cameras and wrote that “even a paid update is better than nothing”. Under the overview, another reader asked Canon to “charge us $100 for a firmware update” for missing features on older Cinema EOS cameras. Canon has just shown that it can add a lot with software, with its firmware update for the EOS C400, C80 and C50.

OpenPocketCine monitor app on a smartphone
OpenPocketCine turns a phone into a monitor for DJI Osmo cameras. Image credit: OpenPocketCine

Price and availability

All projects mentioned in this series are free, and most publish their source code; a few accept donations or offer extra content to supporters. You can find each project’s install and removal instructions in the links in the individual articles. Using any of them is at your own risk.

Have you ever bricked, or nearly bricked, a camera with a mod? What would you need to see from a project before you trust it? Let me know what you think in the comments below!

Leave a reply

Filter:
all
Sort by:
latest
Filter:
all
Sort by:
latest