** NOTE: filenames may be case sensitive depending on your platform! **

put per console data in a folder and specify the folder with
-d foldername
on the command line


required files include (provide it as):
---------------------------------------
-kv.bin         (decrypted!) (alternate: keyvault.bin, KV_dec.bin)
-smc.bin        (decrypted! PRE-HACKED!)
-smc_config.bin (alternately config.bin, config_raw.bin)

-nanddump.bin   (provides above data, as well as LBA mapping for the final image)
alternately, nanddump.bin can be provided here for the above files, separate files override anything
    in the nanddump (ie: if you provide smc.bin, the smc.bin in nanddump.bin will be ignored)
Using this, it should be possible to update a nand build while retaining settings without any extra
    work.

none of these should be necissary but can be placed here for the builder*:
-------------------------------------------------------------------------
-crl.bin
-extended.bin
-secdata.bin
-dae.bin
the provided files are accurate templates for 12611 and will work with any console
    * if you provide these encrypted, you must provide corresponding .meta file


options files:
--------------
cygnos      causes bootstrap to set 360 UART to cygnos compatible speed
olddvd		xell check looks for tray state: not closed (default check looks for eject button turning console on)
nodvd       xell check looks for tray state: fully out (implies olddvd)
nomobile	when using a nanddump.bin image, mobile*.dat in it will be ignored
noremap		when using a nanddump.bin image, block mappings will not be applied to the final image
xenon       sets console type as xenon (command line overrides)
zephyr      sets console type as zephyr (command line overrides)
falcon      sets console type as falcon (command line overrides)
jasper      sets console type as jasper (command line overrides)
jasper256   sets console type as jasper256 (command line overrides)
jasper512   sets console type as jasper512 (command line overrides)
    * these are checked for as "file" or "file.txt", for example nodvd will
      be checked for as both "nodvd" and "nodvd.txt"
    
    
you can also put cpukey.txt here containing the cpu key for the
machine that belongs to the above files, see cpukey.txt for format.


Settings files that can be placed here as well, but are not required:
---------------------------------------------------------------------
MobileB.dat (first boot/resolution/region/etc settings)
MobileC.dat (connect to live data)
MobileD.dat (media center extender setup)
MobileE.dat (data created when it asks you if you want to add live info)
MobileF.dat
MobileG.dat
MobileH.dat (unicode xlaunch settings - devkit only?)
MobileI.dat
MobileJ.dat (xbdm settings - devkit only?)

you can get these files by extracting an existing/used console dump via
the included mobileExtract.exe
