I don't do
PersonalPOI\MIB2TSD\personalpoi\InfoFile\1\default Update.txt crc ok
PersonalPOI\MIB2TSD\personalpoi\ppoidb\1\default hashes.txt crc ok
PersonalPOI\MIB2TSD\personalpoi\ppoidb\1\default\icon all icon crc ok
It's a shame I don't have a car yet ... I'd check if it works
If not then you have to wait for Radas
Workaround for test on 877 and 877A units
I see the Spanish thread doesn't know of a solution you could tell them and give Jose the links since you have a login
https://www.clubseatateca.com/threads/cargar-radares-en-los-nuevos-my19-navy-system.8455/page-31
They are off on a tangent at the minute.
I've heard from Radas and he wants us to try it out via editing. I don't have the unit with that part number. I've also forgotten the checksum trick
... which I need to get back up to speed on.
This old trick for the standard now:
Content of MIB2TSD into the root of the SD card, i.e. the PersonalPOI and metainfo2.
That avoids the signature which we can't compute then you just got got to compute the metachecksum.
Basically the first signed file with the eight line signature at the bottom you aren't be able to recreate since you need the VAG primary key and nobody has that as I understand (closely guarded secret). Since the part number had not changed on the standard side Radas kept that, the high he used the old trick of going direct. That's how it was left when VW pulled the plug on their website.
That is what will have to be done with the standard.
The contents of the standard are pulled out and put in the top directory . Then if you are tinkering with the checksums then recreate these. I think there is possibly only one to do once you find out
how to do it.
That's the one following the variant part numbers.
The body of knowledge is out there... Just got to find someone to share. Jose on the other board could follow it up with Radas as well since the Spanish thread all use his Spanish camera database constructed from Poinspector by Jose. Obliviously Radas knows
how to do it since the program computes these.
If I make a memory break through I will let you know. I did reply to Radas so I'm hoping he will add those variant codes in and recompile.
It's this in the metainfo2.txt file that can't be reproduced in the route directory
[Signature]
signature1 = "9880af1b5d5456de15affd708b3b74b2"
signature2 = "3cf0dbe1d0baf902e43229a07cfb9281"
signature3 = "3c76dea04775d174ac4f937445ae538b"
signature4 = "84d056d12279144f13341a7ccec3a7a2"
signature5 = "39120b41cbf137351aa6a08c732b3521"
signature6 = "5a224666234d8700e6c46bf2a943452c"
signature7 = "b06daa662fc8d9a1aee981c0a5df7c1a"
signature8 = "4bcd566ead66604069d58ab0a9f77d14"
This is side stepped by copying the directory
PersonalPOI\MIB2TSD
Directory
personalpoi
& file
metainfo2.txt
Into the route of the SD card replacing everything else.
That then leaves you to recompute edit the metainfo2.txt file adding the variant lines and recomputing the checksums:
----
I've got my brain in order now... been a while since I've done these metafilecheck calculations
We use the free
MD5 SHA program since we can cut and paste out the SHA1 string with this.
This utility, install:
https://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
Attached my original metainfo2.txt file from the standard directory, not the top one.
We edit out the line with
Notepad
MetafileChecksum = "a8caf02b4482130a3e8755a6be4c257b5c5db741"
and that line feed to give the file test.txt attached.
Assuming the SeatCupra site doesn't take out or add line feeds etc... on the original you run MD5 SHA and that returns under SLA1 the hash you edited out
- that's the derivation of the checksum.
a8caf02b4482130a3e8755a6be4c257b5c5db741
That's edited back in and that's the current file with Notepad.
Try it on your own subdirectory file in MIB2TSD ones the POIs have been produced.
[BTW By magic the SeatCupra site didn't add anything onto to the file so the download tallies if you run the MD5 SHA
- we like that]
Now you want to add the variants to your file in my case the test.txt file, save and put it through MD5 SHA again, that gives you the revised checksum, edit that line back in with the new varients and that should work.
That's add the lines after Variant23
Variant24 = "47215"
Variant25 = "47216"
I don't have the 877 or 877A unit but I'll check the unit, I have doesn't stumble on the edited file and checksum & the standard unit worked fine with the variants added to the list and the recompute MetafileChecksum presenting the sub directory to the unit in the top directory.
That's shift the contents of MIB2TSD to the top directory of the SD card with the edit in the MetafileChecksum following the illustration above.
Attached is the example file with the Variants on and the MetafileChecksum computed. In my data for_renaming_too_metainfo2.txt is renamed to metainfo2.txt and is placed in the route as per the instructions.
That's a worked example in the attached files from the source metainfo2.txt, example of computing the hash to producing the final file for renaming plus ofcourse putting the subdirectory contents into the route directory.
This workaround now needs testing on a 877 / 877A unit. It would appear from the German posts this is the solution... they just neglected to provide the technical info of
how to do it
.
Radas wants people with this unit to test the workaround out so he can built into the program so it does it for you.
Thanks
