yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Febernacke:
I don't understand the two recovery things..

I am running Barebone 1.5.1 and I have installed bootmenu using SndInitDefy_2.0.apk. But I only have Custom Recovery (latest recovery?) and Stock Recovery but no stable recovery.. how do I get stable recovery?

EDIT: So, I tested anyway just got lots of errors and my 2nd init menu is now gone. But my normal froyo barebone 1.5.1 is booting as it always have done.
[Defy Android Development] dlhxr:
i don't have experience like you. but maybe you can try to install bootmenu again?:)
[Defy Android Development] Hashcode:
The "encryption unsuccessful message" is new to ICS. It's caused by a failed mount of what the system thinks is /data partition. ICS will try to mount /data again w/ encryption enabled.
[Defy Android Development] dlhxr:
thx, i'll try again after my exams:D

but i think the ics on defy would be perfect then and no use to do this one again:p
[Defy Android Development] ovu85:
i had tryed many roms on the virtual partition since one day when the multiboot didn't worked and flashed the real partition. Anybody else had this problem?
[Defy Android Development] UEman:
You have to reflash the multibootzip after each update of your main, else what you describes is happening.
[Defy Android Development] ovu85:
thank's , didn't know that.
[Defy Android Development] TweetyPeety:
m1cha ? is it you :)

I have red the first post and WOW it sound pretty easy. I will try it maybe on the weekend. GREAT STUFF DUDE
[Defy Android Development] wyumhk:
cm72-111223 (main) + CM9-NIGHTLY-111223 (virtual) multiboot

I have a red lens Defy, I wonder if I can have multiboot with the above 2 ROMs ?

Have anyone tried ?

Is there any problem ?

EDIT :

cm72-111223 is cm72-111223.0500-NIGHTLY-Defy+.zip,

which runs on the same 2.3.4 kernel.

EDIT 2 (tested result) :

Same as this post : http://xdaforums.com/showpost.php?p=20824038&postcount=3. No signal, the others seems Ok.

Some differences compare to installing CM9-NIGHTLY-111223 as the main system:

1. CM9 (virtual system) has not detected the SIM card's language/time zone correctly (or no detect).

2. APN entry is empty.
[Defy Android Development] free2live:
Have you disabled PIN? CM9 doesn't have the ability to check PIN. At least not yet

Edit: there is a zip with apnconf in the Cm9 thread

Sent from another planet
[Defy Android Development] TJKV:
So I just thought of something... If we have two folders on sd card, fsimages and fsimages2, and we keep switching the names whenever, we can have triple boot :D

More folders, more number of roms :D

I will try this in a few days by adding wajkiui to my cm7+ cm9... dualboot and see...
[Defy Android Development] brajesh.sharma87:
It works, I have already tried with CM7, Miui and CM9 (Froyo Kernel). :)
[Defy Android Development] marco_:
Same here.

Defy+ MB526

primary: 2.3.6 buildnr. 4.5.1-134_DFP-132 => 100% ok

secundary: CM9-ICS-MR1-111223-quarx2k-by-bihariel => no carrier, gives 'Error when searching for network'.

If it only occurs when using CM9, likely that CM9 is the problem.
[Defy Android Development] wyumhk:
The PIN of my SIM card have never been enabled, such that it works when CM9 is used as the main system.

Do you mean this apnconf ? http://xdaforums.com/showpost.php?p=20966462&postcount=2461. It seems that this file is corrupted.

I also tested using CM9-ICS-MR0-111213-jordan.zip as the virtual system. Also no phone signal (and no data signal), wifi is ok.

Moreover, cannot save manually created APN for both 111213 & 111223.
[Defy Android Development] marco_:
Nogoodusername suggested in the CM9 thread that CM9 asop can only boot as a primary rom.
[Defy Android Development] hackergnome:
I mean any aosp!

Includes cm7 n cm9

Dont know abt miui...
[Defy Android Development] UEman:
Any rom you try as virtual system won't have signals. That just doesn't work.
[Defy Android Development] hackergnome:
Nope!

Only cm7 and cm9

Tried miui and it has network!!!
[Defy Android Development] antukubo:
Not really.

I used CM9 111202 as virtual - disable SIM Pin - and I manage to receive and make call. I don't have to use Baseband Switcher at all since it auto recognized my carrier. The only thing, my signal bar is zero (like no network)

I upgraded to CM9 111213 and like others, I don't have signal even with baseband switcher. I tried to disable SIM Pin but it keeps telling me wrong pin.

Anyway, CM9 as my virtual system is just for testing purpose (until we get the solid one). I will just relax and wait for the next nightly builds :)
[Defy Android Development] wyumhk:
Tested result :

cm72-120102.0338-NIGHTLY-Defy (Froyo) as main + WajkIUI 2.1.6 ICS (Froyo) as 2nd virtual

this works for both systems (both has network).

cm72-111223.0500-NIGHTLY-Defy+ (GB) as main + MS2Ginger 2.1

main has no problem, virtual unable to boot (black screen then reboot), may be due to kernel version ?
[Defy Android Development] wyumhk:
Just for a quick test :

I have cm72-120102.0338-NIGHTLY-Defy (Froyo) as the main system, then I installed an old nightly cm72-111204.0310-NIGHTLY-Defy as the virtual. The virtual has signal and can make phone call (although time zone/default language are not detected correctly in the virtual).

This test is CM7 main + CM7 virtual. May be not so meaningful ?
[Defy Android Development] hackergnome:
Forgot to tell that problem is only with gb kernel!!
[Defy Android Development] wyumhk:
I am going to set up a dual boot CM7 + CM9 (or CM9 main + CM7 virtual) dualboot when Epsylon releases next CM9 nightly. It seems that it is not possible now.
[Defy Android Development] bartekopa:
Hi, i have a questions. Whether I can increase the memory data (in multiboot)? Becouse 300mb is too small for me. Thanks in advance ;)
[Defy Android Development] nepotu:
You can create custom files that meet your space requirements (using this if you are using linux or using this if you are using windows).
[Defy Android Development] bartekopa:
Thanks, but whether I can move my data from 300mb data.img to new data.img?

edit.

ok, i know, i can resize data.img
[Defy Android Development] marco_:
Bihariel posted a link to a tool on page #2, called TopoResize.

It can be used to create and resize ext2 and ext3 image files from Windows system.

=> SD card has to be mounted in windows, does not work in phone.

Be sure to check it out.
[Defy Android Development] hemil:
I don't have stable recovery and latest recovery in my rom........can i create such recovery partitions ?????;
[Defy Android Development] brajesh.sharma87:
dude, read the first post patiently and you will understand everything. Then if u have any problem, ask in this thread and people will answer you. :)
[Defy Android Development] Gazm4n:
Update your recovery and you can have multiboot.

http://xdaforums.com/showthread.php?t=1356767
[Defy Android Development] hailmary:
has anyone tried to run CM7 base & miui in virtual?

if yes, what is the img file sizes used?

might not be meaningful too.but just curiosity for possibility
[Defy Android Development] Gazm4n:
Tried it some weeks ago. Used default sizes for the images - worked.
[Defy Android Development] brajesh.sharma87:
Myself running CM7 as base and MIUI as virtual. Used the default file size given in the first post. :)
[Defy Android Development] diamond_4g64:
When i installed cm7, following the guide, i was indicated to run my rom on latest recovery as 2nd-init boot so if i want to use this program that i am ready to instal without loosing my stuff in cm7 can i simply use the other in stable recovery?
[Defy Android Development] trevor68:
Thank god I'm not the only one. :)

I went to stable recovery and ran the multi-boot zip. I then went to Custom Recovery and got a red light for awhile before it loaded (yes the image files from first post are in /fsimages). I was about to wipe cache/dalvik and load Quarx Froyo CM9, then had the same horrible thought, is my CM7 in Stable, or in Custom? :confused:
[Defy Android Development] trevor68:
bit the bullet and installed ICS Froyo build to custom recovery. It works fine, thanks for the handy mod.

I have issues with the market just downloading forever though, not sure if this is related to using the virtual, or just ICS maybe?
[Defy Android Development] brajesh.sharma87:
no problems in market download.

create a folder in cache/download and restart.
[Defy Android Development] trevor68:
yeah i had done that, which removed the errors, but just downloaded forever.

Funnily enough a few reboots later it just started working properly. :D
[Defy Android Development] diamond_4g64:
i am not getting this.

here is how i did the instal;

first i went in boot menu

i select boot

i select 2ndboot as default

i go in stable recovery

i wipe data

wipe cache

wipe dalvik

instal from sd in this order; multiboot, cm7, gapps

reboot

i go now in recovery

i instal from sd; miui, baseband switcher

reboot

now it reboots in miui and if i reboot i go in bootmenu and select 2nd init or 2nd boot and it will always open miui

how come i cant boot the first??
[Defy Android Development] m11kkaa:
The problem is that you installed the multibootmod BEFORE yout NAND-system(cm7).

An update of the NAND-System will always remove multiboot.

So just install cm7 and AFTER that install multibootmod.
[Defy Android Development] wyumhk:
Overclock & Vsel in virtual system

The settings in the bootmenu affect the main system only, and flashing new ROMs can usually preserve these values.

For virtual system :

I set the freq. & Vsel by editing the /system/bootmenu/config/overclock.conf in the virtual system. However, this file is overwritten when new ROM is flashed to the virtual.

How can I preserve these settings for the virtual system ? or just edit overclock.conf every time after re-flashing ?
[Defy Android Development] jpchopper:
Apparently I did something wrong. I've had multiboot working before, but this time cannot get it to work. I have CM7.2 on my stable recovery and tried putting CM9 (froyo kernel) into the virtual recovery. Wiped data, cache, dalvik etc, (in custom) then installed cm9 then gapps...

2nd boot stopped at red "M"

Booted back into cm7 on stable, wiped everything...usually safe b/c I have nandroids saved. Got an MD5 mismatch on every one.

Ended up wiping cache in stock recovery but (possibly) hit wrong button, because I lost 2nd init and now I'm in process of trying to reflash sbf.

Long story short, anyone have any ideas why 2nd boot/dual boot does not work? I've had it in the past working (before the last time I had to reflash sbf) but no joy this time.

I was using CEE as base ROM.

sorry for the rambling post but would love to have this working when I get phone back to life.
[Defy Android Development] diamond_4g64:
Right on the mark mate! Too bad i figured this out before youre post but thanks!!
[Defy Android Development] diamond_4g64:
Another question.

If i want to keep as is my stable recovery and flash a new virtual rom must i wipe data, cache and dalvik before i instal? Or i just go to latest recovery and go right to instal from sd card?
[Defy Android Development] wyumhk:
It is the same as you are working with the non-multiboot system :

Upgrading nighties ==> wipe cache & dalvik

Install different ROM ==> full wipe / factory reset / dalvik
[Defy Android Development] TJKV:
Doesn't wipe data/factory reset affect the main rom even if you do it from custom/latest recovery?
[Defy Android Development] wyumhk:
Is your CM7.2 on the main system also froyo ?

Both main / virtual should be the same kernel.
[Defy Android Development] jpchopper:
Pretty sure it was on froyo kernel, although I did also have the CM9 kernel 2.3.4 installed for playing with the defy+ CM9 versions. Was using CM7.2 on froyo, however, because I still use the camera (green lens defy)...

Still not sure why it wasn't working, and honestly, why cache wipe got rid of everything, either.

Will have to wait for fix, don't have a computer here, and work computer blocks install of rsd lite etc. so for the moment I seem to be up a foul smelling creek without a paddle...
[Defy Android Development] wyumhk:
Yes, you are right. Custom recovery "wipe data/factory reset" will delete the /sdcard/.android_secure, which contains the applications installed to the sdcard. I had such problem before, so I had installed both the main and virtual systems again :

Main system

Stable recovery

wipe data/factory reset

install cm7 (froyo) to the main

boot up ==> CM settings ==> application location ==> internal only

install S2E (not necessary, most probably)

reboot

install all other applications in main

Virtual system

reboot and flash the multiboot.zip

reboot then select custom recovery

wipe data/factory reset

install CM9 (froyo)

boot up and install all other applications in virtual

Since my applications are not installed to /sdcard/.android_secure, wipe data / factory reset deleting the directory will not cause any problem.

I just "Custom recovery" and "wipe data / factory reset" once again, and verified the main system was not affected.

I am sorry to recommend "wipe data / factory reset" without mentioning the above clearly.

EDIT :

Even doing the above steps, I have encountered problem once after wipe data.

It is more safe to have a fresh copy of /fsimages instead of "wipe data / factory reset".
[Defy Android Development] TJKV:
Then it isn't a problem for people who have no apps on the sd too :D

I don't, 1.3gb is big enough to fit all the apps I want with space to spare.

But I think a better way to clean install the virtual system is to delete the old fsimages folder, make a fresh one with empty images ;)

Or were you talking about something else?
[Defy Android Development] wyumhk:
Yes, big enough.

If people want even more space, they can use S2E if they are using CM7 as main, but this requires adding an ext3 partition to the sdcard.
[Defy Android Development] TJKV:
Btw, does wiui as virtual with cm7 froyo kernel work? It didn't seem to with 2.1.6 version of wiui... Wiui wouldn't boot.
[Defy Android Development] wyumhk:
Is wiui = WajkIUI 2.1.6 ICS ?

CM7 froyo (main) + WajkIUI 2.1.6 ICS (virtual) works !

I used this combination for 2 days.
[Defy Android Development] TJKV:
Yup, wajkiui. Hmm, that's funny. I'll try again reflashing multiboot mod. But I don't think that's the problem, because cm9 virtual works fine. What is the last boot/stable cm7 you flashed? The 11/11/11 special?
[Defy Android Development] bone101:
I Flash a New install of cm 7 stable 7.1.0.1 in 2nd boot .

After the procedur the cm7 was in first boot - strage or ?

and the cm9 image witch was before there is now in 2nd boot.

Ps.: anybody know where i can find somthing about the recoversystems ? I ve got a recovery sys. witch includes modules : restore/recover pds what is this ?
[Defy Android Development] wyumhk:
They are cm72-120102.0338 (Froyo) + WajkIUI.

The fsimage of WajkIUI is still on my sdcard, but just renamed to fsimage_WajkIUI. I just renamed the CM9 fsimage to fsimage1, fsimage_WajkIUI back to fsimage, boot into WajkIUI still no problem.

During boot up, red Moto appeared, LED turned blue, then red, this screen keep showing the red Moto for around 1 minute (or longer than 1 minute) ==> so please try again and wait a little longer time.

---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------

In my Defy, the LED is different when booting main/virtual.

Main : LED blue, then green.

Virtual : LED blue, then red.

How about yours ?
[Defy Android Development] antukubo:
Same as mine. Afaik it should be like that.

I flashed so many ROMs (wajkiui, miui, cm9, etc) on virtual for testing purpose. Some of them using multiboot V0.4 and some of them need to be flashed with V0.3. So, if anybody failed to flash their ROM, you might need to try different multiboot version.

Just a suggestion ;)
[Defy Android Development] TJKV:
Yes, I'm doing the same wrt the folders. Nope, moto logo was there for half an hour before i pulled the battery and retried the flashing, same thing the next time.

No I mean what was the last Stable you have flashed, not nightly. Nightlies do not replace the boot.img. I just want to know what boot.img (aka kernel) you have. Maybe you can tell me the kernel version in settings -> about phone if you don't remember the last stable you used?
[Defy Android Development] bone101:
You can change the kernel sepperatly...........

Tell me when i'm wrong :

boot.img = boot menue

Devtree = kernel

Recovery.img = cwm recovery version

Flash the nightly and the right kermel

And the system would work....

Cm7 = froyo kernel

Cm9 exist in an froyo and in an gingerbread kernel version
[Defy Android Development] TJKV:
Yup, that's my intention, when I have the time to transfer fresh fsimages and flash WajkIUI again, to try with a different boot.img...
[Defy Android Development] bone101:
I think you can only use froyo or ginger.......

Maybe the multiboot is behind the kernel ... In my multib. version 0.4
[Defy Android Development] TJKV:
Only froyo for my case, with CM7 and WIUI. Wanted to see kernel from which boot version of CM7 he is using, where wiui works
[Defy Android Development] bone101:
I corrected an error in my 2nd last post
[Defy Android Development] TJKV:
Um, okay, thanks I guess but seriously, don't take the trouble. I will just flash the relevant cm7 stable release and reflash my current nightly to get the correct version. So it doesn't really matter what is what :P
[Defy Android Development] jpchopper:
So.

I'm back up and running, new sbf and CM72 in stable recovery, installed multi boot .4

In latest recovery installed CM9 for froyo kernel and Google apps for same.

Rebooted, 2nd boot did nothing for almost 7 minutes.

Pulled battery, custom recovery and flashed CM7 kernel. Rebooted into 2nd boot, blue then red...then it shut down and booted back into normal (2nd init).

This repeated over and over again.

What am I doing wrong?

Thanks
[Defy Android Development] wyumhk:
I think the kernel is the same as yours. Please check the attached image.

So, I suggest you to try a clean install of WajkIUI again.
[Defy Android Development] K3n H1mur4:
Flashed CM9 (froyo kernel) in virtual system, booted and running. But my main system (MoKeeOS w/ froyo kernel) won't start (bootloops), only starts if I select "2nd init + adb" in boot menu, and gets LOADS of FCs at acore, calendar and satusbar. I'm booting at CM9 right now, gonna reflash MoKee at main system recovery to erase Multiboot.

I'm not sure if people was still getting this issue at this version of Multiboot, but I didn't have any problem with signal strenght, BTW. Anyway, I'll stick with single boot for now, until CM9 is fully working.
[Defy Android Development] wyumhk:
I had many FCs at acore in main system after installing the virtual (but no boot problem in the main). I don't know if the acore FC is related to the conflicts of apps installed to sdcard or not.

Anyway, by freshly re-installing the main and virtual as mentioned in http://xdaforums.com/showpost.php?p=21401063&postcount=249. My phone is fine for both main and virtual.
[Defy Android Development] hackergnome:
maybe coz nand data partition collapsed in sd system...

happent to me too... delete data.img from sd and reflash mokee...
[Defy Android Development] K3n H1mur4:
Tried it. Wiped data in virtual recovery, didn't work, still getting FCs. My main concern now is that I'm not able to mount USB storage (for some unknown reason, it never worked in recovery for me, and I can't get the statusbar to stay long enough so I can select USB storage and mount it). Tried an app who claims to automount usb, but got a message telling the app isn't compatible with my phone. If I mount it through the virtual system, it resets to the files I had when installing the system. I think I managed to get through this last issue, gonna test it now.

Tried renaming the fsimages folder, didn't work. Trying the solution I mentioned above, if it doesn't work, I'll try yours (but I'll rename data.img, I can't risk deleting it and being unable to mount the SD to place another FW and anoter data.img). Will edit with the situation after the break.

--EDIT--

Forgot to mention, both virtual recovery and normal recovery are of the same version, but are separate recoveries (since I wiped /data in the virtual system, but the apps in the normal system are all there and running). After wiping /data in the virtual system, I've got no more bootloops in the normal.

--EDIT'S EDIT--

Dunno if I got something wrong while copying MoKee to SDCard, but it won't install. I'll try renaming the data.img in SD, then, if it doesn't work, will try copying the fw and install it again. Right now, it seems the bootloop came back.

--EDIT'S EDIT'S EDIT--

Ok, I got what's wrong with copying: somehow, while in virtual system, it manages to recognize the SD and transfer the file to it. But, when entering stable recovery, it only show the file as having 0 bytes. It understands the file is there, but fails to recognize its content. Will try booting without SD to see what happens.

-Minor edit: flashed with no card, FCs still happening. Will try and get a way to put that goddamn zip into that SD and flash it, so I can get some sleep.

--FINAL EDIT (I SWEAR!)--

Got my mom's phone, put my SD into it, transferred MoKee's zip, and also renamed data.img to data.img1, to solve that other doubt. Installed flawlessly via recovery (so, as you can see, the issue was with transferring while using the virtual system - something about the SD being both mounted and unmounted, probably). Wiped cache and dalvik-cache. Yet, my system's getting FCs all the time. I'll try moving the whole fsimages folder to my computer (ain't safe to delete them yet), backuping my apps, and wiping data. It it doesn't do, I'll flash a goddamn SBF in it and start it all from the very beginning.
[Defy Android Development] hailmary:
LOLOLOL

it happend to me too...i did wipe data in virtual & got my defy crazy when i got back to base ROM then back to virtual & vice versa...

i just reflashed the base ROM & all worked fine,virtual is intact, only the base ROM corrupted -- i lost everything there:D
[Defy Android Development] antukubo:
Strange... I wipe data/factory reset + wipe cache partition so many times in virtual (when testing CM9, Wajkiui, Miui, etc) but my primary system didn't have any problem at all.

I guess it depends on the stability of primary system. From what I've read, the problem occurs mostly on CM7.2 Nightly & MoKeeOS.
[Defy Android Development] TJKV:
It happens when you have moved some apps to the SD card on the real system. When you do a Wipe Data from virtual, the real system's SD apps are also removed. I'm guessing that's why the problems. You probably didn't have any of the real system's apps on SD, so no problems.
[Defy Android Development] antukubo:
Yup! you're totally right :)