Develop Bugs

[GUIDE] Dualboot Custom ROMs on L5 and L7

{
"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 L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
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 or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
​

Thanks for the mention

@WinterR test the unofficial snapshot, please

What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1

ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img

Now DualBootPatcher supports the L7 and L7II!!!

I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?

@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )

If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?

So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?

ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).

Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel

Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel

Thread closed as per OP request.
-XDA Staff

[HM 1S/H2A/Redmi 1S] DualbootPatcher - a much simpler dual boot solution

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support Xiaomi Redmi 1s 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 or the old CWM )
2. A ROM
3. The Dualboot Patcher - http://goo.gl/0bcbbN (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 Miui ROM, I highly recommend installing Miui as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Special Thanks
@chenxiaolong for the awesome DualBootPatcher. @TechExhibeo for helping me with builds @Caio99BR for his awsome thread for L3 land L7
​
XDA:DevDB Information
[HM 1S] Dualboot , Tool/Utility for the Xiaomi Redmi 1S
Contributors
onano, chenxiaolong, Caio99BR
Version Information
Status: Testing
Created 2016-01-06
Last Updated 2016-01-06

Reserved

Good Job Brother
keep it UP

how do i backup and restore for each rom?

antr34 said:
how do i backup and restore for each rom?
Click to expand...
Click to collapse
a normal backup from recovery will backup every rom, if you want to backup individually use this tool http://forum.xda-developers.com/showthread.php?t=2491299 by rlorange
edit: Thread updated with much more information

hi OP, nice work.
But found it bit complicated. Is there any video tutorial available ? That would be much easier to understand. ?

Awesome Good job

First of all thanks for the app.
Here's the problem that i have faced....
When i flash the patched rom using in app flashing it failed to install. When flashed through twrp, it's saying that 'the zip file is corrupt'. Can u please give me a solution?
Here's the log file
View attachment MultiBoot.log

nice work bro!!!

vicky romero said:
First of all thanks for the app.
Here's the problem that i have faced....
When i flash the patched rom using in app flashing it failed to install. When flashed through twrp, it's saying that 'the zip file is corrupt'. Can u please give me a solution?
Here's the log file
View attachment 3601075
Click to expand...
Click to collapse
Please provide proper details for which partition you patched the zip

onano said:
Please provide proper details for which partition you patched the zip
Click to expand...
Click to collapse
Dual partition

vicky romero said:
Dual partition
Click to expand...
Click to collapse
i'd refrain from using dual partition on our device, since our /system partition is rather small, i'd say repatch zip to use /data since it will give you much needed space and should work just fine (P.S. i'm using /data as well)
Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install

onano said:
NOTE: If you want to dualboot a Miui ROM, I highly recommend installing Miui as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
First Thank you sir @onano, excuse me sir if we wanna install MIUI as secondary should we simply patch its zip using the DualBoot Patcher app or exe?
If we set any alarm on primary which have support for power off alarm clock [if I set the alarm at 9:00 and at 8:30 I shutdown the device at about 5/4/3(I don't know how many) minutes to the 9:00(8:55/56/57) the device will automatically poweron and the alarm clock will sound normally] could I have any problem? I ask because the situation I've described isn't specified
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
onano said:
i'd refrain from using dual partition on our device, since our /system partition is rather small, i'd say repatch zip to use /data since it will give you much needed space and should work just fine (P.S. i'm using /data as well)
Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Click to expand...
Click to collapse
Can you take the "Simple Announcement) into the first post please?So this mod will be more "safe" and simpler for noobs too

Micky99 said:
First Thank you sir @onano, excuse me sir if we wanna install MIUI as secondary should we simply patch its zip using the DualBoot Patcher app or exe?
If we set any alarm on primary which have support for power off alarm clock [if I set the alarm at 9:00 and at 8:30 I shutdown the device at about 5/4/3(I don't know how many) minutes to the 9:00(8:55/56/57) the device will automatically poweron and the alarm clock will sound normally] could I have any problem? I ask because the situation I've described isn't specified
Click to expand...
Click to collapse
it will work just fine unless you change the default rom after setting alarm, if your default rom is the one on which alarm is added then you should have no problem.
and that toaster and alarm clock was intended as sarcasm
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Micky99 said:
Can you take the "Simple Announcement) into the first post please?So these will be more "safe" and simpler for noobs too
Click to expand...
Click to collapse
Already in Known issues Segment.

Thanks for mention

onano said:
i'd refrain from using dual partition on our device, since our /system partition is rather small, i'd say repatch zip to use /data since it will give you much needed space and should work just fine (P.S. i'm using /data as well)
Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Click to expand...
Click to collapse
Tq for your suggestion but still the same issue. I tried to patch cm12.1 r31. It failed to patch and gave an error code 12.

is there anyway to install rom on second partition of external sd, just in case my 1st partition got corrupted or formatted it wont effect second partition

i have made miui as my primary rom now to flash ota do i need to patch the zip first?

rocknegi said:
i have made miui as my primary rom now to flash ota do i need to patch the zip first?
Click to expand...
Click to collapse
no, if miui is primary rom then no need to patch it . its also on first post
NOTE: If you want to dualboot a Miui ROM, I highly recommend installing Miui as the primary ROM. Otherwise, any mods will need to be patched before flashing.
Click to expand...
Click to collapse

onano said:
no, if miui is primary rom then no need to patch it . its also on first post
Click to expand...
Click to collapse
just want to make it clear, as long as I'm on primary rom, I don't need to patch if I want to install any mod or kernel?

[tool] Multirom v3 , DualBoot Patcher Updated to version v3

{
"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"
}
Multirom v3 , DualBoot Patcher
Now Supports both variants'
now Cm13 is fixed
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* dead phones , car explosion , your phone explosion
* 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 tool
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction :
I'm proud to present you the first dual boot project for the Qualcomm-based Samsung Galaxy S3 Neo and Samsung Galaxy Grand 2 and Galaxy S5 mini ! This will allow any ROMs and as many as you want to be installed at the same time. It works by patching the secondary's ROM installation scripts and boot image to load the ROM files from an alternate location (/system/dual, /cache/dual, and /data/dual). Because of the way this is implemented, no changes to the primary ROM are necessary
About :
Hello guys, as some of you guys know and some of you dont I was working on dual boot and dual boot v1 beta, which was released in our great Telegram group, but not in XDA, because of some reasons and rude MAXSIMUS96 that doesn't have any respect to a great development. But anyway I dont care
Lets Start
Well here's v3 + dbtools removed
patched files are flashable with recovery now
added full s3 neo support :angel:
added full grand 2 support :angel:
added full s5 mini support :angel:
more
Now you can have unlimited ROMs!
Tested with 4 CMROMs + 2 stock ROMs
Here's the topic of the base tool used: Dual Boot Patcher
Here
Make sure you leave a like on the great post of base tool I used here
What is Dual Boot or Multiboot?
DualBooting or multi Booting means having 2 or more ROMs at same time on the phone and choose between what you want to boot on next reboot
Why i need this? Is it even useful???
Yes it is! You can fix offline charging on some ROMs like CM12.1, you can have stock battery life, motion beauty, CM12.1's and CM11's performence at the same time without flashing any of them. Just one click from changing to the ROM you like
Whoa that sounds awesomeeee! is it difficult to install??
In v1 yes, but now on v1.5 i added dbtools (DualBootTools) that make most of things automated and even easier for noobs
now v2 things got even easier full s3 neo support
Any ScreenShots !?
see post #3 attachments
I want to see how it is ! is it possible , any videos ?? !?
see post #3 post
First Things first ! Go and make Backup of your files
Requirements :
an S3 NEO
root access of course
busybox if you are on stock ROM
recovery (twrp 3.0.0 is the best)
brain (the most important)
time and being relaxed
downloaded files
installation tree:
download and preparing files
setting kernel
patching the ROM
flashing
switching ROM
updating ramdisk
extras...
done enjoying
Explaining the tools
First: dbtools (removed due v2)
DualBootPatcher:
the great app mentiond above that made dualbooting possible
installation :
Now we know all about the tools,so it's time to use our brain
Step 1
download and install DualbootPatcher app
if you are in motion rom do this
if you are on motion rom install Motion fix zip at downloads section . it will change device codename back to s3ve3g
Step 2
Open the app
Slide the menu and go to ROMs
It will request for root access
Allow the root access
and a message will ask about to set the kernel
Select "set now" and after it said kernel set now
Step 3
reboot your device
Now after device is turned on
Go to the app and navigate "Patch Zip File" from the menu
and tap that + button select zip of ROM you want to patch
A window will come up and if you see in "your device selected by default" you done everything right.
then:
If you are CMuser ( means you have a cm12.1 , cm11 or ... on your primary rom)
and want to install another cyanogeonmod rom (cm11 , cm12.1 ...)
Select the partition configuration as "Secondary"
If you are trying to install another ROM that has a huge system
Select partiton configuration as "data slot" and select an ID for the ROM
better to be a number
(It will be installed on data partition this means it will use the device internal storage space )
and select continue and set where to place patched file .
you can add more files to patch there .
and after you are ready to patch the files tap that tick button in action bar
to start patching
Step 4
After you patched the zip ROM go ahead and navigate to ROMs from the menu
select button down corner and select patched zip you patched
and then select keep location (or if you want you can change the location ) and add more patched zips or tap the up corner tick to start install
note : if any thing wrong happend PM me on telegram and send me multiboot.log in internal storage.
Step 5
after ROM is installed
it should be selected the installed rom .
tap and switch to primary rom
now use three dot on side of primary and select update ram disk
and then select reboot now
now after device rebooted go back to the app navigate to roms
now use three dot on side of new ROM you installed and select update ram disk
after it said done
select the rom you installed . ( tap on the icon of it or name )
( if you saw a message about checksum select continue )
reboot the device and see the magic !!!!
your new ROM is booting !!!!
Cool, let's stop enjoying and continue
Step 6
now after your new ROM booted
take your time to setup the device
and go and install dualboot patcher app again
now open the app
Go to ROMs and allow root access and
now use three dot menu in side of primary ROM and select update ramdisk
now use three dot in side of new ROM and select update ramdisk
and reboot
Step 7
now ENJOY your dual booted phone
for now on you just need to select the ROM and boot into it
it doesnt need updating ramdisk any more.
now go to the browser and navigate to this topic and leave a thanks
it helps to keep up the work
How to flash a kernel gapps, camera fix, etc.?
Just patch the file to same partition configuration and flash with app
or patch it with recovery tools and flash
How to flash a kernel gapps, camera fix, etc. on primary rom ?
Just patch the file to primary configuration and flash with app
or patch it with recovery tools and flash
How to boot into other rom if you have boot loop with the current rom ?
boot into recovery twrp 3 and select images , navigate to /sdcard/multiboot/ and you see your ROMS listed in folder , like primary , dual , etc .... open the folder of ROM you desire to boot and flash boot.img to boot partition and reboot the phone
How to Wipe the roms ?
go to rom options in dualboot app select wipe rom and tick all of them and done .
or use the dualbootpatcher utility
How to use dualbootpatcher utility ?
flash in the recovery and BOOOOM !
Thanks & credits
It's all done now, thanks for reading carefully
Please at least leave a THANKS to the topic, it make me feel better and work harder on v2 for our device.
I can't receive any donation due to my country. It will be really nice if you send me donations with google gift cards
credits : DualBootPatcher Developer : @chenxiaolong
@LGaljo for his great help about fixing grammar mistakes and thanks to @Swp1996 for testing on grand 2 and thanks to @sasukesama for testing and helping with s5 mini and thanks to @ziad311 for testing v2 & thanks too @German Developer for video tutorial And @zaworka for testing and helping to bring this to lte users
hitting thanks button isn't that hard guys
Version Information
note SEANDROID ENFORCING is not a bug it's needed so please don't try to edit the work without permission or try to fix SEANDROID ENFORCING!!!!
What is working and what is not working on the ROMs?
Everything works great
Only bug is about CM11 :
Files created by CM11 ROM can't be opended with the other ROM :B
That's only problem .
Status : stable
version : 3
dbtools version : removed in v2

added s5 mini to the app go to main topic
here are downloads on Main topic post 2
Main Topic
Code:
v3
added s3ve3gdd ( fixed )
added s5 mini lte version
new design ( im sorry for v2.7 bad design )
fixed cm13 completely
added db-wiki
--------------------------------
v2.7
added in app tut
added fixes for cm13 possibility fix ( my device doesn’t have cm13 so i cant test it )
--------------------------------
v2.6
added new design
--------------------------------
v2.5
optimized Samsung devices
--------------------------------
v2.4
fixes
added multi patch ( more then 2 )
--------------------------------
v2.3
security updates
--------------------------------
v2.2
added support s5 mini
--------------------------------
v2.1
added grand 2 device support
added grand 2 motion fix
--------------------------------
v2
files are flashable with recovery now
dbtools removed
easier to install
update to last sources
new design
fixed partitions
added full s3 neo support
--------------------------------
v1.5
Now you can have unlimited ROMs!
bug fix with system partiton
added data slot support (fixed)

this post will be the ROM suggestions and combinations and screenshots
here is a video by @German Developer
here is a video by @German Developer https://www.youtube.com/watch?v=ePRdE1OzRWE
my own best :
stock or motion as primary cm12.1 as other
app data sharing is on beta DONT USE IT TILL V2 . ( it make apps use same data )
any tw rom or cm13 should be as primary to work !

can i use "*#9900# debug settings-high-reboot" ?
wtf? i cant flash cm13 to dual

Hi. Sounds like a great thing you present here! Does this release also work for S5 mini G800F? Or will it in the future? Thanks!

Ahmetay said:
can i use "*#9900# debug settings-high-reboot" ?
wtf? i cant flash cm13 to dual
Click to expand...
Click to collapse
Yes you can
And you can't use cm13 as dual it must be the primary ROM in order to daul boot it
---------- Post added at 06:05 AM ---------- Previous post was at 06:02 AM ----------
Goofy42 said:
Hi. Sounds like a great thing you present here! Does this release also work for S5 mini G800F? Or will it in the future? Thanks!
Click to expand...
Click to collapse
Its only for Qualcomm devices so no g800f support sadly : (

Awesome, thanks for doing great job.

bill_kevin said:
Awesome, thanks for doing great job.
Click to expand...
Click to collapse
im glad to help you guys ,,, development in here is like a desert ... i will try to help u guys because we have motion rom based on s5 mini for galaxy s3 neo & grand 2

pac rom worked from external sd, just wow.

Ahmetay said:
pac rom worked from external sd, just wow.
Click to expand...
Click to collapse
And its very fast

I can't sucessfully work
There is no cm 13 on my roms

bill_kevin said:
I can't sucessfully work
There is no cm 13 on my roms
Click to expand...
Click to collapse
cm13 should be on primary till i fix it . u can install pac rom for now ...

any updates???

No hope for a 800F version?

Good news for lte users , after working on the other variant i able to add all variants

It can be installed in the g800m Model ?

Did I get this right and G800F is now supported?
Did anybody on CM13 (hennymc) try to install the patcher?
It sounds like a great tool to check out other ROMs.
Respect to the dev, if that is working!

Goofy42 said:
Did I get this right and G800F is now supported?
Did anybody on CM13 (hennymc) try to install the patcher?
It sounds like a great tool to check out other ROMs.
Respect to the dev, if that is working!
Click to expand...
Click to collapse
Yes, it is working on the G800F. I'm using CM13 as primary :fingers-crossed::good:

Goofy42 said:
Did I get this right and G800F is now supported?
Did anybody on CM13 (hennymc) try to install the patcher?
It sounds like a great tool to check out other ROMs.
Respect to the dev, if that is working!
Click to expand...
Click to collapse
Yes you heard right

Hello, I'm reading this discussion with interest.
Once the device is rooted and recovery installed, can I maintain the original rom as primary (possibly with unroot) ?
The intention would be to have my mobile as standard when using for business and pass to CM 13 during my spare time.
Thanks

[MOD][APR 11][DEV] MultiROM v33

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Omni TWRP - https://github.com/lj50036/platform_manifest_twrp_omni (branch twrp-6.0)​
Donations
[MENTION=3418703"Tasssadar[/MENTION] would be glad if you could spare a few bucks. You can use either paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris. And if you want to donate me for porting the updated version of MultiROM, PM me .
Thanks to all donors, it is much appreciated ​
XDA:DevDB Information
MultiROM Xperia Z1, Tool/Utility for the Sony Xperia Z1
Contributors
aquaboy11
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-12

Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk

drakonizer said:
Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.

aquaboy11 said:
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.
Click to expand...
Click to collapse
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?

drakonizer said:
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?
Click to expand...
Click to collapse
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.

aquaboy11 said:
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.
Click to expand...
Click to collapse
So you mean the recovery? I've got that working too, seems like we're both stuck at the same point...unfortunately we don't have the sources of the old multirom v30x.

Is it only me? I cannot find download links for your version

Hitman73 said:
Is it only me? I cannot find download links for your version
Click to expand...
Click to collapse
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs

drakonizer said:
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs
Click to expand...
Click to collapse
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.

aquaboy11 said:
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.
Click to expand...
Click to collapse
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.

drakonizer said:
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.
Click to expand...
Click to collapse
MultiROM v30 boots fine.
I used Sony's device tree
mr_init_devices.c
Everything from BoardConfig.mk after line 41.
I could give porting kexec to MM a shot when I have some spare time.

Hi. I experienced a problem entering the recovery. My device stuck at the Sony symbol displayed an the orange LED when I try to enter. Before I updated my recovery I used the one from v30 thread without any problems. Any idea where the problem is?
Thanks in advance!

LB multirom
Hello, I have a small question ...
If I install MultiROM v33 on my Xperia Z (LB) "locked bootloader",
can i install secondary ROMs for unlocked bootloader ???
thank you

Is this still being worked on?

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For OnePlus 5 (cheeseburger)

{
"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 Oneplus 5. 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 Oneplus 5 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 (OnePlus5) 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-cheeseburger-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r221.g4661ff8e"
Screenshots:
In screenshots tab​No Screenshots available 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
One Plus 5 Support: https://github.com/chenxiaolong/DualBootPatcher/pull/642
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For OnePlus 5 (cheeseburger), Tool/Utility for the OnePlus 5
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r221.g4661ff8e
Stable Release Date: 2017-07-08
Created 2017-07-07
Last Updated 2017-07-08

Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" || abort("E3004: This package is for device: cheeseburger; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- This won't work on stock OOS because of encryption.
3- Here's perfect 100% Working guide by @prile97 Here

Changelogs:
- 07/07/2017
Initial Release
- 08/07/2017
We are Officially Supported, Pull Request Here
Featured on XDA Portal

Woww.. Itz so soon.!!!

Stuck in Boot screen after updating ramdisk and rebooting.
Oos 4.5.5 and latest magisk 13!
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

+1

I'll be getting my OnePlus 5 most likely monday by the FedEx date. I'm so glad to see this available for this device. I had some issues with my Nexus 6P and running this. I love to flash different roms to see all the different options and this will be fantastic.

stuck in boot screen after updating ramdisk.
edit: can't install xXx rom anymore.

So the app was randomly removed from the magiskSU root list and the app isn't requesting root access back at all. I cleared data, cache and uninstalled but it still won't request root access.
Flashing the patched ZIP through TWRP installs it but it won't boot the system, stuck on OnePlus logo power by Android.
Only fix is to flash the utlities ZIP and choose to boot from primary ROM again, I tried stock OOS, custom OOS with AROMA and also RR as secondary ROM but none worked.

Stuck in boot screen after updating randisk. Solved rebooting in TWRP and dirty flashing full Oxygen OOS flashable zip and Super Su in one shot. After this I loosed TWRP, there were stock one again, so flashed TWRP again.
From my OP5.

fmotta said:
Stuck in Boot screen after updating ramdisk and rebooting.
Oos 4.5.5 and latest magisk 13!
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk
Click to expand...
Click to collapse
Interceptor777 said:
So the app was randomly removed from the magiskSU root list and the app isn't requesting root access back at all. I cleared data, cache and uninstalled but it still won't request root access.
Flashing the patched ZIP through TWRP installs it but it won't boot the system, stuck on OnePlus logo power by Android.
Only fix is to flash the utlities ZIP and choose to boot from primary ROM again, I tried stock OOS, custom OOS with AROMA and also RR as secondary ROM but none worked.
Click to expand...
Click to collapse
I need some logs. Please flash this and attach the log
https://dbp.noobdev.io/misc/getlogs/GetLogs-20161128-1.zip

Are you guys encrypted or decrypted? I had the stuck on boot screen after updating ramdisk while I was encrypted.
But I don't want to try again now that I am decrypted :crying: I

Here you are

fmotta said:
Here you are
Click to expand...
Click to collapse
Please test this build
https://transfer.sh/uyzD0/Android_GUI-debug.apk

Same as before. 5 fast vibrations and reboot to recovery.

Thanks for it.. But will wait for multirom..

fmotta said:
Same as before. 5 fast vibrations and reboot to recovery.
Click to expand...
Click to collapse
Can you try with any custom rom as first rom?

Good job mate !
I updated the ramdisk thing and after i managed to get out of the bootloop now i'm unable to use wifi and fingerprint sensor
Don't try this

wow! this is amazing work!
it's like what we used to do with multi-Rom @ Nexus devices... Bravo!

GMX1PT said:
Good job mate !
I updated the ramdisk thing and after i managed to get out of the bootloop now i'm unable to use wifi and fingerprint sensor
Don't try this
Click to expand...
Click to collapse
Can you explain more?