FORUMS
Remove All Ads from XDA

[DEV][2012/08/29] Multiboot v0.8

1,253 posts
Thanks Meter: 2,123
 
By m11kkaa, Recognized Developer / Contributor on 27th November 2011, 07:44 AM
Post Reply Email Thread
So I created a new thread for this so I can edit the first post for release-info.
This is the old thread:
http://forum.xda-developers.com/show....php?t=1133866

Please note that the multiboot-feature will be removed if you update your real system.
The virtual systems will stay on the sdcard so just reinstall the mod and you can boot your virtual systems again


Changelog:
Code:
v0.8:
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system

v0.7:
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu

v0.6.1:
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start

v0.6:
- new hook-method with kernel-side code which should be the solution to most rom-problems 
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future

v0.5.5:
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)

v0.5.4:
- fixed problem with install-script

v0.5.3:
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms

v0.5.2:
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms

v0.5.1:
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)

v0.5:
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot

v0.4:
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img). 
  Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference

v0.3/v0.3.1:
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes

v0.2:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)

v0.1:
First release

Source:
https://github.com/M1cha/DefyMultiboot

Download:
http://forum.xda-developers.com/atta...3&d=1346244428

Installation:
1. Download zip-file and copy to sdcard
2. create 3 filesystem-images in ext3-format and copy them to /sdcard/multiboot/NAME with the names system.img, data.img and cache.img.
Please replace NAME with the folder-name of your virtual system(you have to create this)
You can download ready-to-use images from here:
http://www.multiupload.com/VY3U4IXRO1
2. install zip-file in CWM


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


Bugs:
- Data-Wipe deletes android_secure


Donate:
Developing Multiboot makes much fun and I really like the results but takes much time, so feel free to donate a beer.
The Following 122 Users Say Thank You to m11kkaa For This Useful Post: [ View ]
 
 
27th November 2011, 09:38 AM |#2  
Senior Member
Flag RLP
Thanks Meter: 17
 
More
Hey,
i have no "Lastest Recovery" but a "Custom Recovery"
Can i install your script or does it not work with this version of the Bootmenu?
The Following User Says Thank You to deskjeti For This Useful Post: [ View ] Gift deskjeti Ad-Free
27th November 2011, 09:48 AM |#3  
m11kkaa's Avatar
OP Recognized Developer / Contributor
Thanks Meter: 2,123
 
Donate to Me
More
Which rom do you have installed?
I will check if it's compatible.
The Following 2 Users Say Thank You to m11kkaa For This Useful Post: [ View ]
27th November 2011, 09:51 AM |#4  
Senior Member
Flag RLP
Thanks Meter: 17
 
More
Thanks for the fast answer
i installed the CM7.2 Nightly "cm72-111125.0850-NIGHTLY-Defy"
27th November 2011, 10:14 AM |#5  
m11kkaa's Avatar
OP Recognized Developer / Contributor
Thanks Meter: 2,123
 
Donate to Me
More
The nightlys should always have the newest version of bootmenu.
Where you downloaded the nightly? I only could find "cm72-111123.1710-NIGHTLY-Defy.zip".

But generally it would work if you install but the problem is that you will never be able to change your real system because recovery will only make changes to the virtual one.

That bootmenu has 2 recovery-entrys is a lucky thing which I use as trick so I don't need to modify bootmenu

But when bootmenu-integration is done and you have an old version you will have to update bootmenu.
The Following 2 Users Say Thank You to m11kkaa For This Useful Post: [ View ]
27th November 2011, 10:45 AM |#6  
m11kkaa's Avatar
OP Recognized Developer / Contributor
Thanks Meter: 2,123
 
Donate to Me
More
updated to v0.4
See first post for more info
The Following User Says Thank You to m11kkaa For This Useful Post: [ View ]
27th November 2011, 12:18 PM |#7  
Senior Member
Thanks Meter: 2,755
 
More
Gonna try this now. I downloaded your empty .img files but how do I create my own img's on Win7? And what do you think is the smallest size I can make them safely to use with MIUI or ICS?
27th November 2011, 12:30 PM |#8  
m11kkaa's Avatar
OP Recognized Developer / Contributor
Thanks Meter: 2,123
 
Donate to Me
More
I don't know how you can create the images on windows, sry.
Maybe I can write a little App which does this directly on Android.

I have to admit that the images I uploaded are a little bit oversized.
system needs max 200MB
cache and data depends on your usage.
I would choose a minimum of 100MB for data and cache. If you plan to install many Apps you should make the data-partition over 300-500MB
The Following 2 Users Say Thank You to m11kkaa For This Useful Post: [ View ]
27th November 2011, 12:34 PM |#9  
Senior Member
Thanks Meter: 2,755
 
More
Doesn't matter, instructions for Linux would do too

Hmm..oversized but no prob downloading because they were empty, only transferring via USB takes time. 200 MB for system and data and 100 for cache sounds good I'll make them myself if you can give me the instructions, I have Ubuntu.

App to do this on the phone itself sounds good, makes it even faster, no transferring from PC Thanks for your work
27th November 2011, 12:51 PM |#10  
m11kkaa's Avatar
OP Recognized Developer / Contributor
Thanks Meter: 2,123
 
Donate to Me
More
The Problem is that I can't find a mkfs.ext3-binary for Android
Maybe I'll extract it from another phone which contains this.

But as of now, here are the instructions:
Code:
dd if=/dev/zero of=./system.img bs=1000000 count=200
mkfs.ext3 ./system.img
The number 200 specifies the size in MegaBytes. I hope this will help you so far
The Following 2 Users Say Thank You to m11kkaa For This Useful Post: [ View ]
27th November 2011, 01:03 PM |#11  
Senior Member
Thanks Meter: 2,755
 
More
Sure does

But like the poster above said, CM7 latest nightiles contain Custom Recovery, Stable Recovery, and Stock Recovery in the Bootmenu option for recovery. So Custom Recovery = Latest Recovery for your tool? I remember it used to say Latest recovery a few months back, dunno when that changed.
Post Reply Subscribe to Thread

Tags
multiboot defy

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes