cross compatible on:

Skoda Columbus (Mib2H),
Seat Navi Plus (Mib2H),
VW Discover Pro (Mib2H),
Audi MMI Navigation Plus (Mib2H)

Porsche PCM4.0 (Mib2H)

started by @Mohrhuhn

https://www.briskoda.net/forums/topic/535959-columbus-map-update-2026-mib2-high/#findComment-5995662

tested by @langers2k & @Tell

 

# ECE 14.7 GB

Version: V03.959.823.TS 450 ECE 2026-2027

DevVersion: P450_N60S5MIBH3_EU_NT_Q3.25

Škoda portal: https://updateportalmaps.blob.core.windows.net/maps/HIGH2_P450_EU_202625.zip

Files inside: 2025.10.08

Downloadable: 2026.02.05

Published: 2026.--.--

# Rest of World 16 GB

-

  ======= coverage =======
# EU
Albania*, Andorra, Austria, Belarus*, Belgium, Bosnia and Herzegovina*, Bulgaria*, Croatia, Cyprus*, Czech Republic, Denmark, Estonia*, Finland, France, Germany, Gibraltar, Great Britain, Greece, Hungary, Iceland, Ireland, Italy, Kosovo*, Latvia*, Liechtenstein, Lithuania*, Luxembourg, Malta, Moldova*, Monaco, Montenegro*, Netherlands, Northern Macedonia*, Norway, Poland, Portugal, Romania*, Russia*, San Marino, Serbia*, Slovakia, Slovenia*, Spain, Sweden, Switzerland, Turkey*, Ukraine*, Vatican City
* partially

 

# ROW
Argentina*, Australia, Bahrain, Botswana*, Brazil*, Brunei*, Chile*, Indonesia*, Israel, Jordan, Kuwait, Lesotho*, Malaysia, Mexico*, Mozambique*, Namibia*, New Zealand, Oman, Philippines*, Qatar, Reunion*, Saudi Arabia, Singapore, South Africa, Swaziland*, Thailand*, Turkey*, United Arab Emirates
* partially

======= instruction =======

1. download 7z/zip archive from direct link

2. extract content to SD Card or USB

3. insert memory device into slot of Columbus

4. start of update usually is offered automatically, manually can be found under Navi-> Settings

 

!!! note for MAC users

On 29/07/2018 at 20:55, ZaphodB said:

Macs are a bit more problematic as they put some 'hidden' files on the card which confuses the head unit

-> https://www.briskoda.net/forums/topic/452002-direct-download-links-for-ece-20182019-maps/page/2/?tab=comments#comment-5095042

 

couple of potential questions are answered in previous posts:

Columbus Maps 2026

Columbus Maps 2025/2026

Columbus Maps 2025

Columbus Maps 2024/2025

Columbus Maps 2024

Columbus Maps 2023/2024

Columbus Maps 2023

Columbus Maps 2022/2023

Columbus Maps 2022

Columbus Maps 2021/2022

Columbus Maps 2021

Columbus Maps 2020/2021

Columbus Maps 2020

 

monthly POI's collection files downloading from X-o-m-k-a's blog

 

The P450 version is not compatible with VW and SEAT (FEC not supported)!

With 'More-Incredible-Bash (M.I.B.)' you can integrate an 'Audi(Skoda)_Lifetime_FEC with ExceptionList'!

Then the installation will continue to work with 'SEAT or VW'!

Indeed, that's what I did with my Seat several years back when this turned up. Why it worked for me. 😀

It's this project:

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash

You load it in the red menu with that edit.

On the post on the other board where it's taking about the txt file of the part number not being there, it's a red herring (British expression as a false story) the txt looks fine to me that doesn't reflect the FeCs. Final test when I'm up. I know when the engine is running and I go into an information screen where it's using Škoda FeCs only, it shows a blank line for the infotainment part when it isn't using the host one.

What you need to make your unit work like a Skoda is to have 08300008 in your addFeC list in addition. 5 years ago now since I did this. Those using AIO software would need to find where the FeCs go in and edit and re-install or use the link above. If they do the dirty again we may need this 023000EE (the Audi life long navigation Fec if it becomes Audi only).

I was given assistance before since the software above has to match up with firmware installed. At that stage the patch had not been written for the firmware I was using. It was written for me and is now part of the Mr Bonk stuff. That's the only wrinkle. It tells you if your firmware isn't identified.

Edited 17 February17 Feb by Tell

The gap above the 450 means its running with navigation FeC but not of the brand. Runs fine though. Means @MartiniB the compatibility list is true but may need a navigation FeC edit for other than a Skoda.

Edited 17 February17 Feb by Tell

Updated perfectly on my Audi A4 B9

Top work lads.

Yes 330 supported all the brands navigation FeCs but by 350 they reduced it to just the two 08300008 and 023000EE . I did have a moment where I thought it had been changed in 330 but no 350. The wonder of how the navigation FeCs work you can throw them all in and it runs through them till it finds one that works. I was told by the person that helped me set it up previously in 2022. "You can remove it now" once they reverted. Decided no, I'd keep it how it was just in case it happened again. It did, three or so years later.

Nice English day gecko in the picture. Did accidentally import the real thing from PNG once. Given two conch shells by a local. Un beknow, one had two eggs inside. One morning a gecko was spotted running across the carpet. Where did that come from. Found the broken egg inside the shell. Few weeks later the second one hatched out. It had travelled half way across the world in the luggage. Papa New Guinea day geckos. Just as well it wasnt a gekko gecko (tokay gecko) they are considerably larger and noisy. Had those Indonesia living behind a picture frame at a orangutan rehabilitation centre. Let you do the Google. Partners got a degree in zoology. Comes in handy.

Edited 25 February25 Feb by Tell

I use the 23000ee from more incredible bash.

I bought shells home from the Maldives one of those still had a live crab in it

43 minutes ago, BooBoo124 said:

I use the 23000ee from more incredible bash.

I bought shells home from the Maldives one of those still had a live crab in it

Yes that will be from their documentation. Mib wiki and all of that. It was the Audi FeCs that I worked out how the Seat ones worked. Users were in the dark. Retrofitters were selling firmware updates with just one year of mapcare on it, not the lifetime one. It ran out and stopped working - good for repeat business. Effected two of us. The retrofitter looked at the FeC screen, tapped it and said its your navigation FeC. I'd photographed them before and after, so comparing notes worked out the year sequencing of them. Different from the Audi table I'd found. So the long life FeC we had been sold wasnt long life. It's just off the end of the table which makes it a long life FeC. Kick it to the end and it's a long life FeC. Hex table. Seat were shipping cars without life long FeCs unlike Skoda and VW. They ran out after a year. Mapcare was never sold to UK customers of Seat so you were stuffed. You had to sort it out yourself for the mib2 high. Seats love / hate relationship with built in navigation, all rather daft. Now they love it and you need it for predictive braking in EVs.

See if I can find that Audi table that I decoded... was this fragment which had been worked out for Audi

Audi added +2 (
20 > 2019 map,
22 > 2019/2020 map)
24 > 2020
26 > 2020/2021

Hex characters. Did the same for Seat and worked out the sequence. So the Audi ee is way off the end.

The Retrofitter's mumble gave the game away of their business model and photographing of their before and after screens. They were not selling life time FeCs. They fixed. The guy returned to Poland after Brexit.

(will be a hermit crab)

Edited 25 February25 Feb by Tell

I have a Seat Ateca from which refuses to load the newest upodate. Is there a manual how to MIB this thing to work with it?

A dummy proof manual

You might find this useful

https://www.seatcupra.net/forums/threads/updating-the-inbuilt-mib2-satnav-mib2-tricks-and-mib1.388586/page-163#post-5097617

There is the github toolbox linked.

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash

The documentation is the wiki on there.

The toolbox works with specific releases of the firmware. You need to check in the github materiel. They may have it working for all now. The toolbox goes in the green or red menu whatever they call it. You edit in the FeC to the list with the notebook editor.

These units work across brands so you can have Skoda and Seat navigation FeCs in together. Tries one, then tries the next etc. So from the last time they did this I had the Skoda FeC in as well. The expert said you can remove that now when they put the Seat FeC matching back in the next release. I didnt bother. Kept it in just in case it happened again. It did a few years later.

The github software will tell you if your firmware release doesnt match what its designed to use. 1447 was the last release and it definitely was designed for that. Has a module for each matching release. For mine, a kind sole wrote mine and then it became part of the project. The documentation as I said tells you which ones it works with.

Manipulation of that red or green menu or whatever colour can be found on YouTube videos. Slightly different on the keys dependent on the style of the mib2 high. Mine is the old style that was found on the Tiguan mk2 units. I say this since I know that someone else with a Seat had put a different infotainment unit in that required different fumbling with the keys.

Essentially the github project, incredible bash etc puts the work bench tools into the unit. The SD card goes in and fumbling the keys takes you into the application. The app stays in the unit after but does nothing. Next time you want to do a bit more surgery you put the SD card back in. As said you do need to add the additional navigation FeC to the end of the FeC list, which you'll find.

After the installation process, you do a long hold on the start / stop and you are off. Its always a good idea to photograph the before and after FeCs so you know what has changed. Then you forget about it.... and thats all I remember.

Edited 19 March19 Mar by Tell

Thx, I see i have an old firmware. Updating that is no porblem but getting the errors after that fixed is. Too much risk for me i think.

to fix "B201A - Checking SVM" fault after update

Edited 19 March19 Mar by Taztoza

47 minutes ago, Taztoza said:

Thx, I see i have an old firmware. Updating that is no porblem but getting the errors after that fixed is. Too much risk for me i think.

to fix "B201A - Checking SVM" fault after update

The tool kit has a built in clear errors it reboots the unit a few times. So you either use the toolkit or 1447 AIO firmware but you'll need to edit in that FeC or use the toolkit on that. Upgrading old units to 1447 AIO has been relatively easy by those that did it. Documentation at the time suggested you cant but that hasn't been found to be the case. Very early Seat mib2 firmware in the units has been upgraded that way.

So one of two routes, your firmware is on the compatibility list for the tool box, if not the update to 1447 AIO, then use the toolbox to do the FeC edit.

2 hours ago, Tell said:

You might find this useful

https://www.seatcupra.net/forums/threads/updating-the-inbuilt-mib2-satnav-mib2-tricks-and-mib1.388586/page-163#post-5097617

There is the github toolbox linked.

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash

The documentation is the wiki on there.

The toolbox works with specific releases of the firmware. You need to check in the github materiel. They may have it working for all now. The toolbox goes in the green or red menu whatever they call it. You edit in the FeC to the list with the notebook editor.

These units work across brands so you can have Skoda and Seat navigation FeCs in together. Tries one, then tries the next etc. So from the last time they did this I had the Skoda FeC in as well. The expert said you can remove that now when they put the Seat FeC matching back in the next release. I didnt bother. Kept it in just in case it happened again. It did a few years later.

The github software will tell you if your firmware release doesnt match what its designed to use. 1447 was the last release

So i bought some VCDS and have read the unit code . I know how to update it with VCDS. So I will update from MHI2_ER_SEG11_P4708 1409 to MHI2_ER_SEG11_P4709 1447

Then Mr Bonk project to get the FeC. Was 1409 not listed in the Github project ?. I will quickly eyeball what said at the time. I stuck with my firmware and just did the FeC edit which means add it to the end of the prepared lists in the project.

Answer is 1409 is in the project so you dont need to update the firmware. Just use the github project and edit in the FeC against the list. You place it at the bottom in addition with the notepad editor watching any line feeds... if its got one keep it, if it hasn't do the same. You keep the engine running whilst using the github tool. It will reboot the unit a few times. Then after the add FeCs command you reboot the unit, go in the Fec screen and check its taken it. Then you are good to go.

https://www.seatcupra.net/forums/threads/sw-update-for-mib2-infotainment-system.427280/page-42#post-4973567

Edited 23 March23 Mar by Tell

I simply can't get the FEC codes in. Added them to the feclist on the sd card but when i list them up with the head unit they don't show up

YESSS Ionly had to restart the head unit. Somehow they are loaded from .... something to something at startup and don't change untill next startup

Edited 23 March23 Mar by Taztoza

Did they go in or not. Perhaps the patch never worked although it should tell you whether it went in. There is a help email address on the github link somewhere. Last para feels as if you are saying it now works... hopefully. I know it needs the long press on the on/off switch to get the re fresh after the edit.

5 hours ago, Tell said:

Did they go in or not. Perhaps the patch never worked although it should tell you whether it went in. There is a help email address on the github link somewhere. Last para feels as if you are saying it now works... hopefully. I know it needs the long press on the on/off switch to get the re fresh after the edit.

Only thing that did not work is Gracenote.. I don't know which database i can use. So i left it empty and got an erro 134 during install. The fec codes work now and i have updatet to 450.

I renamed the patch folder to MHI2_ER_SEG11_P4709_1_MU1447_PATCH to make it work under MIB because the AIO 1447 renames the firmware to MHI2_ER_SEG11_P4709_1 and MIB looks for a patch folder with the same name as the running firmware of the device.

Edited 23 March23 Mar by Taztoza

@BooBoo124 might be able to advice you on Gracenotes you rename a file and import via the Bash project... he told me that the other days. All my music is on Flac in sub directories with the art work 512×512 in each directory called cover.jpg. I get album art that way. I've never been too both bothered with Gracenotes.

THe conversation with @BooBoo124 was in the radio logo thread the other day. I'll edit in if I find it. Ah different conversation but BooBoos your man for Gracenotes.

Edited 23 March23 Mar by Tell

I will try the v23 and see what happens

1 hour ago, Taztoza said:

I will try the v23 and see what happens

21 works

https://mibsolution.one/#/1/9/MHI2%20-%20HARMAN/Gracenote

On 23/03/2026 at 19:08, Taztoza said:

Only thing that did not work is Gracenote.. I don't know which database i can use. So i left it empty and got an erro 134 during install. The fec codes work now and i have updatet to 450.

I renamed the patch folder to MHI2_ER_SEG11_P4709_1_MU1447_PATCH to make it work under MIB because the AIO 1447 renames the firmware to MHI2_ER_SEG11_P4709_1 and MIB looks for a patch folder with the same name as the running firmware of the device.

I worked out what you did. Updated to 1447 AIO but then had to use the Mib tools for the FeC edit but because it wasnt designed for the AIO had to do the rename. I think the tool would have worked with the firmware you were on but you'd taken the 1447 AIO update route by then. Straight 1447 has those issues where it was originally designed for the Cupra copper screen and cant be seen without altering the coding of the display if you arent in "copper" before. The user community sorted that out in 1447 AIO.

I got put off by changing the firmware at the time and just did Mib Tools after someone in the community wrote the patch. This is all 5 years ago when one of the mib2 high releases didnt support Seat. It's a repeat of that now but there is that techie solution for those that want to raise to the challenge.

As an aside my unit had previously been updated by a rather unreliable retrofitter. The back up file which mib tools generates showed exactly what the retrofitter had previously done with the dates and times. Their handy work didnt impress the people who support mib tools.

Hello,

I have an Octavia III, with map updates 2023/24. My info says i have SW 370. Does that mean that i can only download maps for SW370, or will the latest mapupdates update my SW to the latest version also?

Sorry for asking, i'm new here.

Thanks in advance!

Edited 28 March28 Mar by Leon_1973

You will be fine. The software is independent to the map file. Software defines you have a mib2 high and you have 350 maps on it etc. Obviously you got Skoda FeCs. The conversation above was about a bit of software surgery to a Seat since the Seat navigation FeC has been dropped from the 450 map release so we give it a Skoda navigation FeC in addition. Taztoza decided to update the Seat firmware at the same time. The VAG firmware upgrades to mib2 high were only incremental to resolve any bugs identified.

As long as you present the map file correctly you wont have an issue. The unit checks the integrity of the file before it does the update. Only files designed for it get in the unit which arent corrupted etc. MartiniBs associated link give hints. 32gb SD in Fat32 is ideal or 64gb in ext3 or you can use an USB but the only thing on it must be the unzipped map file. If it comes off a Mac you use CleanMydrive to remove Mac rubbish 🗑.

Thanks, i'll download the latest maps. Let you know!

Which maps do I need for my Octavia III, year 2014? System is factory-original, no modifications.

VIN <removed>

Do I need MIB1 or MIB2 maps and system?