Thread: Nuvi 265WT bricked

Unfortunately, I doubt it could load a 0827 gupdate.gcd from an SD, even if the HWID isn't screwed up by attempting a flash with MTK 1091 fw.

Originally Posted by pgardella

..............
The Garmin rep had me try the 1091 firmware, but the Updater refused to run because it didn't match the hardware.

He/She/It had you do WHAT?! God save us from blonde service desk droids. How was that fw rgn named? If it was named anything other than 109101000xxx.rgn [where xxx is the fw version] the flash would be forced. If it was named other than conventionally, the flash may have started but then aborted. Maybe your HWID has been overwritten to 1091? If Caty's good advice below doesn't work, try flashing the original 0827 fw in updater.exe named 'out.rgn'. If unsuccessful, try the 0827 cure fw as the same name.

Originally Posted by catymag

Lol fantastic advice flash wrong firmware!
Try to run cure as admin with Windows 7 or try a pc with XP.


Edit:Try also QuickCure3 [Only registered and activated users can see links. ] bottom of the post.

Originally Posted by pgardella

The firmware she had me try was "109100010760.rgn". So that's good.

No, that's BAD. The correct convention to prevent wrong fw flashing would be 109101000760.rgn. Like i said, any other naming can force the flash. Check the rgn file name again, probably you've mistyped it.

The HWID I noted originally came from G7Win after the call with Garmin, so thankfully its not overwritten.

I'll try the XP machine, then renaming the 082700010760.rgn to out.rgn and reflash, then try a cure version of the 082700010760.rgn file and let you all know.

What should the GPS unit say when the firmware update is successful? It goes into Mass Storage Mode, so I'm assuming I can see it in Windows (RMPrepUSB or Disk Management). But does the GPS show anything?

Don't flash the original fw if the HWID is still 0827, you still need the cure fw loaded for it to be able to reach Mass Storage Mode.

The unit will be stuck on the splash screen. The cure fw cannot fully boot, which is it's entire purpose so that a faulty file cannot be loaded during the later part of the boot process. As long as the nuvi goes to MSM, you can see the internal files in Windows Explorer, try removing the newly loaded map[s], it may be enough, but you can always then reformat with RMPrepUSB if there are other damaged files as well.

On the SD possibility, would I just use the "nuvi2x5W_GCDFile__760.gcd" and rename it GUPDATE.GCD? Should it show anything on the screen?

If you are going to do that from the SD, rename it gupdate.gcd and put it in a Garmin folder on a clean card. If it flashes it'll show 'Loader' above the Garmin logo and maybe a green line briefly below it. Try it before you load the cure. It probably won't read from the SD anyway, and because it stuck on 'Loading maps' I really think it's probably a faulty map file rather than a bad fw but it's worth a try i guess. If it doesn't flash, move on to the cure. Once you've loaded the cure, if removing the maps doesn't work, then reformat it, create a Garmin folder in the root of the unit memory and just flash the original fw as an rgn with updater.exe [named 082701000760.rgn only].