This resource is applicable to all Seat navigation systems plus other Vag brands which are MIB2 / 2.5. It is built from the knowledge base on the Leon forum from a long running thread which has the advantage of tracking the twists and turns over a period from 2013 of Mib1 and Mib2 standard units and Plus (high) units. Mapcare is currently not available within the UK apart from on a preliminary basis of one year on new cars circa 2019 on. In Europe Mapcare is now offered for life on some models in the brand, least on Cupras, previously a three year period in other countries on Seat for a token amount circa 120 Euros.

DIY updates without Mapcare can be carried out on standard Mib2 units following the "workaround" which was derived by Exciter and is widely used. Slight downside is it sets an SVM error (software version management) in the unit which can be difficult to clear but works fine with the error. Most people do not bother with the error and do not know they have it if they don't run a VCDS type of check on the unit. You can attempt to clear it with VCDS tools.

DIY updates without Mapcare can be made on the Mib2 Plus / high unit but it first needs to be turned into a retrofit unit of which that is not currently a DIY task, a retrofitter is required to adjust the navigation FECs. Ideally the FEC should be set to 073000EE which give updates to the year 2073. Some retrofitters have a habit of setting the navigation FEC low possibly looking for repeat firmware update work. The firmware can be updated whilst getting the navigation FEC adjusted. Once the FEC is updated the developers menu can be used to update the maps. SVM errors can also be created which you can optionally clear via VCDS tools.

DIY activities on the Mib1 standard unit is more limited. In the early days of the Seat navigation thread only about 50 percent of people managed to update the maps using cards purchased off ebay. It was not clear why some people could do it that way, others could not ending up out of pocket. That died a death and can't be recommended. There are some retrofitters that claim these units can be enabled for updates similar to Mib2 high units. This may be the case for Mib1 high which shares the same upload map file, see above. FEC solution may be different. Mib1 high seek quidance from a retrofitter of options. Where a Mib1 card is lost / stolen or corrupted it is possible to make good via downloading the original release to the card or using a Mib2 blank card to restore a working system if the card is lost.

Mib3 was launched on new and face lifted models in 2020 e.g. Leon 4, FL Ateca, Tarraco etc. At this stage what we know about Mib3 is it uses Here Maps cartography and over the air map updates are made via Seat connect services + uploads similar to mib2 high. See


How do I know which unit I have ?

Press the “NAV” Button >

Confirm the “Setup” >

“Version information” selection on the display.

Check the first text line in "Version information".

If the first three digits are 6P0 it's a mib2 standard (serial number is also on the card)

5F with a mapping card in the slot it's mib1 standard

If not it's a mib1 or 2 "Navi System Plus" (no card in the slot)

(Other techniques are available - that's that the Seat website test)


Updating a Standard Mib2

The maps are held on an SD card in the unit. Extracting it you will also see in small print the 6P code as well.

Before proceeding it is important to take a copy of the contents of the SD card. There is one file that you will need from it plus you need a back up of the whole card in case you need to restore back the original. The infotainment system is linked to the card release in this file, you will need it for the update.

You must also use the original card or if you wish, purchase another VAG Mib2 card. An example of this would be once the current all European maps exceeds the Seat 16gb card. There is a Skoda 32 gb card being rolled out, expected that the all European zone map will exceed 16gb, part why zoned maps are now released and for Vag connected services.

June 2021 the All European map out grew 16GB current short term solution if you require all of Europe on the card:

For GB language across Europe you just need GB and the meta_info.db in the folder:


That's a fix till it out grows the card again. Other languages pick your plate and delete the rest except meta_info.db


Note if 1520 release was the first release the unit was paired with it's likely you will need to follow the heading Lost, Stolen and Missing Cards from a Mib2 Standard Unit below to obtain a suitable overall.nds file for the workaround with the steps below.


The VAG units recognise the CID on the card as being VAG. No hidden directories and you can't delete the CID by reformatting the card. The unit will not work with any other card other than a VAG card or any other overall.nds file it's paired with once Mapcare runs out. The only wrinkle to this is some retrofitters of a mod to the standard unit.


Using a PC or a MAC ?

PC: 7 Zip is the preferred VW tool, other unzip tool including those built into Windows, can cause difficulties.

7 zip can be obtained from

MAC: VW instructions


If the map update is performed using the Apple® OS X operating system you may find that
Discover Media does not recognise the map material or displays it incorrectly. This is due to
a lack of compatibility between the “7 zip” program and the OS-X operating system. In
addition, the OS-X operating system has a tendency to create hidden additional files on
external data media. We therefore recommend that OS X users use the “Keka” unzipping
program. We also recommend using the “CleanMyDrive” program to remove any hidden files."

If a MAC is used CleanMyDrive is run against the SD card after the maps are copied across to the SD card.

Having identified which unzipping tool is required and special Mac SD card cleaning required... free to proceed.

  1. Download the latest standard MIB2 maps
  2. on the infotainment go to settings, safely remove, sd1 card
  3. remove sd1 card from glove box slot
  4. long press on the on / off to reboot it a couple of times
  5. insert sd card in to computer
  6. copy and paste all contents to a directory on your computer
  7. Format the SD card keep it as fat32 and leave format settings as default in file explorer (don't forget to push the card lock mechanism to off) (ditto in a MAC or delete all from the SD card)
  8. Copy the new downloaded map version to the SD card (after unzipping it)
  9. Replace /maps/EEC/EEC_WLD/OVERALL.NDS on the SD CARD with the one from the original SD card
  10. eject the sd card (on a MAC run CleanMyDrive on the SD card - then eject)
  11. Inserted the card into the card 1 slot in glove box whilst infotainment is off
  12. power on and go to navigation

The unit should then boot up into navigation. Note it does take a little longer first time round. If it refuses to boot up, press the volume button forcing a reboot, hold down until the unit reboots. If this fails it will be issues on the overall.nds file / copy issues. Revisit the process. Failing this restore the back up.

You will also need to pick up any POIs that you show on the screen since these will be dropped after a map update. Petrol stations, parking location etc.

Do not format the card in anything other than Fat32. The unit runs QNX so will not correctly see the SD card if it is not in Fat32. The CID is not deleted in a format that is outside of the area that can be addressed.

On map sources

All VAG group maps are generally the same except they can sometimes have different file container names. Standard and high streams which are different but no difference in the release maps within the stream.

Seat sometimes breaks this rule by releasing different quarters to the others, more by accident than design. VW tends to be the first stop off for maps. These are published on forums as the direct download link or can be obtained from the VW website. You now need to register on the VW site, email and a password with mixed characters, length, $ etc. Press reset if you don't get it right first time. You don't need to provide the owned model car or any other details except email and password.

Note for maps outside of Europe, if you don't know the direct link you must register with the local VW country site. The full listing of map releases outside Europe is no longer visible on the European VW site.

If you don't used a published file link and do it this way you select say a recent Tiguan (2019) and Discover Media unit which is a MIB2 standard. Select the country and hover over the download button to read the release or click. No need to click if no new update having read the link, bottom left of screen or wherever your browser shows the details prior to clicking the link. DONT SELECT A TIGUAN 2020 or above - that's not MIB2 - that's MIB3 as per Leon 4s / Ateca 2020 - this resource currently covers MIB2 / 2.5 only.

Updates are released twice a year, June and November.

Current release see

That concludes updating a MIB2 standard unit maps using the workaround.


Upgrading to 32gb Skoda Card (for use on a Mib2 Standard only)

The original Mib2 standard Seat card is 16gb at some stage it's considered that the all European maps will exceed the 16gb limit. Skoda cards are now released in 32gb.

You can avail yourself of one of these ready for the day. The test one was described on ebay as

"Version 2020 SKODA GEN2 MIB2 (Amundsen 2) Card Sat Nav SD Navigation"

You use the workaround to retain your existing overall.nds file. Works fine due to the CID on the card being recognised by unit. You need to do a reboot before swapping cards.


Lost, Stolen and Missing Cards from a Mib2 Standard Unit

Godzzi and myself covered on the thread the process of getting back a card that was lost or stolen out of the unit. Buy a card and put back the overall.nds file from the year or one before. For good measure you can go back to V1 Seat map release rather than playing lucky dip with the download releases if you don't know which release was paired with the car, link below and use the most recent map update over writing the overall.nds file with the V1 one.

If link below is broken follow:

V1 link (Credit Markobc with that one):

or Skoda's download manager version (more resilient to network timing out issues)


Godzzi tested for me that going back beyond the paired overall.nds file worked. So if in doubt jump back releases if you don't know what the release was. Then do the workaround using the overall.nds file. (I did test that with a unit with the overall.nds of 1030 and works fine with 0430)

Variation of the workaround but going back to the Seat base year for mib2 if no more information on what was in the car. Full credit goes to Exciter for the workaround. Basically now identified that these overall.nds files contains effectively a release date stamp as well as a general database index. For other VAG cars you might want to go back to 0235 (2014/15) which is the very first release ahead of it coming to Seat.

The card needs to be a Standard Mib2 card, can be Seat, Skoda or VW. Might wish to consider the recent 32GB card planning ahead.


Lost, Stolen and Missing Cards from a Mib1 Standard Unit

Where the contents of a card are corrupted / deleted etc it is possible to restore the files if you know which release of the maps that the unit is on. Appropriate research may be required to identify this either from the card if you have it (printed details), build codes or what release similar models were on at this period although for Mib2 this can vary as to the first one the dealer finds in the draw. Other than a process of elimination until a card is put into the system that works.

If the card is missing a Mib2 blank card can be used since the CID identifier on the card is common between Mib1 and Mib2. The CID is a way of limiting map updates purchased on SD card to only VAG authorised cards. Mib2 card can cheaply be bought off internet for the purposes.

See post

In this example the release for the part number 5F0919866H was required. That release is the P40 ECE 2014/15 year release. The download file and instructions pull back the P40_N60S3MIBS2_EU_NT_Q3.13 from the Skoda servers which is the common VAG release across brands.

The following release for the Mib1 standard was P45_N60S3MIBS2_EU_NT_Q1.14 for ECE 2015 SEat part number 5F0919866K.

If using the Skoda download manager the release code say XXXXXX in this case P45_N60S3MIBS2_EU_NT_Q1.14 is edited in to the command

That triggers off the Skoda download manager to prepare the file for download, offers the download manager which you then execute. Read the link to the example where it should be noted that some of these early files were compressed with Winrar, so Winrar should be used to extract the image. See the post.

These are two examples for the release 2014 / 15 and 2015. There were a number of releases prior to this, twice a years of MIB1 standard (shown on the discussion thread). You have to dig around the net to find them and server location do change. Currently these example are good for October 2020 on Skoda servers. Seat servers do not hold a back catalogue and VW ones have also changed. The P designate, year and the Seat part number should hopefully index into any lost files which is how I found the P40 release on Skoda servers to help a poster. The Skoda download manager offers a more stable connection which you can edit in as per above


Got a new car but in a country where they don't like you to use built in satnav ? (Mib2 Standard only)

This one worked for somebody in Israel where VAG group doesn't sell the cards. The car was shipped zoned to the country map. Obtained a European Skoda card, deleted the contents and installed the Seat site map for the non European region including Israel. Worked fine. Took the card as a first time installation. Basically the CIDs on the cards must be international. It did not work with the European maps... brings us onto the next trick.


Got a car with a working installed map but outside of the region - need to get local map working ? (Mib2 Standard only)

Example taking a car to Morocco. Exporting a US VW to France. Exporting a European car to Palestine. Emigrated with your mib2 car from Europe to Australia.

The T6forum perfected some of this but joint working across the boards got it going for more modern units. Guy in Palestine sorted that out for latest VWs which were the problem.

Arona standard Mib2 is happy with the original T6forum method with the workaround above.

Advanced method with example with Israel as the map (text taken from a VW user):

1. Download the required Region Map Update. (For example, "Non-European countries - Package 3")

2. Use a VW SD card, as VW SD Cards have a special [CID] card identification code, and normal SD cards cannot be used for browsing data.

3. Erase everything on the card, (Before making a backup of what's on it).

4. Copy and paste the maps folder after unzipping it (do it in Windows because the mac fails something when unzipping, or use a recommended program "see volkswagen page").

5. Use a file explorer to open the 'maps' folder on the SD card. Depending on the map package you have, you will see several numbered folders.

6. Change the name of the corresponding folder of the Region number found inside the 'maps' folder on the SD card to '00'. For example; To use the MRM3 Region SD card to navigate in Morocco, etc., rename the folder '27' to '00'.

7. Copy the OVERALL.NDS file from the original (European) maps folder, which is in the “maps / EEC / EEC_WLD / OVERALL.NDS" path, and subscribe it to the card in the same path.

8. Copy the file OVERALL.NDS from the original maps folder (European), which is in the path “maps / 00 / nds / PRODUCT / E1 / OVERALL.NDS”, and subscribe it to the card in the path “maps / 00 / nds / PRODUCT / XX / OVERALL.NDS ”where XX is the code of the desired region (ME1 in the case of Morocco).

9. Copy the PRODUCT.NDS file from the original (European) maps folder, which is in the "maps / EEC / PRODUCT.NDS" path, and subscribe it to the card in the same path.

10. In the car, restart the Infotainment System by keeping the on / off button pressed for a few seconds, then insert the card and you're done.

Basically 7. is the Exciter workaround

8 and 9 are the two additional steps that some VAG heads required to make it work on out of zone maps. Was fine for the Arona, step 1- 7 was sufficient and only presenting the target country in 00 directory not editing and leaving the rest as is. Suspect the wifi standard heads of Seat would need steps 8 and 9.

Had maps of Morocco and Israel on a European Arona unit.

The method with steps 8 and 9 was used on the VW car brought to France from North America and the car that was exported to Palestine from Europe. For the US car the country code is 01 so 00 content is renamed to 01.


Mib2 High / Seat Plus Map Update

The ability to update the maps on these units is defined by the navigation FEC. No workaround was been found except to update the FECs (Function Enabling Code). Essentially the software in the unit runs like a 60s / 70s computer program with a parameter file to control how it behaves. The FEC is a sequence of codes that enable certain functions. In this case we are interested in the navigation high FEC. Experience with the original FECs and a retrofit when the navigation stopped working, a Google of Audi FECs provided a key as to how the navigation FEC works. It is this FEC that is the navigation Mapcare code.

A decode of this code enables you to identify the limits of being able to update the maps in the unit. A ready reckoner was produced for the Seat navigation high FEC. Mapcare is not currently supported in the UK although retrofit software follows the same controls. Whether non UK based, factory or retrofit, reviewing the Mapcare FEC tells you whether you have the ability to update the maps and when this ability will runs out.

How to do it on a Seat MIB2 Plus / High unit:

1. Hold Menu button until service mode shows.
2. Press "Function enabling codes (FEC, SWaP)"
3. Press "Installed codes"

Look for the FEC starting with 073 and note down the two last characters.

Use the table to decode the last two characters:

Code Allowed - Map Update month

112015 June
132015 Nov
152016 June
172016 Nov
192017 June
1b2017 Nov
1d2018 June
1f2018 Nov
212019 June
232019 Nov
252020 June
272020 Nov
292021 June
2b2021 Nov
2d2022 June
2f2022 Nov
312023 June
332023 Nov
352024 June
372024 Nov
392025 June
3b2025 Nov
3d2026 June
3f2026 Nov
412027 June
432027 Nov
452028 June
472028 Nov
492029 June
4B2029 Nov
4D2030 June
4F2030 Nov
512031 June
532031 Nov
552032 June
572032 Nov
592033 June
5B2033 Nov
5D2034 June
5F2034 Nov

For example if the Mapcare code ends in 22 you can load up to and including the June 2019 release but can't go beyond. 16 covers June 2016 but not beyond. 10 doesn't include 2015 June. 3f means you can update to November 2026 etc.

Those people with Mapcare or retrofits can check up to when they can update their maps against the serial release.

Derivation is here, post 1914:

Subsequent to producing the "ready reckoner", in 2019 Seat released "unlimited Mapcare" in Europe on specific models (at least Leon Cupra with navigation high) (I.e. in the Dutch market, Leon Cupra 2019 models).

The unlimited code which you need on a retrofit to fall inline with this is:


That particular code gives you updates to the year 2074 and should be the one that retro-fitters that claim unlimited updates should aim at. The code allows Seat to continue to offer Mapcare plus specials that have "unlimited" Mapcare rather than 3 years or 1 years. VW and Skoda have dropped Mapcare so you do not see navigation FECs in their screen subsequently but on older models you may, dependent on region. All Seat navigation high FECs start with 073000 the next two characters in Hex define the limits to the update.

A Google of the "unlimited FEC" 073000EE threw up this post 49 with Seat's 2019 navigation FECs

Navigation plus

These codes agree with the decode table already constructed plus reveal Seat's Lifetime Mapcare code that they rolled out to specific models in 2019. Discussion from post 2285 and the car revealed with it on:


Updating the Maps in a Seat Plus / Mib2 High

Having a valid Navigation Plus FEC allows the unit's maps to be updated (see above). Similar to the standard unit Seat, VW and Skoda all provide the map files on their servers which are identical by release. VW tend to release the maps on time followed by Skoda and Seat. The Seat release for the high unit has at times been released for a quarter that is normally not published.

The VW release is June and November each year, week 22 and week 45 although there may be some variation in the exact release. It is easier to use a published file link however if you don't you now need to register on the VW site, email and a password with mixed characters, length, $ etc. Press reset if you don't get it right first time. You don't need to provide the owned model car or any other details except email and password.

You select say a Tiguan (2019) and Discover Pro unit, that is the Seat Plus unit (mib2 high), select download. Note, with Mib3 roll out picking a more recent vehicle may / will lead to a Mib3 download. Safe with 2017 Discover Pro vehicles or just Tiguan 2019 with Discover Pro unit.

The VW instructions are on the PDF, well written, 7 zip can be downloaded from the link. You are advised on a PC to only use 7 zip. If a Mac you need to use CleanMydrive on the SD card after the copy and the VW recommended Mac unzip “Keka” .

Alternatively you can use the published download links (probably more ahead of the weblinks above since these are posted as direct file server links).

The unit's import needs to read exactly what was downloaded. It does a signature check. If there is an issue it will not start the update process off (just one byte out and the unit will abort the import). Forums tend to be full of these issues for the high but as long as one does not vary from VW instructions and your navigation high FEC is fine. It will go ahead.

For a PC best to download and unzip to a local drive, then copy the contents to the SD card, you need a 32gb standard SD card, class 10 or above, Fat 32 format. People mess this bit up by formatting the card to something other than Fat 32. Then once installed in the unit and triggered off it will do the update over a period of time restarting from where it left off, if you stop and start the car. 1-2 hours.

Retrofit you can use the backend menu ("developers menu") - Long MENU button press with two screen opening up one after the other, second screen select SWDL. The exact process to proceed may vary - ask your retrofitter - the menus can be counter intuitive and the system reboots a few time - power needs to be kept onto the unit by either running the engine or opening the door and closing it every 15 minutes else you are back to square one (extra 5 minute safety net to 20 mintes when power is cut to the unit, circa 45 minute process on European maps). It may also be possible to use the front end screen method on these dependent on the retrofit but is much faster to use the backend developers menu. The backend menu is locked off in high units delivered from the factory. Developers menu can be enabled via VCDS but beware if the navigation FEC does not allow the map upgrade it will import the map with an error marked up and will lock the navigation up within 30 seconds of selecting a destination. You then need to reload a copy of the original maps to get the unit working again or any serial map number before. i.e. have a downloaded copy of the maps the car came with which is your restore option. If you see "N" or "Err" or "F" against the NavDB line within SWDL rather than "D" it's not going to work, the navigation FEC does not allow the map to be successfully uploaded to the unit and used (30 second lock out will occur with an error screen). You need to exit the SWDL menu without going ahead.

Previously some Leon mib2 high owners in the UK with the fixed delivery one year Mapcare have updated their maps sourced from the VW website, basically all Skoda owners without connect services use the VW site. All the same maps but released later although Seat did put out some odd quarters at one stage probably by accident. They do have recent mib2 standard South America and Middle East maps thou that VW aren't publishing so not all bad.

Example of a UK Leon user with the one year high Mapcare with updated maps via the VW:


June 2021 release "192" excludes the Seat part number and will not load on stock firmware. Subsequent releases have been fine.


A firmware edit exists to enable the 192 maps to be loaded and RoW alternatives eg. FeC edit plus any other outdated FeCs... DIY approach:

Tap for solution on software thread


TMC UK Solution

Traffic Master discontinued their UK RDS broadcasts which VAG cars used in April for TMC, solution exists by shifting reception to the alternative UK broadcaster of traffic management data, Inrix.

Click for the Mib2 High Fix

Click for Mib2 Standard Fix



The Mib2 units break into standard and Plus (high) they use the following cartography and are branded:
  • TomTom: Seat Standard ~ Skoda Amundsen ~ VW Discover (all standard release)
  • Here Maps: Seat Plus ~ Skoda Columbus ~ VW Discover Pro + All Mib1 High units (all high release)
The map updates are interchangeable that is to say a series release can be used across the equivalent models. The upload files are byte for byte the same once unzipped for the same release although sometimes packaged with slightly different release numbers. On this basis the VW servers are the ones to use for map updates since they are more timely and faster.

Reporting Cartography Errors

Both TomTom and Here Maps allow users to report missing roads, speed limits, POIs, turn restrictions etc. The reporting process is slightly different between the two companies.

Mib3 units which replaced Mib2 in 2020 new and face lifted (FL) models uses Here Maps cartography only across the range, updates are processed differently to those described above, however errors and additions can be reported using the same methods.

TomTom you report on a map where the issue is providing evidence, web links and photographs which can go forwards into their validation process. It is either accepted or rejected. HereMaps you draw the feature onto the map, correct the feature, also providing evidence. That also goes forwards into a validation process but is less clear when it is accepted except you may see the feature when not logged in which case means that it has been accepted and not held against you. House numbering can also be added against HereMaps.

Website for Reporting TomTom Cartography issues (used by mib2 standard):

Website for Reporting HereMaps Cartography issues (used by mib1 standard & high, mib2 high, mib3 all models):

In both instances you need to set up an account. Providing evidence via photographs, web links of plans or screen shots. eg. if a new estate road is built, turn the GPS location on, on the phone and take an image of the street sign etc. Upload as a correction.

UK local authorities often have the Ordnance Survey local planning maps online for identifying local services to the public, they are updated at least once a year and are the gold standard of the physical layout of the area. These can be used to identify missing streets, erroneous street names, roads which are paths, house numbering etc.

Although they can be purchased for private use:

They can be found on most local authority websites in one form or another. It was an EU planning requirement to provide these maps to the public. This provides another validation tool.

Google Maps operate a similar map error reporting screen on their maps with a validation process. The reporting tool is not so detailed and indeed due to this the success of getting corrections authorised by Google Maps is much less than TomTom and HereMaps. HereMaps shows you the latest aerial image which tends to be much more up-to-date than Google images. Also may explain why Google lags behind on getting new housing estates on their map since they are not visible from the aerial images and cannot verify from the reports.

All providers have cars they send round to survey the roads as required. Frequency of these surveys, the serial images and reporting tools effect the accuracy of the maps. They also use GPS probes derived from moving traffic and public domain mobile tracks to identify routes. In principle new roads should be identified this way. They also digitally cross examine each others maps to identify suspect areas in their maps. All of this works on a large scale but not so well in specific areas e.g. new housing estates which slip by or minor new bypasses, road layout, turn restrictions. The standalone systems supported by TomTom and HereMaps also allow users to report any issues they find as they use the maps. Delivery drivers do this where they find an issue and is fed into the reporting process.

Once you have made your report and it's acceptance to TomTom or HereMaps you can check the roll out of it into their systems by looking at their maps. Bing uses Here Maps. Herewego is an early version of the HereMaps database. The app Co-Pilot contains HereMaps data and is updated frequently for free whilst Sygic uses TomTom maps with the same approach. Examination of accepted changes in the maps, how they are rolled out across the apps that they support and then into the cars system shows the progress. To get something into the car's system takes circa a year. Google supporters would say Google is faster but depends on their validation cycle and whether they get the issue crowd sourced into the live database and of course is not a built in car navigation system only an adjoin, so does not fully integrate with the cars virtual cockpit on next turn.

Google uses real time vehicle movement reporting for routing delays, VAG uses TCM and more recently "online" car data. The rollout of "online" to Seat may weaken the argument that Google is better during traffic delays with the cars system also better integrated. It's found on other VAG brands online data works much better than over the air TCM data. The integration of Traffic Sign Recognition (TSR) into the warning system of the car and speed camera databases used can provide better safeguards against accidental speeding than those in Google / Waze. Similar arguments apply to Carplay maps.
First release
Last update
5.00 star(s) 2 ratings
DPM Performance