Thanks to @chenxiaolong DualBoot is possible on OnePlus 2
Original thread for DualBoot patcher is located here:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs report or questions to developer post in original thread.
Questions about how to use DualBoot you can ask here.
Download newest patcher from here:
https://snapshots.noobdev.io/
OnePlus 2 support is added to ver. 8.0.0.r1775.gccb8192
DualBoot Patcher is still under development, expect bugs!
I'm not responsible for bricked phones and your wife/girlfriend pregnancy!
You have been warned!
How to:
First make nandroid backup in TWRP!
1. Install DualBoot patcher apk, open an app and go to ROMs section
2. Set the current running kernel as kernel for Primary ROM (app will ask you to do so)
3. Download CM12.1 or any different AOSP ROM, Gapps and go to "Patch zip file" section.
Use minimal Gapps if you installing on stripped /system partition.
4. Patch the ROM (for OnePlus 2 choose "Data Slot") and patch Gapps ("Data slot").
a) Primary ROM upgrade (you can patch zip for Primary ROM if you want to flash primary and don't destroy second system.
b) Secondary (Patched ROM will be installed in /system partition), to use it you need at least 1GB free space in /system partition, you can for example delete from /system all apps that can be downloaded from GooglePlay eg. Youtube, Maps, GMail.
c) Multislot1, 2 , 3 - will install ROM in /cache partition (not usable in OnePlus 2 because /cache partition is too small).
d) Data slot - use it if you don't want to touch /system partition.
e) Extsd slot - Not usable in OnePlus 2.
5. Flash patched ROM and Gapps in TWRP or ROMs section in DualBoot app, click red button to do it.
6. Reboot
You second system should start.
How to switch between ROMs:
1. Both ROMs needs DualBoot patcher installed, in "ROMs" section you should see ROMs list.
2. To switch the ROM simply tap Primary or Secondary, tick indicator should appear on ROM.
3. Reboot
To check partition sizes and free space, go to "Free space" section.
App sharing probably still don't work, I didn't try it but most likely after you try it you will need to restore your nandroid.
Testes on OnePlus 2 A2003, I'm running OxygenOS 2.1.0 as Primary and CM12.1 as Secondary (installed on /system partition)
Kudos, love and donations goes to developer, I'm only the Messenger:
@chenxiaolong
DONATE
Wow me first.
Gonna try it tomorrow.
Will report back.
Sent from my ONE A2003 using Tapatalk
Thanks thanks thanks
Great weekend assured.....
Sent from my ONE A2003 using Tapatalk
Nice.. Thanks will try it over the weekend
Thanks a lot !!!
Sent from my ONE A2003 using Tapatalk
lukas77 said:
Thanks to @chenxiaolong DualBoot is possible on OnePlus 2
Download newest patcher from here:
https://snapshots.noobdev.io/
OnePlus 2 support is added to ver. 8.0.0.r1775.gccb8192
Click to expand...
Click to collapse
is this the only version which supports our device or we can use the latest version as well?
hunhool said:
is this the only version which supports our device or we can use the latest version as well?
Click to expand...
Click to collapse
Use latest, in version I mentioned support were added.
Awesome!
Similar features like multi-rom from @tassadar for Nexus devices?
vergilbt said:
Similar features like multi-rom from @tassadar for Nexus devices?
Click to expand...
Click to collapse
TBH I've never used MultiROM and as far as I know MR needs special recovery and kernel. DualBoot needs only root to work
Sent from my ONE A2003 using Tapatalk
That's right MR need a modified twrp and a kernel with kexec-hardboot
Seems like dual boot is easier to handle
lukas77 said:
TBH I've never used MultiROM and as far as I know MR needs special recovery and kernel. DualBoot needs only root to work
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Dualboot could run more than two ROM or OS?
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
vergilbt said:
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
Click to expand...
Click to collapse
No idea, ask the developer @chenxiaolong in his thread provided in OP.
Also attach multiboot.log file created in /sdcard
Sent from my ONE A2003 using Tapatalk
vergilbt said:
I'd anybody running dual boot? Isn't working for me...
1. Install room
2. Set kernel of primary
3. patch rom to data slot
4. Zip patched rom without changing location (superSU grant permission)
5. Reboot
But after reboot it loads every time twrp recovery and not secondary rom...
Where is my fault?
Click to expand...
Click to collapse
You didn't install the ROM via. TWRP recovery. There might be an issue with the way the ROM patcher flashes the files via an Online Flash (with you booted into your Primary ROM) vs. an offline flash (in TWRP, pre-boot).
work fine for me with oxygen 2.1 in primary and cm12.1 in/data ,
sadly my favorite rom : mookee seems doesb't support this patcher, flash fail everytime in twrp
Thank you very much for this great port!
Is there any chance of getting MultiROM support for the 2? I loved MR in both my Nexus 5 and OnePlus One.
jmazzamj said:
Thank you very much for this great port!
Is there any chance of getting MultiROM support for the 2? I loved MR in both my Nexus 5 and OnePlus One.
Click to expand...
Click to collapse
Don't you think you should ask this question MultiROM developer? This is completely different app, not related to MultiROM.
Sent from my ONE A2003 using Tapatalk
Great to have this on our device! Always used multirom on my OPO but to be honest, this is a better solution! Usually I had to reboot to TWRP and being offline for 15 minutes or more. Now I can just patch&flash a rom while staying online.
The only thing is... Why is it called dual boot? It's multi boot actually.
Related
Hello I have made a very detailed video showing how to get Stock Samsung Lollipop (5.0.1) and CyanogenMod 12.1 (5.1.1) on the same phone [n910w8] dual booting.
THIS IS DONE AT YOUR OWN DESCRETION and I am not responsible if something goes wrong or you do something wrong. I have repeated the process at least 10 times to see how it works. Even did it on a Samsung Galaxy S4 with no issues.
This video is demonstrating the installation process for the Galaxy Note 4 n910w8 (Canadian snapdragon version used in video)
PLEASE TAKE YOUR TIME even watch the video a few times before you give it a try. In the end you can always flash stock Samsung Rom and do a factory reset.
I really enjoy using this feature and having the choice between two different roms on the same phone.
You can share apps from your stock Samsung Rom to your Cyanogenmod Rom without having to reinstall most of your apps. Saving lots of space.
I hope you enjoy.
Like.
Subscribe.
Click an add or two.
Thanks and a wonderful day.
Happy dual booting.
VIDEO LINK:
Samsung Galaxy Note 4 Dual Boot/multi Rom support:
https://youtu.be/CpegzNc4ZH0
Download Link Dual Boot Patcher:
https://snapshots.noobdev.io/
Download Link CM 12.1 (trltetmo) WORKING ON N910w8:
https://download.cyanogenmod.org/?device=trltetmo
Download Link Cyanogenmod Google Apps:
http://wiki.cyanogenmod.org/w/Google_Apps
Thanks:
chenxiaolong
Working on getting support brought to the Samsung Galaxy Tab S 8.4 also. Awaiting conformation, working with the developer. No garinties but fingers crossed that another top device gets dual boot compatibility.
Does anyone have a link to this build????
cm-12-20150413-NIGHTLY-trltetmo.zip
i keep trying on cyanogenmod website but the link is down.
If anyone could help it would be greatly appreciated.
It would really help with Google cardboar/vr testing. Native sbs is reported working on the rom I am looking for and it would be worth a try.
Nice mate
So by using FolderMount I am able to save so far 3gb of space on my data folder. I transfer app data to external SD card. Link the app data on external SD card with FolderMount which tricks the app into thinking it is installed on internal data.
Then I created a backup in FolderMount. Switch roms load FolderMount. Restore backup for FolderMount. Restore link app data locations because cm and touchwiz see external SD card different and FolderMount corrects this thankfully.
Click the green linking tab a few times and FolderMount will recognize the data.
As I said I have saved 3gb of room on my internal data having app data on external SD card.
If something like this was built into our dualboot patcher it would make things easier. Maybe if we spoke to the developer of FolderMount. If not using both FolderMount and Dual boot patcher I now have 3 roms on my Note 4 and almost 4gb free space on internal data between all 3 roms. Look at the pics of before in my previous comment and this one to see.
Just finding ways of maybe booting 4 roms on one phone.
Will report back.
Think I am on to something, let me know what you think. Give it a try possibly. I will be making a youtube video to help better demonstrate.
Before and after of data saved
My current Tri Boot state on my Note 4
Currently running Touchwiz stock lollipop 5.0.1 (primary partition), cm12.1(secondary partition) and cm12(data partition) all on the same phone.
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
samurai_vara said:
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
Click to expand...
Click to collapse
Try reinstalling cm12 and sharing again once you boot up.
Leonidas87 said:
Try reinstalling cm12 and sharing again once you boot up.
Click to expand...
Click to collapse
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
samurai_vara said:
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
Click to expand...
Click to collapse
Once you do those 3 steps all apps should share between both the primary and secondary Rom once you do a quick reboot after enabling the app sharing. Whenever you install a new app on one or the other Rom and then boot in to one of the roms you will usually see android upgrading or upgrading apps something like that during boot up. But yea you only need to enable app sharing in the second Rom not primary. Everything from the secondary Rom seems to share with the primary Rom. Overall it is a great system. Complicated in thought but it works. Once you get a feel for it you will be impressed.
Nice. I will try this when I get home. Been wanting to run CM but gear vr has me stuck on touch jizz. Will report how it works.
Sent from my SM-N910T using Tapatalk
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
chrisa887 said:
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
Click to expand...
Click to collapse
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Leonidas87 said:
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Click to expand...
Click to collapse
I see, I want the cm12 as my secondary rom so I patch it first then install it then I patch the gapps then install them then I can reboot to secondary rom and set everything up right?
Sent from my SM-N910T using Tapatalk
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Leonidas87 said:
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Click to expand...
Click to collapse
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Great job, thank you dev.
I have question about App Sharing. Should I install Gapps on both roms or only on Primary and share them?
chrisa887 said:
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yes patch then install. No need to reinstall Google apps all that will still be there.
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
Ok, to clear the air, I am not the original Dev for this particular project. I had been working on a very similar project until I found this. It just needed for me to add support for our device. So I did just that. I made a prominent build and after extreme testing it is ready to be shared with you.
See Continuous Integration Builds at the end of this post for a link to download latest releases. All releases starting from November 5, 2015 and onward will support the Huawei Ascend Mate 2.
It can patch:
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in other ROMs
NOTE: If you want to dualboot a stock EMUI ROM, I highly recommend installing it as your primary ROM first. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of Extsd slots. These install to the external sd partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher got support for sharing apps (deprecated) and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
How do I...?
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
WATCH THESE HOW-TO VIDEOS:
Credits to @superbass311 for making these videos.
It will demonstrate how to use this app effectively. If you read the instructions and still can't figure it out then this will be very helpful to you!
How to install Multi Boot Patcher:
How to flash another ROM with Multi Boot Patcher:
How to flash Xposed with Multi Boot Patcher:
How to share apps with Multi Boot Patcher:
Original Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Contributors
chenxiaolong, SHM
Version Information
Status: Testing
Continuous Integration Builds: https://snapshots.noobdev.io/
Created 2015-10-11
Last Updated 2015-11-07
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
MT2-User said:
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
Click to expand...
Click to collapse
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Edit: please try not to quote the entire first post. Can be a pain scrolling through if using an app.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Click to expand...
Click to collapse
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
MT2-User said:
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
Click to expand...
Click to collapse
If CyanDelta targets the patched ROM then yes, buy pointless to jump back to the cyandelta app. While using the Dual Boot Patcher app you can install from there. After the patch is made you go to, Roms, then click on the icon at the bottom right. It will have a phone with an arrow pointing down. In the same location press another icon with an add sign. Select the patch ROM. Then flash it through the app. Don't even need to go to TWRP at all unless its the primary ROM. This is explained in the OP already
Sent from my Ascend Mate 2 using Tapatalk
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
MT2-User said:
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
Click to expand...
Click to collapse
No worries, maybe @superbass311 will make a video for others to help them out. He likes making them videos lol.
Sent from my Ascend Mate 2 using Tapatalk
Oh sh+t! @SHM I did not see these post! He'll ya this will be my reading for tonight and I will try it all out then I'll make a video. Sweet!
Sent from my Ascend Mate 2 using Tapatalk
Interested in App Sharing.
From @chenxiaolong (http://forum.xda-developers.com/attachment.php?attachmentid=3318276&d=1431909206), space would be saved from keeping two/more APKs; however, if I have to install the same App in each ROM, how would that happen? Or actually the 2nd, and other subsequent ROM(s) just redirect the same App other than do real installation OR delete the same App after permission of the same shared App?
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
MT2-User said:
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
Click to expand...
Click to collapse
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
SHM said:
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
Click to expand...
Click to collapse
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 700 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
SHM said:
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
Click to expand...
Click to collapse
DId you install each App 3X? Or just backup/restore using TB?
MT2-User said:
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 500 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
Click to expand...
Click to collapse
For your first question, yes, but the primary ROM needs to be patched first in order for it to work. My recommendation with that is to grab the latest ROM zip for your primary and patch that zip using the app. Then install the patched zip to your primary. It will add needed files and binaries to make things more effective. This also makes sure not to mess with other ROMs as well. As for your second question about gapps, if you wish to install the gapps to a ROM, let's say PAC rom, and PAC rom is installed on your external SD, then you must patch the gapps zip using the configuration for PAC. When the patch is done, simply flash. Doing this insures the gapps is properly installed to that specific ROM. Otherwise it will just install to your primary ROM by default and if your primary ROM already has gapps then this isn't what you want it to do lol. You must patch the gapps zip for each ROM configuration to insure that it installs to that specific ROM. It takes no time to do this. Its easy, and quick. Give it a try
MT2-User said:
DId you install each App 3X? Or just backup/restore using TB?
Click to expand...
Click to collapse
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
SHM said:
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
Click to expand...
Click to collapse
Actually I got confused from the quoted content in OP saying in each ROM to install the App first.
MT2-User said:
Actually I got confused from OP saying in each ROM to install the App first.
Click to expand...
Click to collapse
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
SHM said:
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
Click to expand...
Click to collapse
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish between system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
MT2-User said:
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
Click to expand...
Click to collapse
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
How much space are you using running three ROMs?
SHM said:
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
Click to expand...
Click to collapse
:good::good::good:
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the App from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App and data sharing?
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I?
Switch the ROM if something doesn't work properly ?
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Downloads
App - Here
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Lenovo Vibe K5 & K5 Plus , Tool/Utility for the Android General
Contributors
Dreamstar, chenxiaolong
Version Information
Status: Beta
Created 2016-12-19
Last Updated 2016-12-25
Reserved
Thanks for this!
Can anyone confirm this working?
Can confirm this is working in Lenovo Vibe K5 a6020a40 device thanx for this you are awesome
This is truly awesome!!
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
netship said:
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
Click to expand...
Click to collapse
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Wow man just wow!
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Thank you Very much!!
Recieved error message while installing secondary rom.
Guys any solution?
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
You may try this.
netship said:
You may try this.
Click to expand...
Click to collapse
I tried bro still same problem...
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Upload that log file here
Error log
App sharing not working.. or I'm doing something wrong.. don't know but not working for me.
What about efidroid manager
Can anybody try to port it to lenovo k5??
Last I checked with 10/4 aicp nightly, it's not working. Needs some fixes.
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Same here tried changing name no success
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?