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

V2.20 is the latest version of patcher. V1.30 is from about 4 years back but should still work to patch fw_all_bin of V6.30 as i think the global rules in defs.txt apply to it. If you want to be sure it's properly patched, google for "Garmin Universal Firmware Patcher V2.20" as this forum's rules forbid posting it here.

Check the charger you're using has sufficient amperage to both power the DriveSmart and charge its battery simultaneously. If you're using the original 12V vehicle charging cable that'll work because it has 5V 2A output. If it's only a 1A PSU it may not both change and it power on. Regardless, certainly if the battery has been totally drained there may be a delay even with a 2A charger as there needs to be a safe level of charge before the device can be powered up. Depending on device, from dead-flat it may or may not power itself on without you using the power button once there's sufficient change in the battery.

No there's no need to write the HWID into the RGN file and your naming of it is correct for safe flashing.

Hello all, I have a garmin 920xt that got bricked some time ago during a firmware update through garmin express (I think the craddle's usb cable was not in a very good condition and stopped working half way).

1) Bricked device MODEL, Firmware version, HWID.
Garmin 920XT, I don't remember the exact firmware version. I tried g7towin to get the HWID but even in preboot mode a get USB Error: WaitComplete: Error waiting for ERROR_IO_Pending

2) Why and how the device got bricked.
Updating firmware through Garmin express and getting disconnected half way through it

3) Symptoms: what's wrong in your device?
It stays in the logo screen forever

4) Does your pc sees your device ?
If I press the upper arrow button then it's shown in the device manager but not as a Mass Storage. Updater finds it (preboot) and even shows its ID.

5) List all the procedures you already tried to unbrick it and their results and errors messages obtained.
Downloaded the latest firmware 9.90 from garmin and tried the GarminCure3 tool to create a cure. The tool fails with an exception: XRgn::DetectHWIDandSWVER(): ramloader has invalid format

6) Do you have Garmin USB Drivers installed ? Yes, the 2.3.12 version

7) If you don't know HWID get it by Use program G7ToWin to retrieve your HWID
It doesn't find the gps

8) Write down if you already read or tried GarminCure3 tool - the new way to create cure firmwares for Garmin devices
The tool fails with an exception: XRgn::DetectHWIDandSWVER(): ramloader has invalid format. Also tried the QuickCure3.rgn file with updater but it wasn't compatible with my device.

9) Can you reach preboot mode? Yes, by pressing the upper arrow button (on the top right) and putting the device in the craddle holding it. It stays in preboot while I press the button.

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

Many thanks

@Taikeido
The unit/device main software, aka "firmware", for Garmin's Forerunner 920XT and probably other watches quite differs from their usual structure. In the case of the Forerunner 920XL, it's in RGN format rather than wrapped in a GCD file. Of course that in itself is not unusual at all particularly in their older navigational devices all of which used RGN files often wrapped as an EXE file. GCD files are basically RGN files with an additional header to allow the extraction of the file by the device itself to update it's firmware.

Where your 920XT is unusual is that Garmin's supplied RGN file seemingly is "an RGN within an RGN", and when that underlying file is saved then compared to the supplied file they both contain only one BIN file (fw_all.bin), the main system software for region 0E (decimal 14). There is no boot.bin present (actually it's the ramloader and not a bootloader) which is contained in a 'normal' RGN file. I suspect that the supplied RGN file, which has an additional header somewhat like a GCD file, is made like that so that it can be handled by GarminExpress which usually does not process the more-common 'normal' RGN files. That's because GE connects to devices in Mass Storage Mode/Media Transport Protocol rather than Garmin Mode/Preboot Mode. The latter modes being used, for example, by Updater.exe to flash a 'normal' RGN file's BINs directly to the relevant Regions of devices' flash memory. Now GarminExpress does things quite differently, it places a software update file appropriately in the device's GARMIN folder and then on the next boot-cycle the device itself deals with the file and updates the relevant region(s) accordingly, exactly as Updater.exe does directly in preboot. Aye there's the rub, to quote Hamlet. Because to remove the corrupt update file from the device we need Mass Storage Mode and to re-gain that in a soft-bricked device we usually modify the ramloader (boot.bin) using Cure3 or some other method but there is no boot.bin as such. I am quite certain what's preventing your device from booting is that the update file was only partially transferred to the device by GE but is indeed present in the Garmin folder as 'gupdate-990.rgn' or similar name albeit incomplete. The device detects it but stalls on the logo splash screen trying to extract the file. The solution is to remove the corrupt file or overwrite it with a healthy one but i don't know how to do that with certainty or with therefore absolute safety without access to the ramloader to modify it.

I'm now guessing from hereon so you will be proceeding entirely at your own risk, however i think that you may be able to flash the 'underlying' RGN in preboot using Updater.exe safely despite that there is no conventional ramloader present in the firmware. That of course would not 'un-brick' it because the corrupt update file will still remain in the Garmin folder and will be detected again on the next boot attempt. However if you modify the appropriate reference to RGN internally to change that reference of 'RGN' in it to something else, say, XGN for example, and then flash that modified file with Updater.exe you may be able to get MSM back because hopefully it won't look for the update file on boot. That's how Cure3 firmware works, by modifying common file names such as IMG, GPI and importantly GCD to other names so they are not initialized on start. In this case we are only concerned with a specific update file with ".rgn" extension rather than with ".gcd". To do that modification you should obtain the file "Forerunner920XT_990.rgn" from the following coded link:

Code:

Please Login or Register to see the links

Then open Forerunner920XT_990.rgn in RGN_Tool (extract attached ZIP below) and press the 'Save' button in the first section to save the underlying RGN file:

[Only registered and activated users can see links. ]

It will prompt you to save the file as "fw_all.bin" so change both the file's name and its extension to "test.rgn". Open test.rgn in a Hex editor and search for GUPDATE in plain text which is 47 55 50 44 41 54 45 in hexadecimal. There should be only one instance of it which is followed by "RGN" (52 47 4E) so use the edit function of the editor to change that single instance only of RGN to XGN (58 47 4E) then save the file as cure.rgn or something else convenient. Read more here on making cure firmware the 'old-fashioned' way: [Only registered and activated users can see links. ]. In your case you are only concerned with the one single file, named GUPDATE.RGN or similar.

If you want, although a little pointless in this case, you can change the file's name from cure.rgn to the 'safe-naming' of 176501000990.RGN before flashing with Updater.exe in preboot. Hopefully after flashing even though the watch will still stick on the logo splash screen it will have Mass Storage Mode re-enabled and you can remove the corrupt GUPDATE.RGN file from the GARMIN folder. You can then flash the original firmware back to allow it to fully boot.

Remember, this is all at your own risk. If you need help making the cure RGN i'm happy to do so, just ask.

@Laolay G
That device runs a version of Android rather than the Garmin proprietary OS.
No method of 'curing' Garmin's Android firmware has yet been found or made publicly available.

@Arva
I can only offer the same advice given to Taikeido in Post #308 and it seems you've already attempted to flash the underlying RGN, resulting in that error message, but using a cure fw.

About preboot mode: Your device has defaulted to preboot/boot block/garmin mode or it would not be visible in Device Manager. Most devices which have a faulty 'unit software' (firmware) will indeed default to that mode as your fenix has done (sometimes "System Software Missing" or similar message is displayed on the device screen).

Usually a 'soft' bricking occurs immediately after a firmware or files update, meaning it happens at the very next boot attempt after the update. If such a bricking is caused solely by firmware, it can usually be fixed by simply re-flashing an original (NOT cured) fw to overwrite the corrupt data and without actually having to follow a process to access preboot because it's already in that state.

Unfortunately, suddenly failing like that in normal operation can be strongly indicative of a hardware failure rather than a firmware problem (i.e., a 'hard' bricking, not repairable by software methods). Usually that's due to flash memory damage, not effectively repairable by users.

The error message you received can also be because the device/pc connection was lost, even momentarily:
* Try another USB cable, more than one if several are available;
* Re-read the suggestions in Post #308 to be sure to make the RGN fw file correctly, and,
* Be persistent in trying to get it to flash, it may take numerous attempts to flash a flaky device which moves in an out of preboot.