yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] kokotas:
I'll try to describe it according to cLK version, without having tested all:

Original cLK v1.4:

Can have only one boot partition which can be used by a kernel

and it is used by the kernel of the NAND Rom.

In order to switch SD Roms,

the user has to flash each time the kernel of the SD Rom to 'boot' partition, losing the access of the NAND Rom.

in order to switch between NAND and SD Rom,

the user has to flash each time the kernel of the NAND Rom to 'boot' partition, losing the access of the SD Rom.

Stable mainline cLK v1.5:

Can have two boot partitions which can be used by a kernel.

Usually the 'boot' partition is used by the kernel of the NAND Rom, so that leaves us 'sboot' partition for flashing a kernel of an SD Rom. But if someone wants to use 'boot' partition for flashing a kernel of an SD Rom, there is no restriction except that he will lose the access of the NAND Rom.

In order to switch SD Roms,

the user has to flash each time the kernel of the SD Rom to 'sboot' partition, without losing the access of the NAND Rom.

In order to switch between NAND and SD Rom,

the user enters cLK menu and selects from which boot partition to load the kernel.

WIP cLK v1.5.x:

Can have 8 boot partitions which (in theory all) can be used by a kernel.

Usually the 'boot' partition is used by the kernel of the NAND Rom, so that leaves us 7 extra partitions to flash a kernel of an SD Rom. Whatever was referred in cLK v1.5 case for 'boot' partition applies here too.

In order to switch SD Roms or switch between NAND and SD Rom,

the user has a multiboot menu shown at startup where he selects from which boot partition to load the kernel which is flashed only once and not at every switch.

I wrote that script (mkbootimg.sh), as the procedure of installing the Rom's kernel.

So your idea is : each time someone wants to "reboot to another rom" he will actually flash the kernel of the Rom to the extra boot partition(lets say it sboot).

That is a nice idea for cLK v1.5 which has only one extra boot partition.

And it makes useless all the work I've done by adding multiboot feature in the last version. C'est la vie...

Anyway, be aware that the cmdline returned from the mkbootimg.sh is not ok.

Since getting the name folder of the rom that user wish to switch is easy,

skip the quest for the cmdline from startup.txt and just set the cmdline to

"rel_path=%the_name_folder_of_the_rom_that_user_wish_to_switch% nand_boot=0"

I think it will be ok. I'm just not sure if 'nand_boot=0' is required for the NativeSD Roms. Try and see.

Well all boot partitions (boot,sboot,etc.) are able to hold a kernel which will be loaded. I think the kernel should be able to boot a Rom placed on the card, given the right cmdline arg(rel_path=).

Regards!
[HD2 Android SD Development] Team-Leader:
I try al longe time to flash 4EXT Recovery for android NAND users in clk with the HD2 toolkit.

But i cant finde the option to do this.

Can someone please help me.
[HD2 Android SD Development] Xylograph:
The nand 4EXT recovery I've made available is flashable via recovery itself...

Shouldn't be that hard... especially when you are on clk.. Make sure your recovery partition has at least a size of 7mb and you should be good to go.
[HD2 Android SD Development] Looki75:
Quick question for you Xylo,

I have a NAND ROM which is using an A2SD script (apk and dalvik are in sd-ext).

If I install a NativeSD ROM, my understanding is that the /system and /data will be store in sd-ext.

Question: are the NativeSD ROM's /system and /data stored in a specific folder (eg 'sd-ext/NameOfTheRom/')?

In other words: can the NAND ROM+A2SD and the NativeSD co-exist at the same time without interfering one with the other?

(and so being booted separately from MAGLDR)

Thanks for your help
[HD2 Android SD Development] Xylograph:
Exactly..

The NativeSD Rom wil be installed in a predefined 'rom-name' folder.
[HD2 Android SD Development] Xylograph:
I don't know about how android will react on the Unallocated partition, someone should test it...

Also I don't think fat32 partition is mounted as mmcblock, maybe just /sdcard or mmcblk0.. securecrt will probably know more about this..sorry

---------- Post added at 10:15 PM ---------- Previous post was at 10:12 PM ----------

If you don't want to wait for long you can do some experimenting yourself.. You'll need the PPP connection stuff and some extra permission entries in the updater-script.. which you can probably 'copy' out of a current kernel (cLK) package ;)
[HD2 Android SD Development] sly2:
how 'Flash via recovery'?

Sorry for my dumb question, but how 'Flash via recovery'???

I use sd images (magldr) already very long, but i dont tryed any nand and have no idea about it...
[HD2 Android SD Development] HypoTurtle:
It's not, unless i'm missing something (run 'mount' in terminal and take a look). The fat mount would be the vold/179.1; and I think that's pretty standard for all roms.

Depends on what you have on NAND, currently only works if you have android running on magldr and thus have CWM (or similar) recovery.

In terms of benchmarks with AnTuTu RAM score is 288 for me, the sort of score gotten from sd roms, nand gives around 500
[HD2 Android SD Development] clio94:
/system is read only?

bytheway i managed to get this rom,boot from clk.I know nothing about scripts and programming,but i can combine things.The procedure i followed

1.i installed rom via magldr

2.In folder /sdcard/Nativesd i put a startup.txt file with commands

set mtype 2524

set ramaddr 0x11800000

set ramsize 0x1e400000

set initrd_offset 0x00a00000

set KERNEL zImage

set initrd initrd.gz

set cmdline "rel_path=Nativesd"

boot

3.Ι installed clk bootloader from kokotas http://xdaforums.com/showpost.php?p=21821506&postcount=883 and also put in sdcard the file flashsboot v2.zip http://www.mediafire.com/?nhyausx0p5whu

4.Ι made a sboot partition in clk.

5.I go to recovery and flash flashsboot v2.zip.This file can flash in sboot partition the zimage and initrd.gz you have in a folder and also can read the startup.txt parameters.

6.I went back to clk and choose to boot from sboot partition

7.Rom boots ok but no data connection.I tried to copy the ppp files and i saw that it didnt let me to do it

8.Install a nand rom (tytung v2.7) and then i installed link2sd,to be able to have ext partition mounted in nand rom.Then i copied manually all the files for ppp connection in sd-ext/aokp/system,gave the correct permissions and data now works ok

The only problem for me now is the strange behaviour of wifi,that i described also in nand rom thread.

Τhe next test i will do maybe tomorrow is to see if the rom will boot from haret.exe in wm.The speed of this rom is a-m-a-z-i-n-g.
[HD2 Android SD Development] Xylograph:
Not anymore with thanks to jjblaster3 pointing me in the right direction :)

Ok guys.. another possible breakthrough..

I've ported 4EXT recovery to SD which is also the recovery I use for testing all this stuff and I really recommend using it..

This is for all WP7 and Magldr users who either have no or a different recovery..

Please download 4EXTRecoverySD and unpack it to the root of your sd-card..

Set your Magldr AD SD Boot folder to 'Recovery' folder and Boot from SD

Recovey will startup.. flash the ROM package and choose SD-EXT install (default)

Reboot and set your Magldr AD SD folder to 'NativeSD' and Boot from SD.. the ROM should now boot.

If you want to enter recovery again to flash another ROM or something else..repeat the above steps..

I have no idea how android will handle WP7 sd-card partitions so I recommend to try it on a different sd-card with a 1.Fat32 and 2.EXT partition.

Please report and good luck !

Tomorrow I will start working on haret and cLK compatibility (PPP) so these users can try this also :)
[HD2 Android SD Development] YamazakiRobert:
can you make a .img for de 4ext recovery?

i have tried the aokp version on a 1.5 gb ext4 on class 10 card a noticed the system more realiable

i have played too dead triger and worked great

thanks for your hard work!
[HD2 Android SD Development] wis1152:
Has anyone got this to boot on class 4 sd card?

EDIT: scrap that got it booting now:D:):D:)
[HD2 Android SD Development] Xylograph:
Check this thread for the 'nand' version..

Yes I am using a class4 16 gb sandisk sd card.. works fine... try using 4ext recovery to see if it works ;)
[HD2 Android SD Development] Robbie P:
Same here, booted fine. 16gb c4
[HD2 Android SD Development] wis1152:
Working now:D thanks:) This is fast:D
[HD2 Android SD Development] Robbie P:
Agree it is fast. Although funnily enough, I get the same antutu score for the portadroid version, which was also fast:confused:

Congratulations Xylograph and securecrt, LNE team may soon be unemployed:highfive::fingers-crossed::)

Edit; WP7 works ok after, separate sd card boot.
[HD2 Android SD Development] ivica86:
Fantastic achieve , Xylo and Securecrt you are the best :D :D :D :D :D
[HD2 Android SD Development] seaman2k:
great work it is easy way i like it :)
[HD2 Android SD Development] securecrt:
can you make some details description on how to make it with WP7?

I will put it to Q&A section,thanks.
[HD2 Android SD Development] securecrt:
ideas for WP7 user to use NativeSD ROM

@Xylograph

I think the WP7 users have severel partitions on their SDCARD already, so if they make the sdcard an ext4 partition it will not be the mmcblk0p2 , maybe is mmcblk0p3 or mmcblk0p4 ,

I think in this case we can add a boot cfg file in /sdcard/NativeSD dir , each time the initrd.gz is loading check the /sdcard/NativeSD/boot.cfg to find is there any contents in it, for example the user want to boot the ROM from mmcblk0p3 , we use the users setting from that file otherwise we use the default mmcblk0p2,

for the installer , I can change the install.sh also use the same idea , read the user defined cfg and install the ROM to the right partition.

It seems not difficult to do this change. But I need some WP7 users to test it.

Xylograph will help you guys to create a ROM for testing purpose.
[HD2 Android SD Development] ictimai:
Is it true magldr doesn't allow for charging with completely discharged battery? If it is the case then, Xylo, let me aks if your concept tends to make SD-ROM boot also with cLK as the main loader eventually? If not can we get it with WM6.5? (Personally prefer WM6.5 far more to WP as it yields much more freedom to unharnessed users ;) )

Another question please: will this project give us SD Androids equally fast and battery-savers as NAND versions are? Please refer to this disturbing discussion
[HD2 Android SD Development] melando:
I have some idea as I am using a swap script which checks for the linux swap position and appears to report in a log file where it is. In my case, /dev/block/mmcblk0p2 (on top of WP7 partition and FAT partition). As securecrt says we could probably use a similar approach.

So all I need to do is resize and convert to ext4.

Let me know if it would help to post the script as an example (it was from here: http://xdaforums.com/showthread.php?t=1630083 )
[HD2 Android SD Development] Robbie P:
I have been booting from separate cards.

Now I have partitioned my 8gb card with 2gb FAT32 first, 1.5Gb ext4 and 4gb WP7 last, all primary. Will see how it all goes.:fingers-crossed:
[HD2 Android SD Development] melando:
Hope you can mod the PA build for native SD :)
[HD2 Android SD Development] gigsaw:
Question: is the speed depending even On the SD reader present on the phone or only on the SD card? I don't know how fast it is the reader...but if it has a limited speed, will it be a method to encrease it?
[HD2 Android SD Development] Team-Leader:
But how can i make a recovery partition or set the size?

Only had an 14GB FAT32 and an 1GB Ext4 partition on the sd card.
[HD2 Android SD Development] Magic2010:
You have to go to cLK menu and resize the recovery partition.

I advise you to install kokotas black cLK first if you want to enter "Nativesd world"

Here´s how to install a cLK: http://xdaforums.com/showpost.php?p=20519350&postcount=3

Where to download it: http://www.mediafire.com/?nhyausx0p5whu#tzg7whl9wwaih

But I advise you to do a bit of extensive reading about all this before you do anything.
[HD2 Android SD Development] bojanbl:
4. shell script (makebootimg.sh) combines ram disk and kernel:

mkbootimg --kernel /sdcard/NativeSD/zImage --ramdisk /sdcard/NativeSD/initrd.gz --cmdline "$cmd" --base 0x11800000 -o /sdcard/s_boot.img (I executed this in terminal and it created s_boot.img on scard

7. flash_image sboot /sdcard/s_boot.img

I am still experimenting, will try tomorow, btw I manage to update clk via commands in terminal flash lk /sdcard/lk.img
[HD2 Android SD Development] poyensa:
Thread cleaned a bit. Please stay on topic, dispersed information helps to nobody. Thanks for your collaboration!
[HD2 Android SD Development] clio94:
good idea and it seems with a little fine tunning will work ok.

i tried this mkbootimg --kernel /sdcard/NativeSD/zImage --ramdisk /sdcard/NativeSD/initrd.gz --cmdline "rel_path=cyan" --base 0x11800000 -o /sdcard/s_boot.img and it create a s_boot.img file

then i tried

flash_image sboot /sdcard/s_boot.img but i had a message "partition not found. error -1"

then i tried

flash_image boot /sdcard/s_boot.img and now in boot partition i have the kernel from cyanmobile x rom and also in clk says kernel @ boot(cyan)

so the other partitions (sboot,tboot) maybe need somehow to get mounted in order to be recognized from the rom terminal? or if this is not possible maybe we can use twrp recovery to mount the partition in recovery and flash it from there
[HD2 Android SD Development] datagr:
Could you try this apk pls in clk and tell me how it goes? :)

Before you click the apk pls copy the mkbootimg.sh and mkbootimg in the sdcard/ (get them from 2nd post from Xylographs guide about clk)

Then install the apk and test it.

Click switch

then choose which rom you want to switch

then click CLK

then click reboot

update1 : Quick fix redownload pls and retest :P

update2 : put the 2 files (mkbootimg.sh and mkbootimg) in nativeSD folder and download again the apk that I have attached.This one it should work fine with clk! :)

update3 : clean up folder /tmp just in case, so please re-download the apk :)

update4 : quick fix for command string code. re-download pls and test :)

update5 : apk removed temporarily until I have a confirmed answer from the testers for clk functioning. Please be patient until tonight that I will release the final version 5. :)
[HD2 Android SD Development] datagr:
By the way, it is so hard to develop blindly...I can't test anything that I am coding... :confused:
[HD2 Android SD Development] HypoTurtle:
Have you ran 'cat /proc/mtd', it might show what partitions are named as.
[HD2 Android SD Development] datagr:
tell me pls your opinion about this procedure :

mkdir tmp
cp sdcard/nativeSD/mkbootimg.sh tmp/
cp sdcard/nativeSD/mkbootimg tmp/
chmod 777 tmp/*
tmp/mkbootimg --kernel sdcard/nativeSD/zImage --ramdisk sdcard/nativeSD/initrd.gz --cmdline "rel_path=name_of_rom_that_will_boot_after_switch" --base 0x11800000 -o tmp/s_boot.img
flash_image sboot tmp/s_boot.img
rm -rf tmp/
[HD2 Android SD Development] HypoTurtle:
That would be what I'd follow, at a guess I'd say clio94's issue: flash_image sboot /sdcard/s_boot.img but i had a message "partition not found. error -1" is that he was trying to flash sboot while running NAND. Could you clarify clio94?

I think your app following those steps, from within a running NativeSD ROM would run as expected.

Ignore that last post, I think I misread something =tired
[HD2 Android SD Development] Szczepanik:
Screenshots look good thanks (WM6.5). Might be nice to be able to show the ROMS in alphabetical order. Great job thanks!

Cheers

Tom
[HD2 Android SD Development] clio94:
app doesnt work because sboot partition doesnt appear in the rom.I tried it while i was running cm9ight from sboot and nexushd2 from tboot

see picture

edit

it works.It seems that mtd is limited to 8 devices.After erasing tboot and vboot,sboot appeared and it work ok! Although it seems that rel_path doesnt need to be there as i see that instead of rom name it writes in partition something like rel_path="java.io.outputstreamwriter"

You did a great job.Thank you very much
[HD2 Android SD Development] arungk2:
sense native sd

can sense roms be ported to native sd :confused:

are there any native sd sense roms

i have not found any please help
[HD2 Android SD Development] kaiserlein:
It's working like a charm :thumbup:
[HD2 Android SD Development] melando:
Xylo I for one am waiting to see PA1.5b and 2.12 ported, till then PA2.00 is working well
[HD2 Android SD Development] Xylograph:
Thanks again for your time and effort, great work !

So.. in theory.. you could flash a complete rom to your nand using a NativeSD ROM :D

Sure, Ask your favourite sense dev to do it... Actually.. since these sense roms tend to be so bloated they hardly fit on the whole available 'nand space' .. this NativeSD should be a dream come true for sense users... I am suprised nobody has picked up on it yet...

You mean 1.6 and 2.13, right ? Working on it, but I am very busy so no eta..
[HD2 Android SD Development] melando:
Oops I'm a day out of date...

I did not ask for ETA (of course) - NativeSD advances have been more significant.

Would be great if you are able to have ROMs sharing app.s and data (even phone messages, call log etc.) as far as possible - that would really bring switching ROM to life. So long as the data is 100% secure (no I don't mean n***s)
[HD2 Android SD Development] fahd_freak:
+1 to that...
[HD2 Android SD Development] Xylograph:
Sharing apps and especiall app-data will always be very risky and not 100% guaranteed..

It's the same when moving form one rom to another without wiping your /data partition.. and as you know.. I often say:

"A clean install is always recommended"

With sharing app-data it actually will never be a 'clean install' so this will need a lot of testing and proper implementation... for that I could use some help...

Phoen!x ??? :)
[HD2 Android SD Development] jully3881:
can i say something , yes i want say something..
[HD2 Android SD Development] giovanne:
I was thinging of something. Sorry if it is already possible.

Maybe the time will come and there will be a PA in e.g. version 2.13 for NativeSD.

Would it be possible to install this in a folder like e.g. PA213 instead of PA? Or simple switch the name of the existing ROM maybe from PA to PA200 ?

Then there will be the possiblility to multiboot PA. One currently using and the new one for testing and maybe switching it to PA if it is running well.

And that would give me the possibility to boot in e.g. "Productive" and "Testing"-PA Rom ;)

At the moment I only use the PA rom. Haven't the time to have a look in alle the ROMs :crying:

And maybe the apps and data can be shared between the PAs :p
[HD2 Android SD Development] bojanbl:
Not in theory it is practically possible and you can even flash latest version of CLK from android terminal app

following next sintax:

flash_image partition_name /path/image_file.img
[HD2 Android SD Development] datagr:
lol sorry for that stupid coding error! :P

java.io.outputstreamwriter is the java engine to export a string from a text file!

I will fix it today when I will get back from work.

By the way can you tell me if it is working the app in clk?

I need a clean answer because I am confused after the post edit.

What do I need to fix in the app to have it ready for all clk users?

P.S. I will add also an "about" button with all the people that help on making this possible the version 5 (if it's ok with all this) :)
[HD2 Android SD Development] clio94:
App is working for clk.If someone has boot and sboot partitions,your app will work ok.The only "bug" is that in rel_path= line.
[HD2 Android SD Development] kaiserlein:
Can confirm, as I wrote on previous page the app is working like a charm :D:good:
[HD2 Android SD Development] ric69:
Hi guys and thanks for your excellent work :good:

I saw that EXT4 Recovery can make 2 sd-ext partition, is there a way to make one for nand and other to nativesd ?

That's probably not possible, but I ask maybe since I corrupted my nand version this morning (and all nativesd too, because formatting sd-ext give us no chance to keep something ... ok that's not the first and last time I loose everything :laugh:)
[HD2 Android SD Development] Magic2010:
It might possible if you use Ext3 + a script that uses Ext3.

But don´t know for sure, maybe someone can confirm this.
[HD2 Android SD Development] Dala11:
Very cool stuff!

Just one question, what happens when the phone reboots without you noticing? Will it then boot the rom on NAND? That could be less then ideal..
[HD2 Android SD Development] datagr:
Hello all,

Please download version 10 with latest updates. :)

Here is the link :

http://xdaforums.com/showpost.php?p=33815218&postcount=1392
[HD2 Android SD Development] ad2003:
Hi. How can I fix permissions for actual native SD ROM
[HD2 Android SD Development] timmymarsh:
Good work man, thanks for your hard work too :good:
[HD2 Android SD Development] Faith_G:
ROM Manager app works to fix permissions.
[HD2 Android SD Development] ad2003:
Thanks. Didn't know that. Can I also renew dalvik this way?
[HD2 Android SD Development] HypoTurtle:
Found these recoveries during my travels (same recovery just one updated/adapted), could they be of any use to us?

Original (Nexus 1 / other HTC devices) and HTC Desire looking at the full adb access and conversion of ext2/3 to ext4.
[HD2 Android SD Development] Xylograph:
Sure... if you can say something without insulting people..

Possible yes, but you'll have to modify the scripts..I am not going to give every new update release a new name.. if you don't like the new update flash back the previous version.

I am thinking to add this additional functionality.. so one can choose to either install the NativeSD rom to the mmcblk0p2 ext partition (default) or mmcblk0p3 (advanced) partition

I want to make the second (mmcblk0p3) option 'Filesystem independend' so people can experiment with different ones... should be used with caution though (especially for WP7 users I suppose)

Depends what you have on nand.. if you have Magldr/cLK I suppose you can set it to default boot from sd..

Thanks m8, Great stuff !!

Thanks, but I don't see anything 'new' we do not have already to be honest..
[HD2 Android SD Development] macs18max:
NativeSD is going huge now with most of the top roms getting there. Does anybody get this feeling that there should be a seperate section for nativesd. What I'm saying is under HD2 android developement we should have

HD2 Android NAND developement

HD2 Android SD developement

HD2 Android NativeSD developement

rite now reading feedback regarding NativeSD on different ROM is mixed with NAND section and SD section.

What say? ;)
[HD2 Android SD Development] datagr:
Is it possible to have a tester for that?

Version 5 multiboot app supports CLK.
[HD2 Android SD Development] ad2003:
Everything works fine here with unofficial cm10 since 1week now!

Thanks for the great work to you!
[HD2 Android SD Development] mootmetal:
for recovery i did set the boot for recovery... but after flashing the rom i cant access sd card to choose native sd for sd boot when i choose ad sd dir it goes back to magldr menu
[HD2 Android SD Development] LinChina:
Would it be possible to implement the re-boot function/button into SD Recovery directly from your tool, or has this been asked already ???

Cheers.....LinChina
[HD2 Android SD Development] strikelight:
I think the problem people said they had with that was that if you weren't near a computer, you'd be unable to boot into the actual OS, as you'd only be able to keep booting into recovery...

Would it not be possible though to modify the initrd.gz's of the recoveries to switch the required files to the previous running rom atleast? that way, you get a one time recovery boot, and then next time will boot back to the OS? datagr's tool keeps track of the current rom if i'm not mistaken, so it should be possible... Or am I mistaken in the functionality/capability of the initrd.gz files in the recoveries?