The meaning of error codes has been discussed on xbh in this thread :
http://www.xboxhacker.net/index.php?topic=7290.40tmbincdump-read2 acts as a logical firmware dumper (it will avoid bad sectors) and just reports unused/blank sectors (usually at the end of the firmware) with error code 0x380 (not really an error).
These usused/blank sectors are usually filled with FF. If your Nand has zero bad sectors, the logical dump obtained will be the same as the physical dump.
tmbincdump-read3 acts as a physical firmware dumper.
Sectors are grouped together to form blocks of 32 sectors.
If one sector is bad, the group is marked as bad (I think).
0x350 reports the first sector of a bad block
0x310 reports the following sectors of a bad block
This dump will work all the time if you reflash (even if you have bad blocks).
Of course official MS software will never encounter problems with a Nand that has bad blocks (MS uses cheaper nands that have a few bad blocks).
But it may not be the same with hackers tools, since tool's author may have error free nand at the time he developped the tool. Not everything is understood about the mechanism that allows MS software to 'avoid' bad sectors. So it may work or not, try your luck. It depends a lots on where are the bad sectors. Try to use lastest version of tools, in case improvement happened in regard of non error free nands.
This post has been edited by openxdkman: Feb 11 2008, 11:46 AM