[HD2 Android NAND Development] bauner:
Here are the config settings from the upcoming V3 explained

use_ext4_partition=0|1

1=use ext4/ext2/reiserfs/btrfs partition on sdcard ((it must be the 2nd partition on sd card) set use_data.img=0 if you use ext4 partition)

0=use data.img (if use_dataimg=1) or use phone data partition (if use_dataimg=0)

format_ext4_partition=0|1

0=use existing userdata in ext4/ext2/reisefs/btrfs partition on sd card

1=format 2nd sdcard partition with ext4/ext2/reiserfs/btrfs (the second partition on sd card must exist before! and can be unformatted(raw) or formatted with any filesystem)

(can take a few minutes. after format finish format_ext4_partition= wil be set back to 0) (to prevent formating again on reboot)

use_ext2_instead_ext4=0|1

1= use ext2 partition instead ext4

0= use ext4/reiserfs/btrfs

use_reiserfs_instead_ext4=0|1

1= use reiserfs partition instead ext4

0= use ext4/ext2/btrfs

use_btrfs_instead_ext4=0|1

1= use btrfs partition instead ext4 (experimental!!! no filesystem check/repair tool availible this time)

0= use ext4/ext2/reiserfs

!!!!!ensure that only one of the use_xxx_instead_ext4= can be set to 1!!!!!!

use_dataimg=0|1

0=use data partition on phone (or ext4/ext2/reiserfs/btrfs partition on sd card if use_ext4_partition=1)

1=use data.img on sd card (if no there is no data.img in data folder it will be auto generated on boot. this can take a few minutes)

mount_data_img_sync=0|1

1=mount data.img with sync option

0=mount data.img without sync option (unsafe!!! a little bit faster, but data corruption is possible!!!)

data_img_size=0|1

size of data_img in data folder on sd card in mb (max 2048)

copy_data_from_nand=0|1

0= work with a clean data.img or ext4 partition

1=copy data from phone partition to data.img or ext4 partition on sd (can take a few minutes. after copy finish copy_data_from_nand wil be set back to 0) (to prevent overwriting your data on reboot)

copy_data_from_img_to_ext4=0|1

if set to 1 it copies your data from existing data.img into ext4/ext2/reiserfs/btrfs partition on next reboot (can take a few minutes. after copy copy_data_from_img_to_ext4= wil be set back to 0 to prevent overwriting your data on reboot)

backup_current_data=0|1

1=your actual enabled data source (nand, data.img or ext4/ext2/reiserfs/btrfs partition) is getting copied into an backup.img (which can be used for recovery or (if you rename it) as data.img on next reboot (if backup.img already exists it will be renamed to backup.old) (can take a few minutes. after backup backup_current_data= wil be set back to 0 to prevent overwriting your backup.img on reboot)

0= don´t do a backup on next reboot

backupfile_free_space=50

free space (in mb) in the backup.img (if you want to use it as data.img)

wipe_dalvik_cache=0|1

1=clear dalvik cache on boot (if you try to get existing userdata from other roms to work and/or stuck in bootloop or getting fc´s) (this bootup takes much time because the compilercache for every app ist beeing recreated) (after clearing wipe_dalvik_cache= will be set back to 0)

0=don´t clear dalvik cache

run_fix_permissions=0|1

1=try to fix app permissions (if apps don´t work)(after fix run_fix_permissions= will be set back to 0)

0=don´t try to fix permissions

recover_data_from_backup=0|1

1=restore your data from backup.img on reboot to your currently enabled data source (data.img or partition on sd card) (nand is not supported because the low storage space) (after recover it will be set back to 0 to prevent overwriting on reboot)

0=don´t recover