I format the usb to NTFS g that sorted it. 

 

Cheers fellas

23 hours ago, BooBoo124 said:

After looking at the manual the MMI will only read exfat via SD card & not USB. So above 32gb NTFS is indeed the go to format

 

Interesting FLAC isn't on that list. Reckon that's an old page :). Newer firmware / hardware in Mib2 High's plays Flac. The image size of 800x800 doesn't tally with 512x512 standard as per Seat Mib2 and Mib3 spec.

 

I've printed it out as my off pista update routes for the maps. I can see with more modern PCs cutting down on ports they may not have SD card slots so USB may have attractions to some for the update rather than using the VW instructions I posted up above which is the gold standard dealing with Mac's as well.

2020 version

22 minutes ago, BooBoo124 said:

2020 version

But it's not showing a WAV file thou 🙄. They will all be the same but varying quality of documentation. I reckon it won't resolve 800×800 cover art thou. 

So I'm going to do the map update today. Do I need to sit with it which it does it. Or can I get it going and lock up and let it get on with it like OTA updates?

29 minutes ago, BooBoo124 said:

So I'm going to do the map update today. Do I need to sit with it which it does it. Or can I get it going and lock up and let it get on with it like OTA updates?

How it works normally without aiding it is that it churns away doing it 20 minutes after you close the door with ignition off, then stops, it has a restart point, then will restart from there. The whole process is ~40 minutes but with restore points can be longer since it restarts from where it got to when it dropped the restart point. You can cheat by opening the ďoor and closing it before the 20 minutes is up. 20 minutes is the power down, the normal one when the radio / music stops if sitting in the car. Some people say you can leave the door open, never tried that. Most people just drive to work without navigation and get the ~ 40 minutes one way or another.

 

I use the SWDL menu since I like to get it done and see the stages. You must open and close the door every 15 minutes on that, 5 mins leeway. No restore point, you have to start again if it looses power. One of these days I may do it the normal way 🙄.

Edited 15 May, 20223 yr by Tell

Update success in 29mins

Thanks guys. 

12 minutes ago, BooBoo124 said:

Update success in 29mins

Thanks guys. 

Probably the USB 🤣. 

Thanks! Updated within an hour (SD Card - SanDisk Extreme). In the end only copying the update to SD Card on Windows machine worked, on a Mac (event though I deleted the hidden files) it always errored out when trying to update.

 

What I don't understand is that I have reported issues on roads via https://mapcreator.here.com/ and even received confirmation that these changes are correct and will be implemented in Q1 2022, none of them is implemented in the latest update, though. 

3 hours ago, tp_ said:

Thanks! Updated within an hour (SD Card - SanDisk Extreme). In the end only copying the update to SD Card on Windows machine worked, on a Mac (event though I deleted the hidden files) it always errored out when trying to update.

 

What I don't understand is that I have reported issues on roads via https://mapcreator.here.com/ and even received confirmation that these changes are correct and will be implemented in Q1 2022, none of them is implemented in the latest update, though. 

On the first just one character out can lead to the map upload being aborted. Keka and CleanMyDrive are the two techniques for a Mac, Keka unzips, CleanMydrive deletes all the Mac characters it puts in, that's run on the SD card. The SLA1 signatures check is carried to ensure the files have not been tampered with. A VAG master key (primary key) is used construct the signature based on the contents of the file. A user key is built into the unit. Examination of the contents with the signature and if it says, "yes" it get passed for import. What must have happened the cleaning process whatever you used didn't clean as expected. Whilst I don't have a Mac it always works when I tell people to use those two pieces of software as VW recommends.

 

For the hell of it I once ran the SLA1 authorisation algorithm with the set of user published keys.  I found that the master key, whatever that is, is the same across the firmware and map files since the same user key would work. A few years back you needed a month's Cray super computer time to crack the master key, why the industry was telling people to get off 1024 SLA1. They study this subject at University now.... branch of applied mathematics coming from pure... once you get the master key you can manufacture source files that appear as real ones. The mib2 firmware exploits have been done by avoiding the signature key check. The family of mib tool / toolkit software and firmware presented in such a way plus developer tools left in the firmware, clever.

 

On your second MartiniB's attention to detail he publishes when the files were processed within them, in this case

 

Files inside:    2021.10.14

 

The process is Here Maps will generate the master file and it goes off to whoever turns these files into the VW map files. Thus your 2022Q1 is outside of the date.

 

The Here Maps app Here WeGo is suppose to be the first view of the production files and if that is wrong, that's when you tell them since they have duff data in their master file. Co Pilot also gets updates more frequently so you can check there as well to see whether their master database reflects what it is suppose to be. 

 

The Mapcreator app seems to use artificial intelligence to pull parts of maps apart and falls foul of rounding error !. Sure it does, so it decides points you placed together get pulled apart, duplicates included etc. To combat that you have to visit the same location on the map daily say and run across the bottom right horizontal bar validation tool clicking on each item to see what it's revealing. Where the automated validation system has introduced errors they can be seen there plus joins in roads left open. They are only geographers that run these systems bless them 😉.

 

MapCreator you are working with the development database, not the production database. You also get pestered with mapping fantasists that place farm tracks on maps as highways. Builders roads on development sites that should never be digitised and the rest of the nonsense. Here Maps process do study other digital maps and flag up what they have "missing" against others. So nonsense from those maps can get into HereMaps if not correctly validated. They use probes generated from mobile file track data as well as a tool.

 

In the UK OS planning maps used by local authorities can be used as the gold standard for what is on the ground. They are part of the Land Registry maps done by proper surveyors, next level up is the developers plans on new builds which they sell the houses against. The aeriel image can be compared with them. Street View is useful but also shows how Google bounces their cars down private farm tracks and they get put in as public roads. The speed that is digitised against minor roads will also effect the cars routing algorithm, where some of the rubbish routing comes from. 

Edited 16 May, 20223 yr by Tell
spelling

20 minutes ago, Tell said:

On the first just one character out can lead to the map upload being aborted. Keka and CleanMyDrive are the two techniques for a Mac, Keka unzips, CleanMydrive deletes all the Mac characters it puts in, that's run on the SD card. The SLA1 signatures check is carried to ensure the files have not been tampered with. A VAG master key (primary key) is used construct the signature based on the contents of the file. A user key is built into the unit. Examination of the contents with the signature and if it says, "yes" it get passed for import. What must have happened the cleaning process whatever you used didn't clean as expected. Whilst I don't have a Mac it always works when I tell people to use those two pieces of software as VW recommends.

 

For the hell of it I once ran the SLA1 authorisation algorithm with the set of user published keys.  I found that the master key, whatever that is, is the same across the firmware and map files since the same user key would work. A few years back you needed a month's Cray super computer time to crack the master key, why the industry was telling people to get off 1024 SLA1. They study this subject at University now.... branch of applied mathematics coming from pure... once you get the master key you can manufacture source files that appear as real ones. The mib2 firmware exploits have been done by avoiding the signature key check. The family of mib tool / toolkit software and firmware presented in such a way plus developer tools left in the firmware, clever.

 

On your second MartiniB's attention to detail he publishes when the files were processed within them, in this case

 

Files inside:    2021.10.14

 

The process is Here Maps will generate the master file and it goes off to whoever turns these files into the VW map files. Thus your 2022Q1 is outside of the date.

 

The Here Maps app Here WeGo is suppose to be the first view of the production files and if that is wrong, that's when you tell them since they have duff data in their master file. Co Pilot also gets updates more frequently so you can check there as well to see whether their master database reflects what it is suppose to be. 

 

The Mapcreator app seems to use artificial intelligence to pull parts of maps apart and falls foul of rounding error !. Sure it does, so it decides points you placed together get pulled apart, duplicates included etc. To combat that you have to visit the same location on the map daily say and run across the bottom right horizontal bar validation tool clicking on each item to see what it's revealing. Where the automated validation system has introduced errors they can be seen there plus joins in roads left open. They are only geographers that run these systems bless them 😉.

 

MapCreator you are working with the development database, not the production database. You also get pestered with mapping fantasists that place farm tracks on maps as highways. Builders roads on development sites that should never be digitised and the rest of the nonsense. Here Maps process do study other digital maps and flag up what they have "missing" against others. So nonsense from those maps can get into HereMaps if not correctly validated. They use probes generated from mobile file track data as well as a tool.

 

In the UK OS planning maps used by local authorities can be used as the gold standard for what is on the ground. They are part of the Land Registry maps done by proper surveyors, next level up is the developers plans on new builds which they sell the houses against. The aeriel image can be compared with them. Street View is useful but also shows how Google bounces their cars down private farm tracks and they get put in as public roads. The speed that is digitised against minor roads will also effect the cars routing algorithm, where some of the rubbish routing comes from. 

 

 

Thank you for exhaustive answer to my questions. I will definitely use the Keka / CleanMyDrive when updating the Navi next time in the future.

 

Back to the maps, I haven't noticed the  "Files inside:    2021.10.14" row, so please pardon my ignorance.

 

Does it basically mean we are actually updating the navigation data within the cars to approx. half a year old map data? (At least that's what seems to be a trend from the previous updates - the "files inside" were approx 6 months when the update was released)

1 minute ago, tp_ said:

Back to the maps, I haven't noticed the  "Files inside:    2021.10.14" row, so please pardon my ignorance.

 

Does it basically mean we are actually updating the navigation data within the cars to approx. half a year old map data? (At least that's what seems to be a trend from the previous updates - the "files inside" were approx 6 months when the update was released)

Short answer, yes.

 

Here supply the raw map data to VAG many months before VAG release the maps because it takes them time to convert the raw data into the correct format for their sat nav systems.

 

On the older VAG sat navs (e.g. RNS-D, RNS-E, etc) the map data freeze was August of the preceding year, so October is an improvement!

8 minutes ago, PetrolDave said:

"Files inside:    2021.10.14"

 

8 minutes ago, PetrolDave said:

Short answer, yes.

 

one of reason why i prefer Waze, saved me huge amount of euros

and Google Maps for abroad(EU) trips

 

22 minutes ago, MartiniB said:

 

 

one of reason why i prefer Waze, saved me huge amount of euros

and Google Maps for abroad(EU) trips

 

I've seen nonsense data on Waze... complete garbage where someone has digitised a housing estate that has not even been built. Certainly hasn't passed any QA checks. Google Maps also have processing delays plus rubbish QA. Another one with a complete housing estate missing for 5 years. I don't give them any stuff now. Tough they won't take out a farm track in the village which leaves cars coming down and dead end or bouncing down an unmade road. DHL and Amazon use the farm track... One of them ran over a dog in the dark charging down the farm track that isn't a road. So they can rot.

 

I keep Here Maps and TomTom up-to-date but won't touch Google Map editing since they are rubbish. It's the domain of poor QA and mapping fantasists that enter roads where there aren't any since they feel there is a public road from the aeriel image... no. Farm tracks plus the ones that take plans for an estate that hasn't been built on a green field site and put roads in. 😨. They are not kicked out during QA.

Edited 16 May, 20223 yr by Tell

Dumb question. Can I use a USB stick inserted into the USB slot next to the phone holder to update the Columbus?

 

I've used an SD Card into the reader on the unit in the glovebox in the past to update, but I just wondered if a USB was an option?

Yes I did. I used a 64gb drive format to NTFS

21 minutes ago, BooBoo124 said:

Yes I did. I used a 64gb drive format to NTFS

Nice one - cheers! 👍

1 hour ago, numskull said:

Dumb question. Can I use a USB stick inserted into the USB slot next to the phone holder to update the Columbus?

 

I've used an SD Card into the reader on the unit in the glovebox in the past to update, but I just wondered if a USB was an option?

SD 32gb card, class 10 in Fat32 is the official way of doing it as recommended by VW in their material which is the gold standard. The maps haven't busted the 32gb SD card yet in Fat32. It does if the card is in NTFS.

 

I just keep a couple, this release, last release and rotate them. Nice 3/4" scrap of paper with the release number written on it clipped in the box.

hi to every one i own an Audi a5 2017-2019 with Audi MMI Navigation Plus  MHI2Q are this map good for update?

i tried ( and get error) my unit is patched 

regards

 

Assuming it's mib2 high and patched with the life long navigation FeC for Audi the conversation above as I recall, if not on the previous release, then it's going to be you are using a Mac and you need to use CleanMyDrive on the SD card after unzipping it. That's the common Mac error after unzipping. Failing that it's the format issue where I say stick to SD card 32gb, fat32 else you enter the territory of formats, covered above. That's about it.

 

The life time navigation Audi FeC was published above or on the other thread. Look at yours and compare. Some retrofitters scam by just giving you a short term FeC to induce extra work. Why you need to check what you have against the life long FeC. That's set at the high point in the table where VAG will stop issuing releases before you hit that.

 

Edit. Was this thread. Audi 23000ee the one Boo boo had.... we went round the houses before pinning the issue down, check yours and check unzip, Mac issues and format plus attached VAG (Discover Pro pdf above) notes I posted on the process above. Some Skoda drivers go off piste by using USB sticks then you enter the format debate. Stick to SD cards class 10 32gb and we dont need to cover that... the Vag guidance.

Edited 29 May, 20223 yr by Tell
making it nice

Yes they are. I have the same unit in my A4 you need fec 23000ee

 

thanks i think is mac related problem now i retry using cleanmydrive
and i'll check FEC on my car 

 

Thanks to all

 

CleanMyDrive solved mi issue 😎

Thanks again 

Greetings from italy

 

Top work my friend 

I dish out the Mac advise although I don't have one... wash my mouth out with salt water... but it fixes them all. Mac's stick an extra carriage return on the line or whatever. The map file is protected with a sla1 signature which means a secure signature is placed on the metainfo2.txt file. Private / User key.

 

https://en.m.wikipedia.org/wiki/SHA-1

 

Vag signs the map file with their private key, the unit knows the public key and says, yes, this checks out and allows import. 1 character out and it rejects it. You can't manufacture the private key from the public key unless you have a security service type of computer like a Cray 😍. Then you could manufacture an import file via the secure methods.

 

Ways around avoiding the signature have been found with the mib2 unit... they didn't close down feeding other code into the unit after the signature which is the exploit that developers of mib tool boxes use and specialist modified firmware which also carries the FeCs through another developers exploit. Saying that cross checks are not made on the integrity of what gets imported if you avoid the signature check so CleanMyDrive is even more important on a Mac if you are importing firmware of this nature.  All clever stuff.

 

CleanMyDrive removes all the bloat Mac characters so it looks like the PC download.