Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

Thanks, I did it!
My mistake was exactly renaming the HWID
Cheers!

Originally Posted by dejavuei

Thanks, I did it!
My mistake was exactly renaming the HWID
Cheers!

Not necessarily that for absolute certainty, usually adding the correct HWID shouldn't affect it but the problem may have been due to the firmware manipulation at some point. Regardless, leaving '0000' is safe for sure. Glad you're sorted anyway, cheers.

1) Bricked device Garmin 465T, Firmware version, HWID 943

2) Got it from the Garage sale

3) Symptoms: The device has a Garmin logo Boot Loop

4) Does your pc sees your device : Only when is flashed with the "Cure" firmware

5) The Pre Boot mode works and the device can be flashed:Tried 4 different Firmware revisions included the last one 4.2.
Quick qure was able to set the device to USB mass storage. I tried to format the memory as NTFS recover back to FAT 32 using RMPrepUSB.Tried with absolutely no data on the internal memory and with original data,no luck.The Garmin never makes Garmin Device .HTML when the data is deleted.
When is flashed with the "Cure" Firmware stays connected to the PC ,but when I Flash it back to the Original Firmware keeps doing the same thik:Garmin Logo boot loop.
Have no NV backup.
I`m running out of options.Recently the friend of mine brought me a 2757 with almost the same symptoms,the only difference is that the quick qure does not help at all and the preboot mode works intermittently.
Any suggestions?

Not sure why you'd want to format the 465T as NTFS before recovering to FAT32 but that wouldn't have been harmful in all likelihood.

So, are you saying the device has not been formatted at all or it has but hasn't been formatted by RMPrepUSB? It might only seem empty and there's something still there not obvious maybe because you don't have folder options in Windows set like this:

[Only registered and activated users can see links. ]

About the 2757, it may have a damaged USB socket if it only can only enter preboot intermittently. Try other USB cables. Are you sure QuickCure was loaded? Regardless, sometime it doesn't work and you need to use Cure3 made from the actual device firmware. You really need to have consistent and reliable preboot access to load an RGN file anyway.

I have tried to format it in NTFS ,because I ve seen some damages on internal files which do not allow to the system to boot up normally.My computer shows the hidden files by default,so nothing left I'm pretty sure....

It clearly has very serious corruption but provided that's only in the visible file system (region 48) and not in some other essential region like 41 you should be able to recover it. Try again with RMPrepUSB and if it still fails to format it in FAT32 try with Low Level Format Tool:

Code:

Please Login or Register to see the links

Perhaps even MiniTool or EaseUS free partition managers can handle it. Then afterwards you can do the format again properly with RMPrepUSB so that it's acceptable for Garmin's OS. There's more than one way to skin a cat (or format in FAT). Garmin devices formatted in windows are often problematic and if done with a mac inevitably give trouble.

The Low Level format tool did not help either.Proceeded ,completed,formatted back with RMPrebUSB,the same result-Flashing Garmin logo for a second or two and reboots by itself....

When Cure firmware is properly loaded and there are no other problems with the device, it should simply stick on the logo screen indefinitely. Do you mean it goes back to a boot-loop when you loaded original firmware after the format?

@GEOMAPIX
If your 1390 is a US/EU firmware device then it has either HWID 0972 or 1104, not 0951, be sure to use the correct firmware for it. You cannot access any of the devices folders or files in preboot, only in Mass Storage Mode. Using Cure3 modified fw restores MSM. Most likely the map you were using when it bricked was corrupt, if that's been overwritten when you used GarminExpress to update it then there should be no further problem AFTER you now load original firmware (Cure fw cannot boot the device, that's the whole point of it .... it stalls the boot so corrupt files aren't loaded, allowing MSM access to remove them). Read this to fully understand the process: [Only registered and activated users can see links. ].