Hi, I recently had the chance to copy the G2 chart (010-C073-00 Southeast Caribbean VUS030R) currently being used in a Garmin 720 chart plotter. I copied the whole SD card into my computer. In it there are two (all uppercase) directories: one is called GARMIN and the other is EULA (this last one seems to be empty). In the Garmin directory are the following files:

GarminDevice.xml
GMAPSUPP.GMA
gmapsupp.img
GMAPSUPP.UNL
gupdate.gcd

I am now trying to make the G2 chart work in a Garmin 440S chart plotter from a friend. I have tried to use several of the map unlocking utilities found throughout this forum. So far I tried with "Fast IMG Unlocker v.1.2", and also "Unlock Garmin Maps V3". In both cases I followed the instructions and the process seems to complete without any problems, and the unlocked map is generated without any errors or warnings from the application. The resulting .img file seems to be identical in both cases, so I assume the unlocking process in the end was the same.

So far I tried to run the unlocked map by just creating a "GARMIN" directory in the new SD card, I also tried adding the remaining files that where also included in the original SD, and the empty "EULA" directory. But when I turn on the 440S there is the usual routine of "Loading Maps" but after that none of the G2 features seem to be present in the unit. Furthermore as a secondary test, I loaded the unlocked map file onto a separate micro SD card and placed it into a "GARMIN directory by itself and tested it on my Nuvi 255. Once the Nuvi boots up, I can now see "Fishing Contour" lines over open sea areas. These green lines where not there before, and as I understand are one of the features of the G2 chart.

So it seems the map is indeed unlocked, but somehow the 440S unit is failing to recognize it. I'm new to map unlocking, so if anyone could please give me some pointers of what I might be doing wrong, it would be much appreciated. BTW I just copied the original .img file (locked map) to the SD and plan to test it and see if the 440S complains in any way that the map is locked, so I would know it is actually reading the SD card at boot-up.