Last edited by Neil; 10th June 2015 at 04:36 AM. Reason: Merged & edited 2 identical consecutive posts.
[Slaps forehead with open hand]. Oh wow, do I feel stupid. I assumed that the drivers had been automatically installed because the first time I connected the unit to my computer the "device sucessfully installed" dialogue box had popped up and I was able to connect and transfer data without any problem dozens of times in the week preceding the bricking of my device. However, after I clicked on the link you provided and installed the drivers, the updater was able to recognize the device and the forced upgrade worked exactly as it should have.
That being said, I'm really sorry I didn't try out kunix's tool - I would have but the forced upgrade did the trick and I didn't want to push my luck. Thanks so much to everyone for their help - I'm grateful beyond my ability to express the sentiment.
Kunix's cure can't boot, after removing faulty files from dakota, flash original firmware.
Read with care cure thread.
sent with my phone
You have to navigate to get to the good.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
Not sure quickcure can work with Dakota, it has been tested on nuvis only from what I can read in kunix's thread.
Use "normal" GarminCure3 tool.
Follow instructions to get preboot in Dakota in this thread and then step by step how to flash it with normal cure in:
[Only registered and activated users can see links. ]
and
[Only registered and activated users can see links. ]
You have to navigate to get to the good.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
Bookmarks