Results 1 to 10 of 19
-
16th July 2014, 09:30 PM #1
How to clone LIVE services
Cloning/copying paid for/subscribed Live Services from one x40 or x50 Live device (with a valid subscription) to another x40 or x50 Live device (without a valid subscription)
After doing a FULL WINDOWS back-up:-
1. Patch the current navcore (using whichever tool you prefer) for the non-subscribed device.
2. Create/add a new serialnumber.txt file to the root with the DeviceSerialNumber from your ttgo.bif file (like "W12345K12345") taken from the device which does have a current subscription.
3. Create/add a new simid.txt file to the root with the ICCID number from your SIMCARD/mobility.sim file (like "89312300004560000789") also taken from the device which does have a current subscription.
4. Insert the SD card or restart your device and let it reboot. You will get the expected "cannot use this map" message; now switch off.
5. Re-patch the map(s) with the latest FastActivate or other tool and restart your device.
6. Then just go into the "MyTomTom account" screen and input your valid username & password!
This should/could be tweaked/modified for other Live devices too so please let us know how you get on.
--------------------------------------------------------------------------------------------------------------------------------------
Step by step tutorial on cloning the TT LIVE services on an x10/20/30 device, BT capable:
Start with your real device:
enter a go 740 SN to file serialnumber.txt; it starts with WL**********, total 12 chars.
enter an European ICCID in file simid.txt; e.g. 8931440************, total 19 digits; apply Luhn's checksum to the leftmost 18 digits, and the 19th digit at the right is the checksum; may not matter, just have the 7 digit prefix reproduced.
enter string GO 740 LIVE in file usbname.txt
enter string TomTom GO 740 LIVE in file motd.txt
enter an IMEI in file imei.txt; e.g. 354226*********, total 15 digits, Luhn checksum over the leftmost 14 digits, and the 15th is the checksum.
Note that the details MAY HAVE TO BE from a real go 740 device...
install NC v9.510 with dsa-21July2014 to device; select MB, all go modes in the mode table (with Ctrl/click), mode 24 last.
start the device; it will not recognize the maps because of the new SN; so reconnect it to PC, and use the new device ID from file ttgo.bif to patch the maps.
restart the device
Set a BT/DUN connection up:
if using BlueDUN on a smartphone or tablet, add the smartphone/tablet to device, done
if using a real DUN capable phone with a real data provider, switch, with the Skin Chooser, to mode 25; there add the phone and configure its wireless data, manually if necessary; then switch back to mode 24.
Let the device connect to the network via BT/DUN, in mode 24; check the Network status, should be Connected; now connect the device to PC
Make a device full backup to an USB memory stick or SD card, formatted entirely (no partitions) and labeled TOMTOM.
From now on, use always this storage in relation with TTome!
Check the contents of file ttgo.bif (on the storage):
your new SN should appear on line DeviceSerialumber=
your usbname.txt contents should be on line DeviceVersionHW=
your motd.txt contents should be on line DeviceName=
File SIMCARD/mobility.txt should contain the rest of details: ICCID, IMEI, and three others.
Now you are ready to associate the cloned device with your TT account, via TTHome:
connect storage (not the device, its storage backup) to PC; start TTHome: it should show a TomTom GO 740 LIVE device written in the right/lower corner of the TTHome window.
log into TTHome with your TT account (create a new account); here you will be invited to associate the cloned go 740 device to your TT account (could be the 3rd option, if you had the real device previously associated to the existing TT account). You may as well create a new TT account for this clone.
Great, now is the hard part: go to the TT website and buy a new TT LIVE 12 month Europe subscription, it is EUR 49.95 at an EU site (more at UK, Switzerland, etc).
Return to TTHome, do Operate my GO against the cloned storage (I repeat, you never connect the real device to TTHome, you just synchronize it with the goodies downloaded with TTHome to the storage(SD, USB stick)):
execute Change preferences/ My TomTom account(it's in screen 7/7) and enter your username (email address actually) and password to the clone.
From now on, you will have TT LIVE services working on your clone.
(play with them on Operate my GO)
End Operate my GO, exit TTHome, synchronize the cloned storage to your real device.
From now on, you will have TT LIVE services on your TT device, which masquerades as a GO 740, while in reality being a go x10/20/30 emulating mode 24.
All credit to DSA and his helpers for thisbiggerdave Reviewed by biggerdave on . How to clone LIVE services Cloning/copying paid for/subscribed Live Services from one x40 or x50 Live device (with a valid subscription) to another x40 or x50 Live device (without a valid subscription) After doing a FULL WINDOWS back-up:- 1. Patch the current navcore (using whichever tool you prefer) for the non-subscribed device. 2. Create/add a new serialnumber.txt file to the root with the DeviceSerialNumber from your ttgo.bif file (like "W12345K12345") taken from the device which does have a current Rating: 5
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 9 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
-
18th July 2014, 03:40 AM #2
Can I copy LIVE services from x50 to x40 or it camn be done only between the same models?
Can I use modified Truck navcore (DSA version)?
-
18th July 2014, 01:51 PM #3
It works across from one to another. I did it from my subscribed 550 to an unsubscribed 940
I reckon it should work on the truck navcores BUT remember the latest 9.702 doesn't show traffic bar etc on the x40/x50's anyway so you'd need to stay with the previous 9.701 navcore. give it a try & let us know here. I don't know if all DSA versions can read the new serialnumber.txt file & simid.txt file or only the new 19July2014 or later versions.
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 1 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
felis69 (6th March 2021)
-
18th July 2014, 10:32 PM #4
Couple of questions if I may 😉
1/ Will it work between v10 and above and older ones? For example New go 5000 and 550 live units.
2/ Will tt server accept 2 or more units at same time? Fe I share my unit details (not login/pass) with someone and there will be "2 identical SIM's" potentially logged in.
Reason I'm asking is my 550 isn't capable to receive live services in Poland so maybe this way I can use it instead of spending money for newer unit. Thanks.
-
18th July 2014, 10:41 PM #5
1) I can't see it would work "cross navcore" (from v10 to v9 etc) BUT maybe try it although I don't think that will work?
2) I logged into TTHome with both my genuine 550 & my cloned 940 and got no error messages etc so should be OK.
I also had both running side-by-side at the same time and both connected to Live services simultaneously so, again, no problem there either
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 2 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
-
18th July 2014, 11:18 PM #6
Ok thanks Dave.
Is there anyone with a new uncrackable device and valid live subscription (not smartphone) willing to share their device id and SIM number (as stated in post 1) with me? For testing and if successful for personal use only. Just PM me ☺ Thanks.
-
19th July 2014, 12:04 AM #7
From the man himself:-
(1) No, you cannot port a new device subscription to an old device, because there will be a protocol mismatch between the old client and the server acting as a server for a new device (based on the subscription (new) serial number).
(2) Yes, read the forum experiments starting with page 361.
But since you have a GO 550, you may buy a new subscription for your device. But, you would have to use the device in the BT/DUN mode, so that the connection to the TT servers will happen (with the internal GPRS, that connection won't work).
And now, I would be very curious to find out if you get LIVE traffic from the TT servers - which actually cover the traffic in Poland, but for new devices capable of the smartphone connected mode!
Of course, do not spend your money on new subscriptions just for experiments.
-dsa
Portability issues
In principle, it is possible matching clients with servers of different versions, but another go between, network proxy, would be needed.
We lack sufficient data for such exploit (it presupposes sniffing the traffic between client and server, for each of the versions we would want to match).
So, let's forget about it...
-dsa
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 2 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
-
19th July 2014, 02:52 PM #8
Also from the man himself (for someone here to help with please?):-
You could do a test to confirm that the BT/DUN connection works well:
* use any of your devices, the original or/and the clone; reinstall the NC with dsa-20July to make sure that folder ppp exists.
* install on an Android tablet or/and smartphone the BlueDUN trial app, and start it - from the moment a DUN connection is accepted, it will work for 5 minutes, more than enough, then it has to be restarted; make sure that the tablet/smartphone is connected to the internet via WI-FI only.
* use Toggle GPRS to switch to BT/DUN (from initially GPRS); tell if LIVE services work, get Connected.
* going back to GPRS requires two more clicks on Toggle GPRS (first moves to No Network, then the second to the GPRS mode)
I will have an interesting conclusion confirmed, if you are successful with the BT/DUN tests.
------------------------
I forgot to mention that you have to add the tablet/smartphone running BlueDUN as a new "phone" to the TT device, in any mode, just as a hands-free. In other words, the tablet/smartphone address has to get into file settings.dat, otherwise I do not select it when raising the networking.
If you also have another, main phone, as hands-free, you would want to stop its Bluetooth, so to make sure that connection gets faster to the intended BlueDUN device (presumably listed after the main phone, in file settings.dat).
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
20th July 2014, 02:16 AM #9
Had a lot of reading ... Installed latest dsa on my 550 live to check smartphone connection but so far failed ... Can't pair my phone in DUN mode - probably because it is HTC one ... Then can't change skin under dsa ... Is there any way to check what mode is unit currently in: gprs/dun/no network? Will try during coming week.
-
20th July 2014, 01:10 PM #10
Hopefully you've seen his reply on the original forum & that helps?
Good points made in a peer forum, let's answer them:
DUN for a smartphone - install and run the trial (free) version of the BlueDUN app. You may simply add the phone in any mode, even in the current Slf(self) - 37 - mode, if it's not already added to your TT device.
Skin Chooser, to be used for skin changes; don't miss a one time touchscreen setup, with a pen (but to repeat it, properly, remove file skins/etc/pointercal from device); and, at installation time of the NC with dsa, do not make any selection in the mode table, just MB; any number of times, the dsa installation could be repeated, until it's right for you.
Network mode - that's tricky indeed: look at Status & information/Version information/Network, after a device wake-up. If it's only the fake Model: 00.00.00, and the Conecting... status, then it's No Network. If Model is not fake, (IMEI and SIM ID are always real for a real x40/50 device), and upon getting into status Connected, MCC/MNC is also not fake (not equal with 22222-only), then it's the real GPRS mode. Conversely, if Model and MCC/MNC remain fake when status gets Connected, then it's the BT/DUN mode.
Sometimes, Model (and MCC/MNC) remain inherited from the previous mode, but if you stop and wake-up the device, then their content is reset, and the above rules apply.
Don't forget, in principle there are three network modes, and the Toggle GPRS button cycles between them, with modes preserved across device restarts. Unless it's an unfixed bug, because I couldn't test it myself for lack of a real x40/50 device.
Reading the dsa Help, section how to clone a device, useful.
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
The Following 3 Users Say Thank You to biggerdave For This Useful Post:
- [ Click To Expand ]
-
UM - Trucker POI Professional...
hello could someone share the ttokg - Trucker...