{
"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 Htc One (m7). 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
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
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-UNOFFICIAL-m7.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_m7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/Tasssadar/multirom (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device files - https://github.com/dzej1/android_device_htc_m7
Donations to Tassadar
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Thanks to all donors, it is much appreciated
Downloads
1. Main downloads
MultiROM: multirom-20141028-v29-UNOFFICIAL-m7.zip
Modified recovery (based on TWRP): TWRP_multirom_m7_20141028.img
Working on it MultiROM Manager Android app: Google Play or link to APK
You need to have kernel with kexec-hardboot patch only in your primary ROM!
2. third-party kernels with kexec-hardboot patch
ElementalX - http://forum.xda-developers.com/showthread.php?t=2249774
teaMSeven - http://forum.xda-developers.com/showthread.php?t=2307371
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 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.
* Sense-based ROMs (hopefully) with working storage
* Android 5.0 preview related tweaks
MultiROM v28b
=====================
* Now working Sense-based ROM as secondary.
MultiROM v28a
=====================
* Some edits in device files
MultiROM v28
=====================
* Fix freezes in the boot manager
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
* SailfishOS support (for certain devices)
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
* Misc F2FS fixes
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 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
=====================
* Fix hardware keys not working for some users
* Update Ubuntu Touch patches
MultiROM v22
=====================
* Fix linux-type ROMs (Ubuntu Touch) failing to boot for some users
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
=====================
* Implement "boot the last ROM" auto-boot type
MultiROM v18
=====================
* Fix silent-but-unpleasant crash with exFAT
MultiROM v17
=====================
* Changes to support MultiROM Manager app
* Add support for exFAT
MultiROM v16a
=====================
* Fix kexec not working on some kernels
MultiROM v16
=====================
* Add overscroll bounceback effect to rom list
* Add support for controling via physical keys
* Bunch of under-the-hood changes for mako and m7 support
MultiROM v15
=====================
* Fix cmdline handling for kexec, doesn't change anything for grouper, just to
have the same version for both flo and grouper (no need to update)
MultiROM v14
=====================
* Find and change correct fstab (fixes freezes on boot)
* Mount /realdata without nosuid (fixes no root on 4.1 and 4.2 ROMs)
* Use libbootimg to work with boot.img files
MultiROM v13
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices
* Add run-on-boot scripts (for advanced users who know linux and bash, see
[url]https://github.com/Tasssadar/multirom/wiki/run-on-boot-scripts[/url])
* Use libbootimg to work with boot.img files
MultiROM v12a
=====================
* Detect kexec-hardboot patch in kernel even if /proc/config.gz is not
available
MultiROM v12
=====================
* Implement screen rotation and 1280x800 theme
* Fix auto-boot option
* Fix listview's fast scrollbar behavior
MultiROM v11
=====================
* Option to hide Internal ROM
* Option to rename Internal ROM
* Support for Ubuntu Touch
MultiROM v10
=====================
* Non-error message boxes aren't red now
* Add possibility to switch between several color themes, go to misc tab and
try it out
* New MultiROM installer format
* Add "discard" option to /data mounting
* Add battery status to misc tab (bottom right corner)
* Add brightness setting
* Implement ADB
MultiROM v9
=====================
* Make it compatible with LZ4 ramdisk compression
* Improve touch-related code. You should not get anymore phantom button
presses nor listview freezes
MultiROM v8
=====================
* Fix kexec-hardboot with new bootloader v4.18
* Search for already present USB drives on start
* Centre "MultiROM" title in main UI
MultiROM v7
=====================
* Correctly boot Ubuntu after recent kernel update. Read this post:
[url]http://forum.xda-developers.com/showpost.php?p=37389003&postcount=1031[/url]
* Remove specific support for Ubuntu - it is now handled as "generic linux"
(with rom_info.txt file). Nothing should change for the users
* Sort ROMs alphabetically
* Add "progress dots" to USB screen, so that user knows that it is doing
something
* Recovery was also updated, don't forget to flash it
MultiROM v6
=====================
* Properly check for kexec-hardboot patch in kernel
* Internal" is always first in ROM list now, as originally intended
* Much more logging for kexec-related stuff
* Print last 50 lines of klog to "Emergency reboot" screen
MultiROM v5-2
=====================
* Fix ubuntu
* MultiROM still says it's v5. I did not change the version number because it
is literally one character fix.
MultiROM v5
=====================
* Support for ROMs with configuration file. This makes porting
Ubuntu/plasma/webos/anything much more easier. See the third post.
* MultiROM will no longer let you boot Ubuntu ROM if it's name contains
spaces, because the boot would fail.
MultiROM v4
=====================
* Fix GPS on ROMs other than Internal
* Minor UI changes
MultiROM v3
=====================
* Switch to Ubuntu 13.04. Version 12.10 is no longer supported
* Switch to kexec-hardboot based multi-booting. Read the first post.
* Add support for booting from USB drive
* MediaScanner no longer scans /sdcard/multirom, which means no useless
battery drain
* Recovery was updated, make sure to flash it, too.
MultiROM v2
=====================
* Add support for Ubuntu on 3G version of Nexus 7
* Fix some issues with 4.2 ROMs
* Recovery was updated, make sure to flash it, too.
MultiROM v1
=====================
* Initial version
Recoveries:
Code:
28.10.2014
=====================
*Update autoboot settings for MultiROM v29
26.9.2014
=====================
* In app finally as MultiROM-Recovery.
22.9.2014
=====================
* Working USB-OTG
18.9.2014
=====================
* Initial version
@domicq thank you for your efforts, have to try this out
EDIT: TWRP doesn't work, I just get a reboot
dd98 said:
@domicq thank you for your efforts, have to try this out
EDIT: TWRP doesn't work, I just get a reboot
Click to expand...
Click to collapse
I have any problem with TWRP, specially for you have i downloaded and flashed recovery from my post. Try flash it again, or flash clean twrp and then flash mrom-twrp
domicq said:
I have any problem with TWRP, specially for you have i downloaded and flashed recovery from my post. Try flash it again, or flash clean twrp and then flash mrom-twrp
Click to expand...
Click to collapse
Unfortunately it still doesn't work, I tried flashing the Official TWRP, booting into it and then flashing your MultiROM TWRP but it didnt work
It is possible install Miui as secondary Rom ? Thanks
Enviado desde mi HTC One mediante Tapatalk
kevinlopez97 said:
It is possible install Miui as secondary Rom ? Thanks
Enviado desde mi HTC One mediante Tapatalk
Click to expand...
Click to collapse
I haven't tried that. But you can try it.
kevinlopez97 said:
It is possible install Miui as secondary Rom ? Thanks
Enviado desde mi HTC One mediante Tapatalk
Click to expand...
Click to collapse
Everything I've tried works including miui (I think too many to remember). Only issues I've had is with ROMs that use aroma. To install these as secondary.....
Nandroid original primary
Flash new Rom as primary
Boot new Rom
Nandroid new primary
Restore original primary
Install new primary as secondary from nandroid
Never had to change recovery either.
Always back primary when trying a new secondary.
Sent from my HTC One
MultiROM Manager - Unofficial edit with m7 support
mrommgr-147-m7.apk (official release comes maybe next week, it has problems with checking if device has multirom twrp, so you can use apk for renaming roms and adding rom icons)
You sir are fantastic. In going to try three ROMs: SinlessGPE, L preview port, and ViperONE. Hope all goes well
ANDR01DN00B said:
You sir are fantastic. In going to try three ROMs: SinlessGPE, L preview port, and ViperONE. Hope all goes well
Click to expand...
Click to collapse
L port didn't work for me just hung on splash screen but i expected it
liam_davenport said:
L port didn't work for me just hung on splash screen but i expected it
Click to expand...
Click to collapse
I got it to work literally once. There's a proprietary lib zip I can pm you that you can possibly try. What I did was:
Delete current version of L ROM, install it again with lib zip, and superSU.
ANDR01DN00B said:
I got it to work literally once. There's a proprietary lib zip I can pm you that you can possibly try. What I did was:
Delete current version of L ROM, install it again with lib zip, and superSU.
Click to expand...
Click to collapse
Thanks man, Much appreciated
Anyone tried This ?
Want to use viper and liquid smooth Rom but i dont want to risk anything because my lower Button dont work and cant Boot to recovery if i get a bootlopp etc ..
Sent from my HTC One using XDA Free mobile app
ANDR01DN00B said:
I got it to work literally once. There's a proprietary lib zip I can pm you that you can possibly try. What I did was:
Delete current version of L ROM, install it again with lib zip, and superSU.
Click to expand...
Click to collapse
Upload it if you can. I'd be willing to try.
hey ! nice to see some cool changes on this tool.
I'm on the older Multirom 19v with 2.7.0 TWRP, do i have to just flash Recovery and zip file ? or do i need to uninstall the older version ?
Thanks:good:
I cannot boot ViperONE as my secondary. Here is log: https://docs.google.com/file/d/0B64IJ9xlDpb4X0NZWHlNZVVJc3M/edit?usp=docslist_api
Cool stuff, but weird issue: used flashify to update recovery, then flashed new multirom. Everything fine so far, but when rebooting, my phone did a factory reset.
remix92 said:
Anyone tried This ?
Want to use viper and liquid smooth Rom but i dont want to risk anything because my lower Button dont work and cant Boot to recovery if i get a bootlopp etc ..
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Hold power and volume up. Takes you to bootloader then recovery from there.
Sent from my HTC One
ANDR01DN00B said:
I cannot boot ViperONE as my secondary. Here is log: https://docs.google.com/file/d/0B64IJ9xlDpb4X0NZWHlNZVVJc3M/edit?usp=docslist_api
Click to expand...
Click to collapse
That needs installed as primary first. See my earlier post.
Sent from my HTC One
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 Samsung Galaxy Note II. 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 the 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 support 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
* Install ROM to external SD card [Newly Added feature]
You can also 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 - This at present does not have support for n7100, working on getting it enabled.
This is the easiest way to install everything MultiROM needs. Install the 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 (the 3rd party kernel should also have kexec-hardboot patch) 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 . If you want, just search for "MultiROM installation" on and 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-t03g.zip) - the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_t03g_YYYYMMDD.img) - the zip file from second post and flash it in recovery.
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.4 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. 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
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 and then reboot.
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.
To flash GAPPs for the Secondary ROMS, Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash GAPPS ZIP file.
Installing of Touchwiz as Primary Rom & AOSP ROM as Secondary.
Boot into recovery and flash Modified TWRP Multirom recovery
Next, Flash the Multirom zip.
Next, Flash the Modified Agni Stock Kernel and then flash the Mali blobs zip too and finally reboot the phone
Allow the phone to auto boot into the touchwiz rom. Once booted reboot the phone into recovery again.
Now you can flash any AOSP rom as Secondary ROM. for that follow the below steps
Select Multirom - > Add Rom -> ROM Type & Location to install the ROM -> AOSP ROM ZIP -> start the installation.
After installation is complete, go back and select the AOSP ROM that you installed and select "Remove Boot.IMG".
Reboot the Phone now and in the Multirom Manager Menu, select the secondary rom and allow it to Boot.
Note : Wifi is not working on the AOSP ROM installed as secondary, this needs to be debugged further. I am guessing it is due to the kernel version installed on the stock rom versus the touchwiz roms. Apart from the wifi, all other features are working fine.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/tilaksidduram/android_kernel_samsung_smdk4412/commits/kitkat
MultiROM device tree - https://github.com/tilaksidduram/android_device_samsung_t03g
Thanks a lot to Tasssadar for creating this awesome utility.
XDA:DevDB Information
MultiROM, Tool/Utility for the Samsung Galaxy Note II
Contributors
tilaksidduram
Version Information
Status: Beta
Created 2014-10-10
Last Updated 2014-10-11
Downloads
1. Main downloadsMultiROM: Multirom Zip
Modified recovery for Multirom (based on TWRP) : Multirom Recovery zip
Kernel with kexec hardboot patch for AOSP ROMs only : Kernel Zip
Note : Other 3rd party AOSP Kernels like Agni, Plasma & Devil do not have the Kexec Hard-boot patch in them at present, so if you have flashed them on you primary ROM then you will not be able to boot into any of the secondary ROMS. I am working with the kernel owners to have the kexec hard-boot patch added into the kernel.
Kernels for Secondary ROMS : These Kernels are not Kexec Hardboot enabled, install them to fix the WIFI Issue on secondary ROM.
1. Omni ROM
2. SlimKat ROM
3. MIUI ROM
4. CM 11
5. Paranoid Android
Kernel with kexec hardboot patch for Touchwiz ROMs only : Agni Kernel for Stock Touchwiz ROMs
Kernel Developers, please merge this patch into your kernel - https://github.com/tilaksidduram/an...mmit/2c9d9821eaa7e250ffe89b67d0a6c8b1c8219bc4
You need to have kernel with kexec-hardboot patch only in primary ROM
2. 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
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. 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.
Great work. @tilaksidduram
:laugh::laugh::laugh: great, I'll try this ! :highfive:
Sounds interesting!
Great work indeed
Amazing, superb, perfect, brillant, excellent You are great man, you are great. I'm waiting for this since I saw this in Nexus 4 forum. Thanks.
Great work.
Finally wait is over?
wow i'm waiting the link for download
Thank you sir, first for bring MultiRom to our Note 2, second for step-by-step instruction. I can't wait for DL and try. Amazing job.
finally multirom for note2... thanks you....
Sent from my GT-N7100 using XDA Premium 4 mobile app
OK Tilak! Thanks for your work! Let's wait a kernel with the patch, I want to try this solution :laugh::laugh::laugh:
FUSIONdev said:
OK Tilak! Thanks for your work! Let's wait a kernel with the patch, I want to try this solution :laugh::laugh::laugh:
Click to expand...
Click to collapse
I already patched the stock kernel and it available for download in my 2nd post. you can flash it against any AOSP based Kitkat Rom for the N7100.
Currently i am running PA as my primary rom and i have installed around 6 other roms (Omni, Slimkat, Miui, Liquid smooth, CM 11, ) as secondary. All of these are working fine.
give multirom a try.
Nice....work
Let's hope the Kernel Devs include the patch so that we can also test/check it with Samsung Touchwiz Kitkat Roms
By the way Thanks @tilaksidduram for bringing this treat to us
Bug? Or problem a part those listed in op?
Inviato dal mio OnePlus One
Thanks @tilaksidduram
Thanks
Thanks bai thanks. You r the great. keep going on......
Looks very interesting definitely gotta check this out...
Thanks for the contribution to the note 2 users :good:
This is only working on aosp roms? Is possible to run a touchwiz rom and an aosp rom?
{
"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 LG G3 [D85x/F400/LS990/VS985]. 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, 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
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 (optional) - 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.
Click to expand...
Click to collapse
2. Manual installation
Note 1: Encryption is supported, but not recommended to be used with MultiROM.
MultiROM has 3 parts you need to install:
MultiRom: (multirom-YYYYMMDD-vXX-UNOFFICIAL-<device>.zip) - download the ZIP file from second post and flash it in recovery.
Modified Recovery: (TWRP-multirom-YYYYMMDD-<device>.zip) - download the ZIP, Flash with TWRP
Patched Kernel (Optional): 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.
Click to expand...
Click to collapse
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM (For TWRP 3.0.2+ MultiROM Icon is in the top right corner). Select the ROM's zip file and confirm. As for the space, clean installation of stock LP or MM 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 AS MOST OTHER PORTS, IF YOU CARE TO ADD SUPPORT, PLEASE DO SO. THANK YOU
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 Advanced -> MultiROM (For TWRP 3.0.2+ MultiROM Icon is in the top right corner) in recovery and do Inject curr. boot sector.
Flash MR_Bump script (only for bump'd devices)
Click to expand...
Click to collapse
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 (For TWRP 3.0.2+ MultiROM Icon is in the top right corner) 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.
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 - Settings to change behavior of MultiRom.
Click to expand...
Click to collapse
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
Thanks to
@Tasssadar - For Multirom
@Eliminater74 - For previous work on MultiROM for G3 devices
@nkk71 - For the extra twrp/multirom mods including The kmsg logging options and no kexec workaround
@z31s1g - For The TWRP Themes (MultiRom)
Click to expand...
Click to collapse
XDA:DevDB Information
MultiRom Resurrected, Tool/Utility for the LG G3
Contributors
bryan2894, Eliminater74, thewalkingdude
Source Code: https://github.com/multirom-g3
Version Information
Status: Stable
Created 2015-07-11
Last Updated 2018-02-16
Downloads
Downloads
Flash Order
TWRP
MultiROM Installer
Bump Script Mod Modified by @dadi11 (only for kexec kernels)
Confused? Read the FAQ on how to install MultiROM.
Click to expand...
Click to collapse
Attention
I can now be reached though IRC on Channels #lg-irc and #MultiRom
at this Link: IRC: FreeNode
Just enter your Nickname and verify that your not a bot and click connect.
Click to expand...
Click to collapse
Downloads
MultiROM Installation Files: AFH
MultiROM Manager: Supports All Devices
Bump Script: Bump Script Modded by @dadi11
MultiROM Re-injection Script: MultROM_Reinjection_Script_1.1.zip
Click to expand...
Click to collapse
D850/D852/D855/D856/LS990/VS985 recoveries are pre-bumped
Click to expand...
Click to collapse
Changelog
MultiROM
Code:
====================
02-16-2018
====================
* MultiROM v33e
* multirom: Support for encryption
* multirom: Fix multirom for devices using SDCardFS (@nkk71)
* multirom: Support for Android 8.0 ROMs (@nkk71)
====================
06-16-2017
====================
* MultiROM v33e
* multirom: Support mounting booted external EXT4/F2FS (@AdrianDC)
====================
01-24-2017
====================
* MultiROM v33d
* Add LineageOS icon
* Patches by nkk71:
* Fix: Update external partitions mount strategy
====================
11-04-2016
====================
* MultiROM v33c
* Enable no-kexec support by default (used if necessary)
* NOKEXEC: Re-bump boot before flashing primary_boot.img
* Integrate bump into trampoline (bump after injection)
* MultiROMMgr: show partition mount for ext ROMs
* Credit to @nkk71 for the following patches:
* NO KEXEC 4.1
* Fix booting into ext ROMs from MultiROMMgr
* Fix segfault in Developer Options
* Support for Android 7.1+ ROMs
====================
10-10-2016
====================
* Add support for bump'd devices
* Auto-bump devices after injecting MultiROM
* Fix image flashing
* MultiROMMgr: add support for stock roms
* MultiROMMgr: add support for external roms
====================
09-27-2016
====================
* MultiROM v33b
* No kexec-hardboot support v4 (by @nkk71)
* Allow auto booting from external storage (thx to @nkk71)
* Update MultiROMMgr app to support no kexec-hardboot (thx to @premaca)
====================
08-26-2016
====================
* MultiROM v33a
* No kexec-hardboot support (by @nkk71)
* Fix unknown boardname issue
====================
06-19-2016
====================
* Initial app and kernel release
TWRP
Code:
====================
02-16-2018
====================
* TWRP 3.2.1-0
* recovery: Support for encrypted devices
* recovery: fix support for adoptable storage
====================
06-16-2017
====================
* TWRP 3.1.1-0
====================
01-24-2017
====================
* TWRP 3.0.3-0
* Patches by nkk71:
* MultiROM: Create real block device for fake boot.img (fixes long kernel flashes)
* MultiROM: Fix restorecon to use ROM's own binary
* MultiROM: Add failed boot.img injection warning
====================
11-04-2016
====================
* Fix image flashing
* Move bump tools to multirom/trampoline
====================
10-10-2016
====================
* Add support for bump'd devices
* Auto-bump devices after injecting MultiROM
====================
09-27-2016
====================
* No kexec-hardboot support v4 (by @nkk71)
* Fix installFromBackup (thx to @nkk71)
* Fix support for Nougat ROMS (thx to @nkk71)
====================
09-06-2016
====================
* Fix recovery for F400
====================
08-26-2016
====================
* No kexec-hardboot support (by @nkk71)
* Add secondary support for ROMS with system.img (by @nkk71)
====================
07-03-2016
====================
* Updated kernel for recovery (fixes Aroma crashing)
* Add sd-ext partition to fstab
====================
06-19-2016
====================
* Updated recovery to 3.0.2-0
* New Stock TWRP 3.0 Theme (thanks to @z31s1g & @nkk71)
MultiRom FAQ
1: HOW DO I INSTALL:
Here is a helpful post from a user on how to install MultiROM successfully.
{101}darkvoid090 said:
First of all I would like to thank the developer for responding to my feedback and pushing an update for f400 devices that fixed the no kexec work around. It is working now and can be enabled. I have managed to install and successfully boot {aosp}(DU 10.5 unofficial port) and bliss 6.4 and {cm13}(Bliss 6.4 official port). The trick to install these roms while using stock based (fulmics 6.1) in my case is to do the following: :silly:
1- Have latest twrp multirom/multirom installer flashed
2- Flash Mr.Bump.zip on primary (follow link from 4th download)
3- Go to multirom options and enable no kexec workaround (use the enable only when needed option)
4- Add a new rom using its zip file
5- Flash gapps(optional)
6- Flash acc kernel (may not be required)
7- Flash Mr.Bump.zip (very important otherwise you get boot auth error when booting to secondary room)
8- the device will automatically reboot after step 7, choose your rom from the list and wait for it to boot, your device might get stuck on the LG logo for a few minutes at first time, wait for the rom to boot up to 5 minutes if its still at the lg logo, and up to 10 minutes if its at the rom logo.
9- That's it you should be ready to go now.
*My Personal Notes and observations:
a- Flashing the no kexec kernel zip from the crossed section 3 in downloads in any of the secondary roms will eliminate the need for no kexec workaround (at the expense of secondary rom system stability)
b- Installation/Flashing of any zip in secondary rom takes a VERY LONG TIME so wait patiently (Specially for Kernel) {is there any way to fix this?}
c- Using the external SD Card is not recommended since its very slow compared to internal memory (at least in my case) although i have a kingston class 10 MicroSD card 64GB. I recommend instead that you move some stuff onto the sd card to make space for the rom
d- the secondary roms will notify you about your sd card as soon as they boot. open the setup and choose the first option (use to store files videos etc...) if the setup says corrupt sd card, you might have to format it, just move your stuff somewhere safe, format the card in the rom the requires it, then move your stuff back. The card will work with all your roms without issues when formatted. This workaround was needed to use the sd card with unofficial DU port, it may be fixed in later versions, but as it stands now this is the only workaround available. DUE TO THIS ERROR DU MAY NOT WORK WITH SD CARD INSTALLATION, please take note of this.
e- Sometimes boot actions will not complete(updating Supersu library for example), recovery actions will have no result(ota scripts or Supersu library update through twrp method), fixed by deleting the rom from multirom twrp then re adding it.
f- Main rom refuse to boot/ boots into recovery when selected: reinject boot sector for primary rom, worst case you might have to dirty flash it.
g- I recommend against messing with kernel settings even though it provides a wide range of options, so far I have had 2 boot loops(or maybe I'm just noob lol )
h- So far no issues with bluetooth or wifi or any functions in both roms, will report after further testing.
*bonus tip: stuck with boot auth error? you can reboot your phone into recovery with hardware buttons using the following combination (tested on F400L):
Power+volume down > 2 seconds after lg logo appears release both then immediately press volume up+down ONLY. if you do it right you should reach the factory reset screen which will actually take you to recovery not format your device.
Click to expand...
Click to collapse
2: Android M and or CM13 gives me binary errors when installing on secondary
Should be fixed on latest TWRP v3.0 Flash that.
Click to expand...
Click to collapse
3: My secondary ROM fails to boot, but it was working before... OR
My secondary ROM fails to boot, and returns to the MultiROM menu/Recovery...
You may need to fix the SELinux contexts. From recovery, in the MultiROM menu, select List ROMS and choose the ROM that doesn't boot. Then choose the "restorecon" option. This should restore the SELinux contexts for your secondary ROM and fix the boot.
Click to expand...
Click to collapse
4: What is the no-kexec workaround and how do I enable it?
The no-kexec workaround by @nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
More details about can be read here: http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
Click to expand...
Click to collapse
Amazing! But i cant test it!
Enviado desde mi LG-D855 mediante Tapatalk
Awesome !!
Little question : Does kernels needs to be updated with a new kexec-hardboot patch, or it's fine with current kernels ? Thanks for you work !
RL77LUC said:
Awesome !!
Little question : Does kernels needs to be updated with a new kexec-hardboot patch, or it's fine with current kernels ? Thanks for you work !
Click to expand...
Click to collapse
Only the New patch works. But its easy to patch.. you can also revert your old patch and apply the new one. its pretty simple takes like 5 secs........
Eliminater74 said:
the op
Click to expand...
Click to collapse
I just wanted to ask does it work for the stock kernel too, or is that still a no go (you only have the cm kernel in your thread)
suljo94 said:
I just wanted to ask does it work for the stock kernel too, or is that still a no go (you only have the cm kernel in your thread)
Click to expand...
Click to collapse
The patch has been applied to stock kernels as well..
can i have an stock based rom as primary and a aosp based as secondary?
I can help you testing, i have a d855 16gb, currently using the "old" multirom, with stock as primary and cm12.1 as secondary.
I think flashing your new "multirom.zip" and your patched stock kernel, can be an easy (and safe) test to begin with.
datCalata said:
can i have an stock based rom as primary and a aosp based as secondary?
Click to expand...
Click to collapse
You can have whatever combo you want even whit "old" multirom [emoji2]
diogo.sena said:
I can help you testing, i have a d855 16gb, currently using the "old" multirom, with stock as primary and cm12.1 as secondary.
I think flashing your new "multirom.zip" and your patched stock kernel, can be an easy (and safe) test to begin with.
Click to expand...
Click to collapse
Have you tried? Interested to know if it works :good:
I'm interested, I can help you to testing it... I have a D855 16GB with oldest multirom installed
I'd be glad to help you
Hi
I would like to help you with testing, I have an LG G3 D855 32GB (the one with 3GB of RAM). What should I do?
Thanks
Daniele
Meakii said:
Have you tried? Interested to know if it works :good:
Click to expand...
Click to collapse
Calm down, i just offered help, doesn't mean i'm testing...
Hi @Eliminater74
Could you tell us how is it going : did you find some tester or are you still looking for it ?
Thanks for your work !
One more tester with 16GB variant here. What should I do?
I would like to beta test I have the 32/3 on a stock rom but it is no problem to test this on a cm based rom,
Update: I have created the MultiRom TWRP Recovery Image thats is the correct size and I feel good enough to release this full version here now......
Im just waiting for a few more parts to compile and ill post it up........................
UpDate: MultiRom is now Up for downloading..
Please Note: This is still testing.. I do not own this Device. Let me know ASAP if it works or doesnt work.
{
"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 Redmi2. 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, once they are ported to Redmi2
* Boot from USB drive attached via OTG cable
Check this video with CM13.0 base and Tesla Secondary on our device.
You can also watch a video which shows it in action in general.
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 (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_wt88047_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel *OPTIONAL* - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch. (You do not need install patched kernel if you continue to use multirom with no-kexec-workaround only)
MultiROM (multirom-YYYYMMDD-vXX-wt88047-signed.zip) - download the ZIP file from second post 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.
Using USB drive (not tested yet)
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/multirom-redmi2/multirom (branch android-7.0-mrom)
Modified TWRP - https://github.com/multirom-redmi2/Team-Win-Recovery-Project (branch android-7.0-mrom)
Kernel w/ kexec-hardboot patch - https://github.com/premaca/Xiaomi_Kernel_OpenSource (branch cosmos)
Device Tree - https://github.com/multirom-redmi2/android_device_redmi2 (branch mrom)
Credits
Little or more, these are the people helped, motivated me to bring this to our device
@martinusbe
@Alx31
@Ashish94 (For building the kernel with my commits)
@nkk71 (For kexec workaround)
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
XDA:DevDB Information
[MOD][MAY 18][Redmi 2] MultiROM v33, Tool/Utility for the Xiaomi Redmi 2
Contributors
premaca
Version Information
Status: Beta
Current Beta Version: v33
Beta Release Date: 2016-05-18
Created 2016-05-18
Last Updated 2016-11-15
Reserved
Downloads
20161115
Download the required things from this folder - https://www.androidfilehost.com/?w=files&flid=129625
The kexec patched kernel is Jerrica cosmos, which you can use for MM and N ROMs as Primary/Secondary.
20160728
Download the required things from this folder - https://www.androidfilehost.com/?w=files&flid=85630
- no-kexec-workaround is announced Stable -
20160724
Download the required things from this folder - https://www.androidfilehost.com/?w=files&flid=83809
Old Downloads
1. Main downloads
MultiROM: multirom-20160710-v33-UNOFFICIAL-wt88047.zip
MultiROM: multirom-20160520-v33-UNOFFICIAL-wt88047.zip
MultiROM: multirom-20160518-v33-UNOFFICIAL-wt88047.zip
Modified recovery (based on TWRP):
TWRP_multirom_wt88047_20160710.img
TWRP_multirom_wt88047_20160520.img
TWRP_multirom_wt88047_20160518.img
Kernel w/ kexec-hardboot patch : OPTIONAL - If you continue to use multirom with no-kexec-workaround only
bk-180516v2.zip (Berserk Kernel)
multirom.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!, if not using no-kexec-workaround
2. third-party kernels with kexec-hardboot patch (NONE YET)
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller_20160520.zip
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.
4. Multirom manager APP
MultiROM Manager APP: MultiROMMgr-Redmi2.apk
Changelog
11.15
- Support for Nougat ROMs
- Kexec patched kernel based off Jerrica Cosmos release (Those who prefer kexec boot)
- No-exec workaround is enabled by default, you do not need enable explicitly, check it.
- You must install Recovery
[Note]: Tested with N ROM as Primary and other N and MM ROMs as secondary, both Internal and External. Have not tested any other scenarios, please let me know if you have issues in other cases.
07.28
- Back to be able to install Secondaries and Boot. (Do not know if there is temporary compatible issues, but reported that earlier version had issues)
- Multirom manager App compiled again for all variants
- The App doesn't still display the external ROMs, i will try see if we can fix it.
07.10
- Minor upstream changes
- Multirom manager App compiled and released.
05.18
- Enabled F2FS
- no-kexec-workaround (Please read post#3 for details)
- recovery updated to 3.0.0.2
- External SD Card ROMs are now shown with every reboot during Auto-boot dialogue
- External SD Card ROMs are tested, i'm running two Roms externally now
05.18
- Initial Release
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will Miui work as Primary or Secondary ROM?
Yes, MiUI Lollipop version works with Multirom as Primary ROM, once again reiterate, only as Primary ROM. You can then install other ROMs as secondaries.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
Reserved
Enabling no-kexec workaround
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Way to go Prema
Is it working fine now without any issue and thanks for awesome deving
salahXDA6805 said:
Is it working fine now without any issue and thanks for awesome deving
Click to expand...
Click to collapse
You guys are all to tell me about that, as of now it's working good. Go ahead and test out.
I meant do we have to press volume up button as shown in the video???? Or u have solved the glitch
salahXDA6805 said:
I meant do we have to press volume up button as shown in the video???? Or u have solved the glitch
Click to expand...
Click to collapse
Yes that is too fixed, follow the installation steps as told. Flash recovery, flash mrom-zip followed by kernel-zip.
Nothing is gonna happen to your current primary rom or any adverse affects. Go try it when you get time.
Okkkk brooo I'll try it soon and thanks once again
Nice job bud, keep it up!
great i am going to flash it
saurabh1234 said:
great i am going to flash it
Click to expand...
Click to collapse
For Secondary ROMs, add the ROM zip file, then go back to that and flash Gapps too, before you reboot into it. Otherwise, as usual you need to resolve SetupWizard FC, at least thats what I see in my device.
premaca said:
For Secondary ROMs, add the ROM zip file, then go back to that and flash Gapps too, before you reboot into it. Otherwise, as usual you need to resolve SetupWizard FC, at least thats what I see in my device.
Click to expand...
Click to collapse
yes that is gapps problem now days
Still confusing little bit
Can we boot different based rom? Last time i see ashish94 make video multi rom, but all rom based on aosp (tipsy & validus), so can us boot rom based cm13 & aosp, or maybe cm13 & miui too, or just same based rom?
RieTech said:
Still confusing little bit
Can we boot different based rom? Last time i see ashish94 make video multi rom, but all rom based on aosp (tipsy & validus), so can us boot rom based cm13 & aosp, or maybe cm13 & miui too, or just same based rom?
Click to expand...
Click to collapse
You can boot any custom rom, except MiUI (which i have never tried). I tried GZRoms, Temasek, RR as primary and vice versa (only those zip files are there in my scared :laugh::laugh.
Btw, that video is made by me :silly::silly: and Ashish shared it in his thread :silly::silly:
premaca said:
You can boot any custom rom, except MiUI (which i have never tried). I tried GZRoms, Temasek, RR as primary and vice versa (only those zip files are there in my scared :laugh::laugh.
Btw, that video is made by me :silly::silly: and Ashish shared it in his thread :silly::silly:
Click to expand...
Click to collapse
i want to know....is vFat is external storage...???
saurabh1234 said:
i want to know....is vFat is external storage...
Click to expand...
Click to collapse
Okay, currently the way it works is, which ever the partition is mounted, (default /external_sd) it is Internal, vFat is just a duplicate of it, never used it yet.
If you want to use actual Internal Storage, go to main 'Install' and use Select Storage. Then you come back here and 'Internal' becomes of that.
May be you can identify with 'XXXXX bytes' besides Internal (the size of the memory of that partition), i can at least because i use 32GB sdcard and real internal is 16GB.
premaca said:
You can boot any custom rom, except MiUI (which i have never tried). I tried GZRoms, Temasek, RR as primary and vice versa (only those zip files are there in my scared :laugh::laugh.
Btw, that video is made by me :silly::silly: and Ashish shared it in his thread :silly::silly:
Click to expand...
Click to collapse
Maybe u must tried with miui now haha (so i can follow u without getting any error )
Thanks for clearing my mind, maybe i need to try boot cm13 and aosp now~
*note: sry, i didnt if that video made by you lol
Miui is not working
I have tried this multiboot but it did not work with miui
DreamNexus said:
I have tried this multiboot but it did not work with miui
Click to expand...
Click to collapse
Of course crapui won't boot. The kernel only supports Android 6.0.
{
"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"
}
For LeEco LeMax 2
Supports all * Roms (see Compatibility sections)NOTE:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this Kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
What is MultiRom?
MultiROM is one-of-a-kind multi-boot mod. 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. Roms are installed and managed via the 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.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
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 possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
Compatibility
(From MutliROM boot menu. From MultiROMMGR some unworking ROM may work as Internal).
As Internal ROM tested & WORK:
- All ROMs
As Secondary ROM tested & NOT WORK:
- ROMs based on Android Nougat with enabled sdcardfs (for now tested & work: RR-N,AOKP,AICP,DU)
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:
This is the easiest way to install everything MultiROM needs... Just follow the Below Instructions:
* Install the app ( download link ) !!! App updated 04/13/17, please reinstall it!!!
* Select MultiROM and Recovery on the Install/Update card.
* Press "Install" on the Install/Update card to start the installation.
* DONE! MULTIROM IS READY TO ROCK!
You current rom WILL NOT be erased by the installation.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
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 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 the Rom, follow these steps:
* Go to MultiRom -> List Roms and select the Rom you want to update.
* Select "Flash zip" and Flash the 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 something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam 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 - No Need to Explain this I Think!
- 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 a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for LeEco
LeMax 2 MultiRom Device Trees
MultiRom Manager App for LeEco Le 2 & Le Max 2
Credits:
andr68rus - porting Multirom to LeMax 2
Thanks to:
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
deadman96385 - For official TWRP for LeMax2 sources
Rishabh Rao - For sources MultiRom for Le 2, instructions, MultiROMMgr mods.
Martinusbe - For sources MultiRom for OP3
Version Information:
Status: Unofficial, Beta, Version v33b
ENJOY!
XDA:DevDB Information
MultiRom For LeEco LeMax 2 [v33], Tool/Utility for the LeEco Le Max 2
Contributors
andr68rus
Source Code: https://github.com/multirom-leeco/
Version Information
Status: Beta
Current Beta Version: v33
MR-TWRP Version: 3.1.0
Beta Release Date: 2017-05-01
Created 2017-03-04
Last Updated 2017-05-01
reserved
reserved2
reserved3
thanks,any kernel support kexec?
通过我的 Le X820 上的 Tapatalk发言
Nice!
the recovery doesnt work,cant boot into rec just frozen in the recovery screen
通过我的 Le X820 上的 Tapatalk发言
weigeloveu said:
the recovery doesnt work,cant boot into rec just frozen in the recovery screen
通过我的 Le X820 上的 Tapatalk发言
Click to expand...
Click to collapse
I just found its due to the network, it didn't download the
Full
Recovery.
Is there the links to download the rec and multirom?
It can't boot the stock rom.I can't boot into the internal ROM now is there anyway to boot the internal ROM?
weigeloveu said:
thanks,any kernel support kexec
Click to expand...
Click to collapse
It has No-KEXEC workaround.
weigeloveu said:
the recovery doesnt work,cant boot into rec just frozen in the recovery screen
Click to expand...
Click to collapse
Strange - i test it and it work fine.
weigeloveu1 said:
I just found its due to the network, it didn't download the
Full Recovery. Is there the links to download the rec and multirom? It can't boot the stock rom.I can't boot into the internal ROM now is there anyway to boot the internal ROM?
Click to expand...
Click to collapse
I dont understand question. If I understand:
This is binary of recovery and multirom: https://github.com/multirom-x2/multirom-x2.github.io BUT better way to do it by apk provided.
If you have any problem with boot your internal ROM after injecting, than resotre boot from backup that you need to do before install
I will update new build in few minutes, I have fixed bug with touchscreen.
Thanks,the app couldn't download the correct multirom-20170303-v33b-unoffical-x2.zip.
I download twice,one time is 9.68m one time is 4m.
I use stock ROM as primary ROM.Could boot in but just black screen.
weigeloveu1 said:
Thanks,the app couldn't download the correct multirom-20170303-v33b-unoffical-x2.zip.
I download twice,one time is 9.68m one time is 4m.
I use stock ROM as primary ROM.Could boot in but just black screen.
Click to expand...
Click to collapse
It may cause because you try during I upload new ver.
1. Remove from Downloads folder:
Code:
mr-twrp-recovery*
multirom-20170*
2. Start app, check multirom & recovery checkbox and press "install"
App may reload manifest file from server with some delay. Try to press on refresh.
Before install need to make backup of your current rom in twrp and desirable all data. If you internal rom have problem with boot after injecting multirom, just restore from twrp backup boot partition. Also you can use uninstaller
Could your provide the links to download the multirom recovery.IMG and new multirommanger.zip.
I use secondary ROM lineage 13.this ROM don't have root access even if I flashed the addonsu.so I can't use the app now.
Thx for advance
weigeloveu1 said:
Could your provide the links to download the multirom recovery.IMG and new multirommanger.zip.
I use secondary ROM lineage 13.this ROM don't have root access even if I flashed the addonsu.so I can't use the app now.
Click to expand...
Click to collapse
You can get its here: https://github.com/multirom-x2/multirom-x2.github.io
About LOS13: did you try to flash SuperSU.zip?
andr68rus said:
You can get its here: https://github.com/multirom-x2/multirom-x2.github.io
About LOS13: did you try to flash SuperSU.zip?
Click to expand...
Click to collapse
Thx for your help sorry for my bad English
thanks for your efforts @andr68rus !
multirom installed but can't boot primary rom.
blue led flashing, screen flashing (black, on/off).
looks like kernel panic.
i restored "boot" from a twrp backup and the phone booted again.
Gesendet von meinem Le X820 mit Tapatalk
A.N.Droid said:
thanks for your efforts @andr68rus !
multirom installed but can't boot primary rom.
blue led flashing, screen flashing (black, on/off)
looks like kernel panic.
Click to expand...
Click to collapse
What primary rom did you use? It seems to me need inject boot sector.
Try do this:
Boot twrp, multirom menu -> inject boot sector ( I have same issue and it solved it). Please write result.
If Internal (primary) rom does not boot after you install multirom
Boot twrp, multirom menu -> inject boot sector, reboot
If child ROM goes reboot after installation, than try:
Boot twrp, multirom menu -> inject boot.img and choose /sdcard/multirom/roms/....../boot.img , after that it will boot.
andr68rus said:
What primary rom did you use? It seems to me need inject boot sector.
Try do this:
Boot twrp, multirom menu -> inject boot sector ( I have same issue and it solved it). Please write result.
Click to expand...
Click to collapse
i'm using an older build of your rr-m.
injecting boot sector did not solve the issue.
i'm preparing to clean install the latest rr-m build. i will be back in a few hours and report.
Gesendet von meinem Le X820 mit Tapatalk
A.N.Droid said:
i'm using an older build of your rr-m.
injecting boot sector did not solve the issue.
i'm preparing to clean install the latest rr-m build. i will be back in a few hours and report.
Click to expand...
Click to collapse
I use RR-M as Internal ROM, and it work (but I have same issue, and solve it if I does not wrong by injecting boot sector. If you cant solve this problem I will make clean install some later and try from beggining myself.
For NOW I try:
Internal ROM
- RR-M
Child roms:
LOS13
LOS14
MIUI8
But it must work in any ROM.
Can someone install more than one ROM on the internal memory?
{
"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 Note Edge. 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 attached files) 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_tbltexx-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_tbltexx_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.
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. micky387 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/micky387/multirom (branch mr-7.1)
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project (branch android 7.1 mr)
Stock kernel w/ kexec-hardboot patch - https://github.com/micky387/Micky38...r=f1763aec92e75e8faba73801a09d5e896935da4d+69
Lineage 14.1 kernel w/ kexec-hardboot patch - https://github.com/micky387/android_kernel_samsung_tblte_dpc3
XDA:DevDB Information
MultiROM, a Tool/Utility for the Samsung Note Edge
Contributors
micky387 @Tasssadar for your amazing tool
Version Information
Status: experimentale
Created 2017-04-22
Last Updated 2017-04-22
Downloads
1. Main downloads
MultiROM: Zip
Modified recovery (based on TWRP): recovery.img
Kernel with kexec hardboot patch (becareful ,use the borrect kernel for android version): Zip
You need to have kernel with kexec-hardboot patch only in primary ROM
2. 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.
FAQ and other notes
ALL IS IN ATTACHED FILES
**********************************************************************************************************************************************************************
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. 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 share kernel" when installing the secondary ROM, the systems are separated.
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 boot animation shows only the last part on primary ROMs, why?
Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.
too
That's another great project @micky387. You are not letting note edge die. Thanks.. Is there any note7 patched kexec kernel?
SM-N930F
catalyst05 said:
That's another great project @micky387. You are not letting note edge die. Thanks.. Is there any note7 patched kexec kernel?
SM-N930F
Click to expand...
Click to collapse
Note 7 ??
You want say note 7 ported rom right ??
If not,you can flash my samsung MM rom or RR nougatd in primary rom with the good kernel and add your rom in secondary.
Only primary Rom need custom patched kernel.
Or,you canflash my kernel V4 because you need a note edge kernel even with ported Rom
Hi Micky, will we get an update from your MickyRom V3 (last Samsungupdate 26.03.17 security update) for our beloved Note Edge? Only times so asked
audiomarko said:
Hi Micky, will we get an update from your MickyRom V3 (last Samsungupdate 26.03.17 security update) for our beloved Note Edge? Only times so asked
Click to expand...
Click to collapse
Hi man,
Yes ,i have DL the last official FW (N915FYXXS1DQC1)
With this MOD, No need to take my head with wipe and install anything :silly: :good:
Nobody have tested yet ??
Any issue ?? something ?
Hello Micky .... am just trying to test your new kernel ... runs until now very liquid and still energy-saving ... great work
Sent from my SM-N915FY using XDA-Developers Legacy app
audiomarko said:
Hello Micky .... am just trying to test your new kernel ... runs until now very liquid and still energy-saving ... great work
Sent from my SM-N915FY using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks.
I will add Stock V4 later but added last update of F2FS filesystem from original source, add new Zcache,sound control and 2/3 another thing
Any user's report ??
micky387 said:
Thanks.
I will add Stock V4 later but added last update of F2FS filesystem from original source, add new Zcache,sound control and 2/3 another thing
Any user's report ??
Click to expand...
Click to collapse
anticipation [emoji4] [emoji4] [emoji4] [emoji4] [emoji4]
Sent from my SM-N915FY using XDA-Developers Legacy app
@micky387
Thank you for your whole work.
Can I use Multiroom if I formated the SD-card as internal storage?
Gesendet von meinem unknown mit Tapatalk
@micky387 did you see this? I think it's gonna be great
SM-N930F cihazımdan Tapatalk kullanılarak gönderildi
---------- Post added at 11:42 AM ---------- Previous post was at 11:38 AM ----------
MultiROM Without Kexec Hardbooting Ported to OnePlus 2
A well-known MultiROM has been ported to OnePlus 2 by XDA Senior Member MZO. Except MultiROM MZO has released a modified version of TWRP 3.1.0.0. With this using the no-kexec workaround, it allows you to use MultiROM without having to flash a kexec enabled kernel. The stock ROM also works on this MultiROM port so you can have the quality camera like in the stock ROM just a reboot away. All OOS, OOS based, the MIUI port, Nougat 7.1 are compatible. If you’re using OP2, give this solution a try and pick up your ultimate ROM combo.
SM-N930F cihazımdan Tapatalk kullanılarak gönderildi
Ram121 from RamKernel https://forum.xda-developers.com/note-4/orig-development/kernel-ramkernel-t3472138 will be adding kexec to his kernel hopefully for v9
Micky .... Thanks for the new kernel ?????????
Sent from my SM-N915FY using XDA-Developers Legacy app
Hi.
I can flash secondary rom like aokp, ressorection, nobel.
I try to flash racerom ver 8.2 or norma and i get message "can't map... Zip rom name".
I have n915f device.
What the problem?
Thank you
Anybody?
micky387 said:
Hi man,
Yes ,i have DL the last official FW (N915FYXXS1DQC1)
With this MOD, No need to take my head with wipe and install anything :silly: :good:
Nobody have tested yet ??
Any issue ?? something ?
Click to expand...
Click to collapse
I have tried to install Noble Note 7 port as the secondary Rom with your MM Rom as primary with F2FS configured. I believe l have followed the steps and Noble is installed and l can select it at boot. But it just boot loops back into recovery after l select it, any clues?
Further to the above, I have been able to get the secondary Rom to boot and it works. Is there anyway to root the secondary Rom? I have tried SU 2.52, 2.65 and 2.73 system less, any clues.
EDT: Reinstalled rom and update now rooted with Magisk all good.
Sent from my GT-N8010 using Tapatalk
yossim66 said:
Hi.
I can flash secondary rom like aokp, ressorection, nobel.
I try to flash racerom ver 8.2 or norma and i get message "can't map... Zip rom name".
I have n915f device.
What the problem?
Thank you
Click to expand...
Click to collapse
Hi Yossi, had experienced this too. I think it's because of the ram. Primary rom is already using high part of the ram, so it won't runnig the Race rom or Norma rom.. Therefore for the secondary rom most probably only small rom will work such as AOKP, Resurrection Remix, Slim om etc..
ufukan said:
Hi Yossi, had experienced this too. I think it's because of the ram. Primary rom is already using high part of the ram, so it won't runnig the Race rom or Norma rom.. Therefore for the secondary rom most probably only small rom will work such as AOKP, Resurrection Remix, Slim om etc..
Click to expand...
Click to collapse
Thank you for your reply, but when i run aokp rom the amount of ram is the same like the primary rom, no less.