yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] leodfs:
I can confirm a small bug on cmw. If total number of virtuals are odd, the system will reboot after press cmw. You can just add one empty folder, then it will work. it is nothing serious.

i think royale`s app doesnt even change any system file, and mine changes only one, that is replaced by the new 0.5 version. So problems are not related.

Edit: when you guys say that you go back, does the string CMW RECOVERY appears? If no, it is normal. Just select a name then you will go to recovery. There is NO recovery after you just press CMW Recovery.
[Defy Android Development] joydeep1985:
Okay so here is the situation now . as per told I made two copies of folder ( CM7.2 + MIUI ) so its even numbers . And after that when i select CWM it straight goes the figure 4 i.e the CWM string doesnt appear and along with that 2 of my virtual systems occur . Thats alright . But interestingly If i select again a name , It just reboots itself . :( . No recovery for me :(
[Defy Android Development] adamo3957:
I suggest reflash multi boot

teamwork makes the dream work
[Defy Android Development] m11kkaa:
Please send me a backup of the folder "/system/bootmenu" if you have this problem because currently I can't comprehend this problem.
[Defy Android Development] joydeep1985:
Already tried that . No change

Okay sure here you go .
[Defy Android Development] jpchopper:
So still getting same results with 4 folders in multiboot. Default set to second boot, when I click cwm recovery the screen blanks momentarily then returns to the initial screen, no recovery.

Currently running CM9 primary, trying to add a CM7 secondary but don't want to accidentally install on top of primary.
[Defy Android Development] adamo3957:
Reflash your real system,

Then reflash multi boot 0.5

Make sure you have no multi boot manager apps installed,

And you don't need to wipe when you reflash you real system

teamwork makes the dream work
[Defy Android Development] leodfs:
Edited. Deleted
[Defy Android Development] joydeep1985:
My setup is all similar just that my primary rom is CM9 and virtual is MIUI and CM7.2 . Everything i did was exactly similar . Just d difference is on last part. When i select the CM7.2 after going into CWM . IT again reboots and comes into bootmenu Virtual system select names ( 2nd boot is set as default ) . In my previous post i have attached my bootmenu . I wonder what has gone wrong in it . :confused:

BTW Nice video ;) and ur accent is jus fine :p if not perfect :D
[Defy Android Development] leodfs:
Edit: Could you please verify if you have the pds.img on cm7.2 virtual folder?
[Defy Android Development] joydeep1985:
Nope its not there :( :( how to get it ? Actually i jus unzipped the fsimages which M1kkaa has attached in 1st post. I thought if i would be able to get into CWM i would just again reflash the CM7.2 Zip there
[Defy Android Development] leodfs:
Dude, PM me
[Defy Android Development] joydeep1985:
update : You were right Leodfs . multiboot 0.5 somehow was preventing creation of pds.img file .
[Defy Android Development] leodfs:
In the new 0.5, fshook.edit_devtree.sh:

if [ ! -f $FSHOOK_PATH_MOUNT_IMAGESRC$FSHOOK_CONFIG_PATH/pds.img ]; then

dd if=$PART_PDS/dev/block/mmcblk1p7 of=$FSHOOK_PATH_MOUNT_IMAGESRC$FSHOOK_CONFIG_PATH/pds.img bs=4096

fi

replace this: $PART_PDS/dev/block/mmcblk1p7 for this /dev/block/mmcblk1p7.
[Defy Android Development] m11kkaa:
Yes that's a bug I mentioned when I was rewriting devtree-patching some minutes ago.

The new version will take a full-backup of the nand(except system, data and cache). This will take 51MB more space per virtual system (and first boot takes some more time) but this way you can flash a backup of virtual system to nand if you want(including boot,devtree,...) and it looks cleaner anyway.

Maybe I can decrease the size by backing up some partitions which aren't needed(like bootloader or cdrom) globally for all systems.
[Defy Android Development] joydeep1985:
I attached my bootmenu zip in my previous posts quoted to you . That might help you . :) if you need to test more please do let me know . I would be glad to help you out.
[Defy Android Development] N34S:
cm9 > black screen

hi everybody!

i have just putted 4 folders in sdcard/multiboot (including in 1 of these the 3 images for install the system, in this case cm9), restored 2nd-init 1.1.6 recovery from zip made myself, installed multiboot v0.5 and tried it.

i been able to get in CWM recovery after booting in 2nd-boot, but when i've rebooted after flashed the CM9 zip in his recovery, the screen went black and nothing happened. what's the prob?
[Defy Android Development] joydeep1985:
Do not use multiboot v0.5 yet . Its not yet fully functional . Instead use v0.4 along with royale's multiboot manager . It works fine . if you need a guide please follow these two posts .

Guide For Dual boot And Multiboot Manager
[Defy Android Development] m11kkaa:
It's fully functional, there are only a few bugs :D:D:D

Next release should fix most of them.(should come tomorrow)
[Defy Android Development] joydeep1985:
Wow thats cool news .Jus curious .Will that work with GB kernel as well ? :D :D . I mean if i can put froyo kernel as primary and mix of froyo + gb kernel roms as secondary ? :D :D that would be legendary and awsome :D :D (if not i m asking for too much then only :p )
[Defy Android Development] m11kkaa:
I made preparations so such thing will be easier but auto-switching the kernel will come in later versions.

For now it's important to fix things which doesn't work before adding new features.
[Defy Android Development] xblosa:
0.5 works great (after i removed the spaces in directory names)
[Defy Android Development] adamo3957:
Reboot from multi boot cwm doesn't work just power off then on

teamwork makes the dream work
[Defy Android Development] CallMeVentus:
Heya people......I can't seem to solve this problem .

When I flashed Multiboot v0.5 over v0.4 , I can no longer find my 2nd boot .

The Multiboot partition only has one blank space , then "Boot from NAND" , "Recovery (CWM)" (also blank page) and "Reboot"

I wonder where I've done wrong ?

Note: I have Multi Boot Manager installed on the real system and my images are in /sdcard/fsimages

Herpderp Defy.
[Defy Android Development] adamo3957:
That's because you need to uninstall multi boot manager and the virtual images need to be in the folder multiboot, all this is on the op please look next time

teamwork makes the dream work
[Defy Android Development] brajesh.sharma87:
perfect going!!!

Just a suggestion, If there is an option to share the /data partition for different ROMs, it wud be more practical to use multiboot. That way, we can keep our SMSs, Calls and other apps always updated. I hope u people get my point. :D
[Defy Android Development] adamo3957:
Different roms crash when you use the same data, hence why we have to do data wipes to install, the only one I can think of where data sharing would be beneficial would be the milestone aokp, and the tablet interface version,

Careful on your wording as that's an offensive way of putting how you feel, especially when you have multiboot for free when moto won't update a defy past froyo

teamwork makes the dream work
[Defy Android Development] brajesh.sharma87:
offensive way?????

I think u can be a gud judge.
[Defy Android Development] joydeep1985:
Please stop fighting :D ;) we have lot of work to do . BTW CM9 4.0.4 is out . And also there is a point in adamo's statement . If we have a common data partetion and we have several roms .After wiping data we would lose all the information in all roms if we have a common partition . So in a manner thats not desirable :)

But if according to Brajesh we have a common partition . We can really take a lot of advantage in having common data and apps in all roms . We wont be needing too much of hassle to install apps on diffrent roms :) .

For that previously i posted a info that battery is not synchronised on all roms . So if synchronization is possible then similarly we can always ask Royale to include that synchronisation feature into his multiboot app (when he would be back after exam ) . So that we can synchronize all apps + data + contacts from primary rom to virtual roms :) The might be the alternative solution what Brajesh has suggested :)

Just 2 cents for my ideas ;) :p
[Defy Android Development] royale1223:
I'm trying to support v0.5 multiboot in MBM. Please test.

http://xdaforums.com/showpost.php?p=24213173&postcount=44
[Defy Android Development] adamo3957:
Just installed logcat will test,

As for battery stats the safest way I can think of is if the script copies the battery stat files to SD then overwrites the virtual one,

I think re mounting that section of nand is too dangerous, I had to re flash sbf from my script being wrong,

Once we fix battery stats then you can find out what folders are stable in all roms ie data/app/ is a fixed folder in gb and ics

Also yes 4.0.4 is out but I'm not updating as for me 17th march build is perfect, I have working video and panorama so I'm waiting to update unless the urge comes

teamwork makes the dream work
[Defy Android Development] N34S:
also happens when booting ROM directly from menu :S

I hope with the fixed multiboot of today can work
[Defy Android Development] leodfs:
I don`t see why you guys are believing so much that the solution of measure problems are in sharing battery stat file.

As the solution for calibration recommended for almost all rom developers involves deleting this file when installing a new rom .

Also is good to remember that is always recommended to wipe data even when you are just updating your rom. For some lucky reason it sometimes dont cause problems when you dont do it. Share data is not a good idea at all.

If you really want that, do a image of your data partition and try to do a link of it between your virtuals.

Sent from my MB525
[Defy Android Development] joydeep1985:
Yes very much agreed. Sharing of data partition is not recommendable . but ofcourse we can replace or synchronise the stats file from one place to another . I was jus talking abt not sharing but to synchronise so that all roms have their own files yet they have the same data everywhere so we wont need any sharing of data partition at all IMHO .

Anyway first things First . let the bugs get resolved first . That is the main aim for all of us to get multiboot working . Advanced options can be taken care of later on as m1kkaa said in earlier posts :)
[Defy Android Development] m11kkaa:
I released version 0.5.1 which fixes several bugs and makes much things more clearly.
[Defy Android Development] royale1223:
I have created a small app to test prop changes on booting to a virtual system. Please test it and post screenshots (from both base and virtual). I have also made a new test version of MBM.
[Defy Android Development] trurl3:
It's something wrong with this app - can not install - parsing error.
[Defy Android Development] m11kkaa:
Sorry but I can't install the apk:

CM9(tried manual sign and system-partition): Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]

CM7.1: [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
[Defy Android Development] royale1223:
That was an unsigned apk. this should work.
[Defy Android Development] joydeep1985:
You rock Dude !! its working like charm !!! awsome work !! although did an extensive testing yesterday screwing my entire set up :) i am happy its working so well :) :)
[Defy Android Development] m11kkaa:
@royale1223: This app does only work with ICS.

Real system:

virtual system: (multiboot 0.5.1, 0.5 should give other results but that doesn't matter because it's no longer supported)

Edit: I changed SDK-Level to 10 with apktool and it works in CM7, too. :)
[Defy Android Development] royale1223:
Thanks a bunch.

I think you should also set props from 2nd-init.sh so that the real system also have corresponding prop entries.
[Defy Android Development] m11kkaa:
I don't want to patch 2nd-init.sh but it I think it doesn't matter: Whern there aren't any multiboot-entries multiboot is disabled and there are no additional infos to share.

BTW: Did you got my mail with the improvement.suggestions?
[Defy Android Development] N34S:
the problem still remains also with this fixed release :(

> can't start CM9. black screen and no bootlogo after selecting it in the menu. nothing happened. <
[Defy Android Development] royale1223:
Replied, thanks for the mail.
[Defy Android Development] trurl3:
Is this patched version posted?

Edit// Signed version gives the same parsing error.
[Defy Android Development] m11kkaa:
Maybe you are using the wrong kernel.

Also please note, that since 0.5.1 the first boot will take some more time because it creates some images.

royale uploaded signed version. I will not upload the patch I locally made because it's not my app.
[Defy Android Development] ganesh0992:
seriously v3 was working well....even v4 worked well...since v5 I can't flash the cm7 as virtual system...with ics as main

k this what I did....

made sdcard/multiboot/cm7/(copied the images)

went to stable recovery flashed v5.1 then to custom recovery wiped cache,dalvik then flashed cm7...then wiped again....now cm7 gives boot loops in 2nd boot.....tried 2nd init boot grrr it boots cm7...ics gone lol...

same happens wit v5 too.....tried doing sdcard/fsimages/ too...but same result....tried many times but the one flashed in custom becomes real system...

never happnd with v3 and v4....used to work fine....
[Defy Android Development] trurl3:
I have prepared imageas, flashed v 5.1 in stable, wiped cache and dalvik in custom, flashed CM9-NIGHTLY-120330, flashed GB kernel, wiped again, reboot, 2nd-boot to CM9 and stuck in black screen. After prolonged time self reboot to nand.
[Defy Android Development] hackergnome:
Hey a request/whateva

Can u Centre Align the names of virtual/real system in multiboot menu?

That will look cool

If u dont know what i mean see nook tablets xloader or touchpad's os selection menu...(it really lloks cool!)
[Defy Android Development] m11kkaa:
@ganesh0992: Please read the first post FULLY before trying anything.

Under "Some Info" you can read that "Custom Recovery"-option is no longer supported and fill affect your real system.

As multiboot_v0.5.1 sets your default-bootmode to 2nd-boot just let it boot without pressing Vol-Down after you installed multiboot.
[Defy Android Development] trurl3:
Thank you for MULTIBOOT screen :).

One Note: If you want to just reboot your nand ROM you have to catch blue ligt after reboot and choose 2nd-init in boot menu. OR wait to 2nd boot and choose -> boot from NAND :)
[Defy Android Development] hackergnome:
Everything back to stable now...

No more recovery crash!! Ver 0.5.1 is awesome!!!

Another request/suggestion...

Add Default boot selection...

I dont know of this is possible or not but is it posible to put a a key combination to boot certain default selection w/o using vol keys...(No key combo at boot process,I know thats difficult,but combo inside multiboot menu?)

Like when multiboot menu comes up we can quickly use Home button to boot nand os(this can also cause accidental booting) and Search button for sd default os
[Defy Android Development] ganesh0992:
lol shame that I wasn't aware of such a new update...thought new version was just bug fixes with same old steps...multi boot is awesome now....works gr8...

PS : v4 fixed the battery bug for gb kernel virtual system...the bug is back in v5....
[Defy Android Development] royale1223:
Added MBM 1.17 with full support for multiboot 0.51, see the thread. Thanks adamo3957, micha

http://xdaforums.com/attachment.php?attachmentid=974044
[Defy Android Development] m_zet:
Any one succeeded placing fsimages from multibook v.0.4 to /sdcard/multiboot/CM9 (<--example) and was able to book into this ROM?

I was trying this and no luck. I guess I have to do everything from scratch (in virtual)?

---------

So I did get back with those images to v.0.4 that was working to SDcard/fsimages and it work fine.

But when put in v0.5.1 in sdcard/multiboot/CM9 just back screen and then reboot.

When in 0.5.1 virtual CWM and installed the CM9 -29-03-2012 then it still did not book into CM9.

And when copied to fsimages on SDcard and booted in 0.4 it shows the upgrade.

Hmm. I would really wanted to be able to put those images from fsimages folder into SDcard/multiboot/cm9 and be able to run the virtual ROM under 0.5.1.

Any ideas?
[Defy Android Development] pabloltg:
I did everything as is, but after selecting the folder MIUI v4 (sdcard / multiboot / MIUI v4) is reset and re-enter the same menu .. never boots the system .. any ideas?
[Defy Android Development] joydeep1985:
Did you try to go into MIUI recovery ( from 2nd boot ) and try to Wipe Data + cache + dalvik cache ??? The first boot always takes a long time . Sometime it may take around 5 minutes . And make sure its froyo kernel that you are using . IF not then it may not work .
[Defy Android Development] pabloltg:
I have the Codename (Froyo) as real system.. but still, when i select the MIUIv4 (Froyo too) folder, the phone is rebooted and never pass of 2nd boot.
[Defy Android Development] joydeep1985:
Please go through this post before trying anything and make sure you have gone through each and every steps . Missing any one of the steps it may might not work . And also try setting the default boot to 2nd boot . And see how it behaves .IF it doesnt try to go through the steps and make sure you have performed all of them correctly .

http://xdaforums.com/showpost.php?p=24237176&postcount=524
[Defy Android Development] royale1223:
Added new version of MBM, please get me some screenshots, also if there is someone who can create icons for me please send pm.
[Defy Android Development] wizwin:
@m11kkaa: A minor clean up suggestion for 0.5.1 package:

From the zip:

rm /system/.gitignore

rm /system/bootmenu/script/.gitignore

;)
[Defy Android Development] trurl3:
If anyone has managed to install any ROM using defy_multiboot_v0.5.1.zip? I tried several times but every time first boot into installed ROM ends with rebooting to bootmenu. Nothing works. Even older ROM's installed by v.04 doesn't work in v.0.5.1 although when I switch back to v0.4 they are working good.
[Defy Android Development] joydeep1985:
I m running 4 Versions of Froyo based roms and along with that CM9 is my primary rom . ;) they are jus running super cool Except for that battery stat bug . Or else v0.5.1 is superb
[Defy Android Development] trurl3:
Maybe... how do you make /fsimages for new ROM's? Do you use any Multiboot File Manager?

I am tracking multiboot theme from the beginning and maybe this is my problem... first, when m11kkaa posted his multiboot_v4.0.zip for new ROM one have to use a pack of images in /fsimages folder placed in root of SAD card. Then royale and leodfs made their Multiboot Managers, which used m11kkaa's multiboot.zip and still used /fsimages but each one in different manner. Now in m11kkaa's new multiboot_v0.5.1.zip those /fsimages seems to not working anymore.
[Defy Android Development] ganesh0992:
what's the prob?? can u list the steps u followed??

v5.1 works gr8 in my defy plus except the battery bug always in virtual cm7...which got actually fixed in v4 or v5(forgot)...but the shows up again now...else everything is fine...

Edit : its no more /fsimages its SD/multiboot/name_of_the_rom/the_3_images
[Defy Android Development] hackergnome:
For the new mod images should be moved to /sdcard/multiboot/
[Defy Android Development] trurl3:
As you can see, "name_of_the_rom" is either name... If I want i can name my rom "fsimages". Really important is what is inside /name_of_the_rom folder. How do you make this three images?

Posting his multiboot_v4.zip m11kkaa gives fsimages.zip which contains packed folder with three redy images for installing ROM. The name of this folder now is not important, but for multiboot_v4.zip - it was /fsimages.

Edit// Just now I installed CM9-NIGHTLY-120329 on virtual so maybe problerm is gone. Anyway please let me know how you prepare images for your ROM's ans whether you use any MBM.

Edit2// Now I can not boot to previously installed CM9-NIGHTLY-120329 - after boot attempt immediately reboot. And this time I can not install another ROM.
[Defy Android Development] xblosa:
Recently i moved from 0.4 to 0.51, now i'm unsure how to update virtual system. I couldn't find a description
[Defy Android Development] joydeep1985:
Select the CWM (Recovery) option from the recovery menu . It would take you to a screen with all virtual system names ( but without the string CWM string ) from there if you select any of the virtual system names , it would take you recovery menu . from there you can now update the virtual system which you have selected
[Defy Android Development] joydeep1985:
I suggest you proceed my steps which i have mentioned earlier few posts back.

You Rather go with the Setup CM9 as primary and CM7 as virtual . And since you are new to multiboot try to avoid royale's MBM for the time being . First learn how to use M1kkaa's v0.5.1. When you are thorough with it you can surely proceeed with MBM .

Oh yes and for creating or preparing images for ROMs . I just copy the fsimages (only img files)to /sdcard/multiboot/<Your Rom Folder>. Thats it . IT has been told several times those who are new to v0.5.1 please dont use MBM for the time being . v0.4 and v0.5.1 has huge changes . so it would take some time to get perfect MBM .

For multiboot complete reference please follow the steps i mentioned in this post Below . I am successfully running CM7.2 and MIUI as my virtual system . Also have installed AOKP last night . My primary Rom is CM9 2903 build .

http://xdaforums.com/showpost.php?p=24237176&postcount=524
[Defy Android Development] fiskenigaten:
Have a battery problem! :-( I just installed multiboot and tried to flash Pikachu (didn't work) Now when I run my NAND system my phone only charges to 88% which should equal the amount of battery used while I was in multiboot (12%). Should I callibrate? :confused:
[Defy Android Development] dlhxr:
I have to say it is brilliant! The new version 0.51 is wonderful!

After trying for one day, 3 kinds of system, several bugs have been found.

bugs:

1.it cannot recognize the folder with a blank space in multiboot folder.

2.if the folder name is too long, the system cannot boot. such as cyanogenmod9... after i choose the cyanogenmod9 in multiboot menu, the red light twinkled twice and reboot. the same folder with the name cm9 boot ok.

3.another strange problem. i have put up before. since i am a Chinese using Chinese, there are some folders and files on the sdcard named in Chinese. all is well in the nand system, but all chinese characters appear to be ????? in the multiboot system. The problem is just in file and folder name and other parts concerning with Chinese characters are ok. I tried to rename a folder in multiboot system with Chinese and it displayed ok, but other folders are still in ?????...so weird.

Some suggestions:

I don't know whether you use pc or notebook with multisystem. there are two function missing here~

1. counting down function. if we have this, it means we don't have to press the ok button when rebooting. i don't know whether it is possible and realizable here.

2. manage the order of the systems in the multiboot menu. it displays in letter order, firstly multisystem, then a blank and nand system. can we change it by ourselves?

Thank you for your great work!
[Defy Android Development] fiskenigaten:
Good thoughts! Would also like to see a bootlogo or LOADING text instead of black screen when booting up :)
[Defy Android Development] dlhxr:
it seems that the battery problem is hard to solve~;)