terrytpot
24th November 2008, 01:38
Navcore 8 Tutorial
Lets begin by explaining what’s required to install cracked or patched maps.
All maps must have a .dct file which is in effect a validation key giving you permission to use the map. This file is used by several sources and if its not correctly applied will result in failure in any of several ways.
Before you can use a map you will require software capable of using the map which is either the " navcore " installed on your device or the "tomtom home" software on your PC.
There are various navcores available with 8.412 being the newest (before that it was 8.410,8.320,8.310,8.302,8.301,8.300 8.204,8.203,8.201,8.051,8.016,8.011,8.010,8.002,7. 481 etc) as of March 2009 (theres also 8.070 for trucks)
Navcores can be either "official" from tomtom or "patched/cracked" from other sources e.g. SE8.010 by TTuser or use yDG’s tool for patching official navcores for the device they were originally intended for.
Unfortunately (at least as far as v8 navcores are concerned) these navcores will not recognise maps that have .dct files created using keygens and as such you will need to install an unofficial navcore or patch it for the .dct file to be recognised.
To complicate matters further home will need patching as well or it wont recognise keygen'd .dct's properly and will prevent you using features such as "Operate my tomtom" and this can cause issues with updating the map.To do this a new patched .dll file is required which you can either download or create yourself using yDG's patch tool.
So to sum up for now you need to do the following:-
1 ) Make a FULL copy of your tt and put it somewhere safe. If you get any problems you can always restore it and you're working again.
2) Download a new navcore and easyusertools
Use this post for the latest official navcores kindly shared by BiggerDave [Only registered and activated users can see links]
or use the following for access to non-standard navcores:
Each of these links contains a "basicpack" for installing to any device and also device specific "SEttsystem" files dependent on which device type you have.
You need one of each, so for an x10 you want "basic" and "for gox10",for any other type of device you want "basic" and "for all devices except gox10".
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.002.9117
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.010.9369 also includes 8.011.9373
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.016.9380
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.051.9404
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=339472 ([Only registered and activated users can see links]) Navcore 8.070.9589 (TRUCK)
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.201.9497
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.203.9717 also includes 8.204.9718
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.300.9732
[Only registered and activated users can see links] ([Only registered and activated users can see links] Navcore)t=332713 ([Only registered and activated users can see links] Navcore) Navcore 8.301.9736
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=339436 ([Only registered and activated users can see links]) Navcore 8.302.9378
[Only registered and activated users can see links] Navcore 8.310.9760
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=340459 ([Only registered and activated users can see links]) Navcore 8.410.1218
[Only registered and activated users can see links] Navcore 8.412.1236
For only the ttsystem files for all SE navcores by BiggerDave (which is the bit called either for x10 or all devices except x10) go here: [URL][Only registered and activated users can see links]
yDGpatch_1-2-16-14 for yDG’s new patching tool
Latest Easyusetools [URL][Only registered and activated users can see links]
Which looks like this when you start it up:
[Only registered and activated users can see links]
3)dl a new map
[Only registered and activated users can see links] 825 maps
[Only registered and activated users can see links] 815 maps
[Only registered and activated users can see links] pre810 maps
[Only registered and activated users can see links] v6 maps
4)dl a new .dll for home
If you want any of the v8 dll's see this from yDG
[Only registered and activated users can see links]
At this point as I prefer to format (see 5) I cut and paste all the folders I will require after updating to my desktop eg:
art,ASR,contacts,helpme,LoquendoTTS,mp3,photos,ras ter,schemes,sounds, text,voices,zip and any media players.
Heres some media player links
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) by retkris
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) by fox50,and there are some films allready converted for it here
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank)
When the update is done simply paste them back onto the tomtom You can ,of course , just format and then take copies of the folders from the Full copy at step 1 )
(if you try nav 8.2 onwards you'll need a new ASR folder from TTuser)
5) If you have an official v8 navcore on your device skip this step and go to step 6) This is where the fun starts, I find it best to format my tt and install from scratch to avoid any prior issues complicating events.
copy the new navcore on to your tt like this:
[Only registered and activated users can see links]
Making sure that its not still all in one folder. Then add the extras you require from your copy at 1) or 4) if you saved them to desktop
6) If you have a device allready using a V8 navcore updated officially by tthome then you don’t need TTusers basic pack, just overwrite your existing files on your tt with the patched "ttsystem" file that matches the navcore that’s installed on your device or use yDG’s tool to patch it to retain full functionality of the navcore..
7)add the new map to tt or sd card
8 )use the easyusetools to crack the map. ( My personal recommendation is to use runmefordct as runmeforallautomatic tries to patch home and the navcore as well which it cant do)
9)add a patched .dll file to the correct place on your pc to patch home or use yDG’s tool to patch it yourself…
[Only registered and activated users can see links]
by yDG
EASYUSETOOLS by TTuser.
here’s a quick explanation of eutools contents which look like this:
[Only registered and activated users can see links]
1 )insert meta folder..
in here place a copy of the map.pna and map.meta , for tomtom speedcams you need two files for eachcountry:
"country_TomTom.ov2" and "country_TomTomOv2.ver"
(you only need to do this if cracking a map on pc before adding it to your tt or sd , if cracking on the device itself just add the camera files to the map first)
2)progs folder..In here are all the tools that do the job of cracking stuff.
[Only registered and activated users can see links]
In the meta text file you need to have the name of the map version you want to crack along with a load of gibberish which is the blowfish code followed by the exact name and version of the map and looks like this:
[Only registered and activated users can see links]
(make sure you dl the latest version of easyusetools to get up to date meta's for new maps or your runmetools will give errors when trying to crack newer maps)
3)ttsystem folder..no need to use this or runmeforall if you are using a v8 navcore as they can't be patched.
4)Device id file..type and save your device id in upper case with no spaces eg AKYWEYTRED If you already have a ttgo.bif file on the device being cracked and its connected to the computer whilst doing so the tools can use the device id from the bif itself like this:
[Only registered and activated users can see links]
5)Runmeforall.. used if tt is connected to pc and will add the new dct file/files in the map on your tt.(if using an older navcore than v8 will also patch your navcore and tthome) ok for old navcores but quite slow and wont patch nav if v8 required. It wont use the file "device id" for cracking but will get the info required from the ttgo.bif file on your device ,so if you haven't got a .bif on your tt you can create one using the version.txt file included in the swichfiles zip that’s in the ttsystem download.
6)Runmefordct.. creates the .dct for your map and cameras and places it in the "insert meta" folder or on your tt depending on where the map is that you want to crack. If all is done correctly the result will look something like this:
[Only registered and activated users can see links]
7)Runmefor meta.. Only used to create a map.meta file for a genuine purchased map. You don't need it for cracked maps so as 3) leave it alone.
Here's a bit more about cameras if you're still not sure what’s what...
There are 2 popular ways of adding camera alerts to your tomtom ,you can....
1 ) use the tomtom camera alerts,full details on installation to be found here:
[Only registered and activated users can see links] ([Only registered and activated users can see links])
2) use POI camera alerts,full details on installation to be found here:
[Only registered and activated users can see links]
Lets begin by explaining what’s required to install cracked or patched maps.
All maps must have a .dct file which is in effect a validation key giving you permission to use the map. This file is used by several sources and if its not correctly applied will result in failure in any of several ways.
Before you can use a map you will require software capable of using the map which is either the " navcore " installed on your device or the "tomtom home" software on your PC.
There are various navcores available with 8.412 being the newest (before that it was 8.410,8.320,8.310,8.302,8.301,8.300 8.204,8.203,8.201,8.051,8.016,8.011,8.010,8.002,7. 481 etc) as of March 2009 (theres also 8.070 for trucks)
Navcores can be either "official" from tomtom or "patched/cracked" from other sources e.g. SE8.010 by TTuser or use yDG’s tool for patching official navcores for the device they were originally intended for.
Unfortunately (at least as far as v8 navcores are concerned) these navcores will not recognise maps that have .dct files created using keygens and as such you will need to install an unofficial navcore or patch it for the .dct file to be recognised.
To complicate matters further home will need patching as well or it wont recognise keygen'd .dct's properly and will prevent you using features such as "Operate my tomtom" and this can cause issues with updating the map.To do this a new patched .dll file is required which you can either download or create yourself using yDG's patch tool.
So to sum up for now you need to do the following:-
1 ) Make a FULL copy of your tt and put it somewhere safe. If you get any problems you can always restore it and you're working again.
2) Download a new navcore and easyusertools
Use this post for the latest official navcores kindly shared by BiggerDave [Only registered and activated users can see links]
or use the following for access to non-standard navcores:
Each of these links contains a "basicpack" for installing to any device and also device specific "SEttsystem" files dependent on which device type you have.
You need one of each, so for an x10 you want "basic" and "for gox10",for any other type of device you want "basic" and "for all devices except gox10".
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.002.9117
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.010.9369 also includes 8.011.9373
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.016.9380
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.051.9404
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=339472 ([Only registered and activated users can see links]) Navcore 8.070.9589 (TRUCK)
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.201.9497
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.203.9717 also includes 8.204.9718
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) Navcore 8.300.9732
[Only registered and activated users can see links] ([Only registered and activated users can see links] Navcore)t=332713 ([Only registered and activated users can see links] Navcore) Navcore 8.301.9736
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=339436 ([Only registered and activated users can see links]) Navcore 8.302.9378
[Only registered and activated users can see links] Navcore 8.310.9760
[Only registered and activated users can see links] ([Only registered and activated users can see links])t=340459 ([Only registered and activated users can see links]) Navcore 8.410.1218
[Only registered and activated users can see links] Navcore 8.412.1236
For only the ttsystem files for all SE navcores by BiggerDave (which is the bit called either for x10 or all devices except x10) go here: [URL][Only registered and activated users can see links]
yDGpatch_1-2-16-14 for yDG’s new patching tool
Latest Easyusetools [URL][Only registered and activated users can see links]
Which looks like this when you start it up:
[Only registered and activated users can see links]
3)dl a new map
[Only registered and activated users can see links] 825 maps
[Only registered and activated users can see links] 815 maps
[Only registered and activated users can see links] pre810 maps
[Only registered and activated users can see links] v6 maps
4)dl a new .dll for home
If you want any of the v8 dll's see this from yDG
[Only registered and activated users can see links]
At this point as I prefer to format (see 5) I cut and paste all the folders I will require after updating to my desktop eg:
art,ASR,contacts,helpme,LoquendoTTS,mp3,photos,ras ter,schemes,sounds, text,voices,zip and any media players.
Heres some media player links
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) by retkris
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank) by fox50,and there are some films allready converted for it here
[Only registered and activated users can see links] ([Only registered and activated users can see links] / _blank)
When the update is done simply paste them back onto the tomtom You can ,of course , just format and then take copies of the folders from the Full copy at step 1 )
(if you try nav 8.2 onwards you'll need a new ASR folder from TTuser)
5) If you have an official v8 navcore on your device skip this step and go to step 6) This is where the fun starts, I find it best to format my tt and install from scratch to avoid any prior issues complicating events.
copy the new navcore on to your tt like this:
[Only registered and activated users can see links]
Making sure that its not still all in one folder. Then add the extras you require from your copy at 1) or 4) if you saved them to desktop
6) If you have a device allready using a V8 navcore updated officially by tthome then you don’t need TTusers basic pack, just overwrite your existing files on your tt with the patched "ttsystem" file that matches the navcore that’s installed on your device or use yDG’s tool to patch it to retain full functionality of the navcore..
7)add the new map to tt or sd card
8 )use the easyusetools to crack the map. ( My personal recommendation is to use runmefordct as runmeforallautomatic tries to patch home and the navcore as well which it cant do)
9)add a patched .dll file to the correct place on your pc to patch home or use yDG’s tool to patch it yourself…
[Only registered and activated users can see links]
by yDG
EASYUSETOOLS by TTuser.
here’s a quick explanation of eutools contents which look like this:
[Only registered and activated users can see links]
1 )insert meta folder..
in here place a copy of the map.pna and map.meta , for tomtom speedcams you need two files for eachcountry:
"country_TomTom.ov2" and "country_TomTomOv2.ver"
(you only need to do this if cracking a map on pc before adding it to your tt or sd , if cracking on the device itself just add the camera files to the map first)
2)progs folder..In here are all the tools that do the job of cracking stuff.
[Only registered and activated users can see links]
In the meta text file you need to have the name of the map version you want to crack along with a load of gibberish which is the blowfish code followed by the exact name and version of the map and looks like this:
[Only registered and activated users can see links]
(make sure you dl the latest version of easyusetools to get up to date meta's for new maps or your runmetools will give errors when trying to crack newer maps)
3)ttsystem folder..no need to use this or runmeforall if you are using a v8 navcore as they can't be patched.
4)Device id file..type and save your device id in upper case with no spaces eg AKYWEYTRED If you already have a ttgo.bif file on the device being cracked and its connected to the computer whilst doing so the tools can use the device id from the bif itself like this:
[Only registered and activated users can see links]
5)Runmeforall.. used if tt is connected to pc and will add the new dct file/files in the map on your tt.(if using an older navcore than v8 will also patch your navcore and tthome) ok for old navcores but quite slow and wont patch nav if v8 required. It wont use the file "device id" for cracking but will get the info required from the ttgo.bif file on your device ,so if you haven't got a .bif on your tt you can create one using the version.txt file included in the swichfiles zip that’s in the ttsystem download.
6)Runmefordct.. creates the .dct for your map and cameras and places it in the "insert meta" folder or on your tt depending on where the map is that you want to crack. If all is done correctly the result will look something like this:
[Only registered and activated users can see links]
7)Runmefor meta.. Only used to create a map.meta file for a genuine purchased map. You don't need it for cracked maps so as 3) leave it alone.
Here's a bit more about cameras if you're still not sure what’s what...
There are 2 popular ways of adding camera alerts to your tomtom ,you can....
1 ) use the tomtom camera alerts,full details on installation to be found here:
[Only registered and activated users can see links] ([Only registered and activated users can see links])
2) use POI camera alerts,full details on installation to be found here:
[Only registered and activated users can see links]