yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] joydeep1985:
Can you name stock roms i can try ? cause you already have told froyo stock roms arent working . so which stock roms should i try ? mention both froyo and GB roms please as per your recommendation ? :)
[Defy Android Development] m11kkaa:
Froyo-Roms should work if you are on froyo-kernel.

GB-Roms should work if you are on gb-kernel.

Greenbreadmod-Roms should work on both froyo and GB-kernel.

Didn't try everything but I hope the compatibility is now mostly 99% :)
[Defy Android Development] joydeep1985:
Would like to bring few points on note here with Bootmenu 1.2 , TWRP and Multiboot 0.5.5

I tried to flash whiterabbit But it says assert fail mounting ("/system"). I guess TWRP doesnt mount the Virtual /system img due to which aroma installer fails . I wonder why none of tweetypeety's versions arent working in multiboot . M1kkaa can you check why these three roms arent working in multiboot ( Whiterabbit CM7.1 , MIUI pikachu , Mookee ).

Edit : My bad Everything is working fine apart from the point mentioned above I edited the rest of points and removed them. Its perfect.

I would post the same in TWRP thread to bring it to considerations if some fixes are necessary both in multiboot and TWRP as well as in bootmenu .
[Defy Android Development] randolph2:
mutiboot v 0.55 works fine

----------------------------------------------------

DeFY MuLTIbooTEd WiTh Ms2GINger aS NanD and CoDEnAme ,wIuI and PiKaCHu ROms as 2ND booT
[Defy Android Development] walter79:
If you like to run normal defy+ 2.3.6 motorola defy roms as second system. You can use 2nd-init files from MS2Ginger 4.0 beta 4 or newer.

Working:

CM9 defy+ first system --> MS2Ginger 4.0 beta 4 second system or CM7.2 defy +

MS2Ginger 4.0 beta 4 first system --> second system CM9 defy+ or CM7.2 defy+
[Defy Android Development] nyamd20:
How do i find my virtual system?
[Defy Android Development] trurl3:
If you got installed it, then you will find it for sure. Did you install any ROM as virtual yet?
[Defy Android Development] nyamd20:
Nope I Did flash a rom before but i dont think it was as virtual Anyway i can find it?
[Defy Android Development] Anhell:
hi there, i`ve been struggling with a little inconvenience, i`ve isntalled the latest multiboot from the nand recovery, everything installed fine, then reboot and bootmenu appears, selected one of my virtual roms and suddenly i`ve come up the my nand rom... if i go to MBM now, it says it`s active in the matter of fact and the virtual rom it`s working, but well i`m in my nand rom... :confused:

I`ve got Pikachu 2.3.2 (froyo) as a nand, and CM9 (Froyo) with Codename (Froyo) as VFS
[Defy Android Development] trurl3:
Did you install m11kkaa's multiboot.zip? You can find it on first post of this thread. If so, look here

http://xdaforums.com/showpost.php?p=24835883&postcount=110

and here

http://xdaforums.com/showpost.php?p=24840276&postcount=115

Maybe this is what you need to know.
[Defy Android Development] dlhxr:
i happened to find that the battery status in all my virtual rom are the same...

is it one feature in multiboot 0.55 or a coincidence?

but they are not the same with my real rom.

just a guess!
[Defy Android Development] joydeep1985:
Thats an interesting story . But AFAIG its not the feature . M1kkaa didnt mention it anywhere in his changelog for latest build . So .... I guess thats jus an Coincidence :p
[Defy Android Development] N34S:
I followed these exact steps with multiboot 0.5.5

and the problem persists. black screen with red led. here's the log.

EDIT: finally i can boot CM9 GB via 2nd-system, but i'm stuck in bootanimation, repeating continuously the sequence of the log.
[Defy Android Development] joydeep1985:
When You actually post . Please dont forget to mention your build (whether its CM9 / CM7 / MS2ginger / MIUI as primary) and which build it is (Froyo/GB) . Please go through my steps and see if it causes you any trouble . The link is in my signature . Have updated it for 0.5.4 . There aren't much differences though in v0.5.4 and 0.5.5 . The installation procedures are pretty same of course.
[Defy Android Development] jorgeoro:
Hey m11kkaa i found a detail here, the multiboot.zip contains a folder where all other folders are, so when flashing that zip, it gives an "aborting install" to me, then i uncompressed it and just made a zip with the needed folders without putting them inside other folder and it worked. Please check that, it may be a problem for others.
[Defy Android Development] dlhxr:
Finally I found out why Chinese characters on sdcard files are displayed in ???.

The encoding doesn't compatible with that in busybox (or shell script?)

The android system can't umount the sdcard totally and mount it in the default way when booting, because you have already mounted sdcard in the preparation stage for multiboot and the virtual system is using the sdcard all the time.

Some scripts in fshook.functions.sh

mount -o rw $FSHOOK_CONFIG_PARTITION $FSHOOK_PATH_MOUNT_IMAGESRC

The sdcard is mounted with one kind of encoding (is it utf-8)?

And in the real system, the sdcard is mounted with another encoding (I guess GB18030?).

So the Chinese character is displayed as ??? in virtual system...

@m11kkaa

Could you help me find a way of mounting sdcard in busybox with the same encoding as real system?

I found a way to solve this, but it is so ugly...

I added two lines in real system/system/bootmenu/script/2nd-init.sh

mkdir -p /sdcardtmp
mount -o rw /dev/block/mmcblk0p1 /sdcardtmp

So the encodings are the same...But I don't think it's a good idea
[Defy Android Development] m11kkaa:
multiboot does not mount the sdcard (at /sdcard) so it shouldn't has influence on the way android mounts this partition.

can you post the output of the mount-command with both real and virtual systems so I can compare them?
[Defy Android Development] donb123:
Error 127

I'm sorry but how to use multiboot was a tad confusing. I created the img files and copied them to a wiui folder. I then went to 2nd boot, chose the WIUI virtual, then went to CWM and chose the zip file to install. This appeared to succeed but when it attempts to boot gives an error 127 see /cache/multiboot/error.log for more info

Thanks for any help!
[Defy Android Development] Casper87:
Create a folder called "WIUI" on SD Card in directory "MULTIBOOT". Copy .IMG's to "WIUI" folder, reboot -> Boot -> 2nd system -> CWM -> select WIUI -> install zip from sd card. Reboot to 2init -> Boot-> 2nd system -> select WIUI , enjoy.

By the way... what is your primary system? CM7 / MIUI ?
[Defy Android Development] dlhxr:
Why don't you believe me...

If you have mounted the sdcard before system booting, the android mounts the sdcard just the same as multiboot did.

I just added some lines in 2nd-init.sh and the main system mounts the sdcard the same way as multiboot...

mkdir -p /sdcardtmp
mount -o rw /dev/block/mmcblk0p1 /sdcardtmp

And i tried to remount the sdcard via term using the code following.

mount -o rw,remount sdcard /sdcard

and nothing happened.

How can I get the output of the mount-command?
[Defy Android Development] koerc:
Stock Rom

after bl7 root I hope I can finally think about multiboot.

As I read you have to flash MIUI or CM first to operate multiboot.

Why can´t I simply install bootloader on stock rom and have the ModRoms as virtual?

thanks for the great possibilities you opened!
[Defy Android Development] dlhxr:
You can do this, but you have to install bootmenu first!
[Defy Android Development] donb123:
---------------------

CM 7.2 And the above instrux is what I did.
[Defy Android Development] Math43:
Hello !

I've root my bl7 dfp-231 stock rom too and I install multiboot 0.5.5

I try to install MIUI Rom as second system by following this instructions, i've a bootloader error when my defy reboot. (I don't remember the error code :( )

I've try with MS2Ginger 4.0 too and the nandroid backup is applying to the NAND and not to the second system.

Ive take the MIUI Rom here -> http://miui-france.org/?page_id=1901 (ROM 2.3.30 Stable version)

Thanks !
[Defy Android Development] dlhxr:
I finally make Chinese characters displayed normally. I have to admit that something is not right with my previous post.

I just add 4 letters in the file fshook.functions.sh

mount -o rw,[COLOR="Red"]utf8[/COLOR] $FSHOOK_CONFIG_PARTITION $FSHOOK_PATH_MOUNT_IMAGESRC

And everything is OK with the file and folder names in Chinese.

But it still proves that your sdcard mounting process before system booting does really have some effects on Android mounting process.
[Defy Android Development] joydeep1985:
Btw I am not sure the MIUI rom you are using is a GB rom or not . At present only similar kernels are allowed like you have DFP-231 which is a GB kernel so Virtual system which you are flashing should also be a GB kernel rom only . :)

Also one more thing, AFAIK the stock roms are not well supported yet . So I guess M1kka would guide you in that . So the steps which mentioned was for CM9 / CM7 alongwith other Customer Roms. Not with Stock roms . If you want to Multiboot with stock rom . I havent played around it much yet :(

Edit : You have posted that Nanodroid backup is applying on the Nand system not 2nd-system. Make sure you have chosen Recovery from multibootmenu . And then again the virtual system. that should open the recovery for virtual system not the Nand
[Defy Android Development] Math43:
1.

System Version: 45.0.2310.MB526.NonEFIGSretail.en.EU

Build Number: 4.5.1-134_DFP-231

2. Multiboot 0.5.5 (The lastest download here), I've Android BootMenu 1.0.7-jordan display on the BootMenu Screen.

3. CyanogenDefyRecovery v5.0.3.1-jordan

4.I don't remember exactly the bootloader error, it's like "Err:A5,70,39,00,27"
[Defy Android Development] joydeep1985:
I have updated my previous post . Please check it .As far as i have seen everything is fine only . I guess just that the defy+ stock rom doesnt play too good with multiboot yet . Anyway try it with CM9 as Nand and Ms2Ginger v4 as virtual . That should be working anyway
[Defy Android Development] Math43:
Ok thanks a lot , I will try. But for CM9, is there a blur version ?

Edit: I just see a difference from the steps to add a second system:

At point 9. But now you wont see any nand boot (Real system) or reboot string anymore. I still see NAND.

Edit: About your edit about the NAND, I try again and it's the same... nandroid backup apply to the NAND but i'm in the Second system recovery...
[Defy Android Development] joydeep1985:
okay ... try flashing the attached bm_cwm_mb_v0.5.zip in my post and then try again . If you still having problem pm me .
[Defy Android Development] adamo3957:
Its the recovery string that will disappear multiboot now supports nand recovery

teamwork makes the dream work
[Defy Android Development] kelvinmorcillo:
I'm a little lost, can someone help me?

Some info:

- The menu-entry "Lastest Recovery" is no longer supported and will affect your real system!

- boot the System-Chooser with the 2ndBoot-option in bootmenu

Ok, I do choose 2nd boot option, then recovery to flash the rom, but there is those two options again when i 2nd boot, (Latest recovery, Custom & Stable)

Which one do I choose to only change my virtual system? When I second boot it doesn't matter?

Thanks in advance!
[Defy Android Development] joydeep1985:
if you are using v0.5.5 then its not the 2nd-boot option but 2nd-system you must choose. and put all the images under /sdcard/multiboot/<your virtual system foldername> . Then you would see a menu of all the virtual systems after you choose 2nd-system option
[Defy Android Development] adamo3957:
If I get it right what he is doing it selecting 2nd boot, boot menu then does a reboot and he is heading back into boot menu when the blue led comes up

You have to select 2nd boot / 2nd system then when the blue led comes on leave it, the led will change colour and then you are now in multi boot menu, or choose the options with +adb after them to boot directly without it rebooting

teamwork makes the dream work
[Defy Android Development] donb123:
I have v0.5.5 and don't have any menu item that says "2nd-system" and my second system, wiui, won't boot. I get the error I mentioned previously.

I do however boot into 2nd boot and get the read light and multiboot menu. Even tho I installed v0.5.5 from zip file in CWM, the menu says v0.1 and v0.5.5 is the only version I've ever installed.

Edit: I just installed CM7.2 as the 2nd OS and it worked. Something weird about wiui I guess...
[Defy Android Development] joydeep1985:
WIUI worked also for me . Dont know why isnt it working for you . Just create one more VFS (Virtual file system) in multiboot folder and try it again . And also your multiboot version should be v0.5.5 not 0.1 . Install multiboot from stable recovery and as Adamo said . Set 2nd-boot+adb as default boot and leave it like that and reboot . IT would give you all the virtual system names menu along with CWM and Nand boot .

Now then try to flash WIUI and see what happns . I guess it has something to do with the bootmenu of WIUI which is not compatiable with multiboot v0.5.5( jus guessing) though it shouldn't happen.
[Defy Android Development] dlhxr:
IC4M

Please download the lastest version, some mistake corrected.

It has two branches, branch1 and branch 2. You can see the differences through the pictures below.

You have to use the version above 1.3 or 2.1, because the format function in previous version doesn't work! Sorry for this.

Image Creator for Multiboot

Branch1 Instructions:

It is a simple Windows application to make images for multiboot.

You can make any size of the image you want by this.

Run IC4M.exe and then you will know what to do and remember select the format option. Do Not delete dd.exe and mke2fs.exe because they are used for creating and formatting the image.

After created, you need to rename the img file to data.img, system.img or cache.img. And put the three img files into a folder. Then move the folder to /sdcard/multiboot.

Now you can see another system made by you on booting. Go to the recovery for the new system, flash the rom you want to use and all is well.

Branch2 Instructions:

The folder name in the application means the folder name you are going to use for the virtual system.

Once finishing the creating and formatting, you will find a folder in the path you selected. Just move it to the phone (/sdcard/multiboot) and then reboot, you will see the system you just created and flash a zip through the virtual recovery.

Notice that you can pm me when you find a bug or a suggestion.

I hope it will help you.
[Defy Android Development] donb123:
Thanks!

I re-did everything and it worked this time. Thanks!
[Defy Android Development] jorgeoro:
Hi i can boot cm9 just once or twice, then i just get bootloops (even doing a data-dalvik wipe) so i have to reflash. Also after some battery's removals because of the loops, my stable ROM (cm7) gets damaged and i have to reflash it too. Any idea?
[Defy Android Development] trevor68:
I have the latest working using CM7.2 (real) and CM9 (virtual). Was pretty confusing and I only saw the Multiboot Menu once, when installing CM9, haven't been able to find it since.

At the moment I boot 2ndInit if i want Cm7 and SecondSystem if I want CM9 which is all good, but is there a way to make CM9 the default boot, so that I don't have to choose it every boot?

Currently Default BOOT is 2ndSystem, but then I have to choose CM9 to boot.
[Defy Android Development] donb123:
There's a good idea for a feature request- a timeout to boot the default OS under 2nd boot.
[Defy Android Development] N34S:
Now I can't start the 2nd-system rom without connecting the device to pc usb with adb activated :cool:
[Defy Android Development] joydeep1985:
Thats a future enhancement for To-Do list :)
[Defy Android Development] jpchopper:
Try rebooting and hit down volume when the blue led comes on, reflash multiboot in the stable recovery and reboot. Menu should be back. Hth
[Defy Android Development] XPStef:
Hallo together,

I am a Milestone 2 user and interested in your work of the Multiboot. walter79 (?) had asked if you can do it also for the Milestone 2, because it should be only one file, which is changed (i hope you understand what i mean). Ok, so it is possible for you to do it or to test it? If not, I would have some guys from android-hilfe.de who could test it.

Thanks for your time
[Defy Android Development] Niteeshkanungo:
2nd boot from primary part.

Any possible way to install secondary boot partition -itself into the Primay storage.. Reason- I use to switch SD cards alot..I have like 800 M.b's+ space free and empty since the first day i bought it ... :)
[Defy Android Development] TJKV:
There is a way i think, if you edit the script to mount the images from /data/fsimages. Walter79 has posted in this very thread how to do it...search it out if you want and tell me if it works :)

Edit: here it is :)

http://xdaforums.com/showthread.php?p=23638577#post23638577
[Defy Android Development] edwardo_machino:
This! Has anyone figured this out? I am in the same predicament, no root access available, no option to give it. Using virtual system, latest Epsylon nightly build (4/28).
[Defy Android Development] trevor68:
I can find it, forget where now, I think I have to start Recovery first, then I see it.

As for the 2nd Boot timeout thing, my second boot doesnt work at all, does nothing.

If I boot to 2nd-init I get CM7, if i boot to 2nd System i see CM9, select it, and boot into CM9.

that was my request to be able to reboot into CM9 without having to select it.
[Defy Android Development] Ptikjp:
Hi,

I second the idea to have an automatic bootup.

I think the following implementation would be ideal:

* hide the multi boot process in general.

* give an option in multiboot to set the default boot volume (either NAND or secondary(ies))

* upon init of multiboot have the LED flash a yellow color with ( volume down) mechanism to enter multiboot. I think this would be seamless...

I don't want anyone that gets a hold of my phone "by accident" to see the multiboot options. A little research will yeild results to reflash the rom and my phone will be gone forever. LOL.

If it is hidden then only those that know will be in the power to steal. :)

Just some suggetions. :)

----

Btw, thank you so much for creating this. You have enabled me to have my stock rom with working WIFI calling and also my favorite rom (CM7) on my phone. I really really appreciate it. Thanks so much again.
[Defy Android Development] bchiu:
For some reason I can't download the fsimages.zip?
[Defy Android Development] trurl3:
Use Multiboot Manager from this thread - it is help for manging multiboot v0.0.5.zip:

http://xdaforums.com/showthread.php?t=1522329&page=13

Then you can create all necessary images with volume you wish (i.e for cache it's enough 50 MB, then for data you can prepare more storage place i.e. 350-400MB)
[Defy Android Development] shrek8421:
Multiboot question

Firstly I just want to thank all the devs involved in multi booting. This is bloody great.

Anyway I have a concern regarding multiboot and CM9.

Not sure if this the right forum so please direct me if I am wrong,

Here is my setup:

Defy+ with 1700mAh battery.

Nand: CM72 White rabbit 1.5.1

Multiboot 0.5.5

IN multiboot:

- CM72- kang

- CM9 Quarx

-CM9 epsilon3

Only CM72 roms have battery errors.

The battery icon comes with a "?" mark and shows as 100% charged all the time.

I have tried using Quarx's CM72 latest nightly too. But it has the same problem. In ICS roms there are no issues.

I have tried many battery fixes (installed via multiboot CWM) but there is no difference.

Can someone tell me what I am doing wrong?

BTW if I use any of the above CM72's as my NAND then there are no issues.
[Defy Android Development] vuhothang:
I running Epsylon CM9 20120428, i can't run multiboot 0.5.5, it only display bootmenu 2.0.0. how to return old bootmenu to run 0.5.5, i can run multiboot with Epsylon CM9 20120416.
[Defy Android Development] shrek8421:
Did you choose at boot 2nd-system or 2nd-boot???

You should choose 2nd-system. Then you will get all the multiboot options
[Defy Android Development] vuhothang:
yes, i selected 2nd-system but bootmenu 2.0.0 ics screen always overlay the multiboot screen. When i press volume down to select virtual os i flash multiboot screen i can see a little time and bootmenu 2.0.0 will display.

Someone can send me bootmenu 1.2.0 ics to flash. Thanhks!
[Defy Android Development] Euro_Rules:
I can't install multiboot. I am getting error every time :( Please Help

[Sun May 6 16:51:10 UTC 2012]: Setting bypass_sign to 'yes'...

D/[Sun May 6 16:51:10 UTC 2012]: mounting virtual data partition...

D/[Sun May 6 16:51:10 UTC 2012]: creating bypass-file...

D/[Sun May 6 16:51:10 UTC 2012]: unmount virtual data-partition

D/[Sun May 6 16:51:10 UTC 2012]: removing folder...

D/[Sun May 6 16:51:10 UTC 2012]: Saving environment...

I/[Sun May 6 16:51:10 UTC 2012]: fshook-initialisation done!

I/[Sun May 6 16:51:10 UTC 2012]: booting cyanogen-rom...

D/[Sun May 6 16:51:10 UTC 2012]: patching init.rc...

E/[Sun May 6 16:51:10 UTC 2012]: Error: 1

:( :( :(
[Defy Android Development] pranks1989:
Same here! Epsy's 28April Defy+ build has touch recovery(I am not saying about TWRP). That may be the reason why multiboot is uncompatible!
[Defy Android Development] trevor68:
yep tried epy's 7/5/12 nightly and all i have is bootmenu 2 now. not only that, but its both my 2nd-init boot AND my 2nd boot as well, not happy jan! :(
[Defy Android Development] 769151238:
NEED HELP

I have a issue, i can't install second system. I only get what is the picture show. I think maybe I don't understand this step "Please replace NAME with the folder-name of your virtual system(you have to create this)" Tell me in a easy way.
[Defy Android Development] vuhothang:
You much make /sdcard/multiboot/(Name of Virtual link CM9 or WIUI....) in CM9 or WIUI folder have 3 file: system.img, data.img, cache.img.
[Defy Android Development] joydeep1985:
People who arent happy with bootmenu version v2.0.0 and twrp . I must tell you multiboot is yet not in synchronised with touch bootmenu yet . Later on versions that touch bootmenu/multiboot would be integrated to get compatiable with twrp. For the time being I would like to let you know that if you want old bootmenmu back . use adb commands to push bootmenu v1.1.8 (compatiable with multiboot v0.5.5.) to /system/bootmenu folder .

adb push bootmenu /system/bootmenu

.This should solve your problem. Right now I dont have the bootmenu v1.1.8 zip .Nogoodusername has posted them in earlier posts . I would attach it to my post later on . for the time being please find and download that bootmenu zip.

the user vuhothang is right you have to make a folder under /sdcard/multiboot/<your virtual system folder>. For eg : /sdcard/multiboot/CM7.2 and extrat the fsimages.zip under /sdcard/multiboot/CM7.2. Now the CM7.2 would have cache.img, data.img, system.img . That should solve your problem :)
[Defy Android Development] vuhothang:
Ok, i will reflash Epsylon nightly older with bootmenu 1.2.0 ics (it can run twrp recovery), i will take /system/bootmenu to try with newest nightly.

Thanhks!

I will use to root explorer to take folder bootmenu. I will upload when i have it and tested.
[Defy Android Development] vuhothang:
i was download epsylon 20120416, unzip and take bootmenu in system folder. I push (replace) folder bootmenu to /system. I was set permission like original bootmenu in 20120508. But many file image to set permission (not finish), i set finish all file (not include image file). When i reboot to bootmenu it run to bootmenu 2.0.0 with error image file.

How to set permission all file in folder, many file to set permission. I using root explorer to set permission. Help me how to set permission to folder effect with subfolder and files in this. root explorer or command abd.

I will try with older build.
[Defy Android Development] vuhothang:
I was copy bootmenu from 20120406 (1.2.0) to 20120508. I was set all permission by chmod in adb. But always bootmenu 2.0.0 touch. Now bootloop.

I will reflash 20120508 and wait new multiboot compatible with touch bootmenu.