Database Info

[MOD][2015-08-29] MultiROM v32

​(Click on the image above to download my MultiROM Manager App)​MultiROM for the Samsung Galaxy S3 i9305, brought to you by Alexander_the_B0ss​
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm 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.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S3 4G. It can boot any Android ROM . Besides booting from device's internal memory, MultiROM could boot from external SD card(untested). The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system.
Features:
* Multiboot any number of Android ROMs (as many as your internal memory can hold)
* Restore nandroid backup as secondary ROM (damn useful feature)
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. I personally can't stress enough for you people to make nandroids becuase you never know.
Installation
Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app Install my modified app and select MultiROM and recovery on the Install/Update card the app is still in alpha, so don't select install, use manual install below. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM itself - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel (Only TWO: AGNi PureCM or AGNi PureSTOCK) - Download the ZIP file and flash it in recovery (seems like kexec-hardboot isn't activated by psndna88, so menu won't show up on boot)
*Downloads in Post #2*
If your MAIN ROM is TouchWiz or TouchWiz based, please use AGNi PureSTOCK kexec-hardboot status unknown, someone with stock rom please install app and tell me if kexec-hardboot is enabled.
If your MAIN ROM is not TouchWiz, but CM or AOSP (basically custom rom except MIUI) use AGNi PureCM no kexec-hardboot, tested.
You current rom will not be erased by the installation.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card (UNTESTED)
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - Add ROM to boot manager
List ROMs - List installed ROMs and manage them
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - Well, settings
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Screenshots
Application
Recovery (Sorry for pictures...)
Bonus pic(zoom to see the RGBG-Matrix (PenTile))
My Homescreen and Lockscreen (for those interested)
Big thanks to Tasssadar for this awesome utility.
XDA:DevDB Information
MultiROM, multiboot tool for Samsung Galaxy S3 4G (i9305), Tool/Utility for the Samsung Galaxy S III I9300
Contributors
Alexander_the_B0ss
Version Information
Status: Beta
Current Beta Version: v32
Beta Release Date: 2015-08-30
Created 2015-08-29
Last Updated 2015-09-02

Reserved
DOWNLOADS
MultiROM itself: HERE (Check NOTE 2 below for testing zip)
Uninstaller: HERE
Recovery: HERE
Note 1: For recovery use 720x1280 multirom theme from here.
Note 2:
MultiROM Installer with MultiROMManager app and TWRP theme installation testing zip here. Basically what this zip does is, after MultiROM is installed, it copies to system/app my own version of MultiROM Manger to support i9305, then copies to the internal sdcard the theme for TWRP and sets the correct attributes.

What is that? I dont understand

a possibility to install more than just one operating system

Quick update for you guys:
Recovery works, but the theme is kinda weird, so use the theme provided for 'perfect' recovery
MultiROM menu won't show on boot, sent PM to Tassadar for help request. Meanwhile, i am trying to modify MultiROM Manager app to support i9305 to possibly have a workaround for the menu not showing up.
Stay tuned for more development and an OP update after everything is working. CYA

Another quick update for the ones interested in the project. I have succesfully compiled MultiROM Manger app that detects our device (after twenty attempts, then gave up and updated Android Studio to the latest version and redownloaded Android SDK and NDK. First attempt after reinstall worked).The APK fresh from the oven is here. This represents a milestone in MultiROM development because with the app now detecting the device one can avoid the boot menu not showing bug. BUT WAIT, THERE'S MORE
The bug i talked about is related to kernel, because the app doesn't detect kexec-hardboot.
Stay tuned for updated OP soon™.

Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom

fs71gh said:
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM

Alexander_the_B0ss said:
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Click to expand...
Click to collapse
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4

fs71gh said:
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
Click to expand...
Click to collapse
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom

Alexander_the_B0ss said:
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
I guess the problem is with the rom specifically (some things left out while porting), as I got your your apk working with two other cm11 roms.

@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned

il3gal said:
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
Click to expand...
Click to collapse
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.

Alexander_the_B0ss said:
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Click to expand...
Click to collapse
Thanks for your "talk with ROM Developers". Hope kexec-hardpatch is enabled (if I am right) soon and we will have boot menu working

@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305

il3gal said:
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
Click to expand...
Click to collapse
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.

Alexander_the_B0ss said:
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Click to expand...
Click to collapse
Get well brother.

Get well soon friend

any news ?????

hi, does this work on the older i9300 model (3g)?

[STABLE] EFIDroid MultiBooting on Nokia X2 [PORTED by yoAeroA00]

/include/disclaimer or warning.h
/*
* Your warranty is not void as I Think!!
*
* 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 Port
* 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 $ Lot
* But I will always be here to HELP! You...
*/
yO Guys..
To Support the Project PM me but if you are not a Developer than Press Thumps Up! :good: Button for Encouraging..:good::fingers-crossed:
I @yoAeroA00 and @m11kkaa has spended two Days to Successfully Port it to Nokia X2 so you better try it out...
If you wan't any feature to be added in EFIDroid than you are specially welcomed:good:​
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, m11kkaa, Nokia X2 Users and Fan's...
Source Code: https://github.com/efidroid/device/tree/nokia/ara
Version Information
Status: Stable
Created 2017-01-14
Last Updated 2017-01-21

Let's Continue
Table of Contents
1> About EFIDroid
2> How to install EFIDroid on any Supported Device
3> Configuring new ROMs from the APP before Installation
4> Adding a System to the newly created ROM Slot
5> MultiBooting into your newly created ROM
6> FAQ
About EFIDroid
As @m11kkaa said EFIDroid is a easy to use, powerful 2ndstage-bootloader based on EDKII(UEFI).
It can be installed one-click with the EFIDroidManager App. You can Add/RemoveEdit Multiboot ROM's.
There's no special support needed by ROM's or RecoveryTools(no kexec etc).
And I think @yoAeroA00 EFIDroid is a relatively new Multiboot solution for Snapdragon SOC based mobile devices which is based on the EFI implementation by Intel (EDK2).
In last few month's 90% of the Developers has just drop out for no Reasons. Without these drop-out's it could gain a Huge Success.
For more information , please visit to the Github WIKI and for support, please visit EFIDroid Slack. @m11kkaa and I @yoAeroA00 will always be on Slack Community to Help you Porting it to your Devices or Help you a little bit.:silly:
How to install EFIDroid on any Supported Device
> You can Download EFIDroid Manager App from Google Play.
> After installing EFIDroid Manager App Go to Install/Update..
> Then Click Install:
{
"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"
}
> It should be Successfully Installed!
Configuring new ROMs from the APP before Installation
Note: You need to configure the system before installing any new ROM for Multibooting.
> Before you do any of this you should have a ROM .zip file Handy on your SD card (/storage/sdcard1/ and !!NOT!! /sdcard!).
> To Add a ROM Slot got to "Operating Systems" List and click on the FAB (Floating Action Button)..
> Choose an ICON for your new ROM Slot..:good:
> Choose in the screen /data/media/0/multiboot or any other on screen places as a location for your ROM Slot.
> Enter a name and description for your ROM.
> You can leave the partitions as they are (Schema LoopSystem + BindOther) or modify their names or sizes.
> If you need your own custom replacements than configure them as per your needs in the Replacement Tab.
> Press the tick in the top right corner if you have finished setting up things.
> Now you can see that your newly created ROM Slot is in the "Operating Systems" list.
> Then Reboot to See the EFIDroid's Magic!:silly:
Adding a System to the newly created ROM Slot
Note: Once you are in the UEFI, you can navigate around with Volume Down to go Down, Volume Up to go Up and the Power Button to confirm your Selection.
> To flash a ROM select the empty slot, select TWRP (Internal) and then press Power Button.
> Next select your newly created ROM Slot.
> You will be now landed in TWRP and be greeted with a warning about keeping the System Partition ReadOnly. Swipe the Slider at the bottom to Acknowledge it.
> I will highly Recommend you to format all the Partitions(System, Data, Cache) to EXT4 or any file System before you Continue to Install any ROM..
> Click Install, select the Micro SDcard at the Storage tab and then navigate to the directory where your ROM .zip is placed.
> Select your ROM .zip file ****!-ROM.zip.
> Disable the Zip file signature verification and slide the Confirmation Bar.
> If Everything is good then you can Reboot!
MultiBooting into your newly created ROM
> Select your new ROM and press the Power Button. Do not be put off because of the long “Booting <ROMName>” screen as your ROM will open & play the boot animation very late (Unfortunately for only the First time).
> Aaaand Finally we are in the New ROM!
FAQ
Note: If you have any questions, please ask in the This Forum thread or PM me
Q.1> This is a UEFI port, can we port Windows?
> Not, till Yet but with your support we can easily Port it.
Q.2> Can I still use fastboot after installing this?
> If you flash to the boot/recovery partitions, UEFI will be overwritten.(dd in Android/Recovery instead) all other partitions will work as usual.
Q.3> I FOUND A BUG, what should I do now?
>Report it on Github. If there already is an issue for your bug and you don't have anything useful to add, just hit the thumbs-up button. This way I know how many people are affected and can adjust my priority list. I will not keep track of all bugs reported in posts of this thread. If you want a bug to get fixed, report it on Github.
​[email protected]​

yUP Two...
:fingers-crossed::good:

Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind

netradip said:
Why you not start your new project to fixing ril and camera on cm13 and los 14 by your hacking mind
Click to expand...
Click to collapse
he's not ROM builder but kernel builder :laugh:

yoAeroA00 said:
yO Guys..
Currently Testing..
To Support the Project PM me but if you are not a Developer than Press Thanks! Button for Encouraging..:good::fingers-crossed:​
XDA:DevDB Information
EFIDroid for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, yoAeroA00, Nokia X2 Users and Fan's...
Source Code: http://Coming Soon...
Version Information
Status: Testing
Created 2017-01-14
Last Updated 2017-01-14
Click to expand...
Click to collapse
Could you please fix bugs on the new Lineage OS ?

Multi rom on 2,2gb is bad idea

thinhx2 said:
Multi rom on 2,2gb is bad idea
Click to expand...
Click to collapse
It is not multi ROM Bro. It is Grub bootloader through which I can even boot from a system image file stored in a folder on sdcard... And even boot Linux on the Mobile(Need's to be Ported First!)....
If anyone wan't to help me than PM me so that we can give it a start...

KenX2 said:
Could you please fix bugs on the new Lineage OS ?
Click to expand...
Click to collapse
Yes, but only those bugs related to kernel...

How to you add config of X2 to EFIDroid?

i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file

thinhx2 said:
i'm building efidroid
source: https://github.com/thinhx2/device @yoAeroA00
I need you phone to take file,i build done lk.img but i need 1 nokia x2 to read file
Click to expand...
Click to collapse
No need Bro I have successfully made EFIDroid for Nokia X2...

after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.

frnsl3 said:
after install this my sdcard not detected on twrp and stock ROM. But sdcard read on cm12, i have change my sdcard still got this problem. On stock rom i have clean flash trough NCS.
Click to expand...
Click to collapse
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
My SD card could be detected in TWRP and CM12, but it's mounted Read-Only, I can not add any file or remove any file.
I tried to connect it to my PC and format it or use the " Check " inside tool then It's had worked correctly but the problem happens again when I reboot my phone
How can I fix this ?

yoAeroA00 said:
Hmm you have followed wrong steps while installing EFIDroid..
Uninstall it and see if your problem still persists..[emoji44] [emoji6]
Sent from my ara using XDA-Developers Legacy app
Click to expand...
Click to collapse
all i need is just repartition my sdcard bro :silly::silly:, just install efidroid its get partition error. now working as usual :victory:

@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
Click to expand...
Click to collapse
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?

symbuzzer said:
@yoAeroA00 can you share direct image file, and "how to install manually" steps for advanced users like me?
---------- Post added at 11:15 AM ---------- Previous post was at 10:58 AM ----------
"https://github.com/efidroid/files/releases/download/builds/otapackage-20170120-nokia_ara.zip"
files already found. can you help with manual installation steps?
Click to expand...
Click to collapse
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3

yoAeroA00 said:
got to https://slack-redir.net/link?url=ht...ndroid/software-hacking/efidroid-t3447466&v=3
Click to expand...
Click to collapse
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?

symbuzzer said:
No, I didnt mean that.
- I flashed lk.img via fastboot flash boot lk.img
- I can reach efidroid's menu
- But I can't add installed rom and twrp recovery from there
(I can't use efidroid's android app, because of my data partition is encrypted - it show's not supported message when I click install button)
So is there any advanced way to add my rom and recovery manually, like editing a xml based config file etc?
Click to expand...
Click to collapse
Ohh... You should flash uefi_boot.img not lk.img and currently EFIDroid is in development so you can only add ROMs by using it's app and soon I will write a tutorial on how to install ROMs on EFIDroid...using app[emoji6]
Sent from my ara using XDA-Developers Legacy app

[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 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