Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 64 of 64 FirstFirst ... 1454626364
Results 631 to 637 of 637
  1. #631
    Junior Member
    Join Date
    Jul 2009
    Location
    Brazil
    Posts
    3
    Rep Power
    0

    Default

    Hey guys
    I have a Garmin Drive 52 stuck on the logo.
    HWID 3061

    I manage to enter in preboot, accessing with gps7towin to see the id, but as there is no firmware I cannot create the CURE.
    I was thinking of trying to use some LDR.bin from another firmware and try to delete the .img and .gpx that must be in trouble, or format the drive
    Does anyone have any ideas

  2.    Advertissements


  3. #632
    Important User GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    GarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devices
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,453
    Rep Power
    1057

    Default

    @rafaelroni
    Using a ldr.bin, aka boot.bin, from another device's fw is very risky and potentially will hard-brick it by writing an incompatible bootloader to region 5. It's not possible to know if a different device's ramloader (boot.bin) will be safe unless it's been tried and reliably reported so i highly recommend you not be the first.

    Drive 52 is identical to Drive 5 Pro in that they use the same firmware and share a HWID. I'm unable to personally confirm that their HWID is 3061 however if you've used G7ToWin correctly and it's reported 3061 then that's reliable.

    Do you have a file system backup of the device, even an old one? If so, it may be possible to use that to download the correct firmware from the Garmin server.

  4. #633
    Junior Member
    Join Date
    Jul 2009
    Location
    Brazil
    Posts
    3
    Rep Power
    0

    Default

    Thanks for the tip, I won't try to use the wrong LDR.bin.

    The problem is that Garmin is not distributing firmware or .gcd for this model.

    Do you have any idea how to solve this problem?

    I'm sure it's a wrong .gpx

  5. #634
    Important User GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    GarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devices
    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,453
    Rep Power
    1057

    Default

    You can try to re-enable Mass Storage Mode using QuickCure3 which is available towards the base of this thread's first post. It's universal and doesn't involve the actual device firmware at all, but it doesn't always work like Cure3 made from original fw does consistently. It's safe to try it because as it shouldn't make things any worse even if it doesn't work to restore MSM to allow file removal. However, if successful in removing the offending GPX files, you might still need to load the original (non-cure) firmware somehow afterwards if the device remains stuck on the start-up screen after you do. It should just boot normally though once you remove the known-bad files.

  6. #635
    Member
    Join Date
    May 2011
    Location
    UK
    Posts
    19
    Rep Power
    0

    Default

    Garmin_Drive_52_HWID3061_ver9.70 [Only registered and activated users can see links. ]

  7. #636
    Junior Member
    Join Date
    Aug 2023
    Location
    Thailand
    Posts
    2
    Rep Power
    0

    Default

    Nuvi 1490 hwid 972
    When I updated the firmware and turned it on again it stuck at the Garmin logo.
    First i try cure firmware and formatt NUVI drive and and copy something back and flash original firmware but still stuck Garmin logo
    anyone have idea?

    [Only registered and activated users can see links. ]

  8. #637
    Garmin/GPS Systems GMod. GarminCure3 tool - the new way to create cure firmwares for Garmin devices
    GarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devicesGarminCure3 tool - the new way to create cure firmwares for Garmin devices
    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    5,125
    Rep Power
    1465

    Default

    Perhaps when you copied "something back" you included the corrupt file which caused the initial bricking. Try loading Cure fw again, then removing some likely files that were placed on it during the update. The other possibility is the re-formatting you did doesn't suit the device, Garmin's proprietary OS is very particular about the way the visible memory can be formatted in FAT32. If you didn't use RMPrepUSB with the recommended settings then do again: [Only registered and activated users can see links. ]
    'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
    Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
    [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].

 

 

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
  •