Why all the new "invisible" TomToms using navcore v10/v11/v12 cannot be cracked

[lemonfish]

All of the newer TomToms from September 2010 onwards (such as the GO1000 range and all VIA models) do NOT show up as a drive on the computer and therefore cannot be accessed or edited. The reason is because they are using Linux based file systems instead of FAT/FAT32.

This wasn't a decision by TomTom to make it harder for us to copy or crack their devices. This was done because Microsoft successfully sued TomTom for using the Microsoft FAT and FAT32 file systems on a Linux platform, which Microsoft claimed it was an infringement.

Therefore TomTom were forced to use another file system other than a Windows based one. TomToms run on Linux anyway, so the choice to use Linux file systems do make the devices run faster than ever before, as their file systems are generally more reliable and capable than the older FAT/FAT32. This is a positive for customers, but it's a negative for us who want to update our new TomToms by sharing files with each other, as we do on here and other forums.

Currently the only way to update the new TomToms is to use their program called "MyTomTom," although you have to pay for updating most things like new maps and safety cameras.

So far, nobody has been successful in trying to "crack" this new system, or rather make it possible for us to update the new TomToms using Windows Explorer. One must wonder though... how hard can it really be??

Below is a list of these models using navcore v10/v11/v12 which cannot be cracked:

GO 800/1000/2000 series
Via series
PRO 7100/7100 TRUCK
PRO 7150/7150 TRUCK
PRO 9100
PRO 9150/9150 TRUCK
Start 20/25/40/45/50/60 Series
Blue & Me TomTom 2 LIVE
Sony XNV
TomTom Connect

[lemonfish]

from Downunder35m:

There is a way to access these devices using the network enviroment, but you only get access to the stuff you can freely acces using the default IP and the non protected areas:
http://169.254.255.1/mpnd/status
http://169.254.255.1/mpnd/progress
http://169.254.255.1/mpnd/trigger
http://169.254.255.1/mpnd/logintoken
http://169.254.255.1/mpnd/assocpreconf
http://169.254.255.1/mpnd/settings
http://169.254.255.1/sa/hello
http://169.254.255.1/sa/goodbye

There is also a NC10 EU map that seems to work on NC9 and these new devices but I have not tested it.
My tests with the VIA got to a stand still as my Windows now refuses to fully access the network - the TT appears as an unknown network.
I can still access it but using MyTT is rendered useless.
The problem is the Hash/RSA protection of BL and NC related folders.
You can patch a NC10/11 after "unpacking" and selecting the right file but you can't install the modifed NC because of the protection.
Same for patching on the device:
Even devices with active SD can't be patched as the actual NC files stay in the protected memory areas.
Only if someone can provide a keygen that genereates a map activation without the need of patching other maps could be used.
And for the patching part and normal keygens it would be neccessary to have a network driver (RNDIS) or program that can override the RSA protection or at least offer normal access to all parts of the internal memory.

TT recently puplished all sources for the NC's incl, NC9 and 10, so it would be only a matter of some Linux freaks developing someting usefull.
there were companies using Go720/730 with their own software as well as succesfull portations of the TT (Linux) NC to other devices but at this stage there seems to be a lack of good "hackers" willing to get going.
It was told the Truck maps can't be activated, also that 32mb devices never could use LoquendoTTS and of course that a V9NC will never work on old devices.
As we all know this was prooven to be wrong, not really by our usal hackers but by normal users with good Linux knowledge that disected the NC and offered new ways for the "old guys".
So IMHO it is only a matter of time till we laugh about TT's that can't be modifed.
But we have to be honest and realise that only active users with the right knowledge and interest will start with that or be able to make progress.
Hardest part still is finding a way around the protection or to find the correct private key.
Check the Wiki pages in regards to RSA and you'll understand