Well, it's quite a co-incidence that you connected to WebUpdater while it still had Cure3 fw loaded. That's re-downloaded a new healthy gupdate.gcd, thus overwriting the corrupt .gcd loaded by GarminExpress. Then when you loaded original fw made by Cure3 in the form of an RGN file it's been able to boot fully because the actual cause of the 'bricking' had been removed. The same result would have occurred had you simply connected to PC and removed the damaged GCD using Windows Explorer. It's important to note a very relevant point, which is that Cure3 fw CANNOT boot the device and in fact that's the entire purpose of it. It prevents any files (bad or good) from loading and intentionally stalls the boot process on the splash screen without any files loaded. However that re-enables mass storage mode so that files can be removed or as a last resort a re-format done. Glad you're sorted anyway.
Bookmarks