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

Dealing with your second para first: It's actually quite common to find devices bricked because of a bad map. The logo splash screen stuck on 'Loading Maps' message is an indication of a faulty img file that cannot successfully load. If the img is on a card then removing the card lets the device boot normally. Otherwise it has to be 'cured', by loading a modified firmware like kunix's Cure3/QuickCure firmware or one that's individually made by modding it in hex editor to change .img to .xmg; .gpi to .xpi; etc. to bypass loading them. That allows the device to be browsed in MSM but it still won't boot of course with Cure3/QuickCure loaded. The offending file(s) can then be deleted, or the internal file system gets properly reformatted if necessary. For the device to then be able to boot normally the original firmware is loaded along with only 'known good' files. That process by definition will technically void the warranty also but it's done regularly by knowledgeable users all the time rather than suffer returning a device to Garmin for warranty replacement. So what Garmin loses on the merry-go-round they likely more than pick up on the hurdy-girdy. I've personally saved them from numerous warranty claims by curing devices and I've never once sent back a device bricked thru my own fault. They are quite likely aware that a percentage of warranty claims are caused by user mis-adventure via clumsy firmware manipulation however may also be aware of efforts by more skilled users to save them other claims.

Back to the 'moral' question of not disclosing that a device was bricked by clumsy firmware modding, I think we're on the same page or at least on adjoining ones in theory. Also you're correct that they'll look after the event but I believe only if there's a strong suspicion about the cause. My point too is if they don't ask for all the details upfront it's probably because they are prepared to accept a small percentage of 'fake' claims, much like an insurance company will because it's not commercially viable to chase down the dud claims as to do so thoroughly they'd need to investigate all claims and that's costly. What I think Garmin and other large firms do is look for repeated faults in the same or related products. If they have a systemic problem they want to move quickly to sort that out. Every now and again they'll accidentally release a faulty firmware version which might make devices misbehave or even freeze. When they identify that they'll remove the bad firmware from their servers and issue a replacement. You can see that's likely happened by viewing Change Logs, when a jump in firmware versions shows e.g. say V3.50 is issued but is quickly replaced by V3.60, the history then shows 3.40 followed by 3.60 and all reference to 3.50 disappears quietly. Just as quietly they'll replace or fix the problem devices with 3.50 on-board, no big fanfare at all in fact not even a public announcement or apology usually.

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.

No, what i said was only in regard to a device which shows 'System Software Missing' and it's an indication that a wrong or corrupt firmware has been flashed to region 14 (the main system software which is fw_all.bin component of a firmware file). The device will then usually default to preboot mode by design. In any other case, such as stuck on logo because of a bad file not loading, you need to get it into Mass Storage Mode and firstly need to load cure firmware to attain that. To load the cure firmware you need preboot and that won't be defaulted to (other than in very old 'region-only' devices which don't use MSM) so you have to hold the screen in the proper place while turning on. Your 760 would have been a b*tch to get into and hold preboot, the position to hold the screen is different to most and they stay in preboot for only about 10 seconds then move to the white calibration screen if a flash isn't commenced. Fortunately if not bricked they can enter preboot by holding the battery symbol for ~6 secs to access a hidden menu with 'SW Ver' as the first page. In that state preboot not MSM is the default connection mode for all 7 and 2 series and many others like 1xxx etc. and it's held perpetually while the device has charge. If then connected to PC it shows only in Device Manager under 'GARMIN Devices' and is seen by Updater.exe normally.

Another question: I had to charge nuvi760 and nuvi200 with USB cable, why can't I turn the units off while it's charging?

You mean connect it to a PC with a data cable to charge? In that way it's connected in MSM with the PC tower symbol showing as well as being charged. You can force it off by holding the power slide to the left for ~10 secs but it'll turn right back on so it's effectively a restart. If you use a charging-only cable with no data wires it may try to go to MSM briefly then boot up normally. There are ways to make a USB cable that acts like a Garmin car charger. A couple of threads for you (you're welcome :
[Only registered and activated users can see links. ]

Code:

Please Login or Register to see the links