OK, here's the link: [Only registered and activated users can see links. ]
Here's how you use it.
* Grab the file, and unpack it. (Password is "A" without quotes).
* Rename the NaviPnd.dll on your SD card to NaviPnd.bak. (Just in case this doesn't work, you can go back).
* Copy the NaviPnd.dll from my file over to your card.
* Plug it into the car, and try it.
Disclaimer:
This hack comes with no warranty. If it causes your car to become sentient and swear at you, it's not my fault. You use it at your own risk. As I've said above, if it fails, and prints an error message, take a picture, and post it to aid in debugging the problem.
How it works:
The code reads the card ID from the SD card, and then compares it to what it expects. (I assume it's part of the hash in the unlock files). It then makes a decision based on it. "Is this good? Or is it bad?". I changed the "Is it good" to say "It is good", and to go on about it's business. If we're lucky, it'll just work, and we're home free. If they copy the card ID over again later, and use it for something, it might not work. I have a couple of angles up my sleeve if that's the case.
Good luck!
Last edited by FrankRizzo; 9th August 2015 at 02:35 AM.
Moderator why a link which you have to pay ?
OK, I'm trying to determine exactly what's going on here. It's probably 1 of a couple of things.
* It could be that the file is signed, and it's checked by the firmware in the head unit. If this is the case, we're dead unless someone has a spare headunit they don't mind loaning to me.
* It could be that the application CRCs itself. If THAT'S the case, then we have a possibility. (I might find where this is done, and disable it).
So, to help me determine which of those is the case, I have prepared a test file. The steps for this are the same as they were for the hack above. Slap this on the card, and see what it says.
[Only registered and activated users can see links. ]
(There's lots of slack space at the end of the file. I changed 1 byte of that. If the code checks itself, this should be fine. If the headunit is checking it, it'll still fail.)
(Just in case anyone is curious, the disassembly of this .dll is 9,544,014 lines long. There's lots of room for stuff to hide.
Last edited by FrankRizzo; 10th August 2015 at 03:56 AM.
Hi
I think when garmin creating these SD Cards, They are reading CID of SD card and writing somewhere in the files. May be it is encrypted.
Than One SD card inserted in the Audio CD 20, It should compare CID of the SD card and from the file where it is hidden.
So you need to know the CID of the SD card which its files shared here so you can search in the files. If you can find the place, It is possible to read CID of other SD cards with using this tool
And Possibly everybody can use their own CID of SD cards and write in the place.Code:Please Login or Register to see the links
What do you think friends
If you discuss this previously and if this is a duplication I am sorry
Last edited by Neil; 11th August 2015 at 08:53 PM. Reason: Coded link [please code all outside links as per Rules] ;)
Bookmarks