Thread: Cyclops™ Safety Cameras for Garmin

Originally Posted by roger1109

Sorry,read my join Note in my previous post

I tried to do the tests in the most scrupulous way possible ..... np if you will not believe

Bye,bye

Yeah, sorry, i made that post just before you did the edit with the extra info. BTW, i'd believe you if you told me the sky was green and the grass was blue (anything's possible in Kentucky though!).

This is very interesting.

Unlock codes work in:
2x0 (your test), and i'll check soon in 255 to make sure they work in 2x5 as well as 2x0;
13xx/14xxx (i've just confirmed your 1340/1440 tests. In my 1300 US v6.2, original works with jm code).

Don't work in:
25x5 (you tested) and that means not in 24x5 either;
35x5 (i tested) and that means not in 34x5 either;
and probably not in any xx (i tested in 40>42 convert - doesn't work, will try soon in x0).

I'll also test in 23x0, 37x0 & nulink 1690 when i can.

I guess Pietu has a 2xx or 1xxx judging by his jpg guide.

Tested in 34xx it doesnt work ,but jetmouse .unl in 1200 works

Huh? I've never had an issue, even when using a proxy!



The issue is not these links but the user's client...

Hi..Eagle-eyed, roger, Neil.. Will love to hear when test are finish in nuvi 3590LMT EU.
I follow you here

Have fun

PS: I go to bed now, I nearly sleep in here

Not quite so though ... 2xx & 1xxx have had fw updates after Jan 10 and yet no protection for Cyclops only for maps. I just wonder why they have not bothered to implement it for those older devices, an oversight? I mean, if they did it for maps in 2xx & 1xxx why not for cyclops gpi too.

Originally Posted by Neil

I mean, if they did it for maps in 2xx & 1xxx why not for cyclops gpi too.

I think it is simpler than we can think. On this devices there were samples of Cyclops with old FID. Why Garmin must to bothered about it?!

I've found that on AU sold 1xxx devices, there were variants of FID 900 and 2496, and surprisingly, non-encrypted versions of AUSTRALIACYCLOPSSAMPLE.GPI as well.

On 3 US sold devices checked (1490, 1450 and 1300) there were no sample cyclops. All instead had 006D135900.gpi which is Airline data (MSM_Airport_v31) with IDs 0, 0, 0, 3. Not in a POI folder, but directly in .system.

Originally Posted by Neil

I've found that on AU sold 1xxx devices, there were variants of FID 900 and 2496

FID 2496 was in negligibly small quantity of device. I am a little know a programmers.They never modify old software without substantial reasons. Map update is beginning from 2200 FID and GMA check was reality. When FID had reached number of 2496 the stock of 1xxx was negligible. Why Garmin must to bothered about it?!

Maybe you misunderstood. I wasn't suggesting in any way that they should be 'bothered' about (doing) it. I was only curious as to why they bothered not doing it when they enabled GMA protection in fw of 2xx and 1xxx for maps. It would have been simple to do both at the same time.

The one example i found of an unencrypted sample file on an AU 1390T is a curiosity also, and i wonder what their thinking was there too? [Only registered and activated users can see links. ]. It's the only Cyclops gpi file that i've seen where GPFT says "File is not an encrypted GPI !"
I'm betting Giomen has an opinion.

On a more productive note, this is what i've found so far:

Models where JM generated unlock codes work with 700, 900 or 2496 FID:
2xx, 3x0, 465, 5x0, 6x0, 7xx, 8xx & 1xxx series.

Models where JM codes work only with 700 or 900 (2496 won't work):
xx, 2xxx & 3xxx. For those and related devices change FID 2496 to either 700 or 900 and add unl code, or simply unlock the file. Use PGFT.

Originally Posted by Neil

I'm betting Giomen has an opinion.

Garmin developer is a lazy thing! I understand them - I am the lazy thing too!