Results 1 to 10 of 16
27th June 2018, 10:58 PM #1
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?
[Login or Register to remove this advertisement]
vda767 Reviewed by vda767 on . 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
28th June 2018, 02:14 AM #2TomTom Master
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
28th June 2018, 05:07 PM #3
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?
28th June 2018, 11:34 PM #4TomTom Master
Join Date : May 2012Location : At homePosts : 1,810Thanks: 3,043
- 6,881 PostsRep Power : 15Reputation : (3055)
28th June 2018, 11:43 PM #5TomTom Master
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
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 -
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
28th June 2018, 11:44 PM #6TomTom Master
29th June 2018, 06:41 PM #7Join Date : Feb 2012Location : NetherlandsPosts : 449Thanks: 889
- 1,026 PostsRep Power : 15Reputation : (340)
29th June 2018, 11:00 PM #8
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?
30th June 2018, 10:59 PM #9TomTom Master
Go ahead, do your best. If you'll be lucky - let's us know.
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!
1st July 2018, 10:37 AM #10
@rusigor: I started this topic as a discussion, not just a simple Q&A section, and I found the "impossible" was not really a discussion. You explained about maps of GO App and TT device being different formats, that I comprehend, but then I wish to know why it is so hard to achieve that you must say "impossible".
One thing I learned from life is that given enough interest nothing is impossible. Maybe people now have cracked GO App giving them maps for life for free, why anyone bother doing hard work to let people with old Nav2 device use latest map. My answer is lack of interest. A second hand smartphone is quite cheap, just buy one and problem solved - a kind of solution that I personally don't like.
Let take for example, UK map is quite small, it easily fits on even a device with 512MB is internal storage. But TT drop support for devices with no mean of having 4GB memory. For what?!? My common sense dictates that TT wants more money. They want people to throw away their good old devices to by new, a kind of "pay and problem solved". Even if I had money I wouldn't give that greedy TT a cent.
Thank you anyway for hints and directions. I hope one day I'll see GO App ported to TT device but as you said that day may never come.