Maps for SsangYong Tivoli 2018 (X100 / X103)

Hi canderson, Willy875. Thank you for your support. I was looking for the latest (as here specified 1140 version of the x100 European maps), but unfortunately there are no x100 maps available on the official SsangYong site (see image attached). I have tried on Google, but I was not lucky enough to find the maps on any site. Could you provide me assistance in order to download the latest version?

1789505013390.png


Appreciate your support in advance.
 
Unless I'm mistaken, TomTom maps are now encoded to work only on a specific GPS model.
If you say it's possible to install a recent version on this model, then why not?
Absolutely different by model. Different builds for different devices.

But they were giving away maps for the SsangYong, so there was no need to go through the exercise of serializing them for individual in-dash systems.
 
Hi canderson, Willy875. Thank you for your support. I was looking for the latest (as here specified 1140 version of the x100 European maps), but unfortunately there are no x100 maps available on the official SsangYong site (see image attached). I have tried on Google, but I was not lucky enough to find the maps on any site. Could you provide me assistance in order to download the latest version?

.....

Appreciate your support in advance.
We don't have access to them here. Since SsanYong has shut down support, and because I think these maps have no special serial number key, meaning a map would work on any similar SsanYong car, what you'll want to try is to get another user with one of the more recent maps for your vehicle to 'drop box' one to you.
 
We don't have access to them here. Since SsanYong has shut down support, and because I think these maps have no special serial number key, meaning a map would work on any similar SsanYong car, what you'll want to try is to get another user with one of the more recent maps for your vehicle to 'drop box' one to you.
The latest released maps are version 1140 for the x100 and version 1130 for the x103. The cars share part of the DeviceID, so there is no unique activation for each car, but only for groups
 
It would be interesting to have feedback on the possibility of copying a map installed on one GPS to another GPS.
The matter is a bit more complex: a RSA private key is used to sign the .dct file, which contains the salt and the x100/x103 device ID (which is not the one displayed on the screen). If the signature or the device ID differs, nothing will work.
 
The matter is a bit more complex: a RSA private key is used to sign the .dct file, which contains the salt and the x100/x103 device ID (which is not the one displayed on the screen). If the signature or the device ID differs, nothing will work.
Could you please share the maps with me? It would help me a lot
 
The matter is a bit more complex: a RSA private key is used to sign the .dct file, which contains the salt and the x100/x103 device ID (which is not the one displayed on the screen). If the signature or the device ID differs, nothing will work.
Interesting. We have been under the impression from owners that these maps were being downloaded without respect to any device serial number. From what you are saying, even though the maps were free and without subscription, the same process was involved here as was true for the standalone TomTom devices of that generation.
 
nteresting. We have been under the impression from owners that these maps were being downloaded without respect to any device serial number. From what you are saying, even though the maps were free and without subscription, the same process was involved here as was true for the standalone TomTom devices of that generation.
As long as the `meta.dct` and `meta` files are present in the map datas, the procedure is always the same. The map's `deviceid` is derived from the GUID obtained from the car radio's firmware and is shared across specific groups—such as X100, X103, C220, etc. Therefore, a map signed for the X100 group will work on all X100 units, and so on.
 
As long as the `meta.dct` and `meta` files are present in the map datas, the procedure is always the same. The map's `deviceid` is derived from the GUID obtained from the car radio's firmware and is shared across specific groups—such as X100, X103, C220, etc. Therefore, a map signed for the X100 group will work on all X100 units, and so on.
Ah, OK. That makes sense and is closer to where I thought we were. I think you're saying that there's a unique key for each device model (e.g., X100, X103, etc.). That would prevent attempting to actually use botched downloads for the wrong model.

Back in the day, the standalone devices also used *.dct files, but a unique key was generated for every individual device serial number, not just specific model families.
 
Ah, OK. That makes sense and is closer to where I thought we were. I think you're saying that there's a unique key for each device model (e.g., X100, X103, etc.). That would prevent attempting to actually use botched downloads for the wrong model.

Back in the day, the standalone devices also used *.dct files, but a unique key was generated for every individual device serial number, not just specific model families.
As I’ve already told you, the device ID used for the maps is different from the car radio's serial number; however, the same values are always used to generate a unique device ID for each group (X100, X103, C220, etc.). Consequently, all firmware versions ending in X100 will share the same ID used for the maps.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Latest resources

Forum statistics

Threads
30,388
Messages
209,493
Members
70,059
Latest member
Oleksandr111

Latest Threads

Back
Top