Database Develop

[MOD] MultiROM v32x [12/11/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. -- If you are on a stock-based ROM .230, flash this kernel.
This is still a work in progress. Only ROMs like as Omni, CM11 or Carbon have been confirmed working as of yet. 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 kernels 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 OR on any ROM based on 10.5.A.0.230/233 (or any other ROM compatible with these kernels)
Flash a supported kernel
Reboot into MultiROM TWRP and 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/olivieer/android_kernel_sony_apq8064 (HodorKernel | branch 10.5.A.0.xxx) and https://github.com/omnirom/android_kernel_sony_apq8064 (branch android-4.4)​
FAQs can be found here.
CREDITs
Tasssadar
domicq
omnirom
Everyone else mentioned here.
XDA:DevDB Information
MultiROM for Sony Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
Olivier
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-11-12
Created 2014-08-10
Last Updated 2015-11-12

Changelog
DOWNLOAD
You can always get the latest releases from my build server or using the MultiROM Manager.
CHANGELOG
Code:
[b]12/11/2015:[/b] Updated MultiROM to v32x and MultiROM TWRP to 2.8.7 (incl. upstream <-> TWRP 2.8.7.0)
[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]29/01/2015:[/b] Improved compability with some ROMs
[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.3.0)
[b]08/12/2014:[/b] Fixed the installation of L-based ROMs as secondary ROMs
[b]04/12/2014:[/b] TWRP upstream
[b]21/11/2014:[/b] Moar TWRP upstream, updated to MultiROM v30x, fixed klog saving and text size on emergency reboot screen
[B]01/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), added kernel for [B]10.5.A.0.283[/B]-based ROMs
[B]14/09/2014:[/B] Added [I]new[/I] kernel for CM11 (new blobs/kernel)
[B]03/09/2014:[/B] Added kernel for CM11 (old blobs/kernel)
[B]31/08/2014:[/B]: Updated to v28 | fixed MultiROM loading twice | automatically replace recovery ramdisk
[B]11/08/2014:[/B] Added another kexec-hardboot-patched kernel based on [B]10.5.A.0.230[/B] ([URL="http://forum.xda-developers.com/devdb/project/dl/?id=7909"]boot_230.img[/URL]) and a [URL="http://forum.xda-developers.com/devdb/project/dl/?id=7908"]flashable multirom uninstaller[/URL] - [COLOR="Lime"]Stock-based ROMs now supported![/COLOR]
[B]10/08/2014:[/B] Initial public release.

Currently supported kernels
SUPPORTED KERNELs/ROMs
HodorKernel (4.4.4 Stock)
Lightning Kernel (CM11 | 4.4 Stock)
KMA Kernel (CM11)
OmniROM 4.4.4 (supported by default)
ParanoidAndroid 4+ (supported by default)
ParanoidAndroid 5+ (supported by default)
SlimKat (supported by default)
SlimLP (supported by default)
Validus ROM (supported by default)
Zombie Kernel (4.3 Stock | 4.4.4 Stock )
EDIT: Almost every kernel support kexec-hardboot now, I've hence stopped updating this list.

Looks very good, thanks for your work
Gesendet von meinem Nexus 5

Bro can I add the kexec hardboot patch to my lightning kernel based on cm source thanks

i flashed boot.img but i dont have the modified twrp recovery i still have my old recovery ( Philz Touch ) anyway to manually flash recovery only?

nikhil18 said:
Bro can I add the kexec hardboot patch to my lightning kernel based on cm source thanks
Click to expand...
Click to collapse
Of course.
Akil97 said:
i flashed boot.img but i dont have the modified twrp recovery i still have my old recovery ( Philz Touch ) anyway to manually flash recovery only?
Click to expand...
Click to collapse
Your kernel also needs to be kexec-hardboot-patched so you have to flash the one from the OP.
Gesendet von meinem Xperia Z mit Tapatalk

Olivier said:
Of course.
Your kernel also needs to be kexec-hardboot-patched so you have to flash the one from the OP.
Gesendet von meinem Xperia Z mit Tapatalk
Click to expand...
Click to collapse
Actually i flashed your modified OmniROM kernel with kexec support but i did'nt get the recovery tried flashing it two times

Did you do it via fastboot like op stated?

I frankly don't know what you're doing wrong. To get sure I didn't upload a wrong file, I re-downloaded and tested it and... it does work.

I have carbon band first boot crash... I flash omni band again

After installing MultiROM can we change the primary ROM to anyother ROM or it has to be OMNI based?

Oliviers modified recovery will not boot if you have other recovery installed in FOTA. You need to wipe it first.

zakitheracer said:
After installing MultiROM can we change the primary ROM to anyother ROM or it has to be OMNI based?
Click to expand...
Click to collapse
As of now, you have to flash my kernel (intended for OmniROM), hence your Internal ("primary") ROM has to be compatible with it.
macia10 said:
Oliviers modified recovery will not boot if you have other recovery installed in FOTA. You need to wipe it first.
Click to expand...
Click to collapse
I'd recommend keeping MultiROM TWRP recovery in the FOTA partition by the way.

Olivier said:
I'd recommend keeping MultiROM TWRP recovery in the FOTA partition by the way.
Click to expand...
Click to collapse
But its not installed to FOTA by default so it would be good to add an instruction on how to install it to FOTA

So it is possible in future for the boot.IMG to be compatible with CM11?
Sent from my Xperia Z using Tapatalk

Quick tips : If you're using stock ROM right now you should wait for a specific kernel to be released first to use with this multiboot.
please do correct me if I'm mistaken.
Sent from my C6603 using Tapatalk 2

A new build is up as well as a patched boot.img for all ROMs based on 10.5.A.0.230/233. I have updated the OP and the Changelog.

Good idea would be FOTA multiTWRP with ability to inject kexec support to any installed kernel.

The Boot img for .230 ROMs is softbrocking my phone for some reason
Flashing it on eXistenz

[MOD][Arm64]MultiROM for YU Yureka[v33][Beta 1]

{
"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
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-tomato.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (twrp_mrom.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 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 easily 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.
Downloads
1. Main downloads
MultiROM: multirom-20160220-v33-UNOFFICIAL-tomato.zip
Modified recovery (based on TWRP): recovery_mrom.img
Kexec-harboot kernel : Dominator-v2.4-2016-02-16-0953-UB.zip
2. Third-party kernels with kexec-hardboot patch
Yet to come!
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.
Credits
@abhishek987
@TheStrix
This port is based on the hard work of @Tasssadar, @500 Internal Server Error, Geoff Levand, @webgeek1234, Mike Kasick, @Hashbang173, and many others. Thank you.
XDA:DevDB Information
MultiROM for YU Yureka, Tool/Utility for the YU Yureka
Contributors
Men_in_black007, abhishek987
Version Information
Status: Testing
Created 2016-02-23
Last Updated 2016-02-23

FAQ's
1. Should I flash recovery only via Flashify app?
-Not essentially, You can flash it via recovery.
Boot to TWRP.
Install->Tap on Images(bottom right screen)>Locate and select your recovery.img
Flash to 'Recovery' partition.
Reboot back to TWRP(IMPORTANT).
2. Can I flash any other kernels?
-As of now NO. Only the given 'Dominator Kernel'
You can flash only 'kexec hardboot' supported kernels. Other kernels won't work.
Don't worry within few days, Devs are going to add support to their kernels.
3. Which roms can I flash?
-All Android 5.1+ roms can be flashed without any issues.
14 How to flash without Hardbricking?
-Follow the steps from OP and there are videos to make the things easy in initial pages.
Maximum it causes bootloops(softbrick), not hardbrick if you follow the guide.
5. Can I flash roms to ext-sd card and USB-otg? How?
-Yes you can flash them to ext-sd card and USB-otg.
Boot to TWRP.
Tap on Multirom.
Tap on ADD ROM
Select the right Location
Spoiler: Meomry Location SS
Flashing on ext-sd and USB otg takes some time, so be patient, don't freak out!
6. Where to find roms installed in my ext-sd and USB? How to boot into 'em?
-After flashing you'll be booted into MultiROM menu.
All your roms flashed on internal memory will be in Internal tab.
Others will be in External tab.
Spoiler: Screenshot
7. How to rename/remove/delete/wipe dalvik & cache or flash any other zips to existing rom?
-Follow
Boot to recovery.
Tap on MultROM
Tap on the rom which you want to remove/add zips.
You'll find all the options you need!
Spoiler: Screenshot
8. Is there any option of app sharing?
-NO. This is entirely different from mboot. You need to install separate apps in each ROM.
9. "Unable to flash, I'm getting errors" / "Executing updater script failed" / "Rom is not booting" ????
-Please provide logs. It'll be located in /data/media/0/multirom/last_kexec. log
It'd great if you can provide the screenshots.
Press VOL DOWN + LOCK KEY to take Screenshots.
Bugs
This is just a beta build so bugs are expected some of bugs the bugs which I am aware of are
* Roms above 5.1 are working (5.1 roms are also working)
* Ported roms are not working however roms ported as taking 5.1 gets boot
If you found any just report me
Video
Check this video for proper installation :
https://youtu.be/aAYSLt8zjNE

RESERVED

excellent work....
finally multi rom recovery is here.....
thanks bro...

@Men_in_black007, in muliboot app, when I click on rom, I get the error "could not determine the boot partition because this device's codename 'YUREKA' is not recognized." no matter which ROM i flash.
Please let me know if there is a work around for this.
I have tried flashing cm12.1 latest nightly , MIUI V7 developer edition v6.3.24, cm 13 latest nightly as primary ROMS.

Reserved
Reserved...
Trying it. Exited.:highfive:

there is no multirom option in advanced....please help

No link for Uninstallation.

Do we hav to keep the given kernel installed for using multirom? Or can we change it once secondary rom is installed?
Sent from my AO5510 using XDA-Developers mobile app

Dominator kernel isn't working with new official cm13 nightly builds.. Please fix...

purig said:
Dominator kernel isn't working with new official cm13 nightly builds.. Please fix...
Click to expand...
Click to collapse
Yes, it won't work until gets updated with new source.

What is the android version of this rom??is it AOSP based??thank you!!

Yureka + ?
Men_in_black007 said:
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
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-tomato.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (twrp_mrom.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 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 easily 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.
Downloads
1. Main downloads
MultiROM: multirom-20160220-v33-UNOFFICIAL-tomato.zip
Modified recovery (based on TWRP): recovery_mrom.img
Kexec-harboot kernel : Dominator-v2.4-2016-02-16-0953-UB.zip
2. Third-party kernels with kexec-hardboot patch
Yet to come!
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.
Credits
@abhishek987
@TheStrix
This port is based on the hard work of @Tasssadar, @500 Internal Server Error, Geoff Levand, @webgeek1234, Mike Kasick, @Hashbang173, and many others. Thank you.
XDA:DevDB Information
MultiROM for YU Yureka, Tool/Utility for the YU Yureka
Contributors
Men_in_black007, abhishek987
Version Information
Status: Testing
Created 2016-02-23
Last Updated 2016-02-23
Click to expand...
Click to collapse
Sir can I use this in my yureka plus?

where is multirom apk??

[MOD] MultiROM for Xperia SP

{
"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. 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
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 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-device.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-fota-device.zip) - download the ZIP file from second post and use a recovery
to flash it into the FOTA partition (see TWRP 3 thread for more informations).
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
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.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
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 Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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.
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/AdrianDC/multirom_core (branch master)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch master)
Device Tree - https://github.com/XperiaMultiROM/android_device_sony_huashan (branch master)​
MultiROM available for Huashan also thanks to :- [MENTION]Tasssadar[/MENTION]
- The XperiaMultiROM team
- The MultiROM HTC team
- [MENTION]Arvind7352[/MENTION]
- [MENTION]nkk71[/MENTION]​
XDA:DevDB Information
MultiROM for Xperia SP, Tool/Utility for the Sony Xperia SP
Contributors
Adrian DC
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-04-03
Last Updated 2017-06-07

Reserved
Downloads
1. Main downloads
Xperia SP (Huashan): https://mega.nz/#F!mpMATaJa!gGshpOwYueKdK0bu6YSNUg
MultiROM: multirom-2017MMDD-v33x-device.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-device.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8960t Marshmallow based): kernel-2016MMDD-device.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
No longer required thanks to the no-kexec workaround.
OPTIONAL: MultiROM installed as a secondary "ROM": multirom-2016MMDD-recovery-secondary-device.zip
Mostly meant to be used for Stock ROMs users and devs. Only use as secondary ROM to flash.​
2. Third-party kernels with kexec-hardboot patch
* None, and do not use any that would have it until the kernel is ready
Nicely ask your kernel developer to merge kexec-hardboot patch.​
3. Uninstaller
MultiROM uninstaller: Unavailable due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.​
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Reboot the phone
Changelog
Code:
MultiROM v33x - TWRP 3.2.1 - 21/01/2018
=========================================
* Merged TWRP 3.2.1 updates into MultiROM TWRP
* Improvements for Android 8.1 support
* Improvements [URL="https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/"]made with nkk71, RIP[/URL] >> [URL=https://www.xda-developers.com/rest-in-peace-xda-recognized-developer-nkk71-has-passed-away/#comment-3719128510]Comment[/URL]
MultiROM v33x - TWRP 3.1.1 - 01/11/2017
=========================================
* Improvements for Android 8.0 support
* Improvements for SDCardFS support
* Improvements from secondary ROMs handling
* Changes on the boot UI's Android ROM icons
MultiROM v33x - TWRP 3.1.1 - 07/06/2017
=========================================
* New implementation to handle external boot
on Ext4 / F2FS MicroSD or USB Drive in order
to allow access to the external storage for media,
through the storage 'external_multirom' path
MultiROM v33x - TWRP 3.1.1 - 17/05/2017
=========================================
* Include all recent improvements from TWRP 3.1.1
MultiROM v33x - TWRP 3.1.0 - 03/05/2017
=========================================
* Upstream updates from recovery and sources
* Fix for the offline charger detection mode
MultiROM v33x - TWRP 3.1.0 - 12/03/2017
=========================================
* Include all recent improvements from TWRP 3.1.0
MultiROM v33x - TWRP 3.0.3 - 05/03/2017
=========================================
* Built in a clean new tree of Android 7.1.1 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Include all recent improvements from TWRP 3.0.3
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
MultiROM v33x - 18/12/2016
======================================
* Minor improvements of MultiROM
* Improved versioning with header showing build date
* libbootimg changes from my recent updates
MultiROM v33x - 17/10/2016
======================================
* Improve autobooting to external ROM (MicroSD / USB)
MultiROM v33x - 18/09/2016 - 24/09/2016
======================================
* Updated to no-kexec workaround v4 by nkk71
* Autoboot accessible for external / MicroSD
MultiROM v33x - 16/08/2016
======================================
* Add support for the new ramdisk structure with init.real
MultiROM v33x - 14/06/2016 - 15/07/2016
======================================
* Support for hardware keys (Volume +/- & Power)
MultiROM v33x - 06/06/2016
======================================
* Support for Stock SONY ROMs added
MultiROM v33x - 23/05/2016
======================================
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
MultiROM v33x - 11/05/2016
======================================
* Support for no-kexec workaround to boot ROMs
MultiROM v33x - 15/04/2016 - 09/05/2016
======================================
* Improved UI with unified Internal / External ROMs in one tab
MultiROM v33x - 03/04/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Kernel patchers :
Code:
23/04/2016 - 06/06/2016
==========================
* Updated to latest sources, standalone kernel without modules
* Deprecated, releases abandoned.
06/04/2016 - 15/04/2016
==========================
* Updated to latest CM-13.0 & CM-12.1 stable kernel status
03/04/2016
==========================
* Initial huashan release, unstable kernel for the moment
Recent ROMs tested so far :
Code:
LineageOS 14.1 : OK (Primary & Second)
AOSP 7.1 : OK (Primary & Second)
AOSP 7.0 : OK (Primary & Second)
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
CyanogenMod 14.1 : OK (Primary & Second)
AICP Marshmallow : OK (Primary & Second)
AOSP-CAF Marshmallow : OK (Primary & Second)
AOSP-OMS Marshmallow : OK (Primary & Second)
AOSP-RRO Marshmallow : OK (Primary & Second)
Sony 4.3 based ROMs : Normally OK (Primary & Second)
eXistenZ Ultra 4.0.0 : OK (Primary & Second)
Warning : If using old ROMs as secondary, primary ROM
should not have F2FS filesystems for Data and Cache
Other ROMs : To confirm & report here

Reserved
FAQ and other notes
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.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.​
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./external SD card. 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.​
Can I have different versions of Android working alongside
Yes.​
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.​
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods.
Best solution is to remove the root zip from the ROM and flash it separately later.​
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.​
Current local manifest of the MultiROM build
Code:
<!-- https://github.com/AdrianDC/multirom_development_sony -->

And no, this is not an april fools joke.

Clicking on that link for patched kernel, opens a google search page which shows links for AK kernel, is that what we're supposed to use??
STUPID QUESTION. NEVERMIND.

Whaaat ?
What the F#?+ !
Thank you thank you thank you.
Thats all i say !

WTF?! OMG! Thank you so much adrian!

Adrian >> Harry Potter
Sent from my Xperia SP using XDA-Developers mobile app

For People Using this MOD:-
Follow the Instructions carefully and try reporting which ROMs work with it. This would reduce Adrian's effort to list bootable ROMs. Hope almost all of the ROMs boot.
Congrats @Adrian DC :laugh: :highfive:

Thanks to AdrianDc
I've installed the cm-13.0-20160329 beside my AICP 10 (Lollipop).

Great! Please try to fix for .207
P.S. Remains only wait DT2W from you

-Mr.freeze- said:
Great! Please try to fix for .207
P.S. Remains only wait DT2W from you
Click to expand...
Click to collapse
Dont rush him or he'll personally send a assaniation pigeon from the other side of the world to your home

Primary: CM12.1 unofficial works great
CM13 Works great too
CM11 bugyusz didn't boot (because it use stock kernel)
AICP Works great
Sent from my Xperia SP

Furrydaus said:
Dont rush him
Click to expand...
Click to collapse
I'm not hurry him. This can be called wishes)

I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)

desalt said:
I installed cm13 and then wanted to flash AICP10 by twrp 3.0.1 r6, but encountered these errors (see the attached pix please)
Click to expand...
Click to collapse
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk

darjwx said:
The rom is successfully installed. Nothing to worry about. I had also some days ago that error but the roms booted without a problem.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
tanx, but the Multirom menu doesn't appear and I have no choice to select AICP, moreover in the recovery there isn't any secondary ROM.

would you please see the following attached pix? do you see anything wrong?
the first one, says something (in mount menu) after failure in flashing the second rom.
and from the 2nd one, I guess my SD card is locked.
.

desalt said:
would you please see the following attached pix? do you see anything wrong?
Click to expand...
Click to collapse
First : Accept & set it to never ask again, it's ok.
Second : No. All storage devices are "block" based, doesn't mean anything related to the MicroSD being locked.
About old ROMs : No yet support nor known to work one day,
I'll get back to it soon enough but nothing sure yet.
Finally about latest CM12.1 / CM13 Beta releases : The newest MultiROM kernel patcher
can freely be used to test both ROMs as it has been updated to the same state.

I installed the proper Gapps for both cm12 and cm 13 without any problem when they were single Roms on my phone. but when I try to install each of them beside the other one as a secondary Rom , face to an error and installation process fails.

[MOD][08/03/2016] MultiROM v33x for Xperia Z [ABANDONED]

{
"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. 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
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 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-yuga.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-yuga.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
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.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
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 Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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.
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)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)​
MultiROM available for Yuga also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC​
XDA:DevDB Information
MultiROM for Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned

Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-yuga.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-yuga.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Yuga due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.​
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Yuga release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)

FAQ and other notes
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.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
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./external SD card. 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.
Can I have different versions of Android working alongside?
Yes.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
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.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.​

awesome work bro! Can't wait to test. Ill report you very soon! :good:

Nice to see someone taking over. I'll close my thread.
Sent from my Sony Xperia Z3+ using XDA Labs

Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..

itsnie said:
Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..
Click to expand...
Click to collapse
Please read OP again. Especially about "no-kexec workaround".

i installed both zip file.but recovery hasnt multirom option in andvanced!!!

Thank you a lot, I'll try it later!

The basketbuild site isn't working,they are doing recovery,
Would you please upload the files to another server?
Sent from my C6603 using Tapatalk

Does anyone know if there is multirom development on the xperia z5 e6653? I got it working on and of, but there are more breakdowns than anything else. This results in having to frequently reinstall the original boot.img and restart from scratch. Any help is appreciated. Thx
Sent from my E6653 using XDA-Developers mobile app

i have installed in xperia z and flash cm13 in sd card.. on multirom i have seleceted CM13 but still booting in to primary
---------- Post added at 08:34 AM ---------- Previous post was at 07:44 AM ----------
multirom worked using ressurection remix and cm 14 thank u.....

I tried -
PureX Z Premium v3.0
X rom ( 5.1)
Xperia_Z_eXistenZ_Premium
ResurrectionRemix-N-v5.8.0
almost all stock based ,But non of them works and gives error during flashing..
Only
ResurrectionRemix-M-v5.7.4
Omni rom , are working fine ...
Any help how to use sony stock roms or others ?

Chippa_a said:
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
Click to expand...
Click to collapse
Did not help... the setting is unchecked by default.
Charging on a Wallcharger works, pluging the phone to the computer doesn't show anywhing.
Falshing the Recovery only still worked fine, but after flashing the MultiROM zip the phone doesn't budge when connected to the Computer.
Syslog attached.

The MultiROM menu is not under Advanced such as v32 rather the icon upper right - pic 1.
RR N 7.1.1 as second Rom failed, ERROR 7 @ RR M 6.0.1 - pic 2.
My oldest backup Omnirom 4.4.4 as sec Rom was successfully - pic 3.
#Edit: Additional compatible secondary ROMs::
-XOSP M [6.0.1] [Unofficial] [Release 6] 6.3 [Revision 3] [2016/08/03]
-AOSP M [6.0.1] [FINAL] [OMS/Substratum] [Updated 31-10-2016]

The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?

MichaBit said:
The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?
Click to expand...
Click to collapse
You need newer twrp recovery for newer roms

langeveld024 said:
You need newer twrp recovery for newer roms
Click to expand...
Click to collapse
There was und is always the newest One installed. :angel:

MichaBit said:
There was und is always the newest One installed. :angel:
Click to expand...
Click to collapse
Alright but error 7 ALWAYS means wrong recovery

langeveld024 said:
Alright but error 7 ALWAYS means wrong recovery
Click to expand...
Click to collapse
Oh, Im currently desiring LEOs 3.1.1, so I will give Nailyk a drink.

[MOD][08/03/2016] MultiROM v33x for Xperia ZR [ABANDONED]

{
"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. 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
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 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-dogo.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-dogo.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
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.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
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 Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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.
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)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)​
MultiROM available for Dogo also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC​
XDA:DevDB Information
MultiROM for Xperia ZR, Tool/Utility for the Sony Xperia ZR
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned

Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-dogo.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-dogo.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Dogo due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.​
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/show...26&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Dogo release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)

FAQ and other notes
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.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
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./external SD card. 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.
Can I have different versions of Android working alongside?
Yes.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
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.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.​

I installed it every thing is working but can't boot to the secondary rom when I choose it the phone just restarts the primary rom works without any problem I used CM 14.1 as secondary

did its work on xperia zr.? can i used on Locked Bootloader.?

Hey chippa.. can you release multi boot for this device compatible on lineage 14.1 and Lineage 15.