Thread: New GPS - how to use old maps off of SD Card

It's not the "omission" that I'm talking about. It's knowing the consequence but still doing it. Then using a policy made for quality control to fix a problem that ones had caused. While I have not worked at Garmin (I was asked by in-law just the other day if I wanted to; I said, hell no.) But I do know how support groups work (for a different product line) A "defective" item is received, it is checked (and not just blindly fixed/replaced) for the reason of the problem (because they keep track of this info). Then it is fixed or replaced (not necessary with the same original device.) Later, another group (usually Quality control) looks at the data (of the defective product if any) and if they find a reason to, they will request an investigation (then it's not hard to know that it's a hacked firmware) Company often don't ask question before replacing (if within the warranty period) because they don't want to burden the owner of the product. This doesn't mean they don't investigate why the problem exists by looking at the defective product afterward.
I believe what you are saying is investigate before replaced and what I'm saying is post mortem investigation.

I wasn't specifically referring to Garmin finding the bad .img, but whether anyone has a unit "broken" because of a bad .img (I didn't see any posts on that in the forum) Not trying to be difficult, I'm just curious.

Who knows if it's LifetimeUpdater or not. It was just a real bad experience that I just wanted to forget

Actually, I don't fully understand the "mumbo-jumbo" myself sometimes; I'm good a depth knowledge, but you seem to be good at breath knowledge. Remember, most people looking for answer are user of a (singular) product not someone who work with (or have accessed to) many different products. The problem is that even if they learned how to do it, they don't often do it enough to remember what they did if the problem occurred again. If I stop working on my codes for a couple of months, I will have a hard time understanding what I did and has to spend time familiarizing myself.

I do have a question: You mentioned when a unit "bricked" it goes into preboot mode. I thought (from what I read) you have to press certain region of the screen for a specific amount of time (or plug/unplug USB connection at right time) depending on what device it is. Not a trivial thing to do or remembered.
Another question: I had to charge nuvi760 and nuvi200 with USB cable, why can't I turn the units off while it's charging?