Bricked Garmin Assist 51

**gibraltar** · 28th May 2025, 10:40 PM

**** FIXED NOW **** But still looking into the RTL Trap problem, which would cause the devices reset randomly and also produce distorted voice

1) Bricked device MODEL, Firmware version, HWID.
Garmin Assist 51

Code:

Please Login or Register to see the links

2) Why and how the device got bricked.

Set the device to Mass Storage Mode via the diagnosis menu, made a copy of what is in there, then formatted the device to exFAT.
The devices keep getting into RTL Trap and abnormal shutdown and was wondering if that would fix that. Replaced the battery already.

3) Symptoms: what's wrong in your device?
It can boot up to the Garmin screen, display the product model. Then in the copyright screen is just show the copyright c. (Before factory reset, it still display the map copyright information)

4) Does your pc sees your device ?
Yes and no, system mode does something. Can't get it boot into the storage mode again.

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
Did a factory reset by holding on to the bottom left corner of the screen then confirm the reset.

6) Do you have Garmin USB Drivers installed ? Garmin: USB Drivers Updates & Downloads
Yes

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
If that is the one from GarminDevice.xml

8) Write down if you already read and tried everything in these two threads: GarminCure3 tool - the new way to create cure firmwares for Garmin devices and How to unbrick a nüvi - step by step guide
Yet to try that, need to find the correct firmware.

9) Can you reach preboot mode? If no ,have you followed this? Garmin devices preboot mode
Yes

10) Probably no , but do you have NV backup?
No

11) Once you get a reply and a procedure to follow from our experts, please give an accurate reply about what you did and obtained results.

**Neil** · 29th May 2025, 12:29 AM

Read this thread for more information on how Runtime Liberty Traps occur: [Only registered and activated users can see links. ]

DriveAssist latest fw is V6.80 which you're using and was it released in May 2024 so Garmin should be aware of the problem and fix it in a later upgrade. You should try initially by clearing the non-volatile memory: [Only registered and activated users can see links. ]. Procedure will be the same as for nuvi 2xxx/3xxx series. If that doesn't help perhaps downgrading to V6.70 will solve it if the annoying re-starts keep happening for you. The only published charge from 6.70 to 6.80 was "Improved the display quality in junction view" so you could try using 6.80 without any JCV files loaded to check if it still occurs, although keep in mind it's likely not the actual files themselves causing the problem, it's when the firmware crashes encountering an unresolvable error.

Latest older fw i have for it is V6.20.

**gibraltar** · 31st May 2025, 04:13 PM

Tried the Nonvol memory reset, the problem still there.
Got another DriveAssist 51 running side by side, seems having the same issue. In few occasion it also reboot at the same time.
If you can send the older firmware over, would be greatly appreciated. Doesn’t seem like the link in Garmin working for older firmware.
Many thanks

**Neil** · 1st June 2025, 01:26 AM

Garmin removed all older versions from their public servers many years ago.

Note there's a gap in Garmin's Change History from V6.20 to V.6.6:

Spoiler:

The inference to be drawn is that there were at least 3 fw versions that were released only to be later withdrawn, V6.30 to V6.50. Garmin always deletes badly failed fw releases from its change log. If a proposed version fails internal testing it's not released generally and that's also the case if limited user testing is unsatisfactory, i.e. with "UAT" versions. So the next release following, say V6.20, is V6.30 as we would expect and we'd likely never even know of the failed Alpha, Beta or UAT version at all. Clearly on at least 3 occasions they've less loose faulty RTM versions in the recent past. Additionally, if you look at the earlier change logs there's been more such occasions because there are many other gaps:

Code:

Please Login or Register to see the links

My point is that going back to an earlier version will probably fix your current RLT errors but potentially might introduce other problems. My best guess is that there is some basic problem with the DA firmware that's eluded their efforts to correct, and the various band-aid solutions have not solved that or have fixed one problem and started another. As it's been a year since V6.80 they may well have now simply given up on it. Anyway, here's V6.20 for you to try if you want: [Only registered and activated users can see links. ]

I also have 3.40 and 3.50 and you might even be able to find others on the defunct Perry site via the Wayback Machine, for example:

Code:

Please Login or Register to see the links

**gibraltar** · 1st June 2025, 12:37 PM

Thanks for sharing that. Trying to get the device back into pre-boot mode again and not managing it well.
Had it in for less than a second, then failed again. Have two devices side by side still couldn't mange either of them. Wondering if I missed something.
It would be on top of the G and A, just G. Wondering if there are any option from the diagnosis menu may trigger the same result.

Many thanks.

[Only registered and activated users can see links. ]

**Neil** · 1st June 2025, 01:20 PM

Modern devices are notoriously difficult for everyday users to flash with an RGN file in preboot. It's now a real challenge to initiate a flash from Updater.exe. Because combined with the difficulty of first attaining preboot, it's then only held by the device for a brief period. Once a flash is actually initiated however it will hold preboot until Updater finishes flashing. Some older device could be triggered into preboot via the hidden menu behind the battery symbol, but Garmin removed that capability in later series. They really don't want us mere mortals messing with their devices 'under the hood' and limiting preboot availability helps achieve that.

You might be better off flashing individual fw BIN files using the ramloader (i.e. "boot.bin") as Ldr.bin to initialize TXT commands on a microSD card, read this: [Only registered and activated users can see links. ]. If you're not comfortable making an Sd flash kit yourself after reading up, then just ask and i'll make one for you ASAP when i have some spare time.

**gibraltar** · 2nd June 2025, 11:58 PM

Thanks! I am wondering if you also have an older copy of Garmin Assist 50 LMT-Dfirmware?

**Neil** · 3rd June 2025, 03:14 AM

Other than latest V5.90, i have only V5.40 for DA50 US/EU HWID 2270: [Only registered and activated users can see links. ]

If that version's not suitable, you may be able to find others on the Perry site archives i suggested earlier.

Thread: Bricked Garmin Assist 51

Thread Tools

Display

Bricked Garmin Assist 51

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions