Thread: How to reverse back your Garmin unit to a previous FW version

@GermanStar
Try this then:

Spoiler:

Open the GCD file in RGN_Tool and press the 'RGN" button saving the file as"XXXX01000xxx.rgn" where 'XXXX' represents the HWID of your nuvi 57 (should be 2087) and 'xxx' is the firmware version (e.g. version 4.50 is '450').

[Only registered and activated users can see links. ]

Drag the saved RGN file onto Updater.exe and enable the radio button next to 'USB Device'. Put the 57 into preboot, click 'OK' to execute the downgrade. Click thru any message about lower version.

Code:

Please Login or Register to see the links

Thanks for the push, I really appreciate it! Unfortunately, I cannot get past the following message from Updater: there are no usb devices available

I have tried with three different Garmin units (nuvi52, gsmap64s, and nuvi57) on two different PCs: Win 10 and Vista). No joy.

EDit: The problem may be my unfamiliarity with preboot. What is preboot, and how to achieve it?

OK I've done a little more research, and now successfully have the device in Mass Storage mode, and believe I sorted out preboot -- thumb on upper left, hit power, then connect to USB before calibration screen, thought I don't see preboot mode anywhere on the display. Still no joy: there are no usb devices available

Originally Posted by GermanStar

OK I've done a little more research, and now successfully have the device in Mass Storage mode, and believe I sorted out preboot -- thumb on upper left, hit power, then connect to USB before calibration screen, thought I don't see preboot mode anywhere on the display. Still no joy: there are no usb devices available

Some more tips:

• You need Garmin USB Drivers loaded to the PC for it to see devices in preboot: [Only registered and activated users can see links. ].
• In Mass Storage Mode check for a file named gupdate.gcd in the device's (usually hidden) .System folder. If that file is present remove it or the device may flash back to current firmware version after downgrade. You may need to make changes to folder options in your computer. [Only registered and activated users can see links. ]
• Have the RGN file already loaded to Updater.exe BEFORE putting the device in preboot. Enable the radio button for 'USB Device' and leave the GUI open and visible on your desktop.
• To enter preboot have device fully OFF (not in standby), connect a usb cable directly to a REAR port only of PC (no hub), hold top LH corner of screen and connect the device while watching the GUI and hit 'Enter' key on KB or 'OK' button of GUI. Keep holding screen firmly until you get success message from Updater.exe or hold at least until 'Loader' shows on device screen.

Wow, this is really tricky. I sort of figured it out, and successfully loaded the older firmware, but it did flash back to the newest version. I'll follow your new instructions and let you now how it goes. Thanks!

Success! We'll see how useful the unit is now with this old firmware. It's back to interacting with Basecamp. That is one issue resolved. The other is the matter of the unit hiding waypoints it is not navigating to, not much of an issue for most, but a real problem for me, as I do a lot of off-roading in extremely remote terrain, and tend to follow waypoints I've loaded from Basecamp like breadcrumbs.

Thanks again, you've been a terrific help.

Originally Posted by GermanStar

The other is the matter of the unit hiding waypoints it is not navigating to, not much of an issue for most, but a real problem for me, as I do a lot of off-roading in extremely remote terrain, and tend to follow waypoints I've loaded from Basecamp like breadcrumbs.

Basecamp is not friendly with Nuvi. Save waypoint to separate GPX file on PC and then copy this file to device in GPX folder with any name for exception of current.gpx. After restart waypoints must be in list.

BTW, I believe what Garmin is up to here is actively disabling features in order to boost sales of their ridiculously expensive ($600) 276Cx unit. Now they don't want their newer automotive units to interact with Basecamp at all, and are discouraging off-road use however they can. I have a couple of nuvi 52 units, and they do nearly everything the 276 Cx does. And I have couple GSMAP64 units for hiking.

Anyway, one of my 52s broke so I picked up a 57 as replacement. When I realized Garmin had hobbled this thing, I called product support and screamed bloody murder. I suspect I was not alone, because they pretty quickly abandoned the nuvi name altogether. Subsequent product updates hobbled it further still. They now sell what was nuvi 57 as GarminDrive 51. In the meantime, I picked up a brand new nuvi 52 on eBay. So I'm good, but it would still be nice if a firmware reversion would render the 57 at least marginally useful. I'll find out next week when I go traipsing around the mountains some more. I'll bring a backup 52 in case it lets me down again.

Originally Posted by Grizzzly

Basecamp is not friendly with Nuvi. Save waypoint to separate GPX file on PC and then copy this file to device in GPX folder with any name for exception of current.gpx. After restart waypoints must be in list.

Basecamp is perfectly friendly with nuvi 50 and 52. Been using 'em for years. I copy and delete dozens, sometime hundreds of waypoints from Basecamp to nuvi 52 units every week.

Tested the 57 today with v2.30 firmware, and it is still flaky. Waypoints along mapped roads appear only after successfully navigating to one, but other waypoints along dirt roads may appear or may not. In one instance, we were driving toward a hidden waypoint and encountered a locked gate, so had to turn around. As soon as we turned around, the waypoint, now receding, was suddenly visible on the map. Bizarre. It is better than it was, but I'd hate to have to rely on it while traveling the back-roads. It is clear that Garmin is rewriting firmware to restrict the unit, as much as possible, to navigating toward selected waypoints only.

This is important information, because I believe I will no accept firmware "upgrades", for my old nuvi 52 units, in fear of nefarious hobbling activity from Garmin. Dunno about you guys, but I think this is all pretty crappy. I would love to dump Garmin on its high flying corporate ass, but am utterly dependent upon Basecamp and Garmin compatible maps.

@GermanStar
Like the other G, "Garmin givith and Garmin taketh away". However, that's not novel behavior by Garmin (also other manufacturers), very often they do things such as remove features and the firmware changelog doesn't reflect the changes accurately, like they just put 'Minor bug fixes'. Often there are good reasons for doing it because a device proves problematical in everyday use and/or for them it's the easiest way to sort it 'cos they've already got your money, right?

In this case I believe you're correct and they are nobbling devices very much on purpose. Other recent nuvi series and Drive line seem to be affected too. They may well extend to fw 'upgrades' for other devices recently superceded automotive ranges too, but probably not really old lines like 2 series and 1xxx because there's little point if my theory is right. That theory is they want ppl to buy an outdoor device for such activities and use their auto device for usual routing ... but who knows for the moment, maybe their software guys are just cocking up badly? Time will tell though.

[Only registered and activated users can see links. ]