Region conversion to EU on MIB units: procedure and firmware path
Applies to: MHI2; MHI2Q; MIB2; MIB2.5; MHS2; MST2; MH2P; MHIG; MHI3; MMI3G+
Converting a non-EU MIB head unit (US, Japanese, Korean, Taiwanese, Chinese or ROA) to the European region is one of the most common modifications owners attempt. The goals are usually EU maps, EU radio band, extra languages, CarPlay/Android Auto or access to patches that only exist for EU trains. The EU firmware will not simply install on a unit set to another region. The variant and train must be changed first, or the region check must be bypassed. Many post-conversion faults trace back to skipped steps, the wrong package or leftover US datasets. This article collects what owners report about the procedure, the firmware path and the faults that appear afterwards. It is grouped by platform, because MHI2/MHI2Q, MHS2 (Delphi), MST2, MH2P and MHI3 each behave differently.
How to recognise the situation
The unit's software train shows a non-EU region code, for example MHI2_US_..., MHI2_JP_..., MHI2_KR_..., MHI2_TW_..., MHI2_CN_..., MHS2_US_..., MST2_US_... or a ROA variant.
Typical signs that a conversion is needed or has gone wrong:
- An EU package on the SD card is ignored, or the software download menu reports that the device does not support the region.
- A Standard update refuses an EU train because the installed US version number is higher.
- The 'User defined' option is missing or greyed out in the red engineering menu.
- After a partial conversion, languages stay limited (for example English and Spanish only), the radio plays only static, menu text is missing or there is no audio.
- FEC codes still show an NA region, navigation is disabled, or a nav database update fails with error F/E15.
Before you start
Conversion involves flashing firmware, changing EEPROM values and rewriting coding and datasets. Owners who did not prepare often ended up restoring the unit from backups or over UART/D-Link.
- Write down the current train, MU version, part number and hardware variant (for example AU37x vs AU57x, VWG11 vs VWG13).
- Back up coding, adaptations and datasets with your diagnostic tool, and take an M.I.B. backup of the unit before any change.
- Connect a stable external power supply. Full SWDL updates are reported to take roughly 30-40 minutes.
- Never abort a software download. One report of an aborted update left the unit showing the EU train while menus and languages stayed US.
- Use a freshly formatted FAT32 SD card with freshly downloaded files. Bad images and incomplete cards caused failures, including a TNRREF error.
- Check the supplier of the unit (Harman, Technisat, Delphi, Aisin and so on). Aisin-built JP units follow a different conversion path.
- Read the full conversion guide for your platform on the MIB wiki before starting.
Why EU firmware will not install directly
The update process checks the unit's region and variant, stored in EEPROM, against the region list in the package's metainfo. If they do not match, the package is rejected. The fix is one of three approaches:
Owners also report that an update cannot normally go to a lower version number. A US unit on a newer IFS root, for example P4246, may therefore refuse an EU train such as P5092 in User defined mode.
- Change the variant and train to EU, using the M.I.B. toolbox GEM functions, an EEPROM editor, mibtool over telnet, D-Link/UART or, on Porsche, PIWIS.
- Enable SWDL with the 'ignore region/variant' option so the check is bypassed during the update.
- Edit the metainfo region list (and supported trains on MH2P) so the unit's current region is accepted.
MHI2 / MHI2Q procedure as most owners describe it
Owners use several variants of this sequence. The order below is the one most often described. Some owners change the train first and flash afterwards. Others flash with ignore-region or a custom meta first and run the conversion afterwards. Both are reported to work.
- If the unit is on very old firmware, update it within its own region first. Setting the train to EU on old firmware gave a 'Memory fault (core dumped)' error, which was resolved by updating to the newest firmware. Some guides also update a US unit to a higher US train first, such as MHI2Q_US_AUG22_P5087 or a US 3324_1 build on AU57x.
- Enable developer mode in the red engineering menu and install the M.I.B. toolbox from SD so it appears in GEM. Owners reported problems with M.I.B. version 3.6.0 and used 3.5.0/3.5.1 or a later release instead.
- In GEM > M.I.B. > Advanced settings, run the EU conversion of the train (EU_conversion_train), then the EU conversion coding steps. Wait for the automatic reboot. Some guides also run Format_nav_db at this stage.
- In Advanced settings, enable SWDL and ignore region/variant. Do not restart the unit at this point.
- Return to the main menu and open the red engineering menu. Choose the software update, select User defined and set all items to Y. Set the Bose item to N (deselect Bose) on cars with Bose, or if the unit has no Bose. Owners report no sound or other trouble when the Bose part was flashed. On some AU57x cars with Bose and no VCP, owners disconnected MOST instead.
- After the EU firmware is installed, format the navigation partition, for example the internal memory format in module 5F via VCDS/VCP/ODIS or the Format_nav_db option.
- Reinstall M.I.B., take a new backup and patch the unit for the new train. Rewrite EU FECs, then install EU maps.
- Code EU options and load EU language datasets/parameters with VCP or ODIS if needed. Finish with a factory reset (Settings > Factory settings > Select all).
Choosing the target firmware
Pick an EU train for the same platform and hardware variant as the unit. Owners report the following targets for conversions. Confirm the right one for your unit against the MIB wiki and the version the M.I.B. tool reports. Use the MU version that belongs to the train, and never pair a train with a different MU.
- Audi MHI2Q (A4/A5/Q5/Q7): MHI2Q_ER_AUG22_P5092_MU1329 is the most frequently reported target. Owners whose converted unit had no public patch, for example P3638, moved to P5092.
- Audi MHI2 AUG22 (for example Q7 4M from MHI2_US_AUG22_P3252): MHI2_ER_AUG22_K3346 (MU1438). During that update a tuner prompt may appear repeatedly. Because 3346 contains no tuner files, choosing Cancel/Skip let the install finish.
- Audi A6/A7 AU57x: MHI2_ER_AU57x_K3663. Use the 57x package on a 57x unit. One owner's SD card was not recognised because a 37x file had been used.
- VW MIB2 (VWG11): MHI2_ER_VWG11_K3342. For MIB2.5 (VWG13) owners mention K4525 and similar builds.
- Porsche Macan PCM4 from MHI2_US_POG11_P4255: MHI2_ER_POG11_K5126 or its AIO build. The variant must be changed before the SD update is accepted.
- VW MHIG (JP units): MHIG_EU_VW_K1550, installed as a normal update after running the M.I.B. EU convert option.
AIO packages: conflicting advice
Owners disagree about using all-in-one (AIO) images such as MHI2_ER_AU57x_K3663_1_MU1425_AIO for a conversion.
Several reports say the AIO image is meant for updating units that are already EU. In their experience it is not suitable for US/KR/JP-to-EU conversion: a unit froze after an AIO-based JP-to-EU conversion, and these owners recommend the standard K3663 package with user-defined options instead. Other reports say an AIO image combined with the M.I.B. toolbox handled EEPROM, coding and datasets without manual editing. One owner hit error DUV624 after skipping the AIO step. All sources agree that the variant and train must already be EU before an AIO image will run.
When User defined is missing or the downgrade is refused
These workarounds are reported for MHI2/MHI2Q:
- Look in the red engineering menu, not the green menu. Enable SWDL and ignore region/variant in GEM first, then return to the main menu and open the red menu.
- On cars with Bang & Olufsen, User defined was greyed out. Running a Standard update first, then enabling SWDL with ignore and setting all user-defined items to Y, worked in a confirmed report. Bose units are said not to have this problem.
- If the installed US IFS root is newer than the EU target, owners either flashed the target's IFS-ROOT first or did a Standard update to the EU train. They then rebooted, repeated the ignore region/variant step and ran User defined with everything selected. One report also mentions adapting 5F channel 45 to active so that User defined appears.
- Other options mentioned are a modified metainfo or a manual reflash over D-Link. The emergency update path was not recommended.
Faults after an MHI2 conversion and reported fixes
Most post-conversion faults come from datasets, coding or EEPROM values that still describe the old region.
- Radio plays static and the frequency setting is missing: a full factory reset fixed it in a confirmed report.
- Radio stations not stored after ignition off (MIB2.5): a factory reset was suggested.
- Unit misbehaves after an update done with ignore variant: change the EEPROM variant to EU and code RSDB to 1, without reinstalling the software afterwards (confirmed by one owner).
- Languages stay English/Spanish only: load the correct EU language datasets and complete the coding.
- Speech check timeout or checksum error: load the 0x002D00 and 0x000280 datasets matching the installed package. In another case, re-running the update with only SpeechRes selected was suggested.
- FEC shows NA region and maps are disabled, or the nav update fails with F/E15: redo the conversion with M.I.B., rewrite EU FECs and verify that coding is set to EU. The built-in conversion does not always change coding, especially on older software.
- No audio, no car image, volume 'currently unavailable', or 5F unreachable after a JP-to-EU flash: owners restored coding and adaptations with a VAS5054 or re-ran the EU conversion from M.I.B. One report of 5F not being readable via VCDS/ODIS blamed a variant mismatch and suggested a full SWDL update plus re-patching. That advice was disputed.
- Firmware installs fail and ODIS cannot see the unit after a train change: mismatched RCC/IOC/MMX components were blamed. The suggested fix was correcting the components manually from emergency mode, using /tmp/version.txt to identify them.
- GEM no longer opens and the map view looks wrong: check whether the update list is empty, then redo SWDL with all items selected manually.
MHS2 (Delphi) units
MHS2 conversions follow a different route. Owners report updating the US unit to the intermediate MHS2_US_AU_P2037 first, for example from MHS2_US_AU_P0463. The US2EU conversion is then applied from the MIB wiki/MIB Solution files, either from SD (the 'extract to SD' instructions) or via D-Link with VCP or ODIS-E. Simply changing the region setting does not work.
After the unit accepts ER firmware, owners run a normal update from the red menu without changing user-defined items. They then upload the language XML, install FECs, format the nav partition with an OBD adaptation tool, update EU maps and code EU settings. One owner reported that WiFi, and with it wireless CarPlay, worked again after the maps update.
- Incoming call audio only on the phone after moving from MHS2_US_AU_P2037 to MHS2_ER_AU_P2035: restoring the original sound dataset was suggested.
- Do not copy a full dataset from a car with a different sound system. Owners transferred only the first-language (0280) and general-language (2D00) datasets.
- Unresolved: one owner found the CAR menu (TPMS, service, drive select, climate) inactive on every EU train tried, while US trains kept it working.
- Unresolved: running the US2EU script over telnet and restarting left one unit still booting the US version.
MST2 / PQ units
On MST2, the EU package's metainfo must match the unit. Owners enabled telnet (MST2 activator), backed up the unit, then edited the metainfo region and variant to suit it, picking the correct STD, PLUS or NAV variant. A PLUS unit failed until files from the PLUS folder and the matching meta were used.
Reported examples include MST2_US_VW_P0890D to MST2_EU_VW_P0891D and EU targets such as MST2_EU_VW_P0879D. Map FECs may need re-patching afterwards. Some US units have telnet disabled and a newer variant, for example part number 2GM035844. For these, owners describe EEPROM/variant programming or writing a full EU eMMC image via OTG or an eMMC programmer instead.
- Some composition media units accept only two US firmware versions. Owners advise keeping the US firmware there and coding the EU radio and EU language with VCP, because flashing EU risks bricking.
- Unresolved: a 2018 Tiguan showed 'Phone unavailable' and lost the Bluetooth icon after conversion.
- Unresolved: one unit booted with no update applied after a 0891 SWDL. It was recovered by restoring the IM from backup.
- Unresolved: after a US2EU patch and metainfo edit, one P0253T unit offered no train to select.
Other platforms
The notes include a few platform-specific reports outside MHI2, MHS2 and MST2.
- MH2P: if the EU firmware will not install after using the MH2P toolbox, edit main.mnf so the current US train is in the supported trains list (or blank the list), reboot and retry. For an A8 conversion, owners went straight to the newest EU train, MH2P_ER_AUG35_P2873, rather than the EU equivalent of the installed US version.
- MHI3: no radio sound or stations after changing the variant to EU was blamed on the CP firmware still being US. The suggestion was to keep the variant and CP on US.
- MMI3G+/HN+: a unit stuck on the Audi logo after a JP-to-EU flash was still in SWDL mode. Deleting /HBpersistence/SWDL/update.txt via IPL/UART access fixed it (confirmed). Missing menu text after a conversion is usually solved by uploading the EU language dataset.
- Audi Q5 simple radio (no MMI): owners flashed RG3_ECE_0480 with ODIS or VCP like any other control module. This takes 30-40 minutes on a battery supply.
What did not help or is disputed
Some approaches failed for owners or remain contested.
- Using AIO packages for the conversion itself, according to several owners (see the AIO section).
- Selecting every item in a full SWDL is debated. Some owners select all except Bose. Others say selecting all causes problems on MHS2/MHI2 and prefer classic SWDL with checkIfNotEqual or only the required sections.
- A full SWDL with all items did not fix English speech/navigation commands in one case.
- Re-flashing the EU dataset with ObdeleVen to fix wrong-looking menus was reported as unreliable, and the advice to use ODIS/VAS instead was disputed.
- Changing the train alone as the first step, without the following variant and SWDL steps, did not complete a JP-to-EU conversion.
Frequently asked questions
- Do I need to edit the EEPROM, or is ignore region enough?
- Reports differ by platform. On MHI2Q, owners say SWDL with ignore region plus a User defined update is enough, with no EEPROM change. On other MHI2 units the variant and train are changed first with the M.I.B. toolbox or an EEPROM editor. If the update was done with ignore variant and the unit misbehaves, correcting the EEPROM variant to EU afterwards was confirmed to help.
- Should the Bose item be included in the update?
- Most owners deselect Bose in the User defined list. Flashing it was linked to no sound after conversion. On some cars with Bose and no VCP, owners disconnected MOST during the update instead.
- Why does the unit refuse the EU train even with User defined?
- The installed US version may be newer than the EU target. Owners resolved this by flashing the target IFS-ROOT or doing a Standard update to the EU train first, then repeating the ignore region/variant step and running User defined.
- Will EU maps work straight after flashing EU firmware?
- Usually not. Owners format the navigation partition, re-patch the unit, rewrite EU FECs and verify EU coding before loading maps. Leftover NA FECs or wrong coding produce errors such as F/E15.
- Can a converted unit go back to its original region?
- Owners have restored the M.I.B. backup in the green menu and installed the original-region software from the red menu. This is one reason to take a backup before converting.