Bootlooping devices can be tricky to flash however the flash chip may have physical damage as already suggested in Post #125. When you get the message from Updater.exe that it's "unable to program the requested memory region" it means that it's not able to write data to a specific region which it's trying to flash, i.e. in your case Cure3 firmware contains the boot.bin intended to be flashed to region 12 (a virtual region), fw_all.bin to region 14 and resources.bin to region 127 (both physical regions).
If there's actual damage (think, like 'bad blocks') to the flash memory, which involves any of the relevant permanent regions, then the flash fails with that Updater message. You can keep persisting in trying to flash it and hope to fluke it but the fact that you've seen it remain in Device Manager for a while means that it's holding preboot (not dropping it in a few seconds like some bootlooping 'soft-bricked' devices do).
You can also try flashing it from an sd card using a modified boot.bin as RGN file in preboot with Updater.exe. It's less than simple to make the required kit for that so i've made one for your nuvi but if you use it the risk is all yours.
Preparation: Please use only a Windows PC, preferably a desktop and connect only to a REAR USB2 port. Avoid using a front USB, hub or USB3 port. Have a suitable 'known-good' miniUSB cable with the A plug inserted ready in the selected port of the PC.
Now look behind the spoiler below:
Spoiler: Click to view
Report back results. Hopefully you'll now have Mass Storage Mode available. We can go further only if it has indeed worked as intended.
Remember, this is solely at your risk if you choose to use the above recovery method. I've taken all care in the making of the SD kit however if your device has a failing flash memory the chip may just die at any time and each flashing attempt puts additional strain on it.
Bookmarks