Thread: GarminCure3 tool - the new way to create cure firmwares for Garmin devices

@rafaelroni
Using a ldr.bin, aka boot.bin, from another device's fw is very risky and potentially will hard-brick it by writing an incompatible bootloader to region 5. It's not possible to know if a different device's ramloader (boot.bin) will be safe unless it's been tried and reliably reported so i highly recommend you not be the first.

Drive 52 is identical to Drive 5 Pro in that they use the same firmware and share a HWID. I'm unable to personally confirm that their HWID is 3061 however if you've used G7ToWin correctly and it's reported 3061 then that's reliable.

Do you have a file system backup of the device, even an old one? If so, it may be possible to use that to download the correct firmware from the Garmin server.

Thanks for the tip, I won't try to use the wrong LDR.bin.

The problem is that Garmin is not distributing firmware or .gcd for this model.

Do you have any idea how to solve this problem?

I'm sure it's a wrong .gpx