{
"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 OnePlusX. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
-- updated for new bootloader 10/24--
Installation
Download & Flash:
TWRP Modified Recovery: TWRP_multirom_onyx_20161024-01.img
MultiROM Installer: multirom-20161024-v33b-onyx.zip
MultiROM uninstaller: multirom_uninstaller.zip
Patched Kernel: Primary roms Must NOT have a Kexec Hardboot Patched Kernel
Modified recovery (TWRP_multirom_onyx_YYYYMMDD.img) - download the IMG file and use fastboot, TWRP or Flashify app to flash it.
MultiROM (multirom.zip) - download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
-> Installation guide by @Vatsal
Adding ROMs
1. Android
Go to recovery, select -> MultiROM menu -> Add ROM. Select the ROM's zip file and confirm.
Go into mr settings and tick the No-Kexec workaround, to be sure (adb is handy too)
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
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 -> 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 -> 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/MR-op3/android_bootable_recovery (branch mr)
Kernel w/ kexec-hardboot patch - Not needed
Device Tree - https://github.com/MR-op3/device_oneplus_onyx/commits/mr
XDA:DevDB Information
MultiROM, Tool/Utility for the OnePlus X
Contributors
martinusbe, Vatsal, DavyA
Source Code: https://github.com/MR-op3
Version Information
Status: Beta
Created 2016-02-17
Last Updated 2016-10-24
Reserved
Downloads
in OP for now
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Looking forward to this!
Verstuurd vanaf mijn ONE E1003 met Tapatalk
Looks very interesting.
Will this include the ability to install ROMs to SD card in the future since the phone only has 16 GB of internal storage?
Good to see great development on OPX thus far.
I'd like to point out that MultiROM v33 is out now!
Thanks for all the development
Regards.
very cool, i was just looking into that
Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english
IchBinNoob said:
Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english
Click to expand...
Click to collapse
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"
DavyA said:
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"
Click to expand...
Click to collapse
Yeah, thanks I already knew the post, but I want to test it now
Any bug list? or things that needs to improve?
Just curious whether or not you're using MM sources included in the new TWRP with eng.stk's commits. Great work
It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources
finally.. waiting for multirom-enabled kernel for 1+x..
DavyA said:
It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources
Click to expand...
Click to collapse
Does installing secondary and swapping primary-secondary works?
A video demo would be great...
Did anyone actually test this yet?
taaeem said:
Did anyone actually test this yet?
Click to expand...
Click to collapse
Just tried it. When adding a ROM it fails as it requires a MULTIROM binary but besides that it's great.
any news for the Kernel?
I try it. Look cool. For uninstall it I use the Moto G Multirom uninstaller zip. Works pretty good!
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 the LG G2. 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.
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 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 - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d802-UNOFFICIAL.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d802_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.
Click to expand...
Click to collapse
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.
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 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.
Click to expand...
Click to collapse
Source code
https://github.com/multirom-g2
https://gist.github.com/wulsic/dfce9de8983d0a6247350fa2e45c13d4
Thanks to
@Tasssadar
@Eliminater74 - For his previous work on MultiROM for the G3 devices
@nkk71 - For the extra twrp/multirom mods including The kmsg logging options
@z31s1g - For The TWRP Themes (MultiRom)
@Skin1980 - For his previous work on MultiRom and LiveBump
@dadi11 for his modded version of skin1980's script
@blastagator for his TWRP devicetree and base installer zip
@genesixxbf3 && @berryman13 for their previous help on the old multirom
And everyone else I probably forgot.
Click to expand...
Click to collapse
Downloads
Flash Order
MultiRom TWRP
Kexec Hardboot patched kernel (CM-13.0 BASED)
Multirom Installer
Click to expand...
Click to collapse
Downloads
MultiROM Installation Files:D802
Click to expand...
Click to collapse
Attention!
Flashing is at your own risk. You can't blame me if you didn't read everything correctly and or ended up getting softbricked.
Click to expand...
Click to collapse
Release only for D802 yet, Support for all G2 variants incoming soon
Click to expand...
Click to collapse
MultiRom status: it boots the second rom but it will eventually bootloop, could also be that I did something wrong or that I must change some variable still. I am trying to logcat it but can't get logcat to work even after editing ramdisk and last_kmsg is always gone so I gotta think of something for that.
Btw. I don't know how it works with loki and my TWRP MultiRom doesn't have extra temperature control and so on like Blastagators twrp has but I can say it's safe to use as I've used it already for sometime and didn't noticed too high temperatures
If someone has some advice or ideas too then he or she is free to be my guest and reply
Also if someone could acquire an logcat from an secondary rom that's also bootlooping that would be nice.
Files are still uploading
EDIT:
It took a bit longer to upload the files as my computer couldn't handle the my virtual machine anymore
Also Mokee comes to optimizing apps screen but then goes back to the boot animation, so that's an good sign
Thanks for this. I Will definitely try this later.
The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.
Wow! You are an hero!
This was the only regret from my previous nexus device!
jneto3000 said:
The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.
Click to expand...
Click to collapse
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:
Is it stable this version? Or is it as the old multirom?
matteo0026 said:
Is it stable this version? Or is it as the old multirom?
Click to expand...
Click to collapse
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low
wulsic said:
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low
Click to expand...
Click to collapse
Thanks! My dream is that i can edit all the partitions size that i can use all the space at the better. (now i can only use adb and edit it with shell)
wulsic said:
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:
Click to expand...
Click to collapse
I did as mentioned by you in the OP:
1. MultiROM TWRP
2. Kexec kernel
3. MultiROM zip
Then I reboot recovery and went to MultiROM option to install a secondary ROM, using Krexus and then XOSP. It says the ROM is installed fine but when I reboot device It boots up directly to primary ROM (which is crDroid).
What am I doing wrong?
I guess this topic would have more attention if it were in Android Development section, people might see this MultiROM topic and think this is the same old topic that already exists and is not working anymore.
Also, about the logcat not working, the only thing I know is about enabling adb on ramdisk, which I did here using Android Image Kitchen (the one you posted is not enabled yet) and replaced boot.img by the new one, but I couldn't test since the MultiROM did not work here yet.
I'm very excited about this multirom. The fact is that if anything goes wrong I might lose something. I still use the g2 as primary phone.
Soon or later I'll try also this mod.
Thanks @op for the effort.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-yuga.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-yuga.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
OPTIONAL: Reflash the kernel patcher to add kexec support
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)
MultiROM available for Yuga also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC
XDA:DevDB Information
MultiROM for Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned
Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-yuga.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-yuga.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Yuga due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Yuga release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.
awesome work bro! Can't wait to test. Ill report you very soon! :good:
Nice to see someone taking over. I'll close my thread.
Sent from my Sony Xperia Z3+ using XDA Labs
Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..
itsnie said:
Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..
Click to expand...
Click to collapse
Please read OP again. Especially about "no-kexec workaround".
i installed both zip file.but recovery hasnt multirom option in andvanced!!!
Thank you a lot, I'll try it later!
The basketbuild site isn't working,they are doing recovery,
Would you please upload the files to another server?
Sent from my C6603 using Tapatalk
Does anyone know if there is multirom development on the xperia z5 e6653? I got it working on and of, but there are more breakdowns than anything else. This results in having to frequently reinstall the original boot.img and restart from scratch. Any help is appreciated. Thx
Sent from my E6653 using XDA-Developers mobile app
i have installed in xperia z and flash cm13 in sd card.. on multirom i have seleceted CM13 but still booting in to primary
---------- Post added at 08:34 AM ---------- Previous post was at 07:44 AM ----------
multirom worked using ressurection remix and cm 14 thank u.....
I tried -
PureX Z Premium v3.0
X rom ( 5.1)
Xperia_Z_eXistenZ_Premium
ResurrectionRemix-N-v5.8.0
almost all stock based ,But non of them works and gives error during flashing..
Only
ResurrectionRemix-M-v5.7.4
Omni rom , are working fine ...
Any help how to use sony stock roms or others ?
Chippa_a said:
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
Click to expand...
Click to collapse
Did not help... the setting is unchecked by default.
Charging on a Wallcharger works, pluging the phone to the computer doesn't show anywhing.
Falshing the Recovery only still worked fine, but after flashing the MultiROM zip the phone doesn't budge when connected to the Computer.
Syslog attached.
The MultiROM menu is not under Advanced such as v32 rather the icon upper right - pic 1.
RR N 7.1.1 as second Rom failed, ERROR 7 @ RR M 6.0.1 - pic 2.
My oldest backup Omnirom 4.4.4 as sec Rom was successfully - pic 3.
#Edit: Additional compatible secondary ROMs::
-XOSP M [6.0.1] [Unofficial] [Release 6] 6.3 [Revision 3] [2016/08/03]
-AOSP M [6.0.1] [FINAL] [OMS/Substratum] [Updated 31-10-2016]
The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?
MichaBit said:
The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?
Click to expand...
Click to collapse
You need newer twrp recovery for newer roms
langeveld024 said:
You need newer twrp recovery for newer roms
Click to expand...
Click to collapse
There was und is always the newest One installed. :angel:
MichaBit said:
There was und is always the newest One installed. :angel:
Click to expand...
Click to collapse
Alright but error 7 ALWAYS means wrong recovery
langeveld024 said:
Alright but error 7 ALWAYS means wrong recovery
Click to expand...
Click to collapse
Oh, Im currently desiring LEOs 3.1.1, so I will give Nailyk a drink.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-dogo.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-dogo.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
OPTIONAL: Reflash the kernel patcher to add kexec support
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)
MultiROM available for Dogo also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC
XDA:DevDB Information
MultiROM for Xperia ZR, Tool/Utility for the Sony Xperia ZR
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned
Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-dogo.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-dogo.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Dogo due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.
How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/show...26&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Dogo release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.
I installed it every thing is working but can't boot to the secondary rom when I choose it the phone just restarts the primary rom works without any problem I used CM 14.1 as secondary
did its work on xperia zr.? can i used on Locked Bootloader.?
Hey chippa.. can you release multi boot for this device compatible on lineage 14.1 and Lineage 15.
{
"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 Galaxy A5. 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 Galaxy A5
* 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) Flash Modified TWRP with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature
2) Flash MultiROM zip in TWRP
3) enjoy
MultiROM has 3 parts you need to install:
Modified recovery Download the Modified TWRP for MultiROM
Patched kernel *OPTIONAL* : Not Needed
MultiROM download the ZIP file from second post and flash it in recovery.
Downloads:
Modified TWRP for MultiROM: https://www.androidfilehost.com/?w=files&flid=110082 Since the recovery image was too big for recovery partition, I used LZMA compression instead of LZO for the kernel, which saved about 3 MB
MultiROM: https://www.androidfilehost.com/?w=files&flid=110089
MultiROM Uninstaller: https://www.androidfilehost.com/?w=files&flid=110117
If you get force closes on secondary nougat ROMs:
Flash the rom, open /sdcard/multirom/roms/rom_name/system/build.prop on primary, or on TWRP with "vi" editor
and change:
Code:
ro.sys.sdcardfs=true
to
Code:
#ro.sys.sdcardfs=true
Then reboot.
DO NOT reboot the rom before changing build.prop line otherwise you will still get force closes!
You current rom will not be erased by the installation.
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings
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 boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject 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.
How does Kexec workaround works
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx branch cm-13.0-mrom
Kernel w/ kexec-hardboot patch: NOT NEEDED
Credits
A big thanks for:
@nkk71 For kexec workaround and for helped me in IRC
@Tasssadar For MultiRom Source Code
That made this possible
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
Click to expand...
Click to collapse
XDA:DevDB Information
MultiROM for Galaxy A5 (SM-A500), Tool/Utility for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-09-10
Created 2016-09-10
Last Updated 2016-09-10
Reserved
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
-CALIBAN666- said:
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
Click to expand...
Click to collapse
He he thanks
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
-CALIBAN666- said:
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
Click to expand...
Click to collapse
No, it will br untouched, but a backup waste only 5 times, at massimum, so, if you have some free space make a backup, but as I said, it will be untouched
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
supertiger1234 said:
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
Click to expand...
Click to collapse
Sure
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Edit: I'll choose your PacRom ;D
supertiger1234 said:
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Click to expand...
Click to collapse
CM is pure android, rr has lots of feature regarding the personalization, so, if you want a rom wich is pure android, get the cyanogenmod, otherwise, if you like to personalize your android get the resurrection remix. Oh you installed multirom, so you can install both of them (you can install more than 2 roms) and decide which one is better for you
EDIT: if you use pac-rom you have to move this as primary, because it has a bug that won't boot if you set it as secondary
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Edit: when i choose rr from the list, the device just reboots to multirom menu. hmm
supertiger1234 said:
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Click to expand...
Click to collapse
Not, try to reboot to recovery and then reflash
DeadSquirrel01 said:
Not, try to reboot to recovery and then reflash
Click to expand...
Click to collapse
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Mmm, maybe i have to remove preload from the fstab. Now i'll do and notify once it's done
Works on my A500M with Stock 6.0.1 and CyanogenMod 13, thank you very much for port this mod to Galaxy A5
supertiger1234 said:
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Click to expand...
Click to collapse
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
DeadSquirrel01 said:
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
Click to expand...
Click to collapse
Hmm, The errors fixed buut now when I choose my second rom, it reboots to multirom menu xD
The non-kecex link doesn't work. Is there something important there?
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
DeadSquirrel01 said:
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
Click to expand...
Click to collapse
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
supertiger1234 said:
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
Click to expand...
Click to collapse
Well, it's a problem of the zip of the ROM. move it as primary or wait until I create a working installer
EDIT: maybe try with this installer https://www.androidfilehost.com/?w=file-thanks&fid=24591020540824243&mid=71&download_id=vlofv1jeu8k8ubpcpd375ql164&tid=1473585621&hc=c6de356c2e1c646fcb44f52216b36595df13152b92265bbb693814053fe5ca85
{
"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 kenzo/kateSupports all Roms (SHOULD)
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 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 Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
kenzo
kate
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
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 (Links Below)
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.
Download link is in the second post.
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 Xiaomi DevicesKenzo/Kate MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For kenzo/kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30
1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
Download Links:
MultiRom Manager App 2.4-rishabhrao
Guys please test this in your Kenzo/Kate and Please tell me how it works
Will it work on 16 gb
pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs
Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc
Does it support the sailfish os?
Is f2fs supported?
Because I can't inject current boot sector
Anyone know if MIUI works?
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs
午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !
Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...
SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Doesn't seem it is able to install roms to the sd card
4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...
SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links
[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post