Related
Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff
Taken and modified from official thread at Flo
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, 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
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
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.
Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni
Reserved
Great work
Sent from my LG-P880 using Tapatalk
Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..
Nice work, could I ask you to prepare multirom uninstaller also?
It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.
Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...
I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.
Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880
love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release
Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?
Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff
For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .
not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?
Introduction
MultiROM is one-of-a-kind multi-boot mod for LG G2. It can boot any Android ROM. 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
Before you begin
This is in alpha stage. If you have the D805/6 model, use the recovery for D802. This should work on both LGD and JDI panels, but you may get some glitches. I'm working on a panel detection script which will be included in the next versions of recoveries.
Also, some ROM combinations don't work properly. You will get stuck on lg logo or MultiROM error message. It's because of the locked bootloader! It won't load the secondary ROM's kernel. We have to wait until there is a way to unlock it.
Click to expand...
Click to collapse
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-v28-UNOFFICIAL-G2.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_codename_YYYYMMDD.img) - download the ZIP file from second post and flash it in recovery.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Click to expand...
Click to collapse
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
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.
Click to expand...
Click to collapse
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs 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
MultiROM - https://github.com/PatrikKT/multirom-g2
Modified TWRP - https://github.com/PatrikKT/Team-Win-Recovery-Project
g2-common device tree - https://github.com/PatrikKT/device_lge_g2-common
Click to expand...
Click to collapse
Credits
@Tasssadar for the original work on MultiROM
@dr87 for letting me use his device tree and his kernel and helping out with some things
@savoca for his loki scripts
@arcardinal
@reas0n for testing
and everyone else I forgot
Donations
All this stuff would not be possible without the original work of Tasssadar. If you like his work, consider sparing him a few bucks on paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
And as of me, I don't want any donations. I do all of this for free. Just press that thanks button
Click to expand...
Click to collapse
This thread was used as a template
Downloads
1. Main downloads
MultiROM: multirom-20140921-v28b-UNNOFICIAL-G2.zip
Modified recovery (based on TWRP): TWRP_multirom__YYYYMMDD.zip
MultiROM Uninstaller: multirom_uninstaller.zip
Mirror: http://d-h.st/users/patrik.KT/MROM-G2
Click to expand...
Click to collapse
2. Kernels with kexec-hardboot patch
Render Kernel (for AOSP ROMs) - http://forum.xda-developers.com/lg-g2/development/kernel-render-kernel-aosp-lg-roms-t2803929
Dorimanx (for stock-based ROMs) - http://forum.xda-developers.com/showthread.php?t=2725023
VanirAOSP - http://forum.xda-developers.com/showthread.php?t=2494756
More coming soon!
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Nicely ask your kernel developer to merge kexec-hardboot patch.
Click to expand...
Click to collapse
Changelog
Code:
MultiROM v28b
=====================
* Fixed loki_tool for VS980
MultiROM v28a
=====================
* Larger UI
MultiROM v28
=====================
* Initial version for G2
* Support for devices with locked bootloader, which need loki
Recoveries:
Code:
21.09.2014
=====================
* Fixed loki_tool for VS980
15.09.2014
=====================
* Fixed installing zips without changing updater-script
14.09.2014
=====================
* TWRP 2.8.0
13.09.2014
=====================
* Initial G2 release
* Used SlimKat kernel source
reserved
happy testing, guys!
NOTE: this TWRP can be used as usual TWRP, it's similar to dr87 custom TWRP, but on SlimKat kernel.
Thanks guys you did it! How to uninstall?
Sent from my LG-D802 using XDA Premium 4 mobile app
TheFerhatKing said:
Thanks guys you did it! How to uninstall?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll make the uninstaller too. Until then, if you want to uninstall, just flash the ROM zip again and remove /data/media/0/multirom folder.
Okay thanks, just tested it a bit and it looks nice but the MultiROM UI is very small is it normal?
Sent from my LG-D802 using XDA Premium 4 mobile app
I'll make it bigger in the next version
Odoslané z môjho HTC Desire 601
Today is a good day!!!!
Looks fantastic! Thanks for your hard work. This will help out tremendously with this community Alot of us use our phones for work and play and cannot keep flashing back and forth. Now if we can get Ubuntu on here then we will really be cooking with fire. lol On my N72013 I had Ubuntu (Desktop) and my daily driver rom. I was able to do all sorts of high level IT work using Ubuntu then once I was don just change back over. This will open alot of doors for the G2. I am glad I got here when I did. AOSP really seems to be exploding contrary to CarbonRom dropping us. Though I understand why.
I am uploading new builds now that will support Multirom!
I love you XD multirom is the best tool for android! Which version of g2 is supported? d802?
EDIT: I've just that only version supported is d802!!!!
Good job guy!
Thanks for your awesome work
Sent from my LG-D802 using XDA Premium 4 mobile app
Cool~
Do you know if you'll be able to port this to d800?
Great achievement guys, you have breathed new life into our aging G2.
Been using Multirom from Nexus 4 days. Last used it on my HTC One(M7).
The best utility to have for the Flash-a-Holics like me.
Hope to see it soon for the Sprint variant LS980
I'm sure this will go in xda portal. Good work and thanks. I will try it later.
I just installed the multirom. It just ROCKS!!!!
I have installed pardus hd rom classic 7.7. Which rom can I use for second?
Is there any uninstaller available??
I used it with my nexus 4 its excellent I was wondering can I boot with my otg stick a ROM cause I have the 16gb with 10gb avaible
t-shock said:
I just installed the multirom. It just ROCKS!!!!
I have installed pardus hd rom classic 7.7. Which rom can I use for second?
Is there any uninstaller available??
Click to expand...
Click to collapse
If it's a stock based ROM, then you should install a stock based secondary ROM too. There are (sometimes) issues with booting stock-based and AOSP ROMs. The uninstaller is on the way. until then, you should be able to get rid of it by flashing the kernel you have and removing /data/media/0/multirom folder.
Ismail.A said:
I used it with my nexus 4 its excellent I was wondering can I boot with my otg stick a ROM cause I have the 16gb with 10gb avaible
Click to expand...
Click to collapse
Yes, you can. But it will be a bit slower. Read the OP...
I'm building the recovery images for d800, d801, d803, ls980 and vs980. The rest (d805, d806 and f320*) will be supported later.
EDIT: D800/1/2/3 builds are up. LS/VS980 and F320* coming in a few minutes
patrik.KT said:
If it's a stock based ROM, then you should install a stock based secondary ROM too. There are (sometimes) issues with booting stock-based and AOSP ROMs. The uninstaller is on the way. until then, you should be able to get rid of it by flashing the kernel you have and removing /data/media/0/multirom folder.
Yes, you can. But it will be a bit slower. Read the OP...
I'm building the recovery images for d800, d801, d803, ls980 and vs980. The rest (d805, d806 and f320*) will be supported later.
Click to expand...
Click to collapse
Thanks but only stock based rom that I found is with aroma.
I tried to replace some lines that you suggest to the script but it won't install.
Any suggestion??
t-shock said:
Thanks but only stock based rom that I found is with aroma.
I tried to replace some lines that you suggest to the script but it won't install.
Any suggestion??
Click to expand...
Click to collapse
Send me a link to the ROM's thread. I will check what line you should change
BTW as I said in the previous post, the d800/1/2/3 builds are up. Also the new twrp 2.8.0 is used from now.
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?
I recently started experimenting with Android 10 and found a fully working setup. So I'm deciding to share my current setup
#USE THIS AT YOUR OWN RISK!
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE DUE TO A BAD ROM FILE OR ELSE!#
#BUGS: NFC isn't working on downloadable build
You tell me#
NOTE: you can also use his newer builds. BUT those aren't preconfigured. For patches that you will need see 3rd post!
Requirements: latest twrp from official source,
Oreo firmware.
This Google play services APK:
https://drive.google.com/file/d/1V8ByPJx_hOoPpQNrG0LQcXzhHpFflN-I/view
I think that's it
Step 1: Download jarlpenguin's latest treble build here:
https://github.com/MontanaDevelopme.../lineage-16.0-20190713-UNOFFICIAL-montana.zip
Install it and wait for it to go into the lineage is setup screen. Reboot to recovery (you can download a rom by just going through setup, but all installed apps will be wiped!)
Step 2: if you haven't already download a rom of choice with a build date similar to this: 201910##
These builds should work with sim-card and possibly gapps
But I recommend this rom (please extract it first, otherwise you won't be able to flash this) : https://mega.nz/#!EE11mZyC!_45oKcdNv8djsA8CEh2ZVoTDkic3BCpLfFfU9TLUhes
Step 3: wipe system and data and head to the install section
Step 4: hit "install image" in the bottom right corner and navigate to the location of the extracted .img file
Step 5: select "system image" after pressing it and swipe to flash
Step 6: wait for it to boot (this can take quite a while so, please be patient!)
Step 7: when the device is booted, immediately head into the files application and install the Google play services app from the folder you put it in.
Step 8: after a while, the "completing system update" message should disappear. But there still is one problem... As this is a ported rom (I know I didn't mention this before) this still has the "system updater" app. So, you might disable that, otherwise it flashes a incompatible rom file.
ENJOY!
###ROOT###
to root the ROM, you need phh magisk, you should easily find it on Google or a search engine of choice. THE NORMAL BUILDS DON'T WORK, phh magisk is made for Android 10 treble builds using phhussons base or patches. That's why the normal version doesn't work
If you need help, feel free to contact me on telegram! @Rush
Sneak 100 profile picture
###GCAM###
To use gcam you should flash a Magisk module called:
"Several fixes for Moto G5/G5s"
Some apks may still not work though... As I haven't figured one out which 100% works
###Alternative ROMs###
To use alternative ROMs you will need to (most of the time) use a different lineage OS version by JarlPenguin together with only the boot & vendor images listed below:
https://drive.google.com/folderview?id=1QztsGvkhURcoCp-FjI40mvUpLp5NHSpj
Also, you know that a room won't boot when TWRP crashes, so don't even try, and no, even though the lineage 17.1 alpha build does "support" project treble, it doesn't have any better compatibility with Android 10 ROMs,
The only ROMs with at least some features I could get running is really just Pixeldust X ported from the pixel 1 using erfans tools
And this also works, of you are using (again) a newer or the latest build together with patches (see boot&vendor images above):
https://sourceforge.net/projects/zj...el-Aonly-10-20191120-GSI.img-1640.7z/download
Don't forget to extract this first! /\
Note: this newer build has NO MOTO GESTURES AT ALL
Sadly, I don't think there is a fix to that
### EVOLUTION X ###
I finally found a build which is working but. Uhhhh is kind complicated to bit to it first time
Basically you follow the normal tutorial, and then replace the advertised build with the latest 202001xx build by jarl
then wait for boot
Then reboot to recovery, and wipe system and data.
Reboot (I know that nothing is installed rn)
Select recovery and boot
Flash the evolution X .IMG fine and hope for it to but crash
Sadly,
There isn't even a guaranteed boot if you do that
But it will do the job good enough
Also, you won't need the GMS services APK anymore as this has everything already updated to ****
Please DONT flash the vendor and boot image patches as these will not allow the device to boot for some godforsaken reason
Link (please extract first):
https://sourceforge.net/projects/de...lution-X_3.3_20191111_ARM64-A.img.xz/download