yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried evervolv and am getting some errors, this is test40 from your script before last

Edit; just tried your last script test41, same errors. I think it is because evervolv has a boot.img, and it might not be unpacked properly.

Note that in the last 3 scripts i had to delete "; then" from line 23 (unexpected "then") before the script would run.

will try pixeldroid again

Edit2; tried pixeldroid (2x ext4s) and no reported errors in screens. checked mount, looked ok. test.zip completed successfully almost immediately, but i found an error in recovery log "line 210 col 17: syntax error, unexpected STRING, expecting $end", have attached log and updater-script, test.zip is 181mb.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea most definately it's the boot.img thing (and I also take it there no binary-installer (i.e. it's not an aroma script) - which won't cause an error persay but have modified the script accordingly anyway)

systeminstall() {
printf "%s\n" "installing system"
cd /
# rm -rf /system/*
systemlocat=` mount | grep /system | cut -d ' ' -f '1' `
datalocat=` mount | grep /data | cut -d ' ' -f '1' `
echo "system mounted at ${systemlocat}"
echo "data mounted at ${datalocat}"
if [ -n "$systemlocat" ]; then
romzip="/sdcard/${2}*.zip"
echo ROM zip found is at ... ${romzip}
if [ ! -d /sdcard/tempy ]; then
mkdir /sdcard/tempy
fi
cp ${romzip} /sdcard/tempy/test.zip
chmod 0777 /sbin/7za
echo META-INF/*aroma* > exc.lst
echo "initrd.gz
zImage
boot.img" > inc.lst
/sbin/7za x /sdcard/tempy/test.zip META-INF -oMEI '-xr@exc.lst' -y
/sbin/7za x /sdcard/tempy/test.zip '-ir@inc.lst' -oramds -y
ubi=` find MEI -name 'update-binary-installer' `
ub=` find MEI -name 'update-binary' `
ups=` find MEI -name 'updater-script' `
echo "UBI location is ${ubi:-$ub} UPS is ${ups}"
mkdir -p /META-INF/com/google/android
cp /${ubi:-ub} /META-INF/com/google/android/update-binary
echo "package_extract_dir("system", "/system");
package_extract_dir("data", "/data");" > /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/symlink(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/set_perm(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/set_perm_recursive(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/setmetadata(/,/);/!d' >> /META-INF/com/google/android/updater-script
echo "modifying updater-script"
echo "umount /NativeSD
umount /DirectSD
umount /system
umount /data
umount /boot
umount /system
umount /boot_dir" >> /META-INF/com/google/android/updater-script
/sbin/7za u /sdcard/tempy/test.zip META-INF/
else
cat "system not mounted"
fi
}
bootingred() {
printf "%s\n" "obtaining an initrd.gz and zImage to work with"
###### Copying zImage and initrd.gz from /boot_dir when one wasn't in the zip
if [ ! -e "ramds/boot.img" ]; then
nandinitrd=` find ramds -name 'initrd.gz' -print0 | xargs -0 ls -s | sort -nr | awk '{print $(NF)}' | tail -n 1 `
zImagelocat=` find ramds -name 'zImage' `
cp /${zImagelocat} /tmp/zImage
cp /${nandinitrd} /tmp/initrd.gz
else
chmod 0777 /sbin/unpackbootimg
cp ramds/boot.img /tmp/boot.img
/sbin/unpackbootimg /tmp/boot.img /tmp > /tmp/bootimg.txt
cp /tmp/boot.img-ramdisk.gz /tmp/initrd.gz
fi
if [ -f "/sdcard/zImage" ]; then
cp /sdcard/zImage /tmp/zImage
cp /sdcard/modules/* /system/lib/modules/ 2> /dev/null
fi
if [ -f "/sdcard/initrd.gz" ]; then
cp /sdcard/initrd.gz /tmp/initrd.gz
fi
}

should work (provided that boot.img is in the root of the folder (could add another findline I suppose) )
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
back to evervolve

the rom.zip has meta-inf, system, boot.img and file_contexts. The meta-inf/..*../android just has update-binary and updater-script

test40-1 screens attached
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea that's how I interpreted the previous 'errors':

systeminstall() {
printf "%s\n" "installing system"
cd /
# rm -rf /system/*
systemlocat=` mount | grep /system | cut -d ' ' -f '1' `
datalocat=` mount | grep /data | cut -d ' ' -f '1' `
echo "system mounted at ${systemlocat}"
echo "data mounted at ${datalocat}"
if [ -n "$systemlocat" ]; then
romzip="/sdcard/${2}*.zip"
echo ROM zip found is at ... ${romzip}
if [ ! -d /sdcard/tempy ]; then
mkdir /sdcard/tempy
fi
cp ${romzip} /sdcard/tempy/test.zip
chmod 0777 /sbin/7za
echo META-INF/*aroma* > exc.lst
echo "initrd.gz
zImage
boot.img" > inc.lst
/sbin/7za x /sdcard/tempy/test.zip META-INF -oMEI '-xr@exc.lst' -y
/sbin/7za x /sdcard/tempy/test.zip '-ir@inc.lst' -oramds -y
ubi=` find MEI -name 'update-binary-installer' `
ub=` find MEI -name 'update-binary' `
ups=` find MEI -name 'updater-script' `
echo "UBI location is ${ubi:-$ub} UPS is ${ups}"
mkdir -p /META-INF/com/google/android
cp /${ubi:-$ub} /META-INF/com/google/android/update-binary
echo "package_extract_dir("system", "/system");
package_extract_dir("data", "/data");" > /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/symlink(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/set_perm(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/set_perm_recursive(/,/);/!d' >> /META-INF/com/google/android/updater-script
cat /$ups | sed -e '/setmetadata(/,/);/!d' >> /META-INF/com/google/android/updater-script
echo "modifying updater-script"
echo "umount /NativeSD
umount /DirectSD
umount /system
umount /data
umount /boot
umount /system
umount /boot_dir" >> /META-INF/com/google/android/updater-script
/sbin/7za u /sdcard/tempy/test.zip META-INF/
else
cat "system not mounted"
fi
}
bootingred() {
printf "%s\n" "obtaining an initrd.gz and zImage to work with"
###### Copying zImage and initrd.gz from /boot_dir when one wasn't in the zip
if [ ! -e "ramds/boot.img" ]; then
nandinitrd=` find ramds -name 'initrd.gz' -print0 | xargs -0 ls -s | sort -nr | awk '{print $(NF)}' | tail -n 1 `
zImagelocat=` find ramds -name 'zImage' `
cp /${zImagelocat} /tmp/zImage
cp /${nandinitrd} /tmp/initrd.gz
else
chmod 0777 /sbin/unpackbootimg
cp /ramds/boot.img /tmp/boot.img
/sbin/unpackbootimg /tmp/boot.img /tmp > /tmp/bootimg.txt
cp /tmp/boot.img-ramdisk.gz /tmp/initrd.gz
fi
if [ -f "/sdcard/zImage" ]; then
cp /sdcard/zImage /tmp/zImage
cp /sdcard/modules/* /system/lib/modules/ 2> /dev/null
fi
if [ -f "/sdcard/initrd.gz" ]; then
cp /sdcard/initrd.gz /tmp/initrd.gz
fi
}

if that fails can you run: /sbin/unpackbootimg -while in adb shell
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
it failed with segmentation fault again. tried a few things with adb shell and get segfaults, see screen.

We might be able to do it manually;

1. delete first &800(hex) bytes (2048)

2. search for "00000001F8B"(hex)

3. everything up to "1F8B" is kernel

4. everything after, and including "1F8B" is ramdisk
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i get unexpected } line 535, but not sure where to put it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
It mustn't like empty functions just remove the repackboot(){} or add an echo line or something in it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i cant get your unmkbootimg to work, it does not segfault, but it seems to want the input for mkbootimg. if i type adb push unmkbootimg to /sbin | chmod 777 /sbin/unmkbootimg | cd /tmp | /sbin/unmkbootimg boot.img it says something like " [--kernel (filename)] [--ramdisk (filename)]..."

i tried the one from here http://xdaforums.com/showthread.php?t=1877807 but get an error on line 1 unexpected word (expecting ")") :confused:

will try your edit on test42

Edit; i now get "line 554: 3: parameter not set", it is the "fi" line
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
data_NAME=${3:-$ROM_NAME}

if you're wondering the data_NAME variable is so that /system and /data can be in different folders (which should allow /data to be shared between ROMS)

will fix the 3 parameter not set,

that link is an x86 binary (not arm) so wouldn't expect it to run.

Try the one in the zip attached (rename the unpackbootimg to unmkbootimg). Not 100% sure where I got it so can't add credits atm
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
That one works:highfive::cool: see screen

If roms are sharing /data, do we have to differentiate GB, ICS, KK roms? since some apps won't work from different platforms. Or just install them and if they don't work, so be it.

Edit; tried test42 with the edited data_NAME line and new unmkbootimg, and get no errors from adb console, can attach screens. tried "tempy"/test.zip and it completed successfully immediately. i get "line 149 col 17 unexpected STRING. expecting $end" from recovery.log, have attached updater-script
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
If it's going to work at all (not sure what the influence of SELinux etc. has on this) then yea gonna have to differentiate the roms.

At the minute the script as it stands is set to run as sh univ.sh ${type} ${ROM_NAME} ${data_NAME}

and if ${data_NAME} / $3 is blank it takes the value of ${ROM_NAME} / $2 .

If you ran the script as " sh univ.sh ${type} ${ROM_NAME} JB " for example there will be a JB/data folder made in either the NativeSD or DirectData folder, it'll be mounted and the mountfs.sh script altered according.

Running a different rom with the script with JB as the third argument will use the same folder as the first one.

From the screens it looks like the script will run fine for Magldr (will need to correct the clk stuff as that output is a tad different than what I was expecting), can you run " cat boot.img-base " - Is is just the numbers that are saved?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
where is boot.img-base ?

See edit above for test42.

Excellent news, i always wanted shared /data, securecrt, Xylograph and Datagr never got around to doing it :fingers-crossed:

Edit; boot.img-base just has the number 11808000 in it, i couldn't see it after running the script, so i ran unmkbootimg again in console
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
the last test(42).zip had boot.img in it:confused:

also updater script lines at end i think should look like

unmount ("/NativeSD");
unmount ("/DirectSD");
unmount ("/system");
unmount ("/data");
unmount ("/boot");
unmount ("/system");
unmount ("/boot_dir");

with 2 new lines after

Edit; test43 unexpected "}" line 164 expecting "fi", not sure where to put it.

Edit2; assuming fi goes between 145 and 146, i get the attached screen, seems ramds is not made
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
test44 2 screens, first shows first run, second one is after systeminstall is replaced
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
test45 seems to work, no errors in screens attached. recovery.log shows same error as earlier "line 149 col 17: syntax error, unexpected STRING, expecting $end"

Edit; i made the unmount edits in this post http://xdaforums.com/showpost.php?p=53333123&postcount=211 and test.zip takes some time to run....:fingers-crossed:

hangs on htc screen, logcat just says "- exec '/system/bin/sh' failed: No such file or directory (2) -"

have attached dmesg and new ramdisk
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Sorry didn't notice the n's in your previous post.

Two things I noticed.

1. a / in the line " sed -i "/on fs/ a exec /mountfs-${1}.sh/" /tmp/work/*.rc " that need to be removed

2. do you happen to have something at /sdcard/initrd.gz as this will always take preference over any other ramdisk; be it in the rom zip, or in a boot.img

Scratch #2, The initrd.gz you posted isn't exactly a nand kernel. It has the following:

# wait for sdcard
# wait has a timeot of 5 seconds.
# calling it 4 times allows 20 seconds for the mmcblk0p2 partition to show up
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p2
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
wait /dev/block/mmcblk0p3
# SD Card Speed Fix
write /sys/devices/virtual/bdi/179:0/read_ahead_kb 2048
# File system check
exec /bin/busybox sh -c "/bin/e2fsck -p /dev/block/mmcblk0p2 > /fsck.log"
exec /bin/busybox sh -c "/bin/e2fsck -p /dev/block/mmcblk0p3 > /fsck.log"
# mount the 1st (NativeSD) SD-EXT partition
mkdir /NativeSD
[COLOR="Red"]	mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0
# mount the 2nd SD-EXT partition for data
mount ext4 /dev/block/mmcblk0p3 /data wait noatime nodiratime barrier=0 [/COLOR]
# cleanup
# delete /bin to free ram
rm /bin/busybox
rm /bin/e2fsck
rmdir /bin

It's mounting p2 as NativeSD (not sure why), and the whole p3 partition as /data. (It is modified correctly ; albeit with the added / - with the exec /mountfs-directsd.sh ). I'll manually strip the code and post the initrd.gz just to see if that's the only issue.

Edit: initrd attached
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I am getting same logcat as with other ramdisk, hanging on htc screen, will give it a bit more time and post dmesg

edit; oops about not nand ramdisk originally, it was designed to boot from nand and have 2 ext4 partitions. i can try another rom directSD

edit2; fyi attached dmesg

edit3; just tried NexusHD2-kitkat, get same logcat, hanging on htc screen, will give it a bit more time and post dmesg. btw, got rid of that / beforehand.

edit4; attached nexusdmesg and new initrd.gz

edit5; last dmesg shows walter's kernel, something is wrong here, probably me
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Only thing left to check is the busybox binary. Toss the attached into the /sdcard/bins folder (or push to /sbin ) - may need to chmod 777 (not sure if the script itself needs to use busybox).
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
i missed something in the last test, i had a similar named zip on sdcard and the script found both filepaths.anyway.

test45-2 i put busybox and unmkbootimg in /sdcard/bins then ran the sh. get screens attached. seems zImage is lost, but was extracted.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
It's found but it looks like it's trying to copy it in a folder (/tmp/zImage) and it's erroring as it doesn't exist.

run:

"find ramds -name zImage"

and

"find ramds -name zImage -print0"

(removing the last zImage from the cp line "cp /${zImagelocat} /tmp/zImage" should also work but the initrd.gz copied fine)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
ran those, see screen
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
test46; script ran without errors, had to add the edits from http://xdaforums.com/showpost.php?p=53333123&postcount=211 again before test.zip installed properly (add the quotes and brackets to unmount lines)

get same log as before, hanging on htc screen, get same as log message when i try to adb shell.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
test47; getting same log message

Edit; dmesg and ramdisk attached

Edit; reformatted p2 & P3, tried slimkat NativeSD, get test47-1 screens
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Just to explain what's happening there: NativeSD = no mt2 variable being declared (blkid on p3), which means it defaulted to f2fs causing the dump and fsck.f2fs copy errors and similarly the mt2 not set error at the end (causing the script to die due to set -u)

That's been corrected in the attached, I think that 's all the binaries attached, some of them are different to the ones you are currently using - that would seem to be the only variable left that could be causing the mounting errors.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Tried tytung nexusHD2 cm11 directSD ext4 ext4, and it boots :highfive::D

will try another

Well done:good::good::good:

edit; tried miui v5 NativeSD ext4 ext4, hangs on bootanim, attached dmesg and initrd.gz

will try another

Edit2; can we have the new initrd.gz and zImage copied to /sdcard/NativeSD too, to save putting them in manually? Also can the HaRET files be put there too (not for f2fs ofc)

tried ChauTien_SllmKat NativeSD ext4 ext4, hangs on bootanim (no adb again, shows serial number but says offline from adb devices, no log) attached dmesg, initrd.gz and

Edit3; tried slimkat DirectSD ext4 f2fs, and it boots. f2fs zImage and the modules were put on /sdcard.:)

Edit4; pixeldroid_liquid also boots DirectSD ext4 f2fs. I have posted some benchmark results comparing DirectSD dataonext and dataonf2fs on this rom

Edit5; MIUI_V5 also boots DirectSD ext4 f2fs
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I checked slimkat nativesd install on p2 and there is a system and data folder in the slimkat folder, so that looks ok. will delete it and reinstall with new script.

Edit; i am getting "parameter not set" on lines 527 and 551
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Does it say which parameters aren't set? Also could you attach (edit the previous post), the initrd (and dmesg) from the booting DirectSD SlimKat - just for comparison - nothing else has jumped out at me as to why Direct works while Native doesn't. Have you tried any preKK ROMs?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
My bad last night, i didn't pass the 2 variables when i SHed univ:o I shouldn't test AND watch footie.

univ2 slimkat NativeSD ext4 seems to install ok, but hangs again on bootanim. have attached ramdisk, dmesg and a screen of log if it helps.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
had a couple of errors with extra";"s, after "then" and "to"

then had "install_type" error, not sure how to fix it.

See screen

Will post those other things with univ2 soon.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
had a couple of errors with extra";"s, after "then" and "to"

then had "install_type" error, not sure how to fix it.

See screen

Will post those other things with univ2 soon.

Edit; double posted:o:)

have attached dmesg, initrd.gz and recovery.log of directSD

and the same for NativeSD

There are odd errors in both recovery logs.

Edit2; just realised i have p3 as f2fs still, didn't check directSD install past it booting, but it booted. will change to ext 4 and retest.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
slimkat nativeSD ext4 ext4, hangs on bootanim again.

Edit; seems updater script mounts (and bind mounts)all install types regardless of which one chosen, the last to be mounted is directSD. might be why nativeSD not working

Edit2; thinking a bit more about these mount binds, it shouldn't affect where /system and /data files are installed to, since that is done at the start of the script with everything bind mounted previously, but it will affect the subsequent set_perms, they will all be applied to "/DirectSystem/$ROM_NAME/system/*" instead of /system/* etc.

Does this make sense?

It seems the lines 220-223 of univ4 copy a defined line, and the next line, can the next line be omitted?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I found a couple of things it might be

sed might ignore the rest of the line once it has found a match, so it might start the next search for ");" on a new line.

the semi-colon is a command which can be used to combine several sed commands on one line.

Been reading http://www.grymoire.com/unix/Sed.html#uh-33 :cowboy::D

Saw your edit will try later, have to get ready to watch footie:o:fingers-crossed::fingers-crossed:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
tried univ5 and it still hangs on bootanim
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
and no adb I take it (for an adb shell mount; and adb shell logcat)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
no, device is "offline" during bootanim
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
can you post the initrd again (just so we're working of the same) , I'll add a line to the mount script to try and get a logcat, just so you don't have to run the script again
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Here you go

Edit; i don't think the problem is with installing the /system files. I tried using the original NativeSD initrd.gz (after changing the p2 folder name to that used by original rom) and it boots
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
univ6 nativeSD ext4 boots:good::good::good:

have attached 2 screens fyi

Edit; tried ice cream tosti nand rom, nativeSD and it boots:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
It was that pesky ro then (didn't have time to get round to booting my linux VM).

I take it that mount you called was after running test.zip (or a reboot) as is unmounted.

Just need to check if the script can be run just to do the mounting so that it can be bundled into the test.zip

Just to clarify this should now mean that what works is:

NAND

DataOnExt (with ext and f2fs)

NativeSD (ext/f2fs - not sure how /system will handle f2fs though)

DirectSD (ext-ext; ext-f2fs; f2fs-f2fs - again not sure how f2fs will handle /system)

FYI By ext I mean any partition type picked up by blkid.

Currently the script can be run in two ways

sh script.sh TYPE ROMNAME {DATANAME N/Y}

or

sh script.sh COMMAND TYPE ROMNAME {DATANAME N/Y}

TYPE being NAND,DataOnExt,NativeSD or DirectSD

ROMNAME being any name of choice (for the moment needs to be within the name of the rom zip)

DATANAME is optional will default to ROMNAME

N/Y also optional defaults to no (requires a DATANAME to be declared if used) states whether or not the script should install /system and /data (thus no need to flash rom zip)

COMMAND for the moment is m for mounting relevant files and partitions and mr for modifying the ramdisk.

Will start tidying things up next week.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
I'll add this here for now. (Robbie P could you post/PM me the running TWRP f2fs recovery, and the f2fs kernel/modules - I haven't got round to recompiling the recovery with the f2fs unmount fix).

Attached is my script and binaries (both found and compiled by myself), similar to the above but with the addition of an untested "new"/old type of porta.

porta will/should function like the old portadroid builds, with system.ext data.ext and cache.ext files on the sdcard.

As it's completely untested I could use some testers to run a few scripts, to pick up on anything I may have missed. (Also anyone who can provide a diff between a portadroid build and a nand one. portadroid itself is a rather difficult thing to follow ).
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
have attached my zipped recovery folder from sdcard and the kernel modules.

the folder contains the haret files, could you use them in the script? startup.txt would need editing. You could also use the kernel in it if needed from the script.

note that the recovery does not seem to format to ext4.

will test beta1 later:fingers-crossed:
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Thanks for those. Just so I can add them to the new thread to provide f2fs.

Can't format to ext4... from f2fs I take it. That would be due to the unmounting issue, if you unmount in terminal as you did before it should format.

I'm not sure exactly what I've done with the haret files in beta1, it should look for the files extracted from the rom zip and from /sdcard (will change to /tmp so you can drop them into /sdcard/bins). But will only do this with haret bootloader (there's a # in bootloader check that you can remove if you want to test this)

The kernel/ramdisk are added into /sdcard/NativeSD/ so should work with the NativeSD startup.txt's (unsure on this).