thanks mate.... doesnt matter what is a name of a file for example: EastEU cams , or EasternEuropean Cameras?
For Nuvi device (as nuvi1340 LMT) :
create at the root of gps a folder called poi
put in this folder the .gpi files of the archive
good luck
thanks mate.... doesnt matter what is a name of a file for example: EastEU cams , or EasternEuropean Cameras?
You can call it what you want.
Also I saw your post about Garmin SCDB.info The Worldwide Speed Camera.
Try not to install both types of speedcams one or the other.
If you keep both types of speedcams you will get double warning all the time.
I would use the official speedcams only.
SD:\garmin\poi\US+Canada_safetycam.gpi
and when your gps ask you: do you want put cyclop inside your gps, you say yes
If you prefer you can put directly inside your GPS, inside "POI" folder ex: your GPS:\Poi\US+Canada_safetycam.gpi
you can remove this inside your poi folder any time, if you dont like !
because "Brexit"
Joke!
so "UK/Ireland Oct-31-2018 Safety Camera, you have UK + Irlande its same for Canada or Usa, its inside same same kit "US+Canada_safetycam.gpi"
if you have inside this kit "UK/Ireland Oct-31-2018 Safety Camera"(UKIreland safetycam.gpi)
and after:
EX INSTALL:-----»
SD:\garmin\poi\UKIreland safetycam.gpi
and when your gps ask you: do you want put cyclop inside your gps, you say yes
If you prefer you can put directly inside your GPS, inside "POI" folder ex: your GPS:\Poi\UKIreland safetycam.gpi
you can remove this inside your poi folder any time, if you dont like !
For check it if is inside your GPS:
- setup
- about
- scrool down
and old exemple (is mine):
Last edited by quebec001; 26th November 2018 at 12:27 AM.
dēzl™ 780 LMT-D
When you update dēzl, the Garmin Express automatically downloads the POI points on device into the folder POI\ :Code:Please Login or Register to see the links
· Driver alerts for sharp curves, school zones, red light and speed camera warnings and more.
This is genuine and works on the device as it should.
Dēzl can not see the unlocked POI point and more because the device has built-in MSV (MSV = software protection).
You can find out more about this here.
Code:Please Login or Register to see the links
Thank you very much for all the unlocked Cyclops files over the years!
I've tried to unlock the locked files for my zūmo 660 myself:
- loading files into Protected Garmin file toolkit_2254_x64 and pressing unlock button, creating new, _unlock files
- changing the FID's and creating a corresponding .unl in the Garmin POI folder using Jetmouse KeyGen_v1.5
- dragging the files over the decrypt in gpi_tool_v1.0 individually
However, I cannot see camera's this way. Is there a certain order in which to operate the Protected Garmin file toolkit_2254_x64? The readme file doesn't explain.
Unlocking Cyclops GPI files using PGFT and other similar methods is fine for older devices. For newer devices they must be decrypted but that's optional for older devices without protected firmware. Your zumo 660 is an older device, so either of the methods you used should work. Have you also tried the "Unlock (FID 65535 ..etc)" button in PGFT because that should work for you without an UNL code. Also try the already decrypted ("unlocked") [Only registered and activated users can see links. ]. If nothing works then maybe you've not got the camera warnings enabled in your zumo's settings.... Something like: Tools>Settings>Proximity Points>Change and ensure the "Garmin Safety Cameras" entry is checked.
Thanks for the quick response Butters, but I've also tried that. PGFT indeed says the files are unlocked but they don't work The unlocked files work fine as always, thanks Sue Davison! , I wonder what the difference is.
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.
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 unlocked files work fine as always, thanks Sue Davison! , I wonder what the difference is.
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.
Last edited by Butters; 16th January 2019 at 01:10 AM.
Bookmarks