Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

Originally Posted by Maldonis

8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
How to unbrick a nüvi - step by step guide
Readed and tried, but I can't found .GCD file for my HWID.

Original

Code:

Please Login or Register to see the links

@ciprigfh
I think you may have confused the instructions. EITHER you directly use the supplied QuickCure3.rgn (unchanged, just safely renamed appropriately as XXXX01000xxx.rgn - see below) OR you use the device's actual firmware to make the Cure3 RGN. It seems like you're trying to make the Cure3 fw from QuickCure3.rgn. QC3 is ready to use after renaming, "XXXX" being your device's HWID and "xxx" being the current fw version loaded to the device, e.g. 290001000154.rgn. Whether you use QC3 or Q3 the RGN's safe-naming convention is the same. Best try with QuickCure3 first as it usually works, but Cure3 always works to re-enable Mass Storage Mode in compatible devices.

It seems the Fenix 5x plus firmware may not be in traditional Garmin format therefore it's not recognized by GarminCure3.exe for patching of file names. Check if it's encrypted because if so there's no help for that as far as i'm aware.

Have you tried using QuickCure3.rgn? If not and you want to try it, [Only registered and activated users can see links. ]. Rename it to 290001000154.rgn and flash in preboot (at your sole risk of course, i don't know the outcome).

Another way if it's not encrypted firmware is to try the old original method we used before kunix made his cure3 app. Done by using a hex editor to rename IMG to MIG for example in the firmware RGN to make a cure firmware specifically for by-passing loading map image files on boot. See post #4 here: [Only registered and activated users can see links. ] Also this thread: [Only registered and activated users can see links. ].

@heresy
This reply is not timely sorry, i only just now noticed and read your post. If you still need help to solve you may need to give some more info after trying again as below.

Some thoughts:
Firstly, 1xxx devices don't use NTU (Unicode) maps, they are only offered NT maps by GarminExpress.

Secondly, QuickCure3 usually works with 1xxx devices but not always depending on the problem causing the soft-bricking.

I get error message "The GARMIN device is unable to program the requested memory region.
This could be due to an incompatibility between this application and the GARMIN device.
If this error continues to occur, please contact GARMIN Technical Support."

That error message may be only due to the device and Updater.exe losing communication, for instance by the device dropping preboot mode, or due to some corruption in the cure RGN file, but it can also be indicative of a damaged flash region that cannot be written to. I suggest you re-make the cure firmware and try again to flash but this time ensure that the RGN is loaded to Updater.exe with it's GUI visible on your desktop and the radio button next to "USB Device" selected. Ensure your device is fully OFF, not just in standby. Hold the top LH corner of the nuvi's screen and connect the device to the PC watching the window next to "USB Device" for it's details to appear. IMMEDIATELY you see the window populated, press OK on the GUI and keep holding the screen firmly.

The problem it seems is that the device is dropping out of preboot before the flash is fully established, you can see in the second image under your point '3' that its details have disappeared from the window to the right of 'USB Device'. Bootlooping devices like yours can be tricky to catch and hold in preboot to get a flash established, so speed is of the essence as is timing and a bit of luck. Patience and persistence is key if the flash fails, it may take many attempts to find the right moment but you can greatly increase the chances by doing things quickly and in the right order to fluke an initiation. Once a flash is properly initiated (with data packet exchange to and from Updater) the device will hold preboot and not re-start unless the connection is physically broken. Your hack with the rubber while clever isn't really really necessary. If you hold the device in your left hand with your fingers on the back of the device and your left thumb pressed in the LH top corner of the screen it allows you to firmly control and move the device around while leaving your right hand free to connect the USB cable in a timely manner. There's a correct sequence for things to be done because the period it will stay in preboot is now extremely limited due to the bootlooping behavior. Usually 1xxx devices do have a 30 second preboot opportunity which is long compared to some other series however in your case it may only be around a couple of seconds before it re-starts and therefore interrupts preboot.

Before attempting to put the Garmin into preboot, follow this:

• Load the cure RGN into Updater.exe
• Leave Updater's GUI open and visible on your PC's screen with the radio button next to "USB Device" selected

Now turn your attention to the Garmin:

• Ensure the device is fully OFF. Force it off if necessary by holding the power button down.
• Plug a 'known-good' USB cable into a USB2 port of a Windows computer (avoid using a hub or a USB3 port or a front port of a desktop PC)
• Apply pressure to the device screen and with your right hand plug the USB cable into the device's miniUSB socket (that will power it on) then move your hand quickly to the mouse while watching Updater's GUI on the PC screen
• Immediately hit the 'OK' button on Updater's GUI (or just hit the Enter key of your keyboard) when you see the window to the right of 'USB Device' on the GUI populated
• Move the cursor immediately to the 'Yes' button on the message about same software version and quickly click it
• Keep the firm steady pressure on the screen while the flash initiates, if you don't do that it will fail for sure. Once you see 'Software Loading' or similar message on the device screen you can relax the pressure but if in doubt just hold until 'success' message is displayed by Updater

The device should now attempt to reboot and stick on the logo screen but have Mass Storage Mode enabled so you can delete the corrupt files or as a last resort properly re-format it, but only if absolutely necessary. [Only registered and activated users can see links. ]