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
@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.
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
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.
Garmin_Drive_52_HWID3061_ver9.70 [Only registered and activated users can see links. Click Here To Register...]
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. Click Here To Register...]
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. Click Here To Register...]
Hi,
My Zumo 660LM seams dead. It doesn't do anything other then show a black screen. No sounds also.
I tried all to start up on battery which is fully loaded as I use one of my other 660. I tried on the bike-cradle as well.
Tried to push the power-on button long and short. Nothing.
So now I found Garmincure3 and want to give it a try. But I can't find the firmware anywhere.
MY 660 doesn't appear on the computer so I can't copy the firmware of my other 660 as well.
I need some help in how to make my computer find the 660. I use the Garmin USB drivers.
And I can also use any version of the firmware for my 660 or a pointer to where I can download it.
Arretje,
Garmin ZUMO 660 software version 5.10 - [Only registered and activated users can see links. Click Here To Register...]
To use Cure firmware (or original for that matter) the device MUST be capable of turning on. Likely you have a different problem due to a faulty hardware component anyway therefore any software remedy cannot help anyway, sorry.Quote:
Originally Posted by Arretje [Only registered and activated users can see links. Click Here To Register...]
Try removing the battery for a while, even overnight. Sometimes that will work to drain all residual current from the device and when reconnected to a power source it will liven up. If not, you will need an electronics technician to trace the fault but if it's the flash chip that's dead it won't be worth repair costs.