[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Samsung Tab S2 - Galaxy Tab S2 Original Android Development

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Samsung Tab S2 - Galaxy Tab S2 Original Android Development

{
"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 Samsung Tab S2. 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 250+ supported devices and their variations.
Information:
I have managed to support for Samsung Tab S2 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 (gts28vewifi) 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-omega-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 HereCheers ! we are officially supported
Note: You can download any version since "9.3.0.r6.g553fe6d3"
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
Samsung Tab S2 Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/791
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Samsung Tab S2, Tool/Utility for the Samsung Galaxy Tab S2
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/dc612b46f492d078b8743de165a2fec33612743f
Version Information
Status: Stable
Current Stable Version: 9.3.0.r6.g553fe6d3
Created 2017-10-03
Last Updated 2017-10-03

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

possible to add support for gts210vewifi (tab s2 9.6 wifi)

adoe said:
possible to add support for gts210vewifi (tab s2 9.6 wifi)
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
Tar added gts210vewifi

Working good

@yshalsager
I know I'm late to the game. But Thank you for bringing this updated MultiRom to our Tabs!!! :highfive:
I haven't had a phone or Tab that was supported in a long time. Just finished an install on the 710 with stock and Lineage. All seems to be going well.
I had to root using SU through TWRP. The App couldn't install properly. Magisk might have worked through the App. But I prefer SU.
Thanks again!!

engine95 said:
@yshalsager
I know I'm late to the game. But Thank you for bringing this updated MultiRom to our Tabs!!! :highfive:
I haven't had a phone or Tab that was supported in a long time. Just finished an install on the 710 with stock and Lineage. All seems to be going well.
I had to root using SU through TWRP. The App couldn't install properly. Magisk might have worked through the App. But I prefer SU.
Thanks again!!
Click to expand...
Click to collapse
It's my pleasure mate, If need to add any device just tell me

yshalsager said:
It's my pleasure mate, If need to add any device just tell me
Click to expand...
Click to collapse
Can you add support for T715 (gts28ltexx) ?

tranthaison2000 said:
Can you add support for T715 (gts28ltexx) ?
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 the logs

tranthaison2000 said:
Here is the logs
Click to expand...
Click to collapse
I'll add it soon

tranthaison2000 said:
Here is the logs
Click to expand...
Click to collapse
It's already added https://github.com/yshalsager/DualB...devices/samsung/05_galaxy_tab_tablet.yml#L431
So, change product name in build.prop to gts28ltexx.

Sm-t817t us t-mobile

Can you add the 810?

Related

[DualBoot] DualBootPatcher - a much simpler dual boot solution for Android One device

{
"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 Android One devices Link
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.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
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 Stock ROM, I highly recommend installing Stock 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
cm-13-20160118-sprout4.zip
would create a new
cm-13-20160118-sprout4_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 as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.

XDA:DevDB Information
DualBootPatcher - a much simpler dual boot solution for Android One devices, ROM for the OEM Cross Device Development
Contributors
Anik_khan, chenxiaolong
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2016-01-20
Created 2016-01-20
Last Updated 2016-01-22

Reserved

Great work @Anik_khan thanks for porting for sprout
Sent from my Nexus 5X using Tapatalk

Dude that was awesome, will it work for both sprout4 and sprout8?

:good: It's Awesome bro.. Very interesting.. :good: :good: and thank you for your support

Hell thats SoooogoooD...

hp5942 said:
Dude that was awesome, will it work for both sprout4 and sprout8?
Click to expand...
Click to collapse
Yep it will! all android one varients

Great job, nice to see that it's up !

Awesome Dude
And add "Android One" to tag list

Name any Custom kernels for dual boot support plz

?......
Sharing apps not working..not show on 2cd rom..... Anyone try sharing apps?

Can't Boot in Data Slot ROM Stuck On Boot Logo
Please Help

You did a great work thanks...........

sweet how does it work

Sharing apps not working
Show update ramdisk
Then show,
The ramdisk failed to update ....,
Plz help

thanks for that

Secondary ROM upgrade
I have a flashable zip for update of secondary ROM (in data slot 1)
How do i install that update?
there is an option 'primary ROM upgrade' but no 'secondary ROM upgrade'

very delighted. finally can be realized in the boot multiple sprouts. thank you for your hard work and team developer
---------- Post added at 04:14 PM ---------- Previous post was at 04:14 PM ----------
you rock ! bro ... awesome

Can we Dual Boot Stock ROM (6.0.1) and CM13?
Hey Guys, I just wanted to know that, Can we Dual Boot Stock Rom (6.0.1) with CM13 ? If anyone has tried doing it please let me know ?Coz I watched Video by #Coreman on YouTube abt Dual Booting Of ANDROID ONE and in that Video he said that we can Dual Boot Stock Rom only with MIUI ROM So if anyone knows please Let me know ? Thank You !

How to install gapps and other zips on secondary ROM ,dataslot.

[APP](DualBootPatcher) Dualboot/Multiboot for Infinix HOT 2

{
"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:
I have managed to add support for Infinix HOT 2 to the DualBootPatcher App and have compiled a test apk.
It's awesome and useful for testing out roms or if you want, switching ROMS.
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.
Click to expand...
Click to collapse
Requirements:
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - in the download section.
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
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock 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.
Click to expand...
Click to collapse
How to use the App ?
Before you start using the app, take note of these:
- Some ROMs will fail to install in the in-app zip installer. Unlike TWRP, all errors (even smallest ones) in the updater-script causes the installation to fail. You can either use a working updater-script from another rom or flash the patched zip in TWRP.
- Some roms like Infinix 5.1 make External Storage the default disk. That also removes the writing access to the Internal storage. So, any attempt to install a secondary ROM to /data/media will likely fail. The solution is to remove your external storage (SD Card), install the rom and put it back (unless you want to install to the external storage itself).
- Leaks happen if you use xposed in some roms.
NOTE: IF YOU DOWNLOADED THE APP BEFORE JULY 28, 2016; PLEASE RE-DOWNLOAD IT IN DOWNLOADS SECTION. IT IS A NEW VERSION WITH MORE SUPPORT AND FIXES.
NOTE 2: Before you start, it's important to change ro.product.device value to d5110_infinix in your build.prop, if you don't do this, you'll face errors. But if errors still happen, then flash it in TWRP.
If you have an Android 5.1 ROM as primary (the one you're currently using):
1) Download, install and open the app
2) 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!
3) Now swipe again and click on "Patch Zip". Click the big pink add (+) button and select the ROM you want to patch and use as Dual/Multiboot.
3) Select either "Infinix HOT 2/Infinix ROM" or "Infinix HOT 2/Android One" in the first drop down menu (according to the partition scheme you have, Infinix ROM partition have system on block 18; Android One have it on block 23). Then select the partition configuration (see more details below for this) in the next drop down menu. I suggest you choose either "Data slot" or "Extsd slot". Give a random number where it states "Enter an ID".
4) Click continue and select where to save the patched file.
5) 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.
6) The app will patch the zip. When done, go back to "ROMs".
7) Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
8) Locate the file you have patched in step 6. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like Cyanogenmod-12.1_20160724_d5110_infinix_data-slot-2.zip).
9) 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. But I didn't test that.
10) Upon finition, 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.
If you have Android 6.0 as primary (your current rom):
1) Download the apk file in downloads section
2) Follow steps above to patch the zip. Make sure you set kernel when the app asks you to. It is important to do that. You can manually set it by clicking on the three dots on the primary rom, scroll down and choose "set kernel".
3) Now when you finished patching it. Don't flash it in the in-app flasher.
4) Boot to TWRP recovery (TWRP 3.0.2 recommended). Don't wipe anything. Just click install zip and chose the patched zip. Wait till the end.
5) Now after the installation. Just reboot and install the apk file on the newly installed ROM and you can switch roms.
Warning: If you don't flash in TWRP while using Android 6.0, you can't switch newly installed roms!!!
Partitions Configurations:
These are places where you can install secondary roms. In our case, I'm affraid it's limited to DATA SLOTS and EXTSD SLOTS. Which means you can only install roms to your Data partition (pratically your internal storage) and your SD Card.
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. This one installs to the System partition slot.
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. Our HOT 2 system partition size is about 2.5GB on Infinix ROM. You can probably install two light ROMs (like cyanogenmod and its variants) to it. But I haven't tested it.
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. Our HOT 2's cache partition is about 250MB which is not enough to install a rom on.
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: Same as the above, but it installs the ROMs to your external SD. Make sure you have backed up your data first!
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:
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:
Download the apk file: DualBootPatcher_X510.apk (6.8MB)
WARNING: Do not use other builds other than this apk file. Official releases don't have Hot 2 support yet! I'm waiting for @chenxiaolong to add support for our device to the main repo so that it will be officially supported.
Sources:
My fork of DualBootPatcher with Hot 2 support: https://github.com/Nonta72/DualBootPatcher
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Known 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 as not much space there. just install on /data partition.
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@Anik_khan for the idea and inspiration :laugh:

Whoa!! Amazing, great work bruh!!

Good work bro

Well done bro! Am so impressed and as well excited!
This is what I call development pals!
It took me quite some time to read through - how much more the time it took to make this work!
Great job keep it up....

Anik_khan said:
Good work bro
Click to expand...
Click to collapse
Thank you for the idea, the path and the inspiration
Bolumstar said:
Well done bro! Am so impressed and as well excited!
This is what I call development pals!
It took me quite some time to read through - how much more the time it took to make this work!
Great job keep it up....
Click to expand...
Click to collapse
Thank you.
We will prove Google that we may not have Kernel sources but we still can make our device great.

hey bro help me please?

anzer77 said:
View attachment 3825304
hey bro help me please?
Click to expand...
Click to collapse
Download the new apk file named DualBootPatcher_X510.apk
I have fixed that issue in this new version.
Please take time to read the whole OP if you didn't. It is important !!!

Nice App Bro

@Nonta72
I have some questions, please
1- Does the app use the same kernel for all roms? or it flashes the required kernel while switching roms?
2- If I'm using Android one 6.0 as a primary rom, will USB OTG work in the secondary rom?
3- Does the secondary rom read both internal and external storage?
4- can I use already installed apps like whatsapp, facebook.. etc as shared apps? does this change the location of apps and its data?
5- Just want to make sure, flashing universal OTA updates for android one rom (the zips that is made by Joseph GodSlave on facebook group) works it it is patched for primary rom?
6- If I want to try multiboot then unistall it & remove everything back to the original state, how can this be done?
Thanks for your time and this very useful app ^^

Mysteryagr said:
@Nonta72
I have some questions, please
1- Does the app use the same kernel for all roms? or it flashes the required kernel while switching roms?
Click to expand...
Click to collapse
Answer: Nope ... It flashes the kernel required by each rom when you switch
2- If I'm using Android one 6.0 as a primary rom, will USB OTG work in the secondary rom?
Click to expand...
Click to collapse
Answer: If the secondary rom supports OTG, then yes. Don't forget that only Infinix 5.1 kernel does support it.
3- Does the secondary rom read both internal and external storage?
Click to expand...
Click to collapse
Answer: Yes, all ROMs you install as Dual/Multiboot can read both storages
4- can I use already installed apps like whatsapp, facebook.. etc as shared apps? does this change the location of apps and its data?
Click to expand...
Click to collapse
Answer: Refer to the App Share section of the OP. And yes, you can share all user Apps data. But you need to install Facebook/Whatsapp or whatever on both (or all roms) to be able to use shared data.
5- Just want to make sure, flashing universal OTA updates for android one rom (the zips that is made by Joseph GodSlave on facebook group) works it it is patched for primary rom?
Click to expand...
Click to collapse
Answer: You don't need to patched a primary rom. Just wipe in TWRP and install it, reboot to it, install the dual boot app and patch a secondary or multiboot rom. You can patch it for upgrade, but you shouldn't do that (just to avoid errors).
6- If I want to try multiboot then unistall it & remove everything back to the original state, how can this be done?
Click to expand...
Click to collapse
Answer: If you want to remove multiboot, just delete the multiboot folder on where you installed your second rom. If you instaled the second rom on /system parition, then it will be at /system/multiboot. If you installed it on data partition then it will be on /data/multiboot. You need a root explorer for that. You might also need to remove any multiboot folder on your Internal Storage as well as Externa Storage.

Nonta72 said:
You can patch it for upgrade, but you shouldn't do that (just to avoid errors).
Click to expand...
Click to collapse
Thanks very much, just one point I didn't get it, updating primary rom (Android one) may cause issues?

Mysteryagr said:
Thanks very much, just one point I didn't get it, updating primary rom (Android one) may cause issues?
Click to expand...
Click to collapse
Well, if you have Android One as primary. Then I guess you can update it. It might require stock recovery as well.
But I never tried it.

Nonta72 said:
Well, if you have Android One as primary. Then I guess you can update it. It might require stock recovery as well.
But I never tried it.
Click to expand...
Click to collapse
Joseph the GodSlave makes universal OTA zips which can be flashed via custom recoveries
Thanks very much for this app :good: it is very cool, you can test ported custom roms without touching system partition which make it easier for rom porters

Mysteryagr said:
Joseph the GodSlave makes universal OTA zips which can be flashed via custom recoveries
Thanks very much for this app :good: it is very cool, you can test ported custom roms without touching system partition which make it easier for rom porters
Click to expand...
Click to collapse
Yeah, I made it personally for that purpose. But I later realized it would be useful for other people. So I uploaded it.

Please I don't get it. I have a custom rom alredy and it tells me this.

olalbinx said:
Please I don't get it. I have a custom rom alredy and it tells me this.
Click to expand...
Click to collapse
It takes more time to make things for you to use on your device than reading an OP!
You could have read the post before asking such silly question.
Your issue is fixed in the OP:
NOTE: IF YOU DOWNLOADED THE APP BEFORE JULY 28, 2016; PLEASE RE-DOWNLOAD IT IN DOWNLOADS SECTION. IT IS A NEW VERSION WITH MORE SUPPORT AND FIXES.
NOTE: Before you start, it's important to change ro.product.device value to d5110_infinix in your build.prop, if you don't do this, you'll face errors. But if errors still happen, then flash it in TWRP.
Click to expand...
Click to collapse
IF YOU DON'T READ THE OP, I WILL NOT ANSWER THESE KIND OF REPORTS. IF YOU DON'T HAVE TIME TO READ, THEN I SHOULDN'T WASTE MINE READING FOR YOU!

Followed everything but it didn't work.
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
Followed everything but it didn't work.
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
You didn't probably follow everything!
Because you're on 6.0 and you have to flash the patched zip in TWRP.

Nonta72 said:
You didn't probably follow everything!
Because you're on 6.0 and you have to flash the patched zip in TWRP.
Click to expand...
Click to collapse
That what I have done 3 times with XUI from x551 and XUI from x554 on data slot
And third time on ext sd card...
It fails to switch.
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
That what I have done 3 times with XUI from x551 and XUI from x554 on data slot
And third time on ext sd card...
It fails to switch.
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
Go to internal/multiboot/dual and see if there is a boot.img file inside that folder.

[EXPERIMENTAL][TESTING][29-3-17] MultiRom Latest For kenzo/kate

1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Download Links:
MultiRom Manager App 2.4-rishabhrao

Guys please test this in your Kenzo/Kate and Please tell me how it works

Will it work on 16 gb

pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs

Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc

Does it support the sailfish os?

Is f2fs supported?
Because I can't inject current boot sector

Anyone know if MIUI works?

Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....

SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs

午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !

Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...

SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs

I tried installing a few different ROMs and it always gave an error..
Hope this helps

Doesn't seem it is able to install roms to the sd card

4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...

SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links

[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Xiaomi Mi 6 (sagit)

{
"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 Xiaomi Mi 6 (sagit). 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 Xiaomi Mi 6 (sagit) 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 "sagit" 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-sagit.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 HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r201.ge0c23176"
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
Xiaomi Mi 6 (sagit) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/639
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@dennis46419 for testing and screenshots
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Xiaomi Mi 6 (sagit), Tool/Utility for the Xiaomi Mi 6
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Current Stable Version: 9.2.0.r201.ge0c23176
Stable Release Date: 2017-07-06
Current Beta Version: Build 2
Beta Release Date: 2017-07-03
Created 2017-07-04
Last Updated 2017-07-07

Changelogs:
- 04/07/2017
Initial Release
- 07/07/2017
We are Officially Supported, Pull Request Here

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") == "sagit" || getprop("ro.build.product") == "sagit" || abort("E3004: This package is for device: sagit; this device is " + getprop("ro.product.device") + "."););
assert(sagit.verify_trustzone("TZ.BF.4.0.6-00122") == "1");
ui_print("Target: Xiaomi/lineage_sagit/sagit:7.1.2/NJH47B/8341297e34:userdebug/test-keys");
ifelse(is_mounted("/system"), unmount("/system"));
2- If you want to use MIUI as secondary:
- remove emmc_appsboot.mbn of firmware-update folder
- modify the updater-script:
- remove these lines
Code:
package_extract_file("META-INF/com/miui/miui_update", "/cache/miui_update");
set_metadata("/cache/miui_update", "uid", 0, "gid", 0, "mode", 0555, "capabilities", 0x0);
run_program("/cache/miui_update");
delete("/cache/miui_update");
show_progress(0.600000, 120);
ui_print("Patching system image unconditionally...");
- and these
Code:
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
- Delete files from miui_update folder in META-INF\com\miui
- and flash supersu or magisk after ROM to disable dm-verify

Everything works so far.
I installed LOS in a data-slot and the dual boot works so good.
The only problem that I found was that if I put a pattern lock in LOS, it'll probably overwrite the one in MIUI, so when i booted MIUI again, my pattern lock was not working. Had to delete manually every *.key file in /data/system

LanzoThunder said:
Everything works so far.
I installed LOS in a data-slot and the dual boot works so good.
The only problem that I found was that if I put a pattern lock in LOS, it'll probably overwrite the one in MIUI, so when i booted MIUI again, my pattern lock was not working. Had to delete manually every *.key file in /data/system
Click to expand...
Click to collapse
what is your primary rom? and u use magisk or su?
my second rom is always decrypt so it useless.
thanks for your answer

yshalsager said:
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") == "sagit" || getprop("ro.build.product") == "sagit" || abort("E3004: This package is for device: sagit; this device is " + getprop("ro.product.device") + "."););
assert(sagit.verify_trustzone("TZ.BF.4.0.6-00122") == "1");
ui_print("Target: Xiaomi/lineage_sagit/sagit:7.1.2/NJH47B/8341297e34:userdebug/test-keys");
ifelse(is_mounted("/system"), unmount("/system"));
2- If you want to use MIUI as secondary:
- remove emmc_appsboot.mbn of firmware-update folder
- modify the updater-script:
- remove these lines
Code:
package_extract_file("META-INF/com/miui/miui_update", "/cache/miui_update");
set_metadata("/cache/miui_update", "uid", 0, "gid", 0, "mode", 0555, "capabilities", 0x0);
run_program("/cache/miui_update");
delete("/cache/miui_update");
show_progress(0.600000, 120);
ui_print("Patching system image unconditionally...");
- and these
Code:
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
- Delete files from miui_update folder in META-INF\com\miui
- and flash supersu or magisk after ROM to disable dm-verify
Click to expand...
Click to collapse
Newbie questions.. how can i do no 1 from phone, i unable install lineage to dualboot

Use total commander from PlayStore.
You can edit and save direct the rom.zip you load

ichanz said:
Newbie questions.. how can i do no 1 from phone, i unable install lineage to dualboot
Click to expand...
Click to collapse
Use RAR app

I don't know why but when I try to patch a zip file it won't let me. It says go to settings / installed apps but I've gone already and it's everything with the permissions on. My root method is magisk as I couldn't get root with Ssu. The program doesn't appear in magisk list in the #superuser section...
Even if i go to settings in the dualboot patcher and try to change backup directory it won't let me.

xkim toino said:
I don't know why but when I try to patch a zip file it won't let me. It says go to settings / installed apps but I've gone already and it's everything with the permissions on. My root method is magisk as I couldn't get root with Ssu. The program doesn't appear in magisk list in the #superuser section...
Even if i go to settings in the dualboot patcher and try to change backup directory it won't let me.
Click to expand...
Click to collapse
Go to settings installed apps, enable data see screenshots
and try again. every time recommend if u want flash or use dpt

dennis46419 said:
what is your primary rom? and u use magisk or su?
my second rom is always decrypt so it useless.
thanks for your answer
Click to expand...
Click to collapse
My primary rom is the xiaomi.eu 7.6.29 and I use Magisk v12

thx I am on global beta and every rom is decrypt. will try xiaomi.eu. thx

dennis46419 said:
Go to settings installed apps, enable data see screenshots
and try again. every time recommend if u want flash or use dpt
Click to expand...
Click to collapse
working fine now
Thanks

We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/639

Would be possible to install and boot a ROM from an external USB? Or something like that?

i have FC

N1ldo said:
i have FC
Click to expand...
Click to collapse
Don't use latest version

How long should the reboot after update ramdisk step last ?
I think its stuck

janosch2001 said:
How long should the reboot after update ramdisk step last ?
I think its stuck
Click to expand...
Click to collapse
I have this problem too

janosch2001 said:
How long should the reboot after update ramdisk step last ?
I think its stuck
Click to expand...
Click to collapse
Gamer6302 said:
I have this problem too
Click to expand...
Click to collapse
I'm guessing both of you you are using either China stable/dev or global stable/dev. What causes a boot loop is the encrypted firmware. Unfortunately I have not found a way around this.
To avoid this error you will have to flash one of the following ROMs (sorted by descending alphabetical order):
EPIC ROM
globeROM (My personal favourite)
Multirom
Xiaomi.eu
PS: Remember when flashing any of the above ROMs coming from either China stable/dev or global stable/dev you have to wipe DATA i.e USERDATA on top of wiping the usual stuff when flashing a ROM.
NB : You will get help faster if you join the MI 6 telegram group

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Xiaomi Redmi 4A (rolex)

{
"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 Xiaomi Redmi 4A (rolex). 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 Xiaomi Redmi 4A (rolex) 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 "rolex" 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-rolex.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 HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r201.ge0c23176"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Xiaomi Redmi 4A (rolex) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/639
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@dennis46419 for testing and screenshots
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/UltraDevsApps/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: Build 2
Beta Release Date: 2017-07-03
Created 2017-07-04
Last Updated 2017-07-04

Changelogs:
- 04/07/2017
Initial Release
- 07/07/2017
We are Officially Supported, Pull Request Here

Thaaaaaaaaaaaaaaaaaaaaaaaank u so much <3

Thank you so much. Going to try it asap. Thanks again
Sent from my Redmi 4A using Tapatalk

vaglan said:
Thank you so much. Going to try it asap. Thanks again
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
After updating ram disk and reboot stuck on twrp. Won't reboot to system. Had to restore. Any ideas??. Should i flash rom from that point on skipping all steps described???.(patch zip,sagit,etc???)
Sent from my Redmi 4A using Tapatalk

vaglan said:
After updating ram disk and reboot stuck on twrp. Won't reboot to system. Had to restore. Any ideas??. Should i flash rom from that point on skipping all steps described???.(patch zip,sagit,etc???)
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
Tried again this time didn't reboot after updating ran disk. Did everything as described everything seemed to work fine. Then i reboot and stuck again in recovery. Apparently does not reboot to system
only boots to recovery again. Try please and be more specific in your description. Ensure your device is set to .... sagit???.Is that right?. Big thank anyway
Sent from my Redmi 4A using Tapatalk

vaglan said:
Tried again this time didn't reboot after updating ran disk. Did everything as described everything seemed to work fine. Then i reboot and stuck again in recovery. Apparently does not reboot to system
only boots to recovery again. Try please and be more specific in your description. Ensure your device is set to .... sagit???.Is that right?. Big thank anyway
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
make sure your device is set to "rolex"
sorry it's my mistake

We are Officially Supported !
Don't forget to say thanks to @chenxiaolong
https://github.com/chenxiaolong/DualBootPatcher/pull/639

Of course I did. Reboots directly to twrp and stays there
Sent from my Redmi 4A using Tapatalk

vaglan said:
Of course I did. Reboots directly to twrp and stays there
Click to expand...
Click to collapse
Don't try with miui official as first ROM
Try to use EU rom instead

I am on developer miui. Thanks anyway. I'll probably try with mokee as first room
Sent from my Redmi 4A using Tapatalk

Does it let us pass SafetyNet? (play Pokemon GO and use Snapchat)

CuteFluffy said:
Does it let us pass SafetyNet? (play Pokemon GO and use Snapchat)
Click to expand...
Click to collapse
If you can bypass it in your rom then yes. It does not affect anything on safety net

yshalsager said:
Don't try with miui official as first ROM
Try to use EU rom instead
Click to expand...
Click to collapse
I'm stuck on recovery too What I have to do,to not lose my data?
Yeah I know I had to do a backup...

Kajzer4321 said:
I'm stuck on recovery too What I have to do,to not lose my data?
Yeah I know I had to do a backup...
Click to expand...
Click to collapse
Flash utilities zip and change your rom to primary

yshalsager said:
I am proud to present the first dual boot project for Xiaomi Redmi 4A (rolex). 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 Xiaomi Redmi 4A (rolex) 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 ?
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 "rolex" 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-rolex.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:
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
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 HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r201.ge0c23176"
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Xiaomi Redmi 4A (rolex) Support: https://github.com/chenxiaolong/DualBootPatcher/pull/639
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@dennis46419 for testing and screenshots
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/UltraDevsApps/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: Build 2
Beta Release Date: 2017-07-03
Created 2017-07-04
Last Updated 2017-07-04
Click to expand...
Click to collapse
Hello sir when i had updated the ramdisk and reboot my device it will not boot , it is always going into the recovery please help what to do .
Thanks in advance

Lineageosmod said:
Hello sir when i had updated the ramdisk and reboot my device it will not boot , it is always going into the recovery please help what to do .
Thanks in advance
Click to expand...
Click to collapse
First don't quote the whole op again.
You should use Xiaomi EU rom or multi rom. Because global or China rom won't work because of force encryption

yshalsager said:
First don't quote the whole op again.
You should use Xiaomi EU rom or multi rom. Because global or China rom won't work because of force encryption
Click to expand...
Click to collapse
EU ROM? MULTI ROM? where can i get these roms? link plz

defy_owner said:
EU ROM? MULTI ROM? where can i get these roms? link plz
Click to expand...
Click to collapse
https://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
https://multirom.me/index.php?m=app&a=view&id=76&app=roms

Is there a way to change booting system inside the recovery??

Database Develop

welcome