yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] Mithrandix:
Hello guys, I tried installing this with the latest PA build but somehow i don't get it working. And yes i have read everything in this topic but i still can't get it to work. I hope someone can help me out after i explained what i did.

The steps i took:

1.Took my SD card out and formatted it with minitoolwizard with 1 partition fat32 and 1 partition ext4 (both primary). I made a folder called Recovery on my SD card aswell.

2. I took the Ext4recovery and used the recovery_leo.img to put it in the HD2 toolkit. I renamed it then to Recovery-raw.img and installed it with the HD2 toolkit with Magldr in flash mode.

3. I then went to magldr /10. Services /1.bootsettings/3.Ad SD dir/, Now i tried selecting the recovery folder below "<.>" but i can't select it in any way. It either keeps throwing me back to the MAGldr menu or it keeps flashing really fast that tells me its trying something but it can't select it.

4. I then tried to install the latest PA build .. with Sd-ext. After the installation it reminded me i have to change the SD dir to Native SD.

5. Rebooted and tried again to select the NativeSD , actually i see 4 things now in the order of:

<.>

SD-Ext

NativeSD

Recovery

But whatever i try.. i can't select it.

6. Restarted again but when booting it gives me the error:

K: Zimage SD kernel open failed ,

Did i forgot something or what i can do change the sd dir?

Thanks in advance

Edit: Was able to change the dir and its working now! .. sorry for the long text
[HD2 Android SD Development] Xylograph:
What the #%$^ is wrong with you man ????

You don't talk like that to anyone here... you sir are no example of a 'forum member' and you should be ashamed speaking to a forum moderator with the best intentions that way..

I have said it many times before and I will do so again..

This is a NativeSD thread and the goal we have in mind is to make it OS independend and usable for everyone..

That this method could also be used on 'name of phone here' , 'name of FS here' , 'name of the best sdcard here' is very cool, but not relevant to the method itself..
[HD2 Android SD Development] timmymarsh:
Guys, chill, this is being taken care of ;)

......unfortunately, there will always be the occasional troll amongst our members [tears off shirt in a hulk like fashion]
[HD2 Android SD Development] securecrt:
I am thinking of make the NativeSD works on Desire ,Nexus One and any other old android phones.

I think it is possible.

The Stock android phone if the user can unlock&ROOT it then the boot partition on NAND flash will be writable by user at any time. so we can also install the system on sdcard/ext4 partition just like HD2 and keep the boot.img on the sdcard with the correspond dir name. And also need a app like the NativeSDMultiBoot to write the boot.img to the boot partition when do the OS switching. The idea is simple and straight forward, I hope the Desire and Nexus One Devs can make some works on it as both of them are using the crap NAND flash like HD2.
[HD2 Android SD Development] timmymarsh:
Hi securecrt :)

Im having problems with several roms (both JB&ICS) in that the nativesd multiboot app & c1's CM9 app do not reboot the rom when changes are made. Is it possible this is something to do with the ext4 partition itself, not reading/writing the way it should? Im thinking im going to have to reformat the partition and start over.

fyi, i use 2 sd cards, one for WP7, the other for android both (SD & native SD). Both cards are good transcend class 6, 8gb and never had a problem with them before. Also my ext4 part is 2gb, only 1.1gb used.

Im most confused by this strange reaction, if it was only happening with one rom id suspect a 'bad flash (lol)' but for it to happen with both JB roms is too much of a coincidence.

ANy thoughts?

Cheers and good work,

Tim.
[HD2 Android SD Development] ictimai:
I've just tried to flash ClockworkMod Recovery 5.0.2.6 into tboot but it doesn't recognize NILFS partition - when the option "mount SD-Ext" has been chosen then the error is the answer, so where is it's "NILFS support"?
[HD2 Android SD Development] securecrt:
I have 7 ROMs on my sdcard ( NexusHD2,PA,BareBoneCM7, Typhoon_CM7, QissMe, CM9ight, CYANX.) I never have this problem like you. can you post the logcat when you push the REBOOT button in the multiboot app(this app need ROOT permission, so you need to check your superuser app, is it possible that you disable it? )
[HD2 Android SD Development] hutc:
thank you once again

thank you xylo so basically they use the same ext4 partition without any overwrite as they are in 2 diferent folders on the same ext4 partition,thank you buddy for clarifying this bu the way i am ready for my back up rom on the native sd card.

xylo dont worry about other comments,your method of doing this is awesome.
[HD2 Android SD Development] ictimai:
So, can NILFS-ROMs be installed normally via "CWM touch 8" while through other recoveries not yet? (So, has exactly this version "8" NILFS support built in?)

Which is this CWM touch 8 and where to download it from? Is this from that your post?

P.S. I can't see separate thread yet so I still keep writing here on NILFS... The effect is out of question and that is why NILFS in Android needs receive proper attention.
[HD2 Android SD Development] Xylograph:
Sure, all of this should be applicable for the other phones you are talking about with most likely very little modfications needed..

Problem is we do not have these phones and besided that.. Isn't it better to improve what we have now first ?

To be honest.. I wouldn't be suprised if users/devs of other phones are already trying to get this same stuff going on their phones.. They wander around our forums just as hard as we wander around @ theirs ;)

The installing of roms is a process 'outside' of recovery.. however restoring and making backups is not...

You should be able to install these 'nilfs2 modified roms' on any recovery for that matter, but that's it..

Even if you would be able to restore and backup nilfs2 partitions using a recovery.. what about a2sd nand users ?? they can't use their ext partition anymore because of that..

Even if you should decide to use nilfs2 as a 3rd partition.. there is only 1 recovery able to mount a 2nd partition as far as I know and that's 4ext recovery with no nilfs2 support..

Btw.. I don't know if you guys are aware (I wasn't) of the fact that you can still find nightly recoveries for our device in arif-ali dropbox..
[HD2 Android SD Development] Cherokee007:
I flash clk from kokotas and i haven't see in clk item sboot. Please how I make sboot partition? Thank
[HD2 Android SD Development] timmymarsh:
mm looks like i dont have root, fix permissions also brings up 'cant open /data/system/packages.xml: permission denied, which would kinda make sense why things are a little weird.......... logcat: permission denied.

.......in SU, there is nothing, at all, no apps listed etc.

Edit: root checker gives mixed results, sometimes root given, others not?
[HD2 Android SD Development] adityameena26:
Native SD on miui..

hii everyone..

tried editing 'mymiui v6' rom to make it able to be used with Native SD..followed the instruction given on first page..but got stuck on the step where I will have to make change in initrd.gz.Dont have any idea from where i can get initrd.gz for my rom..maybe it should be there in kernel.but where can i edit it to make it able to mount ext4 partition..??

any help..
[HD2 Android SD Development] Cherokee007:
Please write me how create sboot but in clk from kokotas item sboot missing and I don't know how make it. I install black_lk_20120911-TouchRec_b8.7z but item sboot i missing. :crying:
[HD2 Android SD Development] NYLimited:
That is quite right although I have not had any idea for a long time what the differences are among them, if any. He has not been around much (since he lost his HD2) and there is no official change log for them that I know of. Maybe his compiler is on auto pilot? :crying:

This is why I thought your port of TWRP was exiting...
[HD2 Android SD Development] wis1152:
What ROM are you having the problem on? I will take alook:)
[HD2 Android SD Development] averestefd:
I use aokp b35's both on sd with the cpu up to a max 1612. Can it transfer this current setup to nativsd ext4 and/or nilfs? How would we do that? And could could storage be icreased from 384mb to 776 without losing my data ie mms...?

Also could someone tell how to check if the current part. For recovery is at 7mb? With kaiser there was a command to type on terminal to report nand partitions...

Thank you....
[HD2 Android SD Development] timmymarsh:
.

Thanks bro, unofficial CM10 only at the Mo, had same issue with aokp jb too ;)
[HD2 Android SD Development] c1cl0n:
My experience can help timmymarsh to fix root acces for NativeSD because I also encountered this problem before

In my sittuation the 1st install to clear sdcard was standart SD port. It is was created .secure_android folder in root path of sdcard

Then any of NativeSD port working without root issues

:D
[HD2 Android SD Development] timmymarsh:
Hey man, OK I'm a little confused lol, should I be deleting it creating something, sorry its been a long day with not much sleep :eek: I have that folder on SD root but it is empty?
[HD2 Android SD Development] wowrlz123:
I'm using 2 roms PA 2.0 and Cm9ight my question is will the roms slow eachother and if i boot different rom everytime will that bug them thanks in advance.
[HD2 Android SD Development] hutc:
methods to install

hi xylo this is how i installed it on the sd card (next time it will be a fast sd card cuurent one is class 4 sd card)

i divided sd card into fat 32 and ext4 in linux via disk utility

then flashed daf.exe of 4ext recovery to nand in windows 7

then flashed nand rom

in magldr menu set your SD BOOT directory to the 'Recovery' folder by choosing '10.services' , '1. Bootsettings' , 3. AD SD Dir in the Magldr menu.

boot into ad recovery

you are in 4ext recovery now flash the native sd roms and follow the instructions

reboot and go into magldr

in magldr set your SD BOOT directory to the 'Native sd' folder by choosing '10.services' , '1. Bootsettings' , 3. AD SD Dir in the Magldr menu.

then back to magldr main menu ,press boot to ad sd and

voila you are in native sd rom : thank you secureret and xylo for your immense help
[HD2 Android SD Development] datagr:
For 100% fix root issues, in all your nativeSD roms, I would suggest you to backup your apps and settings and reformat your sdcard ext4 partition.

Permissions issues usually creates multiple problems in multiple locations(apps,settings,formation of sdcard).

I have seen a trustful guide for creating correctly an ext4 partition.

Just remember to format your ext4 partition inside the recovery tool (you should format the [sd-ext partition] and NOT(!) the [sd-ext2 partition] (this one is your WP7 rom in NAND)).

For your information, I have the same setup on my phone (WP7 in NAND and 4 nativeSD roms in native EXT4 partition).

The nativeSDMultiBoot app needs of course root access to work. :)

I hope I helped and don't hesitate to ask any questions. :)

---------- Post added at 12:26 AM ---------- Previous post was at 12:23 AM ----------

Each rom does not affect the others.They are not active ALL together at the same time. :)

So don't worry, you can have as many roms you want in your ext4 partition without any slow down in performance.

---------- Post added at 12:41 AM ---------- Previous post was at 12:26 AM ----------

Hello,

I have no idea how clk works since from day1 I have been using magldr loader.

I have seen in the zip folder 2 files (one of them is an .sh file).

If you switch rom from the nativeSDMultiBoot app,

then don't reboot,

then unzip somewhere those 2 files that are inside the flash_sboot_v2.zip,

then run the .sh file that it is the tools folder and

then reboot,

will will it work for you?

I can't do any tests since I am on magldr as I said. :)
[HD2 Android SD Development] Szczepanik:
NativeSD on WP7 + NexusHD2-ICS

c1cl0n has posted a step-by-step guide and video for "3in1 [WPH7 + ICS SD + ICS NativeSD] on Your HTC LEO" in the thread [REF] Tutorial: How to partition sd card to run wp7 and android from same sd card

Tytung has posted a NativeSD version of his [17.Sep.2012][MAGLDR/SD][NativeSD] NexusHD2-ICS-4.0.4-CM9-HWA-SD V2.7

Our thanks to both of them. Enjoy!

Cheers

Tom
[HD2 Android SD Development] NYLimited:
Quick question.. I confirmed on my test this problem exists in 2.2.2.0. Do you know off-hand if it is also in the 2.2.1.4 version? Just curious... :)
[HD2 Android SD Development] ictimai:
NILFS Super thread

So, the NILFS Super thread has been started in Q&A. I hope it'll help this sensible concept rather than harming it...

Xylo, why to care about NAND anymore if NILFS on class10 SD performs as fast as NAND still having other superb benefits? Then we should think how to utilize NAND for something quite special... Not to mention WP, WM ;) or maybe however should such ideas like swap on NAND etc. receive green light?
[HD2 Android SD Development] Xylograph:
You have a very strange way of installing all of this m8,

So, you have flashed recovery to your (wp7?) nand via DAF.exe to run recovery from sd ??

You should either install recovery to (android) nand or run recovery from sd when using any other OS on nand..

I wonder if your WP7 install is still working or is there some additional space in magldr reserved for android recovery no matter what os is on (the rest of) your nand?

Anyway, it's nice you have it working ;)

Yes, this 'magldr issue' of not able to backup/recover the boot partition should also be present on the 2.2.1.4 version..

However cLK users should not have any problems using these recoveries ;)

Maybe (not tested yet) if we change the yboot to rboot it does work on magldr..

I hope to find some more time this week to investigate this further..

I could ask you the same question.. Why do you only seem to care about this nilfs2 lately which could be a great stable reliable filesystem, but also one with minimal recovery support and compatibility.. ?

Not to speak about browsing/changing things on that particular nilfs2 partition on a 'desktop os' other than linux.

For example.. If a windows (desktop/phone os) user would have a problem on their nilfs2 rom installation and I would like to see the contents of that partition to see if everything went ok ?

"Uhmm.. wait a sec.. let me install ubuntu.. get my sdcard out so.. I'll be back in a second ?"

Makes me wonder...Are you actually able to mount and browse that nilfs2 partition from within a nand android installation ?

Don't get me wrong.. I do like the idea of improving this method and you guys experimenting with a different filesystem, but from a rom dev point of view this is just not usable at the moment for making quick adjustments to get things done..

Anyway, I will drop by from time to time in the new 'nilfs2' thread to check for new developments and I hope there will be more recovery/android support in the near future ;)
[HD2 Android SD Development] NYLimited:
Understood. I wasn't rushing you. Just curious about the difference since CWM Recovery can write it.

---

Turn on, tune in, drop out... (via Tapatalk)
[HD2 Android SD Development] securecrt:
I totally agree with you!

The ext4 is the best choice for current stage, make it as simple as possible is the basic idea.
[HD2 Android SD Development] kwag:
Hi Xylograph,

Maybe because once a recovery utility adds support for nilfs, we can have the option to either format as ext4 or nilfs2?

Yes, that's a good point, but for regular users!

For advanced users who wish to have nilfs2, we could have the option :)

Yep, for sure. Let windows users stick with compatible file systems ;)

You're right! Again, not an issue for us on Linux. For Windows users, let them stay on Windows, so they won't have issues :)

Yep. Kernel support has been in there since 2nd February 2011, but no binaries, until now!

So yes, if you just put the file mount.nilfs2 in xbin, that's it! you can mount the partition.

From a ROM dev point of view, maybe it can be transparent!

The same way gapps are installed after a ROM installation, a ROM could be installed with CWR that supports nilfs2, so that is chosen at installation time.

Once that is done, a "nilfs_branding" .zip is also installed with CWR that basically installs the binaries and config files, and that's all!

As a matter of fact, I vote to all devs to put in the binaries related to nilfs in every ROM, because they are plain and simply small, and barely occupy space.

If that happens, then all that is needed is to support nilfs2 to format the partition on the recovery utility. That would be it!

So a user simply selects EXT4 or NILFS2? during installation, and it can't be easier than that.

Every regular user or advanced user now would have a choice, and everyone wins!

What do you think?
[HD2 Android SD Development] securecrt:
I dont know why you guys are so happy with nilfs2 from the benchmark results it is slower than ext4.

maybe you guys can say that the nilfs is already improved after that benchmark did. but the nilfs driver is very old. no one works on that for HD2 kernel.
[HD2 Android SD Development] kwag:
Hi securecrt,

nilfs2 is not old or outdated. It's part of the Linux kernel tree, and has been for a long time.

I am very happy with this, because even though nilfs is slower on some things compared to ext4, it's faster on other things.

But that's not the issue. The issue is about data reliability and wear-and-tear of media.

nilfs2 checksums all data and metadata (everything!), just like btrfs, but ext4 does not.

nilfs2 was engineered for SSD media, and for that matter, it server it's purpose on our MicroSD cards.

ext4 will rip and wear a SD card, whereas nilfs will extend the life of the SD beyond foobar!

And to put a tip on the iceberg, if we can just have ONE snapshot say every 24 hours just to conserve space, and something screws up during an update or some software screws up, I could just roll back to a prior snapshot, and everything is back as if nothing had happened.

Try that with ext4!

---------- Post added at 04:16 AM ---------- Previous post was at 04:08 AM ----------

BTW:

"nilfs2 Forked from torvalds/linux

NILFS2 filesystem branch for Linux kernel

Last updated 25 days ago"

https://github.com/konis
[HD2 Android SD Development] securecrt:
the git source is linux-3.6-rc3.

even the nilfs2 has been proved is better than ext4 for some reasons from the latest development, but we still can't see the advantage in HD2, becasue we are using very old kernel 2.6.32 the nilfs2 driver is outdated.
[HD2 Android SD Development] kwag:
Yes, I know. I was just pointing out the current state.

Still, the advantage even with the older driver, is the way it writes to the media. It's a log structured file system, which is completely different than the way ext3/4 write to disk.

And the driver we currently have, still supports all the things I mentioned, and are by far (by design) more advanced than ext4.

All I can say is that I'm currently on CyanMobile 1.0 with nilfs running, and I won't go back to anything else, even if I have to build my own initdr's! :)

This thing runs so smooth, and the responsiveness is just incredible. I've never seen my HD2 run like this :D
[HD2 Android SD Development] securecrt:
I must say if you change to ext4 you will feel more faster.

look this benchmark results(it is based on 3.2 kernel tree):

http://www.phoronix.com/scan.php?page=article&item=linux_32_nilfs2&num=1

the nilfs2 is slower than ext4 at most of the test cases.
[HD2 Android SD Development] kwag:
Try it on your HD2!

Then tell me what you see :)

All I can say is that I can feel the difference, maybe because nilfs uses less CPU than ext4? I'm not sure, and I haven't done any benchmarks, but another user also reported the same thing I'm experiencing, so that makes two of us who have seen a difference.

And really, I don't care if it's even a slightly slower in speed than ext4. I rather have a stable and crash free fs than a fs that can ( and it can! ) fail.

I know chances are very low with ext4 journal, BUT there's no checksum on ext4 data.

But nilfs has:

Checksums

Immediate recovery after system crash (no fsck needed at all!)

Continuous (tailored) snapshots of the fs.

None of these features are provided by ext4, so I'd rather loose some (negligible) I/O disk speed and win those features!

PLEASE, give it a try. Install on two SD cards. One nilfs and the other ext4, and take them for a spin ;)
[HD2 Android SD Development] gazzacbr:
the argument for nilfs2 wasnt only based on speed.

the speed was a secondary and practically was as fast as ext4

the advanages were security of data with continuous logging and snapshots, which means you do not need fsck (in theory) and wear levelling by not overwriting each time.

given the limited life of the HD2, the cheapness of sd cards, and the rewrites in the order of 100,000s is this really a problem?

maybe the fastest filesystem, which could be ext4, will be the best but will 'break' the memory after say 25 years.

can anybody guestimate some numbers as the whether the mtbf of an sd card or even nand is significant in real terms?

http://www.blah-blah.ch/it/general/nilfs2-filesystem-performance/

EDIT: sorry kwag, i started typing this at work before you posted. i have repeated some of your comments ;)
[HD2 Android SD Development] securecrt:
I suggest to use the same sdcard and make both ext4 and nilfs2 partitions install the same rom to different partition and make a benchmark.

can you post your Antutu result with your current ROM?
[HD2 Android SD Development] kwag:
You missed one of the most important factors: Data checksum of everything.

You could have a "write" and corruption during the I/O, and that is called "Silent Corruption", because you will never know that it happened, until you try to access your file, and either see garbbage or an inaccesible file.

Nilfs works similar to ZFS ( and btrfs, for that matter ), where all data is checksummed.

---------- Post added at 05:06 AM ---------- Previous post was at 05:01 AM ----------

Here. More detailed features of what nilfs has to offer:

Fast write and recovery times

Minimal damage to file data and system consistency on hardware failure

32-bit checksums (CRC32) on data and metadata for integrity assurance (per block group, in segment summary)

Correctly ordered data and meta-data writes

Redundant superblock

File and inode blocks are managed by a B-tree structure

Internal data is processed in 64-bit wide word size

Can create and store huge files (8 EiB)

Block sizes smaller than page size (e.g. 1 KB or 2 KB)

Online file system resizing

I'll take that anytime over ext4!
[HD2 Android SD Development] Xylograph:
Well.. I am up for a test.. I've made my 3rd sd partition (mmcblk0p3) 512mb nilfs2.

Could you upload that nilfs2 converted CyanMobileX ROM to some place for testing purpose (or make a diff file like securecrt did) so I could give this a spin ?
[HD2 Android SD Development] securecrt:
:good: I am just too lazy to do this by myself.

I am trying to make the ext4 trim feature work on current kernel.

it was supported from 2.6.33 so I think it should not be very hard to port it to our baseline. :laugh:

you can google "ext4 trim" to get more info about it.
[HD2 Android SD Development] HypoTurtle:
Have attached the diff file modified for mmcblk0p3, should be fine for an initial impression (haven't attached the files needed for the cleaner to run)
[HD2 Android SD Development] Xylograph:
Yeah I will give it a shot..

You lazy ? nah..certainly not if you are focussing on the kernels m8 :good:

Maybe suprise us with a securecrt gingerbread kernel while you are at it ?? ;)

Thanks, but shouldn't there be a couple of bin files (with probably extra permissions inside the updater-script) included ??
[HD2 Android SD Development] kwag:
Here you go. I can't compare to anything else now!, so this is CyanMobile 1.0 running on nilfs. No overclock or nothing:

http://minus.com/lHJRyDHtaPcfT

EDIT: My SD card is a cheap "PNY MicroSD 16GB HC"