Thread: Garmin GB Discoverer 1:50K - Full Coverage (2.00)

Hi Ballebar,
Many thanks for the help. I got the PM with the number and have tried it. But again it does not work. One thing I have discovered is that the unlock file is empty after having tried it. I thought I had made a mistake first and not saved it so did it all again. But it seems to be normal that if the unlock code is not valid that it deletes it. I did try checking the number and there was some white space after the number so removed it - but again no luck. I also revisited the sd card using the diagnostics menu. There is a serial number but it is only 5 numbers (62154) and I was under the impression that the instructions on another page here explicitly said this was not the number and it had to be 10 digits. I did try using this 5 digit number in Jetmouse and it did not reject it and generated a number. Unfortunately this code also did not unlock the maps and when I checked afterwards was also missing from the unlock file. I appreciate this is all rather unknown and a bit trial and error, so I am not sure if you have any new ideas? Has anyone actually managed to unlock these maps?

In Jetmouse Keygen 1.5 you need unit id and map id.
Then generate code and put it in unl file.
Do you try this?

Originally Posted by oracle1207

That's exactly what I did - Unit ID ********** with map id 2043 then generate. But the maps are not visible. I have also tried redoing it with no change.

Are you putting ya map and the unl file in the Garmin folder on ya root???

For all those that want a very easy way to get micro sd id here it is

Use a android phone with SD Tools (free from market)

Take the last 8 digits of cid eg... 8c0484f7

Convert to hex here

Code:

Please Login or Register to see the links

makes 1224782416 use the converted number in jetmouse 1.5fix

Open new txt file name anything while the file is open hit "save as"

Name anything.unl then Change save as type to "all files" and hit "save" your see unl file created now delete txt file keep unl

This really works let me know if this helps you be good to know. Good luck !!!!


Report this post Delete post

The CID can be 62154. If UnitID and CID are a 10 digits then people often make the mistake to say that 62154 is only 5 digits. In fact it is "0000062154" in this 10-digit scope.

If you have the correct CID you don't need to fill in the leading zero values in the KG.

I haven't seen any unit that erases the unlock code. All UNL-files should have a multiple of 25 bytes. All characters should be without spaces, line feeds or carriage returns. No extra bytes within the UNL-file. Make sure it's a plain text file without multi-byte unicode.

It’s also always possible to store all applicable unlock codes in the “[X]:\Garmin\gmapsupp.unl” file as a continuous string (25, 50, 75, 100 or 125 bytes or any multiple of 25). Maybe a little bit harder to see the individual 25-char codes and maintain them but it's on the other hand stored in one central place.

Thanks a lot for this, works a treat. The maps seem to be couple of years old though. Does anyone know if there are more up to date maps available?

Thanks

I've downloaded via megaupload the rar-files. Unpacked them and ran Fast IMG Unlocker V2.1 on the .img file. After about 5 minutes the unlocker gave the message it was finished. I also made a virtual SD-disk and I made a directory Garmin it. So I copied the unlocked .img file to my virtual SD. Started Basecamp and yeah Basecamp saw my virtual SD and the .img file in it. It's called Garmin Discoverer 50K All v2.00. So I started zoomimg on the map. But didn't matter how far I zoomed I never saw real topo images. I kept zooming in on the second level map, never got to the tiles with image info like you see in post #1. BTW detail is on "high" and viewing only 2D mode. "Only basemap" is unchecked.

Also when selecting this map I got the message it wasn't printable, big deal but just mentioning it to check if this is normal and not part of the problem

What's the problem?

Seems to be the basecamp version that is causing this problem. I have 3.05. Will look for 3.1.2. and install it and try again to zoom in. thnx for this version info.