I have the 6P0 Navigation System (not the PLUS, my does not have a HDD) with 0635 maps (bought 06/2016).
Today I tried wiping the card (made a complete back-up first) and copied the contents of the '0730_MP161-1231a.xEUR1' package on it.
Long story short, it did not work. However. I made a couple of experiments:
1. I copied a new version of the maps/00/nds/ROOT.NDS to the original SD card with the original content on it. It was accepted
2. I also copied a new version of the maps/00/nds/PRODUCT/PRODUCT.NDS to the original SD card with the original content on it. It was still accepted
3. I tried to copy a newer version of any file under maps/00/nds/PRODUCT/E**/ to the card. At this moment it was not accepted. It's interesting to note that the card was refused in under 1-2 seconds. This is not enough to read the contents of the files in a single directory (given that the smallest one, E13, is still around 200MB).
My conclusions:
1. While the SD card itself is somehow protected, the contents does not matter. It's more of a 'cloning' protection, than upgrade protection. The reason that those who have 'MapCare' can overwrite the contents of the SD card proves this.
2. The navigation itself must store certain attributes of the SD Card, or the files (or both) that allows it to accept or refuse the SD CARD as a whole or the content on it
3. Not all files are checked for eligibility on the SD card.
4. The quick refusal of the SD card IMHO rules out any checksum (MD5/SHA) based protections, as those would take ages to read (practically the whole SD would need to be read before it could be approved/rejected)
TODO: Rule out file modification date based protection:
>> try changing one file's attributes (create/modify dates), as well as size (add an extra byte to it, yet keeping the dates in tact) and see if it gets accepted or not.
Today I tried wiping the card (made a complete back-up first) and copied the contents of the '0730_MP161-1231a.xEUR1' package on it.
Long story short, it did not work. However. I made a couple of experiments:
1. I copied a new version of the maps/00/nds/ROOT.NDS to the original SD card with the original content on it. It was accepted
2. I also copied a new version of the maps/00/nds/PRODUCT/PRODUCT.NDS to the original SD card with the original content on it. It was still accepted
3. I tried to copy a newer version of any file under maps/00/nds/PRODUCT/E**/ to the card. At this moment it was not accepted. It's interesting to note that the card was refused in under 1-2 seconds. This is not enough to read the contents of the files in a single directory (given that the smallest one, E13, is still around 200MB).
My conclusions:
1. While the SD card itself is somehow protected, the contents does not matter. It's more of a 'cloning' protection, than upgrade protection. The reason that those who have 'MapCare' can overwrite the contents of the SD card proves this.
2. The navigation itself must store certain attributes of the SD Card, or the files (or both) that allows it to accept or refuse the SD CARD as a whole or the content on it
3. Not all files are checked for eligibility on the SD card.
4. The quick refusal of the SD card IMHO rules out any checksum (MD5/SHA) based protections, as those would take ages to read (practically the whole SD would need to be read before it could be approved/rejected)
TODO: Rule out file modification date based protection:
>> try changing one file's attributes (create/modify dates), as well as size (add an extra byte to it, yet keeping the dates in tact) and see if it gets accepted or not.