Hi,

I have tried to perform the update for my unit (MIB2 High); I'm currently on 430, but the update to 450 did not work.

I have tried to add new FEC via addfec.txt in M.I.B but it won't apply to the unit.

Is there anything I might be missing or doing incorrectly? I'm currently on firmware: MHI2_ER_SEG1L_P4709_1 _1447
Yes I had quite a conversation with Taztosa who has a Seat Mib2 High like you on the Briskoda site


If you look at their firmware release I believe it's the same as yours. They did a bit of footwork renaming a directory if you look at their last post after I clarified what they had done. The issue I think is that the Mr Bonk stuff is designed to work with specific software releases. They had installed 1447 AIO which it was not seeing. But that renaming or whatever they said which I enquired about did the trick. You do after doing the addFeC need to reboot the unit via the long hold on, the on/off button which I thought they were stuck on but my interpretation was the Github Mr Bonk stuff was not interfacing with 1447 AIO, if it was just 1447 they would have been OK.

Its one of those processes you only do once and forget about. Also think the program had been redesigned from when I used it 5 years ago. So they were on MHI2_ER_SEG11_P4709 1447 then had to do that:


So yes...
 
Yes I had quite a conversation with Taztosa who has a Seat Mib2 High like you on the Briskoda site


If you look at their firmware release I believe it's the same as yours. They did a bit of footwork renaming a directory if you look at their last post after I clarified what they had done. The issue I think is that the Mr Bonk stuff is designed to work with specific software releases. They had installed 1447 AIO which it was not seeing. But that renaming or whatever they said which I enquired about did the trick. You do after doing the addFeC need to reboot the unit via the long hold on, the on/off button which I thought they were stuck on but my interpretation was the Github Mr Bonk stuff was not interfacing with 1447 AIO, if it was just 1447 they would have been OK.

Its one of those processes you only do once and forget about. Also think the program had been redesigned from when I used it 5 years ago. So they were on MHI2_ER_SEG11_P4709 1447 then had to do that:


So yes...
Thank you for your answer. Unfortunately, I have renamed the patch map to "MHI2_ER_SEG11_P4709_1_MU1447_PATCH" but still the unit won't update the FEC.

I will attach screenshot of the sdcard.

After I used M.I.B. to add the FEC, I used long hold for on/off, but nothing was added to the unit.
 

Attachments

  • Skärmavbild 2026-04-09 kl. 21.05.56.png
    Skärmavbild 2026-04-09 kl. 21.05.56.png
    6.5 KB · Views: 50
  • Skärmavbild 2026-04-09 kl. 21.06.25.png
    Skärmavbild 2026-04-09 kl. 21.06.25.png
    19.8 KB · Views: 50
Last edited:
Thank you for your answer. Unfortunately, I have renamed the patch map to "MHI2_ER_SEG11_P4709_1_MU1447_PATCH" but still the unit won't update the FEC.

I will attach screenshot of the sdcard.
You should be able to communicate with the developer via a link on the github site. That had to be done once when someone in Australia used the tool but left them with European FeCs. I told them the issue but they were unable to do it themselves. That FeC list should preserve the line feed, carriage return that was in it originally. So the file end, however it originally ended, needs to be maintained. Old programming thing that you had to lookout for.

Basically you backup, then run that command. Then after it's done it's thing, introduce a reboot else it doesn't refresh itself.
 
You should be able to communicate with the developer via a link on the github site. That had to be done once when someone in Australia used the tool but left them with European FeCs. I told them the issue but they were unable to do it themselves. That FeC list should preserve the line feed, carriage return that was in it originally. So the file end, however it originally ended, needs to be maintained. Old programming thing that you had to lookout for.

Basically you backup, then run that command. Then after it's done it's thing, introduce a reboot else it doesn't refresh itself.
I will see if I can get it to work somehow. Thank you for your help!
 
I will see if I can get it to work somehow. Thank you for your help!
Basically I think once you have done that backup command then it will write back to the SD card... that's the back which I think is the clue of what Taztosa is talking about. Hopefully it will stick out like a saw thumb. The program has been re-written from when I used it, so I'm not recognising what I remember which was a sequence of difference software. Been generalised now I think so it will only be after it's run with that backup I reckon you'll see what's being talked about. The source I can't see it in un run.
 
Basically I think once you have done that backup command then it will write back to the SD card... that's the back which I think is the clue of what Taztosa is talking about. Hopefully it will stick out like a saw thumb. The program has been re-written from when I used it, so I'm not recognising what I remember which was a sequence of difference software. Been generalised now I think so it will only be after it's run with that backup I reckon you'll see what's being talked about. The source I can't see it in un run.
Hi,

I can confirm that the backup did it, but I needed to remove the previous backup before starting a new one.

So now I have the Skoda FEC (08300008) applied and maps 450.


Thank you for your help!
 
  • Like
Reactions: Walone and Tell
Hi everyone,
I have an Audi Q5 equipped with the MMI MIB2 Standard system, currently running the 2024 maps. I downloaded the new 2026 Europe maps from the link posted by Tell, but I noticed that the file format and structure are completely different from my current version.
Does anyone know if I need to do a firmware update to install them? Or are these new maps simply not compatible with the Audi MMI MIB2 Standard unit? Thanks in advance!
 
Well according to MartiniB of the Briskoda site they are compatible with

cross compatible on:

Škoda Amundsen (MIB2),
Seat Navi (MIB2),
VW Discover Media2 (MIB2),
Audi MMI ?-?-? (MIB2),

MAN Media VAN Navigation

Those question marks probably means he doesnt know exactly. You can use the Mib Helper site put together by hobbyists which give you a link to recent map files. Obviously if they haven't updated the map file link it wont be so upto date. You put your software train in then you take the map.

Fill that box in with your Audi train


Click the map link and download what it says and compare with what you have. There are mib1 SD map files about, so you might be on that. 480 was the last "free" one. Took you too 2023. You say you are on 2024. Its conceivable that there are mib1 maps files for 2024 which were bought on SD card.

It could be that MartiniB like me isnt totally familiar with Audi files. Are you sure it's not mib3. That came on builds after 2020 or so.

I have seen some odd Audi map files in the past which arent, mib1, mib2 or mib3 maps 🤔. They had recognisable names in them for map file attributes but not as we know them. Eggnog etc. Mib2 high but not in the mib2 high file layout that we known. Conceivable you might have a format that never caught on outside Audi on the other brands.

Anyhow if the user community that wrote mib helper have it updated it should point you in the right direction. If mib3 have a look at the Leon 4 thread where there is a sticky thread to the latest offline mib3 files. Suspect it might be an infotainment unit that never caught on, a precursor to the mib2 high... or one that got left behind when they moved to mib3.
 
Last edited:
Tell, thanks for the reply! I originally downloaded the 2026 maps from the MIB-helper.com platform, and that's when I realized they are different from how the maps were up until 2024. I couldn't get them to work then, just as I haven't been able to now. I need to look into it further; I think I'm making a mistake somewhere, after all.
 
Well Audi do use mapcare, so if you haven't got life long navigation FeCs then you might run off the end of what's allowed. Audi drivers with mib2 high use the github project to adjust. Even if its not a mib2 high but some other variation of the mib2 standard, the car will be sensitive to the navigation FeCs. So you need to check whether that is your stumbling block.

Read your FeC table and google what each one is and what is said about it. You will find one of those is your navigation FeC. I gave the Audi mib2 high long life one above. The navigation FeC will also define what maps are suitable and send you on the right course.

You do have a map card ?. If its not using a mapcard then it's not a mib2 "standard". As said I did see esoteric Audi files that contained mib2 high directory names in them but were not actually the mib2 high files as we know them on VW, Skoda and Seat. Some other setup.

Expect Audi boards don't resolve your issue.