MHD fault codes and flash recovery

Two failure families bring people to this page: the engine threw a code after a modification, or the flash itself failed partway through. The first is a Tuesday; the second is a scary afternoon with a good ending most of the time. Both start with the same screen.

Reading codes with MHD

MHD's code reader (no license needed — it's also the free communication test) returns the engine's active fault codes plus the context that makes them interpretable:

• Current and factory **software versions** — what the DME is actually running.
• **VIN**, battery voltage, ECU status, OBD readiness monitors.
• The **flash counter** on F-series and later — how many times this DME has been written.
• A local **code history** on the phone, so a code that keeps coming back across weeks is visible as a pattern, not a series of surprises.

The screen shares out by email — send the whole readout, not a photo of one line, when you're asking anyone for help. Clearing codes is one button; the discipline is on you.

The codes a modified car actually meets

A short honest list, with the factory fault-plan documents reachable from your garage workspace (signed-in customers can pull the full stepped diagnosis for each):

• **30FF / P0299 — turbocharger, boost pressure too low.** The classic underboost code after a boost-control change, a leak, or a tired wastegate. See the MAC solenoid guide for the whole diagnostic.
• **30FE / P0234 — turbocharger, boost pressure too high.** Overboost: creep, a misbehaving solenoid, or a tune meeting hardware it didn't expect.
• **28A4 / P12A2 — boost-pressure sensor, plausibility.** The DME doesn't believe its own sensor — wiring, a failing sensor, or a mismatched T-MAP option.
• **Misfire codes after flashing** are, in MHD's own support experience, usually tired plugs (~10k mi) or coils (~30k mi), not the calibration. Flashing raises the demands; it doesn't refresh the wear parts.
• **2AAE / 2AAF — fuel pump / fuel pump plausibility.** The low-pressure fuel system objecting — the LPFP guide covers the upgrade and wiring side.

When a flash fails

The error strings in the wild cluster tightly: "Timeout," "Failed to flash DME," "Unable to erase memory," "Unable to prepare memory section," and writes that stall in the first few percent. Four root causes explain nearly all of them, roughly in frequency order:

1. 01**Unstable adapter or WiFi.** The dominant cause per MHD's own support history. An obsolete WiFi dongle or a flaky clone cable drops the transport mid-erase. The classic case: repeated timeouts on an old adapter, then a clean flash first try on a wired ENET connection.
2. 02**Voltage.** A tired battery sags under the sustained draw of a long write. One documented case completed "successfully" into a dead cluster and two days of no-start; the fix was a charger and a night on mains.
3. 03**Competing CAN traffic.** An aftermarket display or device left active on the powertrain bus can break DME writes while everything else works. Disable the accessories before you blame the car.
4. 04**A locked DME.** Presents as a failure around 3%. Newer cars ship with locked DMEs that need unlocking (bench work) before any custom flashing — MHD's Unlock Check tool answers this before you spend anything.

The recovery ladder

Work the ladder in order; stop at the first rung that works:

1. 01**Charger on, verify 13–14 V**, ignition in the right state, phone charged.
2. 02**Retry the same flash.** The bootloader usually survives an interrupted write; community experience describes MHD as very forgiving here.
3. 03**Swap the transport.** WiFi failed → go wired ENET (F/G) or a known-good K+DCAN cable (E-series). This rung alone closes most cases.
4. 04**Reflash stock.** If the car won't start, MHD's guidance for locked/failed states is to flash back to stock first so the car runs, then diagnose on stable ground.
5. 05**E-Sys/ENET recovery** (F/G) or a bench flash as the last resort — and a genuinely unresponsive MEVD is the rare exception, not the rule.

Sources

• Code reader capabilities: [MHD codes documentation](https://mhd-tuning.atlassian.net/wiki/spaces/MFS2/pages/11108369)
• Unlock tool and failed-flash guidance: [MHD Unlocker](https://mhdtuning.com/pages/mhd-unlocker)
• Community failure/recovery threads: [f30.bimmerpost.com flash failure](https://f30.bimmerpost.com/forums/showthread.php?t=2131675), [f80.bimmerpost.com write failures](https://f80.bimmerpost.com/forums/showthread.php?t=1953602), [e90post no-start recovery](https://www.e90post.com/forums/showthread.php?t=1570383)