Related
-NOTE: The following guide has been specifically written for LG P-880 (Optimus 4X HD), after a lot of reading, flashing and managing ROMs and kernels on MultiROM; I have been asked by some users, and now it's here, I hope it to be clear and useful; it includes some parts extracted from the original Nexus7 thread, and readapted for our device. For the original MultiROM thread by @Tasssadar, go at the link below:
http://forum.xda-developers.com/showthread.php?t=2457063
MultiROM is one-of-a-kind multi-boot mod, originally built for Nexus 7 by @Tasssadar, ported and re-adapted to work with LG P-880 by @Adam77Root, then by @Fluoxetine, and finally by Mourta @IcanhasLG (coming soon, don't ask for ETA's, please). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to our device. 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 modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, or restore nandroid backups as secondary ROMs, too.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
1) INSTALLATION
MultiROM has 3 parts you need to install:
* MultiROM.zip (A new version built by Mourta @IcanhasLG will come soon; actually, the latest MultiROM.zip by @Fluoxetine can be found here: https://app.box.com/s/fmigiyd8nsprc8jxwahn) - download the ZIP file and flash it in recovery.
* Modified TWRP recovery (the actual modified recovery is the one provided by @Adam77Root - go here for Adam's modified TWRP thread and for download links: http://forum.xda-developers.com/showthread.php?p=46431004). Download the latest IMG file and use terminal emulator to flash it (the easier way to flash it without a PC). Please, follow the steps below for a safe flash:
-Rename the IMG file into "recovery.img"
-Open terminal emulator
-Type "su", then enter
-Type "cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1", then enter
-Type "sync", then enter
-Type "exit", then enter
-Reboot your phone
* Kexec-hardboot patched kernel - You can use iodak (patched since from v8), Mourta, or Cyodak. Download the ZIP file and flash it in recovery.
IMPORTANT: You current rom will NOT be erased by the installation.
2) ADDING ROMs:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choice if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option; if you don't, select the "don't share" option. The sharing mode is helpful if you need to use an anykernel kernel with a secondary ROM (see step 2.1) or just to share the Internal ROM's kernel with secondaries, if you need it.
* Select the ROM's zip file you want to flash, or the nandoid backup file you want to restore as a secondary ROM, and confirm.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
2.1) USING ANYKERNEL PATCHED KERNELS WITH SECONDARY ROMs
Actually, MultiROM doesn't support direct flashing of anykernel patched kernels on the top of secondary ROMs. There are some workarounds to let secondary ROMs use this kind of kernels:
a. Share the kernel with internal ROM:
If you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM, you will be able to share it with secondary ROMs too. If you did it, just follow the steps below, when adding a new secondary ROM:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choose if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option.
b. Remove original boot.img from secondary ROM:
If you flashed a secondary ROM without selecting the "Share kernel with internal ROM" option, but you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM before, you can share it with secondary ROM following the steps below:
* In recovery, Advanced -> MultiROM -> List ROMs -> "Your rom's name", there is a button: "Remove boot.img". This action switches ROM to "share kernel" mode. Flashing a ZIP which contains kernel (even ROM update!) into that secondary ROM could put it into "don't share" mode again.
* After removing the original boot.img, you will see a new "Inject boot.img" button replacing the old "Remove boot.img" one: this option allows you to inject your secondary ROM with a different boot.img, backed up from other kernels you flashed before on the top of other ROMs, or backed up directly from other ROMs. Do this at your own risk, it may cause bugs or not, depending by your knowledge of what you are going to inject here.
At any rate, I personally tried the a. step above, and after that I tried to flash a ROM's zip update: the "share kernel" mode hasn't been turned off.
3) UPDATING/CHANGING ROMs
a. Primary ROM (Internal)
* Wipe /cache, /dalvik, /system, or do factory reset if needed (it won't erase secondary ROMs)
* Flash ROM's ZIP file as usual
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: if you want secondary ROMs to properly boot, you should flash only kexec-hardboot patched kernels, on the top of Internal ROM. Flashing a no-patched kernel won't allow MultiROM to manage secondary ROMs' boot).
* After erasing /system partition, or flashing a new kernel, a "bug" could happen: the menu with all the ROMs won't show up during boot.
If so, re-flash the MultiROM zip after having flashed the ROM update and the other related stuff, 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.
b. Secondary Android ROMs
If you want to change a ROM, select it in Advanced -> MultiROM -> List ROMs, delete it using the "Delete" button, then add the new one (following the instructions explained in step 2). To update ROM, follow these steps:
* Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
* Wipe /cache, /dalvik, and so on, by pressing the proper button showed on the screen
* Select "Flash ZIP" and flash ROM's ZIP file.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
4) ERASING SECONDARY ROMs
* Just go to Advanced -> MultiROM -> List ROMs and select the ROM you want to delete.
* Select "Delete"
5) BOOTING SECONDARY ROMs
* Turn on the phone; after the LG logo, the MultiROM boot menu will appear. If you don't do anything, Internal ROM will boot. If you want to boot into secondary ROMs, you have to tap on the countdown pop-up
* After that, you can choose your desired ROM, then press "Boot". For secondary ROMs which don't share kernel with internal ROM: press "Boot" and hold down the power button until phone vibrates (actually, our MultiROM has a bug which doesn't allow secondary ROMs to boot, if you don't hold power button after having tapped "Boot", if you haven't shared kernel with internal ROM.)
6) UNINSTALLING MultiROM
The easiest way is to just reflash your custom kernel or a ROM zip on the top of your internal ROM, after having made the usual wipes: this will erase the MultiROM binaries.
More updates will come when we'll have a new version, such as for swapping ROMs through internal and secondary positions, making the internal ROM secondary, and so on (these features don't work fine, at the moment).
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img will be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi to get them work in MR...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager, press "Boot" and hold down the power button until phone vibrates. Your device should reboot to the chosen ROM...
Most of the ROMs I've tried as secondary are working flawlessly in MR... Only MoKee have made some Problems...
Fladder72 said:
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img wil be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager and press "Boot", you have to hold down the power button until phone vibrates. Most of the ROMs I've tried as secondary are working flawlessly in MR...
Click to expand...
Click to collapse
Yep, what you're saying is right, nobody affirmed the contrary
Right, I've forgotten the more banal thing: the necessity of holding down power button, while booting a secondary ROM I'm adding it into the guide right now
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Fladder72 said:
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Click to expand...
Click to collapse
Yep, I knew that too, I've already written that in last update Thank you for having helped me remembering those things! You know, sometimes those steps begin automatic, while using this mod, so you don't remember them as a necessary thing to explain, my bad!
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Fladder72 said:
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Click to expand...
Click to collapse
Yep, it's right, I never understood the reason for that..probably it has something to do with some commits, not rightly ported for our device, or not easily portable
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Vanir 4.4.4 runs like hell... Realy fast with Vanir stock kernel, an a bit faster with Mourta's... For me the fastes KK-Rom at this momemt. :good:
Maybe next I'll give Beanstalk a try...
I use only Ext4, because I don't like f2fs... Too much early stage sh*t...
I'm not shure, but I think, Vanir is CM based...
dimi89 said:
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Click to expand...
Click to collapse
Thank you! You must use modified TWRP built by Adam, as said in OP, it's the only recovery built to work with MultiROM binaries
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
@gerciolisz Ahahahah, wt*? XD
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
gerciolisz said:
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
Click to expand...
Click to collapse
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
peppethustra said:
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
Click to expand...
Click to collapse
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
gerciolisz said:
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
Click to expand...
Click to collapse
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
peppethustra said:
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
Click to expand...
Click to collapse
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Donar81 said:
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
Click to expand...
Click to collapse
gerciolisz said:
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Click to expand...
Click to collapse
I have variant3, and I've not the problem.. Yes, maybe it's better to ask him..What do you think, @IcanhasLG?
I have variant 0 and got no problems. I can boot scondaries with Moutras kernel...
---------- Post added at 11:46 AM ---------- Previous post was at 11:30 AM ----------
gerciolisz said:
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
Click to expand...
Click to collapse
Remove the boot.img in recovery/Multirom/Manage ROMs/YourSecondary. Now your primary will share the Kernel with your scondary. Can you boot now primary and secondary without any issue?
{
"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"
}
[/CENTER]
Introduction
MultiROM is one-of-a-kind multi-boot mod for Redmi note 3. 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 the redmi note 3
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (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 (Not for Moto X Play) 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 (If you want to use Kexec) - 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_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - 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. we dont need patch kernel with the no kexec workaround
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 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 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.
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.
XDA:DevDB Information
[MOD][MultiROM][v33][Beta 1][kenzo], Tool/Utility for the Xiaomi Redmi Note 3
Contributors
zeeshanhussain12
Source Code: https://github.com/multirom-nexus6p
Version Information
Status: Beta
Beta Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2016-06-15
Reserved
DOWNLOADS
1. Main Downloads
Multirom :- multirom-20160615-v33-UNOFFICIAL-kenzo.zip
Multirom recovery:- recovery.img
2. third-party kernels with kexec-hardboot patch
no need with kexec workaround
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's
1. Should I flash recovery only via Flashify app?
-Not essentially, You can flash it via recovery.
Boot to TWRP.
Install->Tap on Images(bottom right screen)>Locate and select your recovery.img
Flash to 'Recovery' partition.
Reboot back to TWRP(IMPORTANT).
2.Can I flash any other kernels?
-yes you can flash any roms
3.Which roms can I flash?
-All Android 5.1+ roms can be flashed without any issues.
miui is not supported
4.How to flash without Hardbricking?
-Follow the steps from OP and there are videos to make the things easy in initial pages.
Maximum it causes bootloops(softbrick), not hardbrick if you follow the guide.
5.Can I flash roms to ext-sd card and USB-otg? How?
-Yes you can flash them to ext-sd card and USB-otg.
Boot to TWRP.
Tap on Multirom.
Tap on ADD ROM
Select the right Location
Flashing on ext-sd and USB otg takes some time, so be patient, don't freak out!
sd1 = usb otg
mmcblklpa = sd card
6.Where to find roms installed in my ext-sd and USB? How to boot into 'em?
-After flashing you'll be booted into MultiROM menu.
All your roms flashed on internal memory will be in Internal tab.
Others will be in External tab.
7.How to rename/remove/delete/wipe dalvik & cache or flash any other zips to existing rom?
-Follow
Boot to recovery.
Tap on MultROM
Tap on the rom which you want to remove/add zips.
You'll find all the options you need!
9."Unable to flash, I'm getting errors" / "Executing updater script failed" / "Rom is not booting" ????
-Please provide logs. It'll be located in /data/media/0/multirom/last_kexec. log
It'd great if you can provide the screenshots.
Press VOL DOWN + LOCK KEY to take Screenshots.
10.How to disable auto boot / change rom name / hide roms / brightness of Multirom menu?
-Follow
Boot to recovery.
Tap on MultiROM.
Tap on 3 dots on top right of screen.
Select settings.
Here you find all the customisations for MultiROM menu.
BUGS
- Miui is not supported
Credits @nkk71 for his no kexec workaround @Abhishek from yu forums @TheStrix for cm
NOTE :- All the devs are requested to help in improving this project as it is still in beta stage
Reserved for future....who knows what crazy post will be made here
Good job @zeeshanhussain12
VIDEO GUIDE (SOON WILL BE KENZO SPECIFIC)
Awesome.... Thank you
Sent from my SHIELD Tablet using XDA-Developers mobile app
yes,it looks so good
Sent from my Hol-U19 using XDA-Developers mobile app
Shahan_mik3 said:
Reserved for future....who knows what crazy post will be made here[emoji14]
Good job @zeeshanhussain12
Click to expand...
Click to collapse
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Sent from my Redmi Note 3 using XDA-Developers mobile app
Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...
This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?
nice to see you here buddy @zeeshanhussain12.
ayush321 said:
Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...
Click to expand...
Click to collapse
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk
Filip013 said:
This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?
Click to expand...
Click to collapse
miui gives error while flashing as secondary. i have not tried Xiaomi.EU roms. i have ported DualBootPatcher too i have it in my drive . it doesn't work well with sd 650 as qcom changed base directory in mm and lp. the current problem is with dtb nearly every rom is using different source which have different dtb, it is causing problems. we just have to wait for one official source or use the roms which is built with same trees
zeeshanhussain12 said:
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Can you tell me which roms are currently working with multiROM...
Reserved
Waiting for miui support
Sent from my Redmi Note 3 using XDA-Developers mobile app
Hadi al-Haiqal said:
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Click to expand...
Click to collapse
Haha Eos was the best and can't be replaced
zeeshanhussain12 said:
[/CENTER]
Introduction
MultiROM is one-of-a-kind multi-boot mod for Redmi note 3. 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 the redmi note 3
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (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 (Not for Moto X Play) 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 (If you want to use Kexec) - 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_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - 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. we dont need patch kernel with the no kexec workaround
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 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 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.
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.
XDA:DevDB Information
[MOD][MultiROM][v33][Beta 1][kenzo], Tool/Utility for the Xiaomi Redmi Note 3
Contributors
zeeshanhussain12
Source Code: https://github.com/multirom-nexus6p
Version Information
Status: Beta
Beta Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2016-06-15
Click to expand...
Click to collapse
Awesome Work buddy! Keep going!
@War_machine28 said:
Awesome Work buddy! Keep going!
Click to expand...
Click to collapse
Please don't quote the whole op...
Hey guys, Dual Boot Patcher for the Zuk Z2 Pro is officially supported! Check it out here!
Here's the guide:
First of all download these files from here:
DualBootPatcher.apk;
DualBoot tilities.zip;
DualBootPatcher for Windows (only if you want to patch files from windows instead of Android).
Important: Copy DualBootUtilities.zip into your internal memory because if something goes wrong you can "save" your phone thanks to it via recovery.
Install DualBootPatcher.apk;
Open it and give the root permission;
You will be asked to set the kernel in order to use it, confirm of course;
Now you have to tap on "Patch zip file";
After that select the FAB button than "Add flashable zip" and navigate to add the ROM/file that you want to patch;
You have to select the right device and choose "Dataslot" giving a name to the ROM;
Once is done you're ready to install you ROM/file;
Go to ROMs section and again click on the FAB button, "+" and than "Add patched file" and navigate to add the file that you've just patched;
"Keep Location" at the new prompt;
Now just tap on the tick on the top to start. At the end you will have the last 3/4 rows in green with return "0". Return 0 means "everything is ok";
Click on the ROM you want to boot the phone and reboot;
If something goes wrong you can use DualBootUtilities.zip to switch to your primary rom.
Reboot into recovery (press and hold the power button for 15 seconds);
Select recovery and than navigate and find "DualBootPatcher" that you have already copied to your internal memory and install it;
You will have an AROMA Interface to manage everysingle part of your ROMs;
Code:
[url]https://tlgur.com/d/MGanXyEg[/url]
(I noticed that AROMA interface is overturned, if you've got the same bug you have to try to get the right button on the screen via the volume buttons and power button).
Go next and select your primary ROM;
Code:
[url]https://tlgur.com/d/p8DkWkX4[/url]
Than select and press on "Switch to";
Code:
[url]https://tlgur.com/d/74yyryn4[/url]
Now, just click next until finish;
Code:
[url]https://tlgur.com/d/q8leDoyG[/url]
Reboot your device and you're ok.
Code:
[url]https://tlgur.com/d/MGanXyEg[/url]
Q&A:
Q: How can I update my primary ROM?
A: Just patch the file and select "PrimaryROM Updgrade". Flash it.
Q: How can I flash gapps on my secondary ROM?
A: Patch the gapps using as location "Dataslot" with the correct name that you've got for the ROM.
Q: How can I flash Xposed/Magisk on my secondary ROM?
A: Patch the file using as location "Dataslot" with the correct name that you've got for the ROM.
lucaam said:
Do you want a guide to use it?
Click to expand...
Click to collapse
Yes, please
Inviato dal mio Z2 Pro utilizzando Tapatalk
Works great. I'm on Lineage 13 and MIUI 8
Sent from my Z2 Pro using Tapatalk
HOLY CRAP WHERE WAS THIS ALL MY LIFE (or at least the last few months)?!
Instead of losing HOURS and HOURS out of my life just trying to finish running Titanium backups, TWRP backups, copying to computer, rebooting EDL, QFIL firehosing, waiting for ZUI boot, rebooting bootloader, reinstalling TWRP, installing a custom rom, GApps, Magisk/SuperSU/whatever, signing back into Google, doing settings and disabling built-in Chinese crapware, etc. OVER and OVER again... I can just patch the installer and make a new Data Slot? And switch back to ZUI as primary when it's time to get back to work? This is wonderful! Not quite a VM as far as sandboxing it, but still; such a timesaver!
I've never even seen it before, but patching a couple ROMs (AICP June 3 - Magisk removed from zukfans.eu and Mokee 712 June 6), osmosis' UnSU script, OpenGapps current pico release, and current SuperSU, checking free space, creating two Data slots, installing the ROMs with working Gapps and SuperSU into Data Slots 1 & 2, booting both, signing in to my Google account, and getting DBP loaded into both of them so I could switch around between testing environments and going back to ZUI as Primary ROM took all of about an hour and a half.
Daaaaang!
_____
Update: One obnoxious thing - you'll lose your PIN/fingerprint lock once you switch back to primary. As in, you'll put in the correct PIN, and it won't take it, and I presume won't let you in with fingerprint either; same as if you restore a nandroid backup with device protection enabled. To fix: via ADB or custom recovery file manager, you need to delete /data/system/locksettings.db (thanks to @srnoth via this post ).
That's correct, but only happens once when you install a secondary ROM and then switch back to your primary. Switching between the two works flawlessly afterwards. App Sharing works wonderfully. Apk has to be installed on both systems and the option has to be enabled both times. Then the same directory is used across the two systems.
Sent from my Z2 Pro using Tapatalk
Does anybody know how to install Xposed SDK into secondary ROM?
Sent from my ZUK Z2121 using Tapatalk
Great work!
Can we install two stock like: Android 6 in primary and Android 7 as seconde boot?
Thanks !
ZaK512 said:
Great work!
Can we install two stock like: Android 6 in primary and Android 7 as seconde boot?
Thanks !
Click to expand...
Click to collapse
Just added guide.
Can´t flash Lineage 13.
lucaam said:
Just added guide.
Click to expand...
Click to collapse
Can´t flash Lineage 13.
I have AICP 7.1.2 as primary and I flash lineage 13 exactly as you writte in tutorial but when i make reboot to lineage 13 the blue light turns on and it cant boot.
Is possible to use dualboot patcher with nougat and marshmallow custom roms?
almmpt said:
Can´t flash Lineage 13.
I have AICP 7.1.2 as primary and I flash lineage 13 exactly as you writte in tutorial but when i make reboot to lineage 13 the blue light turns on and it cant boot.
Is possible to use dualboot patcher with nougat and marshmallow custom roms?
Click to expand...
Click to collapse
You can because I was on Mokee 7.1.2 and I flashed Flyme that is 6.0. Maybe the problem is the version of Lineage 13. Try another 6.0 ROM.
Thanks
lucaam said:
You can because I was on Mokee 7.1.2 and I flashed Flyme that is 6.0. Maybe the problem is the version of Lineage 13. Try another 6.0 ROM.
Click to expand...
Click to collapse
Tomorrow I try MoKee 6.01 and othe Lineage 13.
Thanks.
Can't install Xposed into secondary ROM: /system can't be mounted. Any suggestions?
Sent from my Z2 Pro using Tapatalk
I cant install Lineage 13 as second rom.
I try with AICP 7.1.2 and MoKee 7.1.2 as primary rom but the second rom Lineage 13 cant boot sstem and only light a fixed blue led.
Anybody know why it is not possible to boot?
May be i have 7.1.2 as primary and 6.0.1 as secundary is the answer for that issue.
Thanks.
if your primary ROM is android 7 based then every secondary ROM need to be android 7 based. same for primary android 6 -> secondary need to be android 6
---------- Post added at 04:36 PM ---------- Previous post was at 04:22 PM ----------
there is a multirom recovery for the zuk z2 pro avalible, too.
what is the better solution in your opinion?
with multirom i have the possibility to select the ROM when i am booting
Multirom recovery?
Where I can find it?
With that multirom TWRP is possible to have dual boot with 7.1.2 and 6.0.1 custom ROMs working?
you'll find it on zukfans*eu and NO it is NOT possible to use 7.1.2/6.0.1 together. its because of the used modem etc. images ...
m45k said:
you'll find it on zukfans*eu and NO it is NOT possible to use 7.1.2/6.0.1 together. its because of the used modem etc. images ...
Click to expand...
Click to collapse
How can you explain 7.1.2 as primary and flyme based on 6.0 as secondary?
It's not possible. Even if this question is asked a thousand times
Has anybody tried wiping and reinstalling their primary room? I have some issues on my primary so I have to do a clean reinstall.
Also, is app sharing possible with multi rom TWRP?
Sent from my Z2 Pro using Tapatalk
Hi!
- Is possible to have the zui as primary rom and another custom as secondary?
- The custom roms as more time of battery?
Thanks
Introduction
Hello everyone! In the past few days, I was approached by a few people wanting to know the steps I take to successfully flash a ROM as a secondary ROM in MultiROM. Since there seems to be many people interested in trying out new ROMs while still keeping their daily-driver primary ROM untouched, I decided to make this thread for those interested. The following is a tutorial to modify a TWRP flashable ROM zip to make it compatible with MultiROM and then flashing it as a secondary ROM. Let's get straight to it then!
Compatibility
Device(s)
OnePlus 5
ROM(s)
Mostly All ROMs (in theory, at least, hence mostly)
Android Version(s)
Android Nougat 7.x.x
Android Oreo 8.x.x
Prerequisites
Basic knowledge about TWRP flashing, fastboot flashing, zip editing, MultiROM usage, etc.
A working fastboot interface on your computer
Zip-editor installed on your computer (I prefer Bandizip)
Unlocked bootloader (how-to guide here)
Unencrypted/decrypted system (how-to guide here)
Steps To Follow
Step 1: Create a new folder on desktop (or wherever you prefer) and download the following stuff in it:
The flashable ROM zip that you wish to modify to use a secondary ROM in MultiROM
update-binary.zip (attached at the end of this post)
The latest MultiROM recovery and MultiROM zip (available here)
An updated copy of the latest SuperSU (available here)
Step 2: Extract the update-binary.zip file after which you will get the modified update-binary file that we have to use
Step 3: Open the downloaded ROM zip in the zip program that you use and inside it, navigate to META-INF\com\google\android
Step 4: Delete the existing update-binary that you see there and replace it with the update-binary that you extracted in step 2
Step 5: Save the modified zip (this is now the modified ROM zip that can be flashed as a secondary ROM via MultiROM)
Step 6: Copy the modified ROM zip, the SuperSU zip and the MultiROM zip that you downloaded in step 1 to your phone's internal storage
Step 7: Reboot your phone to the bootloader mode and connect it to your computer
Step 8: Open command prompt and navigate to the folder where you've downloaded the MultiROM TWRP image file
Step 8: Run the following command to flash MultiROM TWRP to your phone's recovery partition:
Code:
fastboot flash recovery TWRP_multirom_cheeseburger_20170919-03.img
Step 10: Once the flashing is successful, reboot to the bootloader mode again using the command:
Code:
fastboot reboot-bootloader
Step 11: Press the volume down button until you see "Recovery mode" on your phone's screen and then press the power button to boot to recovery
Step 12: Once you're in the recovery mode (running MultiROM TWRP), flash the MultiROM zip first and then reboot your phone to recovery
Step 13: Once the phone has rebooted to the recovery mode, open the MultiROM menu (three parallel horizontal lines on the top right of your phone's screen) and click on the "Add ROM" option
Step 14: Select the modified ROM zip and flash it (choose the "internal memory" option if it prompts for a partition to flash the secondary ROM in)
Step 15: Once done, hit back to open the MultiROM menu, then click on the "List ROMs" option and select the ROM that you just installed
Step 16: Once you select the ROM that you just installed, select the "Install Zip" option and flash the SuperSU zip
Step 17: Once the SuperSU zip is flashed, reboot your phone to system and you will notice a new selection menu is now displayed before the phone boots into the system
Step 18: Select the new ROM that you just flashed as the secondary ROM to boot to it
Step 19: The phone will bootloop a couple of times - DON'T WORRY, THIS IS NORMAL AFTER FLASHING SUPERSU - and in between the reboots if you see the ROM selection menu appear again, just select the newly flashed ROM and let it continue
Step 20: It should boot into your secondary ROM after a couple of bootloops/reboots!
Disclaimers
You are doing this at your own risk. 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 are unsure of how to go about something. Also, please don't forget to make a full nandroid backup via TWRP in case anything goes wrong.
The above method works for me 99% of the time, but there are a few ROMs that I wasn't able to boot as secondary no matter what I tried. If a ROM doesn't boot as secondary for you using the tutorial above, I'll try my best to help you, but I may or may not succeed.
I haven't tried the above method with Magisk instead of SuperSU. If you wish to try, feel free to do so at your own risk.
Flashing of the secondary ROM will most probably corrupt your primary ROM's password/pin (if you have one setup). If you can't get into your primary ROM after flashing the secondary ROM using your password/pin, flash this zip in TWRP which will remove your lockscreen security settings (but won't touch your fingerprints, if you have any setup).
Thanks To
@martinusbe for adapting MultiROM (recovery, installer zip, manager application, uninstallation zip) to OnePlus 5
@Chainfire for SUperSU and all the work he's ever done for the community
All of you guys for viewing this thread
Changelog
December 26, 2017 - Initial post
OP Update Information
Created: December 26, 2017
Last Updated: December 26, 2017
@shadowstep This will be very useful to many people. Merry Christmas to you
SlyUK said:
@shadowstep This will be very useful to many people. Merry Christmas to you
Click to expand...
Click to collapse
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
shadowstep said:
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
Click to expand...
Click to collapse
Nice... speaking of Dirty Unicorns. Here is an update today.
SlyUK said:
Nice... speaking of Dirty Unicorns. Here is an update today.
Click to expand...
Click to collapse
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
shadowstep said:
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
Click to expand...
Click to collapse
Oh well thats fantastic. DU Oreo should be amazing once unleashed, i'm sure.
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Garfanki said:
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Click to expand...
Click to collapse
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Ok thanks, I will try!
shadowstep said:
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Click to expand...
Click to collapse
can i use magisk instead of supersu ?
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
Already mentioned this in the OP (Point 3 under Disclaimers). I haven't tested the method with Magisk in place of SuperSU.
This is because when I was initially trying to figure all this out, most of the stuff that I was going through pointed out that Magisk wasn't doing too well with the secondary ROM and hence I just chose SuperSU; didn't even bother testing Magisk when SuperSU worked fine.
If you wish to test, go for it. Should do no harm.
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
iirc magisk scripts won't run on secondary rom installation ( twrp multirom or dual boot patcher ) will give you errors and nothing will happen
Sent from my OnePlus 5 using XDA Labs
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
billsz said:
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
Click to expand...
Click to collapse
I haven't tested the method with OOS 5.0 Oreo as my primary ROM. When I last tested, I was running a custom Nougat based ROM (AOSiP) and with that I tested multiple Oreo based custom ROMs (after modifying them, of course, as mentioned in the tutorial) as secondary ROMs and they all worked fine. Not to mention, of course, that if you don't modify the ROM zip files with the updater-binary file I attached in the OP, then it just won't work.
I would like to have os stable Oreo as primary ROM and other Oreo build as secondary ROM, but the installation of secondary rom fails... Why? Is not possibile have 2 ROMS with Oreo?
Any help?
Garfanki said:
Any help?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Thank you, so I must wait... Happy New Year!
oF2pks said:
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Click to expand...
Click to collapse
Good evening, I try to flash flyme rom (downloaded by chinese forum) as secondary rom but the installation fail... Any idea?
Error 7
Can I flash xXx rom as secondary? or does it only work with lineage os based roms?
{
"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"
}
DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Warning: This method requires one time factory reset.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_data-slot.zip file will be created. For example,
Lineage-14.1-oxygen.zip
After patching would create a new
Lineage-14.1-oxygen_data-slot.zip
If you want to root secondary rom, then download Magisk 12.zip given below(Do not use other version, you can update that later from magisk manager app) and patch it like you did with rom
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Now Let's Start
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc on internal storage. So make sure you moved them or made their backup)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher.
6) Install patched rom as secondary on /system or on /data partition - it's your choice. There is lot of space for 3 roms in /system.
If you want to root secondary ROM and flash patched magiskv12.
7) Select your secondary ROM in ROM list and reboot.
Steps to be followed on Secondary Rom
8) Install Dual Boot Patcher.
9) Install MagiskManager.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
FAQ's (FAQ)
Do I need to wipe again for third or next rom?
No, wiping is only required for one time, you can flash as many roms(your device can handle) after that.
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:
First backup all your data including Internal Storage, then boot to TWRP>WIPE>FORMAT DATA then type 'yes' and tap enter. Now reboot and retry DBP.
Source/Credits:
https://dbp.noobdev.io
@chenxiaolong
@bad_request (Thanks for the XDA Post And Guide)
@mario_R (For step by step guide and errors.)
Downloads: https://dbp.noobdev.io/downloads/ and Download latest files
~ Hit Thanks button below if I helped you ~
*Reserved
**Reserved
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
drmuruga said:
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
Click to expand...
Click to collapse
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
jbmc83 said:
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
Click to expand...
Click to collapse
Yes , this tool working great , my problem is known to roms .
Patch roms and files in data slot not secondary slot in which is only one room can boot as secondary. Data slot for multiple roms flashing. And I never update ramdisk which leads to boot into recovery instead of system .
What's the use of dualboot we have only two ROMs to download.. Lol!
Now we should have at least two stable roms to taste this
nikz106 said:
What's the use of dualboot we have only two ROMs to download.. Lol!
Click to expand...
Click to collapse
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
jbmc83 said:
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
Click to expand...
Click to collapse
+1 to this.
Mgphyo126 said:
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
Click to expand...
Click to collapse
Anyone?
mario_R said:
Anyone?
Click to expand...
Click to collapse
Twrp >> wipe >> format data..
And it's ok now. ??
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
DON'T set lock screen !!
you will end up locked away from your primary rom
----------
in my case the primary was globerom and secondary was lineage os
---------
if you already locked from your rom you can boot twrp and open terminal and write
cd data/system
rm *.key
and reboot
kalawy said:
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
Click to expand...
Click to collapse
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Kapil Tapsi said:
If you want to root secondary rom, then download latest magisk and patch it like you did with rom
Click to expand...
Click to collapse
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Click to expand...
Click to collapse
I figured that out ... the hard way :crying:
mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
Click to expand...
Click to collapse
Thanks mario_R for the guide and trick. I did it hassle free as I already had my internal decrypted. But I noticed some people having problem with installation.
it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??
app share have a high chance of breaking secondery rom