Certainly remove the file GUPDATE.GCD, whether you remove more files or re-format depends on the circumstances however I don't think you're understanding the basic process. Cure firmware cannot boot. It's designed that way so the device doesn't load any files like maps, POIs etc which might be stopping it from operating. It's put into a "stalled boot" state quite intentionally that it can be seen by a PC allowing the corrupt file/s to be removed or the internal file system formatted (formatting is only done should you not know which files to remove).

So essentially you need to understand some basics:

  • It's 'bricked' because it can't load a file
  • The corrupt files/s must be removed
  • If it can't be seen by PC to remove the corrupt files/s directly then cure fw must be used so that it is seen by PC
  • If cure is used but you load back a backup which contains the corrupt file/s then nothing will change, when original fw is loaded it will still be bricked
  • If you have no idea what caused the 'bricking' or there are seriously corrupt files which have weird file names that can't be deleted then a re-format is necessary
  • Once the files have been removed or a format done then original fw can be loaded.

It would be very helpful to know what you were doing just before it bricked. Had you just before updated firmware or maps, loaded new POIs or a voice or vehicle files for instance?