Quote Originally Posted by TrueRedRat View Post
Unfortunately, no. :-(
Maybe there is a way to dump it from device?
You can dump the contents of region 14 using text commands in card which will give you V1.6's fw_all.bin, but you'll need to use V2.20 boot.bin as Ldr.bin to execute which will then overwrite region 12. Unexpected and unsatisfactory results may result it you then boot the device before trying to write later fw_all to rgn14. If you wish to go down that path i'd suggest doing all commands in one update.txt file, i.e. dump 14 and 41 (non-vol memory region) and then write V2.20 fw_all to rgn 14. Read this thread: [Only registered and activated users can see links. ]. If you wish to try this method and need further assistance with the txt commands just ask.

Yes, with a usual hierarchy of directories.
Then it's unlikely a 'partial bricking' is preventing the fw update and therefore trying to load cure fw is pointless when you have MSM available. You could try a reformat anyway. Do a files backup first of course if you feel the need. Use only [Only registered and activated users can see links. ] to reformat, don't use anything else including the built-in Windows tool.