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

Resurrection for my old Garmin Nuvi 1360 Asia version (Philippines).
I did install Garmincure3. Downloaded firmware "nuvi13xxand14xxseries_GCDFile__630.gcd" did not work but the QuickCure3.rgn..
It says "no firmware update for device".
Yes, i did the "cure" and not "original". But my nuvi wont go to mass-storage mode but thanks to "quickcure3.rgn".

My problem started when i formatted Nuvi to ntfs, and went to boot loop.
Followed kunix's instructions, and my device went to pre-boot mode (Power ON while pressing the upper left screen).

Since i saved all the files including system files inside the Nuvi before, so i had to copy backup copies of all the folders and files inside the device.
That's why i did not do the garmincure "original". What i did is update to Garmin's "webUpdater".

I am now updating maps using BaseCamp.
[Only registered and activated users can see links. Click Here To Register...]

You could have bricked it badly trying to use that GCD file which is for US/EU 13xx devices with HWID 0972 whereas your Philippine's 1360, like other similar Asian models, has a different HWID (the PH model 1360 is HWID 1311 and its latest software version is 2.20).

The reason the attempted flash of the Cure3 RGN file didn't work is because of the 'fail safe' default naming of the file created by Cure3 and the subsequent cross-matching of the first 4 digits of the file name with the actual device's reported HWID. If a mis-match is found then Updater.exe aborts the flash and reports "No update available" message. However QuickCure3 doesn't involve the firmware of the device being mostly universal.

There is a reason to use an RGN file to re-load the original firmware too after using individual Cure3 fw. Using WebUpdater or GarminExpress doesn't directly flash the firmware. The GCD file is like an 'auto-start' EXE file that flashes the firmware to the various regions AFTER the device reboots and a device with Cure firmware loaded cannot fully boot. QuickCure3 of course works quite differently to enable Mass Storage Mode for removal of files or to reformat. In your case, required to format back to FAT32 from NTFS.

If you copy back a faulty file then the problem re-occurs so provided you're certain the backed up files you've used are known-good your device should now be fine.

The garmin quick cure worked amazingly to get my device into mass storage mode, I am now able to get my nuvi 1410 to connect to my pc to fix the firmware thank you

Worked on my Nuvi 50LM. old but now operates like new even fixed my battery not charging all the way up issues! and to all hard at work to save these units thank you to all! cheers! :bat:

Welcome!
A friend of mine bought a used Garmin 3760 device, he claimed it offered an upgrade. He accepted, the iron restarted, but it only reaches the Garmin logo and stops there. The laptop does not recognize it, even when I plug it in, only the logo appears on the screen. Maybe something else can be done with it? Thanks!

@Lezil
Read this guide: [Only registered and activated users can see links. Click Here To Register...]. I recall that QuickCure worked for a bricked 37x0 device for me some time ago. It's always worth trying it first before making custom cure firmware anyway, it won't harm the device further and may save you some time and effort, so also read [Only registered and activated users can see links. Click Here To Register...] which is additionally linked in kunix's initial post.

Butters@
The firmware exchange was successful.
The device is recognized by the laptop, GarminExpress recommends a software update, but it does not start, it stops at the Garmin logo. I couldn't do the formatting, I don't know which is the damaged file, so I accidentally deleted the GarminDevice.xml file. So GarminExpress no longer recognizes it. Maybe something can be done with it?

Edit:
Solved!!!

@Lesil
By your post edit saying 'solved', i guess you've already worked out that when cure firmware is loaded the device CANNOT fully boot and it's quite intentional that it stalls on the logo screen before it can load any essential files like maps, voices, POIs, etc.. The only purpose of cure fw in fact, is to re-enable Mass Storage Mode (BTW, GarminExpress only sees devices which have Mass Storage or MTP modes available).

After you've removed any offending file/s or formatted, the ORIGINAL firmware must be loaded as an RGN file in preboot mode to allow the device to boot fully. When it does boot, it automatically re-creates the XML file as it does so on every boot cycle. If you formatted the 3760 you will need to load another basemap manually because GE won't offer a replacement: [Only registered and activated users can see links. Click Here To Register...]

Hey guys!
So I do have a bricked Etrex 30. Will try to save it now, did I get the procedure right?

0. Download USB-Drivers (does somebody know if these will work on Win11?)
1. Remove Batteries and µSD from device
2. Download "GarminCure3.exe"
3. Download Firmware ([Only registered and activated users can see links. Click Here To Register...])
Which FW? Could I download directly a RGN, so I wouldn't need to convert the GCD to RGN?
4. When "making" a file with GarminCure3.exe what option do I need to select? "Original" or "Cure"?
5. Connect the device forcing it into "preboot-mode" (holding the joystic in up-position and single press to turn on the device, right?)
6. Now pressing Update in GarminCure3.exe
7. Now I should be able to access the device in MSM, right?

What now? Now I need to update the device via Garminexpress?

Tahnks!

You should explain how your device got "bricked" and symptoms so you can get the most relevant help.
Confirm your HWID is 1305 then Download the latest FW directly from Garmin.
[Only registered and activated users can see links. Click Here To Register...]
Use GarminCure3 selecting "cure" it will create the 1305010000490.rgn
You should have Updater.exe in the same folder.
[Only registered and activated users can see links. Click Here To Register...]
Everything is explained clearly in Post # 1