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

**Butters** · 2nd August 2018, 11:34 AM

It may be possible to restore it. It might depend on what firmware was flashed, both wrong initially and "proper" later. Please give links to those firmwares. Regardless, likely this cure is not what you need. The device may not be recoverable or it might be a very easy fix depending on whether it can access preboot mode (see here: [Only registered and activated users can see links. ]) and additionally what symptoms it displays. Give all relevant info, no matter how minor please.

**Nelson17** · 4th August 2018, 03:07 PM

Garmin Zumo 220

Hello, the device stucks when booting. You only see the Garmin logo. What I already did. I have the firmware zumo2x0_GCDFile__300.gcd. With the tool "RGN Tool" I created the file zumo2x0_GCDFile__300.rgn. I created a cure version with GarminCure3 and flashed it on the device in Preboot Mode. It is still not recognized as a USB device. Can you help me. I got the device from a friend and unfortunately I do not know what was done before and why it is broken.

**Butters** · 7th August 2018, 12:05 AM

@Nelson17
Is there any message appearing on the screen with the Garmin logo when it sticks on attempted boot with normal firmware loaded?

If you prepared and flashed the cure firmware properly but don't get Mass Storage Mode return the problem could be hardware not a corrupt file.

**silmaress** · 28th February 2019, 08:45 PM

Hi!
I've got a Nüvi1390 which is caught in a boot loop.
I already started it into preboot mode and tried to flash the Cure Firmware, which fails with "The GARMIN device is unable to program the requested memory region."

Flashing the QuickCure is successfull but sadly it keeps to reboot instead of being recognized as mass drive.

Any suggestions how to get this device back to life?

Thanks in advance!

**Butters** · 28th February 2019, 10:57 PM

That could indicate physical flash damage which is not correctable by cure firmware. Quickcure3 usually does work on 1xxx series to enable MSM in a software-bricked device so the continued boot-loop indicates that it is maybe a hardware problem as Quickcure doesn't involve the original firmware at all. The message "unable to program the requested memory region" when flashing full firmware might mean that region 14 where the main system software is stored is physically damaged or it could be region 127 or even both.

You could try to flash an RGN made without a fw_all.bin component as a test. Be aware that 13x0 have two different HWIDs. Most are 0972 but devices with Mediatek chips have 1104. Double check your HWID: [Only registered and activated users can see links. ]. To make such an RGN, open original fw in RGN_Tool and uncheck the second section for fw_all.bin then save as xxxx01000630.RGN substituting 'xxxx' for your device's 4 numeral HWID. See image below:

Spoiler: Click

If Updater.exe can successfully flash region 127 (hex 0x7F) then it's maybe region 14 (0x0E) which is damaged. If you get the same message then try flashing again using an RGN file made including fw_all.bin but without section 3, resources_7F05.bin. If you get that message again trying to flash only region 14 then it's likely unrecoverable but there are some other things we can try.

**silmaress** · 3rd March 2019, 01:50 PM

Hej Butters,

sorry for the delay!
This nuvi is HW ID 0972. I tried to Flash both Firmwares build with rgn_tool, but sadly no success. Wether the file with section 1 and 3 nor the file with section 1 and 2 did work, both had the same error.

Any other suggestions?

Hej Butters!
I replied some days ago, but somehow my reply wasn't posted, so now once again.
Thanks for your tipps! I first tried to flash rgn with section 1 and 3, after that with section 1 and 2, but both have no success. Updater always says "unable to prgoramm the requested memory region". HWID ist 0972.

An other suggestions? Since it is the device of a friend and he said, i should put it to trash ist is not that important to save it.

**Butters** · 6th March 2019, 11:12 AM

On the understanding that this device may have physical flash damage making it uneconomical to recover and he's prepared to sh!tcan it anyway, let's proceed to play with it and see if any other little tricks work because if we brick it entirely there's not likely to be any repercussions from him it seems.

If possible i'd like to have some background as to how this happened or whether it just suddenly went into a bootloop. For example, ask your friend if just before the problem started had he'd flashed any firmware or other updates to it please? If not, anything else he may have done just beforehand. If it happened out of the blue, then ask if it was running and/or actively navigating or did it happened when he turned it on. A spontaneous bootloop is more likely to be symptomatic of flash damage.

PS: Did you obtain that HWID from connecting to G7ToWin in preboot or some other way?

**MarcBol** · 16th July 2019, 06:18 PM

Hi, I'm having troubles with a bricked Nüvi 1490T and I want to use this guide to unbrick. However I'm missing the firmware file for this model as you cannot download this from the Garmin website. Has anyone a link to this file?
Thx

**Butters** · 17th July 2019, 01:42 AM

@MarcBol
Garmin doesn't make it easy to directly download firmware files, they prefer that ppl use GarminExpress to update. However if you go to the main history page and right-click anywhere you'll see a context menu with "View page source" or similar (wording is browser dependent). Click that and another page opens giving instructions for downloading the GCD file. Be aware that 13_14xx devices have 2 different HWIDs and if you flash the wrong one you might permanently hard-brick your 1490. Read this thread where you'll also find the direct links to download the latest V6.30 firmware: [Only registered and activated users can see links. ]. To check your HWID use G7ToWin in preboot mode or just look at your GarminDevice.xml file if you have a backup. More info here: [Only registered and activated users can see links. ].