Hello guys, i have a problem with my multimedia on my Seat Leon 5F with factory MSTD_EU_SE_P2313, MU Version 0132, i tried to update the software version with rar file from mibsolution.one (MSTD_EU_SE_P5310 MU0480), everything was going well on the update but when 3 files left to overwrite all of sudden multimedia went black but not completly black and it stays like that all the time, when i try to restart it with holding power button it goes completply black and come with power again but still black and i can't do anything now, i checked it with obd11 and there is communication with 5F unit which i think is a good sign. i need your help if you have any solution...i just want to make it like it was before no need to update it, thank you in advance
It’s likely you need to change the long coding, alter the skin/skinnings (then reboot) until it boots. This is a pretty common “issue” when updating MIB1
 
  • Like
Reactions: ak1_
What about this 😉 SeatCupra thread

Screenshot_20251005_185854_Firefox.jpg



The penny dropped so it's allowed here. I think you are probably updating to the 2023 maps.
 
  • Like
Reactions: ak1_ and DaveS
What about this 😉 SeatCupra thread

View attachment 50772


The penny dropped so it's allowed here. I think you are probably updating to the 2023 maps.
It worked, Thank you very much. I appreciate it. I did the coding how it was mentioned above and then restarted the multimedia by holding power + menu and it continued the update successfully
 

Attachments

  • 5.jpg
    5.jpg
    88.3 KB · Views: 61
  • 6.jpg
    6.jpg
    257.8 KB · Views: 58
You got @East Yorkshire Retrofits to thank for that. They use to sell the software but Vag prevented them since one presumes they wanted to make it dealer visits only. Probably some note that was published with the 480 mib1 firmware at the time which said if an update of older firmware then do this which they put in their advert now deleted.

Vag changed the long string for reason which meant you had to do it to make it work. I remember it came up on their web site before they took the page down but we had never found it an issue on the navigation thread with people updating to the mib1 2023 maps but evident by that post it does effect some people as you found.
 
  • Like
Reactions: DaveS and ak1_
You got @East Yorkshire Retrofits to thank for that. They use to sell the software but Vag prevented them since one presumes they wanted to make it dealer visits only. Probably some note that was published with the 480 mib1 firmware at the time which said if an update of older firmware then do this which they put in their advert now deleted.

Vag changed the long string for reason which meant you had to do it to make it work. I remember it came up on their web site before they took the page down but we had never found it an issue on the navigation thread with people updating to the mib1 2023 maps but evident by that post it does effect some people as you found.
We still perform software updates here at the workshop. We do not distribute software files themselves

The available skins changed, meaning the new software is trying to launch with a skin that doesn’t exist and is getting stuck
 
I've edited that into the resource now in case anyone else trips over on it:


The coding that may be required if they update to mib1 480 firmware.
 
@Tell thank you so much for all your work. This is amazing,

I have one question about MIB2: Firmware 0479 did add support for 2023/2024 maps. What is the latest map I can use with the old MIB2 Firmware 0462. Currently, I am running ECE3 2020/21 which I did successfully update from 2018 many years ago.

Kind Regards
Falco
 
@Tell thank you so much for all your work. This is amazing,

I have one question about MIB2: Firmware 0479 did add support for 2023/2024 maps. What is the latest map I can use with the old MIB2 Firmware 0462. Currently, I am running ECE3 2020/21 which I did successfully update from 2018 many years ago.

Kind Regards
Falco
2026 mib2 stadard maps which was released early. It would be the November 2026 release but was discovered on servers back in the year:


You MUST use the workaround to preserve your original overall.nds file. Take a copy of the original card. If you do loose the overall.nds file there is a trick to get the unit working again detailed in the resource section:


The "workaround" which enables the map update without Mapcare that users of the board called the "workaround":


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

https://www.7-zip.org/download.html

MAC: VW instructions

"ATTENTION

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.

Steps:

  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. Delete the contents of the card rather than re-format the SD card. If reformatted keep the card as fat32, 4096 (don't forget to push the card lock mechanism to off) (ditto in a MAC or delete all from the SD card). There are reported issue with reformatting rather then deleting the contents. Cards have be wrecked in a reformat.
  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 / cluster size gets tinkered with in a reformat. The CID is not deleted in a format that is outside of the area that can be addressed but reformatting has been known to corrupt the card.
(I'm editing in the links)

----

What to do if you loose your overall.nds file and link is in the resource. See above
 
Last edited:
oh really, without updating to 0479 and using my old 0462?
Then everything is much easier because download links for map version 1910 (2022) are already offline, I had trouble getting the old maps and firmware is currently unavailable.

I am familiar with the update process, thank you, I just wasn't sure about firmware requirements
 
oh really, without updating to 0479 and using my old 0462?
Then everything is much easier because download links for map version 1910 (2022) are already offline, I had trouble getting the old maps and firmware is currently unavailable.

I am familiar with the update process, thank you, I just wasn't sure about firmware requirements
Yes it was believe or is true, I have not got mib1 that you needed that latest mib1 firmware to get the Audi file working. Suspects its because its an Audi navigation file. But success was guaranteed if you did that and followed mib1's own workaround for Mapcare. Detailed in the resource section with links.

Mib2 isnt like that. No need to update the mib2 standard firmware for the latest maps but you must follow the workaround instructions for mib2 standard... not unless you had a 2019 model car where you can get away without doing that. They did ship the late releases in 2019 with unlimited mapcare. Prior to that you need the mib2 standard workaround.
 
Thanks for confirming that the firmware requirements are only relevant for mib1.
Do we have any threads where I can find the change history of mib2 firmware versions? I bet copilot got things mixed up since I now question if mib2 0479 firmware update did change anything regarding 2023/2024 maps.
 
Thanks for confirming that the firmware requirements are only relevant for mib1.
Do we have any threads where I can find the change history of mib2 firmware versions? I bet copilot got things mixed up since I now question if mib2 0479 firmware update did change anything regarding 2023/2024 maps.
There is a main firmware thread but people break out of this


No to the change history. They were undocumented fixes within the trains. 4 being the one you are talking about. Basically the thinking is the fixes corrected Android Auto issues. Each train got its own update for an issue. Think 480 is the last on the one you are talking about. I haven't bothered to update our own firmware here. 512 on mib2 standard and 1337 or a number like that on the mib2 high but did the mib2 high toolbox of writing the navigation FeC on that. Linked elsewhere.
 
They might indeed be the last mib2 standard ones. We'll see. They are what would have been released in November this year. Thus if the releases are to go on there wouldn't be anything till June 2026.

Mib2 high I've been searching and putting feelers out for the November 2025 release. Like fishing, nothing yet. Probably more like rock pooling 🦀🐟🐠🐟🍥 :ROFLMAO:.
 
  • Like
Reactions: Walone
Hi all, new poster here and apologies, I'm not a cupra owner, just an SE tech 1.6 TDI 15 plate. I've got what I assume is MIB1 (8 button radio)
I'm running an old firmware and I've found the screen to be a bit leggy, touchscreen stops working on initial startup and freezes. So I'm wanting to update my firmware prior to installing the carabc wireless carplay box mod.
I've attached a photo of my current firmware. 0425.

I don't have an SD card in at present so no map data, but if it makes a difference I'm not interested in adding standard maps data as I'll be using carplay/Android Auto.

I'm a bit of a noob, but I downloaded the rar package from page 145 of this forum, firmware 480. Can someone please confirm this is the 0480 firmware for the Leon mib1 unit?

Also, regarding installation, I found this from another thread - so I guess I'm just looking for someone to say yes - the file is correct and yes - that is how to install it or if I am missing anything. Here's the instructions from other thread:

1) Use SD 8GB at least and to be Class 10 (much faster)
2) Format the SD card in FAT32
3) Copy the data on the SD card (All folders and TXT file should be at the root of the card)
4) Insert the SD card into the player SD1 glove.
5) Put the car ignition (not start the engine under any circumstances or turning off the Infotainment)
6) Press the Menu button on the Infotainment and hold until you exit the service menu.
7) Select SW Update and click on Update.
8) Wait for the system to give us a Update Update message and confirm.
9) We connect the diagnosis device (Vagcom, OBDeleven, etc.) and perform a Scan..
10) Erase all faults.

Appreciate the input. And if this is the correct procedure, thanks to @Daz3d for his upload :) one last thing- to update only the firmware, can you use any SD card or would I need to buy either a brand new one or a VW specific one? I have access to plenty of 16/32gb cards at work, class 10 I believe and have no issues formatting this and formatting to FAT32. Thanks!!
 

Attachments

  • Screenshot_20251030-220652.png
    Screenshot_20251030-220652.png
    563.6 KB · Views: 7
Last edited:
Hi all, new poster here and apologies, I'm not a cupra owner, just an SE tech 1.6 TDI 15 plate. I've got what I assume is MIB1 (8 button radio)
I'm running an old firmware and I've found the screen to be a bit leggy, touchscreen stops working on initial startup and freezes. So I'm wanting to update my firmware prior to installing the carabc wireless carplay box mod.
I've attached a photo of my current firmware. 0425.

I don't have an SD card in at present so no map data, but if it makes a difference I'm not interested in adding standard maps data as I'll be using carplay/Android Auto.

I'm a bit of a noob, but I downloaded the rar package from page 145 of this forum, firmware 480. Can someone please confirm this is the 0480 firmware for the Leon mib1 unit?

Also, regarding installation, I found this from another thread - so I guess I'm just looking for someone to say yes - the file is correct and yes - that is how to install it or if I am missing anything. Here's the instructions from other thread:

1) Use SD 8GB at least and to be Class 10 (much faster)
2) Format the SD card in FAT32
3) Copy the data on the SD card (All folders and TXT file should be at the root of the card)
4) Insert the SD card into the player SD1 glove.
5) Put the car ignition (not start the engine under any circumstances or turning off the Infotainment)
6) Press the Menu button on the Infotainment and hold until you exit the service menu.
7) Select SW Update and click on Update.
8) Wait for the system to give us a Update Update message and confirm.
9) We connect the diagnosis device (Vagcom, OBDeleven, etc.) and perform a Scan..
10) Erase all faults.

Appreciate the input. And if this is the correct procedure, thanks to @Daz3d for his upload :) one last thing- to update only the firmware, can you use any SD card or would I need to buy either a brand new one or a VW specific one? I have access to plenty of 16/32gb cards at work, class 10 I believe and have no issues formatting this and formatting to FAT32. Thanks!!
The 480 firmware if installed on systems with older firmware can appear as if the system is hung but through coding after its installed you do what is linked to here:


Read up a bit to that post where it comes up. It was known about and the solution is as discussed above there and I put it into the resource section linked.

The fix if it looks like the unit is hung after installation is this:

Screenshot_20251030_225828_Firefox.jpg


The discussion about it is covered on the link when I asked.
 
Last edited:
  • Like
Reactions: squarehead94
The 480 firmware if installed on systems with older firmware can appear as if the system is hung but through coding after its installed you do what is linked to here:


Read up a bit to that post where it comes up. It was known about and the solution is as discussed above there and I put it into the resource section linked.

The fix if it looks like the unit is hung after installation is this:

View attachment 51321

The discussion about it is covered on the link when I asked.
Sorry I'm struggling to follow, when I open the link I can't see the coding required? Is this done through VCDS (I have access to this, FiL has a genuine cable and VCDS and he is more clued up with coding - I understand how to format, extract a file to an SD/USB, plug in and run the software update option in settings. Much beyond that is where I'd not feel as confident.
 
Its that in the box above.... and below. That was from East Yorkshire Retrofit when Vag allowed them to sell software. Now the page is deleted off their website but I found them giving out the solution at the time on the board here. Reproduced it and brought them into the conversation above. That was their old advert which they cant place now else they would get slapped wrists 😉

Screenshot_20251030_225828_Firefox.jpg


The coding is for the infotainment unit. Long string. As said it only effects units with older firmware. You could look at the long string before the update since that wont change in the process. Obdeleven Pro version or VCDS etc. It fixed the unit on the thread. It's a known issue.