I'm proud to present the first dual boot project for the Samsung Galaxy S9+ Snapdragon version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
NOTE
Treble-based ROMs are NOT supported(yet)! In-app ROM changing may not work on stock ROM (maybe it works, maybe not) so you have to use utilities.zip or flash the boot.img of every ROM! I do not own a S9+ so I rely on you guys!
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
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 the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. 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. 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
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip 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.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
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.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
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
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a 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
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy S9+ Snapdragon/Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Epic htc 1 said:
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Click to expand...
Click to collapse
Yes root is needed, but the patcher does not support treble ROMs at this point. Maybe in the future.
Im not a programmer, I just add support for devices and compile it. The real programming is made by the official devs
please support for exynos
Joad said:
please support for exynos
Click to expand...
Click to collapse
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
simon151102 said:
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
Click to expand...
Click to collapse
Thanks .
View attachment 20190225.101831.tar.gz
Joad said:
Thanks .
Click to expand...
Click to collapse
Will compile a new version with S9+ Exynos support in the next few days
Update
Support for S9+ Exynos version
Patcher: Download
Utilities: Download
Does anyone have a root for s9 plus (snapdragon)
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Epic htc 1 said:
Does anyone have a root for s9 plus (snapdragon)
Click to expand...
Click to collapse
Use magisks built-in root, works perfect on most devices
Joad said:
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Click to expand...
Click to collapse
I will look into this.
But I cant guarantee for a fix because I have no skills in programming
Thank you very much,if anyone has any information about this plz let me know I'm really interested in this program
Does this work for anyone? and if so, using which roms.
Thanks
cvamoose said:
Does this work for anyone? and if so, using which roms.
Thanks
Click to expand...
Click to collapse
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
simon151102 said:
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
Click to expand...
Click to collapse
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
cvamoose said:
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Click to expand...
Click to collapse
Yes, treble devices arent supported (yet?).
I dont know if the S9+ is treble based, but it seems like this version of DBP works for most S9+ users
kykint said:
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
Click to expand...
Click to collapse
Sorry, Im not a "real" dev.
All I did was following the instructions from the DBP wiki.
Is there anyone that can make a modded version of this that will work on non rooted phones and it doesn't have to be a dual boot patcher but just to get a different ROM running on top or VNC into and use. Maybe like a dual ROM runner.
Related
[Guide] Multi Boot Note 3 (Updated 24/07/2015)
*** Hi Guys i no longer have a note 3 so i cant do any testing but our team member is here to give support for you all and even im here to give support except testing. please contact @[email protected] and @djnim for support.***
I am using this on SM-N9005 Snapdragon Variant of the Note 3; I believe this will work with other Note 3 Variants as well. Few of them are already tested and you can find them below. Others who have different variants which are not tested can try this and update us, and we will be here to help you out if you are ready to try this out.
@chenxiaolong is the one who made this happen to our beloved Note 3
Main advantage of this is you can try any new rom with out loosing or having any kind of trouble with your existing rom. This mod will not change anything in your primary rom, so any time you can go back to your normal state.
Disclaimer
1.I am not responsible for bricked devices, dead SD cards,etc.
2.Before going further! YOU are choosing to make these modifications.
supported Devices: ( Tested and confirmed working)
SM-N9005 (International Qualcomm): hlte (Tested by me )
SM-N900T (T-Mobile US): hltetmo (Tested by @MistaEast ) confirmation post
SM-N900R4 (US Cellular): hlteusc (Tested by @harshal10398 ) confirmation post
SM-N900 (International Exynos): ha3g (Tested by @mohnishkat ) confirmation post
SM-N900P (Sprint): hltespr (Tested by @lord dredd ) confirmation post
SM-N900K(Korean): (Tested by @Premananda_laishram) confirmation post
Requirements
* Read the full guide before Starting.
* Backup your phone if you are doing this first time. (Full Nandroid backup recommended for the new comers and it’s also recommended to others who don’t know what they are doing exactly even if they have multi booted several times)
* Rooted Note 3 with custom recovery (preferred TWRP or philz).
* free space in your internal SD (for example a Cm based roms take up to 2.5GB to 3.5GB and a TW roms take up to 5GB or more.)
* If you face any trouble please read the FAQ before doing something or asking for help. And if you want help please provide as much as details(device, roms, etc.) you can.
*
Instruction:
1.Download your desired Rom which you want to use for multi booting and the mods, addons, gapps, Kernel etc for the same. Keep the files in your internal memory.
2. Download the most recent snapshot release of Dual Boot Patcher and install it on your Note 3.
3. Open Dual Boot Patcher and grant SU permission. Then go to ROMS and you will see your Primary rom, press the 3dotmenu key and click "set kernel". If it fail to set kernal please read the FAQ.
4. Then In Dual Boot Patcher go to Patch Zip File and Choose hlte for snapdragon variant and ha3g for Exynos veriant (Samsung Galaxy Note 3) from the drop down menu.
5. In the second drop down menu select "Data Slot".
6. Below that you have to enter the ID of the secondary rom.(Example 1, 2, 3, etc. - it will take it as /data/multiboot/data-slot-1)
7.Now tap on the below button to choose the ROM's, Gapps, Kernel and mods to patch them and make them perfect for Multi booting.
8. Always remember to keep same slot ID for the Gapps, kernels and mods same as the rom. (Example: if you want to flash the gapps/kernel to the data-slot-1 rom then you have to select the same ID that’s 1 or if you want to flash the gapps/kernel to the data-slot-2 rom then you have to select the same ID that’s 2.)
9. When selecting the files except cm rom zip there will be a “preset” drop down menu, from that you have to select according to the file you are going to patch. (Examp: for roms, kernels, mods, addons – custom; for gapps – Google_Apps; for Su zip – other/SuperSu; For xposed-Other/Xposed)
10. Now press the tap to begin patching button to patch the file. And you will get a new patched zip file in the same location.
11. Now Boot into custom recovery and flash the new patched file and reboot.
12. And your device will boot into New Rom.
13.Install the Dual Boot Patcher app and set the kernel for your second ROM as well.
14. To switch between roms
•Open Dual Boot Patcher app/roms and click on primary or secondary rom as you like and reboot.
•Or Use Swap Roms to switch between Roms.
* Important things to keep in mind: while installing a rom or mod with Aroma installer don't reboot directly from the aroma.
You have to always uncheck the last option to reboot in aroma and click finish. So it can finish the final steps for multi booting.
And if you miss that it will only reboot to recovery. To boot back you have to flash your primary rom kernel or re-flash the patched rom.
Never update a secondary rom through OTA Update.
*. For other devices:
1. You have to download and install X-plore File Manager (which I am using) from play store.
2. Open X-plore File Manager from app drawer and navigate to the patched zip file and open it.
3. Now you will see a folder named multiboot inside that you will find info.prop, now open info.prop with the text editor which comes with the x-plore file manager.
• And then find and change mbtool.installer.ignore-codename=false to mbtool.installer.ignore-codename=true
Revert
To revert back or if you face any problem just flash my Multi Boot cleaner.zip which will wipe all the installation files from \system and restore the primary rom kernel.
As a backup keep a copy of your kernel flashable zip file.
FAQ
1. I can't set the primary rom kernel in xyz rom. And I can’t switch to other rom in primary rom.
Ans. Just download the set kernel fix as per your model and flash it in the recovery.
The above fix only work for primary rom. If you have trouble with any other roms just add ro.patcher.device=hlte(for other models add your model instead of hlte) to the bottom of build.prop of that rom and you are good to go.
If you don’t know how to do that just pm me and I will make a flash able zip to add it to your secondary rom.
if the above didnt work Read this post please
2. App sharing?
Ans. Until now no luck. (Still under testing)
3. This rom can’t be patched.
Ans. some roms are not supported its known, if the Dev have time may be he will consider including them.
Also read this
Credits/ Thanks:
@chenxiaolong
Original Thread: http://forum.xda-developers.com/showpost.php?p=45659284
Don't forget to thank him and if you can please consider a small donation for him because he really deserve it.
@aukhan & Team Emotroid
His Thread (Where I got the idea and help to make this guide): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
@rlorange for the help and support.
His thread for Dual boot backup and restore app. http://forum.xda-developers.com/showthread.php?t=2491299, http://forum.xda-developers.com/not...-4-15-multi-boot-backup-restore-v1-0-t3087187
@AholicCert for helping me with some scripts
@ other XDAmembers
Video Guide
https://www.youtube.com/watch?v=upeSC65t5XQ
Going to try it mate tnx
a_prabhu7 said:
Going to try it mate tnx
Click to expand...
Click to collapse
Welcome try it and let us know.
Sent from my SM-N9005 using XDA Free mobile app
Has anyone tried this out on N900????
thetitanium said:
Has anyone tried this out on N900????
Click to expand...
Click to collapse
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
54NJ41 said:
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
Click to expand...
Click to collapse
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
vagenrider said:
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
Click to expand...
Click to collapse
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
54NJ41 said:
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
Click to expand...
Click to collapse
tried all mate but nothing..
vagenrider said:
tried all mate but nothing..
Click to expand...
Click to collapse
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
54NJ41 said:
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
Click to expand...
Click to collapse
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
vagenrider said:
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
Click to expand...
Click to collapse
Which version 7.2 or other
54NJ41 said:
Which version 7.2 or other
Click to expand...
Click to collapse
7.2
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Rogers Note 3
Anyone can tell me if I can install it for the Canadian Rogers Galaxy Note 3 ?
Thank you
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
vagenrider said:
7.2
Click to expand...
Click to collapse
I have tried the rom but same result as yours. But don’t worry I have an alternative way to set the kernel for your primary rom.
First make folders in your SDCard, “MultiBoot” in it “Primary” it should be like: Sdcard/MultiBoot/Primary
Then extract the boot.img from your rom zip and copy it to Sdcard/MultiBoot/Primary
So the result will be Sdcard/MultiBoot/Primary/boot.img
It’s done.
NightForce said:
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
Click to expand...
Click to collapse
Welcome bro
dream_catcher79 said:
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Click to expand...
Click to collapse
To make space in your system partition.
1. Delete what ever apps you are not using from system/app and syatem/priv-app (Don’t delete if you don’t know what it is or what your are doing.)
Example: shealth, etc.
2. Move some google apps from /system/app to /data/app to make them user app using root explorer.
Example: maps, gmail, chrome, etc.
thermax04 said:
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
Click to expand...
Click to collapse
To dual boot two TW roms is very hard. Because there is not enough space to fit both system file in your system partition. Other wise you have to deboalt the primary rom and you have to deboalt secondary rom zip before flashing. And by doing so you will lose most of the features of your TW roms.
And if you want to use CM as primary and TW rom as secondary its possible but not recommended. Because you will have trouble with flashing mods etc for your TW rom.
The better option at the moment is to keep the TW rom as Primary and others a secondary.
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 other devices too. (See the list below to see if your device is supported)
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the features in this tool
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption 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 current devices it's the CPU's task. Even though modern devices have quite fast CPU 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 scientific measurements though)
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. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least 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, if necessary, 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)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
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.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
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.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?
cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.
Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Worked on my N9 - thanks!
provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "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.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "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.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.
I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
Original thread for DualBoot patcher is located here:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs report or questions for the developer please post in original thread.
Questions about how to use DualBoot you can ask here.
Download patcher app from here:
https://dbp.noobdev.io/files/9.1.0....tcherAndroid-9.1.0.r38.g5d5b401-snapshot.apk
DualBoot Patcher is still under development, expect bugs.
I'm not responsible for bricked phones.
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 CM13 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 CM13 ROM zip (for LG G5 choose "secondary") and patch Gapps ("secondary")
a) Go to settings of the app and install Boot UI.
25.11.2016 -> Note for H830 users,go with data slot instead of secondary until the secondary slot is fixed.
5. Flash patched ROM and Gapps in TWRP or ROMs section in DualBoot app, click red button to do it.
6. Go to ROMs in the app and tap on the rom you want to boot
7. Reboot
You second system should start. (if you get a black screen,wait a bit,first boot usually takes a while)
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.
Location explanation :
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 that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Lockscreen security solution:
On all ROMs you must set lockscreen to have the same lock e.g. a pattern lock with the same pattern on each ROM to unlock.
The issue has something to do with the secondary ROM overwriting the gatekeeper.pattern.key file, so then when you switch to primary you have a pattern lock but with no correct pattern even set, hence why the pattern you enter is always incorrect.
Steps:
1. Set lockscreen security (what ever you decide to use, fingerprints,pin,password, pattern) in the secondary rom first.
2. Set the exact same lockscreen security in the primary rom
3. That's it,now it works on both roms
Tested on LG G5 H850, I'm running stock lg rom as Primary and CM13 as Secondary.
Tested stock roms with aroma installer,doesn't work as secondary,only as primary.
Tested on LG G5 H830, everything works now.
Stock can't be dual booted as secondary due to size,so go with other slots like,for example, data slot
If in app flashing doesn't work,use twrp to flash the patched ROM and the patched gapps
Since the 25.10.2016 the SD card bug on second rom is fixed,link above updated.
Since 25.11.2016 LG G5 H830 is supported, thanks to jeffsga88 for helping with that.
Updated: 04.12.2016
Awesome, thanks....
Enviado desde mi LG-H850 mediante Tapatalk
I can comfirm this works well running stock rooted and cm13 beta with no issue. Many Thanks
It doesn't seem to work on the h830 : (
eminem5055 said:
It doesn't seem to work on the h830 : (
Click to expand...
Click to collapse
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
onestyle007 said:
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
Click to expand...
Click to collapse
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
I also have the h830 and got the same error message.
---------- Post added at 10:30 PM ---------- Previous post was at 09:47 PM ----------
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
The issue is not with rom, the issue is with the patcher. I believe that as of now, the patcher supports only the h850 version.
If the issue is with the patcher then I'm sure it won't be that hard to fix.
Yeah I've just looked at the zip created by the app, it automatically sets it for h850. Thanks for letting me know
onestyle007 said:
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
DualBoot Patcher is still under development, expect bugs,currently on LG G5 there is an sd card bug on second rom,shows as corrupted,hopefully it will be fixed soon!
Click to expand...
Click to collapse
Any news regarding the sd card bug?
Thank you in advance
kafisc said:
Any news regarding the sd card bug?
Thank you in advance
Click to expand...
Click to collapse
No news yet. If anything changes I'll inform everyone about it in the first post
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
nima0003 said:
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
Click to expand...
Click to collapse
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
onestyle007 said:
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
Click to expand...
Click to collapse
OK thanks!
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
nima0003 said:
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
Click to expand...
Click to collapse
I would assume so, the rom would have to be compatible with H830. From what i can tell the Boot Patcher allows you to patch a rom to work on a different partition/slot. It uses a certain set on scripts before to allocate where the files will go then the rom is installed as it normally would.
Please correct me if im wrong anyone
Hi, is the version here different in any way from the original version? Thanks
bonotheedge said:
Hi, is the version here different in any way from the original version? Thanks
Click to expand...
Click to collapse
Version that is posted here has support for LG G5,and since lg g5 is not fully supported (sdcard issue) it's not added to the original version. That's the difference
Thanks. That's what I thought. I hope that this version in some point will also support h830.
Any news about his being available on the h830?
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
tanush said:
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
Click to expand...
Click to collapse
I don't think, I'm sure it's not supported because I put the codenames on github and P2c72 is not in the list. No problem if you want to multiboot I'll add it in no time. You can flash all the roms available here for p2a42 on your P2c72 just fine by removing the first lines "assert get prop" in the updater-script. You can flash these roms the usual way via twrp. But if you use the DualBoot Patcher as for now it won't recognize the P2c72.
911-Future_Maker said:
I don't think I'm sure it's not supported because I put the codenames on github and P2c72 is not on the list. No problem if you want to multiboot I'll add it in no time.
Click to expand...
Click to collapse
Cheers! My phone is on the way from china. Might be another week or so Right now just browsing everything that we have here.
Thanks for this. After so many ROMS ported recently, this would really help me out with having one stable daily driver and others to try to. Not an android developer but I'd like to try my hands as well finally to make a ROM and maybe look into the two bugs that are persistent across all ROMS. Let's see. I've just developed apps for now.
Anyways, thanks, this is indeed good stuff.
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
911-Future_Maker said:
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
Click to expand...
Click to collapse
yes, thats the only reason I had to get it from china. Apparently, only 32 gb version is available outside china.
Thank You Bro
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
tanush said:
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
Click to expand...
Click to collapse
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
911-Future_Maker said:
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
Click to expand...
Click to collapse
Sorry brother didn't go through as I can't actually do it. Still waiting on my bootloader :/
So anyone had any success with p2c72?
I tried, but it fails. Doesn't throw any error but gets stuck in the boot and eventually reboots in twrp.
My only doubt is how does it know that the phone is p2c72? The build.prop says p2a42 so does the app thinks that its p2142 and wrongly patch it?
Is this just for experimenting or is there any advantage using 2 os same time? Isn't this can be cause a heat problem because of the more cpu/ram usage?
Can't find supported version of app! Can anyone here help me out wuth version?
---------- Post added at 04:29 AM ---------- Previous post was at 04:20 AM ----------
911-Future_Maker said:
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
Not able to find the version as mentioned. Tried newer version but not supported.
Multuboot log uploaded.
What to do for setting up kernel in 2nd step?
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
muniphs said:
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
Click to expand...
Click to collapse
Try different version.
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
muniphs said:
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
I had tried r201.
Click to expand...
Click to collapse
ViperOS for markw is here!
Thanks to qwertyTom, karevn, Razziell, Anomalchik,TheScarastic for working on the source code for MARKW.
Kernel: Nosgoth V3 +
Security system from Dec'17
Current version 24/12/2017: Final
Highlights:
1) Beautiful animations.
2) Beautiful design.
3) Advanced functionality settings.
4) Shuster.
5) Very fast fingerprint scanner. (Personally, tester's fingerprint scanner fires very quickly, faster than on other OSes)
Changelog:<full>
Code:
24-12-17
-Final version
-Enabled camera2api (hal3)
28-11-2017
* kernel/xiaomi/markw/
5ccdc6f core_ctl: disable at config [Nikolay Karev]
5b37dcc DTS housekeeping [Nikolay Karev]
70a3c66 Merge branch 'core_ctl' into experimental_work [Nikolay Karev]
Downloads:
20171224-Server, MD5:
20171224-Gdrive
20171128-Gdrive
20171116-Gdrive
Original Thread: 4pda
Final update announcement!
Shared here instead of ROM section as sources are not disclosed.
Hello my Friend,
Please share screenshots for this ROM.
Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse
You'll find screenshots on 4pda thread.
I haven't tried this rom yet. In distant future, maybe. I'll post my own screenshots then, and move this thread on rom section.
Here you go...
Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse
How is battery life brother?
saravuthream said:
How is battery life brother?
Click to expand...
Click to collapse
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.
I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
kibria.mgk said:
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.
Click to expand...
Click to collapse
BJumperBR said:
I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
Click to expand...
Click to collapse
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?
Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
kibria.mgk said:
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?
Click to expand...
Click to collapse
Nice rom. But Vpapers did not work.
BJumperBR said:
Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
Click to expand...
Click to collapse
Many thanks. Applied rom in data slot booted up successfully.
BJumperBR said:
Here you go...
Click to expand...
Click to collapse
Thank you friend!
New 281117 build.
Download: Server, Gdrive
Changelog: <textfile>
hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version
lovekobeme said:
hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version
Click to expand...
Click to collapse
Have you checked the settings in Developers option? You can switch default usb option there.
kibria.mgk said:
Have you checked the settings in Developers option? You can switch default usb option there.
Click to expand...
Click to collapse
Yeah,i try it to solved that,thanks.
New 20171222 build is up, comes with hal3.
Download: server
BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Hi. Im new to flashing and I want to use the dual boot. Where can I download it and how can I use it? A thread for our device would be nice. Thanks
I tried to download the latest build from qwertytom.cloudapp.net but the site can't be reached. Is there another download link?