Doesn’t install any faster because MIB2 always ignored the MIB1 files it didn’t use (those named *map3D*.psf).  It does however download faster, copy to the card faster, and fit on a smaller card.

 

I suppose the only downside is if you own both a MIB1 and MIB2 units you need to download 2 updates, large parts of which are identical. Doubt that situation applies to many.

Note that the files you could download from the Audi portal have always been like this update - MIB2 specific and smaller.  Not sure why VAG used to combine MIB1 and MIB2 for the VW and Skoda sites.  I suspect having a combined update simplified the download selection as users did not have to identify their system as either MIB1 or MIB2.   It’s still possible the official download that VW post may in fact be a combined one.

 

You can always ”shrink” a combined MIB1 and MIB2 update to a platform specific one…

For MIB1… delete the MIB2 folder.

For MIB2… delete all the *map3d*.psf files from MIB1 folder, and MIB1\metainfo2.txt as well if you want.

27 minutes ago, pcbbc said:

You can always ”shrink” a combined MIB1 and MIB2 update to a platform specific one…

For MIB1… delete the MIB2 folder.

For MIB2… delete all the *map3d*.psf files from MIB1 folder, and MIB1\metainfo2.txt as well if you want.

That would fail the SLA1 signature.... Well I reckon. You cant mess with the contents of those directories without resigning them and nobody knows the private keys. You can shuffle the files using that back door trick used on the AIO software but you would be redoing all those checksums ($). Clever people that do that unless they got it automated.

 

$ assuming you can do that on the map files. That's where I'd like someone to take mib3 maps and make mib2 high ones if / when they pull the plug on mib2 high updates. Suggested that to Chillout who said it would be "cool". We may need a cool person in the future to keep mib2 high updates going. Hands up.

 

 

 

Edited 29 October, 20231 yr by Tell

9 minutes ago, Tell said:

That would fail the SLA1 signature....

No it won't.  I've done it many times on MIB2 to shrink the VW updates to a 32GB card.

 

Contents of packages are specified and hashed in content.pkg and signed for wtih content.sig files.

The MIB1 package files reference only files under MIB1 folders and INCLUDE the MIB1 *Map3D*.psf files.

The MIB2 package files reference both MIB1 and MIB2 folders, but EXCLUDE the MIB1 *Map3D*.psf files (and include the new MIB2 AdvancedMap2D.psf files from the MIB2 folders).

 

As MIB1 only ever looks at content.pkg from the MIB1 folders, it won't notice you've deleted the MIB2 folder.

As MIB2 only ever looks at content.pkg from the MIB2 folders, it will be none the wiser you've deleted *Map3D*.psf files (as those files aren't even mentioned in it's copies of content.pkg that it's using for the install).

Mind you I still think for the "average user" I.e. one with limited technical knowledge not to hack the mib2 high map files around.  We might be dependent on you or whoever has access to the Audi servers if the mib2 high map files are continued to be rolled out beyond 2025 as you suggested re the TT ?. Then some clever "cool" soul to rework mib3 to mib2 high. I'm sure that possible.

 

44 minutes ago, Tell said:

Clever people that do that unless they got it automated.

Actually not that clever as they left a huge backdoor in the metainfo2.txt signature check that allows you to create your own installers (e.g. MIB Toolkit, etc) with impunity.
 

Not sure that will help us with map updates though, as the map files are signed separately and not vulnerable to the above exploit. So you can push unsigned map files onto the system with a hacked metainfo2.txt, but they won’t work if they fail the internal checksum* in the associated content.pkg files.

 

* Actually the checksum is only performed if the files size changes (or maybe it only checks the file size against the signed content.pkg - I don’t know). So if you keep the file the same size you can make changes and the navigation will run. That’s not really a lot of use if you want to make a map update though!

 

 

Edited 29 October, 20231 yr by pcbbc

Official update from VW servers (without archive errors):

 

VW1
VW2

Think those are the ones that MartiniB posted up this morning. Post #1. He's editting them in as they come up but a few false turns with problematic Skoda releases 🤔🙄. They are. The second link wasn't working. The first one was this morning.