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

It's the files named Express.log or Express_**.log which disclose the HWID as shown in the image in my last post above yours.

You should have at least one so named, they'd be listed above your "ExpressDetailed" LOG files. These are my recent GE LOG files:

Spoiler: click

[Only registered and activated users can see links. ]

There's always the possibility that although you've found "nuvi13xxand14xxseries_GCDFile__630.gcd" file in the ExpressDetailed log file, and clearly it's the non-MTK firmware by its naming and therefore HWID 0972, that the log may actually be for your other 13xx device. It's absolutely imperative that the original HWID is identified so look again in the Express folder for the files named only Express/Express_**.log and check it/them. Those files will also list the device's Unit ID (UID) in several places, so as an additional check search for "Getting sync upload settings for device" which will show you the first instance of the device's UID in the file, like this for my nuvi 55:

Spoiler: click

[Only registered and activated users can see links. ]

Check that UID against the UID that you found in G7ToWin after the bricking:

Spoiler: click

[Only registered and activated users can see links. ]

Then there'll be no doubt which of your 13xx devices was last updated. It also means if the UID in the log file matches with G7ToWin, which has shown the present HWID as 0972, but in fact the Express log actually shows you'd used nuvi13xxand14xxseries_GCDFile-MTK__630.gcd firmware for 1104, that a cross-flash has somehow occurred when using cure fw.

There are entirely different recovery procedures to attempt depending on whether it's been cross-flashed or not you see. In fact it will likely be far more feasible to recover if it's been cross-flashed because otherwise the original symptoms are probably due to a hardware failure rather than a corrupt file. That's given the inability of Updater.exe to completely finish writing to at least one flash region.