Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 16

Hybrid View

  1. #1
    Important User How to get bricked 3597 into preboot to cure it?
    How to get bricked 3597 into preboot to cure it?How to get bricked 3597 into preboot to cure it?
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Certainly remove the file GUPDATE.GCD, whether you remove more files or re-format depends on the circumstances however I don't think you're understanding the basic process. Cure firmware cannot boot. It's designed that way so the device doesn't load any files like maps, POIs etc which might be stopping it from operating. It's put into a "stalled boot" state quite intentionally that it can be seen by a PC allowing the corrupt file/s to be removed or the internal file system formatted (formatting is only done should you not know which files to remove).

    So essentially you need to understand some basics:

    • It's 'bricked' because it can't load a file
    • The corrupt files/s must be removed
    • If it can't be seen by PC to remove the corrupt files/s directly then cure fw must be used so that it is seen by PC
    • If cure is used but you load back a backup which contains the corrupt file/s then nothing will change, when original fw is loaded it will still be bricked
    • If you have no idea what caused the 'bricking' or there are seriously corrupt files which have weird file names that can't be deleted then a re-format is necessary
    • Once the files have been removed or a format done then original fw can be loaded.

    It would be very helpful to know what you were doing just before it bricked. Had you just before updated firmware or maps, loaded new POIs or a voice or vehicle files for instance?

  2.    Advertissements


  3. #2
    Junior Member
    Join Date
    Jan 2018
    Location
    Dubai
    Posts
    8
    Rep Power
    0

    Default

    Hi Butters.

    It seems my reply last night went missing. Regarding what I did previously, I had updated my lifetime maps on my 3597 which had previously been patched. I bought it second hand. I had a second map installed on a micro sd card. After updating I couldn't see the map on the sd card. That's when I tried to patch the GPS to accept the map. I flashed a GCD file from the Garmin Cure3. After that it doesn't boot now. Only goes to the blue Garmin logo then switches off after a few seconds. I can see the files on the GPS and SD card in Windows Explorer. Any suggestions please?

    I removed the file GUPDATE.GCD as suggested but no difference.

  4. #3
    Important User How to get bricked 3597 into preboot to cure it?
    How to get bricked 3597 into preboot to cure it?How to get bricked 3597 into preboot to cure it?
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,466
    Rep Power
    1059

    Default

    Quote Originally Posted by alanuae View Post
    It seems my reply last night went missing.
    Probably you tried to post at the same time the previous posts were being moved here from the other thread.

    Regarding what I did previously, I had updated my lifetime maps on my 3597 which had previously been patched.
    How was it 'patched' any why? 3597's firmware doesn't have MSV presently so there's no need to patch with the [Only registered and activated users can see links. ]. It can simply use maps unlocked with latest gimgunlock.

    I bought it second hand. I had a second map installed on a micro sd card. After updating I couldn't see the map on the sd card. That's when I tried to patch the GPS to accept the map. I flashed a GCD file from the Garmin Cure3. After that it doesn't boot now. Only goes to the blue Garmin logo then switches off after a few seconds. I can see the files on the GPS and SD card in Windows Explorer. Any suggestions please?

    I removed the file GUPDATE.GCD as suggested but no difference.
    Don't put the GCD file back, it's not needed anyway. Maybe the map on the card is faulty. Remove the microSD card if it's still in the device, then flash the device with ORIGINAL (not patched and not cured) V5.50 firmware as an RGN in preboot and see if it boots. If it boots properly, turn it off and put the card back in to test.

    Report back and don't worry as we have plenty more to try in steps if that doesn't work. Don't forget to tell us in full detail what you did first before this happened.

 

 

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
  •