yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Yea, the zip downloaded from ubuntuone has been changed have left the one attached as is (only change is the / is removed)

and yea try those changes. I'd still guess I've added something that can't run in recovery although I don't know what.

Try that anyway and if it doesn't work I'll make a new thread and let someone point out where I've made a stupid mistake.

Edit: OK, no one pointed it out so don't feel as bad, but something occurred to me and just checked and I did make the mistake I thought I did.

In updater-script change NativeSD.sh to nativesd.sh it appears twice. (set perm and run_progam).
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
same

same, even with the above edit.:crying:

Edit; I'm no linux expert, but it seems that when install.sh is run in /tmp the file nfo.prop has "NativeSD=true" in it, but updater-script looks for just "true", is that right?

Also, in updater script

package_extract_dir("kernel/boot", "/boot");

should be

package_extract_dir("kernel/bootsd", "/boot");

shouldn't it?

I am probably wrong though.

Edit; scratch the second one, the nand initrd.gz is edited in nativesd.sh
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Welcome back, I also wouldn't call myself an expert but I think that the nfo.prop file is making NativeSD=true a variable and updater-script is checking to see if the variable is true or false and acting accordingly (if thats the case that could prove useful in one of the revisions I have in mind). Yes andthe fact that its the nand ramdisk we are using is why this should work for other devices.

Have just gotten my phone back, (someone thought they'd hide it on me), and can just about use aroma with it, have initrd.gzs being added to PAC and NativeSD but they are empty files 0k in size, will start cutting stuff from the script and see what we can do.

Edit. have full sized ramdisks but init.rc is blank (seen this during testing so should be an easy fix)
[HD2 Android Q&A, Help & Troubleshooting and Genera] jerrysue:
Tried the latest zip and got the same result of rebooting.

The attach is my initrd.gz file copied from HYPER of FAT32. Plese check the mistake of it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Thanks have found most of the problems now that I can test myself, will attach a different folder in a minute once I confirm the system boots if you want to be the first to try with nilfs2.

Resultant ramdisk wlll be 10 times the size of the one you attached so without even looking at it i can say that that is the unmodified NAND ramdisk

Edit. Still no boot at the minute, but could use some testers to see if its due to ROM differences.

Install it, (changing rom_name at the top of nativesd.sh) and try to run it you'll probably stall at the black htc screen, from there if you could report what adb logcat reports

Tested. PAC v 1.0 EXT4 Result . - exec '/system/bin/sh' failed: No such file or directory (2) -
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Same with PAC v1.1

- exec '/system/bin/sh' failed: No such file or directory (2) -

have 957kb initrd.gz in both NativeSD and NativeSD/PAC folders though.

Edit; just tried it with MOKEE v1.6b, followed your instructions in last post (and edited updater-script) but it doesn't get past magldr gogogo.

I am using windows7 for this and noticed that the Nativesd.zip folder extracts to NativeSD folder, inside which is NativeSD folder, inside which is ramdisk folder. I think you zipped the NativeSD folder, not the ramdisk folder, and created an extra tier.

In the ramdisk folder there are 7 files, I edited nativesd.sh with MOKEE but got initrd.gz and zImage both 0Kb in MOKEE folder. I think initrd.gz 0Kb and zImage 2.77Mb in NativeSD folder, but I did not clear it before.

I then edited nativesd.sh~ re-installed and got initrd.gz 142Kb and zImage 2.77Mb in MOKEE folder. 0Kb for both in NativeSD folder iirc. I put these into NativeSD folder and it rebooted after black htc screen. From the size, the initrd.gz seems unedited.

I hope this helps
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Just found some comparative test results ext4, nilfs and f2fs

http://lkml.indiana.edu/hypermail/linux/kernel/1210.2/00005.html

Edit; looking at mount times, it seems that nilfs takes about 1.5 seconds to mount (and f2fs over 2 seconds), would the delay in the script be enough for it to mount?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
It mounts fine and runs fine with modifying the nand ramdisk as is am making a test zip now to try and identify the right command to mark the partition as nilfs2.
[HD2 Android Q&A, Help & Troubleshooting and Genera] duhhh:
Can someone explain to me as noob, how to set up and use nilfs_cleanerd :o
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
Hey, what happens to the f2fs project? The site has no files to download. What's the status afterall? I would like to test it on NativeSD, what to should I do? Where is the main thread of f2fs?

So, the f2fs is absolutely the best! So where is the devs' interest in it? I can't understand its absence...
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
No main thread, once I get all the kinks worked out with the nativesd patcher, it couldn't be difficult to add in f2fs support, if you go up one step the f2fs files are here, I can post a test patcher zip and/or modified initrd.gz if you want to test (let me know which rom), probably won't be much dev support until at f2fs is included in the mainline linux kernel.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
Hypo, thanks for your kind answer. I would like to test it on BBCM7, PA v1.5b and PACMAN .

It would be so nice if you provided those patcher zip and/or modified initrd.gz.

However what's about the kernel itself?

You're writing there's no mainline support yet. So probabely the only option is the marc1706 kernel, but how to adapt it if he himself disclaims of NativeSD support?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
That was with the original NativeSD ramdisks, marc said himself that the problem would probably be solved by increasing the wait for sdcard time, and the new ramdisks (using nand rather than sd initrd's as the base) have been confirmed to work with marc1706's kernel.

If you have a f2fs partition set up could you try and install PACman as it is? Just curious to see if it installs at all. Xylo has it set up to mount as 'auto' which should autodetect it (but probably won't boot as you need marc's kernel).

So if you could:

1. Install PACman using the recovery you use now

2. Install PACman using one of Xylograph's SD recoveries (replacing the zImage with marc's kernel), can't say I know too much about how recoveries work but this may add f2fs (at least via mount auto) to the recovery

3. After the above switch the zImage with marc's kernel on /sdcard/NativeSD and see if it boots

Not sure how to confirm if it installed or not other than via looking at how long it takes to install, as linux doesn't seem to have support yet (at least ubuntu)
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
OK, I'll try it, but for now could you tell me please whether there is any way to access f2fs partiton from PC? It could alleviate any possible problems and yet could provide way of ROMs backup...

Is there any program for MS windows?

Is there any kernel patch which any user could routinely apply onto kernel in linux installed on a personal computer?

---------- Post added at 09:30 PM ---------- Previous post was at 09:22 PM ----------

and yet another request please, which Marc's kernel version speciffically should be tried for PACMAN: ICS, JB, or maybe other?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
You need linux to format SD to f2fs in the first place.

But i have found that if you format the second partition to fat32 before formatting to f2fs, then it can be mounted in ubuntu.

Tried just installing pac1.1te (default marc1706 jb kernel included) with standard 4ext sd recovery, it hangs on black htc screen. But all the system files were installed on second partition and the data folder is created but empty. Have attached dmesg.

Will try the nilfs recovery.

Edit; sorry ictimai just saw your earlier posts, you have linux on laptop:o

also i think windows only looks at 1st partition anyway.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
How would you explain this? Is there any f2fs driver already in Ubuntu's kernel or this is just some peculiar coincidence of compatibility (between f2fs and alredy existing other fs's drivier)?

First of all, how do you know what's on f2fs partition?

Secondly, have you already tried then to switch the zImage with marc's kernel on /sdcard/NativeSD (i.e. if you're using cLK then to flash zImage into e.g. sboot)?

BTW Has anyone any idea how to compile f2fs-tools for HD2 to copy binaries into xbin and enable to format the third partition from inside the phone's Android (just like previously Hypo proposed for NILFS)?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
kernel patch info can be found here and here, if you know what you're doing with kernel patches (I don't will linux atm).

Marc seems to have added support to both, but i'd stick with the jb one.

I think we still need some way to check if the partition we have is f2fs, which could be done via a running build on another partition or nand i guess if someone wants to check.

The way you describe the installation went fine, data folder usually is empty on first install, although I would'nt be 100% that the partition i mounted as f2fs but as fat32 (vfat).

If anyone wants to test then from a running build in terminal run:

su

mkdir /sdcard/fs

mount -t auto /dev/block/mmcblk0p2 /sdcard/fs

then run mount and see what it is mounted as.

I'll add a modified ramdisk for f2fs PACman (1.1te) in a minute.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Tried this and same result as the working ext4 1.1te posted above, hangs on black htc screen

have attached dmesg

Hope to get there eventually:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
So, were all these your suggestions about this test version of PACman? Is it ok? Xylo warned this version was NOT for NativeSD! It is so confusing, please clarify a little bit which version of PACman and after what modifications to install? Of course say also when and which kernel to merge/substitude?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Hi ictimai, Xylograph posted the pac1.1te for nand users only, because he managed to get native wifi tethering working, and at that time marc1706 kernel would not boot on NativeSD. Since then, marco.palumbi and securecrt have devised scripts in the ROM's initrd.gz which allow;

1. marc1706's kernels to boot,

2. Enable some bt a2dp support

3. A cleaner way to install the rom

4. ?

See http://xdaforums.com/showpost.php?p=33335230&postcount=545
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I just formatted my sd card p1 to fat32, then formatted it to f2fs.

It mounted in ubuntu.

I installed an SD build and it is stuck on magldr gogogo.

But at least magldr recognised it.

I think that a test might be to install marc1706's kernel to an sd build (swap zimage and put system to root folder), and look at editing the sd build initrd.gz with delay so that the kernel will boot.

We then might be able to test f2fs.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Just ran some mount checks. First of 'mount -t auto' doesn't seem to work on device (through adb shell). I'm sure it did before so this may be kernel related or something (will try again later)

Have converted partitions to fat32, ext4 and nilfs2 before converting to f2fs (following #1).

Fat32 can be mounted as vfat and f2fs and ext4 / nilfs2 can only be mounted as f2fs, not sure what this means in the longrun.

I'll post another ramdisk increasing the wait time to a minute (from 20 secs), after I test it myself.

Edit. Just noticed the romname change with te, so apologies the one posted previously may/should work with 1.1, have attached one for te (wait still 20 secs) and will increase wait if it doesn't work, just rename to initrd.gz

Edit it's a no go at the moment I've afraid, I'll try some other things later
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
you know what, even on NILFS this PAC can't boot (neither v1.1 nor v1.1te), so probably sth's wrong with this "mount -t auto ..." in the ROM...

Yes, this is only now I've just installed PAC (on NILFS of course), and I've had to edit "init" script manualy before flashing the initrd.gz into sboot... Otherwise, it kept freezing on HTC logo.

So I wonder if to do the same with f2fs? However what the mount option to write down in the "init", is there anything like "mount -t f2fs .."?

Hypo, why do you have "init" as binary executable (instead of bash script) in the file attached?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
If you mean that you tried installing unmodified PAC to nilfs2 then yes it shouldn't boot (but should install), mount -t auto will work (I've only tried it once), but there are a few lines needed in init (mkdir nilfs and mounting the partition additionally to nilfs, not sure why that's needed but it seems to be). But from the limited documentation on f2fs it seems to mount the same as ext4, but was gonna try and see if it needed another mount point like nilfs2, but phone's currently in pieces (finally got outershell of) so can't test.

The attached file is based on a nand ramdisk which doesn't have init as a script, the init binary I believe would be the same as init.android binary from the SD/old NativeSD ramdisk, the modifications are done in init.rc with the nand ramdisk (with the inclusion of a bin file and busybox/e2fsck binaries)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
I tried the combo install on sundawg cm7 and the nativesd-ext4 folder creates two files initrd-nilfs2-sc.gz and initrd-nilfs2-v.gz, v version doesn't boot on ext4. The nativesd-nilfs2 folder also creates these files, v version doesn't boot either on ext4. I think that the ext4 combo folder has not been posted, and both are for nilfs2.

This method certainly looks easier to use:good:

Note that the nand (kernel/boot folder) initrd.gz from sundawg's nativeSD rom looks to be from boxmax rom and is large. I had to get nand initrd.gz from magldr download in nand thread.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Just had a quick glance and I think I just forgot to rename the ramdisks made with ext4, the issue is probably the romname not being changed properly.

Did the tmp folder copy into the NativeSD folder? I added that for easy debugging, if it did take a look at init.rc and see if the rom name got added or if it's blank.

This was would be easier to use for current users and the original would be best suited for ROM devs who want to easily add NativeSD support

PS. I do/did the same thing with BBCM7, it helps when the device stall boots and is needed as I've had multiple occurrences where the sdcard has switched to read-only after pulling the battery/force phone off, remedied by having the phone fully boot into a ROM.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
No m8, can't find it anywhere on card.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Can you post the initrd.gz files then, the temp file would've saved ~15 to 20 secs no biggie.

Thanks, I think I have fixed the tmp copy issue, will take a look to see if I can see the problem with the ramdisks, and try and think of what/where I can add some logs to try and fix the combined zip issue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
https://dl.dropbox.com/u/24033707/nilfs2 initrds ext4.zip

https://dl.dropbox.com/u/24033707/nilfs2 initrds nilfs.zip
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
They seem to be the same (both ext4), probably just got overwritten. By any chance did you edit nativesd.sh with the rom name prior to install? Otherwise that is working fine, the only thing I notice is there's a lot of cache stuff going on that I don't recall seeing in other ramdisks.

If you could try the attached with Sundawg-CM7 (ext4) renaming to initrd.gz as per usual.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
hangs on android logo screen before boot animation for both.

Have attached logcat for second initrd.gz, lots of cache stuff.

Edit; didn't edit rom_name in install.sh before install, should I have?

Edit; install.sh is in tools folder, and has correct name and mount -t ext4...

Edit; Sorry, should have posted all this in the patcher thread:o
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
I see the cache stuff, might need to run a diff between the init.rc's, any logcat from -1 (I left most of the cache stuff uncommented in that that),

No install.sh should be fine as it is but was asking about nativesd.sh (in the NativeSD folder), if you didn't touch it then the method I used to grab the rom_name from install.sh is working.

I'll post a couple new zips on the other thread in a moment if you could try them with a ROM that definately works, could be a ROM specific issue, (there's a least 1 report in the NativeSD that modified nand ramdisks (in there current iteration) don't work with CM7.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
log from first initrd.gz

Will check other thread, sorry again.

Edit; it seems your method worked, since i didn't modify nativesd.sh either
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Size isn't really an issue (especially with sense ROM's) the splash image vastly increases the ramdisk size. Have attached the nand ramdisk from the SD/NativeSD thread manually modified (needed to remove the DataOnEXT mount), if you want to try. I'll have a look at the one on the NAND thread to see if there's any difference
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
The splashscreen says boxmax from direct rom, and it hangs there.

Have attached sundawg mgldr nand initrd.gz
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Thanks was halfway through the rom download, have attached 3 ramdisks, not sure what'll work at the minute I'm sure the problem is with how GB/CM7 sets up cache but can't say for sure, might just need a few waits??

The issue I think is within:

mkdir /data/cache 0777 system cache
symlink /data/cache /cache
mount -o -w bind /data/cache /cache
mkdir /mnt/cache/recovery
symlink /mnt/cache/recovery /cache/recovery
chown system cache /cache/recovery
chmod 0770 /cache/recovery

probably the first line, but don't know for sure.

The ramdisks differ as:

1. has the last 4 lines commented out

2. has all the lines commented

3. has none of the lines commented (should be what you get from using the patcher zips)

I'll post this on the NativeSD thread if none of these work to see if someone knows what should be done

Another one to test if anyone has the chance
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
initrd1 hangs on android

initrd2 same

initrd3 same

Thanks for trying.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Just throwing in current findings with f2fs if anyone is looking in to it.

Default mount of f2fs (i.e mount -t f2fs /mnt/f2fs) results in the flags:

/dev/block/mmcblk0p2 /mnt/f2fs f2fs ro,relatime,background_gc_on,user_xattr,acl 0 0

and I can't seem to get it to mount as rw , so thinking that that might be an issue.

The mkfs.f2fs binary has been updated (need to pull the code) and at the very least seems to have resolved the fat/f2fs issue. i.e. once the f2fs partition is made you won't be able to mount it without f2fs kernel support. Correction, partition made via pulled source code binary doesn't seem to make a mountable filesystem
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
how to prepare initrd.gz for PA-HD2 and nilfs? Trying to edit init.rc but with no avail so far (hangs on HTC logo)
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
I've tried edit init.rc (in the initrd.gz):

# mount the 1st (NativeSD) SD-EXT partition
mkdir /NativeSD
mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0

changed to

mkdir -p /NativeSD
mkdir -p /nilfs
mount -t nilfs2 /dev/block/mmcblk0p2 /nilfs
mount -t nilfs2 -o rw,noatime,nodiratime,barrier=0 /dev/block/mmcblk0p2 /NativeSD

and also have tried to change into:

# mount the 1st (NativeSD) SD-EXT partition
mkdir /NativeSD
mkdir -p /nilfs
mount nilfs2 /dev/block/mmcblk0p2 /nilfs
mount nilfs2 /dev/block/mmcblk0p2 /NativeSD wait rw noatime nodiratime barrier=0

these settings variations never yielded any successful boot so far... :(
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
What initrd.gz are you working from? The instructions from post #1 would be to edit the init file from within a SD ramdisk, editing init.rc is done with NAND ramdisks and requires a few more lines of code than the above: yaffs lines need to be commented out, the first line in ueventd needs to commented and a bin folder added (with busybox binary), haven't tested this rom yet with the patcher or on nilfs2 but if could even run it on linux by.

Downloading and unzip the attached -nilfs2(3.1) zip add in install.sh and nand ramdisk (~200kb in size) to the folder and run nativesd.sh, which should leave you with two ramdisks (labelled initrd-nilfs2-v.gz and initrd-nilfs2-sc.gz) in /tmp rename them to initrd.gz and try them.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
You probably mean there is marco.palumbi in efect already, don't you?

This was kernel_tytung/boot_NativeSD/initrd.gz from the ROM PA_leo_v2.52-1.2.zip.

Should the kernel_tytung/boot_NAND/initrd.gz be taken instead for the NativeSD+NILFS mod?

Please, clarify it more plainly, I can't recover from the confusion...

Peculiarly:

- where this nand ramdisk (~200kB) to take from?

- Where to find install.sh? In PA_leo_v2.52-1.2.zip probably there is nothing like install.sh since this ROM seems to rely entirely upon Aroma Installer...

Will the initrd-nilfs2-v.gz and initrd-nilfs2-sc.gz be the same in content? If not then which one to rename into initrd.gz ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
The nand ramdisk and install.sh should be taken from the ROM you want to modify, so the one in boot_NAND.

unmodified NAND ramdisks tend to be ~200kb while the current SD ones are ~900kb

the v and sc ramdisks differ in that with v all the code is added into init.rc, while sc adds a line to redirect to another script.

Your best bet would with the v version, so try it first. And i'd appreciate it if you could try the sc version as well and see if it works.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ictimai:
Thanks Hypo, but where to find install.sh? In PA_leo_v2.52-1.2.zip probably there is nothing like install.sh since this ROM seems to rely entirely upon Aroma Installer...

At least it's me I've failed to find install.sh anywhere in this ROM zip package... Please, check yourself.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
Downloading now but if you just make a blank document called install.sh and add:

ROM_NAME=PA-HD2

to it, it should work just the same

Edit, see what you mean, basically just need a file called install.sh with ROM_NAME= in it, so renaming mount_NativeSD.sh to install.sh would've been fine.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HypoTurtle:
I did mean to run in on linux (didn't think that leaving the /boot lines would be an issue, just though those commands would fail). I would've had the NativeSD folder on say the desktop andd run the script from there but yes if using clk and the ramdisks are ~900kb in size (look in the /tmp/ns2 and /tmp/ns3 folders to make sure all the files are there) then rename one and flash sboot with it and the zImage.