-
Welcome to our new sponsor Lecatona, a brand dedicated to enhancing performance for VAG group sports cars, including SEAT, Audi, Volkswagen and Škoda. Specializing in High Pressure Fuel Pump (HPFP) upgrades.
SW update for MIB2 infotainment system?
- Thread starter Major Tom
- Start date
Normally 30 seconds if you dont have valid navigation FeC after putting in a destination.
I note you started off with a different firmware release and you were just going to use Mib tool, then ended up in 1447 by whatever means and that's the one not working.
I'm going to leave it to the experts but you did change the firmware in the process which wasnt just the application of mib tool.
As mentioned before, please share your log file. It will show the status of the unit.
Currently your FECs are not valid —> no navigation.
jpmedia implied that you changed FW again? If so why?
Did you patch again?
What changed between the working and now not working post?
Currently your FECs are not valid —> no navigation.
jpmedia implied that you changed FW again? If so why?
Did you patch again?
What changed between the working and now not working post?
To summarize what I would like to fix:
1) to install the most recent fw and sw version for Seat Ateca
2) to be able to upload map updates with life time mapcare.
I will make a back up of the current set up.
1) to install the most recent fw and sw version for Seat Ateca
2) to be able to upload map updates with life time mapcare.
I will make a back up of the current set up.
After AIO, M.I.B was not required.
Still, using M.I.B will not break the FECs.
Which M.I.B version did you use?
depending on version you used, there is a log on SD card in folder:
/logs/
or
/backup/logs/
Get the *.log file inside and post here or send me via PM.
Still, using M.I.B will not break the FECs.
Which M.I.B version did you use?
depending on version you used, there is a log on SD card in folder:
/logs/
or
/backup/logs/
Get the *.log file inside and post here or send me via PM.
Footnote: Mib Tool only on supported firmware listed. The 1447 AIO version circumvents the previous issues with 1447 with the missing language files where you had to backload those from an earlier firmware version, change the screen style before installation else it couldnt be seen, then run Mib Tool to add the FeCs.
Mib Tool works on 1219, 1338, 1376, 1409 and 1447 . 1447 if you were not on it, then you have the 1447 AIO or do it the old method.
For an easy life if happy with your firmware then just use Mib tool if not on 1447 but on one of the other four .
Ask the guys nicely if not listed and they might write the module to support another release. Not convinced that 1447 wasnt a beta release and never got shipped on a production car but I'll be told otherwise if I'm wrong I guess.
(I was it appeared in 2019)
Think there has been some operator error as it used to be called. Install ifs root was not tapped to install so Im told in mib tool, then a full charge into 1447 AIO where mib tool was used on it, where it's shouldn't have been. So two errors on different paths.
Always nice to clear things up.
Always nice to clear things up.
Seems to me that going back to 'Factory' standard and then starting again would be good
That would have been restore from the backup in mib tool. I'm told in the first attempt after doing the backup they never did the patch so the add FeC never worked correctly. That was that problem. Then launched onto the 1447 modded one (AIO) for reasons described which didn't need the patch since all FeCs are built in, but the patch was applied that time, so that didn't work. I guess that was the SWDL full install. 1447 isn't a factory standard release that's been patched in most cases. That installation issue and back loading language files and fringing the screen before installation unless you use 1447 AIO. The original is a bit hearsay.Seems to me that going back to 'Factory' standard and then starting again would be good
That's 2 & 3 in here
What training can and cannot do to reduce operator error - KnowledgeOne
Operator error (or human error) is broadly defined as the cause of an unintended consequence due to a bad decision, distraction, voluntary deviation from the procedure and so on. More simply, it is “a failure of a planned action to achieve a desired outcome.”
knowledgeone.ca
I tend to think if you are happy with the firmware but need a FeC upgrade stick to just Mib Tool if you can, but if you want both then it's the 1447 AIO. I don't have any experience in the latter. That's one on from your release. Reckon by that stage the firmware tweaks were marginal but I'll get told if wrong. They seem to be running at about two releases of the firmware in the final years of mib2 high. Something like that.
Mib Wiki as I recall said the 1338 ifs-root was pretty identical to others if not identical. The big redesign of the screen came in the 1000s series release with the aircon settings, ambient light colour being themed onto the screen. Radio logos not shipped preset but picked up over the air and the long hold technique to populate. Any other key features in 1447 that are not in the previous 1000s releases anyone ?. The rest will be bug fixes.
It's the ifs-root that previous retrofitters tinker with where we think yours has that issue. You'd have to do the mib tool backup, patch and add FeC to see whether yours worked. If it didn't revert from the backup in mib tool, but assuming the maps don't revert to Skoda FeCs you already have lifetime Seat navigation FeCs so you probably don't have a reason for doing it except clearing that SVM type of error using the automated option in Mib Tool.
Mib Tool effectively cleared the long term error that Vagtec put in mine, never reappeared in subsequent scans. Might have been Jpmedia handy work. My error came up after I did a map update, you would clear it and it reappeared at the next map update, now it doesn't with the Mib Tool approach of running clear SVM. Never needed to be run again. If-root was buggy that the retrofitter left me with so it triggered an SVM after each map update whilst this one doesnt, better written via Mib Tool approach. (like the way you see the previous guys handy work in the back up... rename, blah, blah and the files saved with date).
If you upgraded to 1447 yourself you could get operator error
... That's the choice do a complete re-churn of the firmware or just a FeC edit if happy with current firmware. Less risk in the former of taking out the unit completely since you can always restore from the backup taken by Mib Tool using the menu option. The dangle of the very last release of the firmware over what you have can temper the decision making.So if you do a restore from backup with MIB tool it will restore 'as from factory' even if it's had mods 'done' before installing MIB tool?That would have been restore from the backup in mib tool. I'm told in the first attempt after doing the backup they never did the patch so the add FeC never worked correctly. That was that problem. Then launched onto the 1447 modded one (AIO) for reasons described which didn't need the patch since all FeCs are built in, but the patch was applied that time, so that didn't work. I guess that was the SWDL full install. 1447 isn't a factory standard release that's been patched in most cases. That installation issue and back loading language files and fringing the screen before installation unless you use 1447 AIO. The original is a bit hearsay.
That's 2 & 3 in here
What training can and cannot do to reduce operator error - KnowledgeOne
Operator error (or human error) is broadly defined as the cause of an unintended consequence due to a bad decision, distraction, voluntary deviation from the procedure and so on. More simply, it is “a failure of a planned action to achieve a desired outcome.”
I tend to think if you are happy with the firmware but need a FeC upgrade stick to just Mib Tool if you can, but if you want both then it's the 1447 AIO. I don't have any experience in the latter. That's one on from your release. Reckon by that stage the firmware tweaks were marginal but I'll get told if wrong. They seem to be running at about two releases of the firmware in the final years of mib2 high. Something like that.
Mib Wiki as I recall said the 1338 ifs-root was pretty identical to others if not identical. The big redesign of the screen came in the 1000s series release with the aircon settings, ambient light colour being themed onto the screen. Radio logos not shipped preset but picked up over the air and the long hold technique to populate. Any other key features in 1447 that are not in the previous 1000s releases anyone ?. The rest will be bug fixes.
It's the ifs-root that previous retrofitters tinker with where we think yours has that issue. You'd have to do the mib tool backup, patch and add FeC to see whether yours worked. If it didn't revert from the backup in mib tool, but assuming the maps don't revert to Skoda FeCs you already have lifetime Seat navigation FeCs so you probably don't have a reason for doing it except clearing that SVM type of error using the automated option in Mib Tool.
Mib Tool effectively cleared the long term error that Vagtec put in mine, never reappeared in subsequent scans. Might have been Jpmedia handy work. My error came up after I did a map update, you would clear it and it reappeared at the next map update, now it doesn't with the Mib Tool approach of running clear SVM. Never needed to be run again. If-root was buggy that the retrofitter left me with so it triggered an SVM after each map update whilst this one doesnt, better written via Mib Tool approach. (like the way you see the previous guys handy work in the back up... rename, blah, blah and the files saved with date).
If you upgraded to 1447 yourself you could get operator error
Why have you done it
.The backup takes a copy of the module it's going to replace, whilst the restore of that back up, puts back what it changed (The principle, not the total firmware). So if it doesn't go right you are back to where you started. Probably some caveats which we'll be told.
The FeCs which it came with must be in one place and the AddFeCs adds new ones ìn. If you remove those additional FeCs and run AddFeCs again it drops them from the screen. Guess if you do a restore it might remove the additiinal FeCs. Pass on that.
Too me it has a group held in say "A" that the car came with, the "B" ones are in the txt editable file. AddFeCs command gives you A+B. Those must then go into the production memory that it runs off.
Suspect the restore is really if the module doesn't work. I know with the module and an incorrect one, you can make it appear that you have lost all your FeCs. Happened once when Jpmedia was perfecting the module for 1338, the FeC screen went blank in my car. I ran the previous one he'd given me and they all came back. Hence why I though Dejan's double FeCs issue could be sorted by it and pointed him in that direction. It turns out it can also remove redundant FeCs.
Similar threads
