Skip to content

Tell

Members
  • Joined

  • Last visited

Everything posted by Tell

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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....
  7. 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..
  8. It reads them all in if in the correct place. The unit actions all of them.
  9. 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
  10. It goes in, in upper case looking at the MIB Tool files. Generally you photograph the FeC screen of the car before and after and compare to see whether it's taken it. Thus if you had a picture of what you had before your CCC characters are the ones you want. On my copy of MIB Tool from 2021 they had example for Europe, US and China, If we assume their documentation is correct it's one of the codes I posted above. Failing that you'd have to find an Ozzie car to photograph it off. In any case if you had Australian maps in it before you altered the FeC it would have disabled them, so once you get it correct you will be able to see what you had before, then do the map update. So it's addfec in mib tool and a reboot. Assuming you used mib tool all along, otherwise there is the question of whether the module had been written for the patch for your firmware release.
  11. If your original navigation FeC code didn't have the 000 in positions 4-6 of the FeC what ever you had before you want that in there plus the rest. If you used mib tool you just edit it in on the txt file. Mib Tool goes in on the green menu. You run it on the green menu via SD card. I guess that's how you did it unless they have another product out or did it on the work bench via Ethernet usb connection. It's the Github jilled work that became the mib tool box of the mib wiki people... but there are variants of the toolbox. If you have done it via the green menu running the tool box there will be a txt file with the FeC codes in it on the SD card in the package. You edit them. Re-run and reboot the unit. I guess however you did it you need to seek out the txt file. I'm sure they will have used the same approach. Mib Tool is on the mibsolution web site.
  12. It can be done that way but the recommended way is the VW pdf. Most fail on not getting it in the directory structure and the Mac issue. In the case above may be the FeC written although if you can see it on the FeC screen then it will have been written. Normally a long menu press will bring you up to a screen that allows you to see the FeCs - a visual check. I would say if the FeC can be seen then it's been read in ok. VW and Skoda are blessed with life long navigation FeCs at delivery in mib2 form. Seat and Audi in mib2 form come with the map update locked down at delivery or once purchased Mapcare / sampler period is out of the period. The life long FeC push the limit so updates can be made. For a period some Cupras were sold with life long FeCs. You can actually interchange the Seat with the Skoda FeCs... some retrofitters load all of the brands navigation long life FeCs in for good measure, handy when they dropped the Seat one, in one release so we know if they ever do that again, what to do. I keep the Skoda one in my unit just in case they do it again 🙄. Shows the Seat navigation FeC plus the Skoda one. On the same basis an Audi with would work with a Skoda lifelong FeC. It could be say Audi was dropped from the RoW if so you use the Skoda one. It could be that. You would have to check that Audi were still getting ROW. It is easy enough to load up the Skoda one by whatever method was used. When it happened to Seat a few years back it wouldn't see the map update. Looking at my Seat notes I see I noted the Skoda one as a European life long FeC Europe 08300008 that would suggest the ROW is different.... so are we sure we have the ROW Audi one ?. Reckon not... from the internet 0ABCCCDD Code: A Brand 2 = Audi, 3 = Bentley, 6 = Porsche, 7 = Sitz, 8 = Skoda, 9 = VW, C = MAN B MIB version 1 = MIB1 HIGH (Harman), 3 = MIB2 HIGH (Harman) ССС Region 000 = Europe, 100 = USA and Canada (NAR - North America Region), 400 = Middle East (AGCC - Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, UAE), 401 = AGCC + Turkey, 402 = AGCC + Israel, 500 = South Africa, 600 = Australia and New Zealand, 700 = India, 800 = Argentina, Brazil and Mexico, 801 = Chile, 900 = Asia / Pacific, D00 = Rest Of the World (ROW - Rest Of the World) DD valid until year (DD is Hex value) DD: 4c= 2030 FF = ~2075/Lifetime Examples MIB2 High: Skoda: 0830004c → Europe until 2030 Audi: 0230004c → Europe until 2030 VW: 0930004c → Europe until 2030 Seat: 0730004c → Europe until 2030 Source: MIB2_Patch_ENG_v0.7.pdf (page 29) You got 000 in there when it should be 600 or something. Check with before and after. Reckon that's the error using a European FeC. It's the CCC part you got to get right for Australia for it to work. 600 Will do according to the table. This is all the mib wiki stuff of the group in that pdf. Thus model answer is 023600ee or 023d00ee One or the other 😍
  13. Normally if it's showing the lifelong FeC which presume ending in EE is then the FeC went in right. 7zip is the approved unzipping program till Skoda messed it it last year but I thought that had been corrected. If it throws up errors it hasn't been. I use the built in Filemanger one now, right click and file whatever it ever is in the examples I gave when it came up before. Build in unzipping program of Windows 10 / 11. Drag and drop to a directory on the PC. Drag and drop then to an SD card, in the root.
  14. Not suppose to use microSD cards. Stick to 32gb fat32 class 10 cards or above. Don't use a Mac but if you do run CleanMyDrive on the SD card before you use it. Suspect though it's the firmware. The AIO variant will be the one you want if it's coming off the mibsolution web site. Pass on what needs to be done if anything for the Australia firmware variant. The AIO variant is the ones put together which do everything... The latest ones update Gracenotes as well least for Seat. Hobbyist activity. Need to find an expert firmware hobbyist if it's not a technical issue of just kicking the update off due to formatting, file preparation or using a Mac without using CleanMyDrive on the unzipped image in an SD card. There have been a few Audi folk popping up on these threads with the FeC edit. There are two approaches either replace the firmware with AIO or the in car FeC edit updating the module. For that one you still need working firmware and the mib toolkit needs to recognise the firmware you have. There are folk out there least in Europe who can write the module to work with the firmware release or some releases. That's the alternative way. Whether yours is too early for that I pass. That was my Seat solution which someone kindly did for me on 2018 firmware. But as indicated this approach has been overtaken by the AIO firmware that hobbyists have developed but here you need to observe what needs to be done for ROW. Pass on that. Mibsolution web site you can run your finger down looking for variants for ROW firmware. Needs some Googling. Mib Wiki is the administrator of the hobbyist group if you track him down on websites and the band of hobbyists that chat on closed networks. There will be Audi ones about. Just a question of finding them. It's all the same software though packaged up for each VAG brand. That is how people accidentally get Skoda software running on Seats and it's pointed out that's Skoda firmware not Seat 😂. You see it. If it's not the firmware and it's just map presentation see the attached. That's the VW documentation. The bible on doing it. Discover_Media_MIB_Gen.2_June_2020_EN.pdf
  15. Built in does me fine. I do run but both when being the "navigator" abroad checking the Google route with the Here Maps one. That way you get the overview as where you are and the street navigation from the car system. You can keep an eye on whether the navigation is cutting a corner off up single track lanes which you rarely want to do. They both have an ability to do that. Google has real time traffic, TMC can lag. Google / Waze you all do the rat run together in a traffic incident.
  16. Yes it's what you said last time this came up. DL double layered DVD. If that's the case you need a special DVD writer that does double layered DVDs and a double layered DVD to go in. My old Panasonic combined DVD / hard disc TV recorder does this.... was a way of packing more onto a DVD by using dual layer with the laser cutting two surfaces from one direction going below the top layer. I wrote a few, re-writable DVDs. More expensive. Was a passing technical curiosity like those high audio CDs. If it isn't the media then it's going to be the navigation FeCs but I thought Skoda had always been lifetime navigation FeCs as now. Perhaps they were not and set at a lower limit so whilst it's a joint mib1 / 2 high map release its limited by the navigation FeCs that Skoda decided you could only update for 5 years after the death of mib1 updates. This one is all before my time on mib. Probably / Certainly the European enthusiasts on mib know the answer if MartiniB doesn't. Chillout one of the programmers was working with mib1 units before mib2 I reckon. Taking them apart and tinkering with them for years.
  17. But then reading around people have done it via SD. No Mac involved ?. I posted the VW pdf periodically. That's on these threads. That gives the hard and fast method. Away at the minute so can't did those out. Using a Mac us tricky, CleanMyDrive after. On a PC 7zip. The integrity of the unzipped file is checked so any odd characters in it will slam on the brakes.
  18. That's a Mib1 Columbus. Whilst the download is suppose to cover mib1 and mib2 Columbus it isn't clear to me how you get them in a mib1. Via DVD I think. There has been a conversation before and DVD was mentioned. Think I went off on the two layer discs. Normal writer does one but some do two.... cue the mib1 Columbus experts. MartiniB might know. Mib1 High is before I came into this. Think the moderator also knows about mib1 high units on how they got map updates into them... that might have been the cconversation that I had. So it's a combined release for mib1 and mib2 high but you just got to get it into the unit. You have got that reading in since its showing you the contents or that's what you have it on now thanks to a retrofitter say. You might find the manual on internet. Well I reckon the secret rests in the world of writable two layer DVDs but I could be wrong. If you got the unit from a retrofitter he might have circumvented the DVD by having it on a workbench using a laptop or the backend menu to do the job....
  19. The moan was that VW hadn't changed or not updated the files from last time but without the original I can't use the trusted scientific method of comparison 🙄. Using a current popular expression in the UK. "It is what it is". Normally said by the guy you get in and means it can't be improved.
  20. The question is, is whether the ones Martini B had marked up on the thread for outside Europe were those or whether VW has a processing error now. I don't have a copy of those files from the time when they were "found" (outside of the region I use). It could be that VW never did update the files. We are expecting mib2 files to be updated to circa 2025, the normal +5 years from the end of production of each RNS / Mib version. May be VW have stopped early. Have to wait to see what happens in the November release this year. Not long.
  21. The code is 1910 or there abouts for the latest release (June 2022). I gave up talking about calendar years when they changed the way they referenced them. Still October you might get the November release. You never know. I see all of the ones direct from the VW site are marked up as 1910 so on face value they are the June release. Like hot cakes best to get your map updates when they come out of the oven fresh 😉. (It's all of the non European ones that the link has changed on)
  22. If you did take the format route previously and you do it again make sure it's Fat32 and the cluster size is 4096. The unit runs QNX and they don't take too kindly to NTFS or other cluster sizes. Attached is the VAG gospel on the mib2 standard "how to", which is what the Amundsen is. Same instructions on file preperation across the brand covering fat32, 4096 cluster size, 7 zip and Keka / CleanMyDrive for Mac users. Discover_Media_MIB_Gen.2_June_2020_EN.pdf
  23. Are you using a Mac ?. If so you are suppose to use Keka for the unzip and run CleanMyDrive on the SD after. Just in case its a Mac issue. You are suppose to do that if using a Mac. Mib2 high it will stop the map import in its tracks but for a Mib2 Standard which an Amundsen is it will try to run with the gibberish associated with Mac characters that the unit may not like. That may well cause it to fail. You don't alter the cluster size. Those that have done on some of the cards have wrecked the card. Just a straight delete if using a PC and copy the unzipped contents onto it using 7zip. Mac the above. As said with an old fashioned format people have wrecked some of these cards. Windows 11 formats to a bigger cluster size by default it should be 4096 (correct number) and that can wreck the card if bigger. People play with the cluster size, it should be 4096 and Fat32. Those are the mistakes when people do a format rather than just right click and deletes what's on the SD.
  24. On timeliness there are production delays in QA and I'm sure they are similar with all mapping systems. Six months or so, then you enter the production part online real time distribution whether via a six monthly cycle as these or over the air quarterly say. People think Google are quicker. A lot of the data is crowd sourced by a user community of mapping individuals, it isn't picked up by cars going around and it then goes into a process of production delay via QA. Digital map companues also digitally analyse each other's maps which is how mistakes get propagated between mapping systems. Tracer GPS tracks are used to identify new routes and bypasses. Again an area for mistakes to be introduced without good QA Areas where mistakes get seeded between mapping systems. Builders roads on new estates are another one, they are not the final roads but are the truck roads when the estate is built. You often find them years are an estate has been built on digital maps that should have never have been entered, mud roads. Bollards to stop rat runs get missed but in overhead images people miss them. UK OS published planning maps as opposed to other OS maps are the defacto on the ground small scale maps but digital map producers dont check against these for mistakes. Suspect in other countries local planning maps also get ignored by the international mapping companies with one solution fits all in their validation process. It's like painting the Forth Bridge constant painting. The language deletion trick allowed the all Europe map to be put on a 16gb SD card, was a fudge. This year that one stopped working since the maps out grew the fix. I have read somewhere of other aggressive hacks of deleting parts of the directory deemed to be not required which work with this release. I did not note that down since they are only short term fixes to the issue of not buying a new VAG 32gb map card (don't change the cluster size it can wreck some of the cards). Only if driving the length of Europe do you require the all European maps, the zoned areas are adequate for the majority of people. You have a mib2 high with the all Europe map in a car that you'd wish to drive across Europe in whilst the run around would stay in the garage. That's what happens here.
  25. It's Ryan of North East VAG Adaptions in Durham is the associate that East Yorkshire Retrofit use. That guy is used by Seat mib2 high people after they mess up their units on DIY firmware updates or another retrofitter has messed it up or fancy a firmware update want someone to do it. They cover VAG stuff. Durham may be closer or easier to get to. They use traditional on the bench retrofitter methods rather than the end user Mib Tool approach. For that you need a bit of hand holding when your FeCs get messed up. That's how I got the Skoda navigation FeC on my Seat when Seat dropped support for one release only. For DIY you need a Mib Tool Skoda expert who can do a bit of surgery on your FeCs or the module if it's currently not supported by Mib tool. One of these guys did it for free on a Seat for me. Another case where a retrofitter in France had messed their FeCs. If you don't fancy DIY and / or are not plugged into the Skoda network of enthusiast on firmware then it's a retrofitter. Ryan is actually East Yorkshires technical expert sub contractor. If you told them the FeC you wanted and the duplicate ones etc they could sort it out I'm sure for a cost obviously. Seems a bit of a mess that your dealer messed it up. Ryan does do a postal service so your dealer could send it to them but you'd have to be clear on the missing app FeC you need and the duplicate. The Mib Tool people miss out that app FeC from their app like Skoda do but it can be put back in by the user. Retrofitters uses "Whatthefec" for their work, Ethernet / USB port boxes to the laptop and password crackers on the unit.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.