Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 10 of 10 FirstFirst ... 8910
Results 91 to 100 of 100
  1. #91
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    778
    Rep Power
    63

    Default

    @sledjunk
    Well that's an inconvenient but not unexpected result. You're right about the log being incomplete but only insofar as it's simply reflecting the flash being interrupted. The commands to delete the gupdate.gcd file from .System folder and dump region41 (the nonvol memory) were completed however the 14_BUP.bin file is just full of empty FFs (indicating the region is empty, also not unexpected) however this is where the flash has failed as region14 is 16MiB in size and only ~10Mib has been dumped before it's fallen over. My best guess is that when it's hit the damaged part of the region is when it's failed. It may turn on eventually left connected to an external source but i doubt it. You could also open it and disconnect the battery for a while, that may clear any rubbish in volatile memory.

    Unfortunately unless you can get it to power back on there is no chance for recovery however flash damage involving such a vital region is very hard to overcome anyway. There's likely no software fix available other than a very skilled programmer with intimate Garmin knowledge could conceivably remap the regions to exclude/ignore the damaged space, much like a few bad blocks can be isolated on a PC's hard drive or SSD. Otherwise only replacing the flash chip can restore it. That involves a lot of fiddly work as it's a BGA connection so the chip has to be carefully unsweated from the PCB and reballing is necessary when fitting the new one. Then it has to be reprogrammed. That's just not economically viable unfortunately anyway. [Only registered and activated users can see links. ]

    Sorry i can't help further unless you can get it to power up, but from hereon it's probably all academic due to the fact that flash damage has made itself clear.

    @Jonnay
    You can get the GCD file direct from Garmin:
    Code:
    Please Login or Register to see the links
    Use RGN_Tool ([Only registered and activated users can see links. ]) to make the RGN file and name it only 161301000400.rgn for safe flashing of either Cure3 or original firmware. You should try QuickCure3 first, it usually works ok and doesn't need the device's firmware at all. Still name it appropriately though. See here: [Only registered and activated users can see links. ] (Post #113).

  2.    Advertissements


  3. #92
    Member
    Join Date
    Jul 2015
    Location
    Ontario, Canada
    Posts
    12
    Rep Power
    0

    Default

    Thank you, Butters. You have been a great help in understanding the process, even if unsuccessful. All is not lost, At least I have a useable replacement screen and battery. I 'may' even try to extract the usb socket. As I mentioned earlier, i have multiples of these units, and even a couple of 'dead' ones due to the USB connector coming loose.

    Again, thank you for your time.

  4. #93
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    778
    Rep Power
    63

    Default

    My pleasure, i like mucking around with this stuff. When you open it up, please do consider my suggestion of leaving the battery disconnected for a while, an hour or even overnight to be sure. It may then power on again and we can try something else i've thought of. A very clever guy, user name kunix who made Cure3 and QuickCure3 also made a little known program he called 'gfwpack'. I guess that means Garmin Firmware Packer 'cos that's what it does. Reduces the size of a firmware. I think he did that primarily so as to enable a fw_all.bin which was too large to use in cross-flashing to modify another device's region14, because of the intended region's limited space.

    Now, looking at what was successfully dumped from your device, even though it seems that there is ~10MiB before the damaged area starts, clearly the flash of fw_all.bin was fritzed. The entire (healthy) region has 16MiB available as i also mentioned earlier, however current and recent fw_all.bin component is only ~9MiB but it isn't loaded to your undamaged area of region14 (maybe doesn't miss by much, but still ...). However, a compressed (packed) BIN file might load properly. I've been able to pack V5.90 fw_all.bin down to under 5.5MiB so ... it..might..work.

    Let me know if you can get it to liven up and if so if you want to try a last gasp attempt.

  5. #94
    Member
    Join Date
    Jul 2015
    Location
    Ontario, Canada
    Posts
    12
    Rep Power
    0

    Default

    Battery is disconnected now and I'll try it again tomorrow. Wish me luck!

  6. #95
    Junior Member
    Join Date
    Aug 2019
    Location
    Chile
    Posts
    2
    Rep Power
    0

    Default

    HI all...This is Ivan from Chile. Cannot find a working link to download GarminCure...do you have any?

  7. #96
    Pro-Member Grzegorz Kl's Avatar
    Join Date
    Mar 2017
    Location
    Poland
    Posts
    319
    Rep Power
    50

    Default

    Quote Originally Posted by imarinkovic View Post
    HI all...This is Ivan from Chile. Cannot find a working link to download GarminCure...do you have any?
    [Link removed]
    Link to other forum removed as contrary to this forum's rules. In any case the file is attached and has been downloaded thousands of time from the initial post of our thread [Only registered and activated users can see links. ].

  8. #97
    Junior Member
    Join Date
    Sep 2019
    Location
    England
    Posts
    2
    Rep Power
    0

    Default

    Downloaded garmin cure and updater OK, got the Garmin GCD file for my Nuvi 1490 OK and the 'Cure' will make a .rgn file, but when I press 'updater.exe' button I get an 'error - cannot run updater.exe file' with its path ( ERROR: can't run C:\GARMIN FILES\GarminCure3\updater.exe ) so I never get the dialogue box to choose serial or USB port etc.

    Have tried this in admin mode on a win7 and win10 PC - any ideas

    This is the full message I get in box on 'cure' after pressing 'make firmware' button

    Processing C:\GARMIN FILES\GarminCure3\nuvi13xxand14xxseries_GCDFile-MTK__630.gcd
    This is a GCD file.
    Patchable HWIDs: 1104
    *Processing HWID 1104
    Processing OK
    ERROR: can't run C:\GARMIN FILES\GarminCure3\updater.exe
    Last edited by wotsup; 27th September 2019 at 06:40 PM.

  9. #98
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    778
    Rep Power
    63

    Default

    @wotsup
    Just drag the RGN file manually onto Updater.exe and it'll load ok.

  10. #99
    Junior Member
    Join Date
    Sep 2019
    Location
    England
    Posts
    2
    Rep Power
    0

    Default

    Thanks for that, the updater screen now appeared and I could choose 'USB device' problem is the computer is not seeing the Nuvi, and if I hold top LH corner of screen after
    plugging in the Nuvi the screen remains perfectly blank for as long as I hold the corner with thumb, I did once get another dialogue box saying loading but it was greyed out
    and did nothing although I left it for ages. Also got another message 'no updates found' although .RGN, .GCD, updater.exe and cure all in same directory - main problem seems
    to be that PC does not detect the Nuvi as a USB device.

    My Nuvi 1490 boots up, sometimes says 'loading maps' and mostly goes to password screen, if it enter password PIN it goes to another screen and a green bar moves across lower part of
    Nuvi screen, sometimes a few mm, sometimes halfway, sometimes all the way, then goes back to password screen..........



    Do not quote previous post.
    Please read complete [Only registered and activated users can see links. ].

  11. #100
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    778
    Rep Power
    63

    Default

    Ok, it might just be that you don't have [Only registered and activated users can see links. ] loaded, that's needed to even connect in preboot. You can check if it's recognized in preboot by leaving Device Manager open on your desktop when you connect, it should show up under "GARMIN Devices". Also be very sure that your 1490 has HWID 1104 because the other possible HWID for 14xx devices is 0972. Connect it in preboot to check with G7ToWin or if you have a file system backup look at its GarminDevice.xml file found in the 'Garmin' folder. More info here: [Only registered and activated users can see links. ].

    Bootlooping bricked devices can be tricky to get into preboot, however once a flash is started they will usually hold preboot no problem. Best to have Updater.exe (or G7ToWin if checking HWID that way) already open and visible on your desktop so that you can quickly initiate the process. Then follow this:
    • Ensure the nuvi is completely OFF, you may need to hold down the power button for up to 10 or even ~30 seconds to force it off.
    • Plug a 'known-good' miniUSB cable directly into a REAR port of a desktop PC (USB2 only not USB3 and no hub or front port).
    • Hold the top LH corner of the nuvi screen while plugging the cable into it watching the app's GUI closely.
    • IMMEDIATELY the nuvi is recognized start the process and hold the screen until finished.

    If you miss it start again ensuring the device is OFF. Normally a healthy 1xxx device will hold preboot for about half a minute but a bootlooping device may drop it in as little as a couple of seconds so you'll then need to be very fast and also persistent.

 

 
Page 10 of 10 FirstFirst ... 8910

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
  •