Flashing your BMW with MHD: the complete setup

MHD is the phone app that made flashing a BMW a driveway job. This is the whole flow — what the software is, what it locks to, how the first flash goes, and how to get back to stock — written from the platform side of the counter. We are independent of MHD; product facts here follow their published documentation.

What MHD actually is

MHD Flasher is a phone app (iOS and Android) that talks to your DME through the diagnostic port and rewrites the calibration — full remapping, not signal interception. It keeps the factory safety structure and adds its own code layer (MHD+) for map switching, flex fuel, and other features that plain calibrations can't carry.

Engine coverage that matters to our customers: N54, N55 (E-series and F-series variants), S55, B58 (gen 1 and 2), S58, plus S63 and N13. The N20/N26/B48 four-cylinders are not part of its catalog. MHD publishes exact chassis and year coverage in their supported-vehicles documentation.

The license model — read this before buying

• A license binds to **one VIN, one account**. One account can hold licenses for many cars; a license never moves between cars, accounts, or owners.
• Licenses live on MHD's servers, tied to the **login method** you first use — Google, Apple, or MHD account. Sign in later with a different provider and your licenses appear to vanish until you sign back in the original way.
• Software is modular: the Flasher license is the base; Monitor (gauges and logging), map packs, and flex fuel are separate line items, with a Super License bundling most of it. There is no resale value — see the FAQ.

What you need before the first flash

1. 01An MHD Flasher license for your engine.
2. 02A supported adapter — this choice decides whether flashing is boring or dramatic. Our full adapter guide covers the protocol classes and the clone-cable lottery.
3. 03A phone that meets the app's requirements (Android with USB OTG for cables; iOS needs Local Network permission granted).
4. 04A battery charger. MHD recommends one for every full write; we consider it mandatory for the first flash on any battery older than a few years.

The first flash, step by step

1. 01**Connect and verify first.** Use the code-reading screen to confirm the app talks to the DME before money or flashes change hands. No license is needed to test communication.
2. 02**Generate your stock file.** Under the Stock menu, generate the updated stock file for your exact DME and export the `.bin`. More on why below.
3. 03**Prep the car.** Ignition on, engine off (press start without touching the brake); on G-series it takes three quick presses to reach diagnostic mode. Accessories, climate, and headlights off.
4. 04**Battery on the charger.** Target a steady 13–14 V. A long write on a tired battery is the classic origin story of a bad day.
5. 05**Flash.** Pick your map, confirm the options, and let it run. Times run from a few minutes on the WiFi adapter to as much as 40 minutes on a K+DCAN cable for the initial write. Don't open doors, don't fiddle with accessories; chimes and the fuel pump running during the write are normal.
6. 06**Afterward:** MHD clears codes and restores coding, then you wait at least 30 seconds after ignition-off before starting the engine.

A first install is a Full Write. Later option changes that carry custom code are a Long Write, and stage or map changes are Map Writes measured in seconds to a couple of minutes. Slot switching after that doesn't involve the laptop-era ritual at all — it's a cruise-stalk sequence covered in the map-slots guide.

Why the stock file is sacred

MHD can rebuild stock for your DME without a stored backup, so you can always go home. That's the floor. The ceiling is different: your exact stock file is the reference every honest tune is built against.

• Our pipeline builds every calibration from a stock read married to your VIN. Not "a stock file" — *yours*, because factory software versions differ and a tune built against the wrong baseline is a gamble.
• A stored stock `.bin` is instant, offline insurance for any future flash, any tuner, any diagnosis — no dependence on anyone's server regenerating it later.
• If you ever sell the car, flashing your original file back is the clean handoff.

Generate it once, at the start, and keep copies in more than one place.

Flashing back to stock

The Stock menu's flash-back-to-stock uninstalls MHD and returns the DME to factory state — a long write, charger on. Stage 0 is the useful middle path: stock power level with MHD still installed, so your flash options and enhanced logging survive. That's the right setting for a dealership visit or a baseline datalog.

How our tunes land through MHD

When you buy a tune from us, delivery is a file: a .bin or MHD-format file tied to your VIN. You drop it into the app (Android's Download folder, or the MHD folder in iOS Files) and flash it as a custom map. You cannot pull a third-party tune off the car, and MHD's flash-time options only ride on MHD-format files — our files are built so the options you selected at checkout are already in the calibration.

The honest one-line comparison for shoppers: bootmod3 is the cloud-native alternative (maps live server-side, license transferable once, covers F/G-chassis four- and eight-cylinders MHD doesn't); MHD keeps everything local on your phone, covers the E-chassis N54 world bootmod3 doesn't, and its tuner ecosystem is file-based. If your car is an N54 or B58 in our catalog, MHD is the delivery vehicle your tune arrives in — see our stage guide for what goes in the file.

Sources

• MHD Flasher overview and license terms: [mhdtuning.com](https://mhdtuning.com/pages/mhd-flasher) and the [MHD documentation wiki](https://mhd-tuning.atlassian.net/wiki/spaces/MFS2)
• Stock file and write-class details: [MHD stock documentation](https://mhd-tuning.atlassian.net/wiki/spaces/MFS2/pages/11436047)