My pleasure to help. You're almost certainly correct that GarminExpress was the cause if you were indeed using it to update immediately before the problem happened. Previously,especially when it was first introduced and probably frankly only in Beta form, there were countless reports of (so-called) "brickings" after using GE where the devices were either stuck on the Logo screen unable to load a faulty IMG, VPM, etc. file, or as in your case a faulty fw_all.bin file in the new GUPDATE.GCD had messed up region 14. Garmin, being Garmin, blamed the victims by claiming that users were disconnecting their devices before the update files were complete .... in some cases that may have been so. However that flood of problems has now reduced to a trickle as GE's matured into a more reliable program.