Tell

Opening up without an unzip error now MIB2 High: https://infotainment-cdn.skoda-auto.com/base/maps/HIGH12_P350_EU_202345.zip Might be fixed.

The VW one any time soon. All eyes on MartiniB. I've been checking the German Skoda board, they have not found the file link yet. Unless there is a delay it should be arriving in the next week or so.

Well if VW don't slip their schedule backwards you should see it any time soon. In the past they leave from work on a Friday early (a German thing) and the maps just appear on the servers but not linked to the webpage yet. Might be this Friday or next, you never know. Often the weekend is the period when they get spotted. MartiniB I'm sure is running his sniffer code as others. The VW release is the gold standard. Skoda and Seat have historic releases sometimes that VW don't have / markets that VW don't operate in. Whilst Audi keep theirs under wrap, VIN protected via a login with the mapcare three year imposed just to get in knowing what the user has purchased. That's why we see Audi drivers on Skoda boards they are running long life FeCs and are outside of the imposition Audi apply via the website (all in one custom firmware with long life navigation FeCs / mib 2 high tool box adjusted FeCs). You learn something almost every day. Was nice to see the November 350 released by the back door from Audi. That's perfectly good to use at this time. I wont be updating to the VW / Skoda one this year November since I've got it already. They are common releases across platforms so one is equivalent to the other except in this case Audi have their own mib 2 high only one, mib 1 high only ones splitting out the combined release. Probably done to keep within the 32gb card limit. Audi are indeed the brains of the Vag group. Well if we discover the Audi release is significantly different to the VW / Skoda / Seat release would it be worth re-installing it again. Hence a comparison file check when we see it.

You won't get it to install it's protected with those signatures. @Pcbbc alluded to a way of making small changes. I've seen talk before. You are reverse engineering the like that GCHQ do. More here when I went to the experts https://reverseengineering.stackexchange.com/questions/15992/defeat-rsa-hash-verification-qnx-working-example Basically the public key is published and known. It's on that thread, it's in the mib2 boxes. It's the private key that isn't or might be. It's the same public and private key across the firmware and map releases. I checked using that code fragment and downloads for maps and firmware. The whole subject came up when people were trying to modify the firmware in these boxes. Then it came to pass there was a backdoor left open via the POI import method. Anything placed after the signature got imported in. Like running behind someone at a turn stile tube gate. How the all in one software works found on enthusiasts sites. More tricky with map imports @pcbbcsays. I'd notice they had more security in them having played about with the mib2 high map files before. In 2018 discovering it was the navigation FeCs that needed to be changed and worked out the Seat ones after a unscrupulous retrofitter was selling navigation FeCs for life that turned out to be for one year. Getting pricey. Only payed once and got them to correct their scam least for me they were peddling. Four night away from home on that one visiting said retrofitter miles away. The tool boxes you see and the modded firmware all use the POI import fragment of code at the start. You can visually check this software since the firmware isn't signed at the end. No bank of four signature lines. This is how you know the Audi 350 map isn't hacked. That's signed unless like the Sony film studio someone got in and nicked the crown jewels. Suspect they guard the private key well but you never know. Brute force can be used and you need Cray computers a few years back. This is where they upped the industrial standard of sla1. 256 to 1024 or something. There were published papers saying the industry better use longer keys since computer power was catching up on brute force hacks. Bread and butter stuff of GCHQ but you wouldn't want hobbyists doing it. Interesting subject.

I had a Citreon alarm that was always doing it. The battery voltage dropping can also do that. You might want to check the quality of the battery. They are designed to pick up voltage loss which means the car is being messed about with. Fours years old, out the battery. Stop start can tax them into shorter life. The double click is the best you can do for a temporary solution till it's diagnosed properly.

Skoda knows they messed it up. They removed the Vin to map file lookup to revert back to the June release. If you use the one published by MartiniB to the Skoda servers you get the corrupted one at the minute. Mib2 highs on the import run an SLA1 signature encryption check so it will grind to a halt on the import if one character is wrong.... probably a lot more than one character out with their zipping error. The German Skoda board bless them don't understand this.... was reading their musing today to check whether it had been fixed yet. The integrity of mib2 standard files isn't protected from being messed about with but mib2 high is by that signature you see on the bottom of the meta file. That bank of four lines on the txt file at the in each directory. That seals it from tampering. Crafty way of protecting it but also protects the data from Skoda making a fool of themselves, not. Zip files themselves when unzipped if they complain means it's corrupted. The SLA1 signature is an over kill since the extraction if zipped does that. It's only sole purpose is to stop users hacking it the way they use it. If it was copied unzipped then the corruption check in transmission which it's claimed for would come in but it's use stops tinkering. To be fair it stops rubbish being loaded on to the system. So it does to that 😀. Bottom line, corrupted zip file you won't get the unit to touch it.

They will call it something else. The same time they lost that six months, they also changed the naming convention. Cue MartiniB. Traditionally, the high version in November was named for the following year. 2024 now. The last June release was the year and next year 23/24 etc. When VAG lost that year on the standard release, when they came back with something that worked, they changed the standard naming convention. I just call the June and November now and VW is best for the source least for the standard maps since they are six months ahead of Skodas.

Yes they have put out the old VW one from six months ago so it's a waste of time if you like to be up front. A few years ago Skoda lost six moths in a hiatus of a technical issues. Think VW just didn't publish but Skoda went onto the six month lags. It's this https://infotainment-cdn.skoda-auto.com/base/maps/STD2_2110_EU_A1_202345.zip which is "old" in our terms but new for Skoda 😁. I got it from here... always interesting to read the German posts... a little green on knowledge. They have hissy fits etc translated to English. https://www.skodacommunity.de/threads/navikarten-update-q1-2022-release-2023-fuer-mib1-mib2.103181/page-192

Dancing on a pin. Reckon 32gb card off ebay is a lot easier. As the maps increase in size as more detail is digitised fiddling to get it to work becomes more tricky with each release. There are tricks you can do to fit RoW maps onto European cards and vice versa for export cars and infotainment units which are a god send for people with these units but other than that. Quite an export market of European cars to North Africa, Middle East. Some to Australia and I've come across a US Golf brought to France.

Once the VW release is out in the next period worth trying with that in case there is something defective in that download. You would expect the download that worked with that menu option would still show the drive invitation which you saw when you checked it again after getting home from the dealer to write you piece up earlier. Like for like test.

Reckon best not to use the Skoda ones at this time since you can't till they sort the issue out the zip issue and the Skoda mib3 on the other thread seems to have people having issues with it. That needs more people to look at it to see whether they are just head unit difficulties or a duff file. Feels like Skodas QA on map files has gone a bit off.

Sounds good. I'm assuming the file is unzipping fine now since you did the comparison.... eh no just checked.

That's Mib2 high only on the Mega link. Works fine.

See how that goes. I'd be interested to know whether anybody can find the drive in the engineering menu which you couldn't.

Generally, if the file is corrupted during download the zip file won't un zip. That check is on the integrity of the VAG work itself. I did find this one which suggests if you can't get the offline to work see your dealer: I'd be interested to know whether the kickstart method works for other people.

Possibly doesn't need any special enabling unlike the mib2 high to get the engineering menu in mib3. Found a video:

I'm wondering whether they unlocked the developer's menu. This thread touches on it but doesn't say more... someone saw a video: https://forum.obdeleven.com/thread/18949/mib3 In mib2 the developers menu is locked down, you unlock it. Whether there is an enhanced level of unlocking which they did for you. Either way, it does take the updates. Your menu just kick-starts it off quicker. My understanding. Needs further research. It could be it isnt finding a valid update ?. That would be the MAC business and Cleanmydrive.

Best to if you want to listen to radio or recorded music. It's the poor man's version of traffic unless you are interested in rail delays whilst driving 🤔. That's why I turned it off in the car, no need with TMC. Its a scanner rat thing.

TMC will re-route the car on the sat nav if it's shown as blocked. TP just breaks into radio stations with a transport report. I've had it turned off for 6 years, TMC does the job instead better. See an issue in front on the map, tap the icon and it tells you the issue in the text. Yes TP and TMC are different. Thread started off as TMC not woŕking and finished with solutions. Traffic announcements is something different.

UK only. A "cross" on TMC channels being received over air means it's not working. The broadcaster that VAG used stopped the service. Solution on the thread are to pick up the other UK broadcaster Inrix that VAG doesn't use but can be got. Clear as mud. We say broadcaster but they run the service and transmit the data piggy backed on other broadcasts.

If you are close to Yorkshire you couId always contact East Yorkshire Retrofit they are well known for their quality of work. Any DIY will follow along the lines of the VAG sister cars. You might find it against those brands posted up.

As far as the VC is concerned I believe you can toggle it between showing the map or the next turn like mib2. Map on that display up front is too small but next turn with lane assist at eye level and distance to go is useful. There will be a mib4 circa 2024 so that will be interesting to see how they improve the design of mib3. Mib2 to me feels like a proper sat nav system (POI import, decent favourite and last destinations store) whilst mib3 they embarked on making it more Google maps like but didn't manage to do it.

Another theory I've seen posted on this is that the exploit to get access to the infotainment system via adding additional code to the backend of POI updates as per MIB2 high was deleted that took out the logo import. Early documentation of mib3 shows both logo import and user POIs in the design process, they got dropped, although it is in the PDFs. The radio logos are transmitted, the missing stations aren't transmitting those, so you use to back fill with MIB2... which obviously you can't since it's mib3 and no import menu. Buck passing. I tend to think it was the security concerns why the logo import was dropped.

Beware of Macs messing up the process. That's where you use cleanmydrive app as per mib2 high. Macs put additional characters in that cause the signature check to fail. There is a VAG Mib3 map update document if you are doing it offline. You register on the VW site with an email to get access to the map updates. https://www.volkswagen.co.uk/en/myvolkswagen/navigation-map-update.html?---={"myvolkswagen_navigation-map-update_featureappsection":"/?{\"selectedCarId\":\"tiguanFrom2021\",\"selectedNaviId\":\"mib3OiHigh\"}"} Attached file in the VW how too. discoverProGen3-en-202045.pdf

Good it had been reported that 14 did the trick on mib1s although not sure whether that was a standard or high. I'd have to go back and read where that came up. These systems were engineered to give flexibility least in mib1 and mib2 high. Mib2 standard old maps and Pcbbc code module for that as covered. On the mib2 standard settled on old maps with TMC working (Pcbbc fix with Inrix built into the fix if it's not a Delphi) rather than new maps without TMC. Mib2 high current maps with TMC working with the re coding to Inrix, 14 if you don't have connect services or that other code covered above with connect services. If you have not got Obdeleven or similar coding device with a mib2 high unit, you can make the changes with the mib2 high toolbox as Pcbbc pointed out on the other thread recently. The other fix to add to the fix list. Green menu tinkering. https://github.com/jilleb/mib2-toolbox That one is for the cost conscience who don't want to spend money on a coding device or find someone to do it for them. Horses for courses.