Hi, is any way to downgrade Zumo 595 from FW 4.60 to 4.40?
In 4.60 is a bug with selecting "Favorite POI" from map. ( see )
Garmin-support says :
"After further investigation, it appears we had a case open regarding this issue. Sadly this issue will not be corrected at this time"
I tried the procedure for change 590 to 595, but I was not successful...
595 FW downgrade
Re: 595 FW downgrade
unfortunately, when I save GCD file (I tried FW 4.40 and 4.30 from Perry) on SD card, then after restart Zumo asks : The software on the device is newer than the one you are installing - do you want to continue? I set YES, installation is in progress, but after restart it asks exactly the same. When I finally give NO, after Garmin starts up, it reports that the 4.60 update has been installed ...
I used this method on Garmin Oregon, but it doesn't work for Zumo... Am I doing something wrong?
I used this method on Garmin Oregon, but it doesn't work for Zumo... Am I doing something wrong?
Re: 595 FW downgrade
when I tried it on the device, nothing happened - Zumo did not report an update. It only found it on an SD card...
- mzeist
- Posts: 116
- Joined: Fri Apr 27, 2018 8:52 am
- Location: Zeist, the Netherlands
- Has liked: 33 times
- Been liked: 31 times
Re: 595 FW downgrade
your favorite POI screen icons seems very small, may be a factory reset will sort things out?
I run 4.60 without problems.
I run 4.60 without problems.
Groet, Marcel.
ST1300 - Etrex Vista, 60CS, Co300, SPIII, SP2610, Nuvi760, Zumo660, Or650, Nuvi3590, Zumo590/5, Zumo XT
ST1300 - Etrex Vista, 60CS, Co300, SPIII, SP2610, Nuvi760, Zumo660, Or650, Nuvi3590, Zumo590/5, Zumo XT
Re: 595 FW downgrade
[mention]sussamb[/mention] : Big thanks! With .system folder downgrade works, and now, I can use my favorites without restrictions !
[mention]Vespamarc[/mention] and [mention]mzeist[/mention] : Factory reset did not help... This bug is confirmed from US Garmin, maybe it only involves some revisions...
[mention]Vespamarc[/mention] and [mention]mzeist[/mention] : Factory reset did not help... This bug is confirmed from US Garmin, maybe it only involves some revisions...