Module-level BMW coding,
done remotely,
done right.
I mostly work directly with workshops — and BMW enthusiasts. Hands-on with 1,000+ BMW cars produced across the last 25 years, with one mission: permanent, affordable solutions.
Want the full toolchain on your own laptop?
Separate from a one-off coding session — this is the complete diagnostic and coding stack installed, licensed to your interface, and configured correctly on your own Windows machine. One remote session, done via UltraViewer or AnyDesk, scoped to whichever chassis range you actually work on.
Coverage by generation
Each chassis family has its own toolchain and its own failure types. No universal script — every problem is addressed during our communication, car history inputs evaluated, live diagnosis of failure performed before anything is coded.
E-series
E46 · E90 · E60 · E70 · E89 · Mini R- Full coding via NCS Expert, module flashing via WinKFP
- Module replacement — usual suspects ABS, FRM, Airbag, including FA fixing
- Retrofits — cruise control, error-free LED lights, AUX, removal of annoying cluster warnings and lights
- Side airbag module programming — the infamous E85 / E89 cases
F-series
F01 · F10 · F15 · F20 · F30 · F45 · F48 · F80 · Mini F- Individual parameter coding, expert-mode edits, VO changes
- Module replacement programming — ABS, Airbag, ICM, headunit, across the whole range from basic Entry unit to NBT EVO
- CarPlay enablement via new firmware on 2015–2016 cars running NBT EVO iD4
- Transmission immobiliser reset, xDrive delete, SOS malfunction delete
G-series · 2016–2022
Pre-SecOC- Wide range of adaptation, programming, and retrofit — region conversions, CarPlay and Android Auto activation are routine
- Component protection removal
- KAFAS module adaptation and driving-assistance feature retrofit
- Transmission immobiliser reset, MGU headunit replacement with used parts
- Dash warning removal, performance retrofits
G / I / U-series · 2022+
NCD2 / KDS- NCD2 coding — FA modification and dataset generation for region, feature, and module changes
- KDS diagnostics for participant/token rejection cases, component protection removal
- Cluster symbol region conversion — PARK, BRAKE, km to mls
- M2/M3/M4/M5 performance retrofits
Everything on the bench
Grouped by job type rather than a flat list — same scope offered on WhatsApp, just organized so you can find what applies to the car in front of you.
Toolchain behind these: WinKFP, Tool32, NCS Expert, INPA (E-series) · E-Sys / E-Sys Launcher, PSdZdata Full & Lite (F/G-series) · ISTA-D for diagnostics across all chassis · FSC tools, readers & generator · HU Service Manager for iDrive service intervals.
What's solved, what isn't
Some procedures are closely guarded across the industry or blocked at the architecture level. Listed plainly rather than implied to be universal.
| Procedure | E-series | F-series | G-series (<2022) | G-series (Secure Gen) | Notes |
|---|---|---|---|---|---|
| Standard coding | Supported | Supported | Supported | NCD2 only | FDL blocked on all modules for 2022+ chassis |
| Transmission ISN sync | N/A | Supported | Supported | Case-by-case | Excludes DKG/DCT M-models, F01 6HP, F80/F10 M5 |
| Headunit FSC / region | N/A | Supported | Supported | Supported | RAM coding required separately on G-series |
| EME ISN sync | N/A | Unresolved | Unresolved | Unresolved | Open problem across the community, pre-LCI hybrids |
| ACSM crash data reset | Unresolved | Unresolved | Unresolved | Unresolved | Not offered — flagged honestly rather than attempted |
From WhatsApp to coded car
Send chassis + fault
VIN or chassis code, current symptoms, what's already been tried. This decides the toolchain before the session starts — E-series work is a different job from SecOC-era G-series work.
Connect hardware
ENET cable for F/G-series, ICOM for broader coverage including older chassis. UltraViewer or AnyDesk for the remote session — no data leaves your shop's connection to the car.
Diagnose the layer
Communication layer first, then data/profile layer. A CODIERDATEN_LESEN failure and an FA mismatch look similar to an untrained eye and require different fixes.
Code, verify, hand back
Changes verified against expected module state before the session ends. If something's outside current coverage — said outright, not attempted blind.
Trusted since 2017
Public track record, not marketing copy — built one thread on mhhauto.com across 900+ replies and 130,000+ views, still active.
A remote ISTA install and setup on a G05 was later publicly vouched for by another forum member as complete and issue-free — worth noting since SecOC-era software installs are where most remote sessions go wrong.
A G01 owner had factory ConnectedDrive and remote services present but hidden from the iDrive menu, with CarPlay previously activated but also not showing. Diagnosed as solvable with an ENET session rather than a hardware issue.
A DSC module bricked mid-programming on a G11 was recovered remotely, with an unrelated navigation fault on the same car fixed at no extra charge. The client said they'd be back for future work.
A member's E-Sys install had empty dist files and wouldn't run across two different versions — flagged in the thread as unsolved until fixed, with other members later pointed to the same fix for identical failures.
An owner confused about their navigation activation was pointed to checking FSC status and loading the correct repair pack rather than a full patch — the simpler, correct diagnosis. Thanked by name once the pack resolved it.
One of several recurring threads where US-import owners get stuck between VO changes, FSC codes, and map activation order — a sequence that produces black screens if done wrong, walked through step by step.
Paraphrased from public posts across mhhauto.com, 2020–2025. Full thread: BMW Remote Software Installation — Programming and Coding.
Have a chassis and a fault code?
Send both over WhatsApp. If it's within scope, we schedule; if it isn't, you'll know before any session starts.