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

Good result. Bootlooping devices are always difficult to catch preboot, persistence (and timing) is the key. However you didn't need to re-format it, GarminExpress was only asking you to update again because it reads the file named 'GarminDevice.xml' to determine whether updates are required. That file is only updated when the device reboots which yours couldn't do (cure firmware can't boot, that's by design), so the information on the XML file was old, i.e. from before it bricked. So in your case you needed only to load the original firmware after you updated with GE and let it boot normally to update the file.

You have no need to try the following now, but this may be helpful for others: A bootloop bricking may be due to an interrupt occurring when maps are being being loaded by GarminExpress or otherwise, the incomplete faulty detail map .img file cannot be loaded when the device is started. You can see this watching the screen, 'Loading Maps' appears and then the device shuts off and re-attempts to boot over and over. This bootlooping may seem infinite, but sometimes it's not. By putting the device on charge using a charge source like a AC>5v DC power pack (not a PC) with minimum of 1 amp output current and leaving it for an extended time it may eventually fully boot. Without powering it down, it can then be connected to a PC and the map reloaded using GE or MapInstall or simply writing over the problem map with a known-good .img file. No loading cure firmware or re-format is required if it can be seen in Mass Storage Mode by PC.

Originally Posted by Butters

By putting the device on charge using a charge source like a AC>5v DC power pack (not a PC) with minimum of 1 amp output current and leaving it for an extended time it may eventually fully boot.

Yes, but why?