Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 40

Hybrid View

  1. #1
    Member
    Join Date
    Jul 2025
    Location
    UK
    Posts
    18
    Rep Power
    0

    Default

    Yes I'm very happy with the outcome, thanks GN for resolving it.

    I initially suspected something like a corrupted file or a problem with the flash memory.

    I tried a few things before asking such as reinstalling maps several times and changing the map region to somewhere else and back again in case that fixed it. Then when I found out to how to turn mass storage mode on I twiddled with a few files to see if the error messages changed.

    After being burnt a few times I'm very careful trying to work out what I can mess around with without breaking things. Then if I do break things how hard it is to unbreak them. Copying files back easy, reflashing in boot modes slightly harder, soldering to test points on the PCB and using custom hardware to reflash trickier. Removing a chip, reflashing then replacing it is something I try to avoid thanks to my eyesight not being what it once was.

    Within the limitations of the forum rules I'm curious as to what precisely went wrong and how it was fixed.

    I gather the Garmin server is sending back a bad unl file for certain models. Is that a recent thing and if not why did it work fine until a few days ago?

    I can fill in some of the blanks as to one way GN might have diagnosed the problem using the GarminDevice.xml file.

    The one question I'd really like to know the answer to (and which may not be answerable here) is what the fix was and how it worked. It certainly did something interesting.

  2.    Advertissements


  3. #2
    VIP Master Nuvi 58LMT "can't unlock maps".
    Nuvi 58LMT "can't unlock maps".Nuvi 58LMT "can't unlock maps".Nuvi 58LMT "can't unlock maps".
    Garman_Nuvi's Avatar
    Join Date
    Apr 2015
    Location
    On the move
    Posts
    259
    Rep Power
    1219

    Default

    Quote Originally Posted by stevex View Post
    Within the limitations of the forum rules I'm curious as to what precisely went wrong and how it was fixed.
    I gather the Garmin server is sending back a bad unl file for certain models. Is that a recent thing and if not why did it work fine until a few days ago?
    I can fill in some of the blanks as to one way GN might have diagnosed the problem using the GarminDevice.xml file.
    The one question I'd really like to know the answer to (and which may not be answerable here) is what the fix was and how it worked. It certainly did something interesting.
    Neil is right.
    Once I had your garmindevice.xml I could have a play around to see if the unlock codes where valid, they where but Garmin's server did not pick up the Family ID to create the code for the 2 regional maps UK & ROI and Southern Europe. I check the error was repeated on a couple of other Traveler devices I have to prove it was not your specific device. All the other maps available received their correct unlock codes base on their FID as they were present.

    I've not actually fixed the problem only Garmin can do that, all I did was identify and choose another download option I had checked would work for you , giving you Full Europe which includes coverage of UK & ROI.
    It's quite possible that the working .unl & .gma files could be used to unlock UK & ROI as they share the Family ID, but why bother "if it ain't broke don't fix it"
    Spoiler: Family ID
    Ht2dwyy
    Last edited by Garman_Nuvi; 17th July 2025 at 05:35 AM.

 

 

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
  •