Thank you so much for quick respond, unfortunately after downgrade your custom FW4.1 my Drive Smart 61 still get same problem.
Can you try to make with FW4.0?
Thank.
Printable View
The problem is same on my Zumo 396 after i upgrade from FW3.1 to FW3.4, Device can't be route or navigate.
https://scontent.fbkk2-7.fna.fbcdn.n...b9&oe=5C6BD5D0
https://scontent.fbkk2-8.fna.fbcdn.n...b3&oe=5C78411B
https://scontent.fbkk2-8.fna.fbcdn.n...39&oe=5C6E3A9A
Sure, here it is ...
This is a custom SD flash kit only for HWID 2588 devices (Drive Smart 61), firmware version 4.00
Instructions: see
DriveSmart 61 (2588) fw4.00.rar
Hi FireFox58
Custom firmware 4.00 still has problem with DriveSmart 61 + Thailand Map patched or Thailand Map (Genuine) then i try to downgrade FW to 3.7, yes this version works great with my Thailand Map (Genuine)
Can you make me a custom SD flash kit with FW3.7 again?
Thanks in advance
This thing is really bad, why does Garmin keep releasing buggy firmware? It is not a commercially correct behavior, Users must be protected.
Anyway, in the next few days I'll prepare the Package for version 3.7
:lol:
This is a custom SD flash kit only for HWID 2588 devices (Drive Smart 61), firmware version 3.70
Instructions: see
DriveSmart 61 (2588) fw3.70.rar
Maybe. That's actually best case scenario and even if so they'll not have incentive to fix it unless it also was causing problems with original firmware used with OEM area maps and legally purchased locked maps for other areas. I'm not optimistic of that being the real situation however. Likely actual case is that it's the reverse of users needing protection from accidentally buggy firmware. Garmin are likely quite intentionally looking to protect themselves from users modifying firmware. Perhaps they now have included further novel protection which makes the device practically unusable when the firmware is patched with UFP. The original firmware isn't buggy, user zdmax reports problems with "custom" firmware which I'm taking to mean "patched". Also the reports are not consistent, he's using TH mapping and found that V4.00 patched still had problems whereas other reports elsewhere seem to confirm both original and patched V4.00 and V4.10 are fine with latest US and EU unlocked maps, however both those maps when used were reported buggy only with patched V4.30. This problem may also be map area/version dependent as well as firmware version dependent in fact. Need more reports to determine this for certain though.
Thank you so much :fz:
Managed to get into developer mode on my Drive 51 however does not succeed in doing this for my Oregon 700
Tried all methods found on various forums but no luck
Can anyone help me ?
KeesvO
Dear vladan,
I kindly ask for you help. It's new Edge explore. HWID 3011.
Is there any other option to upgrade the firmware? The updater.exe crashes as soon as it starts the update process. I tried it the way you descibed. Error info:
App: Updater
At: 12/3/2018 9:15:52 PM (UTC)
OS: WIN32 Windows Platform, Major Version: 6, Minor Version: 2
Processor: Pentium Pro or Pentium II, RAM: 2097151 KB
IOU_USBLINK.CPP-710-2.8
App: Updater
At: 12/3/2018 9:29:25 PM (UTC)
OS: WIN32 Windows Platform, Major Version: 6, Minor Version: 2
Processor: Pentium Pro or Pentium II, RAM: 2097151 KB
IOU_USBLINK.CPP-710-2.8
App: Updater
At: 12/4/2018 1:04:30 AM (UTC)
OS: Windows XP Service Pack 3
Processor: Pentium Pro or Pentium II, RAM: 1048575 KB
IOU_USBLINK.CPP-710-2.8
App: Updater
At: 12/4/2018 1:15:52 AM (UTC)
OS: Windows XP Service Pack 3
Processor: Pentium Pro or Pentium II, RAM: 1048575 KB
IOU_USBLINK.CPP-710-2.8
App: Updater
At: 12/4/2018 6:08:54 PM (UTC)
OS: Windows XP Service Pack 2
Processor: Pentium Pro or Pentium II, RAM: 1048575 KB
IOU_USBLINK.CPP-678-2.8
<PartNumber>006-B3011-00</PartNumber>
<SoftwareVersion>300</SoftwareVersion>
<Description>Edge Explore</Description>
Lucas