iDrive 8 and 8.5 coding

What changed

• Secure coding. On these cars several modules only accept coding that BMW has signed (NCD 2.0). E-Sys signs coding itself, so those modules refuse a change made in the FDL editor. See NCD 2.0 and secure coding.
• The head unit is the main one. Owners report that the iDrive head unit on these cars is secure coded, so the classic iDrive changes (legal disclaimer, video while driving, sport displays) are no longer possible with E-Sys alone.
• Other modules can still work. Owners report coding the body module (comfort functions such as mirrors, windows, lights and lock confirmation) on these cars. It depends on the car and its software level.

Before you start

• Read the car's I-step (Expert Mode > VCM). The same model can behave differently on different software levels.
• Back up first and keep a charger on the car.
• Try one change in one module. If E-Sys reports the module as secure coded, or the coding is refused, leave that module as it is.
• Never force it. A module that refuses unsigned coding is protecting itself; do not try to get around it.

Cars with iDrive 8 or 8.5

Mostly the newer models and facelifts from about 2022: for example the 3 Series facelift (G20 LCI), X1 (U11), 2 Series Active Tourer (U06), 7 Series (G70), X5 and X6 facelift (G05/G06 LCI), i4, iX and i7. Check your car's head unit in E-Sys after reading the SVT.

Questions

Can E-Sys MAX code secure-coded modules?

No. E-Sys MAX works with E-Sys's own coding and does not get around BMW's signed coding. It tells you which modules are secure coded and keeps a backup before every change.

What about BMW-signed coding files from a dealer?

A coding file BMW has signed for your car can be written as it is. E-Sys MAX has a tool to write such a file to the module it is for, after checking that it belongs to the connected car.

Will older iDrive cars keep working?

Yes. Cars with iDrive 6 and 7 (most F and G series up to 2022) code as before. See the G20 list or coding by series.