Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 62
  1. #11
    Member +
    Join Date
    Apr 2010
    Location
    earth
    Posts
    38
    Rep Power
    17

    Default

    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <List xmlns="http://www.garmin.com/xmlschemas/UnlockCodes/v1">
    <Unlock>
    <Code>0000000000000000000000000</Code>
    <Description>TOPO Espa񡠶6 PRO</Description>
    </Unlock>
    <Unlock>
    <Code>0000000000000000000000000</Code>
    <Description>TOPO Espa񡠶6 PRO</Description>
    </Unlock>
    </List>

  2.    Advertissements


  3. #12
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    374
    Rep Power
    251

    Default

    Quote Originally Posted by osiris4isis
    What do you mean "file is not lockable?"
    "lockable" is the word used by Garmin (look at BaseCamp for example).
    According to Garmin, a file is lockable when the map levels section is encrypted (and other bytes in TRE subfiles are changed).
    When a file is lockable the flag at TRE+0x0D is set: this flag just indicates that the file is lockable. Of course, if you change the flag, the file remains lockable...
    The original file wasn't locked? I can lock it (at any time) if I put in encrypted map levels and set flag, right?
    ????? I don't understand how you lock a file... it is not easy. You must use a 32 bits key and the correct algorithm

  4. #13
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    374
    Rep Power
    251

    Default

    @ Cnfhbr
    Are you sure that TRE9 section only exists in lockable files?

  5. #14
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    Quote Originally Posted by sherco40 View Post
    "lockable" is the word used by Garmin (look at BaseCamp for example).
    According to Garmin, a file is lockable when the map levels section is encrypted (and other bytes in TRE subfiles are changed).
    When a file is lockable the flag at TRE+0x0D is set: this flag just indicates that the file is lockable. Of course, if you change the flag, the file remains lockable...
    ????? I don't understand how you lock a file... it is not easy. You must use a 32 bits key and the correct algorithm
    Since I don't use Basecamp that often, I'm not going to debate what term they use. If one go by english meaning, the word lockable is formed from two words: lock able, which mean able to be locked. This is why I was confused by the use of the quote "not lockable" I mean how can the original file not lockable. The creator of it should have the ability to lock it.
    I'm not saying that I (or anyone) could locked the file. I'm saying Garmin (or whoever) created that file should be able to locked it.
    Anyway, I understand what you mean now.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  6. #15
    Navigation software expert

    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,228
    Rep Power
    476

    Default

    Quote Originally Posted by sherco40 View Post
    @ Cnfhbr
    Are you sure that TRE9 section only exists in lockable files?
    See any official map, compiled using the community-generated OSM database (Garmin does not lock such maps).

    For example:

    Non-locked map
    [Only registered and activated users can see links. ]

    Unlocked map
    [Only registered and activated users can see links. ]


    In addition, I can create test files for you (non-locked.img, locked.img and unlocked.img) using MPC, if you want.
    Last edited by Cnfhbr; 4th September 2016 at 13:16. Reason: added screenshots

  7. #16
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    374
    Rep Power
    251

    Default

    If one go by english meaning, the word lockable is formed from two words: lock able, which mean able to be locked
    Yes and this is why the word used by Garmin ("not lockable") is correct.
    A lockable file or map may be "locked" or "unlocked": if a lockable file has an unlock code , the map is "unlocked" but if the file does not have an unlock code, the map is "locked".
    A "not lockable" file cannot be locked.

  8. #17
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    I see. So the file posted in this thread is not lockable, therefore it doesn't need to be unlocked, right? And files with MSV or GMA, can be not lockable as well?
    Last edited by osiris4isis; 4th September 2016 at 09:15.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  9. #18
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    374
    Rep Power
    251

    Default

    Yes, the file in this thread is "not lockable"
    But the file is signed and the signature does not match the file, this is why the file does not work in a unit with MSV (Map Signature Verification) and this is why I think it has been modified.
    (A GMA file is just a certificate that assures that the unlock code has been normally given by Garmin)

  10. #19
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    639

    Default

    Are there any files that has both* MSV and GMA; or is it always one or the other?

    * because the file originally has MSV and when GMA was created later, it just gets added and the MSV wasn't removed.
    "You know the very powerful and the very stupid have one thing in common. They don't alter their views to fit the facts. They alter the facts to fit the views." -DrWho

    Do NOT PM me with requests or for fixes to your problem. Post in thread instead. All communications in English only!

  11. #20
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    374
    Rep Power
    251

    Default

    MSV and GMA are 2 different things that do not interfer.
    GMA (Garmin Map Authentication or Genuine Map Authentication, I don't remember...)has been introduced by Garmin for the map with a FID > 2200: for these maps, if the map is lockable, the map needs an unlock code to be unlocked and this unlock code must be authenticate by a .gma file
    MSV is another procedure: recent maps are signed (they embed some checksum made with the bytes of the file) and if they are used in an unit with MSV, the unit will verify the signature: it will calculate that checksum and compare it with the signature , if it doesn't match, the file will not be displayed.

    For the map of this thread: the map is not lockable so no need of unlock code and so no need of gma file.

 

 
Page 2 of 7 FirstFirst 1234 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.