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
Related
Hi guyz. The wait is finally over. Today I'm posting the method to use Sailfish OS as a secondary ROM in our Redmi 2/A/Prime/Enhanced, which will allow the users to test that awesome ROM without hampering the primary ROM of the device.
First things first, if you don't know how to use multiple ROMs using MultiROM, head over to the beautiful thread by @premaca : http://forum.xda-developers.com/redmi-2/development/mod-multirom-v33-t3381373
Next, if you don't know about the marvelous Sailfish OS which is made available to our device by @adeen-s till now, move to http://forum.xda-developers.com/redmi-2/development/beta-sailfishos-2-0-1-11-beta-redmi-2-t3408459, download both the ROMs and save them to our device.
Let the fun begin.
STEP 1 : INSTALLING SAILFISH OS AS A SECONDARY ROM
Reboot to MultiROM recovery
Select the three line option at top right
Select Add ROM
Select both Android and Internal Storage
Select ZIP file
Flash cm12.1-2016318-UNOFFICIAL.zip
After the process has been completed go back to the main MultiROM menu and select List ROMs
Select cm12.1-20160318-UNOFFICIAL
Select Install zip
Choose the sailfish os zip file and flash it
After the process has been completed, REBOOT TO YOUR PRIMARY ROM. DON'T REBOOT TO cn12.1-20160318-UNOFFICIAL YET.
STEP 2 : MAKING SAILFISH READY AS A SECONDARY ROM
After rebooting to your primary ROM open any file explorer, and browse to /data/media/0/multirom/roms/cm12.1-20160318-UNOFFICIAL. ALL THE OPERATIONS DESCRIBED BELOW WILL BE PERFORMED UNDER THIS FOLDER.
Browse and delete the following files :
../data/.stowaways/sailfishos/lib/systemd/system/system.mount
../data/.stowaways/sailfishos/etc/systemd/system/local-fs.target.wants/system.mount
Open ../boot/ folder and delete main_init
Extract the attached archive to ../boot/
Reboot and boot to cm12.1-20160318-UNOFFICIAL USING NO-KEXEC WORKAROUND
Now Sailfish should boot as secondary. Let me know if it works.
Reserved
Nice work. Could you create a PR to this patch on github.com/adeen-s/droid-config-wt88047
It would allow it to be implemented in future versions.
P. S. The new 2.0.2 version will be made available soon. WIP.
Edit: Since I could not test it yet, does it also boot up as Primary ROM with the applied changes ?
adeen-s said:
Nice work. Could you create a PR to this patch on github.com/adeen-s/droid-config-wt88047
It would allow it to be implemented in future versions.
P. S. The new 2.0.2 version will be made available soon. WIP.
Edit: Since I could not test it yet, does it also boot up as Primary ROM with the applied changes ?
Click to expand...
Click to collapse
1)I'll do it as soon as possible.
2)Thanx for your hard work and dedication to the device.
3)Most probably it won't boot as a primary ROM with the changes. For that, some if-else type checks are needed. I will work on that soon.
Great... i have succesfully flashed the rom use this guidance.
thonipublic said:
Great... i have succesfully flashed the rom use this guidance.
Click to expand...
Click to collapse
Happy to help!?
Somehow not working on @nrdnandan 's build. I followed all your instructions but it freezes at Mi Splash logo
My redmi 2 prime just stuck at MI logo while booting up
plzz need helpp
The best guide, I can boot sailfish OS as secondary rom
Thanks. It worked for me. FYI I used the latest files from the sfos thread.
Sent from my LG-VK810 using Tapatalk
Not working for me. Didn't work with old version of SF also. On restarting and selecting the CM rom from MultiROM, the Mi logo shows for sometime, then a random blue flash appears for a fraction of a second and it just reboots back to the multiROM menu. The same behaviour was observed with the old version as well.
And I did follow the instructions properly. No luck!
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2 + John Miller . The Lineage part is @XePeleato and the Aosp of @haky86.
Too much for you?
More novice users should not be scared because the installation and configuration is incremental and that is why I say that it fits any user profile.
User Profiles:
Depending on the concerns that are most suited to your profile you should take the installation to the point that best meets your needs.
As a user I want ...
1- I want a stock experience with some extras but without Root.
You must install the rom file by TWRP and dot. The rom is the same as the cerberus V2 but comes with no root.
It incorporates among others ..., gyroscope, call recording, multiwindow ...
REQUIRED REQUIREMENTS:
-Bootloader Unlocked.
-TWRP
- Android 6 - C432B594 Stock - Recommended.
2- I want you to have root access too.
After installing the rom you must enter the store and download the application magisk manager and ready. You already have root access and get the most out of the rom, but not only that, but root access can be hidden to play PoGo or use payment applications and pass the SafetyNet test.
3- I want to activate extra functions and transform and customize the rom butt.
Well what you have to do is install this file from TWRP point.
We will achieve the following:
- Activate Multiuser
- Enable Local Update
- You can choose whether to install the Huawei magnifier or not
- Busybox, Viper4Android and SLC disappear
- You can choose to install the busybox and the viper in a systemless way and in this way the SLC is no longer necessary
- Advanced Reset
- New lock screen 100% customizable.
- The screen automatically turns on and off when opening and closing the mobile phone case
- Incorporates system apps uninstaller
- Total Commander
- Greenify
- Etc...
4- I want to be able to choose which rom to start the smartphone.
For that it is necessary to have followed steps 1, 2 and 3 and it is necessary to configure magisk to have default access to all requests per adb and applications and install the multiboot option.
To install Dualboot you must go to the file EXTRAS.ZIP that you will find inside the system folder of the rom. Uncompress your content in the external memory and install the DualBoot app and keep the files in memory because we will need them for later.
Then we start the dualboot application to be granted superuser permissions automatically. Then with SimpleReboot we restart a recovery and make a backup of boot.img in case something goes wrong, since it will be the only thing we will need to repair a possible failure or error.
VERY IMPORTANT: We need to have 3Gb of available space in the External SD for each additional rom we want to install, that is, if we are going to install Lineage and Aosp we will need 6Gb of available space.
4.1- I want AOSP.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.1- I want LineageOS.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.3 I want the 3 Roms at a time.
Then follow steps 4.1 and 4.2
Restarting the system will take us directly to the last ROM installed. Once started and configured we installed the dualboot app that we had left on hand in the external SD. Repeat the operation on each of the additional roms installed. Once installed dualboot in all you can remove the app from the sd and of course all the corresponding installation files.
To change rom you have to enter the dualboot app and choose which one to start the system and restart.
MENTAL NOTE 01:
The 3 roms will have the same bugs as the originals. I am not yet qualified to fix them or even try, but I think that to be my first job is more than enough.
MENTAL NOTE 02:
The DualBoot application also installs an app called Leaks that controls possible bugs to send them to the original DualBoot developer.
I do not want to forget to give credits and thanks for:
@topjohnwu for creating magisk
@chenxiaolong for creating DualBoot and @BrainNotFound for portarlo
+ John Miller to create CerberusV2
@haky86 for creating Aosp and CWMR
@XePeleato for creating LineageOs and TWRP and Kernel
Greetings from Barcelona (Catalonia)
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Please delete, XDA app crashed while writing
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Link please :laugh::laugh::good::good:
kilroystyx said:
Link please :laugh::laugh::good::good:
Click to expand...
Click to collapse
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Click to expand...
Click to collapse
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
hi6120sft ale-l21 said:
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
Click to expand...
Click to collapse
Because it is cool, no more reasons sorry
I stucked on a first logo
blewko said:
I stucked on a first logo
Click to expand...
Click to collapse
Try a factory reset with stock recovery and flash again.
It helps in most cases
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
he should work... i have magisk and xposed but on C432B596 ROM
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
xander33 said:
he should work... i have magisk and xposed but on C432B596 ROM
Click to expand...
Click to collapse
Are you passing Safety net?
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It works. Flash Xposed and don't forget to wipe cache.
Phone will start in about 30 minutes.
It works. Use SDK 23 for this rom
Vinnipinni said:
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
Are you passing Safety net?
Click to expand...
Click to collapse
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
xander33 said:
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
Click to expand...
Click to collapse
I can confirm Xposed works. Not the Magisk one though.
Use the one from the mega root thread https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I also know the xposed torch works. Like to recommend xEmui module.
You can run more than one system through this APP.
I have handed up the "pull requests" to the dualbootpacher project for 10 days,but there is no respond.
I can't wait for it anymore,I just want to use the viper4android on PRO5,and still use the Flyme...
So I decide to do it with myself...
It is another way to the goal...hah...
You need to flash a unofficial kernel,if you want to use the application.
What you want is all in the zip.
A patchable kernel:https://forum.xda-developers.com/me...tpacher-pro5-unofficial-t3628955/post72850240
The official website:https://dbp.noobdev.io/
Its official source code on Github:https://github.com/chenxiaolong/DualBootPatcher
Songthings said:
I have handed up the pull requests to the dualbootpacher project for 10 days,but there was no respond.
I can't wait for it anymore,I just want to use the viper4android on PRO5,and still use the Flyme...
So I decide to do it with myself...
It is another way to the goal...hah...
You need to flash a unofficial kernel,if you want to use the application.
What you want is all in the zip.
Click to expand...
Click to collapse
Could u explain how it works ?
PYCON said:
Could u explain how it works ?
Click to expand...
Click to collapse
I just add a support for PRO5,you may find the answer here:https://github.com/chenxiaolong/DualBootPatcher
Thanks!!! faust already uploaded one multiboot but there were some issues. I'll try your version. Thanks!!
would this work to install ubuntu as secondary?
Add a patchable kernel,edited from the newest flyme(Chinese version) kernel.I feel it is smoother than any unofficial kernel.
(Better signal also)
An unofficial but official kernel.
You can use TWRP to flash it,you'd better backup your original boot before flash it,please remember any unofficial kernel will cause serial number losing(display is unknown).Of course, it will be back after you restore your kernel.
Flyme6 ONLY.
Mollic said:
would this work to install ubuntu as secondary?
Click to expand...
Click to collapse
:crying:I don't know,I haven't used Ubuntu mobile anymore.
It is for any flashable zips,
?Maybe you can give a try?
I have the dual boot working. I had to face some issues:
1. If I install Flyme as main rom and RR as secondary, the RR home button tap is not working.
2. If I install RR as main rom and Flyme as secondary, Flyme reboots just before start.
3. If I install one in main slot and other in dual slot, all system space is full and I couldn't flash google apps in RR rom.
The problem of points 1 and 2 is DTB partition is different in flyme and RR and the dualboot manager is not managing it.
To solve this issue I have used the TWRP by @st0rm77 in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
I have created a backup of DTB(Device Tree) partition for flyme and other backup of DTB partition for RR.
If I'm on flyme and I want to move to RR:
1. Restart in TWRP recovery and Restore RR DTB backup
2. flash dualbootutilities zip. It is an aroma manager to manage your dual boot roms. I select secondary rom (RR) and then "switch to"
3. reboot.
If I'm on RR and I want to move to Flyme:
1. Restart in TWRP recovery and Restore Flyme DTB backup
2. flash dualbootutilities zip. It is an aroma manager to manage your dual boot roms. I select primary rom (flyme) and then "switch to"
3. reboot.
To face the point 3 problem I have flashed RR in one Data slot named "rr".
p82maarj said:
I have the dual boot working. I had to face some issues:
1. If I install Flyme as main rom and RR as secondary, the RR home button tap is not working.
2. If I install RR as main rom and Flyme as secondary, Flyme reboots just before start.
3. If I install one in main slot and other in dual slot, all system space is full and I couldn't flash google apps in RR rom.
The problem of points 1 and 2 is DTB partition is different in flyme and RR and the dualboot manager is not managing it.
To solve this issue I have used the TWRP by @st0rm77 in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
I have created a backup of DTB(Device Tree) partition for flyme and other backup of DTB partition for RR.
If I'm on flyme and I want to move to RR:
1. Restart in TWRP recovery and Restore RR DTB backup
2. flash dualbootutilities zip. It is an aroma manager to manage your dual boot roms. I select secondary rom (RR) and then "switch to"
3. reboot.
If I'm on RR and I want to move to Flyme:
1. Restart in TWRP recovery and Restore Flyme DTB backup
2. flash dualbootutilities zip. It is an aroma manager to manage your dual boot roms. I select primary rom (flyme) and then "switch to"
3. reboot.
To face the point 3 problem I have flashed RR in one Data slot named "rr".
Click to expand...
Click to collapse
Yeah,PRO5 has no suitable firmware,working in both RR and Flyme...
And what a pity, the dualbootpacher has not supported the firmware switch...
Do you think it is necessary adding a support for boot gui ???
the viper4Android could install on flyme6 and it's working.
常山找邓艾 said:
the viper4Android could install on flyme6 and it's working.
Click to expand...
Click to collapse
老哥，有教程嘛？是全局viper音效吗？??
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?
First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19
How's the battery life?
works offline charge?
Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life
Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi
pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.
Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok
In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?
Never mind! I went ahead and installed it following the instruction . It works, thanks!
bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?
Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.
betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?
Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.
Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks