Thread: Garmin 2689 LMT - Europe map download.

Man! You're such hard work Geoff, LOL! .... All the map threads are listed in the [Only registered and activated users can see links. ]. The thread for the latest files you need happen to from be the very first listed there presently: [Only registered and activated users can see links. ]. Take the following files from catymag's Post #1 there:
Original gmapprom.img locked, signed; gmap3d locked, signed; CN Europe NTU 2016.30 Foursquare locked, signed img; D3048210A.JCV - Lane Assist Portrait Full; Nuvi 34XX ASR; SID 25x9

Unlock all the img files with [Only registered and activated users can see links. ]. Rename 'gmapprom.img' to 'gmapsupp.img'.

PS: OSM maps are not locked and not signed, so they will work in any unit whether protected fw or not. I'm now wondering if the patching has worked as the GMapTool info seems to indicate your present EU map is unlocked properly. Before you download again, i'll remake the kit for you in case something went wrong with that download, it's much smaller than a map re-download and i won't include the nonvol backup script in it as you've already got those regions ... Standby.

EDIT: Here 'tis:

Spoiler:

[Only registered and activated users can see links. ]

Same procedure, extract it to a clean microSD. Ensure unit's fully off, insert card and turn back on.

No it's not the problem, that's the 'conventional' naming for an img file in a card, also the placement "x:\Garmin\gmapsupp.img" is universal for a media card in any Garmin device. If the original EUU img from Caty's post doesn't work when unlocked then it's likely the SD patching method isn't working properly for some reason.

You could try naming your present map 'anyname', e.g. 'CNNT_EUU_2016.30.img' and place it in a root folder named Map in the card, but it seems the unit is 'seeing' the present gmapsupp.img on the card when it's loading maps at boot but detecting it as locked even though it seems to be properly unlocked.

Let's know how you go with the new img. If that doesn't work i'll look for some problem with the SD paching pack.

While you're waiting for the map download to finish, if you want to try again with an RGN file i've made one for you from a patched GCD:

Spoiler:

[Only registered and activated users can see links. ]

Extract Updater.rar somewhere convenient such as your Desktop and open resultant Updater folder to find 194801000821.rgn and Updater.exe files. Follow the instructions in [Only registered and activated users can see links. ] precisely and be very quick once the unit details show up in the GUI because i suspect that your unit only stays in preboot for mere seconds, but once a flash has started it should then hold preboot. The very instant you see "nuvi 2689 [UID 3...." or similar in the window click 'OK' or hit the kb Enter key.

One more thing, i almost feel silly for asking, but you have been clearing nonvol memory before/after these flashings i hope. [Only registered and activated users can see links. ]. Unwanted things can remain in there otherwise.

I had considered that Caty and have consistently mentioned gimgunlock+mapsigpatch, even giving Geoff the named thread link in both Post #17 & 22: [Only registered and activated users can see links. ] ... However, if the firmware is properly fully patched this message shows on the patcher's GUI at completion:

Spoiler:

Firmware version as specified in GCD file: 8.20 for Nuvi 26x9 C4.
Firmware name: Firmware version 8.20 for Nuvi 26x9 C4.

Applying rule set MSV... Ok.
Applying rule set GVS... Ok.
GCD signature removed.

File patched successfully.

That means, by my [admittedly] layman's understanding of how it works, that both GCD Verification Signature [or GCD Signature Verification] and Map Signature Verification checks have been removed from the firmware. Therefore even original gimunlock [without Map Sig Patch] should be successful in 'unlocking' maps for use in a previously protected unit, even one with usually a 'strong' protection because its now patched firmware becomes as 'weak' as an older unit like 2xx/7xx with "MSV: ---" and "GSV: ---", i.e. there no longer is either type of verification check in the patched firmware. Only if MSV [but no GSV] is still present in fw does the map require an unlock with gimgunlock+mapsigpatch is my understanding. Happy to be corrected on that tho'.

@Neil
You are right, but nuvi error messages have a sense.
Let's see if our friend is more precise about what he gets.


sent with my phone

I wonder did Geoff get his EUU 2016.30 from the same torrent as this guy?: [Only registered and activated users can see links. ].

Impossible to read your screenshot old bean. To check files/folders appropriateness just look at the threads below 'About Garmin Files&Folders&Addition files' in the [Only registered and activated users can see links. ].

Originally Posted by GeoffRBG

............
Is there any way I can tell if the supplementary files (JCV, ASR etc) are working?


[Only registered and activated users can see links. ]

That's so screwed up i don't even know where to start without a stiff belt of Scotch or a strong coffee, maybe both. The correct folder names are ASR and JCV so there's a start and they go in the unit's hidden .System folder or on the card in Garmin root folder. Where have you got those folders and files placed and are they on the unit or card?

Originally Posted by GeoffRBG

I've enlarged the post #30 pic. Is there a way to check if all aspects of the map are working?
G

Get the Missus to crank over the Model T and go for a drive .... or put the unit in simulation mode and pretend you are.
But best fix up the folder names/placement first.

EDIT: Oops, SF got in first.