I've taken a look at the content.pkg for the ROW maps. For this instance I just looked the the AUS and ASIA files for the ROW maps. But it should be the same for every other continent/country of those ROW maps. The following FECs/FSCs are contained in the AUS and ASIA files: 023D003E (Audi), 083D0002 (Skoda), 063D003E (Porsche), 033D003E (Bentley). So no VW or Seat FSCs/FECs contained. This means the system will need to be patched by writing the Audi, Skoda, Porsche or Bentley ROW FECs in order to make them work on VW or Seat.

For those curious in the future: You'll find the FECs/FSCs "needed" within the following path: Mib2 -> NavDB -> common_EU (as an example) -> 0 -> default -> content.pkg .
You can open this file using Notepad, Notepad++ or any other software that lets you look at any file's text. For the ROW maps there are several common_xxx folders. Like common_aus, common_asia ... and so on. The rest is just looking at the contained FSCs and comparing them to the Map region list for MHI2 Map FECs you can find widely available online. They won't match 1:1, but if an FSC starts with 083xxxxx, then you know those are for Skoda.

Edited 4 hours ago4 hr by viper42

Thanks for clearing that up and your notes for future reference. I've printed it off :). Mr Bonk etc for a patch edit for them on VW / Seat for 453. Suspect 490 will be like this... we'll see, must not count our chickens.

Many thanks guys, especially MartiniB. Tell, I had a look at the year and it says it is 2026/2027, although the major build is 2026. I have a Škoda Columbus so the FeCs should be ok for me. It’s 2230 here (New Zealand) and it’s taken a few hours to download and unzip to an SD card so I will load the maps tomorrow, but the files look ok, despite the file name, so I don’t foresee any problems. Thanks again.

As long as it's a Skoda.... Quite a few second hand Vag European cars get shipped to the Middle East where after changing the FeCs to the car brand they would come unstuck, but using the list above you'd get it working. Some Australians have actually imported European mib2 highs from retrofitters. I've advised them to use that Github patch software to get the RoW FeCs in.

North Africa isn't served by mib2 high maps, mib2 standard it is, mib3 it is. That one comes up quite a bit as European secondhand Vag cars find their way to Africa.

Think your slow download will be since you haven't got fibre to the home. Infrastructure problem 😟. It will arrive in NZ pretty fast at fibre speeds. I have had it all here from 300MBs in London to crawling rural wireless broadband of 30. Networked out from church roofs etc (for runner of wireless 4g) to full fibre to property at 900 MBs. Surprising knock on the door asking whether they could take some branches down at the bottom of the garden. Ours comes underground apart from collapsed ducting, camera down, washing up liquid and digging out to push it further along. Didn't help that the existing cable showed no entry point into the house. The house was built on it. Broken some installation rules. Chiseling on the foot of the house wall by the installation guys found a piece of BT plastic, then the phone cable and tube. Damp and radon gas can come why termination is suppose to outside the house... pass on whether radon gas getting into houses is an issue in NZ.

Basically rural Wales has useless 4g in the main so I don't expect if I had a connected car it would not get updates. Some connected car users use Internet radio.... another dead end for us rural folk. What would we do without full fibre to the property 😍

Do you want to photograph your success screen so MartiniB can use it.

Edited 27 minutes ago27 min by Tell