Map update blocked until the unit is patched, updated or given a valid map FEC
Applies to: MHI2 / MHI2Q (Audi MIB2 High, also Porsche and VW); MHIG (MIB1 High); MHS2 (Audi MIB2 Standard, Delphi); MST2 (VW, Skoda, SEAT Discover Media / TechniSat); MSTD; MH2P; MIB1; MIB3; MOI3
A common problem across MIB head units is that a new map package will not install, is not found, or is rejected outright. In most reported cases the cause is not the map files themselves but a missing or limited map licence (FEC) on the unit, a firmware train too old for the map package, or a patch that has not been applied or does not match the installed train. This article explains how to recognise the problem, how to check what the unit has, and the order of steps owners report as working on each platform.
How to recognise the problem
The map update either never starts or the unit reports that no suitable update is available, even though the map folders are on the card. The exact message varies by platform and menu.
- Map installation does not start, or a warning says the update is not possible.
- The update menu reports no map updates found, nothing on the SD card to update, or no medium file.
- The unit reports no valid licence to update the maps.
- MST2 navigation asks for a card with valid data after a newer map pack is inserted.
- Engineering-menu updates show question marks instead of the map package (reported on an older TT Mk3).
- MIB1 units report an error while reading the new map data.
- A firmware or map install fails with a train support error.
- The old map keeps working, but the newer map version is never offered.
Likely cause
Each unit carries feature enablement codes (FECs). One of them is the map licence. It controls which map releases the unit will accept. Owners report the following causes:
- No map FEC, or only a time-limited one. On MHI2 a limited code such as 02300032 blocks newer maps. The lifetime map code 023000EE is normally added by patching the unit.
- Firmware updates do not add map FECs. The map FEC is separate from the firmware. A unit can still refuse maps after a firmware update.
- The firmware train is too old for the map package. Owners report navigation stopped working after installing maps on firmware that was too old.
- The patch does not match the installed train. A patch built for a different firmware build does not apply. One example is using a P5152 patch on MHI2Q_ER_AUG22_P5092.
- Map FECs are tied to the unit family. An MSTD map FEC will not install on MHIG.
- On MIB3, the map year is reported to be encoded in the FEC. 02100034 is given as the minimum for 2024 maps.
- The SD card is wrongly formatted or the files were not fully extracted.
Before changing anything
Patching, adding FECs and updating firmware all change the head unit's software or coding. Take these precautions first.
- Write down the current firmware train (for example MHI2_ER_AUG22_K2161) and the unit's part number from the version information or the green or red engineering menu.
- Back up coding and adaptations with your diagnostic tool.
- Create the toolbox backup. Owners consistently run the backup before any patch.
- Keep a stable power supply. Connect a charger or power supply for firmware and map installs. Owners report around 30 minutes for firmware and 40 minutes for maps on MHI2.
- Only use patch files that match your exact train. Do not flash files intended for another train or brand.
Step 1: Check which map FEC the unit has
Check the unit's current licences before deciding whether a patch or firmware update is needed. If the map FEC already ends in EE, owners report the unit is ready for map updates without further patching.
- Open the red engineering menu, then System, then Activation keys, then show installed.
- Alternatively, display the current FEC codes in REM.
- If the maps FEC shows EE, go straight to installing the maps.
- On some Audi MIB2 units the map package depends on the installed firmware variant. One confirmed report says to install P370 maps if 3663_1 is listed and P350 maps if it is not.
Step 2 (MHI2 / MHI2Q): Patch on the matching train, then install maps
This is the most frequently reported fix. Firmware updates are optional when a patch exists for the installed train. Owners kept MHI2Q_ER_AUG22_P3638, MHI2Q_ER_AUG22_P5092 and MHI2_US_POG11_P5103 and only patched.
- Copy the toolbox and the patch set for your train to a FAT32 SD card.
- Install the toolbox from the red engineering menu and leave the card inserted.
- Run the backup and wait for it to finish.
- Run the all-in-one patch (patch_unit_aio). Patching adds the valid FECs, including the lifetime map code, automatically. Owners report that adding FECs separately afterwards is not needed.
- If an SVM fault code appears after patching, owners cleared it with the toolbox's SVM script.
- Copy the maps to a FAT32 SD card and install them.
- If no patch exists for your train, update firmware first. Examples reported include MHI2_ER_AUG22_P2133, MHI2_ER_AUG22_K2156, MHI2_ER_AUG22_S2116 and MHI2_ER_AUG22_S2148. K2161 is the commonly named target, followed by patching and installing the maps.
- Units with Bose sound: one confirmed report says patching worked normally after ignoring the region/variant warning. Another note suggested patching after K2161 only on units without Bose. The advice is not consistent.
Step 2 (MHIG / MIB1 High): Add the map FEC
On MHIG the EU map licence is reported as 09100008 or 091000EE. Owners add it over OBD or via a D-Link adapter, or by patching with the toolbox.
- Add the EU map FEC, then patch with the toolbox once the FEC is valid.
- One report found a 2024 map update still found no files because a third FEC (40100) was missing. Adding it fixed the issue in that case.
- In that case the owner formatted the NaviDB in GEM with user.defined and ignore.region.and.variant ticked. The update was then run from REM with user-defined and Select All.
- Older trains may need a firmware update first. Reported examples are MHIG_EU_AU_S1531 to 1549, MHIG_US_AU_S2014 to K2019, and a confirmed direct jump from K0337 to MHIG_EU_AU_K1555.
- MHIG keeps a backup FEC set in /mnt/efs-system/backup/FEC. It is worth checking when FECs appear lost after a firmware update.
Step 2 (MHS2): Run the SD activator, then copy maps to the card
MHS2 reads maps directly from the SD card and has no separate map install step. Owners report that a firmware update is not needed unless existing functions have problems.
- Put the SD activator (Congo or the MHS2 Delphi SD activator) on an SD card, insert it and wait until it finishes. Owners report around 5 minutes and an automatic reboot.
- Clear or format the map card, unzip the new maps and copy them to the root of the card.
- Leave the map card in the unit permanently.
- According to one report, firmware 2035 is only needed to reactivate the official Audi Connect satellite maps.
Step 2 (MST2 / MSTD): SD card based units
Reports differ. Some owners simply replaced the maps on the original SD card, and VW units are said to carry lifetime maps. Others hit the valid-data message and needed the SWaP/FEC patch from the toolbox or a prepared SD patch first. Back up the original SD card before changing it.
- If the unit rejects the card, apply the SWaP/FEC patch with the toolbox or an SD patch, then copy the maps to a FAT32 SD card.
- Without a patch, the card's CID must match. A patch that removes the CID check allows any SD card.
- Full Europe needs a 32 GB card. Other zones fit on 16 GB, or some countries can be removed.
- If the installed map database is too old for the normal update (reported after updating to MST2_EU_VW_P9122D), format the navigation database. Do a first manual map install, then run the normal update.
- ZR units on non-EU trains: one report converted to the EU train, installed EU FECs, then updated to MST2_EU_VW_ZR_P0369T before patching.
- MSTD: one report says newer maps on a VW/SEAT MSTD unit (MSTD_EU_SE_P5310) required patching, adding Audi FEC 022000ee and changing the brand coding to Audi. Back up coding before doing this.
Step 2 (MH2P, MIB3, MOI3)
These platforms are less frequently reported.
- MH2P: maps can be installed without a firmware update. Use an exFAT card, not FAT32.
- MH2P: if the update is not offered, format the navigation database with a diagnostic tool.
- On Touareg, one report says to update to K0824 first. The standard menu cannot start the map update there, so a telnet install script was used instead.
- MIB3: patch the unit with the toolbox, then install maps from the red menu. Owners note a firmware update is not required for maps.
- MOI3: run the navigation patch from the TechniSat toolbox customisation menu, then install the maps.
SD card and menu tips
Several failures came down to card preparation rather than licences.
- Use FAT32 for toolboxes and patches. Windows cannot format cards larger than 32 GB as FAT32, so use a GUI formatter.
- Use exFAT only where the platform requires it, such as MH2P maps.
- Re-extract archives fully and check the folder and file count. Missing files cause a nothing-to-update result.
- Some owners only succeeded through the normal settings update menu rather than the red menu. Others use REM on the bench because it needs no ignition signal. If one route fails, try the other.
What did not help
Owners reported the following as ineffective.
- Updating firmware alone: it does not add the map FEC.
- Using a patch built for a different train or build.
- Using an MSTD map FEC on an MHIG unit.
- On MHI2_ER_AUG22_K2156, the toolbox asked for a patch not present in the patch database. The workaround was moving to K2161.
- On one MHIG_EU_AU_K1555 unit, patch_unit_aio and the SVM fix left the FEC unchanged (0210001c), and the map update stayed blocked. No resolution was reported.
- Installing a newer map package on old firmware left navigation not working in one report.
Frequently asked questions
- Do I need to update firmware before installing new maps?
- Usually not, if a patch exists for your current train. Update firmware first only if no patch exists for your train or the map package needs a newer train. On MHI2, K2161 is the commonly named target.
- How do I know whether my unit is already patched for maps?
- Check Red menu > System > Activation keys > show installed, or the FEC list in REM. If the maps FEC ends in EE, owners report the unit accepts new maps.
- Can I just copy new maps to the original SD card without a new FEC?
- This is disputed. Some MST2 owners on VW units report it works because of lifetime maps. Other units reject the card until patched.
- Do I need to add FECs manually after patching an MHI2?
- Owners report the all-in-one patch adds the required FECs itself. A separate step to add FECs is not needed.
- Does a firmware update restore lost map FECs?
- No. Map FECs are separate from firmware. On MHIG, check the backup FEC folder and re-add or patch as needed.