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 2 September2 Sep 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 2 September2 Sep by Tell

I know what you mean about imported vehicles; a friend of mine has a couple of A5s, one NZ new and one a UK import. He’s given up on getting maps into the import.

As to download speed, I’ve had fibre for over ten years. The speed was fluctuating between 900kbps and 2600 mbps, mostly being around 1800. Our fibre uptake is such that our copper network is being turned off within the next couple of years. The country bumpkins will have to use 5G or Elon Musk. Ugh.

What screen do you want a photo of?

If the A5 has mib2 high then he needs this project:

GitHub

GitHub - Mr-MIBonk/M.I.B._More-Incredible-Bash: M.I.B. -...

M.I.B. - More Incredible Bash - The Army knife for Harman MIB 2.x aka MHI2(Q) units - Mr-MIBonk/M.I.B._More-Incredible-Bash

There are videos. Booboo here came that way. Audi folk have the same deal as Seat folk. Have to shift to life time navigation FeCs. Mib1 no new updates. Mib3 tricky as DIY you have to find a retrofitter although it may have the same deal as Seat now life long FeCs but being an import needs to switch to RoW FeCs from European. That link gives a pdf with RoW mib2 FeCs.

I did come across a table that's shows everything.

Ah Mib3 someone had put this together.

https://www.scribd.com/document/814367576/FEC-All-Available-SWaP

Edited 2 September2 Sep by Tell

1 hour ago, DarinL said:

I know what you mean about imported vehicles; a friend of mine has a couple of A5s, one NZ new and one a UK import. He’s given up on getting maps into the import.

As to download speed, I’ve had fibre for over ten years. The speed was fluctuating between 900kbps and 2600 mbps, mostly being around 1800. Our fibre uptake is such that our copper network is being turned off within the next couple of years. The country bumpkins will have to use 5G or Elon Musk. Ugh.

What screen do you want a photo of?

The screen that shows the release code on it. There are two screens that show that. 453.

Found it. :)

Why nobody mention new P470 maps?

https://navigation-maps.volkswagen.com/vw-maps/Update_25_26/P470_N60S5MIBH3_EU.7z

DBInfo.txt:

PartNumber1="V03959803AC"
PartNumber2="V03959828PT"
PartNumber3="V03959828QB"
PartNumber4="V03959822PE"
PartNumber7="V03959817LC"
PartNumber5="V03959804QS"
ApplicationSoftwareVersionNumber="0470"
SystemName="ECE 2027     "
Variant="ECE"
ReleaseName="2027"
DevVersion="P470_N60S5MIBH3_EU_NT_Q1.26"

content.pkg:

"FSC": "02300040,09300002,08300002,07300040,06300040,03300040"

Working in Audi:

Edited Wednesday at 12:501 day by mrfix

The link was posted on August 12th by viper42

The question came up about RoW so we went back to 453 RoW.... we just need 473 😉. Why 450 series started to be talked about since 453 had been found but not 473 and @viper42 told me how to read off the navigation FeCs in the file. That had been a ten year quest of mine to fine where they were stored in the file, not that you can change them in the file but in the unit.

While 473 would be nice, I am very happy with 453 as it has removed roads that no longer exist.  It is silly being directed down non existent roads.

Now I have another issue that I need guidance with.  As we know from my previous screen shot, 453 works in my Škoda Columbus very nicely.  I have a friend with an Audi MMI Navigation Plus (MHI2Q_ER_AUG22_P5092) with very old maps in it and as viper42 says the FeC for Audi is in 453, and MIB Helper says it uses the same map package as my Columbus, I thought I would update his maps.

I put the SD card in slot 1 and the unit spent a minute or two looking and then decided it couldn’t find the data.

So, we have a NZ new Audi with (old) NZ maps in it, so the region should be ok.  We have a package with the Audi FeC, so that should be ok. We have an SD card with a working, proven, copy of the package, so that should be ok.  Can anyone see any reason why the Navigation Plus can’t see the data?

Thanks.

First you have to patch it using More Incredible Bash. Audi systems require licenses for map updates. More Incredible Bash will write the lifetime map update FEC that’s default on Skoda and VW as an example.

I belive Audi were shipped like Seats so the FeC installed in the unit always tallies with the one in the map file. Their cunning plan was for you to buy mapcare which gives you the ability to update for a 3 years or whatever they sell. VW and Skoda came with unlimited mapcare with a lifelong navigation FeC.

There is a combination of buttons you can press on an Audi where you can read off the cars in built FeCs. You look at that list and read it off. That is a hex number.

The map file hex as @viper42 quoted / use his method shown but don't save the file after is compared with the units current FeC

So the navigation fec on the file has to be less than or equal to the units navigation FeC shown on the unit in Hex terms. The more incredible bash project on github which also goes under the name Mr Bonk or thats what I can it can be installed in the unit and that will write the Audi life long FeC into the unit.... then that <= formula is satisfied and the maps can be updated.

All the Audi drivers round here including @BooBoo124 will have used the github project. For RoW there is a catch unless they have fixed it you need to add the RoW life long FeC into the file, the code included in the project is the European one. This came up a few years back on the RoW with someone from your part of the world. The project comes with extensive documentation so you can find the code you need or trace back the conversation.

So essentially you photograph the cars current FeC screen. Install the project. Mr Fixit youtube video on that. Make sure the cars battery is charged, or keep it running etc. Make sure you got the RoW life long fec in the file of the project not the European one. Then you run the project. Use to be backup and then update the fecs. If you update with the European fec it wont work.

Think the process is install the project in the car which is on the SD card. Then take out the SD card use notepad in text mode to edit the file and add that RoW lifelong fec if its not in it. See notes on their materiel. SD card back in. Use addfec command of the project. Reboot the unit. Go to the audi fec display screen. Photograph it. If it has worked then you will see the updated life long fec shown which should be the audi RoW. Now you are free to update the maps. The project also unlocks assorted screens for off road, performance etc - you can ignore then. Just an added bonus.

Was in the middle of typing this when Viper got in with the short answer.... bells and whistles in this. The main thing is to make sure the unit doesn't power down whilst running the github project. It will reboot the unit a few times but loss of power is likely to corrupt the firmware. A charger can be connected or do it with the engine running. It's a one off procedure which you can then forget. Last time I did was 5 years ago. You just leave the project installed but it's there if you need it again. The SD card for the project you fiie away.

All clear as mud 👌.