Database Develop

[Roms]DualRom-The dual booting solution for Incredible. Use any Rom!!(Update)4-26-11

The below info will remain for historical informations but this system has been replaced by a better system found at http://forum.xda-developers.com/showthread.php?t=1100777
DualRom ***Dual boot 2 roms on your Droid Incredible***
Team ADX presents your dual booting solution for the Droid Incredible. Please Read entire post before using any of the zips given. Undo zip in second post to put your phone back to the state it was in before flashing these zips.
I have added some empty shells to allow people to use any rom. See bottom of first posts.
DualRom comes in DualRomSenseFroyo and DualRomCM7. We wanted to give you the option to basically use the opposite of what you would use as your normal rom. CM7 is CM7. It was compiled from CM7 source and only made changes needed for it to boot off interanl storage. SenseFroyo is stock rom with Ziggy's kernel to allow overclocking. I did not remove any bloat since you will have over 5GB's free so there is plenty of room. I don't use sense roms so I'm not familiar with what sense tweaks are out there but I may research and make changes to the sense rom in future updates. I chose these roms because I wanted roms that would be very stable right out of the box. This is a new method for dual booting and there hasn't been any wide testing yet so you should still consider this Beta till there is more feedback. Everything has been stable in the limited testing. All feedback encouraged and appreciated.
DualRom Terminology for this post
PhoneRom - refers to the rom that is installed normally on your phone
InternalRom - refers to the DualRom version that you 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"
}
* Who is Team ADX?
For those that don't know us Team ADX was formed by a few Dev's from the HTC Droid Eris. We collaborate on projects together even though we've all branched to different phones. Team ADX is Conap, Workshed, and Gnarlyc. Conap has the Droid Incredible and will handle most of the support in this thread. The Team ADX account is usually only used for the op and all follow posts will be done with our personall accounts.
* Why would you want 2 roms on your phone?
Sometimes you can't decide between Sense and CM/Aosp roms. Both have thier benifits and both have thier downfalls. Why not have both on your phone. For app developers this is a great solution so that you can easily test your apps on Sense and Aosp roms. Also it's just another cool reason to root right?
* Any downside to this?
The only downside for this is that it uses the entire 6.5Gb of internal storage that the incredible has. The reason it does is because the emmc which includes the 6.5GB of internal storage also includes the 750mb's for the data partition and the 200mb's for the cache partition of the phone. For this reason HTC has locked this from being repartitioned. I did not find a way to unlock it although there probably is. I personally don't use the internal storage on my phone at all since most apps defaut to sdcard. If you don't use or need to use your internal storage this is a great alternative to what you can use it for. I tested many methods which included putting the rom on SD card or rearanging the partitions where the normal rom is stored and I found this method to be most stable and the least intrusive to your normal rom.
* How does it work?
With this DualRom setup you will be able to keep your current rom and even change your current rom on your phone in the normal fashion you are used too. There is a zip file to flash before flashing your DualRom that will set up your current rom to work with DualRom. It only makes minor changes to your current rom and I will explain that during install instructions. The DualRom will then get installed to the internal storage of the phone. An app called DR Reboot written by Conap specifically for this setup will be installed in both roms that will let you boot back and forth between the 2 roms. There will also be zips automatically added to your sd card that will allow you to choose which rom you want to boot to from recovery.
* Is this risky?
With any phone modification done with root there is always risk involved. From my testing I determined the phone would not let me repartition the internal storage therefore not letting me screw up the phone. As long as you use the zips we provide there should be no issues. As always though flash at your own risk!!!!
* Is this compatible with my rom?
DualRom should work with any rom you use. For the DR Reboot app to work you will need a rom with busybox installed but that is pretty standard. If DR Reboot does not work for you you can use recovery to boot back and forth. The zip you flash in recovery only takes a few seconds so this is still a much faster option then doing nandroid/restore's.
* How do I install this? What do the zips do?
The zip files are named with a number to start. Flash in the order of the numbers. All my testing was done with CWM v2.5.1.2.
1DRPrep-setupEMMCforRomFlash.zip We flash this zip first. All it does is change the filesystem of the internal storage partition(6.5gb) from fat32 to ext3. THIS WILL ERASE ALL FILES FROM YOUR INTERNAL STORAGE. Please backup any files you want to keep. This zip can also be used to reformat if you decide you want to switch from one version of DualRom to another(i.e. Sense to CM7). This zip will take a few minutes to flash so be patient.(I know my progress bars don't move right in recovery but it is working).
2SetupPhoneRomForDualBoot.zip We flash this second. This zip will do a couple of things. It installs the app into your current rom that will allow you to boot back and forth. It also backups the boot.img from your current rom to your sdcard so that it can use it when you want to boot back to the Phone Rom. It add's another zip to sdcard that allows you to boot back to Phone Rom from recovery. It also adds an edited vold.fstab to your current rom so that your phone will not complain that it can no longer fine the interal storage since your using it for something else. If you have dualrom already installed and decide to flash another normal rom to your phone you can just re-run this zip after flashing the normal rom.
3DualRomSenseFroyo.zip or 3DualRomCM7.zip These are the actuall roms. They will install the rom to the internal partition and also put a zip on your sdcard that allows you to boot the internal storage rom from recovery if you need too. Please flash only one of these.
* I've installed it now what?
Once you have flashed the first 3 zips your phone is ready to reboot. Reboot the phone and it will boot to the internalrom. This is a first boot so it will take a few minutes but not really longer then the first boot on a normal rom. Once it boots go through the normal setup of the rom. Then you can look in the app drawer and you well see DR Reboot app. I would reccomend placing a shortcut to this on a home screen somewhere for ease of access. Open DR reboot and from there you can reboot to the phone rom, internal rom, or recovery.(See Photo at top of post) You can still use the normal reboot options of the rom if you want to boot back into the same rom you are in. Alternativley you can boot to recovery and flash the bootphonerom.zip or the boot-internal.zip's to boot to either rom. These are a backup mainly in case the DR Reboot app malfunctions (occasionally it fails to flash the boot.img)and you need to get back into one rom or the other. I would not delete them from the sdcard. That's it....use the roms as normal and boot back and forth as you wish.
* My phone won't reboot to the phonerom even after flashing the phonerom.zip in recovery?
This is why we do a nandroid backup. Restore it now and then reflash the 2SetupPhoneRomForDualBoot.zip.
* What about tweaks/zips/themes?
If the phone is booted into either rom then anything you apply will get applied to the rom you are booted in...(i.e. metamorph). Keep in mind I have not tested much as of yet with the internal rom but in theory it will work fine. The phone rom will continue to work as normal. Any flashable tweaks/themes will only affect the phone rom. The install scripts would need to be modified to apply them to the internal rom. It shouldn't be too hard to modify them and I will try to post some instructions on that later.
* What about ADB?
ADB will acess what ever rom you have booted at the time.
* Will this allow us to boot other operating systems(i.e. WM, IOS)?
No they are not bootable on android devices and don't know if they ever will be. This will allow us to boot larger Rom Ports as some of the Rom's are getting larger then our internal storage.
** KEY POINTS TO REMEMBER
1. Everytime you flash a normal rom please flash 2SetupPhoneRomForDualBoot.zip after to update your stored boot.img.
2. Try to stick with more stable tweaks on the internalrom untill we can work out a easy way to wipe data/cache or a way to make a reliable nand.
3. Nandroid is your friend. Don't forget to do your normal Nandroid's in recovery for the phonerom before flashing any zips.
4. Zips are numbered in order so you can flash them in order.
5. Enjoy your 2 roms!!!
** TODO List
1. Make data/cache wipes available
2. Watch to see if the roms sharing the .android_secure folder on sd is going to be a big problem. So far in my testing is has not been an issue.
3. Make some type of Nandroid available...We have a something but it's not very reliable so working on a more stable method.
*Thanks to:
Cyanogenmod for thier great work http://www.cyanogenmod.com/
Htc I guess for sense and for making quality phones.
Ziggy471 for his kernel http://www.ziggy471.com/
TeamADX members for all they do!!!
XDA member unCoRrUpTeD for getting me interested in Dual Booting
Everyone and anyone who contributes to open source projects
Downloads
FLASH AT YOUR OWN RISK
1DRPrep-setupEMMCforRomFlash.zip - THIS ZIP WILL ERASE EVERYTHING ON YOUR INTERNAL STORAGE WHEN FLASHED. YOU HAVE BEEN WARNED MD5-ea34104a4b8ee11ee3d6442c13c0f93c
2SetupPhoneRomForDualBootV2.zip MD5-f2a55ed14f720332cfe9f88d32918a9f
V2 fixes flash_image binary not having execute permissions causing phone to not boot from phone rom to internal rom. Make sure you are on phonerom and reboot to recovery and just flash this zip if you've already installed DualRom.
3DualRomSenseFroyoV2.zip
V2 includes update boot.img that i added in the test zip i posted. That's the only change.
DRSenseUpdatetoV2.zip
If you flashed v1 of sensefroyo you can just flash this to update so you don't need to wipe.
3DualRomCM7v3.zip
v3
Updated to CM7.02 Stable
v2
Adds new boot.img that automatically fixes the filesystem on reboot.
DRCM7v2Update.zip
Updates DRCM7 to v2 with no wipe if you already have DualRomCM7 installed.
How can I use other roms with this?
I made some rom "shells". You can open the zip of the rom you want to use and drag the system and data folders and drop them in the "shell" zip. There is a shell for miui 2.3, cm/aosp 2.3, and Sense 2.2. This way you all have the option to use any rom without me releasing other peoples work.
MIUI-GB-shell.zip
Sense-2.2-shell.zip
CM-AOSP-GB-shell.zip

* What if I want my phone back to normal?
This Zip will completely undo the changes to your phone rom and will reformat your internal storage back to fat32 so it can be used for storage again.
UndoDualRom.Zip
* Nandroid Backup and Restore
DualRomNandroid.zip Boot to your internal rom and then boot to recovery. Then flash this zip in recovery and it will create a folder called DR on your sdcard in /DualRom/backups/. If you want to make multiple backups then you can rename the DR folder to whatever you want. If you want to restore the backup just rename the folder back to DR. If your only making one backup you can leave it named DR. If you make another backup without renaming the folder then it will overwrite the old backup.
DualRomNandroidRestore.zip Guess what this does ...flash this to restore the backup you made with the DualRomNandroid.zip. This script will restore from the DualRom/backups/DR/ folder on your sdcard. Rename whichever backup you want to restore back to DR.
All zips are provide as is. Use at your own risk.
If you have suggestions/ideas/improvements feel free to let us know. I will note here that I have looked at symlinking the database's for mms and phone logs so they would show on both roms but it seems to cause issues. I beleive the issues have something to do with CM7/2.3 databases is not the same as Sense/2.2 database. I know people have had problems when trying to restore that type of data when switching roms so it's probably the same case here. If anyone has idea's or knowledge more in depth on that issue feel free to share!!!!

So how does this work with SMS/phone logs? If I get a text while on one ROM, and switch to the other, will it still be read with the other? Same thing for phone calls.
This looks like a groundbreaking project, and I look forward to trying this out

TheWhiteBandito said:
So how does this work with SMS/phone logs? If I get a text while on one ROM, and switch to the other, will it still be read with the other? Same thing for phone calls.
This looks like a groundbreaking project, and I look forward to trying this out
Click to expand...
Click to collapse
Currently they act independently of each other so you will only see it on the rom booted up. At some point I will attempt to merge them as much as possilbe. I will need to test what backups and databases are compatible between CM and Sense.

Team ADX said:
* Will this allow us to boot other operating systems(i.e. WM, IOS)?
No they are not bootable on android devices and don't know if they ever will be. This will allow us to boot larger Rom Ports as some of the Rom's are getting larger then our internal storage.
Click to expand...
Click to collapse
This sounds sick, especially having the space to port large roms like Sense 3.0! Looking forward to whatever comes out of this.

Wow this is great ill try it out once there's some way to nandroid.

Wow good job guys. Just wanted to give you some props and say ill definitely be watching this thread for updates and sometime soon I will definitely try it out. Keep up the great work, and thanks.
Sent from my ADR6300 using XDA Premium App

kschwarz88 said:
This sounds sick, especially having the space to port large roms like Sense 3.0! Looking forward to whatever comes out of this.
Click to expand...
Click to collapse
Oh yes *licks lips* Sense 3.0, here we come!

r3nz024 said:
Wow this is great ill try it out once there's some way to nandroid.
Click to expand...
Click to collapse
You can nandroid your current rom in recovery as normal and flashing this won't have much affect on your current rom other then adding the app that lets you boot into the other. The only thing you can't back up is the rom on the internal storage. But even if the internal rom goes all crazy on you it won't affect your current rom.

Is there a way to restore the EMMC partition to FAT32 if I decide not to keep the dual ROM functionality? aka: what's a command I could stick inside of a CWM zip to format back to FAT32?

Is this working with the most recent recovery? I know the OP says it was tested with the older 2.X version

jonesh said:
Is there a way to restore the EMMC partition to FAT32 if I decide not to keep the dual ROM functionality? aka: what's a command I could stick inside of a CWM zip to format back to FAT32?
Click to expand...
Click to collapse
I added a zip to return the phone to normal if you wanted to go back. The zip does this for you but if you wanted to change the filesystem back to fat32 manually you would go into recovery and do:
adb shell
parted dev/block/mmcblk0
mkfs
it will prompt you that it will erase all data and type yes and hit enter
then you choose partition number 3 hit enter then type fat32 hit enter and it will reformat to fat32. The zip does this as well as removing the app from the phonerom and the other files that were installed.

chris61292 said:
Is this working with the most recent recovery? I know the OP says it was tested with the older 2.X version
Click to expand...
Click to collapse
I'm use to working with amon's and not CWM so I'm not sure what the changes were. I know they changed the way you mount the partitions so i'm not sure if i did it the old way or knew way. I will check into it and fix it if it needs to be. Are the newer recovery zip's still compatible with the older recoveries I assume?

Wow! Conap is here! All over the dl...... ty u shed, conap, and company

I saw this and got excited for a WP7 dual boot solution :< we can dream can't we?

very cool. OMFGB and OMGB at the same time xD

Team ADX said:
I'm use to working with amon's and not CWM so I'm not sure what the changes were. I know they changed the way you mount the partitions so i'm not sure if i did it the old way or knew way. I will check into it and fix it if it needs to be. Are the newer recovery zip's still compatible with the older recoveries I assume?
Click to expand...
Click to collapse
as long as the old recoveries support edify, there shouldnt be an issue

r2DoesInc said:
as long as the old recoveries support edify, there shouldnt be an issue
Click to expand...
Click to collapse
Thankyou...

So, sacrificing our emmc for a larger partition would also open up options for larger android roms like a full Sense 2.0/3.0 Rom wouldn't it?

phoenixs4r said:
So, sacrificing our emmc for a larger partition would also open up options for larger android roms like a full Sense 2.0/3.0 Rom wouldn't it?
Click to expand...
Click to collapse
Yes room is not an option here. That doesn't mean it is easier to port but room is definitely not an issue. As soon as i can find the links to some of these larger roms i'll look at them although I'm more accustomed to building from source then I am to porting.

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

[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 Here​Cheers ! 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 Here​Cheers ! 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??

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Samsung Tab S2

{
"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 Here​Cheers ! 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?

[Official] Dual Boot Patcher [Mi Max 2 / Oxygen]

{
"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"
}
DUAL BOOT PATCHER​
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. 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.
Warning: This method requires one time factory reset.
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_data-slot.zip file will be created. For example,
Lineage-14.1-oxygen.zip
After patching would create a new
Lineage-14.1-oxygen_data-slot.zip
If you want to root secondary rom, then download Magisk 12.zip given below(Do not use other version, you can update that later from magisk manager app) and patch it like you did with rom
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk 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.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD 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.
Now Let's Start
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc on internal storage. So make sure you moved them or made their backup)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher.
6) Install patched rom as secondary on /system or on /data partition - it's your choice. There is lot of space for 3 roms in /system.
If you want to root secondary ROM and flash patched magiskv12.
7) Select your secondary ROM in ROM list and reboot.
Steps to be followed on Secondary Rom
8) Install Dual Boot Patcher.
9) Install MagiskManager.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
FAQ's (FAQ)
Do I need to wipe again for third or next rom?
No, wiping is only required for one time, you can flash as many roms(your device can handle) after that.
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".
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
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:
First backup all your data including Internal Storage, then boot to TWRP>WIPE>FORMAT DATA then type 'yes' and tap enter. Now reboot and retry DBP.
Source/Credits:
https://dbp.noobdev.io
@chenxiaolong
@bad_request (Thanks for the XDA Post And Guide)
@mario_R (For step by step guide and errors.)
Downloads: https://dbp.noobdev.io/downloads/ and Download latest files
~ Hit Thanks button below if I helped you ~

*Reserved

**Reserved

Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.

drmuruga said:
Already flashed LOS 14.1 and RR as secondary in data slot everything work fine only issue is audio headphone jack not working otherwise cool.
Click to expand...
Click to collapse
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool

I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.

jbmc83 said:
...which is an issue pertaining to the RR custom rom and has nothing to do with this multi boot tool
Click to expand...
Click to collapse
Yes , this tool working great , my problem is known to roms .
Patch roms and files in data slot not secondary slot in which is only one room can boot as secondary. Data slot for multiple roms flashing. And I never update ramdisk which leads to boot into recovery instead of system .

What's the use of dualboot we have only two ROMs to download.. Lol!

Now we should have at least two stable roms to taste this

nikz106 said:
What's the use of dualboot we have only two ROMs to download.. Lol!
Click to expand...
Click to collapse
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!

jbmc83 said:
not quite correct ^^
we have:
miui stable
miui developer
xiaomi.eu
miui pro
miui globe
lineage os 14.1
resurrection remix
so you could try a total of SEVEN different roms with this tool!
Click to expand...
Click to collapse
+1 to this.

Mgphyo126 said:
I just tried last 5 days. When I choose second rom and reboot, it goes into recovery. Can't boot up second rom. Renew primary rom,wipe data and try dbp again and again. But not successed. Now my primary rom is Los 14.1 and trying second rom as miui global dev rom 8.1.11. Please help me.
Click to expand...
Click to collapse
Anyone?

mario_R said:
Anyone?
Click to expand...
Click to collapse
Twrp >> wipe >> format data..
And it's ok now. ??

when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!

DON'T set lock screen !!
you will end up locked away from your primary rom
----------
in my case the primary was globerom and secondary was lineage os
---------
if you already locked from your rom you can boot twrp and open terminal and write
cd data/system
rm *.key
and reboot

kalawy said:
when patching the primary rom (update ramdisk)it reboots to recovery after the vibrations
didn't install any secondery roms -- yet
primary : MIUI globeROM 7.12.21
app version : 9.3.0.r327.gb3914310-snapshot
if it's relevant > i have magisk 15.3 --magisk edits the boot.img > may the issue be related to that ? was i supposed to remove magisk before? magisk in not the problem > i tried with original boot,img with supersu
edit : also i remember formatting the data before flashing this rom .. wil i have to reformat ?! >>>>> seems that miui encrypts the data with every flash !!
edit 2: i skipped ramdisk update for the primary rom and flashed a secondery rom in /system -- so .. is it the format issue ? if i format now will i have to reformat everytime i flash a rom ?? bcoz i clearly remember formatting before installing this primary rom
edit3 : problem solved with formating data again !!
Click to expand...
Click to collapse
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Kapil Tapsi said:
If you want to root secondary rom, then download latest magisk and patch it like you did with rom
Click to expand...
Click to collapse
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide

mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Click to expand...
Click to collapse
I figured that out ... the hard way :crying:

mario_R said:
Good that you solved it. But for your knowledge and to any user: updating RAMDISK is not necessary. It's necessary only for "App sharing" feature, but I don't recommend it because it causes sometimes bootloops on secondary ROM. Even even creator of DualBoot patcher said it may be unstable.
Thanks for mention me in your thread, but remove that line, it will cause bootloop. First you need to patch Magisk_v12.zip and install it, then install latest Magisk_v15.3.zip as a module in MagiskManager. Like I wrote in my guide
Click to expand...
Click to collapse
Thanks mario_R for the guide and trick. I did it hassle free as I already had my internal decrypted. But I noticed some people having problem with installation.

it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??

app share have a high chance of breaking secondery rom