Post Reply

[MOD][RECOVERY] Multiboot v2.11 - update 14/04/01 (ubuntu touch support)

OP Phil_Suz

17th March 2014, 03:38 AM   |  #1  
OP Member
Flag Montreal
Thanks Meter: 286
 
91 posts
Join Date:Joined: Dec 2013
More
Hi all,

This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/show....php?t=2577211

With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/show....php?t=1266827).

I adapted this method to be able to apply it quite easily on any android device.

This method includes few pieces of software ( sources will be published) :
  • kexec-hardboot : kernel patch from mkasic
  • hardboot-reserve : new kernel patch
  • kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.


Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.

Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )

Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.

You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ

Main advantages of using qcow2 :
  • thin provisionning
  • snapshots
  • compression
  • liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
  • need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/show....php?t=2226889
  • Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
  • suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
  1. - standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
  2. - livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
  3. - liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
  4. - fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
  5. - livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.




Downloads : http://www.androidfilehost.com/?w=files&flid=12801

References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/show....php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/show....php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
Last edited by Phil_Suz; 1st April 2014 at 06:12 PM.
The Following 21 Users Say Thank You to Phil_Suz For This Useful Post: [ View ]
17th March 2014, 03:38 AM   |  #2  
OP Member
Flag Montreal
Thanks Meter: 286
 
91 posts
Join Date:Joined: Dec 2013
More
reserved
The Following 3 Users Say Thank You to Phil_Suz For This Useful Post: [ View ]
17th March 2014, 08:49 AM   |  #3  
matrixzone's Avatar
Senior Member
Thanks Meter: 783
 
2,487 posts
Join Date:Joined: Mar 2012
More
First

Sent from my SAMSUNG-SGH-I747 using Tapatalk
17th March 2014, 02:43 PM   |  #4  
FeelLikeThis's Avatar
Member
Flag Wahiawa
Thanks Meter: 43
 
84 posts
Join Date:Joined: Oct 2011
More
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.

Sent from my SCH-I535 using Tapatalk
17th March 2014, 05:32 PM   |  #5  
PwnCakes193's Avatar
Senior Member
Flag Somewhere, Someplace
Thanks Meter: 6,868
 
2,504 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Totally forgot about this, I'll have NBD included in my next kernel so this can work
The Following 7 Users Say Thank You to PwnCakes193 For This Useful Post: [ View ]
18th March 2014, 08:36 AM   |  #6  
Member
Thanks Meter: 11
 
49 posts
Join Date:Joined: Oct 2012
this is awesome ! i been looking for muilt-boot since i got an S3 !

it's working great!
18th March 2014, 01:38 PM   |  #7  
vbetts's Avatar
Senior Member
Flag Toledo Ohio
Thanks Meter: 54
 
991 posts
Join Date:Joined: Jun 2010
More
Awesome!

Now does it matter what bootloader you're on for this?
18th March 2014, 07:56 PM   |  #8  
Member
Flag Shawnee
Thanks Meter: 6
 
34 posts
Join Date:Joined: Sep 2012
More
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.

Do these videos have audio? kinda hard to follow... or it just my laptop?
Last edited by Walknmemfs; 19th March 2014 at 03:10 AM. Reason: correct spelling
21st March 2014, 09:56 PM   |  #9  
stanguay's Avatar
Senior Member
Flag Magog, Quebec
Thanks Meter: 38
 
136 posts
Join Date:Joined: Aug 2009
More
Restore
Hello,

Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed

I try with different TWRP 2.6.3.1 and 2.7.0

Do you have and idea how to fix that.

Thanks
22nd March 2014, 02:41 AM   |  #10  
OP Member
Flag Montreal
Thanks Meter: 286
 
91 posts
Join Date:Joined: Dec 2013
More
Quote:
Originally Posted by PwnCakes193

Totally forgot about this, I'll have NBD included in my next kernel so this can work

I will add a link to your kernel in first message when it becomes compatible with qcow2 support.

Quote:
Originally Posted by vbetts

Now does it matter what bootloader you're on for this?

There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )

Quote:
Originally Posted by stanguay

Hello,

Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed

I try with different TWRP 2.6.3.1 and 2.7.0

Do you have and idea how to fix that.

Thanks

As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?


Philippe,

The Following User Says Thank You to Phil_Suz For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in AT&T Galaxy S III Android Development by ThreadRank