Database Info

[MI 4i/ferrari][OFFICIAL] DualbootPatcher - a much simpler dual boot solution

{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support Xiaomi Mi 4i.
I am not the creator, just the supporter
Disclaimer
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 features included in this ROM before flashing 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.
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 Miui ROM, I highly recommend installing Miui as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_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.
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
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?
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:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Special Thanks
@chenxiaolong for the awesome DualBootPatcher. @onano for intial works on Xiaomi devices, helping me with builds and also his thread template for Redmi 1S
@thewisenerd for initial bringing up Dual Boot Patcher to Xiaomi Mi 4i
XDA:DevDB Information
[MI 4i/ferrari][OFFICIAL] DualbootPatcher - a much simpler dual boot solution, ROM for the Xiaomi Mi 4i
Contributors
faizauthar12, thewisenerd, chenxiaolong, onano
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-12-05
Last Updated 2016-12-07​

Reserved
/* FAQ */
Q: is that possible to dual booting Miui with cm/AOSP rom?
A: yes it's possible, the primary rom must be Miui
Q: can i dual boot Miui and Miui?
A: you can't , while installing the secondary rom, you will got an error or something like that
Q: can we dual boot Miui 6 with anything or vice versa?
A: no you can't it will flash / patch the current primary Miui rom with the rom flashable zip
Q: is there is anyone do Miui and cm?
A: yes is it, go here (give him a thanks tho)
a video tutorial by @sharan.nyn
is here

- Will try this later. But anyways, thanks in advance!

Did anyone try this....?? I tried and getting an error(Unfortunately Dual Boot patcher(Debug) has stopped) while patching the ROM zip file. I am using the unofficial patcher app as advised in the instructions. Official app doesn't have the Mi4i in the device list hence not able to patch the zip. Can anyone please through some light to go forward.

apna.suresh0305 said:
Did anyone try this....?? I tried and getting an error(Unfortunately Dual Boot patcher(Debug) has stopped) while patching the ROM zip file. I am using the unofficial patcher app as advised in the instructions. Official app doesn't have the Mi4i in the device list hence not able to patch the zip. Can anyone please through some light to go forward.
Click to expand...
Click to collapse
Which ROM zip did you try to patch?
I was able to patch cm-12.1 zips correctly. Haven't tried with Marshmallow yet.

Appreciate if we could get the support for Elephone M2 as well....??? Below is the url for device thread.
http://forum.xda-developers.com/elephone-m2
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
thewisenerd said:
Which ROM zip did you try to patch?
I was able to patch cm-12.1 zips correctly. Haven't tried with Marshmallow yet.
Click to expand...
Click to collapse
I tried below mokee official builds...
http://download.mokeedev.com/?device=ferrari&type=release
I did a trick that the patcher is installed in my other mobile "Elephone M2" and patched zip files successfully, then moved those files again to Mi4i and installed. It worked.
Surprisingly i could able to patch from my secondary ROM (Mokee) but not from the primary rom(MIUI). I believe that MIUI rom is not supporting for patching it seems.

apna.suresh0305 said:
Appreciate if we could get the support for Elephone M2 as well....??? Below is the url for device thread.
http://forum.xda-developers.com/elephone-m2
don't spam orig dev section, use private messaging system
---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------
I tried below mokee official builds...
http://download.mokeedev.com/?device=ferrari&type=release
I did a trick that the patcher is installed in my other mobile "Elephone M2" and patched zip files successfully, then moved those files again to Mi4i and installed. It worked.
Surprisingly i could able to patch from my secondary ROM (Mokee) but not from the primary rom(MIUI). I believe that MIUI rom is not supporting for patching it seems.
Click to expand...
Click to collapse
provide logcat if possible

Thanks a lot for this, after years of runing multi boot on laptop, now I can runing multi boot on phone also. I have succses with triple boot install, everything is working well except one little thing: can in-app switch to another rom only if I on primary (RR 5.1.1), but, if on secondary (slim bit 6.0.1) or on data-slot rom (RR 6.0.1), I can switch to another rom only from twrp via flashing boot.img, even DualBootUtility.zip not working.
I have a one question: What is a Leaks app, who cames with DualBoot patcher app?? What means all that notifications/messages MainActivity leaks, leaks this, leaks that, etc... and what mean that message about memory dumping?? Thanks for answer.

cannot flash cm13 as secondary using miui as primary. Please if any body has tried elaborate steps to dualboot.

If you want to install cm13 as a secondary, that mean cm13 will be installed in chroot environment inside your MIUI ROM, exact path is /system/multiboot/dual. MIUI is "little big" rom, did you check how much free space you have in your MIUI /system partition? And what kind of error you got in recovery when you try to flas secondary.
In any case, steps for flashing are:
1. Boot into MIUI
2. Open Dual Boot Patcher app
3. Go to "Patch Zip File" option
4. Add your cm13.zip (and gapps optional), choose "secondary" on popup, if you want to install as a secondary on /system partition of existing rom
5. Press check mark in top right corner to patch zips you added
6. Boot into TWRP and flash cm13-blah-blah-dual.zip (and gapps-blah-blah-dual.zip optional) just normal, as a usually roms.
That's it.

Do i need to patch primary rom also before installing secondary?
I tried to upgrade primary stock rom with primary patched rom, got error cannot flash over rom through Dual Boot Patcher App.
I tried to clean install primary via TWRP, got error Failed to compute sha1sum of boot. Failed to flash zip file.
How do i make it work? Do I keep primary stock ROM as it is (MIUI) or patch primary ROM and flash secondary CM13.

stiw47 said:
Thanks a lot for this, after years of runing multi boot on laptop, now I can runing multi boot on phone also. I have succses with triple boot install, everything is working well except one little thing: can in-app switch to another rom only if I on primary (RR 5.1.1), but, if on secondary (slim bit 6.0.1) or on data-slot rom (RR 6.0.1), I can switch to another rom only from twrp via flashing boot.img, even DualBootUtility.zip not working.
I have a one question: What is a Leaks app, who cames with DualBoot patcher app?? What means all that notifications/messages MainActivity leaks, leaks this, leaks that, etc... and what mean that message about memory dumping?? Thanks for answer.
Click to expand...
Click to collapse
Can you explain the procedure step by step how did you manage to get triple boot ? Thanks

Account removal
Deleted

Is the project still going?
The status is testing from the first time I saw this thread

Hello. Somewhen at begining of this year, I was use some unofficial version of this app on MI 4i, founded here, in this thread, and mentioned version was working properly. Now, I want to fire up multiboot again, but as I see, things was changed here. Actualy, there is not MI 4i as supported device in latest snapshot provided in first post. Can someone give me a link for previous unofficial Dual Boot Patcher app?
Thanks in advance.
EDIT: Sorry, guys, such a stupid from my side. I found an app, in first post ofcourse.

It's possible
Sorry cause double post, but just for info, I successful running a MIUI V8.0.2.0.LXIMIDG Global Stable in dual boot with ResurrectionRemix-M-v5.7.4-20161005-ferrari from @Rohan purohit
Yes, yes, MIUI 8 in combination with M custom ROM on same phone. We already know, if we want to install L or M custom ROM on our phone, we must have 6.x.x firmware as a base. Procedure for making dual boot MIUI 8 + L/M custom ROM is same as usually. Main trick is how to switch ROM. Again, same as usually, but before every switching, you have to flash firmware files from recovery - 6.x.x if you switching to custom ROM and 8.x.x if you switching to MIUI.
Conclusion: I realy don't like MIUI, I am a person who like AOSP way, but MIUI camera is really really great, and some other features are pretty cool, now I have best from both world.
Unfortunately, this thread is little dead , but if you want to setup something like this or similarly, and stuck somewhere, be free to ask here or PM me, and I can write some mini tut with steps.

stiw47 said:
Sorry cause double post, but just for info, I successful running a MIUI V8.0.2.0.LXIMIDG Global Stable in dual boot with ResurrectionRemix-M-v5.7.4-20161005-ferrari from @Rohan purohit
Yes, yes, MIUI 8 in combination with M custom ROM on same phone. We already know, if we want to install L or M custom ROM on our phone, we must have 6.x.x firmware as a base. Procedure for making dual boot MIUI 8 + L/M custom ROM is same as usually. Main trick is how to switch ROM. Again, same as usually, but before every switching, you have to flash firmware files from recovery - 6.x.x if you switching to custom ROM and 8.x.x if you switching to MIUI.
Click to expand...
Click to collapse
Hey I'm trying to do exactly that! But I'm a little confused about what you mentioned - I am currently running MIUI 8 and wanted to flash a custom M ROM with the DualBoot Patcher, do I need to flash MIUI 6 before doing this? Or can I proceed to setting up the dualboot alongside MIUI 8? I also didn't understand what you meant about switching between the ROMs, do I need to flash a different version of MIUI to the MIUI partition every time I want to switch?
Sorry for so many questions, I was just confused about that and really wanted to do this, to get the best both MIUI and clean Android!

fonefan88 said:
Hey I'm trying to do exactly that! But I'm a little confused about what you mentioned - I am currently running MIUI 8 and wanted to flash a custom M ROM with the DualBoot Patcher, do I need to flash MIUI 6 before doing this? Or can I proceed to setting up the dualboot alongside MIUI 8? I also didn't understand what you meant about switching between the ROMs, do I need to flash a different version of MIUI to the MIUI partition every time I want to switch?
Sorry for so many questions, I was just confused about that and really wanted to do this, to get the best both MIUI and clean Android!
Click to expand...
Click to collapse
You should download or transfer a custom rom .zip file (and gapps optional) on your phone
Open Dual Boot Patcher app and patch all .zip files you want to install as a 'Data slot' (be creative and give some name to your data slot, it is mandatory).
After this you will get new .zip files (e.g. Rom-Name-data-slot-name.zip and Gapps-data-slot-name.zip) and this is a whole magic. Those new .zip files have instructions to be installed inside /data/multiboot/data-slot-name folder inside your primary ROM, not inside /system as ussual.
You will get a modded boot.img inside /sdcard/MultiBoot/data-slot-name also, and this boot.img have instructions to boot OS from /data/multiboot/data-slot-name , not from /system as ussual
Before installation of secondary ROM, start DualBoot Patcher app, and set a kernel of MIUI as a primary:
This is not nothing specialy, after this you will get a stock boot.img of MIUI8 inside a /sdcard/MultiBoot/primary, but you'll need it for further booting back to MIUI
Boot into TWRP and install a secondary ROM and gapps, usually as a normal rom and thats it.
***Switching between ROMs***
From MIUI to Custom:​
Boot into TWRP
Install V6.6.10.0.firmware.zip (this is not whole ROM, this is already known firmaware files, here from xda)
Install /sdcard/MultiBoot/data-slot-name/boot.img as => Image => Boot
Reboot System and whoala, you are in custom ROM.
From Custom ROM to MIUI:​
Boot into TWRP
Install V8.0.2.0.firmware.zip (this is not whole ROM, this is same as V6.6.10.0.firmware.zip mentioned above, but with firmware files for MIUI 8, packed by me )
Install /sdcard/MultiBoot/primary/boot.img as => Image => Boot
Reboot System and whoala, you are in MIUI.
I hope, I was helpful

YES that really helped clarify the process, thank you SO MUCH!! I really appreciate it!!

@stiw47
seems you're happy with dual boot patcher
check this out
https://dbp.noobdev.io/
have a nice day

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Nokia X2

{
"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"
}
I am proud to present Dualbootpatcher For Nokia X2. 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
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Nokia X2 to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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 features included in this ROM before flashing 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.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (Nokia_X2) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like lineage-14.1-20170702-UNOFFICIAL-ara.zip_dual).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps 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.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
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.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r221.g4661ff8e"
Screenshots:
In screenshots tab​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Nokia X2 Support: https://github.com/chenxiaolong/DualBootPatcher/pull/642
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Nokia X2, Tool/Utility for the Nokia X2
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r221.g4661ff8e
Stable Release Date: 2017-07-08
Created 2017-07-07
Last Updated 2017-07-08

Notes
1- If flashing Custom ROM Fail :
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "ara" || getprop("ro.build.product") == "ara" || getprop("ro.product.device") == "cm_ara" || getprop("ro.build.product") == "cm_ara" || abort("This package is for device: ara,cm_ara; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- If you faced bootloop after patching ramdisk :
- Restore your current boot.img

Changelogs:
07/07/2017
- Initial Release
08/07/2017
- We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/642

yshalsager said:
07/07/2017
- Initial Release
08/07/2017
- We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/642
Click to expand...
Click to collapse
But we need lineage os 14.1
Can you fix camera bug

j€nish said:
But we need lineage os 14.1
Can you fix camera bug
Click to expand...
Click to collapse
I don't have the device. I borrowed it to make this. Developing cm14.1 will be very hard

yshalsager said:
I don't have the device. I borrowed it to make this. Developing cm14.1 will be very hard
Click to expand...
Click to collapse
But without ROM who use?
Without ROM this borrowing

j€nish said:
But without ROM who use?
Without ROM this borrowing
Click to expand...
Click to collapse
You can dual boot any two roms of available roms of course

yshalsager said:
You can dual boot any two roms of available roms of course
Click to expand...
Click to collapse
This device kernel bad, custom ROM camera quality bad, camera focus bad
Who use this useless custom ROM
If possible to please make Kali Linux for Nokia x2

j€nish said:
This device kernel bad, custom ROM camera quality bad, camera focus bad
Who use this useless custom ROM
If possible to please make Kali Linux for Nokia x2
Click to expand...
Click to collapse
Kali will be useless, no otg support

yshalsager said:
Kali will be useless, no otg support
Click to expand...
Click to collapse
Well, bro Nokia x2 not support
So no need otg feature
But our android haven't Kali Linux features
So can you make
It is. Very new concept ??
Can do this

j€nish said:
Well, bro Nokia x2 not support
So no need otg feature
But our android haven't Kali Linux features
So can you make
It is. Very new concept
Can do this
Click to expand...
Click to collapse
i think Linux deploy is enough

j€nish said:
This device kernel bad, custom ROM camera quality bad, camera focus bad
Who use this useless custom ROM
If possible to please make Kali Linux for Nokia x2
Click to expand...
Click to collapse
But Kali only on 7.0?
Sent from my MI 5 using XDA-Developers Legacy app

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For YU YUREKA BLACK

{
"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"
}
I am proud to present first Dualboot project For YU YUREKA BLACK. 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
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for YU YUREKA BLACK to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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 features included in this ROM before flashing 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.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-garlic-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps 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.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
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.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some ​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
YU YUREKA BLACK Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][SNAPSHOT] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Snapshot
Created 2017-08-19
Last Updated 2017-08-19

Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Changelogs
-19/08/2017
Initial Release, waiting for adding officially

I'm not able to go in fastboot mode since I'm not able to use volume up and power button together. I think there is some issue with it due to which I'm not able to root yureka black (updated on nougat) plz help

Hi.
Can I install a non-rooted Rom as second Rom? ... Is the dualbootapp needed? Will phone reboot to first Rom when just shut down second Rom?

Hi,
I hoping you can help. I'm getting the following message when I try to flash the zip file. Same message when I use TWRP.
'dual boot patcher failed to extract multiboot files from zip'
Any ideas?
Many Thanks

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Mi 4S (aqua)

{
"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"
}
I am proud to present first Dualboot project For Mi 4S (aqua). 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
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Mi 4S (aqua) to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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 features included in this ROM before flashing 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.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-aqua-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps 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.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
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.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some ​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Mi 4S (aqua) Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Mi 4S (aqua), Tool/Utility for the Xiaomi Mi 4C
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03

Notes
Before you ask for Mi 4C (libra) support, it officially supported !
So just install my APK or use Official Version Here
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Changelogs
-19/08/2017
Initial Release, waiting for adding officially

great...
It's working both bootloader on libra?

hanuraiga said:
great...
It's working both bootloader on libra?
Click to expand...
Click to collapse
Yes both of them are supported in my build. As I said in 2nd post

Could you reupload?

don_kamil said:
Could you reupload?
Click to expand...
Click to collapse
https://dbp.noobdev.io/downloads/

Doesn't work:
- second ROM if you have how first ROM AOSP and second ROM you have Miui
- second ROM if you have how first ROM Miui and second ROM you have Lineageos 15
All other conbinations ROMs works fine in this device if the bootloader firmware is same.

Good work, Thanks

Got bootloop after updating ramdisk.
I'm using LineageOS 14.1 with 8.5.1.0 firmware.

been stuck in bootsplash for 15mins now, same as @CodeingBoy above immediately after updating ramdisk.
gonna wait till half an hour otherwise i quit.
multirom_MI4c_8.4.26_v7.0_b17_56adc950ae

[PATCHER][APP][OFFICIAL] DualBootPatcher For Lenovo Vibe K6 (karate)

{
"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"
}
I am proud to present the first dual boot project for Lenovo Vibe K6 (karate). 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
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Lenovo Vibe K6 (karate) to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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 features included in this ROM before flashing 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.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to "karate" and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like lineage-13.0-20170307-UNOFFICIAL-karate.zip_dual).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
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.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps 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.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
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.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.3.0.r6.g553fe6d3"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Lenovo Vibe K6 (karate) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/791
Known issues:
- You tell me !
Credits:
yshalsager For Adding the device !
@chenxiaolong for the awesome DualBootPatcher.

Notes:
1- If flashing Custom ROM Fail:
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Lenovo K6 Power not supported ?
When I open the app it displays an error message stating : " Cant determine boot partition .... device's codename K33a42 not recognized. "
As far as I know K6 Power's kernel is the same as vibe k6. Both of them have same codename - karate. Hence both devices should be supported.

Please support k6 power k33a42 also

nishadnmanish said:
Please support k6 power k33a42 also
Click to expand...
Click to collapse
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it

yshalsager said:
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it
Click to expand...
Click to collapse
Here is a log file
https://drive.google.com/file/d/0BzcRd6olCOzsT0ZwQ2RWRE52Q2s/view?usp=drivesdk

Magisk is not working with dual boot patcher.. so I edited..
Look into this post..
https://forum.xda-developers.com/showpost.php?p=74467090&postcount=12820
This edited magisk will eork with dual boot patcher..

yshalsager said:
If you have twrp, Flash logs https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
attach tar file and let me add it
Click to expand...
Click to collapse
Please support k6 note

Finally, I found out the way.. to use magisk perfectly in non-primary ROMs of Dual boot patcher..
Guide is here.
https://forum.xda-developers.com/apps/magisk/guide-t3703596
Hopefully it will work with all ROMs!
Tested in my Lenovo k6 power in data ROM.

It does not work with Android 8.1. I cannot even set a kernel. Is there any fix for it?

Thomas_xxxxx said:
It does not work with Android 8.1. I cannot even set a kernel. Is there any fix for it?
Click to expand...
Click to collapse
Oreo isn't supported till now

yshalsager said:
Oreo isn't supported till now
Click to expand...
Click to collapse
Also the karatep or k6 note not supported till now.

yshalsager said:
Oreo isn't supported till now
Click to expand...
Click to collapse
You mean Oreo cannot be primary or secondary ROM? Or both? Because here is shown that there is 8.1 and 7.1.2 dual booted and you say Oreo is not supported -> https://i.imgur.com/4FIt9ga.png

firemax13 said:
Also the karatep or k6 note not supported till now.
Click to expand...
Click to collapse
Give me the logs, I'll add it

Thomas_xxxxx said:
You mean Oreo cannot be primary or secondary ROM? Or both? Because here is shown that there is 8.1 and 7.1.2 dual booted and you say Oreo is not supported -> https://i.imgur.com/4FIt9ga.png
Click to expand...
Click to collapse
It works on few devices as secondary. But for me, It's not working.

yshalsager said:
Give me the logs, I'll add it
Click to expand...
Click to collapse
What logs?

firemax13 said:
What logs?
Click to expand...
Click to collapse
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
Flash the GetLogs zip. The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.

Hello,
I tried this DualBootPatcher on AOSPExtended but when I want to set kernel, it states: "Could not determine the boot partition because this device codename "K33a48" is not recognized." Every solution is appreciated. Here are logs: https://drive.google.com/open?id=1EJuA1Up-5q9ImFhzPVSzfao9pSlAkOar
Thank you.

yshalsager said:
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip
Flash the GetLogs zip. The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.
Click to expand...
Click to collapse
Here's the log.

Thomas_xxxxx said:
I tried this DualBootPatcher on AOSPExtended but when I want to set kernel, it states: "Could not determine the boot partition because this device codename "K33a48" is not recognized." Every solution is appreciated. Here are logs: https://drive.google.com/open?id=1EJuA1Up-5q9ImFhzPVSzfao9pSlAkOar
Click to expand...
Click to collapse
Change it to "karate" It'll work