[Android Development on Bada] nbates66:
ok, Since i've been managing to contact the booted kernel's adb service it's been able to let us see somewhat, the minimal filesystem it's managing to establish in RAM. Without an adb shell installed however, direct commands cannot be given, (like mount) pushing and pulling files works (files pushed onto the wave will disappear obviously on reboot) and i also managed to confirm (i think) the location of the external memory card slot device block using a crude exploitation of the pull command:

E:\adbworkfolder>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
10003c49574a recovery

E:\adbworkfolder>adb get-state
unknown

E:\adbworkfolder>adb pull /dev/block
pull: building file list...
skipping special file 'stl5'
skipping special file 'stl2'
skipping special file 'stl1'
skipping special file 'bml7'
skipping special file 'bml6'
skipping special file 'bml5'
skipping special file 'bml4'
skipping special file 'bml3'
skipping special file 'bml2'
skipping special file 'bml1'
skipping special file 'bml0!c'
skipping special file 'tfsr7'
skipping special file 'tfsr6'
skipping special file 'tfsr5'
skipping special file 'tfsr4'
skipping special file 'tfsr3'
skipping special file 'tfsr2'
skipping special file 'tfsr1'
skipping special file 'tfsr0!c'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'ram15'
skipping special file 'ram14'
skipping special file 'ram13'
skipping special file 'ram12'
skipping special file 'ram11'
skipping special file 'ram10'
skipping special file 'ram9'
skipping special file 'ram8'
skipping special file 'ram7'
skipping special file 'ram6'
skipping special file 'ram5'
skipping special file 'ram4'
skipping special file 'ram3'
skipping special file 'ram2'
skipping special file 'ram1'
skipping special file 'ram0'
skipping special file 'mmcblk1p7'
skipping special file 'mmcblk1p6'
skipping special file 'mmcblk1p5'
skipping special file 'mmcblk1p2'
skipping special file 'mmcblk1p1'
skipping special file 'mmcblk1'
skipping special file 'mmcblk0p3'
skipping special file 'mmcblk0p2'
skipping special file 'mmcblk0p1'
skipping special file 'bml12'
skipping special file 'stl12'
skipping special file 'stl11'
skipping special file 'stl10'
skipping special file 'stl9'
skipping special file 'stl8'
skipping special file 'stl7'
skipping special file 'stl6'
skipping special file 'stl4'
skipping special file 'stl3'
skipping special file 'mmcblk0'
0 files pulled. 0 files skipped.

E:\adbworkfolder>

i've been unable to get the kernel to boot and appear in any way other than "recovery" and "unknown" state, but it can be seen that "mmcblk1" is external memory card, and "mmcblk0" is internal moviNAND, "mmcblk1p5" refers to the logical partition on my memory card, into which i have placed the extracted factoryfs which needs to be mounted as "/system" but the init process doesn't appear to be following the "init.rc" or "recovery.rc" scripts, and i've no idea where else to attempt changes.

for those wondering, i do indeed have that many partitions on my sdcard, mmcblk1p6 i've been attempting to set for use as "/data", params and cache among the other partitions.