Tell

It's a dealer thing. They don't release them.... if you find one on the net they can brick your unit. If they are like Seat ones which they will be there are upgrade paths which you can follow but if you dont you have a problem. Haven't messed with mine. If it's a genuine fault then a dealer will do it. Users do it if there is some issue like Android Auto being problematic then if the user community finds a reliable one online which is the original and not modded you can if it's designed as a valid upgraded that's straight forward and doesn't require VCDS / ODIS. Suspect if it's a Mapcare thing around an old unit that got missed out its a dealer thing. Will post my question to the Skoda expert.

But that is a Columbus since he's showing 0177 an old Mib2 high release. The Metadata file error means it's failed validation. That's why it can't be read in the normal way since its not being seen as a valid update.

Not using a Mac are you ?. An integrity check is made on the files for transmission errors and any fiddling within the files. The Mac operating system adds additional rubbish to the files which is why you are suppose to use CleanMydrive and the recommended MAC OS unzipping program, ditto a PC 7zip for unzipping. Other PC unzipping programs can lead to problems. In the route of media you have the metainfo2.txt file, mib1 and mib2 directories. Attached is the VW guidance. See Mac OS guidance if using a Mac. If still no success you could always download the files again to the HD. Unzip to the HD with 7 zip if a PC. Then drag and drop to your SD card which is blank. People sometimes manage to get them not in the route. Need to be in the route. Since its telling you there is a problem with the metainfo2.txt file it means the files are corrupted or not as expected (The Mac question and correct unzipping). Btw there is a newer release that MartiniB has posted up. 192. 189 was the previous, 187 the one before. I see another post has come in, I'll post since I don't want to loose my edit :). Discover_Pro_June_2020_EN.pdf

The Seat solutions lays here, it's Chillout with his toolbox https://www.drive2.ru/l/589815971363982212/ Been monitoring boards to see how quick they pick up on it. I see MartiniB picked up on the map link being available on that link but not Chillout had the fix since it probably wasn't known that it wouldn't load up on Seats. More on the SeatCupra site. I haven't tested it yet. Requires one of three firmware releases to be on the infotainment unit (on a prior one). Navigation FeCs to be valid (think the normal Seat ones). I believe you then edit the Seat part number back in which got left out of this release (covered in the German board looking at the file). The toolbox tells the unit to ignore validation errors with toggles set as I understand it as per the link above. They will be the signatures not matching since the part number has been edited. I'm told the screen then looks just like normal. Magic as the youngsters say. We still don't know whether it's a big mistake or whether Seat has done the dirty on those people with Mapcare. Looking for MartiniB to flag up when Seat puts a link up (presume corrected) or no link = the dirty. The RoW link suffers from the same issue for Seat / Cupra owners. Had a look.... two accidents in one.

Yep the all European one has popped the 16gb cards even if you alter the allocation unit size to 4096. Unpacked the Seat version of the all Europe one comes to 16,523,067. That day that Skoda warned about in atleast on the German Skoda website where you need a 32gb Skoda card for all of Europe has arrived. Took mine out of the envelope and put it in the partner's car. Really only if travelling opposite ends of the continent do you need this, but then it's nice to have all of Europe than both with sub files. Also nice to see my digital offerings to TomTom appearing on the maps .

Present for MartiniB lifted from the German Ateca forum 2021-22 maps all Europe Seat server: https://seatmapdownloads.akamaized.net/EUAS/EU_AS_STD_1730.zip VW Servers: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-AS_1730_V14.7z Musing about whether all Europe fits on the 16gb card now. Have not tried yet. Reduce your sector size if that doesn't work by the 32GB Skoda card or use a smaller region when they are published.

I know that's what is so annoying. The local Seat dealer is good... Karoq suspension is firmer. I'm holding for electric in 2030. My Ateca is fully loaded everything other than the tow bar, stuff you can't buy now. I see the standard maps have now come out from both Seat and VW. 1730.... pop over to see whether MartiniB has got them. People are moaning about they can't fit them on the SD card now for all of Europe... perhaps that day has arrived.

Checked the Rest of the World release that's missing part number 4, Seat. Don't know what Seat is up to.

OK it's messed up for Seat's they have left out the Seat part number from this joint release found on VW servers so not so joint at the minute. Hopefully it will get corrected. https://www.ateca-forum.de/index.php?thread/4625-mapcare-und-navi-karten-update/&pageNo=65

Afraid we can say the Seat retrofit community isn't having any success with this. May be they forgot about us. Will be interesting to see what's finally on the Seat servers or whether VW revises this. It could be it's an oversight on Mapcare which Seat still uses. Cupras in Holland 2019 were given life time navigation FeC which went on for 30 years or so. They won't be happy bunnies if it wasn't for life or even till 2025.

I see you can't go on holiday for 5 days without something happening :). Thanks. I see the German Skoda board have had success with 192... think you can get the prize on P97.

Where people deviate from the VW guidance it wont fit on. Suppose to be 4k. Go bigger and it won't fit on. Bought ones untouched are that.

Edit. On the last para it's come to pass that Seat Wireless Android Auto is now put on the base mib3 units and its identified by the part number ending in a letter. That one above doesn't which I photographed at a dealer doesnt'. Causing a certain amount of consternation with Seat people with early 2020 models that some get Wireless Android Auto and other don't. There was a production line change. So called zn1 vanished, the base unit. Whilst atleast in Germany business cars can optionally buy with and without Wireless Android Auto, whilst the 3D buillding building of the old mib2 high are optionally priced as an addon to the zn2 build codd (what was the old mib2 high identifier). Not sure whether VW and Skoda have all these wrinkles in the mib3 product offer.

Anwer your other question no. Skoda might call it 1520, 1530 will do.

1530 is your last release for November 2020 published late by Skoda but available Seat and VW. See Martini's other thread. Should be new ones new month.

That's more for the standard SD card based system which has a CID (hidden ID code). All VAG standard mib2 cars read any VAG SD cards so you can buy a 32gb card if you got a 16gb card or lost one. It's really for the SD card based VAG systems not the mib2 high which is this thread title. Don't need a specific VAG card for that. I just get a bit irritated when people ignore Vag guidance and go off pista on mib2 high updates. Suppose to be a 32gb card, fat32, they are cheap. Class 10.

Pass on what its saying about realtime POIs on a Skoda. The stored POIs should be being shown if you toggle them on. Will be in the infotainment menu. You are allowed a set of nine or so in mib. If you have particular needs you can import other ones with Poinspect0r if you Google that. Takes some effort to set up but once done you can import your own still within the limits of how many poi groups you can show at a time. It has a Skoda, VW, Seat user base. It replaces the now deleted VW website in German and the Skoda one that doesn't work very well. Mib1, Mib2 and the previous RNS. Doesn't work with Mib3 where there is (currently) no Poi import menu within the infotainment system (how people get the beeps with their speed camera databases they import themselves). But as said takes some effort at PC computer skills but once done it's there to be used. You can use it to save destinations from coordinates, it's an old Skoda trick I was told about :). Swiss army knife for getting user POIs in, but there will be built in ones on your map file for sure. https://poinspect0r.blogspot.com/?m=1

I never have the space so delete the Google downloads 😂. I have Co-pilot all world ones on my phablet (Here Map based), Sygic Tom Tom all world ones. Both offline, you have HereWeGo online Here Maps and new online AmiGo TomTom based (last two free). AmiGo is suppose to be supported within Android Auto as an alternative (they opened Android Auto up). Haven't tried that within Android Auto but works fine in standalone. Latter two use free online traffic data. Ofcourse with connected cars (mib3 etc) they are now feeding real time traffic data into the system getting the same edge as online Google Maps. Once 2025 comes I'll be using apps where there are new roads rather than the built in mib2 🤣. Nothing so annoying than finding you are off pista according to sat nav when you aren't or just grin and bear it. New bypasses are the issue where they take out an existing route so you can't get a route to where you want to go.

I think DIY FeC adjustments are a bit too dangerous... best to leave it to the experts, some are better than others. A London based one killed a Seat mib2 high but since it was under warranty the owner got it replaced. Was the same retrofitter that had aligned the FeC period to one year that generated repeat business. e.g. unscrupulous operator. The guy has gone back to Poland, home grown northern retrofitters that do a better job now. Due to Seat in the UK putting mib2 highs on Cupra brand up to 2020 and not supporting Mapcare in the UK, quite a market for their work. Re reading Australian VW mib1 high posts at the time around 2015 or so, they were taking their cars back to VW to get Mapcare put on them which would have been unlimited. Semantics. So Mapcare on those vehicles gave you unlimited as they pushed the hex code to a high value. Without Mapcare the hex value is set at the build quarter least in mib2 highs so you cant update it. They probably also had a firmware update at that period reading those boards. Veritable dv52 was commenting on long strings before and after to work out what may have been done. Suspect if you find a reliable Australian based retrofitter and they knew their stuff they might be able to help. Since the mib1 high shares the same map update file as mib2 high, reckon the units will be able to be updated till 2025 if the FeC codes were adjusted. 2025 is 5 years after they stopped fitting mib2 which may be the end life for mib2 updates (2020+5 for mib2 (standard and high), 2015+5 for mib1 standard). We will see. Assume there are some Columbus Mib people in Europe that have taken the map update of November 2020 and will be still taking this forward. One advantage of the shared update file, five extra years of updates.

This is where you need a good retrofitter to adjust the navigation FeC in it I reckon if they exist in Australia now. So it's pre when they took Mapcare off Mib1. Adjusting the navigation FeC was something they use to do with VWs in Australia prior to Mapcare being dropped. It is a Mib1 high from the build code and Google's. That bar that says "Mib1" means it's read it off the SD card / USB. The "N/A" means non applicable so the update on SD card doesn't tally with the function. You need to be careful that you don't force a navigation update where it's not supported, done that been there on my learning curve with mib2, people before me and people after. If you do that you need a version of the map that tallies with the unit or before... The file named on the screen to restore. I spent a month driving about without navigation till I did that. In mib2 high the key before starting off the update via the backend menu is to see a row of Y (for Yes) against NavDB, Eggnog, Truffles, SpeechResVDE via the backend using SWDL. It will be similar for sure in Mib1 high. The navigation FeC protects NavDB which is the cartography. SpeechResVDE is the speech, Eggnog and Truffles are I believe the built in POIs and Names you see on the map. Everything other than NavDB you can update but you kill the navigation if you update NavDB. Attached are keys screens. If you see the third one with the F and Err means the navigation FeC isn't applicable, the update is beyond the period allowed by Mapcare. If you force an update then you get the forth screen with the OKs in it. Enter a destination, start off navigation and within 30 seconds you get the fifth screen. You then reinstall what the map the car came with (version Or earlier) and find a retrofitter to adjusted the navigation FeC least if it's a mib2. Will be the same for mib1. DIY activity is beyond the average user to do a navigation FeC update and can wreck the unit. Least on a mib2 high. I saw Mr Fixit wiki had something assembled from web pages last night I guess. A good retrofitter takes a copy of the units settings, does the adjustment but has a backup to restore if it goes wrong. DIY fiddling you wouldn't have that and at £800 or so messing up an infotainment unit by attempting to reprogram the FeCs isn't recommended although some places offer DIY downloads. It took a day for a retrofitter to restore traffic sign recognition back to my car after the updated the FeCs, read road speed signs as kph not mph so told be I was speeding at half the speed it should. They kept saying job done, half a mile down the found it wasn't. Three attempts and three hours later they got it right. Traffic reports need to be enabled via VCDS. The rather poor retrofitter had a reputation for not reabling those. I was forwarned of that one. There is a much better retrofitter in the UK now than the one I used at the time with positive reports. That's where the problem exists is to find a decent one locally. There are people that offer to do it remotely if you buy the USB box and they go online taking over your computer remotely... Not a totally good one either without risk. Extract the unit and parcel it up or a personal visit is the best (latter). The UK ones use one of the three methods.

On your PS a fake card could do that as you say, so your check would work - good idea. That one is a MIB1 high unit which shares the same upload as a MIB2 high. I see Fkw00d visited the board 22 minutes ago so still alive and kicking but only made three posts in 2019, two on the issues of the map update but no success reported. @fkw00d - see whether that works :). (comes of being a Seatcupra moderator )

Those are the Seat navigation FeCs... the Skoda ones when in play would have had something other than 073 as the lead in code. I did look at Skoda FeC post the abolition of Mapcare on Skoda hoping to find what code that they added. Basically they just abandoned that the navigation FeC in the firmware. Seat did subsequently roll out lifetime in the Netherlands on Cupra's but nowhere else, so they stuck the finish date off the end. That's in that link. One pesky retrofitter in the UK was giving out one year time limited navigation FeCs on Seats when they should have been banging the Hex code out to a high value. The retrofitter was getting repeat business linking the firmware release up to the navigation FeC on the basis that you would need a firmware release each year. Decent retrofitters in the UK now put the navigation FeC at the same value as the Cupra one well off the end of when VAG will stop releasing mib2 updates... life time isn't really life time. That's the history of that table why I created it. Been useful for people with Seats in Europe where they have taken out Mapcare but run off the end of the free updates. FeCs are in play on mib3, had a look in the local dealer but I reckon the concept of navigation FeCs has gone, they do other things... you can pull them up thou on those units and have a look.

No pesky Mac involved in what you are doing ?. If so it's the CleanMydrive and Keka to unzip as per VAG instructions for people who uses Mac's 🤣 》If the map update is performed using the Apple® OS X operating system you may find that Discover Pro does not recognise the map material or displays it incorrectly. This is due to a lack of compatibility between the “7 zip” program and the OS-X operating system. In addition, the OS-X operating system has a tendency to create hidden additional files on external data media. We therefore recommend that OS X users use the “Keka” unzipping program. We also recommend using the “CleanMyDrive” program to remove any hidden files.《 That's due to the unit checking that the upload file is in tact and not tampered with against the sla1 signature. OS-X adds rubbish characters to the unpacked so then leads to the unit failing. If not that... it is a mib1 unit. There is a Dave on this thread who used the developers menu and said they did it that way. On a mib1 that comes enabled already. Mib2 it's locked down and you use VCDS tools to enable it. Long press on the menu button if it's anything like mib2 brings it up, keep pressing till you see an SWDL option if anything like mib2. Indeed what it says on the Dave post where he links to it following the link. Otherwise called the back end menu, cuts the front end out. Fkw00d a fellow Ozzie to you referred to that on here... You could chase them down on the threads or PM them in case they had a break thru. I'd stick to fat32. The presentation is that the metainfo2 file, the two directories for mib1 and mib2 must both be on the route, not one down and no other files or directories should be present except those mentioned. I don't know what the situation is with Mapcare whether Skoda had abolitioned it in Australia by that year. VW called some vehicles in or rather you could take it into a dealer to get Mapcare removed. If it is Mapcare and you use the developers menu you will get the maps in, you will loose what was installed and it might lock you out of navigation if it's like Seat mib2 high and you go outside of the navigation FeC. You then reload your old maps presupposing you can find a copy. I mention that just in case that happens if you use the developers menu and Mapcare was in operation on the unit. Subsequently Skoda and VW abandoned Mapcare circa 2015 with mib2 (some unit on VW certainly slipped into Australia you see that on Ozzie boards), Seat kept it going thru the life of mib2. Developers menu could avoid Mapcare on mib1, but certainly doesn't on a mib2. Basically it kick starts up the update manually and the unit only runs with one task. BTW nice to see Martin quoting my Seat posts 😍.... Failing all of that you find a descent retrofitter to sort it out.

I forgot that if you are really intent on not loading up all of Europe you can use the developers menu and pick out countries. Use to pick out Iceland as the test country when I trying to update a Seat with pesky mapcare.... Iceland loads in about two minutes, not many roads so was a good fast test. Saying that you need to have the developers menu enabled on a mib2 high. That's via VCDS tools then use the backend SWDL command (Obdeleven will do it). Navdb entity is the one where you pick off which countries to update. Writes over the region so you have a mix or old and new maps in the system. As said there is no way of editing the input but you can control the upload via the backend menu. Don't think it's worth the sweat thou to save 25 minutes every six months. The maps were designed for driving across Europe even thou we aren't now with Coronavirus and Brexit. Mib3 they update over the air on a module basis so invisible to the user.

Well done