Related
{
"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 Motorola Moto G. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1.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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-falcon.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_falcon_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch - Not available yet on Moto G
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.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS - Not available on Moto G yet
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
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.
Changelog
Code:
MultiROM v33
=====================
* Updates for Android 7.1 compatibility
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
MultiROM v27a
=====================
* Fix freezes in the boot manager
* Add support for SailfishOS
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scriptshttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
MultiROM v25
=====================
* Add support for the Android L preview
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22c
=====================
* Fix graphics corruption with some custom kernels
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
[url]http://bit.ly/ut_sharing[/url] for more info.
MultiROM v22a
=====================http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
MultiROM v22
=====================
* Fix Ubuntu Touch boot taking long time
* Fix Ubuntu Touch freezing on Google logo for some usershttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
MultiROM v21a
=====================
* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
MultiROM v21http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Initial version
http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
Recoveries:
Code:
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMshttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5http://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Removehttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.imghttp://android.comtek-wiebe.de/MultiROM/falcon/multirom-TWRP-v287_20150805.img
boot.img" on the List ROMs -> *rom name* page.
12.8.2014 - 1
=====================
* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
version
11.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
27.2.2014
=====================
* Support for system-image based (from the Manager app) Ubuntu Touch
installation
* Fix time in recovery
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
4.2.2014
=====================
* Update to support latest Ubuntu Touch testing builds
* Fix date and time in recovery
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
26.1.2014
=====================
* Fix radio in Ubuntu Touch
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
Credits :
@Picohackrhackr for the recovery
@tassadar for the entire multirom
@h2o64 for the OP
MultiROM Manager:
Google PlayStore Link
MultiROM:
MultiROM
MultiROM TWRP:
MultiROM TWRP
KERNEL:
Misc Kernel
MISC:
Bootlogo, Uninstaller
BUGS:
No WIFI on primary stock rom (with SuperSU only)
# su
# mount -o rw,remount /system
# mkdir /system/su.d
# echo wcnss_service > /system/su.d/wcnss
# chmod 755 /system/su.d/wcnss
# mount -o ro,remount /system
XDA:DevDB Information
MultiROM, Tool/Utility for the Moto G
Contributors
Brawn_Sg, sub77
Source Code: https://github.com/sub77
Version Information
Status: Beta
Created 2015-02-28
Last Updated 2016-12-28
Reserved
Reserved
...
First will try this
Which version of multi ROM twrp is given in op
2.8.2 btw someone got it working
Brawn_Sg said:
2.8.2 btw someone got it working
Click to expand...
Click to collapse
Who got it working?
I've always been curious. Won't this take up a lot of space on the phone because of the roms?
someone just try this nd let us know
@FalconG
Snowers96 said:
Who got it working?
Click to expand...
Click to collapse
someone got it working ?
Snowers96 said:
Who got it working?
Click to expand...
Click to collapse
he mean has anyone tested it and got it working
Brawn_Sg said:
someone got it working ?
Click to expand...
Click to collapse
The recovery throws errors like
E: Failed to open theme zip
E: resources failed font
I don't know what does it mean.
Tried installing multirom on 4.4.4 and after the logo screen stays black for 3-4 times more than required boot time.
Still didn't see os boot and used power button to restart the phone.
Tried it on validus lollipop with donkey kernel but the same results.
It ain't working yet.
antarix said:
The recovery throws errors like
E: Failed to open theme zip
E: resources failed font
I don't know what does it mean.
Tried installing multirom on 4.4.4 and after the logo screen stays black for 3-4 times more than required boot time.
Still didn't see os boot and used power button to restart the phone.
Tried it on validus lollipop with donkey kernel but the same results.
It ain't working yet.
Click to expand...
Click to collapse
actually on 5.0 bootloader screen goes black and when multirom comes and we try to boot 2nd rom then it bootloops....i made this thread so that someone can help us in this
Note :E: resources failed font (fixed)
now looking in to E: Failed to open theme zip
Brawn_Sg said:
actually on 5.0 bootloader screen goes black and when multirom comes and we try to boot 2nd rom then it bootloops....i made this thread so that someone can help us in this
Click to expand...
Click to collapse
I'm on xt1033 converted to gpe 4.4.4 boot loader. I didn't update it yet to 5.0.1 gpe.
if someone can get us logs or last kmsg then that would be very thankful
Font Fixed: recovery link:https://www.androidfilehost.com/?fid=95887005526789196
Note: about theme error never mind it you are good to go , will fix it soon as possible
Brawn_Sg said:
if someone can get us logs or last kmsg then that would be very thankful
Click to expand...
Click to collapse
How to take a log or last kmsg if I can't boot into system?
I'll help here. If it is possible via phone.
Thanx if u will help
http://forum.xda-developers.com/showthread.php?t=1520508
plz read this tutorial and provide us some logs
both recovery and multirom updated ........plz test it and tell us if some progress is there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1 Compact. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-vXX-DDMMYY-amami.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom-amami.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either the stock one in second post or third-party kernels which include the patch, you can see list in the second post. Download the IMG file and flash it via fastboot.
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 a ROM after first boot (with dalvik cache generated and connected to google account) takes more or less 700MB 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 (if USB drive partitions are not showed, disconnect USB drive and try again). 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 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.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kexec-hardboot patch for stock Sony kernel- https://github.com/Garcia98/kernel-amami/commit/4185df7caf40ac5aa6c7fc81d4098de58f9af19f
Touch patch for MultiROM menu- https://github.com/CyanogenMod/andr...mmit/907103b43eed80bd2bef89beb957d4052311ae67
XDA:DevDB Information
MultiROM for Xperia Z1 Compact, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
Garcia98
Version Information
Status: No Longer Updated
Created 2015-01-17
Last Updated 2016-06-10
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..
{
"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 Motorola Moto G. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1.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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-falcon.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_falcon_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch - Not available yet on Moto G
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.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android
4. SailfishOS - Not available on Moto G yet
Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
Put both CM and SailfishZIP on your device.
Reboot into recovery
Advanced -> MultiROM -> Add ROM
Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
Head to SailfishOS thread for more info: http://forum.xda-developers.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266
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.
Changelog
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
the L icon)
MultiROM v30
=====================
* Fix logs generated by the "emergency reboot" screen, they were incomplete
MultiROM v29
=====================
* Implement "autoboot if no key pressed" mode - the boot manager won't show up
unless you hold down a volume down button during boot. Must be enabled in
recovery.
* Android 5.0 preview related tweaks
MultiROM v28
=====================
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
MultiROM v27a
=====================
* Fix freezes in the boot manager
* Add support for SailfishOS
MultiROM v27
=====================
* Redesign the boot manager GUI. Looks much better now.
* Fix separate radio.img not working on Android L preview ROMs
* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
restorecon manually on /data/media, ever - it breaks MultiROM!
* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
boot
* Update Ubuntu Touch init scripts
* Use power+volume down (you have to press power first!) to save screenshots.
They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
MultiROM v26
=====================
* Fix boot into secondary ROM from the MultiROM Manager app broken in v25
MultiROM v25
=====================
* Add support for the Android L preview
MultiROM v24
=====================
* Add F2FS support
* Show icons in ROM list, configurable via MultiROM Manager app
* Improve compatibility with different ROMs and kernels when booting a ROM
from the Android app
MultiROM v23
=====================
* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
installation won't boot, go to recovery and use "Re-patch init" option in
Advanced -> MultiROM -> List ROMs -> *ubuntu*.
MultiROM v22c
=====================
* Fix graphics corruption with some custom kernels
MultiROM v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
[url]http://bit.ly/ut_sharing[/url] for more info.
MultiROM v22a
=====================
* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
MultiROM v22
=====================
* Fix Ubuntu Touch boot taking long time
* Fix Ubuntu Touch freezing on Google logo for some users
MultiROM v21a
=====================
* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
MultiROM v21
=====================
* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
breaks the boot.
MultiROM v20
=====================
* Support booting ROMs directly from Manager App
* Fix FCs on CyanogenMod-based ROMs
* Fix support for USB drives formatted with NTFS, broken in v17
* Mount /system in secondary ROMs read-only
MultiROM v19
=====================
* Initial version
Recoveries:
Code:
28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
* Bunch of ROM compatibility fixes - recovery now uses entirely new way to
inject ZIP installation files, which should be much more robust and reliable
* Big ZIPs (> 450MB) are no longer permanently modified when flashed as
secondary ROMs
* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
12.2.2015
=====================
* Update to TWRP 2.8.5
* Fix support for ROMs containing a supersu.zip in their installation file
(e.g. AICP)
15.11.2014
=====================
* Support for ZIP files which are using the new 'block_image_update' command
(e.g. SimpleAOSP ROM)
29.10.2014
=====================
* Update to TWRP 2.8.1
21.10.2014
=====================
* Update autoboot settings for MultiROM v29
14.9.2014
=====================
* Update with changes from 2.8.0.1 upstream version: fix a bug that causes
weird graphics glitches and touch issues
11.9.2014
=====================
* Update to TWRP 2.8.0
* Fix adding ROMs from backup to a FAT32 USB drives
* Remove "share kernel with internal?" from "Add ROM" page, there is usually
no reason to use it anymore and it might be confusing to figure out what it
actually does. You can still get the same behavior by clicking "Remove
boot.img" on the List ROMs -> *rom name* page.
12.8.2014 - 1
=====================
* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
version
11.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation
8.8.2014
=====================
* Show secondary ROM's name in the title bar while executing it's script (e.g.
during OTA update)
* Update Ubuntu Touch updater
* Fix failure to swap ROMs if it contains filenames starting with a dot
* Fix add ROM from a backup producing unbootable ROM with Android L preview
* Add option to remove radio.img from secondary ROMs
* Add config options for MultiROM v27
5.6.2014
=====================
* Update to TWRP 2.7.1
* Hide misleading "Mount: Unable to find partition for path '/data'" message
which appeared during secondary ROM installation, it is not _actually_ an
error.
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
12.5.2014
=====================
* Fix crash during settings loading, causing a bootloop with certain settings
11.5.2014
=====================
* Add F2FS support
* Add tool to switch F2FS<->ext4 to Advanced menu
* Fix problems with backups introduced by TWRP 2.7.0
8.3.2014
=====================
* Update to TWRP 2.7.0
* Remove "save" button from MultiROM settings page, it is saved automatically
now
27.2.2014
=====================
* Support for system-image based (from the Manager app) Ubuntu Touch
installation
* Fix time in recovery
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
4.2.2014
=====================
* Update to support latest Ubuntu Touch testing builds
* Fix date and time in recovery
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
26.1.2014
=====================
* Fix radio in Ubuntu Touch
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
Credits :
@Picohackrhackr for the recovery
@tassadar for the entire multirom
@h2o64 for the OP
DOWNLOADS
Tested Configuration:
Primary Rom: CM12
Sec. Rom: CM12
Sec. Rom: SLIMLP
Sec. Rom: AICP
Sec. Rom: FIREFOX OS
Sec. Rom: CM11 - BEFORE BOOT CM11 AS SECONDARY FLASH SuperSU - BE SURE TO FLASH IT TO CM11 AND NOT TO PRIMARY ROM
Donations / Coffee kitty
Paypal
BiTCOiNS
THX A LOT!:good:
XDA:DevDB Information
MultiROM v32, Tool/Utility for the Moto G
Contributors
sub77, sub77, Brawn_Sg
Source Code: https://gitlab.com/sub4s0nik
Version Information
Status: Beta
Created 2015-04-01
Last Updated 2015-04-01
XDA:DevDB Information
deletetest2, ROM for the Moto G
Contributors
sub77
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2015-04-01
Last Updated 2015-04-01
Reserved
DOWNLOAD
MultiROM:
MultiROM v32
MultiROM TWRP:
MultiROM TWRP 2.8.6 for Bootloader v41.13
MultiROM TWRP 2.8.6 for Bootloader v41.18
MultiROM TWRP 2.8.6 Theme Only - Flashable Zip
KEXEC PATCHED KERNEL:
HYBRID LP (AnyKERNEL)
CM12 for Bootloader v41.13 - use with CyanogenMod based ROMs installed as Primary Rom.
CM12 for Bootloader v41.18 - use with CyanogenMod based ROMs installed as Primary Rom.
MISC:
BOOTLOGO
UNINSTALLER
Hooold up...is it same version with Brawn version or is totally yours
Any chance stock ROM as secondary with primary CM12
Sent from my Moto G using Tapatalk
SH1M4BD3 said:
Hooold up...is it same version with Brawn version or is totally yours
Click to expand...
Click to collapse
Pls dont use this thread.
Will be deleted.
Thread closed as per OP request
NB, we do not routinely delete threads.
{
"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.InstallationManual 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-taoshan.zip) - download the ZIP file from second post and flash it in recovery.
Modified Recovery (multirom-YYYYMMDD-recovery-taoshan.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 ROMs1. 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
Updating/changing ROMs1. 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 menusMain 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 codeMultiROM - https://github.com/STRYDER-007/multirom_xperia (branch multirom-7.1)
Modified TWRP - https://github.com/nkk71/android_bootable_recovery/ (branch android-7.1-mrom)
Device Tree - https://github.com/STRYDER-007/multirom_device_sony_taoshan (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/STRYDER-007/android_kernel_sony_msm8930 (branch multirom)
MultiROM available for Taoshan also thanks to :- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- @Olivier and @Adrian DC for lot of precious help and guidance in fixing many things
- @nkk71 for no-kexec workaround
- @Agent_fabulous for testing
- My Xperia L for surviving this!
XDA:DevDB Information
MultiROM for Xperia L, Tool/Utility for the Sony Xperia L
Contributors
STRYDER~007
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-06-13
Last Updated 2016-09-24
Downloads
1. Main downloads
MultiROM: multirom-2017MMDD-v33x-taoshan.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-taoshan.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8930 Marshmallow based):
multirom_kernel-2016MMDD-taoshan.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.
2. Third-party kernels with kexec-hardboot patch
* None, No longer needed due to no-kexec implementation.
3. MultiROM Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
* Flash uninstaller zip from recovery to remove MultiROM completely. This will also remove all your secondary ROMs.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...)
OPTIONAL: Read about the no-kexec workaround by nkk71
Reboot the phone and Enjoy MultiROM!
Changelogs
Code:
=========================================
MultiROM v33x - TWRP 3.1.1 - 02/10/2017
=========================================
* Fixed incorrect mounting of partitions in TWRP
* Removed unused and deprecated flags in TWRP
* Fixed MultiROM TWRP versioning
=========================================
MultiROM v33x - TWRP 3.1.1 - 24/09/2017
=========================================
* [B]Fixed touchscreen issue in MultiROM UI[/B]
* cyttsp3: Update multi-touch protocol for display driver
* defconfig: Compress kernel with XZ (Smaller TWRP Size)
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
* Include all recent improvements from TWRP 3.1.1
* Updated to no-kexec workaround v4.1 by nkk71
* Autoboot accessible for external / MicroSD
* Improved versioning with header showing build date
* Built in a clean new tree of Android 7.1.2 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
=========================================
MultiROM v33x - TWRP 3.1.0 - 15/06/2016
=========================================
* Fixed MultiROM logo in UI
* Some Minor changes in the UI
=========================================
MultiROM v33x - TWRP 3.0.2 - 13/06/2016
=========================================
* Initial public release
FAQ and other notes
FAQ and other notesAbout 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/STRYDER-007/multirom_device_sony_taoshan -->
Awesome work bro,thanks!!!
You are the best
Honestly, I never imagined that I'll be able to see multiRom on Xperia L
Thanks Dev. :laugh:
Awesome dev!
Will test it as soon as possible!
Thanks!
Awesome! Will test it for sure
WTF (What The Fantastic)
You're the best I'll try it ASAP
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Mouaz Kaadan said:
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
Click to expand...
Click to collapse
1. Yes
2. Yes. You can keep your data along with ROM installation on ext sd.
n78 shadow said:
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Click to expand...
Click to collapse
No chances of bricking at all if you follow instruction and flash it correctly.
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Aenadon said:
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Click to expand...
Click to collapse
1. Yep.
2. There is no Ubuntu OS ported for Xperia L.
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
kumardeepu said:
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
Click to expand...
Click to collapse
Please go through entire thread. Everything is written there.
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.
Click to expand...
Click to collapse
STRYDER~007 said:
Please go through entire thread. Everything is written there.
Click to expand...
Click to collapse
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
kumardeepu said:
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
Click to expand...
Click to collapse
Yes.
Well actually in detail, First stock rom via flashtool->Root->Install SuperSU->Install Recovery via Recovery Installer app->Flash MultiROM Recovery zip->Reboot to MultiROM recovery->Flash MultiROM zip->Add Custom ROM!
MultiROM Updated
MultiROM updated with minor UI changes. Check OP.
Changelogs-
Code:
** 15-06-2016
- Fixed MultiROM logo in UI
- Some Minor changes in the UI
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
ShadowA9 said:
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
Click to expand...
Click to collapse
Flash MultiROM recovery zip first then boot into new recovery and flash multirom zip.
{
"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 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.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: There have been reports that (not only) MultiROM does not work properly with older bootloaders. Update it to version 4.13 or newer in case you have problems.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Ubuntu Desktop
Ubuntu desktop for Nexus 7 has been discontinued and is no longer updated. 13.04 is the last release.
Download Ubuntu 13.04 image from here. Put the image in the memory of N7 or to USB flash drive and go to recovery. Select Advanced -> MultiROM -> Add ROM and choose "Ubuntu" as ROM type. Then select the Ubuntu's image and confirm. Clean installation of Ubuntu is 1.5gb big, and takes a while (10 minutes?) to install.
The first boot takes a bit longer, and 13.04 stays a while (30-60s) in console ("Enter login:") before the GUI shows up, so just wait a while.
Ubuntu ROM must not have spaces in name!
Using Ubuntu on N7, Frequently Asked Questions
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/Tasssadar/multirom (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
XDA:DevDB Information
MultiROM, App for all devices (see above for details)
Contributors
vasishath, shahan_mik3
Source Code: https://github.com/Tasssadar/multirom
Version Information
Status: Beta
Beta Release Date: 2017-03-15
Created 2017-03-16
Last Updated 2017-03-16