Request about availability of your MMI updates

Audi MMI Firmware Updates for European Audi Cars

Keeping an Audi MMI system up to date starts with one thing: identifying the exact firmware branch installed in the car.

Two Audi vehicles from the same year can use completely different infotainment systems, so choosing firmware only by model, production year or screen appearance is not reliable.

For European Audi vehicles, you may encounter software families including:

BNav_
HNav_
HN+_
HN+R_
RMC_
MENT_
MSTD_
MHIG_
MHI2_
MHI2Q_
MHS2_
MH2p_
MHI3_

Each family belongs to a different generation or hardware platform.

Firmware designed for one branch must not be installed on another simply because the vehicle model or model year looks compatible.

If you do not know which MMI system you have, start here:

You can also enter the complete software version into our update checker:

Quick Guide to European Audi MMI Firmware Families

Here are some of the most common firmware families found in European Audi vehicles:

MMI 3G Basic:
BNav_EU_

MMI 3G High:
HNav_EU_

MMI 3G Plus:
HN+EU
HN+R_EU_

RMC:
RMC_EU_

MIB1 Entry:
MENT_EU_

MIB1 Standard:
MSTD_EU_

MIB1 High:
MHIG_EU_

MIB2 High:
MHI2_
MHI2Q_

MIB2 Scale:
MHS2_

Newer MIB2 / MIB2+ systems:
MH2p_

MIB3:
MHI3_

The complete software train is more important than the Audi model name.

Audi MMI 3G Basic – BNav Firmware

MMI 3G Basic can normally be identified by a firmware version beginning with:

BNav_

For European systems, a common software branch is:

BNav_EU_

One of the main firmware releases currently available for this platform is:

BNav_EU_K0260_1_D1

Audi product number:

8R0 906 961 DP

Firmware:

This firmware is intended for compatible MMI 3G Basic systems.

Do not install it on:

HNav_
HN+_
HN+R_
RMC_
MHI2_
MHI2Q_
MHS2_

If your main software version starts with BNav_EU_, verify the complete current version before updating.

MMI 3G Basic also uses its own navigation map family. Firmware and navigation maps are separate packages.

Current European map information:

Detailed map installation guide:

Audi MMI 3G High – HNav Firmware

MMI 3G High normally uses a software train beginning with:

HNav_

European units commonly use:

HNav_EU_

One of the main European firmware releases available for this platform is:

HNav_EU_K0257_6_D1

Firmware:

HNav firmware must not be confused with BNav or HN+ software.

For example:

BNav_EU_K0260_1_D1 = MMI 3G Basic

HNav_EU_K0257_6_D1 = MMI 3G High

HN+_EU_AU3G_K0942 = MMI 3G Plus

They are different systems even though all three belong to the wider MMI 3G generation.

European MMI 3G High navigation maps are also separate from firmware.

Information about the 6.36.0 European navigation database:

Audi MMI 3G Plus – HN+ Firmware

MMI 3G Plus uses several software branches.

On vehicles such as selected Audi A4, A5, Q5 and Q7 models you may see:

HN+EU_AU3G

A well-known European firmware version for this branch is:

HN+_EU_AU3G_K0942

Product number:

8R0 906 961 FC

Firmware:

Do not treat every version beginning with HN+ as interchangeable.

The complete train matters.

Audi A1 MMI 3G Plus – AU210 Branch

Audi A1 uses its own MMI 3G Plus software branch.

You may encounter versions beginning with:

HN+EU_AU210

One firmware offered for this branch is:

HN+_EU_AU210_K0900

Product number:

8R0 906 961 EC

Firmware:

The AU210 identifier is important.

Do not install an AU3G firmware package simply because both systems are described as MMI 3G Plus.

Audi MMI 3G Plus – HN+R Firmware

Selected Audi A6, A7, A8 and Q3 vehicles use another MMI 3G Plus family:

HN+R_EU_AU_

Examples you may encounter include:

HN+R_EU_AU_K0942_4

and

HN+R_EU_AU_P1001

These are part of the HN+R platform, but the correct target firmware still depends on the exact existing software and hardware configuration.

Current firmware pages include:

HN+R_EU_AU_K0942_4:
https://mmiupdates.com/product/hnr-eu-au-k0942_4-8r0906961fb-latest-firmware-for-3gp-3g/

HN+R_EU_AU_P1001:
https://mmiupdates.com/product/hnr_eu_au_p1001-latest-firmware-for-3gp-3g/

Do not assume that every HN+R unit can use any HN+R package without checking its update path.

If your MMI displays something such as:

HN+R_EU_AU_P0770

HN+R_EU_AU_K0942_4

HN+R_EU_AU_P1001

enter the complete version into:

What About HN+_EU_AU3G_K0942 and HN+R_EU_AU_P1001?

These two names look similar but describe different MMI 3G Plus branches.

HN+_EU_AU3G_K0942 is commonly associated with the HN+ platform.

HN+R_EU_AU_P1001 belongs to the HN+R platform.

You cannot determine compatibility by comparing only the final number such as K0942 or P1001.

The part before the firmware number is critical.

Audi RMC Firmware

RMC is another Audi infotainment family and should not be confused with MMI 3G.

Its software normally begins with:

RMC_

For European units you may encounter:

RMC_EU_

One important current firmware product is:

RMC_EU_K16158

Firmware:

RMC requires additional care because firmware compatibility can depend on the exact RMC hardware revision.

For RMC_EU_K16158 in particular, check the product requirements and hardware version before installation.

Do not choose RMC firmware using only the vehicle model.

Audi MIB1 Firmware – MENT, MSTD and MHIG

Audi later moved from MMI 3G and RMC to the MIB family.

Early MIB systems may use prefixes including:

MENT_
MSTD_
MHIG_

Legacy European examples you may encounter in Audi software databases include:

MENT_EU_AU_P3120

MSTD_EU_AU_K3151

MHIG_EU_AU_P1531

These are not three versions of the same firmware.

They represent different MIB hardware families.

For example, an Audi A3 equipped with MSTD cannot simply be updated using MHIG firmware.

Always match the complete software train.

Audi MIB2 Firmware – MHI2 and MHI2Q

MIB2 introduced a much larger number of hardware-specific firmware branches.

Common prefixes include:

MHI2_

MHI2Q_

But even those prefixes are not specific enough by themselves.

Examples include:

MHI2_ER_AU57x_

MHI2_ER_AUG11_

MHI2_ER_AUG22_

MHI2Q_ER_AUG22_

The complete branch should remain consistent unless a specific conversion or migration procedure has been verified for the exact hardware.

Examples of firmware currently available in the MMIUpdates catalog include:

MHI2_ER_AU57x_K3663

MHI2_ER_AUG22_K3346

MHI2Q_ER_AUG22_P5092

Different Audi models can use different MIB2 hardware despite having almost identical screens and controls.

For detailed MHI2 and MHI2Q firmware installation information:

Can MHI2 Be Updated to MHI2Q?

No standard firmware update should be treated as a way of turning one hardware family into another.

MHI2 and MHI2Q identify different MIB2 platforms.

Likewise:

MHS2 is not MHI2.

MH2p is not MHI2Q.

MIB3 is not a firmware upgrade for MIB2.

Changing infotainment generation generally requires different hardware rather than simply installing a higher-numbered software package.

Audi MHS2 Firmware

MHS2 is another MIB-based platform found in selected Audi vehicles.

Software versions normally begin with:

MHS2_

Examples include:

MHS2_ER_AU_P0120

MHS2_EU_AU_K0129

MHS2_ER_AU_P0433

MHS2_ER_AU_K0461

MHS2_ER_AU_K0465

MHS2_ER_AU_K0471

MHS2_ER_AU_P1232

MHS2_ER_AU_K1240

MHS2_ER_AU_P1242

MHS2_ER_AU_P2035

A current firmware option is:

MHS2_ER_AU_P2035
MU0235

Firmware:

We also maintain a dedicated MHS2 firmware and navigation guide:

MHS2 should never be treated as MHI2 simply because both systems belong to the MIB2 generation.

Audi MH2p / MIB2+ Firmware

Later Audi models can use MH2p software.

Examples of branches you may encounter include:

MH2p_ER_AUG33_

MH2p_ER_AUG35_

MH2p_ER_AU_

A current example is:

MH2p_ER_AUG35_P2873

Firmware:

There are several MH2p hardware and software branches, so do not select P2873 only because another Audi model uses the same final version number.

Always compare the complete train.

Installation guide:

Audi MIB3 Firmware

Newer Audi vehicles can use MIB3, commonly identified by software beginning with:

MHI3_

MIB3 belongs to a newer hardware generation and must be treated separately from:

MHI2
MHI2Q
MHS2
MH2p

A firmware file designed for MHI3 cannot be used to convert an older MIB2 unit into MIB3.

If your software begins with MHI3_, search specifically for the exact MHI3 software branch installed in the vehicle.

Why the Full Firmware Version Is So Important

A common mistake is sending us only:

Audi A6 2015

or:

Audi Q5 2017

That is not enough to identify the firmware.

Depending on equipment, production date and market, similar vehicles can have different MMI systems.

A useful firmware version looks like:

BNav_EU_P0029_D1

HNav_EU_P0022_D1

HN+_EU_AU3G_P0814

HN+R_EU_AU_P0770

RMC_EU_P12321

MHI2_ER_AUG22_P1234

MHI2Q_ER_AUG22_P4171

MHS2_ER_AU_P1242

MH2p_ER_AUG35_P2711

The beginning of the train identifies the software family.

The final part identifies the particular software release.

Firmware and Navigation Maps Are Different Updates

Firmware is the software that operates the MMI system itself.

Navigation maps are the geographical database used by the navigation system.

They should not be confused.

For example:

BNav_EU_K0260_1_D1 = MMI 3G Basic firmware

5.36.1 / 4G0060884AN = MMI 3G Basic European navigation maps

HNav_EU_K0257_6_D1 = MMI 3G High firmware

6.36.0 / 8R0051884KL = MMI 3G High / Plus European navigation maps

MHS2_ER_AU_P2035 = MHS2 firmware

P350_N60MIBSCALE1 = MHS2 European navigation map package

The fact that a newer map exists does not automatically mean you need to install a different firmware package.

Compatibility must be checked first.

Current European Navigation Guides

If you are looking for maps rather than firmware, use the appropriate map guide.

MMI 3G Basic / BNav:
https://mmiupdates.com/news/last-mmi-3g-basic-europe-map-update-5-36-1/

MMI 3G High / Plus:
https://mmiupdates.com/news/audi-mmi-3g-2023-map-update-6-36-0-8r0051884kl/

MIB2 map compatibility:
https://mmiupdates.com/news/audi-mmi-mib2-2024-updates-available/

MIB2 map installation:
https://mmiupdates.com/tutorials/audi-mib2-map-update-manual/

MHS2:
https://mmiupdates.com/news/audi-mhs2-2023-europe-map-update/

MH2p Europe maps:
https://mmiupdates.com/news/audi-mh2p-europe-2026-2027-p0810-map-update-is-now-available/

Does a Firmware Update Add Apple CarPlay or Android Auto?

Usually, firmware and feature activation should be treated as separate operations.

Installing newer firmware does not automatically mean Apple CarPlay or Android Auto will become available.

On some compatible MIB2 systems, the correct firmware is part of the preparation for Audi Smartphone Interface activation, but the exact activation method depends on the hardware and software branch.

Older MMI 3G systems do not gain native MIB2 functionality simply by installing newer firmware.

For compatible older MMI systems, an aftermarket CarPlay / Android Auto interface is another option.

Can I Install Firmware From Another Region?

Do not change firmware region unless you are intentionally performing a supported region conversion.

European, North American and Rest of World configurations can differ in:

navigation data
radio settings
online services
languages
licensing
hardware configuration
software branch

A US-to-Europe conversion is not the same procedure as a normal firmware update.

If your current software starts with a US or NAR branch, do not simply install an EU package because the car is now physically located in Europe.

Should I Always Install the Highest Firmware Number?

No.

A larger number does not automatically mean that the package is correct for your MMI.

For example, comparing:

K0260
K0942
P1001
P2035
P2873
P5092

is meaningless when they belong to different hardware families.

The correct order is:

  1. Identify the complete current software train.
  2. Determine the exact MMI family.
  3. Verify the region.
  4. Verify the hardware branch.
  5. Check the supported update path.
  6. Only then select the target firmware.

Safe Firmware Update Preparation

Before starting any firmware update:

  • verify the complete current software version,
  • make sure the update package matches the system,
  • read the instructions supplied for that exact platform,
  • use reliable update media,
  • fully extract multipart archives before copying files,
  • keep the vehicle electrical system stable,
  • and never interrupt the system while firmware is being written.

Do not blindly enable every item in User Defined mode.

Do not copy instructions from a different MMI generation.

Procedures that are correct for MMI 3G may be completely wrong for MIB2 or MH2p.

BOSE and Bang & Olufsen Systems

Audio equipment deserves additional attention during some firmware updates.

Depending on the Audi model, MMI generation, amplifier and update package, BOSE or Bang & Olufsen components may require special handling.

There is no single rule that applies to every Audi.

Do not automatically select or deselect amplifier-related components because a generic online guide tells you to.

Follow the procedure for the exact package and vehicle configuration.

MMI Cannot Find the Firmware Update

If the MMI displays:

No update device found

or does not show the update at all, first check the basics.

A common problem is incorrect archive extraction or an additional parent folder on the SD card.

For example:

SD CARD
└── HN+R_EU_AU_P1001
└── update files

may be wrong if the actual update files are supposed to be located directly at the root of the card.

We have a separate troubleshooting guide here:

Firmware Update Installation Guide

For MMI 3G firmware installation:

For MIB2 MHI2 / MHI2Q:

For MH2p:

For the general update workflow:

Find the Correct Firmware for Your Audi

If you already know the complete software train, the fastest option is our update checker:

Enter the complete version exactly as displayed by the MMI.

For example:

HN+R_EU_AU_P0770

not simply:

P0770

The complete version gives us the information needed to distinguish the platform, hardware family and region.

Browse Audi MMI Firmware Updates

You can also browse the complete Audi firmware catalog:

https://mmiupdates.com/product-category/audi-mmi-update-firmware

However, always verify compatibility before choosing an update.

The Audi model and year should be treated as supporting information, not as the primary method of firmware identification.

Frequently Asked Questions

How do I know which Audi MMI firmware I need?

Check the complete software version in Version Information and identify its prefix, such as BNav, HNav, HN+, HN+R, RMC, MHI2, MHI2Q, MHS2 or MH2p. Then match the complete software branch rather than selecting firmware only by vehicle model.

What is BNav_EU_K0260_1_D1?

BNav_EU_K0260_1_D1 is firmware for compatible European Audi MMI 3G Basic systems.

What is HNav_EU_K0257_6_D1?

HNav_EU_K0257_6_D1 is firmware for compatible MMI 3G High systems.

What is HN+_EU_AU3G_K0942?

It is an MMI 3G Plus firmware release used with compatible HN+ European systems.

What is HN+R_EU_AU_K0942_4?

It is a firmware release belonging to the European HN+R MMI 3G Plus family.

What is HN+R_EU_AU_P1001?

HN+R_EU_AU_P1001 is another firmware release for compatible European HN+R MMI 3G Plus systems.

Is HN+ firmware compatible with HN+R?

Do not assume so. HN+ and HN+R are separate software branches. Always match the complete train.

What is RMC_EU_K16158?

It is firmware offered for compatible European RMC NAV-RADIO PLUS / RMC2 systems. Hardware compatibility must also be verified.

What is MSTD_EU_AU_K3151?

It is a software train from the MIB1 Standard family. It is not interchangeable with MHIG or later MIB2 firmware.

What is MHIG_EU_AU_P1531?

It belongs to the MIB1 High software family.

What is the difference between MHI2 and MHI2Q?

They identify different MIB2 hardware/software families. Firmware must match the exact branch.

Is MHS2 the same as MHI2?

No. They are different MIB platforms and require different firmware.

What is MHS2_ER_AU_P2035?

It is firmware for compatible MHS2 systems.

What is MH2p_ER_AUG35_P2873?

It is firmware for compatible MH2p / newer MIB2 platform units using the AUG35 software branch.

Can MMI 3G be updated to MIB2 with firmware?

No. MMI 3G and MIB2 are different hardware generations. Moving from MMI 3G to MIB2 requires a hardware retrofit rather than a normal firmware update.

Are firmware and navigation maps the same thing?

No. Firmware controls the MMI system. Navigation maps are a separate database.

Do I need to update firmware before maps?

Sometimes, but not universally. It depends on your current firmware, target map package and MMI system.

Does a firmware update activate Apple CarPlay?

Not automatically. CarPlay availability and activation depend on the infotainment hardware and software platform.

Can I install European firmware on a US Audi?

Not as a normal firmware update. Region conversion is a separate procedure and must be verified for the exact MMI.

Can I choose firmware by Audi model and production year?

No. Those details help narrow down the possibilities, but the complete software version should be used for compatibility verification.

Where can I check which MMI update is correct?

Use:
https://mmiupdates.com/check-upgrade/
and enter your complete current firmware version.

Adam Ignaczak

Adam Ignaczak is the founder of MMIUpdates.com and an independent Audi infotainment specialist. Since 2017, he has worked with Audi MMI firmware, navigation maps, MMI 3G, MIB, MIB2, MHS2, MHI2 and newer infotainment platforms, focusing on compatibility, update procedures and troubleshooting.
Subscribe
Notify of
guest

0 Comments