Introduction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus One. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
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.
You can install it either from MultiROM Manager app or from this guide:
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 - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so 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.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/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/KINGbabasula/android_kernel_oneplus_msm8974
MultiROM device tree - https://github.com/KINGbabasula/android_device_oneplus_bacon
Thanks a lot to Tasssadar for creating this awesome utility.
Thanks to ATMOSF3AR for his Oneplus One template
XDA:DevDB Information
MultiROM, Tool/Utility for the OnePlus One
Contributors
KINGbabasula
Source Code: https://github.com/Tasssadar/multirom
Version Information
Status: Stable
Current Stable Version: 33
Created 2014-08-02
Last Updated 2016-04-17
Reserved
Downloads
1. Main downloads
MultiROM: Zip
Modified recovery (based on TWRP): recovery.img
Kernel with kexec hardboot patch:
Supported kernels: AK, Furnace
You need to have kernel with kexec-hardboot patch only in primary ROM
Nicely ask your kernel developer to merge this https://github.com/KINGbabasula/and...mmit/af5ef3d76f863f02c51cf860702b01536620ebf5.
3. 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.
Reserved
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
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.
Where can I find files from other ROMs?
http://forum.xda-developers.com/showpost.php?p=58563378&postcount=1864
Can I have different versions of Android working alongside? How to use KitKat and Lollipop at the same time?
Yes. The systems are separated.
guide on Kitakt + Lollipop: http://forum.xda-developers.com/one...ips-tricks-t3027926/post58776196#post58776196
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 after a few seconds on primary ROMs, why?
Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.
Can I use MultiROM without root?
Yes, if you don't use MultiROM Manager app but flash everything manually
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?
Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs
My secondary ROM doesn't boot, what should I do?
Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again
Help Videos
Install MultiROM
Install OxygenOS as secondary ROM
Amazing, thank you bro!
Amazing! Reserved for impressions!
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Edit : Donation done : 2D0766769R4457313
bud77 said:
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Click to expand...
Click to collapse
My kernel is cm11 (not cm11s)with kexec. So it won't work on cm11s, Paranoid android and cm11s based roms.
Tomorrow is the last time I'll use pc before leaving so I may add support in multirom manager and build an unofficial version of the app because it's not officially supported
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
bud77 said:
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
Click to expand...
Click to collapse
I tried on hangouts but I guess he doesn't use it. I think I should port a few things from TWRP into MultiROM because it seems they use the same way of rendering images.
Thank you very much for your efforts,
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
dansou901 said:
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
Click to expand...
Click to collapse
First we need a working ubuntu touch port. I don't think it will be too hard to do. The opo is very similar to nexus 5
nfl46 said:
Anyone got everything up and running yet? Attempting to install MR now.
Click to expand...
Click to collapse
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
Click to expand...
Click to collapse
That's because you need a kernel with kexec hardboot patch in secondary rom too. So you need a special kernel for color os and a special one for miui. You may try instlling the rom choosing "share kernel" option so it will use main rom kernel which has kexec
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
Click to expand...
Click to collapse
WHAT! I have black screen :|
KINGbabasula said:
WHAT! I have black screen :|
Click to expand...
Click to collapse
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
dansou901 said:
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
Click to expand...
Click to collapse
Surely I have something wrong in the kernel. Thanks for telling me that
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
dansou901 said:
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
Click to expand...
Click to collapse
Well that's expected because they use different kernels. The solution is to compile miui kernel with kexec patch and color os kernel with kexec patch. I tried only cm based roms. I'm on cm11 and I can boot slim and mahdi sharing kernel
OK, so we have to find kernel sources from Color OS and MIUI for this to work...
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?
TLDR:
This project is no longer actively maintained, see explanation here.
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
3: Any issues: please report at https://github.com/multirom-nexus6p/multirom/issues I won't be reading this thread very often.
{
"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
This is a port of Tassadar's MultiROM, a multi-boot mod for Nexus 6P. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still very experimental!
This has been thoroughly tested with the most popular ROM's for the 6P.
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
We have a custom built MultiROM Manager .apk in the downloads section, feel free to try it! (somewhat untested, please report, even if install doesn't work, ROM name customization, etc. should work fine)
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app found in the next post, 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.
Accept any Super User request prompts.
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_angler_YYYYMMDD.img) - download the IMG file from second post and use fastboot 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.
MultiROM (multirom-YYYYMMDD-vXX-angler.zip) - download the ZIP file from second post and flash it in recovery.
Your current rom will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select 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.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/multirom-nexus6p/multirom/tree/master (branch master)
Modified TWRP - https://github.com/multirom-nexus6p/Team-Win-Recovery-Project (branch android-6.0) -- Includes the awesome new Material Dark TWRP theme by @daveyannihilation ! Go thank him, or get his Blackout Domination Layers or CMTE (yes, there are free versions on the Play Store, but you can find those yourself, or donate to a hard worker ).
Kernel w/ kexec-hardboot patch - https://github.com/multirom-nexus6p/android_kernel_huawei_angler/tree/mm -- use angler_defconfig
Device tree: https://github.com/multirom-nexus6p/TWRP-android_device_huawei_angler/tree/android-6.0-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it on the specific repo in question here.
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -Rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Please report any unlisted issues to the GitHub bug tracker at https://github.com/multirom-nexus6p/multirom/issues . You'll get faster response if you post there instead of in this thread
Changelog
Here
Downloads
Downloads
v33 -- Stable 7:
MR Installer App: Play Store Link
MR-TWRP: mr-twrp-recovery-20160528-05-STABLE7.img
MultiROM Installer Flashable ZIP: multirom-20160514-v33-UNOFFICIAL-angler-STABLE7.zip
Stock HardBoot Enabled Kernel Flashable ZIP (only your Primary ROM needs this): kernel-hardboot-stock-angler-6.0.1-20160514
MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM):
ElementalX
FrancoKernel
AK
PureNexus
(Alert me if I've missed any!)
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
Also, due to recent events on other projects of mine, you are welcome to fork our Github repositories, and use them to port MR to new devices, and as a reference, but, I ask that no one build targeting the 6P using our source and post it publicly (of course you can build for personal use, but distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!
The only acceptable releases based on our source for the 6P is recovery/multirom themes, though, I strongly ask you tag me so I can note the themed version in the OP.
XDA:DevDB Information
MultiROM for Nexus 6P, Tool/Utility for the Huawei Nexus 6P
Contributors
npjohnson, 500 Internal Server Error
Source Code: https://github.com/multirom-nexus6p/
Version Information
Status: No Longer Updated
Current Stable Version: v33-05282016-STABLE7
Stable Release Date: 2016-05-28
Created 2016-02-12
Last Updated 2017-09-17
[MOD] MultiROM v33 -- Beta 4
Reserved
Reserved.
Reserved.
Reserved
Downloads
Reserved.
changelog
Reserved.
Extra information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful.
Just a heads up, your
Spoiler
tags didn't work, you will probably want to use [hide] instead. Looks promising though!
@daveyannihilation here you go, jump on it lol.
thanks that works
Oh awesome! Subscribed and will install as soon as I get off work. Thank you for your hard work @500 Internal Server Error
#whiteuimustdie #themesmatter
Yeahhhhhhhhhhhhh!! Finally. Very happy to see this
Sent from my Nexus 6P using Tapatalk
Nice work! Can't wait to try it out.
Definitely needed! Super!!
500 Internal Server Error said:
v33 beta 1:
Recovery: https://multirom-nexus6p.github.io/recovery-20160211.img
MultiROM Installer: https://multirom-nexus6p.github.io/multirom-20160211-v33-UNOFFICIAL-angler.zip
Patched kernel: only the primary ROM needs this. Secondary ROM's kernels do not need patching.
Stock 6.0.1 kernel: https://multirom-nexus6p.github.io/kernel-hardboot-stock-angler-6.0.1-20160211.zip
Click to expand...
Click to collapse
Congrats on this man! The Hardboot Patch will be indefinitely helpful for ARM64 users in the future!
No noticable bugs so far. I'm going to build MR with USB support sometime this weekend, will test, and get back to you.
Something we are going to have to deal with that other devices won't is the /vendor partition on the 6P. For example, user install Layers Overlay on stock ROM, now CM based secondary won't boot due to conflicting Layers/CM theme. Th8s wasn't a problem on the Nexus 6 because it didn't have a /vendor, but simply had a /system/vendor for each ROM.
A simple way we could bypass this is to set up a virtual /vendor (like we already have for /boot) and give the option when making the ROM to use a virtual /vendor, and then if the user opts to do so, they could base it off a vendor.IMG, or their current /vendor. If this doesn't sound like something you'd want to do, we could also tell the secondary ROMs to look at /system/vendor, and not ever mount /vendor (though this'd require that MR inject the current /vendor partition contents into /system/vendor on Secondary ROM flash.
Could you make a separate thread in the Original-Development about the HardBoot patch, and irlts inner workings? Tasssdar made a thread like that for the Nexus 6, and it helped a lot of kernel devs get up to speed quickly. It also contained example commands, etc. and was a great place for Kexec newcomers to learn.
Again, Congrats!
And finally its here! Glad you dealt with kexec-hardboot
npjohnson said:
A simple way we could bypass this is to set up a virtual /vendor (like we already have for /boot) and give the option when making the ROM to use a virtual /vendor
Click to expand...
Click to collapse
This should be doable - I can look at how MultiROM mounts the system partition and try to do the same for vendor. However, I'm not sure if there is a need for that since CyanogenMod didn't ship with any custom vendor binaries. I'll look into it when a ROM actually needs it.
Could you make a separate thread in the Original-Development about the HardBoot patch, and irlts inner workings?
Click to expand...
Click to collapse
Sure: I'll post a guide on porting it to other devices. The TLDR version:
- It's based on Geoff Levand's arm64 kexec patch as adapted by webgeek1234 to build on Android
- the hardboot part works by:
kexec call is made to load kernel, ramdisk, and device tree at specified addresses
kernel makes a temporary copy of this data in RAM that won't be overwritten at reboot, along with some code to copy it to the final positions
kernel reboots
Hardboot kernel checks that a hardboot is required, and jumps to the copier code
Copier code copies the new kernel to the final address and jumps to it
New kernel boots.
The extra copying code is needed since on 32-bit ARM the kernel can copy itself to the desired position; on arm64 it can't and extra code is needed. In addition, on 32-bit ARM the position of the ramdisk and device tree doesn't seem to matter; on the Nexus 6P however they have to be placed at the same location that the real bootloader uses.
Omg. Amazing. The only thing i am missing on the 6P. You are the men! Thank you so much.
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Great work!
Sent from my Nexus 5X using Tapatalk
{
"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
This is a port of Tassadar's MultiROM, a multi-boot mod for Moto X Pure/Style. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still very experimental!
I've only tested this with stock M as the primary ROM and AICP M as the secondary ROM
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
The MultiROM Manager app does not currently support the Moto X Pure Edition
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_clark_YYYYMMDD.img) - download the IMG file from second post and use fastboot 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.
MultiROM (multirom-YYYYMMDD-vXX-clark.zip) - download the ZIP file from second post and flash it in recovery.
Your current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
Untested on clark
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.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/Hashbang173/multirom/tree/master
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
kexec-hardboot patch - https://github.com/AICP/kernel_motorola_msm8992/compare/41e44cc5e5...a6959bcd07
Device tree: https://github.com/MotoX-2015/android_device_moto_clark/tree/android-6.0-mrom
Thanks
This port is based on the hard work of Tassadar, Geoff Levand, webgeek1234, Mike Kasick, 500 Internal Server Error, and many others. Thank you.
Issues
* Does not yet support encrypted devices
* Please report
XDA:DevDB Information
MultiROM for Moto X Pure Edition/Style, ROM for the Moto X Style (Pure)
Contributors
Hashbang173
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-02-14
Last Updated 2016-02-14
Downloads
multirom-20160214-v33-UNOFFICIAL-clark.zip
TWRP_multirom_clark_20160214.img
Stock M patched kernel
MultiROM uninstaller
List of ROMs/Kernels with kexec hardboot baked in
These ROMs/Kernels can be used as the primary ROM without any modifcation
AICP (starting from 2/15/16 build)
Other CM based ROMs depending if they are upstream to the AICP kernel
Frankenclark in the next release?
One more
#First
Second
Very interesting. Thanks!
@Hashbang173 the way u r doing great things for mx style, we should rename the phone as moto x hashbang edition.. Thanks for great wrk
Thanks @Hashbang173 for the awesome work!
Seems to work great!!! If I install or delete an app from the second rom will the change remain after a reboot?
guraki said:
Seems to work great!!! If I install or delete an app from the second rom will the change remain after a reboot?
Click to expand...
Click to collapse
Why wouldn't it?
OK thanks!!! The only problem I have is that moto display doesn't work in Stock rom ...
guraki said:
OK thanks!!! The only problem I have is that moto display doesn't work in Stock rom ...
Click to expand...
Click to collapse
Hmm, I guess that could be a problem with my patched kernel. Have you tried toggling moto display on and off?
Yes I did..!
@Hashbang173 multi rom this was the only thing remaining
thanks dude for your hard work
Interesting I couldn't get TruPureX to be my secondary rom not sure if I did something wrong
Sent from my XT1575 using XDA Labs
Flashed TWRP-MultiRom, pached Kernel and MultiRom on Dual Sim XT1572.
Primary ROM ( Stock Marshmallow) is working fine. Wifi is not working.
On Secondary ROM , flashed AICP 15/2/2016 build with gapps and did a reboot.
After Reboot, Secondary ROM is stuck in the installation process with AICP boot animation even after 15-20mins... Any solutons? (btw Phone is hot as hell, it has never been this hot)
Wow, I didn't expect to see this on the MXP, now all we need is ports of arm GNU/linux and it'll be just like the Nexus 7 (2012) days.
iNik123 said:
Flashed TWRP-MultiRom, pached Kernel and MultiRom on Dual Sim XT1572.
Primary ROM ( Stock Marshmallow) is working fine.
On Secondary ROM , flashed AICP 15/2/2016 build with gapps and did a reboot.
After Reboot, Secondary ROM is stuck in the installation process with AICP boot animation even after 15-20mins... Any solutons? (btw Phone is hot as hell, it has never been this hot)
Click to expand...
Click to collapse
Try to reinstall the patched kernel!Did the moto display worked for you on stock rom?
---------- Post added at 11:58 AM ---------- Previous post was at 11:31 AM ----------
Moreover after using the second rom and then rebboting to the stock one the WIFI cant be enabled.....
guraki said:
Try to reinstall the patched kernel!Did the moto display worked for you on stock rom?
---------- Post added at 11:58 AM ---------- Previous post was at 11:31 AM ----------
Moreover after using the second rom and then rebboting to the stock one the WIFI cant be enabled.....
Click to expand...
Click to collapse
I Tried to reinstall the patched kernel, did not work. I have disabled all moto apps for battery purposes, cant help you with Moto Display bro.
btw I too have the WIFI problem.
Now Went back to stock kernel and everything is fine.
Noob question, How do we get frankenclark kernel to work with the patched kernel ? does flashing one after another 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"
}
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.