Update refused on a large version jump: following an intermediate update path
Applies to: MHI2 (Harman MIB2 High: VWG11, AUG22, AUG24/AU43x, AU57x, US AUG22); MHI3; MIB3 / MOI3; MST2 Technisat (PQ and ZR); MST2 Delphi; MHS2; MHIG (MIB1 High)
A firmware update that is rejected with an error, a 'version too old', 'unsupported train' or 'train blocked' message, or a downgrade warning usually means the target release does not accept the train currently installed. VW Group head units only install a package when the current train is on the package's supported list, so older units often need one or more intermediate releases first. This article covers how to recognise the problem, why it happens, the stepwise paths owners report for common platforms, and what did not work. Treat the paths below as reported experience, not guarantees, and always verify against the metainfo of the package you actually hold.
How to recognise the problem
The unit starts reading the update medium but refuses to install, or the update aborts early. Owners describe several variants of the same underlying issue.
- A generic error when selecting the new release in the update menu or red engineering menu.
- A message that the current version is too old, or that the train is unsupported or blocked.
- A downgrade warning even though the target looks newer by its number.
- An update that stalls or gets stuck partway through.
- After an apparently successful step, a component such as RCC is shown as NOK, or the train changes but the software MU version does not.
- On MIB3/MOI3, navigation stops working after jumping releases.
Why the update is refused
Each firmware package carries a metainfo2.txt file whose SupportedTrains entry lists which installed trains it will accept (sometimes with wildcards such as MHI2_ER_VWG13_*). If the installed train is not listed, or is listed as blocked, the update is refused. For example, owners report that MHI2_ER_VWG11_P3301 accepts any MHI2_ER_VWG11 train, while MHI2_ER_VWG11_K3342 lists P3301 but not older builds such as MHI2_ER_VWG11_S2125_1. Similarly, a K3346 package was reported to list P2133 but not MHI2_ER_AUG22_S2133.
Build numbers are not always chronological. MHI2_ER_AUG22_P3241 is older than MHI2_ER_AUG22_K2161, so installing it on a K2161 unit is a downgrade. On Delphi MST2 units the 08xx releases were not issued in numerical order. The letter prefix (S, P, K) on its own was reported not to block an update.
Some limits are hardware, not software. Early MST2 units on 01xx firmware have less RAM and owners report they cannot move to 02xx (P0138T can go to P0140T at most). First-generation Delphi PLUS 02xx units and non-navigation Delphi hardware were reported to brick if given 08xx firmware. These cannot be solved with an intermediate step.
Before flashing anything
Several fixes below involve firmware flashing, SWDL patches or edited metainfo. Take precautions first.
- Note the current train, MU version, hardware version and part number from the version screen or a diagnostic scan.
- Back up coding and adaptations. Where a toolbox is already installed, owners recommend taking a full backup before updating further.
- Keep a stable supply: use a battery maintainer, or keep the engine running where owners report that this was done. MHI3 dealer-style updates were reported to take about four hours.
- Open the target package's metainfo2.txt and check SupportedTrains against your current train before starting.
- Make sure the package matches your platform and region: PQ and ZR builds are not interchangeable, and an Asia build such as MHI3_ER_AU_P4398 is not the EU line.
- Expect existing patches, FEC/SWaP activations and CP-off changes to be removed by an update; plan to repatch afterwards.
MHI2 VWG11 (VW Harman)
The most commonly reported path from older builds such as MHI2_ER_VWG11_S2125_1, S0259, P2103 or P2125 is to install MHI2_ER_VWG11_P3301 first and then MHI2_ER_VWG11_K3342. A direct P2125 to K3342 attempt that gave an error succeeded via P3301.
Alternatives reported: some owners prefer stopping at MHI2_ER_VWG11_K3332, describing it as smoother or more stable than K3342; others go straight to K3342 using an edited metainfo that adds the current train. One note warns that K3342 broke USB on Passat units fitted with a USB hub.
- Read SupportedTrains in the P3301 and K3342 packages.
- Update to P3301 by SD card.
- Update to K3342 (or K3332), then patch if required.
- If the version screen shows the new train but the MU version has not changed and the FEC/SWaP menu is missing, one owner resolved it by turning ignition on, emptying both SD slots, inserting the card in SD1, holding MENU for three seconds and cancelling the documentation prompt.
MHI2 AUG22 (Audi A4/A5/Q7 and similar)
From older builds (MHI2_ER_AUG22_S2140, S2133, S2116, K2140 and others) the first step is MHI2_ER_AUG22_K2161. Many owners stop there, as it is reported to be sufficient for full functions and patching. Units with Bose audio were reported to need an edited metainfo, or to keep the Bose step selected, depending on the note.
To go beyond K2161, the confirmed route is K2161, then MHI2_ER_AUG22_P3241, then MHI2_ER_AUG22_K3344, then MHI2_ER_AUG22_K3346. Note that P3241 is a downgrade relative to K2161 and can leave RCC shown as NOK; continuing to K3344 resolved this. For the K3344 to K3346 step owners enabled SWDL and chose a user-defined update in the engineering menu, selecting all components and unchecking Bose where fitted. One owner reported a direct S2140 to K3346 jump worked, but most notes say it is refused without editing metainfo.
MHI2 AUG24 / AU43x (Audi TT, R8)
The deciding factor is the LTE/SIM module. If the unit has a SIM slot, owners update to K1074_1 (MHI2_ER_AU43x_P1074_1) first so the LTE module is updated, then to MHI2_ER_AU43x_P5098_MU1339. Without a SIM slot, a direct update to P5098 from builds such as MHI2_ER_AUG24_S0316 is reported to work. One detailed note suggests loading the 1074 package to see whether it would update LTE only, and if so running it for LTE only before P5098 with the B&O option unselected. Custom metainfo for 1074 was used in some cases.
For smartphone/ASI icons, owners also updated the virtual cockpit firmware after the MMI. An R8 owner reported using the TT 1074 package with custom metainfo before moving to P5099.
MHI2 AU57x and US AUG22
From MHI2_ER_AUG11_P0040, one reported sequence is K2589, then P3634, then K3663. Others report going directly to the all-in-one MHI2_ER_AU57x_K3663_1_MU1425_AIO; a direct update from MHI2_ER_AU57x_S2519 to K3663 was confirmed using a FAT32 32 GB USB stick (a microSD in an adapter was not recognised). Do not flash an AU57x package onto an AUG22 base: its SupportedTrains list does not include AUG22.
For US Q7 units, MHI2_US_AUG22_K2162_MU1422 was described as the latest supported target. MHI2_US_AUG22_K3347_MU1439 does not list K2162 in its supported trains, and owners advised staying on K2162.
MHI3
Owners report MHI3 units on P3385 or earlier must go to MHI3_ER_AU_P3620 before MHI3_ER_AU_P3853, by SD card or USB from the engineering menu. A dealer-style route via ODIS with the online TPI and SVM codes covers gateway and telematics as well. Wireless Android Auto not working after reaching P3853 was traced to the telematics firmware not being updated; updating it via ODIS fixed it in a confirmed case.
MIB3 / MOI3
Reported paths: 0156 to 0238 to 0268 to 0278 (all files on one USB stick, one run, confirmed), then 0278 to 0330. From 306, install MOI3_RW_SKMQB_P30800P (308) before 330 or 332; installing P30800P then 332 was confirmed. Skoda owners also report 0270 to 0308 to 0332. Starting a single 330/332 update instead of the sequential one failed for one owner.
Skipping steps was reported to lose navigation and FECs; recovery required updating the OCU and either a dealer FEC or online SVM. For 18xx builds, one owner went 1803 to 1896 to 1940 and advised checking the TPI for the VIN, as a part number change exists around 1896.
MST2 Technisat (PQ and ZR)
Updates within the same family are normally accepted regardless of MU version; 245T to 252T was confirmed. The reported normal ceilings are about 0254 for 02xx, 0369 for 03xx and 0478 for 04xx units.
Crossing families (02xx or 03xx to 04xx, for example MST2_EU_VW_ZR_P0369T to MST2_EU_VW_ZR_P0480T) is refused by a plain update. The approach owners describe is: patch SWDL, edit the target metainfo2.txt to link the unit's CPU/variant, then run a standard (not full) update via SD card, following the published 02xx-to-04xx guide. Owners warn this is high risk if the procedure is not understood. Additional cautions: uncheck DUV in the component list to avoid display problems; Wi-Fi may stop working on 4xx firmware on some hardware; if an original 2xx emergency image remains, uncheck both emergency entries during SWDL. The Technisat emergency update was mentioned as a recovery route after a failed update.
The part number appended to an MST2 file name identifies the update file, not the unit, and does not need to match. Early 01xx units (P0138T) were reported to be limited to P0140T and cannot use CarPlay or Android Auto.
MST2 Delphi
Delphi 08xx numbering is non-linear. The order confirmed by several owners is 0842, 0867, 0870, 0890, 0891, 0876, 0879. MST2_EU_VW_P0879D is generally preferred as the latest usable build; MST2_EU_VW_P0883D was reported to block POI entry. A full SWDL from MST2_EU_VW_P0876D to MST2_EU_VW_P0891D was confirmed.
02xx units typically top out at MST2_EU_VW_P0231D. Moving 02xx to 08xx is reported only for navigation units and requires following the published Delphi 02xx-to-08xx guide; PLUS 02xx and non-navigation hardware were reported to brick. Whether the installation manager must be edited is disputed: some owners say it is never needed, others describe modifying it. One P0227D unit refused P0231D with no resolution recorded.
MHS2 and MHIG
Owners report MHS2 units can go from MHS2_ER_AU_K1240 (or any 1xxx train) directly to MHS2_ER_AU_P2035 without the intermediate P1242. MHIG units on MHIG_EU_AU_S1544 were advised to update straight to MHIG_EU_AU_K1555 via the red menu.
What did not help
- Forcing the newest-looking build directly onto an old train without checking SupportedTrains.
- Installing MHI2_ER_AUG22_P3241 on a K2161 unit and stopping there (downgrade; RCC NOK).
- Flashing an AU57x package onto an AUG22 unit.
- Using a PQ build on a ZR unit or vice versa.
- Trying to move 01xx MST2 hardware to 02xx or higher.
- Running a single 330/332 package instead of the sequential update on MIB3.
- Choosing a file purely because it has the highest number on Delphi units.
Frequently asked questions
- How can a train be checked as supported before flashing?
- Open metainfo2.txt in the target package and read the SupportedTrains entry. If the installed train (or a wildcard matching it) is listed and not blocked, a direct update is expected to be accepted.
- Is editing metainfo an alternative to intermediate steps?
- Owners report editing metainfo to add the current train allowed direct jumps on several MHI2 units, and it is required for MST2 cross-family updates together with an SWDL patch. It bypasses the manufacturer's checks, so back up first and only do it with a documented procedure.
- Will an update remove existing patches and activations?
- Owners report that updating removes FEC/SWaP and CP-off patches, so plan to repatch. Coding itself was reported not to be changed by a firmware update.
- Do the S, P and K prefixes matter?
- Owners report that the prefix alone does not block an update; what matters is whether the train is in the target's supported list.
- Is an all-in-one (AIO) package a way around the path?
- Some owners installed AIO builds such as MHI2_ER_AU57x_K3663_1_MU1425_AIO directly from older trains. Others prefer normal updates followed by patching. Check the package readme and metainfo either way.