yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] walter79:
You can make a multiboot version for Milestone 2.

Only data partition is different for Milestone 2. It use mmcblk1p26.

I think Milestone 2 user will like it.
[Defy Android Development] TJKV:
So if I replace m11kkaa's fshook.init.sh with this script in /system/bootmenu/2nd-boot, I can keep the fsimages folder in /data?? That'll be really useful if sd card has insufficient space :) it might be faster too to run the virtual from nand...

But then the Multiboot managing apps won't work I'm guessing, so we are limited to one virtual system...

Unless I kept one virtual in /data, and the rest on sd card? Then switch the script whenever I want to switch b/w sd and /data!
[Defy Android Development] mihovil13:
Did anyone tried dual booting a linux distribution (or Ubuntu, like Backtrack 5) and a GB rom like CM7 or MS2?
[Defy Android Development] hackergnome:
Good idea! will try i think i have a Maverick Image in my hd... will search...
[Defy Android Development] mihovil13:
Ok, tnx, post results please ;)
[Defy Android Development] leodfs:
Sigh... The beneficts of a unlocked bootloader... not good dude, you made me sad. I think there is some work on ubuntu for defy, but for what i see it will not work on dual boot and you need one ubuntu running on pc.

With the changes m11kkaa did i think that's possible the manager i did will not work. As I will not update it anymore, anyone wants the source code to do it? Pm me.
[Defy Android Development] walter79:
[APP] Windows: Create Your Own Data.img Maker Application, +/- From Existing data.img

http://xdaforums.com/showthread.php?t=824154

Donload can found here: http://xdaforums.com/showpost.php?p=22622139&postcount=96
[Defy Android Development] joydeep1985:
With laterst CM9 nightly 0703 there has been a problem with dual boot. The root access option vanishes from developer options . However the root access option is not a problem when CM9 is installed as the primary rom itself .
[Defy Android Development] mihovil13:
I think you spelled it wrong, the latest nightly is from 17/03.

And, Quarx's releases seem to do properly with the multiboot option...
[Defy Android Development] joydeep1985:
Which quarkx's build working on multiboot ? Cause as far as I have seen the last Froyo build by Quark'x is 0803 build. Apprarently Multiboot doesnt seem to be working for GB builds. There are no root access available. The option under developer options for root access is also missing in epsylons latest builds only under one scenario (If i install it as a 2nd boot from custom recovery) . As as result I cant restore my apps widout root access and most important i cant access baseband switcher :( for changing baseband. :(
[Defy Android Development] adamo3957:
Any chance of a script for 2nd system with access to the nand data files

Ie primary ics milestone port

2nd system running the tablet interface version?

teamwork makes the dream work
[Defy Android Development] m11kkaa:
I managed to make a little GUI to choose system at boot.

This should make the whole thing a little bit easier :)
[Defy Android Development] joydeep1985:
wow that would be cool :D would you share it wid us ? :D
[Defy Android Development] m11kkaa:
of course, if it's ready. But there's still much work.
[Defy Android Development] trurl3:
Isn't it something like leodfs and royale1223 do?
[Defy Android Development] m11kkaa:
no, they made a multiboot-manager(I have the sources of that and I will use this in future to create/delete virtual systems).

My GUI is like a bootmenu on a PC. You get a list of installed operating systems and you can choose which one you want to boot.
[Defy Android Development] joydeep1985:
That would be really cool. But somehow i have some clarifications ask for .

1. If we multiboot . The battery percentages arent the same on each and every rom you have installed . Sometimes the battey percentage really falls at staggering rate . But on single boot its quite normal . I wonder it should be a bug with the roms on multiboot configuration itself . Sometimes the battery change is drastic i would attach an example of battery percentage later on with this post to show how does it behave.

2. IF you make a boot selection menu , that would be occurring before the ICS bootmenu isnt it ? so that we can choose the actual OS which we want to boot in .
[Defy Android Development] m11kkaa:
1. This happens because every system has it's own batterystats. If you are a long in system B and then you switch to system A he thinks he lost 20% of battery within 1second(as example). I tried to make global batterystats but currently I don't know a way todo that.

2. the selection-menu will be started after/by the bootmenu(with 2ndboot/2ndsystem -option). But you can set it as autoboot within bootmenu.
[Defy Android Development] leodfs:
Thay battery problem is not multiboot fault, at least not directly. If you just install a rom on top of other you may see same drops. Thats why they recommend calibration after every flash.

What m11kkaa is doing is something similar to grub, and this idea is very cool. It will probably be on 2nd-boot/system script, so it will not replace your bootmenu.
[Defy Android Development] adamo3957:
Correct me if I'm wrong but as far as I knew in regards to 1 the battery percentage is held by the system itself which means battery calibration needs to be done on both roms but then I think it would be confused when you boot into a second rom while the battery is half way?

teamwork makes the dream work
[Defy Android Development] m11kkaa:
With the difference that multiboot acts much later than a bootloader like grub because we can't change the kernel-args or boot custom kernels.

That's the reason why multiboot has to patch much things before it can boot another system-partition and why it can't be used with systems which use different kernels(you could call the mod a rootfs-changer if you compare it with normal linux-systems) :)
[Defy Android Development] trurl3:
That would be very good. I have try leodfs system, but copying fsimages to virtuals foler tired me at the end. Now I use royale1223 MutiBoot manager, but this has its own issues. For example - if after installing new ROM you change name of fsimage (i.e. add to it name of ROM you installed), you have to remember to make whole new empty fsimages folder on SD. Always there have to be folder fsimages on SD card. If not, your new ROM could gone. Once more - after any change of number of existing ROM's (i.e - deleting one of it from SD card or changing its name) royale's MultiBoot dosen't want to open. You have to uninstall it and install anew.

So I think your method probabely would be easier and safer to use. I will wait unpatiently :)
[Defy Android Development] leodfs:
Wow, how come just move one folder to another folder tire you:rolleyes:? You dont even need to do that, you just let a fsimage.zip in the virtual folder and extract there, just renaming for what you want. After extracting it and selecting it on manager you could latest recovery(for install a new system)/2nd-boot from it.

My theory is that you got it wrong. How are using my manager to switch virtuals and installing a new one?
[Defy Android Development] antukubo:
i'm using leodfs method and got no problem at all (not even tired..;))
[Defy Android Development] trurl3:
Maybe I am wrong, but using m11kkaa's multiboot.zip it's possible to have only one virtual ROM in /fsimages on SD card. And each new ROM one have to install in fresh empty /fsimages on SD card. Assuming someone use multiboot manager (either yours or royale) it is necessary to do something with 'used' fsimages containing installed ROM's. In your method /fsimages with installed ROM's have to be copied to /virtuals folder then one may change name of /fsimages to adequate ROM name. In roayle's method it's enogh to 'extend' name of original /fsimages. Anyway, in this case there is still need to have on SD card one copy of /fsimages folder (either empty or with installed ROM) lest it not 'vanish' from SD card (proved).

As you suggest it is possible to have in /virtuals folder copy of fsimages.zip but it takes place... and still there is need to copy installed ROM's to /virtuals folder as multiboot.zip need to have /fsimages in root of SD card. Am I wrong with it? Is it enough to place empty /fsimages in /virtuals folder?
[Defy Android Development] m11kkaa:
Because the changes I made are VERY huge I want to let some of you test the new version before I release it.

If anyone wants to make a beta-test please PM me. thanks.
[Defy Android Development] adamo3957:
Ok I've been trying to think of a way to phrase this idea but all I got is this,

Is it possible to extend the multi boot script in such a way as to allow flashing of a kernel ie,

Enter boot menu,

Select rom to boot,

From there multi boot goes into clockwork mod and flashes the boot.img associated with that rom,

Reboot,

Boot into selected rom,

The only thing I can see with this tho is we would have to run all roms from the SD card as unless the boot img is backed up of nand and restored when nand booting then the nand rom would purely be used for the boot menu

teamwork makes the dream work
[Defy Android Development] m11kkaa:
I have enough beta-testers now.

@adamo3957: That's a way but I just think it's a little bit crazy to auto-flash a kernel and then rebooting the whole system until you can boot your selection.

Maybe I'll add this feature in future but for now I have other priorities.

I hope, that someone will get a working kexec in future. This would make the whole bootprocess much easier :)
[Defy Android Development] hackergnome:
hey there a really amazing thing with this mod...

If i use multiboot on never cm9 or cm7 nightlies with "++++Go back++++" feature in recoveries i get two recoveries

Like if i flash argen2stone on sd card i get argen2stone bootmenu of i press go bacl in custom recovery...

If i press go back in stable recovery i goto cm bootmenu
[Defy Android Development] leodfs:
Now I get the "tire" part. Sorry dude, I will try to explain things the way I should from the beginning:

0-) This one really big and annoying explanation is only for my manager. If you want to install royales after, you have to flash m11kka's multiboot again. So, for now, don't mix things :)

1-) Flash m11kkaa' 0.4 multiboot on stable.

2-) Open my manage after boot. If you just flashed m11kkaa's it will show fresh on the right of the string "Active: ". That is just right.

3-) Now a inner explanation: That list on manager are from folder inside folder "virtual". In a really very simple way to explain, m11kkaas script has one part where is defined the path of virtual (/mnt/sdcard/fsimage) that will replace the partions from nand. That part is called in two different occasions:

a) when you enter custom/latest recovery.

b) when you 2nd-boot.

What my manager does is replace that part, for the folder selected on the list. So you don't need to have a fsimage folder on root of your sdcard.

4-) If you have a functional virtual on fsimage before install and running my manager, you just have to move it to /sdcard/virtual, and rename it the way you want. After that you will have to open the manager and select it. Now if you want to run it, just boot on 2nd-boot, because the proper files were updated.

5-) If you want to install a new rom from a fresh fsimage.zip images. Unpack fsimages.zip images for a folder inside /mnt/sdcard/virtual, for example /mnt/sdcard/virtual/wiuiv4. Now open the manager and select wiuiv4 from list. That is it, any zip you flash on latest recovery, from now on, will take effect on the images inside /mnt/sdcard/virtual/wiuiv4, because the proper files were updated, and when you boot with 2nd-boot it will be from there also.

5.1-) If for any reason the list is not updated with the folder you just created, is because the multiboot was openned before you created the folder. Just close it and open again. There is no exit button so it may have to be close with a task manager or android built in app manager.

6-) If you install m11kkaa multiboot.zip it will replace the custom locations inside script files my manager created and it will require a folder /mnt/sdacrd/fsimage again. To active the one you have under /mnt/sdcard/virtual, just run my manager after that and select desired virtual for 2nd-boot/latestRecovery to.
[Defy Android Development] brajesh.sharma87:
Thanks for expressing my words. I had this idea for so long.
[Defy Android Development] trurl3:
O.K. that's explain everything... So it is easier that I thought. Maybe will try it, but for now i want to try new m11kkaa's multiboot.zip.

Anyway you should post this explanation in your thread to avoid misunderstanding

//Edit - I did try and all works as it should... it's really so easy/
[Defy Android Development] adamo3957:
I think its workable but for now I agree with m11kaa, let's get a working selectable rom list first and then implement a kernal flash process

teamwork makes the dream work
[Defy Android Development] adamo3957:
Edit: for now you could use this process if you kept a nand with the boot image on your SD,

Just restore nand then chose your 2nd boot option, then to swap back restore the primary kernel then boot 2nd init

teamwork makes the dream work
[Defy Android Development] joydeep1985:
May be this as a sticky in original post can help others :rolleyes: . I guess that was really a nice post to avoid all sought of confusion between m11kkaa multiboot process and leodfs process . This should enlighten the new commers here :) :cool:

---------- Post added at 07:15 AM ---------- Previous post was at 07:04 AM ----------

However . if the batterystat.bin is maintained by the system . We can copy the real system battery stat into the virtual system batterystat.bin before booting :rolleyes: . I am jus giving an idea . Not sure if it would work on not . In case the batterystat is related to some more files just apart from batterystat.bin . We can spot those files and copy it to virtual system .That might solve our problem of losing 20% batterystat by virtual or real system.

Or may be we can put an option as in bootmanager to synchronise the real system batterystat.bin with virtual system batterystat.bin :D ( thanks to myself for my awsome noobness i got this idea :p ) just sharing the ideas which i am having . :D . Devs should know that more thn me :)
[Defy Android Development] adamo3957:
Mounting the battery stats is entirely possible as the cache recovery is mounted to provide reboot etc, its just the write to prevent the virtual mounting its own bat stats,

In fact it shouldn't be too hard, if I get chance tonight I'll have a play and see if I can get it to work, if it does I'll post up

teamwork makes the dream work
[Defy Android Development] royale1223:
I'm glad to see that multiboot scene is getting very active. But don't you guys think that instead of modding and hacking the current 2nd init bootmenu it would be better to create an entirely new bootmenu based on 2ndinit for multiboot purposes?

1) 1st of all the nomenclature :

The bootmenu will be called andgrub or something better.

The 2nd-init boot will be called the "nandboot".

The 2nd-system boot will be called "sdboot".

This will avoid a lot of confusion.

2) The interface

a) Main screen screen:

NAND BOOT 1

NAND BOOT 2

SD BOOT 1

SD BOOT 2

........

SETTINGS

RECOVERY

REBOOT

POWEROFF

b) Settings :

SET DEFAULT

SD BOOT SETTINGS

CPU SETTINGS

​

3) Functions :

a) AndGrub will check for all possible sdboots from sdcard at start and list them.

b) sdboot settings will contain kernel settings.

i) AndGrub will come with the commonly used moto kernels

ii)From sdboot settings you can set the kernel used for the particular sdboot

iii) AndGrub will flash the above kernel automatically in case of a mismatch.
​

c) Recovery will contain custom recoveries for all nandboots and sdboots

d) Everthing else is pretty self explanatory​

I'll start working on it as soon as the goddamn exams are over. Anybody who wants help is welcome. It'll take time but it won't be that hard because we can use many things from the current 2nd-init bootmenu.
[Defy Android Development] ganesh0992:
CM7

I used lastest CM9(Quarx's) for defy plus as Main rom and Cm7 by(Quarx's) as the virtual one....everything was flashed fine.

But

1. CM7- the virtual rom doesnt show any network...yes i switched the baseband to my region but still "no service"....

The same baseband works well in the CM9(Main ROM)....its just with the CM7(virtual one)...

2. The battery cylinder is empty with a question mark [?] <--- like this. I tried wiping everything but no result...the battery is always the same.

It works well in CM9(Main ROM) though.

Except the SIM and Battery everything is fine with CM7(Virtual ROM)

Whats the problem???

PS : Is it possible to use MS2Ginger as a virtual ROM with CM7/CM9??
[Defy Android Development] brajesh.sharma87:
search for the Quarx's MOD in this thread. With that u can surely multiboot these 2 roms.
[Defy Android Development] bds bamrah:
I have cm7.2 as base rom..can I install miui on virtual systm? Further can I shift from miui to cm9?

M on green lens defy,froyo kernel

AWESOMEDEFY@1.1GHZ
[Defy Android Development] joydeep1985:
yes you can install miui on virtual system . provided miui and cm7.2 kernel are the same i.e froyo kernel . In cases like your virtual is a GB build and base is froyo build , thats likely not to boot . As far as my observation as been there .

---------- Post added at 05:43 PM ---------- Previous post was at 05:39 PM ----------

Yes that would be definitely nice . But as far as i think and my idea goes . Keeping the current bootmenu as our primary base for work . We should proceed to make the new bootmenu :) . Your idea is awsome btw . if auto flashing kernel and batterystat.bin problem is solved We can literally put any kinda rom and any number of rom to multiboot . I am also a coder just wish i could know how to proceed into android development . I am literally boiling inside to code :p .
[Defy Android Development] m11kkaa:
Here you can see multiboot's sourcecode:

https://github.com/M1cha/DefyMultiboot

bootmenu's code you can find on epss or quarxs github :)
[Defy Android Development] ganesh0992:
Can anyone help out on this???
[Defy Android Development] adamo3957:
1 go a few pages back there is a post of quarx with a boot only script attached, download and use root explorer etc to place in correct folder,

2 have you tried wiping battery stats? Only thing I can recommend

teamwork makes the dream work
[Defy Android Development] joydeep1985:
You didnt reply which Defy you are using . Is it defy or Defy+ ? According to my suggestion You try reflashing and wipe cache / dalvik cache before you boot into the virtual system.

Edit : I saw in you signature you are using defy+ , Should not be any problem IMO .
[Defy Android Development] yamandude:
i'm here to help :)

i did make a video on how to actually multiboot your DEFY . so if anyone wants to see it you can ..

hope i helped :)
[Defy Android Development] joydeep1985:
There is a news guys ;) have seen by some senior member poster in CM9 thread ;) just have a look at it ;)

http://xdaforums.com/showthread.php?t=1519448

couldn't have been more happy for tht :D :D today
[Defy Android Development] m11kkaa:
I added a donation-link in the first post just for the case you want to spend me a beer ;)

New version is coming soon...
[Defy Android Development] ganesh0992:
I used the quarx's script and network thing works well....but still the battery shows a question mark like this -->> [?]

more ideas...it wud me more user frndly if there exists a option where the boot menu names can be customized by user...

e.g NAND BOOT 1 can be renamed as CM7 boot

SDBOOT 1 as CM9 boot

Stable recovery as CM7 recovery

Custom recovery as CM9 recovery

etc etc anything according to the user's roms...and rename it anytime as per the roms...
[Defy Android Development] leodfs:
Guys, just wait for micca`s new version. It is very cool. He kind of choose same line as I did to manage multiples virtuals : put them inside a folder. The virtual name is the virtual`s folder name. It is cleaner, easier to implement and easier to rename.
[Defy Android Development] m11kkaa:
The new version v0.5 is up in the first thread!

A working Multiboot-Manager is coming soon...

A tried to make some screenshots but for some reason that doesn't work anymore in bootmenu-mode.

Maybe someone can make a good instructions-video. Thanks!
[Defy Android Development] m11kkaa:
I managed to make screenshots and they are in first thread now.

Have Fun!
[Defy Android Development] mihovil13:
Do you or someone please know how do I use your tool to dual boot CM9 and Backtrack?
[Defy Android Development] joydeep1985:
here is some sought of confusion . How do i flash the zip into virtual system ? i mean when i select the custom recovery and i have 3 file systems . It doesnt know which of the three file systems to choose for ( say CM7.2 , WIUI , Whirerabbit) . So how does it know whc virtual system it should flash to ?
[Defy Android Development] leodfs:
There is a cmw option. When you click it it will open a list with your virtuals. Click in any and it will open a recovery that will take effect on selected virtual. That is it.
[Defy Android Development] joydeep1985:
Okay thats little weird . I wd try to explain my situation here . I was on CM9 As my primary boot and CM7 as my 2nd boot( Two other also were there i am not mentioning them ). Now i was following royal's multiboot manager . So i had fsimages folders under direct sdcard .

So what i did was created a multiboot folder and moved the fsimages folder (which contains the three image files ) to it . Then went to bootmenu >Stable recovery flashed m1kkaa multiboot 0.5 version .

Now henceforth the problem starts . I have the menu as when i go to boot as ->

[2nd init]

[2nd boot]

[2nd init + adb]

[2nd boot + adb]

No stock was here as mentioned like m1kkaa in the snapshots.

So still then also i went to [2nd boot + adb] Option.

IT shows me the following menu

CM7.2

MIUI

WIUI

Boot from NAND

Recovery(CWM)

Reboot

Now when i go to CWM . It jus reboots into CM9 . Now where did i go wrong ? oh yes and also CM7.2 if i select tht . IT shows its starting and just stands still (Makes sense since the path was moved manually it shouldnt work ). But Why CWM in the [2nd boot + adb ] menu gets unresponsive ? Inspite it has all the images ? or should i try afresh to copyu all those images and reflash ( virtual System ) ?
[Defy Android Development] leodfs:
Edited, deleted
[Defy Android Development] joydeep1985:
Just updated my post . IT reboots into CM9 doesnt stand still actually i was misguided that time . I would try in a minute by setting 2nd boot as default and tell whats happening .

Update : Have set 2nd boot as default and tried to select CWM from the menu . It just comes back to the menu and doesnt go to the recovery :(
[Defy Android Development] leodfs:
when it works, it indeed opens a menu a second time, but only with virtual names. After you select a name there it will open recovery.
[Defy Android Development] joydeep1985:
Yes ideally that should actually happen . But when i am selecting the CWM .It comes back to the same menu without opening any sort of recovery . Have i done anything wrong in the process ? or did Royale's Multiboot Manager messed up the boot settings ? :confused:
[Defy Android Development] leodfs:
Could you confirm that is figure 3 from OP that is appearing, not 4? Could you post a picture of after you press cmw, and that your virtual numbers are not odd?
[Defy Android Development] jpchopper:
I'm getting the same results. When selecting cwm recovery get kicked straight back.
[Defy Android Development] adamo3957:
Please try having 4 folders in your SD card under multi boot folder

Ie /sdcard/multiboot/folder1

Folder2

Folder3

Folder4

Then when you select cwm you should get the options

Folder1

Folder2

Folder3

Folder4

Choose a folder and it should take around 5-10 seconds and then cwm should begin

[Edit] have you un-installed the multi boot apps - try that and then re flash multi boot

teamwork makes the dream work