Develop Bugs

[MOD] MultiROM v31x [13/02/2015]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Many Stock-based ROMs will fail to install because their boot.imgs cannot be unpacked using normal tools or use unsupported compressions. Please contact me in that case, but do note I can't add support for each Stock-based ROM out here.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Don't try to flash ROMs with Stock boot.imgs (supported by LBs). They need special unpacking tools and are therefore currently not supported. I haven't yet tried flashing other Stock ROMs. Besides, I have configured MultiROM to only support boot.imgs that use the 2 stage boot method (boot.imgs with recovery ramdisks inside).
This is still a work in progress. Don't ask for ETAs please.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernel to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on OmniROM
Flash my modified kernel
Flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/tree/master (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/omnirom/android_kernel_sony_apq8064 (branch android-4.4)​
FAQs can be found here.
CREDITs
Tasssadar
Kr3i0s
omnirom
Everyone else mentioned here.
XDA:DevDB Information
MultiROM for Sony Xperia ZL, Tool/Utility for the Sony Xperia ZL
Contributors
Olivier
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Beta
Current Beta Version: 31x
Created 2014-09-02
Last Updated 2015-02-13

Changelog
DOWNLOADs
You can get everything from my build server.
CHANGELOG
Code:
[b]13/02/2015:[/b] Updated to v31x | Updated adb | Print error when multirom crashes | Added support for multiple entries per path in fstab | Set is_second_boot also if mrom_kexecd=1 is present in /proc/cmdline | Support interlaced PNGs | Updated to MultiROM TWRP 2.8.5 (incl. upstream <-> TWRP 2.8.5.0)
[b]17/01/2015:[/b] Updated to MultiROM TWRP 2.8.4 (incl. upstream <-> TWRP 2.8.4.0), fixed "Swap ROMs" feature
[b]08/01/2015:[/b] Inserted dummy line instead of removing to prevent breaking IFs (fixes the installation of AOSPA 5.0)
[b]04/01/2015:[/b] Updated to MultiROM TWRP 2.8.3 (incl. upstream <-> TWRP 2.8.1.3)
[b]08/12/2014:[/b] Fixed the installation of L-based ROMs as secondary ROMs
[b]04/12/2014:[/b] TWRP upstream
[b]28/11/2014:[/b] Moar TWRP upstream, updated to MultiROM v30x, fixed klog saving and text size on emergency reboot screen
[B]28/11/2014:[/B] Updated to MultiROM TWRP 2.8.1 (incl. upstream <-> TWRP 2.8.1.0) | Fixed perms of extract_elf_ramdisk
[B]23/10/2014:[/B] Upstream: Updated to v29x | Added "DirtyUnicorns icon" | Added device hook to allow incomplete fstab file | Bind mount /realdata to /data for rom quirks to work properly
[B]02/10/2014:[/B] Added support for external sdcard
[B]27/09/2014[/B]: Fixes for recovery, updated to MultiROM v28x (device-specific version)
[B]02/09/2014[/B]: Initial public release.

SUPPORTED KERNELs
OmniROM (and DirtyUnicorns, which is based off Omni)
lightning kernel by nikhil18

psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks

psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
DU should work too, but otherwise no.
AndreIrawan97 said:
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks
Click to expand...
Click to collapse
Yes, probably.

Thanks for this, it gave new life to my ZL! Multiboot rocks! I've managed to run Omni, CM11 and Carbon KK , so far so good. Are you also by chance doing a stock kernel for ZL that works with multirom, just like your stock kernel in Z? Hope you could also create stock kernel for ZL, really appreciate it. Thanks in advance.

What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?

francarl said:
What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?
Click to expand...
Click to collapse
I'd need you to upload a stock boot.img/kernel.elf in that case.

Olivier said:
I'd need you to upload a stock boot.img/kernel.elf in that case.
Click to expand...
Click to collapse
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.

^^ probably not, as multirom needs w/ kexec modification, which isn't listed above.
Did someone manage to boot ubuntu ( http://forum.xda-developers.com/showthread.php?t=2434585) in multirom? How?
Could we have native ubuntu touch support with the next version, please?
Gesendet von meinem Xperia ZL mit Tapatalk

stock rom as primary rom
ryanrudolf said:
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.
Click to expand...
Click to collapse
Thank you.
So could this kernel be used to start stock rom 10.5.1.A.0.283 as primary rom?

Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!

thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again

Olivier said:
Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!
Click to expand...
Click to collapse
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.

ryanrudolf said:
thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again
Click to expand...
Click to collapse
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
Kr3i0s said:
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.
Click to expand...
Click to collapse
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk

Olivier said:
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk
Click to expand...
Click to collapse
sorry for asking, but do you have any news on this? thanks

francarl said:
sorry for asking, but do you have any news on this? thanks
Click to expand...
Click to collapse
Patience please, I do have other things in life to do - I'll let you know for sure.
Gesendet von meinem Xperia Z mit Tapatalk

MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.

Olivier said:
MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.
Click to expand...
Click to collapse
@Olivier which version of lightning kernel to use?

Kr3i0s said:
@Olivier which version of lightning kernel to use?
Click to expand...
Click to collapse
The one for Stock ROMs.

[MOD][SEP 25][MULTIBOOT] MultiROM v32a

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-armani.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_armani_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
Currently dual booting MIUI isn't working! So DO NOT try to dual boot MIUI with LP/KK ROMs.​
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 676mb of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/multirom-armani/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/multirom-armani/android_kernel_xiaomi_armani/tree/multirom(branch multirom)
MultiROM device tree - https://github.com/multirom-armani/android_device_xiaomi_armani/tree/multirom (branch multirom)​
Credits
@Tasssadar (for making this awesome utility!)
@KINGbabasula (armani's multirom is possible cz of him!)
@akhilnarang (He's the person who's always present to help! Cheers!)
@vasishath (For pointing out the fix for white glitch)
All my dear testers! Thanks for testing!
​
XDA:DevDB Information
MultiROM for Xiaomi Redmi 1S, Tool/Utility for the Xiaomi Redmi 1S
Contributors
TheStrix
Source Code: https://github.com/multirom-armani/
Version Information
Status: Stable
Current Stable Version: 32a
Created 2015-09-05
Last Updated 2015-09-25

Downloads
1. Main downloads
MultiROM: multirom-20150925-v32a-armani.zip
Modified recovery (based on TWRP): TWRP_multirom-armani_20150925.img
MultiROM Manager Android app: Google Play or link to APK (NEW!)
Kernel w/ kexec-hardboot patch (LP ROMs): LP_kexec_20150925.zip
Kernel w/ kexec-hardboot patch (KK ROMs): KK_kexec_20150925.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!​
2. third-party kernels with kexec-hardboot patch
Yet to come!
Nicely ask your kernel developer to merge kexec-hardboot patch.​
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.​
Changelog
Code:
04/09/2015-MultiROM v32
==========
* Initial stable release for armani
25/09/2015-MultiROM v32a
==========
* Fix white noise while booting secondary ROMs
* Added new updated KK and LP kexec patched kernels
Recoveries:
Code:
04/09/2015
==========
* Initial stable release for armani
* MultiROM TWRP 2.8.7
25/09/2015
==========
* Upstream changes

FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM​
Installation Video
Thanks to YouTuber Dhananjay Bhosale (@TheDj408) for making this awesome installation video!

Awesome Work Buddy
This is a outstanding work buddy
Keep it UP
Thanks for MultiROM

Great work @TheStrix
Sent from my A0001 using Tapatalk

GREAT WORK , THANKS BUDDY !!
Can you upload some Screenshots/Images/Video for better understanding

Something new for our device after a long time.

Awesome work @TheStrix ! Guys Smash that Thanks button

Nice work mate @TheStrix now armani users can enjoy two roms
Sent From My Yuphoria Using Tapatalk

Gunikmaliwal said:
GREAT WORK , THANKS BUDDY !!
Can you upload some Screenshots/Images/Video for better understanding
Click to expand...
Click to collapse
Screenshots added in "Screenshots" tab
And for installation video, I'll wait for some great YouTuber's to make one. Till that you can see multirom installation video for other devices which are using manual method and not Multirom app method to install multirom.

Wow ... Awesome dude

Wow more boot option ... Lets break this phones guys !!!! You god dang flasholic !!!!

The only mod which was missing from redmi
Thanks a lot

Awesomeeeeeeeeeeeeeeeeeeeeeeee.
Thank you @TheStrix . Awesome work and something this device needs with tons of ROMs. Waiting for MIUI + CM dual boot . Would love to see that . And with the upcoming of sailfish OS redmi is gonna rock .

Awesome work @TheStrix! This is gonna rock!

Dude sweet u managed to port it to our device. Was enjoying it on my hammerhead.
Sent from my HM 1S using Tapatalk

I've contacted Dhananjay Bhosale ( https://www.youtube.com/user/dhananjaybhosale1 ) for Video on Installation !

Its working flawless...waiting for devs to include hardboot patch in beast and xecelerate kernel
Sent from my HM 1S using Tapatalk

Great work ... Will this support r the same with the other project like EFIDroid? Its like having native grub loader into the phone
Sent from somewhere on earth

elmumtaz said:
Great work ... Will this support r the same with the other project like EFIDroid? Its like having native grub loader into the phone
Sent from somewhere on earth
Click to expand...
Click to collapse
Yes, functions same as Grub/EFIDroid
You'll see multirom menu to choose the system you want to boot into.

Dual Boot?

Hey,
im wondering if LG G4 (h815) ist working with Dual Boot Patcher.
Any Experience?

I'm also interested in dual booting. Having CM13 with stock ROM also to take photos would be perfect.
Any ideas?

I'm also intersted in it

Best thing is to patch TWRP with Multirom and kernel developers implement that patch on their kernels.
But seeing the low development going on with G4(mostly because of bootloader) I doubt that we will have that so soon.

I'm interested too. It would be great to have this option ! I need stock rom for photos too and would like another rom like cm13 for daily use. I see that this is available for G3 so let's hope it will be developed for G4 soon too.

I have Dual Boot Patcher running on my rooted H815. Genysis as primary and CM13 installed using a data slot. I sent a log to the developer and he got it working within a few days.

bobblesop said:
I have Dual Boot Patcher running on my rooted H815. Genysis as primary and CM13 installed using a data slot. I sent a log to the developer and he got it working within a few days.
Click to expand...
Click to collapse
Hi mate,
That is nice to hear this. Will you share with us how you set it up? Which build you used and which options you choosed (like the one that you put the CM13 on the data slot) to sucessfully make it work ? I really want to be able to dualboot as you do. I tried to patch an AICP rom and to install it on the data slot but when I tried to flash it I received only errors (like dual boot failed to load recovery partition image and some more lines like this one). Thank you !

I installed the latest dual boot patcher app and set the kernel. I then patched the CM13 and Gapps zips for data slot 1. I didn't try flashing these within the dual boot app but did it from TWRP. That rebooted to CM13 so I installed the dual boot patcher app again and can now dual boot!

bobblesop said:
I installed the latest dual boot patcher app and set the kernel. I then patched the CM13 and Gapps zips for data slot 1. I didn't try flashing these within the dual boot app but did it from TWRP. That rebooted to CM13 so I installed the dual boot patcher app again and can now dual boot!
Click to expand...
Click to collapse
Hi,
I tried the same steps just like you and I still got errors. I uploaded the multiboot.log file so if somebody can help me to check it and tell me what I'm doing wrong. Thanks !

You might be better uploading the log to the original thread in the galaxy S4 forum. The developer seems to respond to most issues.

I tried with CM13 as main rom, patched kernel, patched ZIP of an official ROM as secondary, went to recovery to flash it but it gave an error :/.
If someone gets it working please write a mini tutorial

bobblesop said:
You might be better uploading the log to the original thread in the galaxy S4 forum. The developer seems to respond to most issues.
Click to expand...
Click to collapse
Maybe I will do this for sure. But first can you tell me which version of TWRP recovery are you using and exactly the number and name of the DualBoot app ? I'm starting to think that the errors come from my TWRP version. Is this possible ?

I have successfully flashed patched CM13 roms & Gapps using TWRP 2.8.7.0 and 3.0.0.0 I have used a few dual boot patcher app builds from mid February and have 8.0.0.r2304.g03481db-SNAPSHOT installed and tested at the minute.
I had trouble flashing aroma based installs before on my G3.

I have Dual Boot Yeah
First Rom : Stock MM 6.0
Second Rom : AICP MM 6.0.1 du 25/03/2016
Easy
no problem , no bug , just i haven't gapps installed
sorry for my bad english

Can somebody write a little tutorial for dual boot on G4?
I know that we must patch all the zips for the second rom but where to flash them?
On the system?With twrp or with dual boot patcher?
Create a new slot in internal storage?How?How big?
And how to switch between roms?
Thank you in advance ☺
Sent from my LG G4

Ok guys,
I've found a tutorial on some french forum and I translated it
Prerequisite:
LG G4 ROOTED with at least 5 GB of free storage
Have installed a custom recovery
A second custom rom + kernel (AROMA not supported)
Making a Nandroid Backup (not required, but recommended)
Download and install the application -> https://snapshots.noobdev.io/
Procedure:
1.First, install the Dual Boot Patcher application (DBP), and open one, and allow root permissions when prompted
2.In the application, in the upper left corner, press the 3 horizontal lines and then "ROMs"
3. Then press the three dots of primary Rom to view the settings and then click "Set the kernel" and click on "CONTINUE"
4. Return to the main menu of the application, and press "Patch zip file."
5.In the menu that appears under "Device and partition configuration," press the arrow and select "IgG4 (IgG4)"
6.Below, in the "Partition configuration", press the arrow and select "Data slot" then choose and enter the name of your second Rom (Secondary example). Please note, it may break you download an English dictionary in your keyboard so you can enter a name.
7.When done, press below on "Press to select a file to patch." Select the zip file of the secondary rom, then press "Touch to start patching"
8.A message confirms that the patch of the Rom went well. Go back into the menu and try "Patching a zip file", but select the kernel this time.
9.After the patching, press in the main menu to "ROMs" and then press the red round button at the bottom right, accept the message with "OK", then press again the red button that displays a "+"
10.Select the secondary patched rom. You will recognize as "secondary" to appear in its name. Reflash it by pressing "✓" in the upper right.
11. Do the same, but select the kernel file of the secondary rom patched. Reflash it by pressing "✓" in the upper right once it is selected.
12.Once done, press "Secondary (slot Data)" (or the name you gave your second Rom) then in the application menu press "Restart."
13.The second Rom starts, it can take up to 10 minutes. Once started, the application will install Dual Boot Patcher
14.Open one, then press "ROMs". Open the menu of secondary rom and press "set the kernel". It's finish !! You can enjoy the dual boot!

[emoji4] [emoji4]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Envoyé de mon LG-H815 en utilisant Tapatalk

herveonex said:
[emoji4] [emoji4]
Envoyé de mon LG-H815 en utilisant Tapatalk
Click to expand...
Click to collapse
How did you do it?
When I tap on Set kernel I get the message "Failed to set kernel"...
And where did you get 6.0.1 rom?
Sent from my LG G4

.Genisys + kernel superxe v1.8 is ok ,no failed
.6.0.1 is vanilla unicorn.
Envoyé de mon LG-H815 en utilisant Tapatalk

So if you're secondary flashing a CM13 ROM and a kernel, do you flash Gapps as well?

[GUIDE] Dualboot Custom ROMs on L5 and L7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
​

Thanks for the mention

@WinterR test the unofficial snapshot, please

What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1

ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img

Now DualBootPatcher supports the L7 and L7II!!!

I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?

@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )

If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?

So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?

ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).

Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel

Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel

Thread closed as per OP request.
-XDA Staff

[MOD][APR 11][DEV] MultiROM v33

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Omni TWRP - https://github.com/lj50036/platform_manifest_twrp_omni (branch twrp-6.0)​
Donations
[MENTION=3418703"Tasssadar[/MENTION] would be glad if you could spare a few bucks. You can use either paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris. And if you want to donate me for porting the updated version of MultiROM, PM me .
Thanks to all donors, it is much appreciated ​
XDA:DevDB Information
MultiROM Xperia Z1, Tool/Utility for the Sony Xperia Z1
Contributors
aquaboy11
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-12

Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk

drakonizer said:
Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.

aquaboy11 said:
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.
Click to expand...
Click to collapse
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?

drakonizer said:
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?
Click to expand...
Click to collapse
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.

aquaboy11 said:
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.
Click to expand...
Click to collapse
So you mean the recovery? I've got that working too, seems like we're both stuck at the same point...unfortunately we don't have the sources of the old multirom v30x.

Is it only me? I cannot find download links for your version

Hitman73 said:
Is it only me? I cannot find download links for your version
Click to expand...
Click to collapse
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs

drakonizer said:
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs
Click to expand...
Click to collapse
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.

aquaboy11 said:
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.
Click to expand...
Click to collapse
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.

drakonizer said:
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.
Click to expand...
Click to collapse
MultiROM v30 boots fine.
I used Sony's device tree
mr_init_devices.c
Everything from BoardConfig.mk after line 41.
I could give porting kexec to MM a shot when I have some spare time.

Hi. I experienced a problem entering the recovery. My device stuck at the Sony symbol displayed an the orange LED when I try to enter. Before I updated my recovery I used the one from v30 thread without any problems. Any idea where the problem is?
Thanks in advance!

LB multirom
Hello, I have a small question ...
If I install MultiROM v33 on my Xperia Z (LB) "locked bootloader",
can i install secondary ROMs for unlocked bootloader ???
thank you

Is this still being worked on?