Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 3 123 LastLast
Results 1 to 10 of 26
  1. #1
    Junior Member
    Join Date
    Sep 2017
    Location
    Canada
    Posts
    1
    Rep Power
    0

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

    I just upgraded my old Nuvi 1690 to a new Nuvi 58LM. None of my old maps from my SD card no longer work. The first error is that it " Cannot unlock maps ". The second error is that the " Maps are corrupt and cannot be used. Go to [Only registered and activated users can see links. ] to download the latest maps."

    I ran the Protected Garmin file toolkit_2254_x64 on one of the maps and the result is below.

    Seems to be a good IMG File as signature 'DSKIMG' was found...
    I00009BC.TYP Found Updating IMG information
    --> CP 1252 (0x04E4) Found ..
    --> FID 2492 (0x09BC) Found ..
    --> PID 1 (0x01) Found ..
    --> RgnID 0 (0x00) Found ..
    --> VenID 0 (0x00) Found ..

    Finished to analyze the file !

    This IMG File is not locked !

    How do I use my old maps on my SD card with this new GPS ? Thanks in advance for the help....

  2.    Advertissements


  3. #2
    Pro-Member Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    220
    Rep Power
    1

    Default

    You need to patch it's firmware: [Only registered and activated users can see links. ]. Also the unlock engine in PGFT is old, you may need to additionally use gimgunlock-0.04.exe to effectively unlock the maps. Google for it, it's no longer available on this forum.

  4. #3
    GPSPower Helper New GPS - how to use old maps off of SD Card
    New GPS - how to use old maps off of SD Card
    dasilvarsa's Avatar
    Join Date
    Feb 2011
    Location
    Global
    Posts
    1,132
    Rep Power
    359

    Default

    Buy the Map if you really need it.
    It's dangerous to patch a unit that is still under warranty. For that matter it is dangerous to patch any unit.
    I sit @ the moment with 2 bricks.
    You can also use free maps from here [Only registered and activated users can see links. ]
    The difference between stupidity and genius is that genius has its limits.
    Albert Einstein.

  5. #4
    Important User New GPS - how to use old maps off of SD Card
    New GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD Card
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,455
    Rep Power
    542

    Default

    I agreed with dasilvarsa, patching map .img is relatively safe but patching firmware is risky. If you like/use your new unit a lot, you need to invest in maps for it. If you can't afford to pay for maps update, get a unit with LTM. You pay little more at front, but the maps are free afterward (assuming you can get Garmin silly updater to work)
    Last edited by osiris4isis; 22nd September 2017 at 04:43 PM.
    Do not PM me with questions. That's what a forum is for.

  6. #5
    Pro-Member Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    220
    Rep Power
    1

    Default

    Quote Originally Posted by dasilvarsa View Post
    It's dangerous to patch a unit that is still under warranty.
    Quote Originally Posted by osiris4isis View Post
    I agreed with dasilvarsa, patching map .img is relatively safe but patching firmware is risky.
    Guys, I respectfully disagree with that. Garmin will replace a bricked device under warranty immediately. They don't raise questions unless you are silly enough to say you've been mucking around with it's firmware which does of course void the warranty.

    If you do 'patch' a map, i.e. unlock an img file, then having it on the device might in fact cause a problem should it get sent back to Garmin under warranty or not. Putting unofficial maps on a media card is totally safe as any problem caused by that can be reversed by the user. Even if such a map was badly corrupt and caused the device to 'brick', the problem's resolved by simply removing the card.

    ........ For that matter it is dangerous to patch any unit.
    I sit @ the moment with 2 bricks.
    Then post about them if you're stuck, we can help to un-brick if they are only software bricked.

    Quote Originally Posted by osiris4isis View Post
    .... (assuming you can get Garmin silly updater to work)
    Do you mean Garmin MapUpdater? It's only been left available to service older LM devices that don't have a visible file system (the region-only types without MSM). It usually won't supply the most recent maps to modern LM device but GarminExpress will. Although GarminExpress started off as a flaky bit of , it's now been refined to the point where it's quite usable and reliable but initially I reckon they released it as a deep Alpha version, at the time I had less bugs around my back porch light. In proportion, it did brick far more devices early on than Big-Bang's firmware patcher or any other unofficial manipulation ever did, although to be fair many were 'bricked' because ppl got frustrated with GE and unsafely disconnected devices while they were being updated which resulted in corrupt files, i.e. very easy to 'de-brick'.

    To my knowledge there's been no posting of a permanent bricking in the patcher thread. Provided ppl follow the cautions and tutorials there is no problem flashing patched firmware. The BIG concern would be if a wrong boot.bin is used rather than an incorrect or corrupt system firmware as flashing wrong Boot BLK and X-Loader can hard-brick any device. When patching a GCD file, only fw_all.bin is patched (the main system software). That's what is contained in region 14 (0x0E). All other components of the GCD file are untouched. Flashing a wrong firmware to rgn14 can usually be easily reversed by flashing the correct BIN file as an RGN in preboot mode. In fact there's usually no need to even have to attain preboot as the device will show 'System Software Missing' message on attempted start-up and default to preboot mode itself.

    In short: Bricking by a corrupt file (usually .img or .gpi or .vpm) is super-easy to fix. Bricking by an incorrect or corrupt 'system software' flashed to rgn14 is very easy to fix usually. Bricking by a wrong boot.bin/Ldr.bin can be permanent and literally result in a 'brick' (but not always).

  7. #6
    Important User New GPS - how to use old maps off of SD Card
    New GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD Card
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,455
    Rep Power
    542

    Default

    Quote Originally Posted by Butters View Post
    Guys, I respectfully disagree with that. Garmin will replace a bricked device under warranty immediately. They don't raise questions unless you are silly enough to say you've been mucking around with it's firmware which does of course void the warranty.
    Well, I'm the first to say that I'm no "angel" but isn't that deceptive/immoral action? It's like buying an item, and you FUBAR it when Garmin warns you before hand not to do it and then sending it back to get it fixed for free (this of course if it's still under warranty) I can see it now, a bunch of new model of Garmin unit arrive in tech support/repair group. They investigate and found firmware was bogus. They started looking around in forum and found out why. Then of course the consequences follows.

    Quote Originally Posted by Butters View Post
    If you do 'patch' a map, i.e. unlock an img file, then having it on the device might in fact cause a problem should it get sent back to Garmin under warranty or not.
    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.

    Quote Originally Posted by Butters View Post
    Do you mean Garmin MapUpdater? It's only been left available to service older LM devices that don't have a visible file system (the region-only types without MSM). It usually won't supply the most recent maps to modern LM device but GarminExpress will. Although GarminExpress started off as a flaky bit of , it's now been refined to the point where it's quite usable and reliable but initially I reckon they released it as a deep Alpha version, at the time I had less bugs around my back porch light. In proportion, it did brick far more devices early on than Big-Bang's firmware patcher or any other unofficial manipulation ever did, although to be fair many were 'bricked' because ppl got frustrated with GE and unsafely disconnected devices while they were being updated which resulted in corrupt files, i.e. very easy to 'de-brick'.
    Whatever that was needed to do a map update for nuvi765 LM; I remembered going through a lot of pain trying to do it on WinXP and finally gave up.

    Quote Originally Posted by Butters View Post
    In short: Bricking by a corrupt file (usually .img or .gpi or .vpm) is super-easy to fix. Bricking by an incorrect or corrupt 'system software' flashed to rgn14 is very easy to fix usually. Bricking by a wrong boot.bin/Ldr.bin can be permanent and literally result in a 'brick' (but not always).
    Excellent info/tips. Need to be in future FAQ.
    Last edited by osiris4isis; 23rd September 2017 at 02:31 AM.
    Do not PM me with questions. That's what a forum is for.

  8. #7
    Member + New GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD Card Grizzzly's Avatar
    Join Date
    Apr 2017
    Location
    VIP Cemetery
    Posts
    74
    Rep Power
    6

    Default

    Quote Originally Posted by dasilvarsa View Post
    Buy the Map if you really need it.
    It's dangerous to patch a unit that is still under warranty. For that matter it is dangerous to patch any unit.
    I sit @ the moment with 2 bricks.
    Sorry! But for me WebUpdater, MapUpdater and Express are in top of chart for bricks and problems! Despite to what I have LMTs but I was never use units directly now. Is there any difference with firmware patching? I think no if you know what you do. Do not know? Investment in learning be affordable because it is only reading of forums within a couple of evenings. The cost of map which is using for one or two trip is more expensive. I guess the man must decide for himself - buy or steal! In any case Garmin obtain a compensation with purchase of new device instead of those that broken by patch of firmware
    P.S. I loved former GpsPower. It was platform for discussion and investigation. Now I see only hunters for advertisement bonuses on other forums. Sale or purchase of stolen goods is really absolute evil!

  9. #8
    Pro-Member Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    220
    Rep Power
    1

    Default

    Quote Originally Posted by osiris4isis View Post
    Well, I'm the first to say that I'm no "angel" but isn't that deceptive/immoral action? It's like buying an item, and you FUBAR it when Garmin warns you before hand not to do it and then sending it back to get it fixed for free (this of course if it's still under warranty) I can see it now, a bunch of new model of Garmin unit arrive in tech support/repair group. They investigate and found firmware was bogus. They started looking around in forum and found out why. Then of course the consequences follows.
    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.

    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.
    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.

    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.
    That would probably have been Garmin LifetimeUpdater. Useless soft and never worked properly, eventually was withdrawn thank goodness.

    Excellent info/tips. Need to be in future FAQ.
    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.

  10. #9
    Important User New GPS - how to use old maps off of SD Card
    New GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD CardNew GPS - how to use old maps off of SD Card
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,455
    Rep Power
    542

    Default

    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?
    Last edited by osiris4isis; 23rd September 2017 at 05:14 AM.
    Do not PM me with questions. That's what a forum is for.

  11. #10
    Pro-Member Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    220
    Rep Power
    1

    Default

    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
    Last edited by Butters; 23rd September 2017 at 06:57 AM. Reason: messed up linked threads.

 

 
Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.