Tell

We unpack to the HD first since its faster else you can get (or may get) a lot of bus activity between the drive and the SD card as it slowly unzips checking what its done, what it's going to do with a very slow teansfer speed. It gets there in the end but faster if you just unzip to the HD (or SSD) then do a straight forward copy to the SD card. That's the traditional recommended way of doing it although if the SD writer / reader is on the motherboard in a laptop or a USB3 dongle the speed improvement may be reduced. Try both ways. I then keep a copy of the unzipped release on the PC and delete the download. The trusty HP Pavillion that I use is 10 years old but did relegate the hard disk and put an SSD in a few years back on a USB3 card. The card reader / writer isn't on the motherboard and is part of a USB2 internal connection (doesn't have the benefits of USB3 ). i5 processor. Use USB3 to back up the HD via a card. My careful approach of always keeping a back up of the map files to cover the current release and the last release just in case one wants to go back.... not that I always keep every download from the year dot of software in the download area, has it's uses. Never delete an email :). Contain release product codes etc.

One file and two folders to be exact :). The picture shows it plus Xman's . He uses E drive for his SD card mines on I:).

You drag and drop those three items out of 7zip onto your HD then drag and drop them onto a clean blank SD card from the HD. That's faster than dropping them directly from 7zip onto the SD card. It's open archive on the right clip of the mouse on 7zip to see what's in it. Then drag the three items to your HD, then from the HD drag them to a nice clean 32gb, SD card with the spec:).... hopefully that's it.

On your SD card on your computer it should look like this after unzipping in 7zip. "I"is my SD drive, yours may be something else.

That's goes unzipped via 7zip onto the card as per Xman's image above. Nothing else on the SD card except the mib1, mib2 and metafile in the route, not one level down. Should have read sometimes the German Skoda site when I gave the Seat link. ... This one if it comes up... Failing that and everything else it will be the firmware release in the unit. Using the "scientific method" you need to find someone who's done it on your firmware release to eliminate that one. The unit has a series hardware release which is checked against the map update, if the hardware isn't recognised it would give the same effect. It's not unknown that the unit's Id isnt in the meta file. That's a steering macro for the update. Checks whether the unit it's seeing tallies with what it's expecting. A duff release of the infotainment firmware might have got this wrong. You could request your dealer updates the infotainment firmware to the most recent. Normally firmware updates are not done as a matter ofcourse only engine management ones. Make them work.

hmm sometimes the German Seat forum moans about incorrect downloads on the VW site, you try this one: https://www.seat.com/owners/my-seat/navigation/ateca-navi-system-plus.html that's the 189 download just in case the other one is messed up. Other than that it must be your card writer or Skoda successfully messed up your FeCs on that unit. if you draw a blank with the Skoda dealer you need a decent retrofitter to sort it out if you want to pay to sort it out (Yorkshire on the coast know what they are doing). You did seem to be going into the back end menu with the SWDL command which should be prohibited in a MIB2 high. That's only enabled via VCDS, the long menu press and two screens open up to give the SWDL command. Mib1 wasn't protected against users doing stuff in the backend. Skoda's are suppose to have a lifetimes guarantee of map updates unlike Seat's that need the navigation FeC adjusted to give the same effect.

Fingers crossed. The unit could have been fussy about the bus speed on the card, ditto the issue that some people have with USB drives when they ignore the VW guidance. The units are like Linux media boxes, touchy when updating them, they aren't computers as such and this is where people have issues treating them as if they are fully specced PCs throwing formats at them found on PCs etc plus the full validation that the units runs before importing the files. That's where it traps Mac users not following the guidance and those that wish to ignore 7zip on a PC (some get away with that). Then you get the bragging of short cuts which dont help if they are not universal.

There are still fake cards about. Had a fake microSD about a year ago. Amazon Marketplace trader... Googled it and it met the spec of the printing and edge. Returned back to Amazon and got my money back. 128gb card for a tablet. Targeted by Chinese manufacturers that frig the Fat table of lesser cards and label and package them up as Sandisk. Great info.

You said that before but then it's not recommended by VAG... if you keep to the VW spec there isn't an issue, deviate from that then problems arise.

I'd buy yourself a 32 GB card as the VW spec on the PDF than go round in circles. They are quite cheap. I operate with three keaping the cars original map release on one, then the last release and the current. One would be sufficient as per the VW PDF You will need an SD card with a minimum of 32 GB of storage to update your navigation data. Volkswagen recommends the use of a Class 10 SDHC card, which is readily available to buy. Move off the recommendations at your peril. Take minimum to mean it's got to be 32gb no more and no less. Search sdhc 32gb sd class 10 On Amazon Prime. ~ £6-50. Not a Marketplace seller one since fakes turn up more so with those sellers in memory cards.... Saving that mine were Dane-Elec from Lidl, Aldi etc. Don't buy the micro SD cards with an adaptor they aren't recommended for this purpose. Another thing that people do. Transcend, Kingston, Sandisk all will meet the spec as indeed Dane-Elec. Skoda servers can be problematic. VW tend to be the best. The Seat has been pretty snappy of recent. The units can also be a bit problematic about how they see cards. For POI uploads they like to be on with the card then poked in which they then see rather than card in, turn on process. That's the process I use, switch on, boot up, card goes in. It sees card. Hit the menus. I remove any other cards in either slot. Pop forward. Update card goes in.

I would think the bus speed, class 10 bit is more important than the sdxc, that means it can address more memory. But the unit may not like bring presented with a card greater than its expecting which is 32gb. QNX is the operating system of the unit so its programmed to specific constraints which is why I always say stick to the VAG recommendations rather than trying to see what you can get away with. Fat32, 32gb SD card, class 10 SDHC, 7 zip on a PC, CleanMydrive and Keka on a Mac etc. Cutting corners or being inventive leads to grief. Those are the posts you read on boards.

The one I have used is the SD Associates (SDA) SD Memory Card Formatter https://www.sdcard.org/downloads/formatter/ .... but then I've never tried the output in a mib2 unit. The other way is to split the SD card into two units and use the built in Windows formatter. The car would then only see a 32gb card nothing larger. This approach

Mib3 one won't show mib1 and mib2 subdirectories we can say that. Then it's going to be variation from the VW compliance document that I attached either the format of the SD card that it doesn't like or extra characters in the download. It feels like the format generated by your Raspberry Pi if the rest was done on a PC. I just keep to the strict VW spec of the 32gb, class 10 card. Fat32 format on a PC and 7Zip.

You present both folders mib1 and mib2 to it off the route directory. Attached is the VW manual which provides the clearest instructions on presentation on the SD card. Page 3 is what you present to it. The metainfo2.txt file is important plus obvious the mib1 and mib2 folders. It dips into the mib1 folder as well it's a shared mib1 / mib2 high map release covers both bases... some people leave that out being too clever for their boots. You come across a four file sometimes on these downloads. That isn't required (forget the name of that), but those three lines are required. Two folders in the route and the metafile in the route. It does a validation and won't proceed if extra characters have got in via the download (the Mac issue) or not using 7zip. Fat32 is best but for the high unit it does reads NTFS. You are suppose to use a class 10 SD 32gb card. The back end menu via the long hold on the menu button if the developers menu has been enabled bypasses the foreground normal may of doing it. Normally you should be able to get into that but it seemed you had. SWDL will start the import but does a validation check on the signatures but as said you look for the flags Y on the navigation attributes. N or Err isn't a good idea to proceed if you seem them. I assume you have a regular unit and not a retrofit. Not sure why its not seeing the SD card unless its the issue that its not fat32, 32gb class 10. Finally you did pick say a Tiguan 2019 car with the pro unit off the website. Hit 2020 cars and you get the mib3 downliad. Discover_Pro_June_2020_EN.pdf

Should read "wouldn't worry about flattening the battery".... wonders of predictive text.

Those are TomTom screen. Mib2 High (Columbus) is Here Maps. You probably needed to post on the Mib2 standard thread (Am... whatever). ;). Your problem is the validation team arent set up to correct towns incorrectly marked up as hamlets etc. They probably sit in India, the Here Maps ones do but have local representation.

No. The files have an SLA1 signature so you can't mess with them. That's how they are protected from faulty downloads and user tinkering.... I've tinkered enough to know that :). You need the primary key for those and to my knowledge nobody has that.

On your second method and its got to the point where it's showing Y or Yes against the navigation attributes (Eggnog, NavDB etc) and not Err or an N or No means you are fine to proceed. It's the developers menu. You either leave the engine running or you follow a strict come back to the car every 15 minutes and open the door (the later I do) this forces the Infotainment unit to remain powered up. Power drops every 20 minutes if you don't open the door. Basically I start it off, come in doors, give myself 15 minutes, go back out, open the door, check, go back in the house, come back out 15 minutes latter.... and watch the finishing touches or go back in the house for another 15 minutes. Once it's finished the menu can be a bit ambiguous least on a Seat. Generally when it appears finished give it another 30 seconds or so and power back up using the on/off. That's the retro-fitters method if you are using the developers menu and don't want the engine running. Generally the drain on the battery isn't much so I would worry about flattening it. Just remember to open and close the door every 15 minutes :). The Y / Yes (which ever it is) on the attributes is important since if you see Err / N or No don't start it off since it's done a validation on your file and decided it's not going to work. If you install like this then it will delete the map in the unit and it's then empty or in the Seat case that still uses Mapcare your navigation FeC isn't valid so the map uploads into the unit but is suspended within 30 seconds of selecting a destination and starting navigation off.

That's definitely mib2 standard and the most recent map is 1520 as per the link. Covers all of Europe. That's the 2021 release to all of the Vag group. Cartography by TomTom. Fits onto the existing SD cards (16gb) doesn't need the newer Skoda 32gb unless you reformat the card to NTFS or alter the sector size from the default to something larger. Neither should you do if you follow the Vag pdf I linked to above. The cult of making it difficult for yourself by going off pista shouldn't be followed. Acres of that on the German community Skoda board... like fitting the wrong spark plugs or lowering tyre pressure to make the ride less bumpy.... Skoda say that release / the one before is for 32gb cards only, that's been found to be wrong. At some point the all Europe map may not fit on 16gb cards and in that case you use a zoned release if planning to drive across those zones or just buy the Skoda 32gb release from an ebay seller. The card is clipped to read only so doesn't grow once put inside the infotainment unit . All good to June 2021 when one looks for the next VAG release.

If it is indeed mib2 just use the first link in the post namely http://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-AS_1520_V13.7z You should always take a copy of the contents of the card before deleting and bare in mind the Mac instructions. Pretty imperative to do that. If a PC best to use 7zip for unzipping than anything else. Mib2 releases run in the sequence of four characters. The above one is 1520. If your release when you press the info button whatever that is on a Skoda is two characters long then it's definitely a mib1 and not mib2. Mib1 for November 2020 was not published by VW, yet to be confirmed that mib1 releases have come to an end, but may be the case. The lack of Skoda mib2 release for November may be related to Skoda publishing six months later than VW. Since there was not a standard mib2 release in June 2020 by VW, the sequences of Skoda's releases may have fallen foul of that. 67 plate would put it at mib2 by my reckoning.

Generally Seat lags behind Skoda but this time round they got their act together. Skoda slipped a release back from last time round as I recall which meant they could offer something new which was old when VW didn't make the June release. Possibly the Skoda November release was going to be the June VW release but since it didn't happen in June, didn't happen for Skoda in November. All the same standard releases between brands. Skoda has a good library of back releases which has its uses, so not all doom and gloom. I'm not too sure how interchangeable the mib3 releases will be between brands. Needs someone to try it who has a mib3 and can find the import menu and takes a file off the VW server and report back.

4kb. If you haven't changed it from the manufacturers size it will be fine, but other than you have to take it back to the sector size as supplied. Obviously it has to be the VAG card. When and if VAG pop the 16gb card you just buy a 32gb Skoda card off your favourite e supplier and put it on there. But it didn't happen this release. Dross deleted from the maps as well as new stuff, so the balance is still below 16gb card format.

It does. Just delete what is on the card. The issues reported are when people reformat the card and change the sector size. Keep to fat32 and you are fine... but obviously if it's been changed then it may not... so back to fat32 and 4k sector size.

I wouldn't let it put you off putting other edits thru. I see you drive a Karoq, same factory as the Ateca 😉.