Mines a Feb '16 build car so no doubt will take longer than 40 mins, but I'll wash and rewax the flat surfaces with Poorboys Natty Paste Black whilst I wait - have a loooog trip ahead. 

1 hour ago, numskull said:

Mines a Feb '16 build car so no doubt will take longer than 40 mins, but I'll wash and rewax the flat surfaces with Poorboys Natty Paste Black whilst I wait - have a loooog trip ahead. 

If you poke the infotainment back on 20 minutes in you'll get the 40 minutes or so all in one go. As I said it does put the update on hold untill it's stirred back to life, so you get 20 minute segments if it's standing. Like when you are sitting in the car and it turns the radio off, those are the 20 minute segments of power it's using or if driving all the time then into 20 minute segments after last closing the door.

Cheers guys - all done and dusted! Got a bit worried when the screen went blank towards thge end and thought itd completed.... and I took the SD out but the unit told me to stop being stupid and put it back in (I paraphrase obvs!) and it then completed. Brilliant! 

Will the update work if you only copy to USB the region files specific to your country, e.g. Australia?

 

Thanks.

1 hour ago, GWCTas said:

Will the update work if you only copy to USB the region files specific to your country, e.g. Australia?

 

Thanks.

There are file checks on the import to stop user fiddling, also protect errors getting in via the download. It's all or nothing with the files. Mib2 standard you can fiddle with, mib2 high you can't.

Edited 19 July, 20213 yr by Tell

Thanks. I assume that means also having both MIB1 and 2 folders on the USB?

9 minutes ago, GWCTas said:

Thanks. I assume that means also having both MIB1 and 2 folders on the USB?

Indeed. It's a joint release it uses both directories getting what it wants from either . Some of the mib2 stuff is held in mib1 directory.

 

If using a Mac you need to follow the Keka, CleanMydrive guidance. Pc, 7zip.

Hi everone

not sure where this topic went but I had the same issue updating my columbus unit in my vrs and here is what I worked out:

 

1. you cannot just remove some of the country files from some other country to reduce the file size to fit the SD card as there is a checksum that causes an error. You could possibly re-engineer this but that's questionable.

2. Not all 32G SDcards are created equal, I was using Toshiba 90mb/s but it formatted to 28.5G and the files would not fit on either fat32, exFat or NTFS. I then looked at my sandisk 80mb/s 32G card and it formats to 29.7G and the the files fitted ok.

 

I guess the answer is that if you are not sure just get a 64G card and the problem will go away or go through all your 32G cards until you find one that formats to 29.5G which is what I did.

 

cheers

Chris

AUS

 

2 hours ago, Old****** said:

Hi everone

not sure where this topic went but I had the same issue updating my columbus unit in my vrs and here is what I worked out:

 

1. you cannot just remove some of the country files from some other country to reduce the file size to fit the SD card as there is a checksum that causes an error. You could possibly re-engineer this but that's questionable.

2. Not all 32G SDcards are created equal, I was using Toshiba 90mb/s but it formatted to 28.5G and the files would not fit on either fat32, exFat or NTFS. I then looked at my sandisk 80mb/s 32G card and it formats to 29.7G and the the files fitted ok.

 

I guess the answer is that if you are not sure just get a 64G card and the problem will go away or go through all your 32G cards until you find one that formats to 29.5G which is what I did.

 

cheers

Chris

AUS

 

You have a blend of topics there.

 

1. You can if it's a mib2 standard but not Columbus. The language files you chump out to get it to fit on the 16gb VAG card since the last release popped the card size. But that's off topic. The mib2 high release which is what Columbus is (mib2 high) uses a signature on the sla1 to protect the release from meddling. You see that signature at the end of the metadata2 files, a bank of four codes, if you see that it's signed. Apart from a hack that's been discovered with the mib2 hardware where you can add some code after it and it slips in undetected, you can't meddle with anything infront of it. One character out and it stops the upload to the unit. It is also protects the unit from any jigger in your communications in getting the download although 7 zip shouldnt unzip if you had that. That's where Mac users with unclean uploads that don't do CleanMydrive get caught out. The hack mentioned is used by the Green Menu (Gem) mib2 toolkits to get their payload into the unit so you can do retrofit activity in the car without pulling the unit out and putting it on a bench.

 

So in essence you can't fiddle with the map upload due to the sla1 signature check, that's more than a checksum.

 

2. The card issue comes up due to cheapskates that won't buy the correct 32gb card and keep it formatted in fat32. They know best and propergate using different cards or usb sticks for the job in something other than fat32, people follow then find it doesn't work. The classic one in the last release of mib2 high was if you had the card formatted in NTFS it wouldn't fit due to the pointers to support NTFS take up more space than fat32. A fat32 full size SD card from Amazon Prime from a well know make will cost about £7 in the UK why use anything different ?... but they do. Veer away from VAG recommendations of fat32, 32gb standard SD card at your peril. It's only the HD that's suppose to be in NTFS, that piece of vag text is clumsily written not the SD card.

 

"Well known make" covers Sandisk etc. Possibly true that dubious cards get caught out in the last release like the Toshiba card since it was the biggest release yet for Europe, not sure of Oz. We say use Amazon Prime since it's be known that Marketplace ones can be of the fake type. Saying this I have had no issue with Aldi / Lidl 32gb SD cards I inherited from by brother... probably have good QA on their suppliers. Testament to German discount chains :).

 

-> next 2022

Edited 22 October, 20213 yr by MartiniB

44 minutes ago, MartiniB said:

-> next 2022

Next 2022 but where 😉.

 

I see it hadn't arrived yesterday when I guessed the range of names, not as good as your processes thou. Meanwhile the German Skoda board has missed the November 2021 standard mib2 release (combined thread), still preoccupied with the 192 release, NTFS v Fat32 and how to copy the files. Groundhog day.

20 minutes ago, Tell said:

Next 2022 but where 😉.

https://www.briskoda.net/forums/topic/498563-columbus-map-update-2022-mib12-high/