Anything is possible with a 'hardware-bricked' unit. QuickCure doesn't rely on using boot.bin and looks for bootloader in the unit's internal memory. If it can't find it then of course it cannot actually do anything. Original fw/Cure3 fw on the other hand is using the boot component of the RGN file to initiate the flashing process and write the individual BIN components' data to the appropriate regions (fw_all.bin to region 14 [hex 0E] for instance), but i don't believe that Updater.exe is 'smart' enough to know if the data has been really flashed at all. It simply knows if it's sending it and will report if it's not or its transmission is interrupted, but doesn't know if the data is then appropriately received and used on the unit itself. That's probably all a bit simplistic and wouldn't satisfy a programmer as a reasonable explanation but as lay person that's my understanding. So, in essence what you've said is correct. QuickCure never actually starts flashing [because it can't find bootloader] and the complete fw RGN although 'sent' by Updater is unused by the unit [so its fw remains as V4.70 regardless of what version is 'flashed'].