HAKAI, the community jailbreak for standalone MPCs, has a new release, and it works very differently from the versions we covered on November 15. According to the team's announcement on its Facebook page, version 2026-11-13 doesn't install anything on your MPC. It loads into the running system and is gone when you restart.

That's a big shift for a project our HACKAI feature described as a patched firmware image. Here's what's in the release, what to check before you try it, and the bugs the team has already listed.

What changed: it loads instead of installing

Earlier HAKAI builds changed the MPC's firmware. The team says the new method arrived with the 12 November release and works differently from everything before it. In the announcement's words, it "does not install files into your MPC's internal file system. Instead, the files are loaded into the MPC's runtime environment. After a system reboot, your MPC will return to its original firmware state."

If it works as described, a restart is your undo button. It also means you should expect to load HAKAI again after each power cycle; the included instruction file covers how. Version 2026-11-13 is a bugfix update to the 12 November build, not another new method.

Before you try it

  • Official Akai firmware 3.10.1.12. The team says this release "will only work" on that version. Check yours before you download anything.
  • A drive formatted as exFAT. The v2026-11-13 release notes say your SSD, SD card, USB stick or hard drive needs to be exFAT, and that other formats "will cause problems."
  • The right download. The GitHub release has two packages: "HAKAI – Gen1 MPC & Force" and "HAKAI – Gen2 MPC."
  • The instruction file. The team asks everyone to read it before running the payload, because this version works differently from previous ones.
  • A backup of your projects and samples. Nothing in the announcement says HAKAI writes to your drives, but this is a first release of a new method. Back up anyway.

What's in the release

The announcement lists mouse support over USB and Bluetooth, plus these HAKAI apps:

  • Chrome
  • Custom Buffer Size
  • File Browser
  • Geek
  • HAKAI Control
  • HAKAI Driver
  • HAKAI Launcher
  • HAKAI VNC
  • MPC Link Audio
  • Tutors Shot
  • VST Manager

Most of these are listed by name only. The announcement doesn't explain what Geek, Tutors Shot, MPC Link Audio or HAKAI Driver do, so check the instruction file rather than guessing. The bug notes explain two of them: HAKAI Control holds the switch for the MPC's LEDs, and HAKAI Launcher is what appears when you start the jailbreak.

One overlap to know about: Akai's 3.10.1 already added a built-in mouse pointer under Preferences > Enhancements, according to its official release notes. HAKAI brings its own mouse support. If the mouse feels choppy with both running, the team's fix is to switch Akai's pointer off.

Which machines it covers

The announcement says it should work on all Gen 1 and Gen 2 MPC and Force devices: "YES FORCE as well." The GitHub release puts the Force in the Gen 1 package and Gen 2 MPCs in a separate one. The project's README still lists Force II as "soon," so if you own a Force II, check the release notes before assuming it's covered.

Not sure which generation your MPC is? The Gen 1 vs Gen 2 table in our HACKAI feature lists the models.

Known bugs and the fixes the team lists

ProblemFixWhose bug
"Failed to capture stream"Turn off Akai's screenshots and turn off Advanced Audio Settings.Official firmware, per the team. Not caused by HAKAI.
The MPC's LEDs are offOpen the HAKAI Control app and turn on the "MPC LEDs" button in the top right corner.HAKAI
The mouse feels choppyGo to Preferences > Enhancements and turn off Mouse Pointer.HAKAI
HAKAI Launcher appears upside downUpdate to v2026-11-13. The release notes say this affected models outside the X family.HAKAI, fixed in this release

The team calls this the first release of the new method and is asking the community to report anything that isn't on the list yet.

Our take: lower risk, still unofficial

Loading into memory instead of writing to the system is a sensible direction. If it works as described, most problems should cost you a restart rather than a recovery job, which is a real improvement over flashing firmware images. Our feature's section on bricked machines explains why that matters.

It's still unofficial. HAKAI's GitHub page says it is an independent project, "not affiliated with, endorsed by, or officially supported by Akai Professional or inMusic Brands," and warns that modifying your device can bring instability, data loss or incompatibility with official firmware updates. That last point matters here. This build is tied to 3.10.1.12, so a future Akai update could stop it working until HAKAI catches up.

Our suggestions if you want to try it:

  • Back up your projects and samples first.
  • Test it in a blank project before you open real work.
  • Don't load it on a gig or session day.
  • Before installing any official Akai update, check HAKAI's releases page for compatibility.
  • Leave remote-access tools like VNC off when you're not using them, especially on Wi-Fi you don't trust.

Free, with an optional tip jar

HAKAI says it "is and always will be 100% free," with no subscriptions or paywalls. If you use it and want to support development, the team has a voluntary Ko-fi page. Downloads and the instruction file are on the HAKAI GitHub releases page.