MZD-AIO on v74: Unsupported, Working, and Where It Breaks

MZD-AIO has never supported v74. Its last release, v2.8.6, is from April 2020, and the installer refuses any v74 build.

Since February 2024 the community has run it on 74.00.324 anyway: edit the installer’s version check, then start it by hand from a terminal on the screen with a USB keyboard. Most of the daily-use tweaks apply. The failure that matters is on units with wireless CarPlay, where AIO overwrites v74 system files with 2020 versions and wireless CarPlay stops working.

AIO stopped in 2020 and its developer has not revisited v74

MZD-AIO (by Trevelopment, hosted at mazdatweaks.com) was the primary tweak tool for Gen 6 Mazda Connect from roughly 2016 to 2020. It bundles the popular community tweaks into one USB installer: disclaimer removal, touch while moving, menu and list loop, bigger album art, a speedometer app. Gen 6 vs Gen 7 is the primer on which cars have this system.

Its documentation lists v55 through v70 as supported. The developer’s only comment on v74 is a closed issue from August 2021 saying Mazda had removed the entry points the installer relied on. The v74 issues opened since, including the wireless CarPlay reports, have no developer reply.

The desktop app still needs the computer’s internet connection off before it will launch, a bug open since early 2024.

The community runs it on 74.00.324 by hand

Owners build the USB with AIO 2.8.6 as usual, then open the generated script and change its version check. Without that edit the CMU (Mazda’s Connectivity Master Unit, the computer behind the dash) reports the firmware as incompatible and stops.

In the car, a community-found entry method opens a terminal on the screen; plug in a USB keyboard and type the command that starts the script. The Mazda3Revolution thread MZD-AIO tweak on FW 74+ carries the steps and the owner reports cited here, from November 2024 onward.

Owners who succeed describe an uneventful install. The ones who struggle hit the same snags: USB sticks the CMU won’t mount, keyboards it won’t recognize, case-sensitive commands, a Mac that refuses to open the 2020 app. Adding a tweak later means repeating the terminal step.

What applies on 74.00.324, by community report

The thread’s crowd-sourced checklist and the replies under it agree on the following.

Reported working. Touch while moving (the AIO tweak affects the Mazda UI and CarPlay, not Android Auto), no disclaimer, shorter page delay, main menu loop, list loop, backgrounds and color schemes, status bar tweaks, camera warning removal, video player with the swapfile tweak, bigger album art, fuel consumption. AA Touch is Miatafy’s separate ScreenTune option for Android Auto input. One owner’s test narrowed a new beep, heard when the commander is held up or down, to main menu loop or shorter delay; the no-beeps tweak silences it.

The speedometer. Works on 74.00.324 for most reporters. On a CMU with factory wireless CarPlay, one tester got one or two reboots after about three minutes of driving, reproducibly, and a user-patched build fixed that for its author but not for that unit.

Reported broken.

AIO’s Android Auto app does not run on v70 or v74. Installed on a car that already has OEM Android Auto, it puts the CMU in a reboot loop every 10 to 15 seconds, and recovery has ranged from a lucky factory reset to a serial cable and a firmware reflash.
Pause on mute is skipped by the installer on v70 and later, because the firmware has it natively.
Boot animation reverts to stock after a reset for some owners.
Audio source order did not apply on the first try for some.

Wireless CarPlay is the failure that matters

AIO’s tweaks replace whole system files with copies from its own package, including the system app, the system settings app, and a firewall script, all from before wireless CarPlay existed. Forum users who diffed the files report that the v74 versions carry the wireless CarPlay code, so installing AIO’s copies removes it.

The symptom is a CarPlay Wi-Fi option that will not turn on. Owners disagree on whether only the Wi-Fi and SSH tweaks trigger it: one kept wireless CarPlay after skipping them, and another lost it with only touch while moving, no disclaimer, and shorter delay installed.

Recovery on 74.00.324. Reinstalling the firmware has restored wireless CarPlay in the reported cases. AIO’s own uninstaller and its file backups have not. See backup and recovery.

No recovery on 74.00.331. That build has no public package to reflash. Owners who lost wireless CarPlay there have stayed without it, on a third-party dongle. Don’t run AIO on 74.00.331. Risky configurations has the rest of the picture for that build.

Black screens, partial uninstalls, and updates that wipe everything

Display toggle. The menu the community route opens has a display-toggle option that blanks the screen and survives reboots and battery pulls. Owners recover by navigating to factory reset with a flashlight held to the panel. See black screen.
Partial uninstall. AIO builds an uninstaller per tweak, and for cosmetic tweaks it works. For the wireless CarPlay loss it has not.
Updates wipe tweaks. A v74 update deletes AIO’s changes, and a dealer visit that includes a reflash does the same. Touch while moving has survived in a few reports; the rest is gone. See factory reset vs firmware reinstall.

AIO still fits v70, and 74.00.324 without wireless CarPlay

On v55 through v70, AIO is supported and does what it always did; use its own documentation for the firmware-specific steps. On 74.00.324 it is a fair choice for an owner with no CarPlay hub or a wired one, who is comfortable with a keyboard and a terminal and accepts forum-only support. It is free.

Owners with wireless CarPlay hardware, or on 74.00.331, risk losing CarPlay with no clean way back.

ScreenTune covers the same tweaks on v74 without the terminal

ScreenTune is the v74-era equivalent: the popular daily-use changes rewritten against the v74.00.324A files, with first-install backups and a REMOVE action on the matching USB. The install is a USB stick and an on-screen prompt; there is no keyboard, terminal, or version check to edit. The order intake records whether the car uses wireless CarPlay, and the package is built for that configuration.

It also adds startup and reliability work AIO did not have. On one bench CMU running 74.00.324A, the screen became touch-ready about 16 seconds sooner (48 s to 32 s), and with wireless CarPlay selected, CarPlay connected about 16 seconds sooner typically (71 s to 55 s) and up to about 20 seconds sooner on a good boot; the boot benchmarks carry the per-boot ranges. ScreenTune covers the current package, and features and options is the exact customer-facing scope.

The touchscreen lockout is the tweak people came to AIO for first: the factory disables touch once the car is moving. If that single change is all you want, TouchTune is a free, open-source script that does just that, built for v74.00.324A. You can read it before you install, and remove it the same way.

Most of what people install AIO for has a direct ScreenTune equivalent:

AIO tweak	In ScreenTune
Remove disclaimer	Yes
Speed restriction removal	Yes
Menu loop	Yes
List loop	Yes
Bigger album art	Yes
Remove beeps	Yes
Track notification	Yes
USB audio mod	Yes
Speedometer app	Miatafy Meters add-on (apps)
On-screen gauges and logging	TrackTune (separate closed beta)
Custom boot animation	Add-on
Color scheme	Add-on

Reinstall firmware before ScreenTune if AIO was ever on the unit

Don’t layer ScreenTune on top of existing AIO modifications. Both touch the same files with different backup conventions, so conflicts are likely. Start clean:

Reinstall the original firmware over USB from an owner-obtained firmware image; see backup and recovery.
Install ScreenTune on the clean baseline.