Taking a Modified Mazda Connect to the Dealer

A dealer visit interacts with the CMU in one of a few ways: not at all, a firmware update, or a full unit swap. What you do beforehand depends on which one you’re walking into. This page covers each case, what survives it, and how to ask for what you actually want.

Do you need to prep at all?

Dealer diagnostic tools and update packages expect a stock root filesystem. If a tech runs an update against modified files, you can see checksum mismatches, update failures, or odd behavior after the update completes.

Whether that matters depends entirely on what the dealer touches:

• Routine mechanical service (oil, brakes, recalls on non-infotainment systems) never touches the CMU. No prep needed. Tweaks survive untouched.
• Anything infotainment-related (software complaint, connectivity issue, head unit work) may trigger a firmware update as part of diagnosis. Revert first.

If you’re unsure which bucket your appointment falls in, treat it as the second one and revert. Reverting is reversible; a failed update mid-write is not.

Reverting before the visit

1. Uninstall through the Miatafy app to revert ScreenTune changes back to the files it backed up before modifying them. This is our own file-level tooling and needs the unit to still boot. See revert and uninstall.
2. If the modification history is unknown (older tweaks, tools other than ScreenTune, an interrupted uninstall), do a full firmware reflash instead, from an owner-obtained .up image (dealer/service channels, Mazda’s update channels, or your own prior backup; Miatafy does not ship the firmware). See firmware recovery.
3. Confirm the unit boots normally, shows the factory disclaimer screen, and has no custom apps visible.

You can re-apply tweaks after the visit. Re-running the Install USB is repeatable, and re-installation inside the 90-day support window is covered at no additional cost.

Dealer firmware updates

How a dealer update works

1. The technician connects a diagnostic tool (Mazda IDS/MDARS or equivalent).
2. The tool checks the installed firmware version against available packages.
3. If an update is available, it writes from the dealer’s update media.
4. The update overwrites the root filesystem — the same mechanism as a USB firmware reinstall.
5. The CMU reboots to the new version.

Because the update overwrites the root filesystem, every tweak, app, and configuration is removed. Region stays the same; dealer packages are region-correct. CarPlay keeps working if the USB hub is installed. And per Mazda service documentation, firmware cannot be rolled back once installed — there is no “undo” on the version.

Asking for a specific version

If your goal is to land on 74.00.324A (the version most ScreenTune products check for), be precise about what you’re requesting. Ask for a Mazda Connect CMU firmware update, not a map update and not a Gracenote update. Those are different packages and a service advisor may default to the wrong one.

Suggested wording:

I have a Gen 6 Mazda Connect CMU and need the infotainment firmware updated to the current region-correct Gen 6 firmware. The version I’m checking for is 74.00.324A. This is CMU/Mazda Connect firmware, not navigation maps and not Gracenote. Can your service department perform that update, what would it cost, and do you need a diagnostic complaint or TSB to do it?

Ask whether the repair order can record the installed firmware version. After the visit, check the version yourself before buying or reinstalling anything.

For the full owner path to v74, see getting to v74.00.324A.

After a dealer update

• Check Settings → System → About for the new version.
• Verify CarPlay / Android Auto still works, if equipped.
• Record the version before re-applying any tweaks.
• If the version is anything other than v74.00.324A, confirm it’s supported before reinstalling. Some versions are not — see not supported yet.

Warranty visits

Infotainment tweaks are software-only changes to the CMU. They don’t touch powertrain, safety, or emissions systems. For a non-CMU warranty claim there’s no mechanical reason to revert.

That said, if a claim makes you uneasy (or the dealer is likely to run diagnostic software against the head unit), reverting first removes any ambiguity. Consult your dealer for warranty-specific questions; this page can’t speak to your contract.

CMU replacement

If the dealer swaps the CMU for hardware failure, ghost touch, or a recall, you’re getting a different physical unit. Everything that was on the old one is gone with it.

What to expect:

• The replacement may carry a different firmware version than your original.
• It may carry a different region code — verify this immediately.
• CarPlay hub wiring stays with the vehicle and works with the new CMU if its firmware supports it.
• Bluetooth pairings must be re-established.
• All prior modifications are gone; they lived on the old unit.

After receiving a replacement:

1. Check Settings → System → About — record version and region.
2. Confirm the region matches your market.
3. Test CarPlay, if equipped.
4. If the replacement runs v74.00.331, read known risky configurations before doing anything else.

CarPlay retrofit installation

If the visit is to install the factory CarPlay / Android Auto retrofit kit:

What the dealer does

1. Updates firmware to v70+ if it isn’t already (CarPlay requires v70.00.021 or later).
2. Installs the USB hub hardware (part TK78-66-9U0C or equivalent).
3. Routes the new USB cable to the console.
4. Verifies CarPlay / Android Auto activation.

Order matters. The firmware update happens before the hub goes in. Connecting the hub first changes the USB topology and makes USB firmware updates fail. The SD card must be removed before the firmware update and reinserted after. Once installed in the correct order, later updates work normally. Some dealers have run this as a free promotional install — worth asking.

After the retrofit:

• Test CarPlay with an iPhone and, if relevant, Android Auto with an Android phone.
• Confirm USB media playback still works through the CarPlay port.
• Note the new firmware version.
• The CarPlay port is the one marked with the phone icon; the other is media/charging only.

For the broader retrofit picture, see CarPlay retrofit.

FORScan changes are not on the CMU

FORScan module changes (RBCM, FBCM, SSU, IC) live in the vehicle’s body control modules, not the CMU. A dealer firmware update or CMU swap doesn’t touch them. Two caveats:

• A tech may notice FORScan-enabled features during diagnostics — for example an auto-door-lock menu showing up on a Sport trim.
• Module reflashing during unrelated warranty work can reset FORScan changes.

Keep a current backup of your AS-Built data either way. See AS-Built backup and restore.

What survives, by scenario

Scenario	Prep needed	Tweaks survive?
Routine service (oil, brakes)	None	Yes — dealer won’t touch the CMU
Infotainment / CMU complaint	Revert or reinstall firmware first	No — dealer will likely update
Firmware update requested	Accept that tweaks will be wiped	No
CarPlay retrofit install	None	No — a firmware update is included
CMU replacement (warranty/recall)	None possible	No — new hardware
Non-CMU warranty claim	Optional revert if concerned	Depends on dealer

If the unit is unresponsive or boot-looping, do not attempt a USB reinstall blind — start with backup and recovery, and contact support if you have modifications from tools other than ScreenTune or a previously interrupted uninstall.