[MOD] MultiROM v33x [20/05/2016] - Xperia Z4/Z3+ Original Android Development

[MOD] MultiROM v33x [20/05/2016] - Xperia Z4/Z3+ Original Android Development

Reserved
DOWNLOADs
MultiROM
Kernel with kexec-hardboot:
- For use with the 32.1.A.1.185 only
- Works on both variants (Single SIM + Dual SIM)
- MultiROM TWRP is already built-in

Reserved

Gonna test it today and will provide a feedback. Thx for work ?

Ok, so can't root it - Systemless method with patching doesn't work anymore. Also can't flash any zip to main ROM - neither by main menu (flashing, but where - no idea), nor by ROM list (main ROM is hidden and cannot make it visible via settings, resets every time to hidden status).

MotexT said:
Ok, so can't root it - Systemless method with patching doesn't work anymore. Also can't flash any zip to main ROM - neither by main menu (flashing, but where - no idea), nor by ROM list (main ROM is hidden and cannot make it visible via settings, resets every time to hidden status).
Click to expand...
Click to collapse
You need to use my kernel; it can be found in the second post.
EDIT: I can reproduce your problem and will check it once I get home (~ 1-2 days).

Olivier said:
You need to use my kernel; it can be found in the second post.
EDIT: I can reproduce your problem and will check it once I get home (~ 1-2 days).
Click to expand...
Click to collapse
Actually I'm using your kernel. Systemless Root in recovery says like it's already patched and terminal returns "abort operation". Looks like you already patched it by Systemless SU, so I can't repatch it again. If you did so, revert this change. By other side, MultiROM along with TWRP works good, except zip flashing from main TWRP menu - it flashes, everything seems to be good, but actually changes did not appear to be applied on main ROM, even when I inject everything, like described in guide (tried both Systemless SU and DRM fix - neither works :/). Also there is bug with main ROM - can't uncheck "Hide internal ROM", so main ROM couldn't be shown in ROM list. If any ideas - I'm up for testing.

MotexT said:
Actually I'm using your kernel. Systemless Root in recovery says like it's already patched and terminal returns "abort operation". Looks like you already patched it by Systemless SU, so I can't repatch it again. If you did so, revert this change.
Click to expand...
Click to collapse
Alright - systemless root doesn't work because my kernel uses a combined ramdisk, meaning the actual ramdisk of the ROM is in /sbin/ramdisk.cpio. SuperSU doesn't know that, tries to treat the main ramdisk as a normal one and fails (hence the abort). I'll try to find a solution...

I remember using this on the original XZ! So great it's being worked on. Will do some testing tomorrow. Thanks a ton, dev.

Olivier said:
Alright - systemless root doesn't work because my kernel uses a combined ramdisk, meaning the actual ramdisk of the ROM is in /sbin/ramdisk.cpio. SuperSU doesn't know that, tries to treat the main ramdisk as a normal one and fails (hence the abort). I'll try to find a solution...
Click to expand...
Click to collapse
We need either edit Systemless SU zip to patch proper boot image or make regular SU zip working (aka system mode) - for now, with .185 kernel it gives bootloops due to SELinux changes

but the z3+/z4 dont have any rom and dont have any romer ╮(︶︿︶)╭

windowgame98 said:
but the z3+/z4 dont have any rom and dont have any romer ╮(︶︿︶)╭
Click to expand...
Click to collapse
Make one.

MotexT said:
We need either edit Systemless SU zip to patch proper boot image or make regular SU zip working (aka system mode) - for now, with .185 kernel it gives bootloops due to SELinux changes
Click to expand...
Click to collapse
Fixed, please re-downloaded the boot image (from the same link), I have updated it. You can now also use the MultiROM Manager to install MultiROM. It can download TWRP, MultiROM and my kernel.

Useless till we dont have at least 2 roms... BUT HEY Thx for making it for the future maybe?
Sent from my E6553 using XDA-Developers mobile app

KOALAaufPILLEN said:
Useless till we dont have at least 2 roms... BUT HEY Thx for making it for the future maybe?
Sent from my E6553 using XDA-Developers mobile app
Click to expand...
Click to collapse
We have some unstable CM builds for now.

So, tested it for a while. Bugs: second ROM doesn't booting properly - just rebooting to black screen, then red LED blinks 3 times and reboots to that state again and then just after second reboot boots to multirom ROM menu.

@MotexT, yes, for me same behavior. Even stock kernel sometimes reboot device on bootanimation.

MotexT said:
So, tested it for a while. Bugs: second ROM doesn't booting properly - just rebooting to black screen, then red LED blinks 3 times and reboots to that state again and then just after second reboot boots to multirom ROM menu.
Click to expand...
Click to collapse
Quarx said:
@MotexT, yes, for me same behavior. Even stock kernel sometimes reboot device on bootanimation.
Click to expand...
Click to collapse
Try now; use the MultiROM Manager to upgrade.

ia this compatible with .253 stock and CM build by Quarx?

I've just ordered a 16GB microSD to test this
You said you haven't tested it with stock ROM well that's precisely what I plan on doing... I'm running CM13 and after a couple of days of research there doesn't seem to be any solution in sight for the camera bugs. However after seeing your thread, I figured if all goes well I could be running CM13 daily and just reboot to the stock ROM when I need to shoot a video (necessary for my professional activity... I'd rather do this than always have my old phone with me).
I'll keep you updated once I get the microSD.
Edit: looks like your server is offline, I can't download your APK... I'll try to download it again tomorrow.

Related

[MOD] [unofficial] Multirom V28 (GPE/STOCK - testing)

{
"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
I was able to get multirom working on Motorola Moto G and would like to share with you guys. Moto G (falcon) is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android ) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install Parandroid (currently it only supports single sim). It might work on the default firmware.
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. 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.
There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- Sometimes Wifi not able to get IP address (static config works) on secondary rom. (same issue is observed on primary rom - fixed after flashing latest kernel)
- Sometimes secondary rom boot failure. Need reboot.
- Touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection. (Fixed)
- On GPE sometimes when booting I see "exec '/system/bin/sh' failed: Permission denied" errors. reinstalling the rom in multirom fixes this issue. Need to check.
You can get the relavent files at following location
http://d-h.st/users/montamer
Multirom Files
TWRP with Mutirom changes
multirom-20140902-v28-UNOFFICIAL-falcon.zip
multirom_uninstaller.zip
Patched Kernels
Stock Kernel (only for Stock firmware not GPE)
Modiefied 3.4.103-XPerience-STK-14-gpemod for GPE stock firmware (original kernel from TeamMEX)
PA Kernel
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible.
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
Not supported at the moment.
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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
Note 2: There have been reports that (not only) MultiROM does not work properly with older bootloaders.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP with Mutirom changes) - download the IMG file from Multirom Files section and use fastboot or Flashify app to flash it.
- Fastboot command "fastboot flash recovery recovery.img"
Patched kernel - You can use either one of the stock ones in Kernel section or third-party kernels which include the patch. Download the ZIP file and flash it in recovery. or flash the img from fastboot.
- Flash the "Stock Kernel (only for Stock firmware not GPE)" if your using STOCK 4.4.4 firmware images using below fastboot command
fastboot flash boot stock_boot_patched.img
- Flash the 3.4.103-XPerience-STK-14-gpemod from recovery if you are using GPE 4.4.4 firmware.
MultiROM (multirom-XXXXXXXX-v28-UNOFFICIAL-falcon.zip) - download the ZIP file from Multirom Files section and flash it in recovery.
Note: make sure to disable screen timeout in recovery (multirom_patched_recovery.img) (not required in latest recovery build)
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
Original MultiROM - https://github.com/Tasssadar/multirom (branch master)
Falcon modified MultiROM - https://github.com/montamer/multirom
Falcon modified kexec-tools - https://github.com/montamer/kexec-tools.git
Falcon CM kernel with kexec-hardboot-patch - https://github.com/montamer/android_kernel_motorola_msm8226.git
kexec-hardboot-falcon.patch
Modified TWRP - https://github.com/montamer/Team-Win-Recovery-Project
XDA:DevDB Information
MultiROM, a Tool/Utility for the Moto G
Contributors
Tasssadar
Montamer
Thanks
h2o64 for the post template

willing to test I've got an xt1034. all I need is a link.
montamer said:
I was able to get multirom working on Moto-G and would like to share with you guys :highfive:. Moto-G is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android ) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install paranoidandroid (currently it only supports single sim). It might work on the default firmware.
There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- sometimes Wifi not able to get IP address (static config works) on secondary rom.
- sometimes secondary rom boot failure. Need reboot
- touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection
You can get the relavent files at following location
http : // d-h.st / users / montamer
mutirom files - falcon/multirom
patched kernels - falcon/hardboot_patched_kernel
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible.
INSTALLATION:
- Flash multirom_patched_recovery.img from fastboot.
- Flash stock_boot_patched.img from fastboot if you are on stock rom
or flash PA-falcon-kernel-signed.zip (build kernel from aospal, should work on other roms????) from recovery.
- reboot to recovery
- Flash multirom-20140819-v27-UNOFFICIAL-falcon.zip from recovery
WARNING
Port is not tested completely and might damage your device. Not for the faint hearted
I will not be responsible for any damage. Try at your own risk and make sure to backup
Credits:
Tasssadar (multirom aurthor).
paranoid android team.
Click to expand...
Click to collapse
I'll try it out.

Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG

DustArma said:
Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG
Click to expand...
Click to collapse
same question... multirom needs kexec support in the base rom. so this is just mutirom system or does it flashes a kernel with kexec support?

Amazing! I'll try as soon as possible. Could you share with us your device tree and your kernel sources? [emoji4]

@TeamMex perhaps something interesting for u man!
OP any instructions on how to use it?

Has you patched memory allocator's and kexec the kernel? Port Multirom is easy xD I have the sourse moded on my github but kexec isn't easy so tell me about your kernel patch
Sent from my XT1032 using XDA Premium 4 mobile app

abhifx said:
same question... multirom needs kexec support in the base rom. so this is just mutirom system or does it flashes a kernel with kexec support?
Click to expand...
Click to collapse
DustArma said:
Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG
Click to expand...
Click to collapse
The stock_boot_patched.img and PA-falcon-kernel-signed.zip are patched to support kexec. You need to flash one of the kernels based on your primary rom, before flashing multirom.zip.
I think new version of multirom doesn't mess with the eMMC partitioning and I have not tried flashing secondary rom on USB OTG.

TeamMex said:
Has you patched memory allocator's and kexec the kernel? Port Multirom is easy xD I have the sourse moded on my github but kexec isn't easy so tell me about your kernel patch
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the kernels shared are patched with modified kexec_hardboot.patch from Tasssadar . I will share the changes soon.

yeshwanthvshenoy said:
@TeamMex perhaps something interesting for u man!
OP any instructions on how to use it?
Click to expand...
Click to collapse
Instruction should be similar to any other multirom flashing. check the original post from Tasssadar for more clear instructions.
http://forum.xda-developers.com/showthread.php?t=2011403

montamer said:
Yes the kernels shared are patched with modified kexec_hardboot.patch from Tasssadar . I will share the changes soon.
Click to expand...
Click to collapse
Interesting, I will be tuned to implement patch in my kernel.
cheers.

TeamMex said:
Interesting, I will be tuned to implement patch in my kernel.
cheers.
Click to expand...
Click to collapse
Awesome.
I'm just curious : how many time do you take to do this @montamer ?
That incredible
Are you a C // C++ developper ?
PS : Please make a clear and readable topic If you don't want I can propose you a design x')

?
Bugs? Dual sim XT1033?

montamer said:
The stock_boot_patched.img and PA-falcon-kernel-signed.zip are patched to support kexec. You need to flash one of the kernels based on your primary rom, before flashing multirom.zip.
I think new version of multirom doesn't mess with the eMMC partitioning and I have not tried flashing secondary rom on USB OTG.
Click to expand...
Click to collapse
fantastic... need to try this. after glorious mutiboot on nexus 4, i now have mutiboot on moto.
now where is the ubuntu build i want to test

montamer said:
Instruction should be similar to any other multirom flashing. check the original post from Tasssadar for more clear instructions.
http://forum.xda-developers.com/showthread.php?t=2011403
Click to expand...
Click to collapse
i do understand the instructions but adding them to ur OP would help first timers. we got people who dont have much experience with advanced stuffs like this man so was just suggesting!

Thank you very much! I'll wait for you to release the changes before implementing it on other kernels.
BTW the PA kernel does not work on LiquidSmooth - it boots but have no wifi/networking, just to say

It made you a little prettier topic :
Code:
[CENTER][IMG]http://i.imgur.com/vh3puLb.png[/IMG][/CENTER]
[b][U][size=5]Introduction[/size][/U][/b]
I was able to get multirom working on [B]Motorola Moto G[/B] and would like to share with you guys. Moto G (falcon) is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android :p) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install Parandroid (currently it only supports single sim). It might work on the default firmware.
[INDENT]MultiROM is one-of-a-kind multi-boot mod for Nexus 7. 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
[url=https://www.youtube.com/watch?v=JDnDNxqfSaw]You can also watch a video which shows it in action.[/url][/INDENT]
[INDENT] There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- Sometimes Wifi not able to get IP address (static config works) on secondary rom.
- Sometimes secondary rom boot failure. Need reboot.
- Touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection.
You can get the relavent files at following location
[URL="http://d-h.st/users/montamer"]http://d-h.st/users/montamer[/URL]
mutirom files - [B]falcon/multirom[/B]
patched kernels - [B]falcon/hardboot_patched_kernel[/B]
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible. [/INDENT]
[b][U][size=5][color=Red]Warning![/color][/size][/U][/b]
[INDENT]It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. [strike]It is messing with boot sector and data partition.[/strike] 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.[/INDENT]
[b][U][size=5]Installation[/size][/U][/b]
[INDENT][B]1. Via MultiROM Manager app[/b]
This is the easiest way to install everything MultiROM needs. [url=https://play.google.com/store/apps/details?id=com.tassadar.multirommgr]Install the app[/url] and select MultiROM and recovery on the [i]Install/Update[/i] card. If the [i]Status[/i] card says [i][b]Kernel:[/b] [color=red]doesn't have kexec-hardboot patch![/color][/i] in red letters, you have to install also patched kernel - either select one on the [i]Install/Update[/i] card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, [b]not[/b] any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the [i]Install/Update[/i] card to start the installation.
[/INDENT]
[INDENT][b]2. Manual installation[/b]
Note: [COLOR="Red"]make sure to disable screen timeout in recovery[/COLOR]
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.
[b]Note 1:[/b] Your device must [b]not[/b] be encrypted (hint: if you don't know what it is, then it is not encrypted).
[b]Note 2:[/b] There have been reports that (not only) MultiROM does not work properly with older bootloaders.
MultiROM has 3 parts you need to install:
[LIST]
[*][b]MultiROM[/b] (multirom-XXXXXXXX-v27-UNOFFICIAL-falcon.zip) - download the ZIP file from second post and flash it in recovery.
[*][b]Modified recovery[/b] (multirom_patched_recovery.img) - download the IMG file from second post and use fastboot or [url=https://play.google.com/store/apps/details?id=com.cgollner.flashify]Flashify app[/url] to flash it.
[*][b]Patched kernel[/b] - 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.
[/LIST]
[b]You current rom will not be erased by the installation.
Download links are in the second post.[/b][/INDENT]
[b][u][size=5]Adding ROMs[/size][/u][/b]
[INDENT][b]1. Android[/b]
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.[/INDENT]
[INDENT][b]2. Ubuntu Touch[/b]
Use the [url=https://play.google.com/store/apps/details?id=com.tassadar.multirommgr]MultiROM Manager app[/url] to install Ubuntu Touch.
[b]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.[/b][/INDENT]
[U][size=5][b]Using USB drive[/b][/size][/U]
[INDENT]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.[/INDENT]
[U][size=5][b]Updating/changing ROMs[/b][/size][/U]
[INDENT][B]1. Primary ROM (Internal)[/B]
[LIST]
[*] 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 [I]Inject curr. boot sector.[/I]
[/LIST][/INDENT]
[INDENT][B]2. Secondary Android ROMs[/B]
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
[LIST]
[*] 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.
[/LIST][/INDENT]
[u][size=5][b]Explanation of recovery menus[/b][/size][/u]
[INDENT][b][color=Blue]Main menu[/color][/b]
[b]- Add ROM[/b] - add ROM to boot
[b]- List ROMs[/b] - list installed ROMs and manage them
[b]- Inject boot.img file[/b] - 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.
[b]- Inject curr. boot sector[/b] - Use this option if MultiROM does not show up on boot, for example after kernel installation.
[b]- Settings[/b] - well, settings.
[b][color=Blue]Manage ROM[/color][/b]
[b]- Rename, delete[/b] - I believe these are obvious
[b]- Flash ZIP[/b] (only Android ROMs) - flash ZIP to the ROM, for example gapps
[b]- Add/replace boot.img[/b] - replaces boot.img used by this ROM, this is more like developer option.
[b]- Re-patch init[/b] - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.[/INDENT]
[u][size=5][b]Source code[/b][/size][/u]
[INDENT]MultiROM - [URL]https://github.com/Tasssadar/multirom[/URL] [b](branch master)[/b]
Modified TWRP - not available yet[/b]
Stock kernel w/ kexec-hardboot patch - not available yet
CM kernel w/ kexec-hardboot patch - not available yet
[B][U][SIZE="4"][PLAIN]XDA:DevDB Information[/PLAIN][/SIZE][/U][/B]
[SIZE=3][B]MultiROM, a Tool/Utility for the Moto G[/B][/SIZE]
[B][U]Contributors[/U][/B]
[URL="http://forum.xda-developers.com/member.php?u=1248420"]Montamer[/URL]

thanks man!

tried with GPE(partially) converted 1033XT
unable to install multirom-20140819-v27-unofficial-falcon.zip
base rom PA 4.5-Beta1
any one facing the same issue

Only for falcon stock firmwares. Doesn't work on falcon GPE.

[MOD][FEB 01] MultiROM v30x

Downloads
1. Main downloads
MultiROM: MultiROM-v30x-170115-UNOFFICIAL-amami.zip
Modified recovery (based on TWRP): TWRP_multirom-amami_20150201-00.img
MultiROM Manager Android app: Google Play or link to APK
Kernel w/ kexec-hardboot patch (Stock 4.4.4 - .157): stock-kexec-boot.img
Kernel w/ kexec-hardboot patch (Stock Lollipop): http://forum.xda-developers.com/showpost.php?p=61802911&postcount=119
Kernel w/ kexec-hardboot patch (CyanogenMod 12): kernel.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!
2. third-party kernels with kexec-hardboot patch
* Validus LP kernel
* Resurrection Remix LP kernel
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:
MultiROM v30x
=====================
* Initial release
Recoveries:
Code:
01/02/2015
==========
* Disabled screen timeout.
* Added filesystems tools.
* Latest TWRP updates and changes.
21/01/2015
==========
* Fixed the installation of block images OTAs through MultiROM.
* Latest TWRP updates and changes.
17/01/2015
=====================
* Initial amami release

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.
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.

Finally, I've been waiting for this for a long time :victory:
Thanks for bringing this great mode to our device, gonna try it soon.
Regards,
Omar.

MultiROM Manager Android app
MultiROM Manager Android app is showing : this is unsupported device (amami) even with the latest version

LIONS1 said:
MultiROM Manager Android app is showing : this is unsupported device (amami) even with the latest version
Click to expand...
Click to collapse
The pull request in the source of the app for adding support for Z1 Compact is opened, just wait a few days until it is merged and the app updated
Sent from my D5503 using XDA Free mobile app

I am using stock as primary rom
And resurrection remix as secondary and i am getting error trying to boot resurrection remix rom,
I attached log.
Thanks

Rempty said:
I am using stock as primary rom
And resurrection remix as secondary and i am getting error trying to boot resurrection remix rom,
I attached log.
Thanks
Click to expand...
Click to collapse
Resurrection Remix on LP uses block images, so that's why it throws that error, but I have already talked with Omar and I think he will disable them for next release, fixing this issue

I'm using official CM12 nightly as primary rom and I tried to install CM11 ROM as secondary, but it failed (kexec-hardboot failure). And I have flashed the stock-kexec-boot.img from fastboot, but it caused bootloop. I think it is the .dat files problem. Although if I will flash the Validus ROM I wouldn't have working camera, because camera fix by xkonni will be overwrited by kexec kernel.

Once again congrats, and nice thread btw

Casserole said:
I'm using official CM12 nightly as primary rom and I tried to install CM11 ROM as secondary, but it failed (kexec-hardboot failure). And I have flashed the stock-kexec-boot.img from fastboot, but it caused bootloop. I think it is the .dat files problem. Although if I will flash the Validus ROM I wouldn't have working camera, because camera fix by xkonni will be overwrited by kexec kernel.
Click to expand...
Click to collapse
Wait for a custom kernel for CM12 (maybe Omar's GreatDevs kernel) with kexec support in Lollipop, as I don't think that CM12 will add kexec support by default due to its security issues, BTW .dat is just a problem for secondary ROMs not for host ROMs
Also stock-kexec-boot.img is just for stock ROMs (by Sony), flashing it in another ROM will cause a bootloop

I am not sure if I understand it correctly. But is it possible to use this on stock rom as primary and CM12 as secondary?

amnher said:
I am not sure if I understand it correctly. But is it possible to use this on stock rom as primary and CM12 as secondary?
Click to expand...
Click to collapse
Well, CM12 as secondary not yet, but yes other LP ROMs which doesn't have .dat files in the zip, like Validus
Sent from my D5503 using XDA Free mobile app

I am using the new Resurrection Remix build (without block image OTAs) as secondary and now work flawesly
Question
To install a rom to ext sdcard, need to create a ext4 partition?

Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
UPD:
Fix zip archive, zipping on Linux and it was gzip archive, sorry.

Rempty said:
I am using the new Resurrection Remix build (without block image OTAs) as secondary and now work flawesly
Question
To install a rom to ext sdcard, need to create a ext4 partition?
Click to expand...
Click to collapse
No, they are created automatically
russel5 said:
Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
Click to expand...
Click to collapse
Thank you, I'll attach it at second post as soon as possible
Sent from my D5503 using XDA Free mobile app

russel5 said:
Compiled kexec patched kernel to CM12
Checked, internal ROM - cm12, second - cm11. All works fine
This boot.img with TWRP 2.8.4.0 and worked vol keys for entering when you are booting
Click to expand...
Click to collapse
your zip seems to be broken (cannot unzip). downloaded various times.

paulle said:
your zip seems to be broken (cannot unzip). downloaded various times.
Click to expand...
Click to collapse
fix, check

russel5 said:
fix, check
Click to expand...
Click to collapse
Added to Downloads in second post

russel5 said:
fix, check
Click to expand...
Click to collapse
yes, now I get it unzipped. Thank you..

[MOD][Z3C] MultiROM v33x

XDA:DevDB Information
MultiROM for Sony Xperia Z3 Compact, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom
Version Information
Status: Testing
Created 2015-05-22
Last Updated 2016-06-06

CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5-Kernel-L (starting with V2)
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.

Reserved
General Informations about Kexec are coming here soon.

I have encountered problems with secondary rom flashing. First try your test carbon rom boot loop, second try restore back up of stock rom failed, third try fresh install of a stock rom failed, fourth try pac rom with your m5 kernel flashing ok but will not start
my primary is cm12.1 with your kernel

me too.
primary rom is stock LP 23.1.A.1.28 with androplusV55
i succeeded installing second rom being CM12.1 nightly build
first without gaaps cm12.1, as per selecting the rom from the romlist in twrp and choosing flash zip
then tried deleting it and added the rom again, this time i flashed gapps as per selecting the rom from the romlist in twrp and choosing flash zip
is gapps required to load cm successfully at all?
When selecting cm12.1 at the multirom boot menu it reboots and only shows the internal (stock) rom and boots just fine.
then i was thinking about doing the swap rom from twrp or perhaps flashing cm12.1 as primary and having stock as secondary.
or perhaps flashing cm12.1 from scratch and then add stock sony as secondary via an old backup
but then i stumbled into this thread http://forum.xda-developers.com/showpost.php?p=60906102&postcount=129
i used multirom twrp which is inbuilt in andrplusV55, not the one from myself5's dl site!
-androplus is stock only supporting
-m5 kernel is only cm12 supporting
and i coulnd't find the way to choose de-select kernel for secondary rom as found somewhere else
what a dilemma

New Version is online!
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation

Important
Just one question
now say i flashed CM 12 as a second ROM
when i boot to it , will apps which i already installed on the stock appear their ??
in other words , does the each ROM affect the other one ?? like if i put something on internal storage will appear on the other ROM ??

Myself5 said:
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation
Click to expand...
Click to collapse
nice one, indeed.
but i still had the same issue, couldn't load cm og pac as secondary rom
i had androplusV55, now i've updated to androplusV57, and it's working like a charm.
apperently it was a kernel issue
ps. noticed that gapps are required so it doesn't share apps i think?
not in my case though, hence im running stock rom as primary
probably M5 kernel can be flashed as well, as long as it is flashed through mulitrom twrp from listed roms, like update tutorial for secondary rom in OP
thanks very much

Hey freaks,
I think there is something to explain.
The first Thing you have to do and this is one of the most important thing:
Donate to Myself5 or even "Thankyou"
Because you must know, this Multirom MOD is very sensitive like a young good looking girl and it can feel a donation...and works even better after a Thank you
Remeber we are here in Z3 "Compact" Area you can NOT choose a Main Kernel for Z3 or other Xperia Models.
The Main Kernel must support kexec-hardboot (support for MultiROM), for Z3 Compact
The best way to get all to work is:
-Backup all you ROMs you have right now on your Device "Remeber Z3 "Compact"
-Save this to your SD Card
-clean your Phone
-Install CM12.1 latest Nighty
-boot one time and check if you have a Plain CM12.1 (LP 5.1.1) System. Now you have Cm12.1 and the Cyanogen Recovery on your Phone.
-Copy the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and "multirom-20150522-v31x-UNOFFICIAL-aries.zip.md5sum" to your SD Card
-Shutdown your Phone and boot on Bootloader Mode (Press and hold Volume Up Button and insert USB Cable) a Blue LED appear now.
-Go with a Terminal in Administrator Mode in your ADB Folder with fastboot. (Windows PC)
-Copy one of the M5 V6 Kernel in the fastboot directory and copy the File TWRP-Multirom-20150524-00-z3c.img in the same directory
-type "fastboot devices" now you see your device is connected
-Now type "fastboot flash boot boot.img" <-- Boot .img is the M5 V6 kernel, you find in the release Zip Files from Myself5
-Now type "fastboot flash recovery TWRP-Multirom-20150524-00-z3c.img"
-Now type "fastboot reboot"
-Your Phone boots now normally and you should press Volume Up or down to enter TWRP MultiRom Recovery...Allmost all is done now.
-In Recovery Mode go to the Normal "Install" Button and choose the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and flash this. Now reboot system.
Well done...Multiboot is installed.
Now you can go everytime you like in the recovery Mode and go to the Button Advanced -Multiboot and install other ROMs, like your Backups or CM12 builds.
All your Secondary Roms must be updated over the Advanced- Multiboot- List Roms feature. To update multiboot itself or the Main Cm12.1 Rom you have to flash over the Main install button.
If this is not working, delete Data and flash your Backup again and sell your Z3 Comapct and buy an IPhone. Apple take care of all your Data
Panic Brothers
-

@Myself5 some problems when restoring backup of stockrom with androplus kernel as secondary. file attached

edit :solved couldnt figure how to flash gapps , rooky mistake but figured it out ....u go to advanced tab in twrp/multirom/list rom/flash zip

First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]

Oh, totally forgot about the app. It's coming next ofc, just need to setup the z3c folder on my server.
Sent from my Xperia Z3 using Tapatalk

Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
AnGrY sCoTsMaN said:
First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]
Click to expand...
Click to collapse
Ey bro on candy5 do you have full connection when you connect your cel into pc?

chikrron said:
Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
Ey bro on candy5 do you have full connection when you connect your cel into pc?
Click to expand...
Click to collapse
you can have stock as primary with androplus kernel, I couldn't manage to have stock as secondary

Ok bro thanks for the tip I'll try later

Hi
So I installed your MultiROM together with the M5-Kernel and cyanogenmod. Afterwards I flashed the modified TWRP recovery. However TWRP has issues to mount my external sdcard (32 GB), its just shown as 0 MB and its not possible for me to re-partition or format it.
- It says "auto" as its file system
- Its formated as FAT32 (tried extFat too)
- This sdcard was taken over from my old i9300
Edit:
Seems I fixed it by booting into cyanogenmod and going under Settings/Storage and select "delete sdcard" down there. Strange.....
Anyways. Thanks for your work!

myself5.de is down
In Case someone noticed my server being down:
I am aware that my server is down, it got suspended by an Admin and I need to figure out why (I have not done anything forbidden, last thing I did was trying to setup an instance of Gerrit Code Review) that however is not that easy cause the server is sponsored and I only have access to the SolusVM Panel, I can't create Support tickets, so I now need to wait for my sponsor to answer me. Stupid as I am I don't have a mirror, cause I did not set up one yet... I hope someone can upload the latest Version and post a link here, would be greatly appreciated.
Regards
Myself5
EDIT: Server is meanwhile back. Thanks to everyone who provided a temporary link

Installing Roms on SD Card and External Memory
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards

Myself5 said:
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards
Click to expand...
Click to collapse
@Myself5 how about multirom app,can it work for aries?

[Addison]MultiROM v33 [No Kexec Workaround]

{
"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 MotoZ Play. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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, 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
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.ays.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app (wait until I compile it) 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 choosing 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-addison.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (MULTIROM-TWRP-3.1.1-Addison-unnoficial.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.[/INDENT]
Adding ROMs
1. Android
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.
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 distributed 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 - we'll, 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
Code:
[HIDE]
<remote name="multirom"
fetch="https://github.com/Tasssadar" />
<project name="multirom-dev/multirom" path="system/extras/multirom" remote="github" revision="master" />
<project name="multirom-dev/Team-Win-Recovery-Project" path="bootable/recovery" remote="github" revision="android-7.1-mrom" />
<project name="multirom-dev/libbootimg" path="system/extras/libbootimg" remote="github" revision="master" />
[/HIDE]
Kernel: https://github.com/Alberto97/android_kernel_motorola_msm8953/commits/twrp-7.1
Device: https://github.com/XPerience-AOSP-Lollipop/android_device_motorola_addison/tree/android-7.1-MROM
XDA:DevDB Information
[Addison]MultiROM v33 [No Kexec Workaround], Tool/Utility for the Moto Z Play
Contributors
TeamMex
Version Information
Status: Stable
Created 2017-05-20
Last Updated 2017-05-20

Reserved
Downloads:
TWRP_Multirom.img
multirom-20170520-v33-UNOFFICIAL-addison.zip
multirom_uninstaller.zip
MultiROMMGR Adapted for Addison

Reserved
FAQ and other notes
Device encryption
Encryption Fully working
SD CARD
Fully working
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 potentially 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.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*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.
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 satisfying to work on code for device I don't have - I invested 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

CREDITS:
 @nkk71 (For kexec workaround) 
 @Tasssadar for MultiROM 
 @Alberto97 For TWRP kernel and Encrypt fixes taked from his TWRP repo.
Screenshots

Try to test but, mod twrp stuck on initial logo ( flashed via , twrp , flashify and fastboot )
Download it three time.
Please you can upload to another host?
Thanks sorry for my bad English.
Inviato dal mio XT1635-02 utilizzando Tapatalk

lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen....
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption

Alx31 said:
lol nice job @TeamMex ! u got it fully working? i only have a touch issue on rom boot selector screen..
i've used mr-dev repos
ok it doesn't boot here neither (im unencrypted dunno if its related) ; couldn't grab a log, terminal throws me a "/sbin/sh: exec: line 1: logcat: not found"
here a booting 3.1.0 mr_twrp for those having issues https://www.androidfilehost.com/?fid=745425885120733531
but this one doesn't have encryption
Click to expand...
Click to collapse
For me it's working fine
Sent from my Moto Z Play using XDA Labs

TeamMex said:
For me it's working fine
Sent from my Moto Z Play using XDA Labs
Click to expand...
Click to collapse
I mean is a upload problem..try to change host
Inviato dal mio XT1635-02 utilizzando Tapatalk

I'm getting, "Failed to create system.img" error for both SD card and internal storage.

Great work!
Waiting for Android O for the device.?
Can you tell if development of Android O for the device(Z Play) is started or not?
Thanks!

VR25 said:
I'm getting, "Failed to create system.img" error for both SD card and internal storage.
Click to expand...
Click to collapse
Me as well

Mrawesome13 said:
Me as well
Click to expand...
Click to collapse
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.

TeamMex said:
Try to decrypt your device.
I forgot to add these info.
It work on encrypted but work better on decrypted devices.
.
Click to expand...
Click to collapse
I've decrypted my data, now recovery gets stuck at the splash screen. The standard TWRP works though. Tried MULTIROM TWRP 3 times -- Auto installation from the MultiROM app and manual from flashify & standard TWRP. I forgot to get a log. Will do it if I have time to try that again.

I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!

Hey, i did that. But it isnt working.. still same message

Anybody who can confirm that MultiROM v33 is working on moto z play under 7.1.1 stock rom with stock kernel?
Thanks!

wokawoka said:
I'm sorry but from the past messages I couldn't understand if this version of MultiROM works with an encrypted OS (as primary or secondary ROM) or not.
If I have understood correctly the original MultiROM from tassadar supports encryption on nexus devices since many years. Is the same valid for this version for the Moto Z play as well?
Could anyone maybe clarify that?
Thanks!
Click to expand...
Click to collapse
yes but him was reverted the encription support.
I will try to update multirom in some day's.

Thank you for your reply @TeamMex!
I'm actually using in this right moment your TWRP 3.1.1 multirom and these are my findings:
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
I'm running a rooted stock moto z play 7.1.1 rom as my primary rom and I've installed MultiROMMGR and reinstalled TWRP from there as well.
Do you by chance have any suggestion about these issues?
Any new version that corrects bugs is of course very welcome. Thank you very much again for your work!

wokawoka said:
Thank you for your reply @TeamMex!
- I don't know why but TWRP is no more asking me the decryption password at boot (at the beginning for the first boots it was regularly asking me the encryption PIN), but after having booted it can read and write the internal storage without the password.
That means that the password is cached somewhere. I personally find this behaviour very risky and it basically defeat the purpouse of having encrypted the phone (see also https://github.com/TeamWin/Team-Win-Recovery-Project/issues/202#issuecomment-342540553 )
- TWRP doesn't boot if my 64GB SDXC is inserted in the phone (formatted on the computer as exFAT or even forced to FAT32, formatted on the phone as external storage, no difference)
- it looks like I can't install any secondary rom. If I try to install a secondary rom on the internal storage I get an error when it tries to create the system.img file (E:Failed to create system.img), if I try to install the secondary rom on a small 16GB sd card it just fails while creating the cache.img file without outputting any error.
Click to expand...
Click to collapse
- Alright, so I was able to resolve the encryption password problem, as iit was my fault and not twrp multirom's: I just had to change again the security settings of the phone to enable the ask for pin code on boot.
- I circumvented the 64GB SDXC problem by using a 32GB SD card (still, it would be great to use a bigger sd card)
- Unfortunately, I'm still not able to use the multirom function: I'm running a moto z play stock 7.1.1 encrypted and rooted system, and as no alternative kernels exits for 7.1.1 at the moment. Is there a possibility in this conditions to get multirom working? I still receive the "E:Failed to create system.img" error when I try to install a secondary rom.
I'm not sure, but it feels like this moto z play multirom port is not actively mantained, which is a real pity because the phone is great and has all the characteristics to be the center of an active community of enthusiasts (in the same way some nexus or Samsung phones do) since it has quite unique features like good specs and an incredible battery life, the mod expandibility and an hardware qwerty keyboard that is going to be released very soon, and it also recently became very affordable.
Having a working multirom would help immensely and push the development of custom roms and alternative OSs (like for example sailfish https://talk.maemo.org/showthread.php?p=1538755#post1538755 ).
I would try to help or to take care of it myself but unfortunately I don't have the specific skills needed. I would be eventually up to give my contribution with some money (actually I'm thinking about creating a bountysource for it).
Is there by chance someone else that could bring on the port and release a stable working version?
If not, do you guys think that the it would be possible to adapt the twrp multirom released for the Moto Z (non-play version): https://forum.xda-developers.com/moto-z/development/mod-multirom-v33b-moto-z-t3513868 ? I can imagine that they have to be very similar.
Thanks again

any update on this?

[MOD][May 08, 2018] MultiROM v33a - TWRP 3.2.1-0 [No Kexec Workaround]

{
"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"
}
You use this tool at your own risk!!
I have tried to put as many safeguards as I can,
but I cannot be held accountable for any soft-bricks, hard-bricks, loss of data and/or information,
or anything else going wrong.
Introduction
MultiROM is one-of-a-kind multi-boot mod for Samsung Galaxy S4 (i9500). 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
Click to expand...
Click to collapse
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 (actually the no-kexec workaround is messing with your boot sector), but it is possible that something goes wrong and you will have to flash factory images again.
Make backups. Always.
Click to expand...
Click to collapse
Installation
Manual installation
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 2 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-i9500.zip) - download the ZIP file from the download section and flash it in recovery.
Modified recovery (TWRP_multirom_i9500xxx_YYYYMMDD.img) - download the IMG file from the download section and flash it in recovery.
Your current rom will not be erased by the installation.
Click to expand...
Click to collapse
Downloads
multirom-i9500
Click to expand...
Click to collapse
Adding ROMs
1. Android
Go to recovery, enter the MultiROM section of TWRP (by clicking the icon in to top right corner) -> 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.
Click to expand...
Click to collapse
2. Ubuntu Touch this is NOT SUPPORTED
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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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 the MultiROM section of TWRP (by clicking the icon in to top right corner) 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 the MultiROM section of TWRP (by clicking the icon in to top right corner) -> 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 corresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
Source code
MultiROM - https://github.com/multirom-klte/multirom
Modified TWRP - https://github.com/multirom-klte/android_bootable_recovery
Device tree - android_device_samsung_i9500
Click to expand...
Click to collapse
Thanks
MultiROM team
TWRP team
@nkk71 for No Kexec Workaround
@Alberto96 for TWRP device tree
Click to expand...
Click to collapse

FAQ and other notes
No-kexec workaround
Q: What is the no-kexec workaround?
A: The no-kexec workaround by nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
More info here
Click to expand...
Click to collapse
Q: MultiROM bootmenu never show up?
A: Go to recovery, enter the MultiROM section of TWRP (by clicking the icon in to top right corner) -> Inject boot sector.
Click to expand...
Click to collapse
Q: Secondary ROM reboot to recovery?
A: Enter recovery > MultiROM menu > List ROMs > Select your ROM and Run Restorecon.
Click to expand...
Click to collapse

Changelog
Code:
MultiROM-20180508-v33a - TWRP 3.2.1-0
======================================
* initial build for i9500
* multirom: inject: Add lzma support (Needed for AOSP ROM's)
* multirom: uninstaller: Add lzma support

Nice job ! I have install latest RR 5.8.5 rom as primary and secondary rom will be latest LS 14.1 for I9500, work as flawless. laugh:

Hi,
Having problem when need to flash supersu or magisk in secondary rom, nothing happen once done flashing. Secondary rom still remain unroot.
Any solution ?

eddylkwst62 said:
Hi,
Having problem when need to flash supersu or magisk in secondary rom, nothing happen once done flashing. Secondary rom still remain unroot.
Any solution ?
Click to expand...
Click to collapse
Not supported at the moment, maybe in future.

afaneh92 said:
Not supported at the moment, maybe in future.
Click to expand...
Click to collapse
Ok !

Database Info

welcome