yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] LeonardoJegigzem:
Hi!, veery nice work m11kkaa!, but i'm having some problems booting the virtual system,

I'm running CM7.1 on the real system, i created the ext3 fs and flashed multiboot in CWM, so i enter to lastest recovery and flashed the CM9... but when i try to boot on 2nd boot i only got the red led on!, i'm missing something of course,

any tip??

Thanks! :)

(sorry for the bad english)
[Defy Android Development] drwario:
In latest recovery I get can't mount cache/log error. When I go to wipe dalvik cache nothing happens. When I try to use 2nd boot I never get passed splash. The boot animation does not start. Is it possible the rom isn't building up the dalvik cache? Maybe that's why boot animation doesn't start?
[Defy Android Development] m11kkaa:
Great ideao but I only have time for little projects like developing multiboot.

Would be great if anyone can make a detailed FAQ.

Choose "2nd-boot + adb". If it shows an error there is an script error.

you don't need to connect via adb - it will be displayed on screen in yellow font.
[Defy Android Development] m11kkaa:
I tried it in the past, but I only put the normal boot.img on recovery-partition and never tested more.

I don't want to test MSGinger since I have green camera and I don't want to mess with these things.

But I can give you instructions if you want to test it yourself.
[Defy Android Development] TJKV:
Make sure the image files aren't on the root of your sd card but in a folder called fsimages.
[Defy Android Development] aribis:
Known issue...you should try version 0.6...that's more stable...

Swyped from Ari@JellyGreenDefy
[Defy Android Development] aribis:
I actually tried with CM10 as nand and had problems with multiboot...couldn't boot the virtual systems...

M11kaa any thoughts?

Swyped from Ari@JellyGreenDefy
[Defy Android Development] trurl3:
I am using multiboot quite extensively for CM9 aqnd CM10 (practically do not return to nand CM7). As for now multibooting doing fine and every time I want I can switch to another ROM (actually I have 3 - one CM9 and two CM10). But recently noted so neither in Multi Boot Manager or Vibhinna there is no active ROM notification. On the bottom of the screen is note: MULTIBOOT inactive. Intersting so in INFO tab there is NAND as actual system... What it could means? Beside it all multibooting system works flawlessly...

Edit// Just now I have switched to CM9 and there Vibhinna is working as it should - actual ROM is tinted red... so it is problem with Multi Boot Manager on CM10.
[Defy Android Development] xblosa:
How do i exchange nand and multiboot?

I am running cm7 on nand and jb (cm10) on multiboot. Could i make a cwm backup of both and restore them in swapped operating mode (jb in nand and cm7 in multiboot)?

Or is this completely impossible?

I could reinstall jb from zero but i would like to keep my cm7 for a while ?
[Defy Android Development] m11kkaa:
This should work, but I can't confirm it.

Please note, that restore to virtual system will fail if your images are too small.
[Defy Android Development] aribis:
m11kkaa as i said when i use cm10 on nand and try to boot virtual systems i get an error "multiboot error...please reboot" written in yellow on black screen...i have cm9 , froyo, gb on virtuals but none boots...but it lets choose the recovery(cwm) and then when i choose any of them it gives the error...
[Defy Android Development] m11kkaa:
Please post the logs.

If Multiboot-Error shows up, the ErrorDetection has found something
[Defy Android Development] aribis:
ok will do that once i redo the whole setup again and install logcat...currently i am booting into cm10 from virtual and cm9 on nand...thanks for the reply!

and also thanks a lot that only for your multiboot i am able to run froyo, gb and ics along with JB on the same mobile without loosing all the setup and feel...

Thanks a ton!!
[Defy Android Development] SkyKOG:
Yup i did that when i was on cm9(virtual) and MIUI(nand) :) ... and wanted to swap them :) ...

Well this does work ... but make sure yer nand is not bigger than yer VFS size lol :P ... this happened to me ... my MIUI data partition was very huge :eek: ...

Anyways ...i took a simpler route too for a fren ... took titanium backups of both ... then clean installed on both VFS and nand(both swapped obviously) ... then i simply restored everything :D ...it worked ;) ....
[Defy Android Development] xblosa:
Sure, will have to create a big data partition. Tared partition from cwm is about 1GB.

There have been too much tweaks over the last year which i suspect titanium will not cover, and i do not remember all of them. Cwm recover seems to be the best way for me.

Anyway, will wait a little bit until cm10 gets more stable (and i am waiting for PDroid support) .
[Defy Android Development] trurl3:
@m11kkaa - is Vibhinna compatible with CM10 or this problem with not recognizing VFS in CM10 happens only to me?
[Defy Android Development] m11kkaa:
Sorry, but I never tested Multiboot with CM10.

But here are some posts about this. Just search and ask these people's if you want to know more.
[Defy Android Development] bharaththeunique:
It works....no prob...sometimes issue with rebooting to nand goes into boot loop....some times it works OK.....pls update this m11kkaa please.....:beer:
[Defy Android Development] diotto:
Hi people. I have a Defy+ with CM9 (from Epysilon3) installed in NAND (GB Kernel).

Can i use multiboot with it ? Some posts ago i saw that there was a bug with GB kernels. Is there a solution ?

Info: i tried CM7.2 (WhiteRabbit 1.6) in NAND and could install CM9 as second O.S. Now with CM9 in NAND i get an "Error: 17" while trying to enter multiboot.

Thanks
[Defy Android Development] espaciosalter20:
I think it's time to update multiboot since there is cm10 around here...

Enviado desde mi MB525 usando Tapatalk 2
[Defy Android Development] m11kkaa:
1) Currently I don't have much time(and it will be much less time when I start studying in October)

2) I'll send my phone to moto for repairinng ear-piece in the next days.
[Defy Android Development] royale1223:
It looks as though the prop entries made by multiboot disappears in CM10. Without those Vibhinna will say that the system is NAND. I'll check and confirm.
[Defy Android Development] xenusr:
Someone can port it to MS2?
[Defy Android Development] walter79:
MS2Ginger has support for multiboot. It use v0.5.xx .
[Defy Android Development] diotto:
GB Kernel ? AFAIK multiboot is not compatible with GB kernel.

I have the same problem here (CM9 and CM10 too)
[Defy Android Development] aribis:
No...green lens froyo...

Another peculiar problem I noticed is that even though I have separate CM10 folders for Quarx and Epsy in virtual...but when I try to install a few apps like xda or adaway it gives me a notification of replacing an existing instance...and when I install those in one CM10 it becomes unavailable from another...both are on the same custom recovery..could this be the problem?

Do you mean defy plus users do not have multiboot? I guess the kernel is not an issue..maybe a particular build problem...but I don't have a defy+ plus to check

Swyped from Ari@JellyGreenDefy
[Defy Android Development] nidhish91:
I don't know why are you facing issues. I am using 0.61 version and testing cm10 on daily basis.

S3nt fr0m my D3fy/w1u1 GB st4BL3
[Defy Android Development] m11kkaa:
Why you guys are using 0.6?

I fixed many bugs related to such problems with 0.6.1 and 0.7.

Older versions are deprecated...
[Defy Android Development] TJKV:
Between 0.61 and 0.7 scripts the only difference is that the latter is for touch boot menu, former for the non touch bm right? No other problems in 0.61 that are fixed in 0.7?
[Defy Android Development] m11kkaa:
In theory yes, but I did many cleanup and little-fixes during touchbootmenu integration. And there won't be two versions in future-releases.

Multiboot now is part of touchbootmenu and can't be used without this.
[Defy Android Development] aribis:
well its the same 0.6.1 we talking about... but I was unaware of the developments and read that 0.7 had issues...anyways will try that way too..

@nidhish you using CM10 as nand and is still able to boot into the virtual systems?...

besides @smoky replied to my installation error that it was an error with apps accessing app data parts on the sd card from different builds...

Swyped from Ari@JellyGreenDefy
[Defy Android Development] Rabbit_bb:
Can somebody refresh link for fsimage?

E:

ok, sory i'v get it...
[Defy Android Development] m11kkaa:
Can't you use MBM to create "fsimage"?
[Defy Android Development] Kazid:
Hi

Here to give my feedback about the Multiboot 0.7 with Bootmenu v2.0 and Recovery v5.6.7 (stable) and v5.7.0 (custom). The ROM running on Defy (green lens) is the CM9-NIGHTLY-120711.

Installed Multiboot by stable or custom recovery, the ROM do not boot by 2nd-init even after 2 reboots. So i lose the currently CM9 installed and have to install zip-file in CWM again to it back to work (and lose the multiboot with that).

[Ignoring 2nd-init is not working]

After installed, gone on Multiboot -> recovery -> custom -> [install ROM]

wipe cache and dalvik on multibook recovery.

On boot shows 3 option, *2nd-init, *2nd-boot *2nd-system

Booting on 2nd-system no more boot after the "kernel" logo.

Booting on 2nd-boot the boot load the second ROM (installed on multiboot recovery).

*CM7 do not finish to load, giving me back some errors on screen that i have to click on Android(the first ever).

*CM10 boots normal, but bring some configures from CM9 (like wallpaper, notifications sounds etc).

After test the second ROM, i have to install CM9 zip-file in CWM again to back to my normal ROM.

The files on /sdcard/multiboot/[ROM] remains only 3 (cache.img data..imb and system.img)

I passed the md5sum check on then and the original files and all then have changed. I though i was installing the 2nd ROM on device and not on images files, but as then had changed the md5sum i got lost.

Sorry my poor english.
[Defy Android Development] aribis:
m11kkaa...as suggested i have now installed multiboot version 0.7 and it is good enough to let me boot into virtual systems alright...the problem seems to have taken a new turn...here:

CM10 on Nand...CM9 as virtual...

multiboot 0.6.1 gives the multiboot error...cannot boot to virtual...

after i have installed multiboot 0.7 i can boot into virtual and then if i try to boot back into Nand its stuck on Moto logo...have to pull battery to reboot...

what i tried:

from...recovery>stable recovery>advance restore...

1)tried to restore boot from backup(did not work)

2)tried to restore recovery(did not work)

3)tried restore system(worked)

only the third option allowed boot into nand but i lost multiboot again...alternatively i could flash the ROM again to boot into nand...

my guess is the stable recovery used in multiboot is still 5.0.6 whereas the CM10 builds are using 5.6.7 and that's why its not booting into nand...

if this is the case then how to install the newer recovery versions on multiboot?

or is it something else...

however this is not the situation if i am on CM9 as nand and CM10 on virtual...

need your help buddy...thanks in advance!
[Defy Android Development] m11kkaa:
How you got to the conclusion with recovery? :confused:

Recovery has nothing todo with 2ndInit-boot.

I think, that the touchbootmenu-installer removes some files which are important for CM10. Normally this shouldn't be the case but I'll have to analyse that.
[Defy Android Development] aribis:
Thats not a conclusion only a guess...i stated just what i noticed after flashing multiboot...

when i flash the quarx build it shows a stable recovery version 5.6.7 and once i flash multiboot 0.7 it takes me to a stable recovery version 5.0.6...

so i guessed that the problem comes from multiboot which is downgrading the recovery version...or maybe 2ndinit has some issue with CM10/CM9 since some people are also facing problem with coming back to CM9 on nand... i dont have much know how to understand otherwise...maybe you will be able to help!
[Defy Android Development] Acceleracer:
touchbootmenu always wastes my defy+! With CM9 installed and after that installed the touchbootmenu, i lost clk4 and vsel4 and the phone doesnt boot up! CM10 just the same! Is there any fix for it? Is there any other non-touch or touchbootmenu that I can use to have again clk4 and vsel4??

OMG now i tried to install TWRP and lost stable+custom recovery !
[Defy Android Development] @non4:
Multi boot isn't compatible with GB kernel, as the touch boot

menu still has multi boot integrated this could be your problem, however it has bricked my bootmenu before on certain roms

Sent from the real world by hacking into the matrix
[Defy Android Development] aribis:
I think it's not only GB...multiboot has problems with CM10 management...i use a green lens froyo defy and been having the problem with changing from nand to virtual booting..maybe the problem is with the booting process of CM10 from other versions which multiboot is currently finding difficulty to handle...

m11kkaa seems to be busy and we are stuck with our inability to multiboot into different roms..hope he soon gets some time to lookup and settle the issue for good...we need multiboot...it's simply awesome!!

Ari@JellyGreenDefy
[Defy Android Development] defim:
Doen't work for me too :(
[Defy Android Development] cyrusct82:
@aribis

I have`d the same problem in GB kernel.

I have managed to boot into nand system by wiping cache and dalvik.
[Defy Android Development] aribis:
Thanx...but that the first thing i tried... and then did the other steps also...but seems i have to start from scratch again...doubt if it will help...btw whats in nand and whats in virtual? which version of multiboot you using?

@m11kkaa...if you have any suggestion or can help to get this fixed please...but do take care if you are busy with your studies...multiboot can wait... so long take care!
[Defy Android Development] cyrusct82:
I had on nand CM7 by Fuzz and virtual CM10 by Quarx.

But this was working only one time.

The second time i had to start from scratch all over again like you.

Now i am in CM10 without multiboot.
[Defy Android Development] trurl3:
Last build of CM10 02/08 from Quarx does not run on multiboot...
[Defy Android Development] aribis:
Very strange that when i was using CM7 or CM9 as nand and CM10 as virtyual i never faced the problem of booting into nand...and i was using multiboot version 0.6.1...however the problem then was that i was not able to access my SD from computer and faced certain root errors...but i could boot back to nand and virtual ok...

since i use the JB as my regular ROM now i had to begin with CM10 on Nand and now 0.6.1 cannot boot into virtual but can boot into Nand and 0.7 cannot boot into Nand but boots into virtual...peculiar catch22 situation...you get either CM10 or you get multiboot!
[Defy Android Development] Quarx:
CM10 builds after 2Augist has support of TLS Register.

Multiboot installed on latests CM10 will not boot any rom without support TLS Register.

Rmmod on "tls_enable" will not help, because it is patching kernel in RAM (see insmod tls_enable.ko in pre_bootmenu.sh in latest CM10).

For boot latest CM10 from other rom without spport TLS, you need load on early stage (ex. "Loading kernel_modules" in 2nd-system.sh) "tls-enable.ko" and replace 2nd-init binary in "bootmenu/2nd-system" from latest cm10 rom. (but it disallow boot any other rom installed on multiboot).

No other ROMs has support of TLS for now.

For support TLS, need rebuild android with support it (jb has by default) and insmod tls_enable.ko in early stage.
[Defy Android Development] aribis:
Thank you Quarx for confirming and elaborating this problem...so does this mean that we are not going to be able to use multiboot in near future...either with CM10 as nand or as 2nd system?

Ari@JellyGreenDefy
[Defy Android Development] trurl3:
It's just on time statement... I was quite ready install to nand latest CM10 from Quarx... now I will wait and see... I become so much addicted to multiboot :D
[Defy Android Development] aribis:
Same here...and it seems it will be a long wait as older builds will have lesser chance of a rebuild...sad!

Ari@JellyGreenDefy
[Defy Android Development] Shubhamqweasd:
pls m11kkaa this is the time when we need MULTiBOOT the most , there are so many jb roms , it will be very easy to try them all , as quarx said it is possible to do multiboot if all roms have TLS register thing :D

so is there any possibility ??
[Defy Android Development] TJKV:
Um so you will need to ask the ROM makers to include that. Not really a part of the multiboot scripts...
[Defy Android Development] kanpurite:
How about we request maniac to include it in cm7 nightly?
[Defy Android Development] m11kkaa:
Didn't analyse the problem in detail. But in theory it should be possible to implement compatibility with TLS-roms without patching roms itself.

But my defy is in repair so I can't do anything.
[Defy Android Development] Shubhamqweasd:
no u got me wrong , TLS registry is in every latest JB rom , theres just some changes need to made in multiboot so that it can run with those roms :D
[Defy Android Development] TJKV:
Oh cool :D

Sorry Shubhamqweasd, I was wrong then :P
[Defy Android Development] smok.y:
hi,

i have ask him in android-hilfe-forum yesterday but i dont get a replay for the moment, i will hope it will be possible for him to get multiboot back.

smok.y
[Defy Android Development] trurl3:
CM10 on nand without multiboot

Unable to wait no more for multiboot in CM10 I felt forced to flash it on nand without trying... and I am really surprised how smooth and good it works. Previous installations of CM9 on multiboot were laggy and sometimes 'froze' with 100% processor load. I was afraid so with CM10 will be the same... but nothing of such... Cm10 works as oiled maschine... i am very pleased. Anyway flashing CM10 is not great thing - at the first time do factory reset and clean caches then flash newest CM10 NIGHTLY and gapps. Surprisingly it is much less problems as with CM9...
[Defy Android Development] aribis:
You have been late to the party @trurl3...multiboot has still some time to come out of the coma that its in now...meantime JB is leaps and bounds above CM9...never liked CM9 though liked its promise of something good to come...so JB is here and it will definitely stay on Nand for me...

As for Multiboot i will await m11kkaa to rebuild the tool so we may begin to enjoy our multi-rom days again...

cheers to m11kkaa :good: ...hope you get back your Defy soon...i cant even think of living without it for long! kinda addicted to Defy :angel:
[Defy Android Development] m11kkaa:
Added a list of changes to "Next-Version"-area in OP I made 2 month ago :)
[Defy Android Development] Shubhamqweasd:
will it be working with TLS registry roms ?:D
[Defy Android Development] brajesh.sharma87:
Hello m11kkaa sir, I've been waiting for you to solve the SD card bug which I told u earlier. :D
[Defy Android Development] m11kkaa:
I think so. We'll know more if my defy is back :P

Sorry, but this needs more time of analyzing than I have.
[Defy Android Development] aribis:
Thats great m11kkaa...and just in time when i was losing all hope :good:

Also take note that the virtual ROM often has root problems and SD is not accessible through USB...

again hope to see you testing multiboot on your Defy very soon!! :highfive:
[Defy Android Development] Euro_Rules:
m11kkaa when new version will came out ???? :)
[Defy Android Development] m11kkaa:
when I get back my defy and TLS-roms are working.
[Defy Android Development] pcz:
Thanks

Well, I made it, but it still not booting! Are you sure that there is nothing else what we need to do?

My kernel version:

2.6.32.9-gb08c3c8 #1
[Defy Android Development] m11kkaa:
What you made? I did not release an update for TLS.
[Defy Android Development] bharaththeunique:
Yay.......hope those customer care idiots unlock ur bl and u get hold of the key too.....!!!!!!.....thnx anyways....!!!
[Defy Android Development] aribis:
Hahaha a little too wishful! :)

Ari@JellyGreenDefy
[Defy Android Development] m11kkaa:
I don't think, that anyone in germany is able to unlock defy :D
[Defy Android Development] pcz:
Sorry, I forgot the quote. So I made what Quarx wrote.
[Defy Android Development] przemhb:
Could someone tell me why after installing touchbootmenuv2.0beta_multibootv0.7-20120618-signed.zip I cannot boot at all? There's no "normal" option in Bootmenu\Boot and any of the other options (2nd-init, 2nd-boot, 2nd-system) does not boot Android; just stucks with a black screen.

Previously I've had SndInitDefy_2.3.apk and defy_multiboot_v0.5.5.zip and I was able to boot.
[Defy Android Development] m11kkaa:
Because touchbootmenu replaces bootmenu completely and newer CM10-roms are using TLS which is not included in touchbootmenu. just read the older posts.

I'm fixing this right now but it's a little bit complicated.
[Defy Android Development] przemhb:
Could you be so kind and let me know how to fix it? (One more thing: I've got Froyo 2.2.2, 3.4.2-155-2)
[Defy Android Development] m11kkaa:
for now, just reinstall you rom so multiboot will be removed.
[Defy Android Development] przemhb:
It seems I've run into much serious trouble... I've tried to restore morning backup of my Froyo and decided to flash system only. Recovery from the

touchbootmenuV2.0beta_multibootV0.7-20120618-signed.zip said there is an error with the image to restore and now my Defy stucks with M logo, so I cannot get to recovery.

Luckily Motorola's recovery worked - I've flashed original SBF via RSD Lite. Now my Defy works again.
[Defy Android Development] m11kkaa:
Ok I think I have a solution.

1) I added a detection into installer to enable/disable tls for NAND-system depending on if it's needed or not

2) I changed tls-module so it disables tls on unload so non-tls-roms can be booted

This still needs some testing but I think I can release it tomorrow.
[Defy Android Development] m11kkaa:
Updated Multiboot to v0.8 with full TLS-support, working reboot-commands and many little fixes.
[Defy Android Development] Shubhamqweasd:
wow , THANKS very much m11kkaa ..

i must say ,.. you are the one , who gave defy the most unique thing it has .. MULTIBOOT.. no other device does multiboot so efficiently ..

ill be installing it , and be posting my review in a while .

---------- Post added at 02:15 PM ---------- Previous post was at 02:01 PM ----------

hey m11kkaa , i just installed multiboot 0.8...

after setting boot to 2nd-system .. it shows all multiboot roms but no option to boot from namdroid ..

will i have to evrytime set the bootmode to 2nd-int in order to boot into nandroid , or am doing something wrong ??
[Defy Android Development] m11kkaa:
no you did everything write. I've just not implemented this feature.

Maybe next version.
[Defy Android Development] Shubhamqweasd:
yes , TLS support is working very good :D

i have just set the default boot mode to - 2nd-int ..

and

choose the one time boot option( 2nd-system) from bootmenu to boot into other roms on sd card :D :D

this is the best working way for me :D
[Defy Android Development] SkyKOG:
So now can I finally install cm10 on nand and boot into miui gb & wiui from virtual...

I'm still stuck on ics july 5th build for the single reason that only that build supported the above configuration which is really important for me...

Thnx for the amazing work :)...
[Defy Android Development] m11kkaa:
BTW I talked with quarx about the USBshare problem inside Multiboot-systems.

It seems to be a multiboot-limitation. sdcard can never be unmounted inside multiboot and that makes it impossible to re-read the filesystem.

only way would be to use data-partition or to split sdcard into two partitions.
[Defy Android Development] Euro_Rules:
Thanks m11kkaa for new build

I tested and its works for me..... :)
[Defy Android Development] hackergnome:
Erm... Please change the date of thread name...

Also check your PM please...
[Defy Android Development] m11kkaa:
both tasks resolved :P
[Defy Android Development] ela1103:
m11kkaa

please implement the next version in this feature

option to boot from nanandroid