How to clone LIVE services

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.

------------------------

[Login or Register to remove this advertisement]

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).

biggerdave Reviewed by biggerdave on 19th July 2014. 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

Quote:

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

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.