Given a map from mobile GO app (including meta and dct files) and the App ID, is this possible to find the Blowfish key to use the map on classic TT device? Have anyone tried? Is there any tool to help archieve the goal?

[Login or Register to remove this advertisement]

vda767 Reviewed by vda767 on 27th June 2018. Porting map from GO app to classic device Given a map from mobile GO app (including meta and dct files) and the App ID, is this possible to find the Blowfish key to use the map on classic TT device? Have anyone tried? Is there any tool to help archieve the goal? Rating: 5

impossible - due to different format of maps (higher) on mobile GO - about 1005 IMHO, whilst NAV2/NAV3 carries only up to 810. Hence - maps from mobile GO can't be used on regular NAV2 devices

But what about running patched latest Navcore on such a device having sufficient internal memory and mass storage? Could you explain the term "format of maps" such as 1005 or 810, please? I thought it was map version, not format. Wasn't it?

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Why? Devices, which uses such a maps - NAV4/NAV5/Go-TT-Trafic - don't need any patches, cause they have life-time map upgrade options - what do you want to patch?
And NAV2 devices can't operate with these maps

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Map format (as we call it) - internal parameter which TT uses to get navcore information if it can operate (and mount) concrete map. It embedded in particular navcore, and at the same time - in mapinfo.dat file. Shortly, all NAV2 navcores 9.xxx/10.xxx as well as all NAV3 navcores 10.xxx/12.xxx caries format 810 - means they can operate with all modern maps (actually we have 3 formats now - 730, 770, 810 - accordingly to colours, see here -

Link URL:

Only the registered members can see the Link URLs. Please Login OR Register.

).
It means, if navcore carries 810 format, it can operate with all maps of all formats up to 810 - including 730, 770. Carminat navcores (8.8xx) caries only up to 770 - means also can operate with 730 maps. Finally all "weak" navcores - mostly 7.xxx - can carry only 730, and won't see any highest formats.

How to know, which particular format has concrete map? Simple! Just open file mapinfo.dat with any Hex-Editor, and read offsets 7 and 6 (yes, in reverse order!) - you'll see combinations:
02DA = 730
0302 = 770
032A = 810

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

I wasn't talking about official solutions. I meant alternative solutions in which "patching" means hacking, cracking, whatever. I wasn't talking about any particular TT device or generation either, just assuming there is a TT device with sufficient hardware, why couldn't it be possible to run a "patched" version of Navcore on it in order to use a map copied from a smartphone?

At the end of the day, a smartphone or a TT device is just a small computer running Linux (Navcore). A Nav2 device may run a patched Navcore from a Nav4 device which, in turn, can operate on GO-app's map, assuming one has all the keys to activate the map on that Nav2 device. So why did you say it was impossible? Lack of knowledge or major incompatibility?

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Answered earlier, but seems you are not linked to read...

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Go ahead, do your best. If you'll be lucky - let's us know.

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

The last one. But you can make your personal investigation, and maybe - you'll learn something, that Guru of TT couldn't find from 2007 year. Good luck!

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Totally wrong, these are versions of TT devices...

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Allso wrong, these are the generations of navcores

Peter

But a discussion about impossible things is pretty pointless ...
You can't use a NAV3/4-NC on a NAV2 device and you can't use a NAV4-map not even with known meta-Code on a NAV2-device. And certainly not a Go-app map. Only NAV3-maps with known code are possible. These things are a fact, no speculation.

By the way: There was nothing to "crack" in the Go-app maps (these always for free), "only" the usage restriction in the Go-app had to be canceled out.