7 hours ago, Tell said:

I believe the addfecs goes in that directory. Mine went into the Seat directory of that and it picked it up from there. Just one directory. in there ER for Europe. I don't believe the MIB2 high unit for Seat is shipped outside Europe why it doesn't have the sub divisions.

 

For Audi you have that choice. If you look at the attached document FEC List.pdf it shows a choice of three, yours would be 023100EE (the NAR)

 

023000EE Audi EU Maps - Lifetime x
023100EE Audi NAR Maps - Lifetime x
023200EE Audi China Maps - Lifetime x

 

Mean's yours must go in on the US list.

 

The only thing is whether your car was shipped from Europe as an import rather than designated for Australia. If it's got European firmware on it then the patch will be picked up as European then you want to addfec slotting in the NAR FEC in the European directory assuming they have written a patch for it... if you see what I mean. If it's the NAR firmware then the table pre-prepared would be fine.

 

Quite a few expats take their cars with them so it may have European firmware in it.

 

The joys of packages. On a website with Mib Tool experts hanging about you can get answers.

 

Basically you run the package taking a backup. It tells you whether a patch has been written. If not you are invited to submit the module it's extracted to the mibsolutions website. The guys can either write you a dummy patch or the full patch. They wrote me a dummy patch which I then did the addfec with. They also wrote a patch and added it to the list where the Seat 1338 originated. So the question is whether a patch is already within the list. Eyeballing you can see them from your software but it will automatically find the patch if one exists and tell you if it doesn't. Question of whether the car has NAR firmware or European firmware. Using the NAR Fec on European firmware should work to give NAR maps... I reckon.

 

Clear as mud. That's how the software worked last year. You might need one of their Bash programmers if it doesn't recognise your software.  On an Audi site you might find a band of Bash programmers familiar with Mib Tool.

 

 

 

FEC List.pdf 102.48 kB · 0 downloads

I just added those keys in all the fec txt files I could find under "patches" folder. I guess when patching it will at least take in one of them?

5 hours ago, TrevW said:

I just added those keys in all the fec txt files I could find under "patches" folder. I guess when patching it will at least take in one of them?

It reads them all in if in the correct place. The unit actions all of them.

Hmm none of them was taken in. I wonder if I should add Fecs in another file rather than just that txt file?

Although the software may have changed from when I used it. Did you do a backup. Did it say whether it recognised your firmware ?. If it didn't recognise your firmware then the patch can't be done and if it's not patched you can't change the FeCs. That's the first stage. Then you have to get the patch written to change the FeCs. Your advised not to try to write your own dummy patch.

 

Did you use Mib Tool in the first place or some other variant.

 

Also is the unit a genuine fitted unit for the Australian market or an import that was designed for another market. Has a bearing on the firmware.

 

I note there is a Mr Fixit Audi Mib tool YouTube video you can check that for comments. You really need a board where the experts on Mib tool hang out. They can dig you out of holes. Mib-wiki the self appointed administrator of the hobbyist group is active on Audiworld from a Google. I would chase him down there. Other members of the group probably post there as well helping people out. So suggest you follow up any talk on Mib Tool there. Mib Wiki maintains the mibsolution website... might even be "Mr Bonk". Saying that they do tend to push you to change the firmware to AIO rather than use Mib Tool. AIO installs mib tool at the end for the final bit after the firmware update, where people abort the process and wonder why they didn't get the FeC update.

 

https://www.google.com/search?client=firefox-b-m&sxsrf=ALiCzsYSE5C-BZeAYkZ5vKSpv0pwkOBGkQ%3A1667030167086&q=mib-wiki+audiworld&oq=mib-wiki+audiworld&aqs=heirloom-srp..

 

 

Yep i did use MrFixit's video to do it. I didn't have those Fecs ending with "ee" and they are there after patching through the Incredible Bash Tool, so i assume that it recognised the firmware if it patched the first time. Now it just didn't patch the Fecs i manually added in the txt file. 

Question of finding where it picks up the addFeCs file. After you have hit that command you must do the long press on the on / off to get a proper reboot since you won't see the refreshed FeCs without that. 

 

I was given a module by one of the programmers when they were perfecting the patch. Certainly you can delete all the FeCs we did that at one stage when he hadn't given me the correct patch. I reinstalled the previous patch and got them back. Somebody else where a retrofitter had messed their FeCs up the team corrected that for them.

 

The FeCs it actually uses are in the patch folders. So by studying your firmware serial number you should see the patch folder it used. You could edit that and reverse the backup / restore. Mind you the original back up is the one to use. Reverse that. Then do the process again but with the rest of the world FeC in the patch folder which you have edited.

 

If you have the original backup, restoring that will give you your original FeCs. Edit the patch folder that you have identified to match the firmware in your car and start again. Failing that you need the programming experts on it.

 

That's how it worked last year since they had edited in the Skoda FeC into every Seat patch folder that matched the firmware release when VAG didn't offer a Seat map release. Doing the edit yourself for the Audi rest of the world map reversing the original backup if you still have it, and start again should fix it....

Edited 29 October, 20222 yr by Tell

8 hours ago, Tell said:

Question of finding where it picks up the addFeCs file. After you have hit that command you must do the long press on the on / off to get a proper reboot since you won't see the refreshed FeCs without that. 

 

I was given a module by one of the programmers when they were perfecting the patch. Certainly you can delete all the FeCs we did that at one stage when he hadn't given me the correct patch. I reinstalled the previous patch and got them back. Somebody else where a retrofitter had messed their FeCs up the team corrected that for them.

 

The FeCs it actually uses are in the patch folders. So by studying your firmware serial number you should see the patch folder it used. You could edit that and reverse the backup / restore. Mind you the original back up is the one to use. Reverse that. Then do the process again but with the rest of the world FeC in the patch folder which you have edited.

 

If you have the original backup, restoring that will give you your original FeCs. Edit the patch folder that you have identified to match the firmware in your car and start again. Failing that you need the programming experts on it.

 

That's how it worked last year since they had edited in the Skoda FeC into every Seat patch folder that matched the firmware release when VAG didn't offer a Seat map release. Doing the edit yourself for the Audi rest of the world map reversing the original backup if you still have it, and start again should fix it....

BTW did you use this one:

 

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash/releases/tag/V3.4.0

 

Claims to fix NAR which I reckon is where the rest of the world goes. So that one is the latest. Possible if you didn't use that release might be your issue.

 

I thought I'd study it. The documentation isn't always the greatest... I get got at by Mib Wiki when I point that out 😂. Wanted to check how much it had changed since when I last used it.

 

So yes it has been changed from when I used it. You don't get to see the specific files it pastes in against your firmware.

 

 

12 hours ago, Tell said:

Question of finding where it picks up the addFeCs file. After you have hit that command you must do the long press on the on / off to get a proper reboot since you won't see the refreshed FeCs without that. 

 

I was given a module by one of the programmers when they were perfecting the patch. Certainly you can delete all the FeCs we did that at one stage when he hadn't given me the correct patch. I reinstalled the previous patch and got them back. Somebody else where a retrofitter had messed their FeCs up the team corrected that for them.

 

The FeCs it actually uses are in the patch folders. So by studying your firmware serial number you should see the patch folder it used. You could edit that and reverse the backup / restore. Mind you the original back up is the one to use. Reverse that. Then do the process again but with the rest of the world FeC in the patch folder which you have edited.

 

If you have the original backup, restoring that will give you your original FeCs. Edit the patch folder that you have identified to match the firmware in your car and start again. Failing that you need the programming experts on it.

 

That's how it worked last year since they had edited in the Skoda FeC into every Seat patch folder that matched the firmware release when VAG didn't offer a Seat map release. Doing the edit yourself for the Audi rest of the world map reversing the original backup if you still have it, and start again should fix it....

BTW did you use this one:

 

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash/releases/tag/V3.4.0

 

Claims to fix NAR which I reckon is where the rest of the world goes. So that one is the latest. Possible if you didn't use that release might be your issue.

 

I thought I'd study it. The documentation isn't always the greatest... I get got at by Mib Wiki when I point that out 😂. Wanted to check how much it had changed since when I last used it.

 

So yes it has been changed from when I used it. You don't get to see the specific files it pastes in against your firmware.

 

---

 

So I'd revert the install from the backup check you got your original navigation FeC back.

 

If you haven't got the fixed release above, install that. Then I'd edit the FeC 023100EE into the two other FeC files the one for Europe and China just in case it's picking up the wrong one, so you got 023100EE in all three files. Then do the patch and Addfec. Reboot the system and check the FeCs to see whether you got 023100EE now.

 

Also it seems the patches are also in M.I.B_Patches_20220625.7z I'm not sure how they fit in with the rest. Whether it's all automated these dates and generates these itself. But in those files is also the addfec and you can put those patches into the addfec directory of patches - I think. So that's the next level of experimentation after forcing 023100EE into all three areas.

 

Best of luck.

2 hours ago, Tell said:

BTW did you use this one:

 

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash/releases/tag/V3.4.0

 

Claims to fix NAR which I reckon is where the rest of the world goes. So that one is the latest. Possible if you didn't use that release might be your issue.

 

I thought I'd study it. The documentation isn't always the greatest... I get got at by Mib Wiki when I point that out 😂. Wanted to check how much it had changed since when I last used it.

 

So yes it has been changed from when I used it. You don't get to see the specific files it pastes in against your firmware.

 

---

 

So I'd revert the install from the backup check you got your original navigation FeC back.

 

If you haven't got the fixed release above, install that. Then I'd edit the FeC 023100EE into the two other FeC files the one for Europe and China just in case it's picking up the wrong one, so you got 023100EE in all three files. Then do the patch and Addfec. Reboot the system and check the FeCs to see whether you got 023100EE now.

 

Also it seems the patches are also in M.I.B_Patches_20220625.7z I'm not sure how they fit in with the rest. Whether it's all automated these dates and generates these itself. But in those files is also the addfec and you can put those patches into the addfec directory of patches - I think. So that's the next level of experimentation after forcing 023100EE into all three areas.

 

Best of luck.

I used the previous version - v3.3.0.

 

I will have a go with this version then! Hopefully it will patch the Fecs I manuall add this time.

Hmm still didn't work - the FECs I added still didn't get patched in. 

I wish ask one or perhaps two of the mib tools people I know on another board to look at the post. You can also chase people up on the Audiworld  board on that thread.

Edited 30 October, 20222 yr by Tell

Hi All - trying to do the update in a 2018 Kodiaq. Pop an SD card in and it tells me there's an update available. Nav->Settings->Version and there are the two options at the bottom as expected. If I hit update it sits on searching for updates for ages. 64G class 10 as exFAT. Fully (not quick) formatted as a straw to grasp at.

Is that normal and it's doing something like checking the integrity?

 

Thanks,

Paul.

3 hours ago, Cattytown said:

Hi All - trying to do the update in a 2018 Kodiaq. Pop an SD card in and it tells me there's an update available. Nav->Settings->Version and there are the two options at the bottom as expected. If I hit update it sits on searching for updates for ages. 64G class 10 as exFAT. Fully (not quick) formatted as a straw to grasp at.

Is that normal and it's doing something like checking the integrity?

 

Thanks,

Paul.

There is a slight delay whilst it does an SLA1 signature check then will start off or blow a raspberry if it fails the signature check. Normally you take out any other cards and just have it in SD1. People have reported issues before. I'd always assumed you pop out the other card, I always do. if using a MAC use CleanMyDrive on the SD card to removed Mac rubbish that causes the SLA1 check to fail.

 

MartiniB I reckon will be finding the November release anytime soon.

 

 

Slightly less technical than all the above but I've recently got a car which has the latest VW MIB 3 infotainment system and wondered if I needed to manually update the maps or does it somehow do it itself? 🗺️

18 minutes ago, john999boy said:

Slightly less technical than all the above but I've recently got a car which has the latest VW MIB 3 infotainment system and wondered if I needed to manually update the maps or does it somehow do it itself? 🗺️

Ah... does it itself. What people do to force it is to pick a route through areas of interest, then it works out you need an update. So you could pick a route to Berlin say from home and it will pull back overtime the map update. Unlike mib2 high which has all of Europe in one big file it has the maps stored as fragments. 60 or so it's in the download file on the VW site but nobody to my knowledge knows what to do with that download. Suppose to be for the East Europe market where connect services are not supported. ($)

 

So basically you can check what release you are on off the infotainment screen then if you fancy an update just plot a route to where you are going. That's how Seat people tell me how to force a mib3 map update. Can take a day or so to come down over the 4g service.

 

($) you can load up in mib2 high countries of interest via the backend menu SWDL but nobody does it that way. Useful for testing the maps.... Iceland is really small :). My FeC test.

Edited 30 October, 20222 yr by Tell

16 minutes ago, john999boy said:

Slightly less technical than all the above but I've recently got a car which has the latest VW MIB 3 infotainment system and wondered if I needed to manually update the maps or does it somehow do it itself? 🗺️

Try this page, I think that should work for you. https://www.briskoda.net/forums/topic/507843-sat-nav-map-update-2021-superb/

 

Put your VIN in here, and see if map is available https://updateportal.skoda-auto.com/

9 minutes ago, varooom said:

Put your VIN in here, and see if map is available https://updateportal.skoda-auto.com/

 

27 minutes ago, john999boy said:

Slightly less technical than all the above but I've recently got a car which has the latest VW MIB 3 infotainment system and wondered if I needed to manually update the maps or does it somehow do it itself? 🗺️

No doubt there'll be an equivalent VW page which I can check.

11 minutes ago, Tell said:

Ah... does it itself. What people do to force it is to pick a route through areas of interest, then it works out you need an update. So you could pick a route to Berlin say from home and it will pull back overtime the map update. Unlike mib2 high which has all of Europe in one big file it has the maps stored as fragments. 60 or so it's in the download file on the VW site but nobody to my knowledge knows what to do with that download. Suppose to be for the East Europe market where connect services are not supported. ($)

 

So basically you can check what release you are on off the infotainment screen then if you fancy an update just plot a route to where you are going. That's how Seat people tell me how to force a mib3 map update. Can take a day or so to come down over the 4g service.

 👍

47 minutes ago, Tell said:

There is a slight delay whilst it does an SLA1 signature check then will start off or blow a raspberry if it fails the signature check. Normally you take out any other cards and just have it in SD1. People have reported issues before. I'd always assumed you pop out the other card, I always do. if using a MAC use CleanMyDrive on the SD card to removed Mac rubbish that causes the SLA1 check to fail.

 

MartiniB I reckon will be finding the November release anytime soon.

 

 

 

Cheers - yes, I pull everything else (don't want to distract it) and from PC so a MAC doing it's thing isn't an issue. I had done a 20 minute drive with it looking.

In desperation I found a 32G SD and formatted it as FAT and that worked with the same files.

It seems fussier than my youngest's diet!

Paul.

22 minutes ago, john999boy said:

 

No doubt there'll be an equivalent VW page which I can check.

 👍

Whoops, it was you posting on the forum that I figured was a Skoda.

 

https://app-connect.volkswagen.com/mapupdates/en/car/

 

Discover Pro?

Discover_Pro_Gen.3_November_2020.pdf

1 hour ago, Cattytown said:

 

Cheers - yes, I pull everything else (don't want to distract it) and from PC so a MAC doing it's thing isn't an issue. I had done a 20 minute drive with it looking.

In desperation I found a 32G SD and formatted it as FAT and that worked with the same files.

It seems fussier than my youngest's diet!

Paul.

I do a broken record on using 32gb SD class 10 card and above.... chose not to play it today 😂. It is the recommended way of doing it. Skoda people go off piste but best to stick to the recommended way else you end up ruling stuff out. 32gb SD class 10 or above 😉. Cheap enough.

1 hour ago, varooom said:

Whoops, it was you posting on the forum that I figured was a Skoda.

 

https://app-connect.volkswagen.com/mapupdates/en/car/

 

Discover Pro?

Discover_Pro_Gen.3_November_2020.pdf 343.84 kB · 0 downloads

May be that way does work but in the early days it didn't so was concluded and said on boards that download is for East Europe who don't have connected service. Disabled in West Europe. No Seat folk have got that to work. If it did you could avoid paying up for connect services. Cunning disabling it. We await the Mib collective working out mib3.

Edited 30 October, 20222 yr by Tell

Yeah the example could have been an over air one if they were still in contract not the USB in the socket. Not persuaded that, that example is real. They come with a one year free contract then you have to cough up. Someone needs to try that out of contract.

2 hours ago, Tell said:

I do a broken record on using 32gb SD class 10 card and above.... chose not to play it today 😂. It is the recommended way of doing it. Skoda people go off piste but best to stick to the recommended way else you end up ruling stuff out. 32gb SD class 10 or above 😉. Cheap enough.

I just read the instructions that say it won't fit!

5 minutes ago, Cattytown said:

I just read the instructions that say it won't fit!

It hasn't broken the 32gb barrier yet if the card is formatted in Fat32. The clever souls that like NTFS a few years back found it wont fit. No NTFS has bigger overheads than Fat32. They were never suppose to format 32gb SD cards in NTFS for this purpose, only Fat32. German Skoda board that were moaning about it a few years back. May be at some stage it will pop the 32gb Fat cards but not yet. Got one 64gb card ready for when it does. 

Any news on the new 2023 update?