At my previous 2 services I was offered an update to the Infotainment system (think it was 91U4) which I declined as it would have removed my 'Mods'.
SW update for MIB2 infotainment system?
- Thread starter Major Tom
- Start date
I've never been offered any on the infotainment system but I always say, that ones not the infotainment system is it ?, they say no. Think you are on the one before 1447 so perhaps they are offering you 1447 and if you had AIO you have the mods. What you don't really know is whether their records are up to date or whether the system when plugged in determines they can improve on what you have in their terms.
There was a German case I read on the Digital Eliteboard board where a guy bought a second hand car, was told by it's owner it had it's infotainment unit modded and how to update the maps, he couldnt update the maps, probably the map Mac issue and not knowing he needed to use CleanMyDrive on the SD drive after unzipping. Could have been the FeC issue like our retrofitter's poor handy work e.g.. not life long navigation FeC but set short to get extra work so the maps wouldn't load, one of the two. Took it to a dealer. Told them, so they returned it back to how it was factory supplied without the maps working (not how it was supplied). He wanted to know how to restore the mod. The dealer probably didn't know they had to restore the original map release if they were going to do that to fully restore it in a working condition with old maps. Dealers aren't software engineers. Mind you probably only a German dealer would embark on this, a rules based solution
.. which made it worse. My old Essex dealer was quite understanding that people mod the infotainment unit and wasn't interested. Similar here. I was going to say only mib2 high units would suffer from this issue but a mib2 standard where they had used a retrofitter to mod the firmware for the map update rather than use the workaround would have the same issue I guess, hinges on whether the FeCs get returned to the factory setting on any firmware update. The German one described above they did, normally it shouldn't happen that a firmware update alters the FeCs, only if they alter the FeCs would this happen as part of a firmware update, normal infotainment firmware update does not touch the FeCs. The navigation FeCs stand outside of a firmware update. Think this was part of the hocum our old retrofitter gave us to secure repeat business.
I know very little about the different units. What's the difference between 'Low' & High? Mine has Sat-nav.
Does it use a map card in an SD slot ?. If so it's a mib2 standard. Should say 6P as the map release although that's changed now.
A mib2 high, doesn't use a map card. Stabbing away at the media button will bring you round to "Jukebox" on a mib2 high. The maps are stored in internal memory on the mib2 high, spare memory is used for the Jukebox. You can copy your music to that from an SD and play from that. Circa 10gb is available for that.
There are other ways to tell from serial numbers but physically a few checks can be made plus a date of manufacture and release of the car seals what the unit is, circa 2015 - 2019 was the mib2 period. Mib1 5 years prior to that. Mib3 after to now.
Some people do replace mib1 with mib2 units so that fails the model release year check if that's been done, the juke box check works thou to identify a mib2 high. Other wise you are looking at serial release codes of the hardware, firmware and software. An alternative.
You don't have anything to worry about. If it's a 5 series release of the firmware they probably put you on 516 the last. Most of the standard unit updates are to fix the behaviour of AA and Car Play of recent. If you don't use them it's neither here nor there.
I'm wondering if you can help with the infotainment system on my 2017 Leon. Attempted to update from 0462 to 0479 as I was having a few annoying issues that I thought this would resolve.
Update seemed to go on successfully and there weren't any major problems with it initially (although it didn't resolve the original issues). The infotainment system then wouldn't boot up when I started the ignition but maybe a few minutes later. This time became longer and longer and today it's not wanting to come on at all. Worried I've bricked it but wanted to reach out here for your expert knowledge.
Thanks for any and all help!
**EDIT**
It's come on again, which is reassuring. I'm just wondering now if I should downgrade back to the original version? This problem is not ideal to say the least lol.
Update seemed to go on successfully and there weren't any major problems with it initially (although it didn't resolve the original issues). The infotainment system then wouldn't boot up when I started the ignition but maybe a few minutes later. This time became longer and longer and today it's not wanting to come on at all. Worried I've bricked it but wanted to reach out here for your expert knowledge.
Thanks for any and all help!
**EDIT**
It's come on again, which is reassuring. I'm just wondering now if I should downgrade back to the original version? This problem is not ideal to say the least lol.
Last edited:
Yeah I was thinking the same thing tbh, coupled with the existing issues think it might need a new unit. Out of interest how would I go about reinstalling the latest firmware? The option doesn't seem to be available any longer - presumably because it detects the same version? Having a read through a couple of threads on this topic would suggest I need OBDeleven?
SWDL menu. Normally needs the developers menu switched on via Obdeleven or similar. Long press on the menu button opens up a second menu with SWDL on it. You hit that and do a manual install all. It then installs what on the SD card over the top of what has been installed.
In case of Hardware issue reinstalling might be the final step toward death.
EMMC might be corrupt.
But maybe you have a damaged file system or file on unit from last FW update, which might heal.
Have fun
.
UART might be interesting to check on units log output.
EMMC might be corrupt.
But maybe you have a damaged file system or file on unit from last FW update, which might heal.
Have fun
.UART might be interesting to check on units log output.
Last edited:
Thanks for the replies all - reinstalled the update yesterday and it seems to be resolved.
It wasn't without it's challenges though! As it was suffering from a failure to boot issue, when it came to the reboots at various points throughout the update, it just didn't come back on. I ended leaving the car and coming back out to it 30mins later to find when I switched on the ignition it would carry on with the update (sometimes it wouldn't come back on so had to leave it for longer) so it took me all day to complete the install.
In fact I was nearing the first reboot when I revisited this thread and saw MIB-Wiki's comment about final step toward death - as you can appreciate, when it didn't reboot I wasn't best pleased with the possibility that I'd bricked it completely, couple that with the fact I was sat in my car with no aircon on the hottest day ever in the UK, I was very close to ripping it out there and then
.
Very strange that I was able to continue the update in the way that I was - also can't think of why it a reinstall of the same software would fix the issue?
Anyway thanks for the advice, very much appreciated!
It wasn't without it's challenges though! As it was suffering from a failure to boot issue, when it came to the reboots at various points throughout the update, it just didn't come back on. I ended leaving the car and coming back out to it 30mins later to find when I switched on the ignition it would carry on with the update (sometimes it wouldn't come back on so had to leave it for longer) so it took me all day to complete the install.
In fact I was nearing the first reboot when I revisited this thread and saw MIB-Wiki's comment about final step toward death - as you can appreciate, when it didn't reboot I wasn't best pleased with the possibility that I'd bricked it completely, couple that with the fact I was sat in my car with no aircon on the hottest day ever in the UK, I was very close to ripping it out there and then
.Very strange that I was able to continue the update in the way that I was - also can't think of why it a reinstall of the same software would fix the issue?
Anyway thanks for the advice, very much appreciated!
Feels like you were trapped in the 20 minute live power cycle. The cars systems, least the infotainment has live battery power to it after you turn the ignition off for 20 minutes only. Vag in it's wisdom has a start again update process for maps and I assume for a firmware update from a restore point in the process (front end menu, not backend SWDL menu). You are suppose to keep the system live by either connecting a battery or running the engine that avoids the 20 minute cut outs. Another way is to keep the door open I believe. To me it feels like you pieced together sufficient time by revisiting the car and opening the door...
I do my map updates with engine off and opening the door at 15 minute intervals (That gives you the 40 minutes in the backend menu). Mib Tool I kept the engine running whilst that installed and use.
I seem to be crossing posts with mib wiki see what he says... mib wiki may be right through, but either way software updates have to be carried out with continues live power else they stop / get corrupted.
I do my map updates with engine off and opening the door at 15 minute intervals (That gives you the 40 minutes in the backend menu). Mib Tool I kept the engine running whilst that installed and use.
I seem to be crossing posts with mib wiki see what he says... mib wiki may be right through, but either way software updates have to be carried out with continues live power else they stop / get corrupted.
Last edited:
The balance is connecting with a duff battery charger at home on the amount of electronics in a car these days could cause damage against that providing you don't loose power from the engine or it peaks / stalls etc. Driving along wouldn't be good so you shouldn't do that.
Trusty diesel isn't going to stop on idle. Suspect where VAG are coming from if you do loose power or the update hangs then you may be stuck if you aren't on a battery charger. 99% of the time you may be fine.
I have a seat alhambra 2016 and I have the same software of this guy:
The device:
Part no. 7N5035680D
Train MST2_EU_SE_PQ_P0351T
SW 0351
SW H.28.28.76_STD2NavPQ_EU
do you think it is possible to have an update of the software? The fact is that my infotainment suddenly starts not to work, it seems like it stops from answering to the controls and keeps going on with the last thing you were listening to…
Hello Everyone!
Kind of a newbie here (even though having my 2018 Leon FR 1.4 TSI 125HP) for 4 years.
I just want to double check on something (after excessively reading most of the posts on how to update the infotainment system)
Device Part Number: 5QA035824B
Hardware:H41
Software:0468
Installed Software Train Version: MST2_EU_SE_ZR_P0468T
HMI SOFTWARE: H29.319.29.3_STD2Plus_EU
So the million dollar question is, I'm supposed to download and update this file MST2_EU_SE_ZR_P0479T right?
I've also uploaded the pictures of the infotainment system.
Kind of a newbie here (even though having my 2018 Leon FR 1.4 TSI 125HP) for 4 years.
I just want to double check on something (after excessively reading most of the posts on how to update the infotainment system)
Device Part Number: 5QA035824B
Hardware:H41
Software:0468
Installed Software Train Version: MST2_EU_SE_ZR_P0468T
HMI SOFTWARE: H29.319.29.3_STD2Plus_EU
So the million dollar question is, I'm supposed to download and update this file MST2_EU_SE_ZR_P0479T right?
I've also uploaded the pictures of the infotainment system.
Attachments
-
1.jpeg -
2.jpeg -
3.jpeg -
4.jpeg -
5.jpeg -
6.jpeg -
7.jpeg -
8.jpeg -
9.jpeg -
10.jpeg -
11.jpeg
If it hasn't been fiddled with already to change its train to 4*. See what others say. I fell into the trap last time that someone had a fiddled box. Once fiddled off the train a standard mib2 can't continue on that train without more fiddling. It's just not a normal update. It was spotted by the part number.
Similar threads
