Using the map portal and entering my VIN I am offered two download options.

 

ECE 2021/2022 and ECE 2022

 

Do I download both? ECE 2022 won’t unpack and errors out. ECE 2021/2022 does I pack but the car says it’s the wrong format. 
 

I’m using a Mac, FAT32 formatted 64GB USB stick. 
 

Current map version in photo:

 

 

1 hour ago, simonharper said:

I’m using a Mac

 

Are you using something sensible to unpack the file... the built in archive tool is pants, especially on very large files. Try Keka or similar from the App Store. Also, when writing to the USB drive, make sure it doesn't crap AppleDouble (loads of hidden dot files) all over the drive - again, there are utilities such as Blue Harvest that will help you out there.

 

Disclaimer: no inherent interest in either of those apps, but long time user of them.

Many thanks, found utility that works, Unarchiver One. Couldn't find Keka on the App Store.

 

Will seek out Blue Harvest.

 

do I need both downoads or just the one?

Just the one… 2022 will be more recent than 2021/2022.

1 minute ago, Yogi-Bear said:

Just the one… 2022 will be more recent than 2021/2022.

Thanks for that. Have downloaded both so will try the 2022 one and see if it works. 

Tried both on a FAT32 formatted USB stick and the system spends a while checkign the USB then says there is no data on it. I'm using the USB port in the centre console where you plug the phone in to charge and use CarPlay. Do I need to buy an SD card and try those slots in the glove box? The Columbus system shows SD/USB as options so assume the USB port should work.

 

Thanks

Suppose to use Keka and CleanMyDrive. Mac's produce garbage characters at the of the data rows. CleanMydrive run on the SD card after getting the files onto it wipes that out. However there were / are issues with the compression used on the latest maps (195). See MartiniB's thread.

 

Possible that the Mac software can handle the unzipping without throwing up errors but is highly likely you will need to give the resulted output a good buffing with CleanMydrive. Keka and CleanMyDrive are the recommended VW Mac tools. If you still have an issue unzipping use the VW download. That's zipped without the variable compression that causes issues with Skodas 195 release.

 

Refer you to MartiniB's thread.

 

 

Footnote. Why the Mac random characters cause an issue is that the mib2 high unit performs an sla1 signature check before importing the map so stops in its track if one byte is out. I know this since I spent a long time trying to edit the import file, it's cryptographically signed. Mac's don't get on well with these files.

Edited 29 March, 20224 yr by Tell
put link in to MartiniB's post

Thanks Tell, Yogi-Bear also recommended these free apps so have now downloaded them from the AppStore and will give them a go.

The only issue will be how the Mac apps for unzipping work with the new variable compression method Skoda used on 195. If that fails uses MartiniB's VW link for 195, your Mac unzip but I bet you will still have to use CleanMyDrive although some report in the past that they can get away without using CleanMyDrive. I sorted out a Seat owner last week you was doing it in a Windows shell in a Mac but still had to use CleanMydrive at the end. 

 

The Mac issue was why VW had their own app but discontinued that now... was not updated in a timely fashion so people just stuck to the Mac instructions where they could get the latest off the servers than wait for VW to update it.... If only I remember the name of that 🙄. I deleted it myself, was a PC and Mac version that took out the unzipping / file preparation stages. You poked the card in and it did the lot. 

ah right. shame they don't have the VW app anymore. I drove Land Rovers for 25 years and their app was very clunky and the dpwnloads were horrendous, but always seemed to work fine from USB drive. Have inn theory cleaned my USB with CleanMyDrive2 so fingers crossed it works. Used Unarchiver One to unzip the download without any errors so hopefully its ok. The macOS unarchiver errored out each time.

Sounds like it will be fine. You run CleanMyDrive once it's on the SD Card. As I said some people get away without using CleanMyDrive, that will be where it unzips directly to a clean SD card removing the Mac dross within the unzip where the program is clever enough to do it. Keka can't be why VW say use CleanMyDrive as well.

 

Suspect the Mac unzipping software would have moaned about the Skoda file if there was an issue. PC one does, where the inbuilt file explorer one didn't. Tripped a few PC people up.

Car now recognises the map update on my USB stick. Currently at 70% and progressing 👍🏼

Thanks so much guys for your help. Car now updated to ECE2022, took about 20 mins to copy across and install from the USB port.

I updated the map on the bear yesterday using the download from the portal.

The instructions say to format the SD card to exFAT so I did and it worked first time.

IIRC, they also say to leave the ignition on.

I tried it by leaving the ignition off and just turning the infotainment on, starting the update and locking the car and walking away.

The infotainment switches itself off after about 30 mins but the update continues, which is nice.

 

2 hours ago, CFB said:

I updated the map on the bear yesterday using the download from the portal.

The instructions say to format the SD card to exFAT so I did and it worked first time.

IIRC, they also say to leave the ignition on.

I tried it by leaving the ignition off and just turning the infotainment on, starting the update and locking the car and walking away.

The infotainment switches itself off after about 30 mins but the update continues, which is nice.

 

Fat32 is good but if a bigger card to 32GB then exFat. If 32GB Fat32.

 

You can do it without the engine running if you open the door every 20 minutes. I do it in 15 minute goes since I use the backend developers menu (SWDL) since it shows what's going on and I just like to get it out of the way. I'm sure on the front menu you can switch off, lock-up and revisit the car every 15 minutes as I do. The system powers down at 20 minutes why you got caught out at 30 minutes. 5 minutes leeway to get your shoes on, spend a penny etc. On the normal update menu it remembers where it got to so continues from there, the back end menu forgets and you have to start again from scratch.

21 hours ago, Tell said:

Fat32 is good but if a bigger card to 32GB then exFat. If 32GB Fat32.

 

You can do it without the engine running if you open the door every 20 minutes. I do it in 15 minute goes since I use the backend developers menu (SWDL) since it shows what's going on and I just like to get it out of the way. I'm sure on the front menu you can switch off, lock-up and revisit the car every 15 minutes as I do. The system powers down at 20 minutes why you got caught out at 30 minutes. 5 minutes leeway to get your shoes on, spend a penny etc. On the normal update menu it remembers where it got to so continues from there, the back end menu forgets and you have to start again from scratch.

thanks for the FAT32 and exFAT explanation.

Maybe I was misunderstood regarding the map upload. What I meant is that the update continued even though the system switched off after the 30 min timeout and completed the update without having to go back to the car several times.

On 27/04/2022 at 11:58, CFB said:

thanks for the FAT32 and exFAT explanation.

Maybe I was misunderstood regarding the map upload. What I meant is that the update continued even though the system switched off after the 30 min timeout and completed the update without having to go back to the car several times.

It does do. That's how people normally do their map updates on mib2 high units driving too and from destination although the sat nav is not available during the process. The overrun of the car's systems being powered on for 20 minutes after ignition off, the wind back in the up date if power lost eventually leads to the full update going thru. A 20 minute drive plus 20 minutes after gives you 40 minutes. Truncate the drive from 20 minutes, some wind back, recommence from a restore point in that, plus 20 minutes and the restore point difference gives you the 40 minutes 😍. It's the restore point that it uses in the normal update that works differently to using the developers SWDL menu where you need for power for the duration since the restore point is zero minutes into the process e.g.. start over again. Front menu you can break the update into parts which it handles automatically.