Guest, 🚨New Stock alert: Premium CUPRA valve caps now available in the store 👉 Order now from the merchandise store
The SATNAV says the map is not authorised. I will take a picture. Give me 5 minutes
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.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.
Seems to me that going back to 'Factory' standard and then starting again would be goodThink 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.
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![]()
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.”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.
Why have you done itSo 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?