If you consider it to be 'lying by omission' then yes, it's deceptive. But I do take the view that it's their obligation to ask questions about the circumstances if they want that information. To be clear, as I said I'm not aware of any device being bricked by use of the firmware patcher, nor am I aware of Garmin ever hunting down reasons why a device was bricked under warranty and then taking some negative action. They simply replace the device with another new or 'refurbished' device of the same model, send the other device to some mysterious chop-shop to JTAG it and re-program it and so the cycle goes on. It's hardly worth their while to do otherwise and maybe cop negative publicity about that kind of corporate vigilante mindset against customers. Turning the same device around after subjecting it to a repair process would maybe take weeks or maybe even months, their warranty replacement policy means ppl get a working navigator back within a relatively short period. A friend of mine left a near-new nuvi on his windscreen in the middle of summer in Wyoming for several hours. It then wouldn't turn on, just black screen. He had a new one back within about a week, absolutely no questions asked other than what the problem was and yet that's a problem well-known to be caused by exposure to excessive heat. Had Garmin actually asked the circumstances he told me he'd have owned up he said but didn't feel obligated when they only asked the symptoms not how it happened.
Well, it'd only be a problem if they found the bad img file and then realized it was an 'unlocked' map. But they'd have to go looking first of course and maybe they would if it was a serial warranty claimer.Interesting, I'm not surprise that Garmin might have a counter-cracked security check or something got corrupted and your unit FUBAR because of a bad .img
But never seen one posting of that problem.
That would probably have been Garmin LifetimeUpdater. Useless soft and never worked properly, eventually was withdrawn thank goodness.Whatever that was needed to do a map update for nuvi765 LTM; I remembered going through a lot of pain trying to do it on WinXP and finally gave up.
Thanks. However it might make less sense to someone less skilled in firmware. It makes total sense to you, but if you were a user who only knows how to use their device but with little knowledge of HOW it works then it's probably mumbo-jumbo. Even trying to get info out of some ppl as to what happened before the 'bricking' is like trying to get blood from a stone. Many of them simply don't understand why you want to know. If they fully understood the actual way the device works they could 'un-brick' it themselves anyway without help provided it's possible to be revived.Excellent info/tips. Need to be in future FAQ.



Likes: 




Reply With Quote

Bookmarks