TLDR: If you're curious as to what's likely happening read it all. Otherwise if you just want to try something else go down to the red asterisk.

Quote Originally Posted by askelly View Post
My better half was taking the device to the 'strong metal container' saying I'd spent too much time on it... It's dead, Jim.... I have spent too much time on it.
She's probably right. But i'm stubborn and we've got some last gasps before Jim hears the fatal words so bear with me. You best tell the missus you'll give her a back rub, take her shoe shopping or woteva floats her boat when this is finally all over.

Q1 - I had disk management running in the background. The device never showed. Even when device manager showed it, disk management did not.
QuickCure3 did nothing. The device always exits preboot on it's own (therefore drops from Device Manager) if a flash doesn't initiate properly within a set period (model dependent) and i think 1xxx series is about 20-30 seconds from memory. If a healthy device exits preboot due to timeout it'd then show the white calibration screen with the black dots. Clearly Updater.exe is initiating the flash but the device either isn't capable of processing the data stream or is ignoring it.

Q2 - The error message about not being able to program the requested memory region only appeared when using the full cure fw. When updater runs, it tells me "your current version is the same as the update version. Do you want to replace the current software with the same software version?" And I click Yes. It gives a message about initializing, then 100% complete, then "erasing" (doesn't say what) then fail.
So that means the device and Updater.exe have exchanged some data. I mean it's been queried by Updater about both its HWID and the current fw version and it has responded appropriately.... therefore there's still some feint hope. I guess almost certainly that the region unable to be processed is region 14, because it contains the "main system software" as Garmin calls it's primary firmware, i.e. the fw_all.bin component of a normal RGN or GCD file. There's no involvement at all of the firmware when using QuickCure. Therefore a problem with region 14 explains why Updater doesn't throw either of those messages when the QC flashing is attempted, but the error shows when using normal Cure which does involve the firmware.

I tried another computer (still Win10), different USB ports, different cables.
Thanks for that test result. It's always worthwhile to confirm that it acts the same using different ports, cables or PC although in this case it wasn't really suspected as a problem.

*So some last rescue breaths for him before he's pronounced dead. This really is the last chance, Should this not work then you can strip it for parts, if you can be bothered, and sh!tcan the rest. Screen, battery, bezel and USB port do have some value.

Behind the spoiler you'll find a kit which contains an RGN file made from a modified boot.bin capable of running text commands from an SD card along with a "how to":
Spoiler: Click
[Only registered and activated users can see links. ]
  • Extract the above ZIP file to find Updater.exe, 097201000630.rgn and a folder named "Contents for Card" which contains Garmin folder, 14.bin and 127.bin.
  • Find a CLEAN microSD formatted in FAT32 only. Reformat it if necessary.
  • From the "Contents for Card" Folder, copy the Garmin folder and the 2 BIN files onto the card and insert it into the nuvi with it fully off.
  • Drag 097201000630.rgn onto Updater.exe to open it's GUI.
  • Connect the nuvi to PC with the nuvi in preboot and flash normally.

If Updater reports an error it's dead mate. Toss it and take the missus to the shops. If it flashes but the file 'Update.log' created in 0972 folder reports an error please post it's contents. Report either way and Happy New Year regardless.