[Asus  Eee Pad Transformer Prime] shreddintyres:
Unfortunately im not very well versed in NVflash or fastboot yet, however if you were able to successfully able to generate the files in AndroidRoot's guide you should be able to perform a full system recovery, how is an entirely different issue

hopefully these help:

c:\>nvflash --help
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--dumpbit [options] {debug|regress|force}
dumps the structure of bit on terminal in text form --getbct
reads back the BCT from mass storage
--odm C Data
ODM custom command 'C' with associated data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--rcm file1 file2
specifies the encrypted and signed RCM message data files
got from nvsbktool for talking to bootrom in odm secure mode
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config fil
e,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
--setblhash <bct file>
send encrypted bct file got from nvsbktool to miniloader to support
downloader bootloader or microboot in secure mode
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
--deviceid N
sets the device ID of the target either hex or decimal
--transport <transportname>
transportname should be <jtag> for emulation platforms and <usb> for othe
r platforms
or it can be <simulation> for doing whole Nvflash process on host side,de
vice not needed
--instance <n>
instance number of the device
--updatebct <bctsection>
bctsection should refer to the section of the bct we are updating.
Curently we suport updates for following sections
<SDRAM> updates SdramParams and NumSdramSets fields
<DEVPARAM> updates DevParams, DevType and NumParamSets
<BOOTDEVINFO> updates BlockSizeLog2, PageSizeLog2 and PartitionSize
--devparam <P> <B> <N>
P is the logical page_size of the device. Default size is 2048 bytes
B is the erase group size of the device.
N is total number blocks of the device (erase group units)

you could try the following but keep in mind im completely guessing and there is no guarantee this will work

first to see if your partitiontable is whack run

nvflash --getpartitiontable <insertwhatyouwantonamethepartitiontable>

---------- Post added at 12:58 PM ---------- Previous post was at 12:26 PM ----------

I just realized that you are trying to flash .blob files, with the bootloader that comes with the NVflash mod you must use .img files you will need to get blob unpacking tools from Android Root to unpack blob files then flash them partition by partition

see this post

http://xdaforums.com/showpost.php?p=28969489&postcount=126