Map Corrupted in device

Hi,

I have OSM and a couple of other maps which I have installed on Nuvi 2455. I obtained a new Nuvi 2557. While I am able to install OSM on to the new Nuvi, I am not able to do the same for the other maps. After mapinstall transfers the map to the device, on turning on the device, I get this error saying map cannot be unlocked and it is corrupted. But when I connect the Nuvi MAC, basecamp can read that map eaily from the device. Same happens with a third party purchased maps on SD card. While device says map cannot be unlocked the map is read by base camp.

How can this be resolved? Has anyone faced similar issues?
  • Would help to know what 'other' maps you're talking about?

    Note Basecamp can often read maps that may be locked on the device, and can read maps off a sd card, so what you're describing isn't unusual.
  • Thanks for the response.

    The third party maps in question are Map-My-India maps. The one is SD card is provided by the vendor along with the unlock code which is present in the SD card. Agreed that Basecemp can read locked maps from SD card, but since the SD card also contains the unlock code along with the map, I was wondering why the device was not reading the same (It actually says cannot read unlocked maps and maps are corrupted)

    The second set of maps where again the device the fails to read, is a much older of the version of the same maps. I was able to install them on my 2455 with the same procedure. I compiled the older version of the map for Basecamp; then used the "transfer to device" feature and sent maps along with waypoints. So Basecamp calls Mapinstall and recompiles the IMG file for the device and transfers the same to the device. This works perfectly well for Nuvi 2455. But the same procedure fails on the new device (2557) which I just unboxed yesterday. Hence the confusion if there was any change to how IMG files are interpreted between the two products. (I tried the SD card on the older device 2455 and it works perfectly with that)

    Meanwhile the same procedure works perfectly well without any hitch for OSM maps. I compiled the route able OSM maps for India from OSM site for MAC Basecamp. I then installed the same on Basecamp and transferred the map to the device. No issues there. And they get read and rendered by the device correctly. Hence was wondering what is difference between the two maps that is causing one to fail, while the other works.
  • I'm not aware of the maps you mention, but Garmin have been introducing ways to prevent pirated maps from being used on their devices, it's possible therefore that your current nuvi is objecting to these maps due to that, even though they may be perfectly valid maps. It's not something though that can be resolved through this forum so you will need to contact Garmin Product Support.
  • Hi,

    They are not pirated maps. I purchased them legally from the vendor. And they are license locked in the SD card. This card reads in 2455 but not in 2557. That is what I was trying to resolve These maps I was trying to compile for basecamp in Mac/PC by gmaptool/mapset toolkits.

    The next step I was going to proceed with was call up Mapmyindia vendor and check the problem. OSM maps are open source maps and not pirated either.
  • I wasn't saying they were pirated, just that the changes made by Garmin to help prevent the use of pirated maps may be causing these to fail also. Will be interesting to hear what the Mapmyindia vendor says.
  • I will try to contact them tomorrow. I just hope they still support Garmin. The issue is: (In my opinion) they are still the best map content guys for India. If they dont support Garmin any more, then it would be a problem. Though I see Open Street Maps are also quite capable. Their coverage over this region is quite good (I just had the 2016 version installed). However, I would still prefer paid content. Need to check the coverage of Garmin maps too. Have not been looking at them as they came in late to market and initially had a lot to catch up to.

    (Sorry for the off topic discussion).
  • Just got a response from the vendor. They have stopped supporting Garmin devices. So that is the issue looks like.
  • I've moved your last post and opened a new thread, and since this issue is resolved I'll close this thread.