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

Hi GPSPower community, I’m trying to revive a DriveSmart 60LM
1) Bricked device MODEL, Firmware version, HWID- DriveSmart 60LM, sw5.90, 2268
2) Why and how the device got bricked-I’m not sure, it was updated via GarminExpress,used only once and since then it got stuck on Garmin logo.
3) Symptoms: what's wrong in your device? – Continuos boot loop on Garmin logo, without any message related to maps.
4) Does your pc sees your device ? –Yes, but only in preeboot mode via updater.exe.
5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
-First, I have tried to update the software via “updater.exe”, version Drive,DriveSmart60_70,andDriveTrack70_590.gcd. The update was sent from PC succesfully but no response from device, it didn’t boot up.
-Then I’ve used “garmincure3” to make cure firmware but it ended just like my first atempt and mass storage cannot be triggered.
-Downgrade via garmincure3 (cure or official) to 580/570/etc but everytime the connection is lost after the update process starts, the device ID disapear from “updater” USB field and throws an error.
- Custom SD flash kit v 590 on a 2 GB card (formatted FAT32&FAT) then on a 32GB FAT32 but it refuses to read the data, "Loader" message does not show up.
6) Do you have Garmin USB Drivers installed ? – Yes.
7) If you don't know HWID get it by – G7ToWin shows HWID 2268
10) Probably no , but do you have NV backup? – No, I don’t have NV backup unless this can be found somewhere inside GarminExpress folder but I don’t think any backup (previous content) was made during GE official update.
Many thanks in advance!

Originally Posted by originallvu

..........
4) Does your pc sees your device ? –Yes, but only in preeboot mode via updater.exe.

It's normal for a bricked device to not have Mass Storage Mode available.

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
-First, I have tried to update the software via “updater.exe”, version Drive,DriveSmart60_70,andDriveTrack70_590.gcd. The update was sent from PC succesfully but no response from device, it didn’t boot up.

You cannot flash a GCD file in preboot via Updater.exe. You can only flash an RGN file that way. Regardless, flashing original firmware will achieve nothing.

-Then I’ve used “garmincure3” to make cure firmware but it ended just like my first atempt and mass storage cannot be triggered.
-Downgrade via garmincure3 (cure or official) to 580/570/etc but everytime the connection is lost after the update process starts, the device ID disapear from “updater” USB field and throws an error.

Modern devices like the Drive series stay in preboot for a very short time, only a matter of seconds. However if a flash is successfully initiated the device will remain locked in preboot until the flash finishes.

- Custom SD flash kit v 590 on a 2 GB card (formatted FAT32&FAT) then on a 32GB FAT32 but it refuses to read the data, "Loader" message does not show up.

Forget using a microSD to flash anything while it's bricked like that. Regardless the 'Custom SD Flash kit" is probably to flash BIN files modified by Uiversal Patcher and it's NOT what you need. A boot-looping device is unlikely to have its firmware invoked sufficiently to execute Ldr.bin anyway.

This is what you need do:
1. Make Cure3 firmware RGN. Name it ONLY 226801000590.rgn because any other naming is potentially unsafe. You might like to try QuickCure first, it doesn't involve the firmware at all and might work to restore MSM. Scoll down to the base of the initial post here: [Only registered and activated users can see links. ] and look for it.
2. Whether you use full cure fw or quickcure you must flash it as an RGN named appropriately using Updater.exe in preboot.
3. Rather than putting your device in preboot first, get everything set up with 226801000590.rgn loaded into Updater.exe leaving the GUI visible on your desktop. Connect a "known-good" USB cable to a REAR USB2 port of the PC (avoid using USB3).
4. Position your left thumb in the proper position on the device screen to attain preboot, first ensuring the device is fully OFF (you may have to force it off by holding the power button down for anything from 10 to 30 seconds).
5. Watch Updater's GUI and plug the USB cable into the device. IMMEDIATELY you see the device's detail appear in the window next to 'USB Device' click 'OK' on the GUI or just hit the Enter key on your KB. Hold the screen until the flash completes.
6. If you fail then start again all over, steps 3, 4 & 5. Persistence pays with a bricked device.

The device will stop bootlooping when cure fw is loaded and you will have access to the file system in Mass Storage Mode to delete any corrupt file/s or if necessary re-format it correctly with RMPrepUSB.

@Butters,thank you for your reply! The thing is that although I've tried so many times to proceed as above mentioned, the device still doesn't respond on any of the CURE firmware RGN. If I flash "QuickCure" or any other CURE.rgn made from previous SW than 590, the device is always disconnected 1-2 seconds after I hit the Enter key. The only RGN which keeps the device locked in preboot until the flash finishes is the one made from sw 590 but even so the device starts without Mass Storage Mode.Regardless the USB port used for this procedure, desktop PC or laptop, the result is the same.