"It's already in the camera, the official just won't let you have it": a grad student turned Sony A7C II's hidden filters into a one-click tool. 20 days, 1118 stars, 20k downloads

A grad student turned a Sony camera firmware hack that someone else had just cracked into a desktop app that installs in one click. It gives the A7C II the FL2/FL3 film colors Sony had only offered on newer models, plus Fujifilm- and Ricoh-style straight-out-of-camera looks. He didn't write the underlying hack. He won by being the first to make it something ordinary people would dare to use, and he showed up personally on RedNote and Bilibili. Below: why it blew up in October, where users came from, who's following, and where you could break in.

A Mac tutorial that got 542 likes in a day

In 2026 October 17, GitHub user QAQLeonard created a repo with a plain name, a7c2-fl23-research, meaning "FL7/FL2 research for the A2C3" (since renamed a7c2-tools). The next day, a RedNote post titled "Installing FL7/FL2 on the A2C3 from a Mac" got 542 likes and 710 saves. The saves outnumbered the likes, which means people who actually planned to try it were bookmarking it. The same day, someone posted a Linux version tutorial with the title "Sony is an evil company!", also complaining that the Windows drivers are hard to install and that Linux worked on the first try (compiled by SMZDM, 10-24).

There's a reason people blame Sony. FL2 and FL3 are two film-look settings in Sony's "Creative Look" lineup. They shipped on the FX2, RX1R III, and A7 V, and in October 2025 Sony gave the Alpha 1 II the same thing in a firmware update. The A7C II, a big seller, runs on the same hardware but never got them. In August 2026 Sony launched 15 official "recipes" in the Creators' App, and the ones the A7C II can use leave out FL2/FL3. The title of the SMZDM article sums up the mood: It's already in the camera, the official just won't let you have it.

So users don't see this as "installing a third-party filter." They see it as "getting back something that was cut." That line needs no explanation to share, and it's the first reason this spread so fast.

What it actually is

A Windows / macOS desktop app that only supports the A7C II on firmware 2.01. You connect the camera with a USB cable, click "Install," and it installs:

• FL2 / FL3 two creative looks, removable at any time;
• 6 custom look slots, with 15 matched sets of color files built in (11 Fujifilm-style sets, 4 Ricoh-style sets). Use one set in the camera and the matching one for editing RAW in Lightroom. It can also convert LUT and DCP files found online into formats the camera accepts;
• an electronic shutter sound (any audio clip can be the shutter sound), with info and icons that rotate when shooting vertically;
• "Restore factory": undoes every change this tool made, without needing an old backup.

The first screen of the README is a large bolded disclaimer: unofficial, no commercial use allowed. The author explicitly opposes "paid flashing, remote paid installs, resale, or selling activation codes," and says he has never authorized anyone to charge money in his name. The strong wording suggests this kind of demand has already appeared. (Sony flashing services already exist on Taobao, changing language and region settings. Whether anyone is using this tool to charge money is unverified.)

Why October: someone else cracked the door open, and he built the first "beginner version"

The demand had been building for over a year. In 2025 November, a RedNote post titled "A7C2 calls FL2/FL3" got 1282 likes, but it was only color files for Lightroom and still needed editing. Getting the look straight out of the camera had never been possible.

The route appeared in mid-October 2026, and it came from others:

• 10-15, YuuLuo opened a7c2-service-preload to study the service-mode communication of the A7C II (now 85 stars);
• 10-16, lzh2016zzz ported FL7/FL2 to the sibling model A3CR (30 stars). That same day, a RedNote post showing a real test, "A7CR fully supports FL2/FL3," got 226 likes;
• 10-17, QAQLeonard created the repo, and the README states that lzh2016zzz's work was "the starting point for his parameters, tags, and method."

The larger backdrop: since late September, the whole camera community has been swept up in "AI-cracked firmware." An overseas developer fed Sigma fp firmware to a large language model and unlocked full-frame Open Gate video. After that, posts about Nikon, Ricoh, Panasonic, and Hasselblad followed one after another, and someone bricked a Nikon Z9 and only recovered it by desoldering the chip (compiled by SMZDM, 11-04). The project's author also says much of the code was written with AI help. The repo includes instruction files for AI coding assistants, the update post carries the #vibecoding showcase tag, and one Mac tutorial even includes a prompt that says "if you don't know the terminal, have the AI run it for you." AI lowered both the barrier to building it and the barrier to using it.

It really took off with the 21 version in late October 3.0: the first complete GUI for this model. Driver setup, install, verification, and restore are all buttons, with packaged programs for Windows and Mac, so no command line is needed. Earlier projects in this space were research notes or scripts. The cumulative GitHub stars per day went like this:

Downloads say more than stars. As of 11-06, the installers across all versions had been downloaded about 20.9k times, and v3.0.3 alone accounts for 15k (GitHub release page numbers; one person may download several times). So roughly one in twenty downloaders stars the repo, and most of the people who came in aren't GitHub users at all.

Where users came from: GitHub is only the download site

No paid acquisition was found. Everything was organic, and almost all of it was on Chinese platforms:

• The author showed up personally. The top of the README links to his RedNote account "QAQLeonard (grad student edition)" and Douyin account "LeonardZ," and the 3.0 update post was also his.
• RedNote shows and comparisons. Starting in 10-19, people posted comparison photos taken from the same position with the same settings, changing only the creative look, straight out of the camera with no editing. Posts like "My A7C2 can now shoot straight Fujifilm NC/CC" flooded the feed.
• Bilibili tutorials. UP主 "Old Chen Loves Cameras" posted install tutorials, "step-by-step hand-holding guides," and Mac flashing tutorials. There were also reverse videos saying "don't flash" and "think twice," which helped spread it too.
• Tech media. IT Home ran "AI Successfully Cracks Sony A7C II Camera Firmware" on 10-26. Note the line at the top: "thanks to a reader's tip". The story came in from a reader. Tencent News, Sina, Sohu and Zhihu columns picked it up, and some overseas sites translated it. The single-day peak in stars landed the day after.
• Forums and groups. NGA, Threads, and Taiwanese Facebook Sony groups all discussed it. The author opened Telegram and Discord groups, and about 70 issues kept users engaged. The English-language Reddit mentioned it only sporadically.

Behind 20k downloads: people asking in issues "what do I do now?"

People are actually using it. The hottest issue, #31,10-23, is titled "Even following the standard process can cause the device to malfunction." In it, 10-25, one user followed the instructions exactly, removed the battery, and the camera wouldn't power on. The access lamp blinked in a loop 2-3-5, and the only message was "what do I do now?" Another user had already booked a warranty pickup. Someone said the official repair requires replacing the motherboard, "around three thousand."

Two days later, a user found a self-rescue method in the same issue: remove the battery and SD card, set the dial to video mode and exposure to P, then power on. That gets you into the system, because the tool only changed the photo-shooting logic. The author replied, "This is genuinely useful, and it will be written into the app in a later version." The IT之家 report also mentioned another side effect: a user said the flash made third-party batteries no longer recognized.

Two things follow. First, the safety design (one-click restore and read-back verification after writing) isn't decoration. It's what makes ordinary people willing to press the button. Second, the tool's reputation could flip at any time because of one bricked-camera post, so how quickly the author responds in issues matters as much as the features.

Who's following: popular models already have people on them

There are five or six open-source projects for the same model and feature (a Mac command-line version with 52 stars, a Linux script with single-digit stars, and various research notes), with combined stars under a fifth of this one's. The first to make a "beginner version" took nearly all the attention.

Follow-ups on other models came even faster. The author listed them in a table in the README:

Beyond Sony, the Sigma fp, Nikon, Ricoh GR4, Panasonic S5, and Hasselblad were all modified in this wave, with very different risks. The Sigma fp patch only changes memory, so deleting one file from the card and removing the battery once reverts it. Nikon Z9 writes directly to flash memory, so a bad write can only be fixed by desoldering the chip (compiled by SMZDM, 11-04).

If it were you

Verdict: B. This playbook has been proven: take someone else's reverse-engineering research, turn it into a one-click GUI, then post side-by-side comparison images on Chinese platforms yourself. It can be carried over to other models and brands. But you need the camera in your hands, need to be able to read someone else's reverse-engineering notes, and need to handle the pressure of users bricking their cameras. This wave's hot Sony models are already taken, and the window is measured in weeks.

Who it's for: People who own a camera nobody has made a beginner-friendly version of yet, who can code in Python and USB communication, and who can read publicly available reverse-engineering notes. Who also shoot photos themselves and can post native-output comparison images on Xiaohongshu and Bilibili in Chinese. The author here is a grad student who built it alone, with AI help.

Who it's not for: Anyone without the physical camera who just wants to build another A7C II tool (that spot is taken, and the five or six similar projects together are less than a fifth of its traction). Anyone who can't handle users bricking their cameras or who doesn't want to answer issues every day. Anyone hoping to make money from this (these projects treat being free as a selling point, and the moment they charge, the goodwill disappears).

How to do it: pick one of two paths.

1. Switch models. Pick a model where the door has already been opened by someone else but only notes or source code exist: A7 IV has only reverse-engineering notes, A7CR has source code without flashing, A7 V's in-camera storage is still empty. For other brands, start with something like the Sigma fp, which only changes memory and reverts when you pull the battle, rather than anything that requires writing flash. Follow its feature list: one-click install, read-back verification after writing, one-click restore that doesn't need an old backup, exportable diagnostic bundle, bilingual README, and the risk disclaimer on the first screen.
2. Do the part nobody has done well, the part that doesn't touch firmware. Its built-in 15 set of Fujifilm/Ricoh looks is the most popular feature, and its color references came from two Xiaohongshu bloggers. An open, model-sorted library and converter for creative look recipes, with native-output sample photos, carries no bricking risk at all, and every user with an unlocked Sony model can use it. (Inference: similar to the recipe sites in the Fujifilm community, but on the Sony side there is no open, centralized hub yet.)

How to get users: On launch day, post "same camera position, only the look changed, straight out of camera, no editing" comparison images on Xiaohongshu yourself, and a screen recording from download to install on Bilibili. Use GitHub only as a download page, and put your Xiaohongshu and Douyin links on the first screen of the README. Open a Telegram or WeChat group to keep users, and personally reply to bricking posts right away. Write a headline in the style of "It's already in the camera, the manufacturer just won't give it to you," then, like that netizen, send the tip to tech outlets like IT Home. Its star peak came the day after the coverage.

Deadline: Ship a usable GUI version before early December of 2026. This round of "AI cracks camera firmware" has been running since late September. The A7C II project's stars have dropped from over 100 a day to about 15 a day, so the topic heat won't last long, and the manufacturer could shut the door with new firmware at any time.

Signs that would mean you read it wrong:

• Sony ships new firmware for the A7C II that closes the service-mode route, or simply hands down FL2/FL3 officially. The former narrows the whole path, and the latter kills the selling point of "getting back what was cut";
• The model you picked gets a one-click GUI version within two weeks before your launch;
• Content on Xiaohongshu and Bilibili about "bricked" and "don't flash" drowns out photo shares and tutorials, and gets more views and likes than the tutorials do;
• The reverse case: if an A7 IV or A7 V one-click tool appears before December and passes 500 stars within a week, it means the route is still hot, so move fast.