Thread: Cyclop Safety Cameras for Garmin

Tried what? If you mean FID 65535 files they should work in your old device. Probably even the original file with FID 2496 and a properly *named* generated *.unl code should work in zumo 660 without using PGFT or anything else other than Jetmouse generator. Note that UNL and GPI files must share the same naming, e.g. SafetyCams.unl paired with SafetyCams.gpi.

The unlocked files work fine as always, thanks Sue Davison! , I wonder what the difference is.

There's a big difference between 'unlocking' with PGFT to FID 65535 and 'unlocking' with tools such as syzygy's gpi_tool. The latter actually decrypts the file. Confusingly such files are often also commonly referred to as simply 'Unlocked', rather than 'Decrypted' or 'Unencrypted' which are far more accurate terms than 'Unlocked' for them.

The initial post gives this explanation:

Note there is a difference between 'unlocking' and 'decrypting' GPI files. Decrypted files will work with all devices capable of using Cyclops files. In modern MSV protected devices patching of the firmware may additionally be needed, more info in this post. Unlocked files generally work fine on older devices without modern firmware protection but may require FID to 700 or 900 change.

To unlock, use pietu's Patch Tool or marcocq's PGFT attached below.

To decrypt, use syzygy's Garmin GPI Tools v1.0. Sometimes decrypted files are often also loosely referred to as unlocked.