Boot multiple roms on nexus 6p using Dual boot patcher! - Nexus 6P General

Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...

Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?

Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.

Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.

DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.

OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?

t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?

DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.

t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)

DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!

t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary

Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.

How do I switch roms

All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).

What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?

DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.

Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!

DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.

Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?

DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.

Related

▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!

▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!
THIS IS A TUTORIAL TO GET CWM ROMS UP AND RUNNING ON UR RHODIUM
SO i felt completely compelled to share my amazing experience and results with my CWM rom!!!!
i almost always try to keep the development process here away from other sites
if you want a REALLY GOOD WORKING version of android on your device without trying NAND ... follow my instructions...
first off i have a ATT Tilt 2 i have been using with this..
to find anything you need to know on android for our phones go HERE
(Neopeek site)
any size card should do for runing CWM builds,,, i however am runnig an 8gb class 4 sdhc and all is well
MY recommended partition sizes... (i set 300mb as all my EXT2 partitions just to make calculating it easier...)
(primary) FAT32 - storage for music videos pics etc... rest of space
(primary) EXT2 - 200-300mb (system) holds rom build... none are over 250mb
(primary) EXT2 - 200-300mb (data) data for android... i believe is the space for app install... so bigger is better..
(primary) EXT2 - 50-100mb (cache) like ram sorta...
with these sizes... worryin about the size of the rom will not matter ..
look on the site link i posted above on how to install and use CWM if you havent before... (dont worry newbs... its easier then everyone makes it seem...)
with CWM builds the standard Gapps are not included...
THIS SITE is the repository to go to... i am using "gapps-hdpi-20101114-signed.zip" but feel free to try others to see if they load...
this is the the most frustrating part of CWM, finding GAPPS that install...
u install them the same way you do a rom... by installing the zip from the sd card...
i do recommend installing gapps zip after you have already installed the rom and booted and restarted android a couple of times
otherwise i recommend THIS ROM as it is the one i use... i know it is only Froyo but it has a themed gingerbread taskbar with black pull down so it still looks nice!!!
lastly
((((technically test kernel.. so not recommended!!... but proven to fix screen not coming on problem...))))
for you crazy tester ppl waiting for the day you brick your phone(im totally kidding dont worry newbs) i use the WIS-Tilt2 kernel the newer test one to be specific...
GO HERE
With this kernel my device goes in to deep sleep with the GReen light and wakes up perfect every time!!!!!
the zip is just modules package and a zImage.. just have to replace and boot...
WARNING... when i updated with the working kernel it looked like it wasnt going to work.. didnt seem to be anywhere enough scrolling text and the boot animation barely played and then the screen went black... i played around with the buttons and found the device to be opperating with out the screen on i kept pressing buttons and the screen finally woke up!!!! be patient!!!! after that it worked perfectly everytime...
other tips... for people experiencing wifi unable to scan problem ..
use the Wifi-nvram.txt trick look it up in xda... once command is entered no need to reboot just turn on wifi and connect!!!
i hope that this has been helpful i couldnt find any where that had all the tips and tutorial in one place to get CWM up and running at least once... had to do it trial and error.. hope my hard work will help you newbs out!!! hahaha
---
Here is the CMW version of the normal FRX06 by arrrghhh. Credits to arrrghhh for the build and to preston74 for making it ready for CMW.
G-apps are already included in this build so you don't have to flash them separate.
http://www.multiupload.com/2VS5ZKUFBA
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
http://www.multiupload.com/TQSN4TG28U
Click to expand...
Click to collapse
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Well, i used CWM with an 1GB SD and worked like a charm...
and first time i did it with a 2gb... i just said more cause there is more room for apps... lol
should prolly clarify that...
Trekfan422991 said:
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Click to expand...
Click to collapse
Yes you are doing a good job
I first made a cmw version of frx06 without gapps, but argghhh told me it was ok if I include the gapps, so I did
You may also integrate my link in your first post, then I'll delete my post.
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Well if you run in to any problems the support here is going to be limited.
On the other hand if you use XDAndroid the support here is maximal.
For testing and dev reasons, I will stay with my current build. I quite like my bluetooth.
For any beginners I would very much recommend that you use 'standard' (see intro to android sticky). Well, at least until you are confident you don't need to be hand-guided through this and know what to do if something goes wrong.
ppcfly said:
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Click to expand...
Click to collapse
It actually is pretty easy - you can backup your current system & data partitions, and throw a new build on - if you don't like it, wipe and revert to the backup.
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions - of course, this results in a failure to boot... I like having many builds on my card at one time so I can flip between them - this also makes testing a heckuva lot easier, so heads up folks!
Nice tutorial and thanks for putting my build in it,but you should put proper credits as Neopeek(and his team) made cwm and i made the build you linked(you can avoid doing this)
And it's gingerbread like themed and the theme name is minimal green..
You can avoid doing 300 mb system as almost all the builds are less than 100 mb,so doing it 150mb is good
CWM and loopmounted builds can co-exist.
arrrghhh said:
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions
Click to expand...
Click to collapse
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
i'm trying cwm with frx6 and it keep saying fail rootfs., what am i doing wrong?
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
jellenl said:
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
Click to expand...
Click to collapse
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
drynaps said:
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
Click to expand...
Click to collapse
Damnit, hyc even told me about this - and I forgot about it.
Thanks for mentioning it!
villa15 said:
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
Click to expand...
Click to collapse
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
jellenl said:
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
Click to expand...
Click to collapse
No thats not it. i did just just what u are saying. I even tried the CherryPieV3 and it still installation aborted. I'm using CWM 1.8 could that be the problem
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
bleuleon said:
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
Click to expand...
Click to collapse
Yes, you´re right. But he said that he also tried frx06, and that doesn´t worked for him too, and with the frx06.zip bundle, you don´t need to extract it first (if i'm right ;p)
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
Click to expand...
Click to collapse
I tried to install your CMW version of he Arrghhh FRX06 build but it fails on installing.
I have followed all the steps closely but still can't get it installed.
In the CWM tool when I choose Install zip from SD card and then choosing the FRX06 update the install process starts and within a few seconds aborts.
This is what I see on my screen:
Installing: // sdcard/npkboot/update-frx06.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Using the FRX06 CWM build from this thread with the WIS-Tilt2 kernel.
Does anybody have a clue about why this is not working?

Dual boot for MDK users

[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
So from there, download Dual Boot Switcher app and DualBootUtility zip.
And loki-doki from here.
The unzip whatever ROM you're wanting to dual boot. Go to META-INF/com/google/android/updater-script and edit the updater-script manually. The instructions for that are in the post up top I linked to.
Patch the boot.img with the automatic patcher tool, patch-ramdisk.sh. It will create boot_dualboot.img. I just renamed that to boot.img.
Then I put the new boot.img back into the ROM folder.
Create a file named dualboot.sh, and put this in there dualboot.sh.
Put this file in the base of the ROM folder, the same place where the boot.img is.
Zip this all up. the gapps zip I just patched automatically with the patcher app, also in the downloads from the first link.
Instructions for dual booting
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Follow these steps.
chenxiaolong said:
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Note: Only the secondary ROM and other zips that should be installed for the secondary ROM need to be patched. Nothing needs to be done for the primary ROM.
Boot into your primary ROM and install the Dual Boot Switcher app
Open the app and set the current kernel as the primary kernel (screenshot)
If the primary ROM is TouchWiz, you will need to remove some bloatware. Otherwise, two ROMs won't be able to fit on the /system partition. You can also convert some system apps to user apps with this tool: https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en
Patch the ROM (see the "How to use the patcher" section)
Reboot into recovery
Flash the patched zip files.
Reboot
Install the Dual Boot Switcher app again in the secondary ROM. If you have a locked bootloader, set the kernel for the secondary ROM (just in case).
Enjoy!
Click to expand...
Click to collapse
Then just flash your ROM.zip, gapps.zip, and loki-doki.zip. Don't wipe anything. Just reboot. It should boot into your second ROM. Install the ROM switcher app again, set the current kernel as the secondary kernel.
If you want to boot back into your primary ROM, just pick it in the ROM switcher app.
Note: When manually patching, you can go off the examples, and it makes it easier, BUT be careful because not all updater-scripts are the same. I copied off of aokp.dualboot.patch and it kept ruining my ROM. I could boot into AOKP all day long, but if I tried to boot into HyperDrive, it'd just stick at the Samsung splash screen. I looked over my patched updater-script and there was another line with:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
that I missed. So, just be sure to make a nandroid backup.
I'm including a copy of the AOKP updater-script that I edited. It's for the official 10-18 nightly. I tried to make a patch info file to send to the guy who came up this awesome app/mod, but for some reason I'm just inept in this area. I suck at how-to's as well, but I don't see anyone else trying to explain this for our phone
Since you said you had to do some steps, care to share them for users in general? Might save your inbox from getting slammed.
Well I had to remove/add a few lines to the updater script, which I kept messing up because I seem to get deslycix when reading code at 2 am.
Then the boot.img needs to be patched, but there's a tool for that in the OP of the thread I linked. It will create a file called boot_dualboot.img. I renamed that to just boot.img, and removed the original from the zip.
Then I put dualboot.sh at the base of the ROM zip.
Patched gapps automatically with the patcher tool.
Flashed patched ROM, patched gapps, and loki-doki. Just Google loki-doki, it's the first result.
Patching the boot.img removes loki. Flashing loki-doki will loki the kernel again.
Edit: I'll do up a better How to later. I'm at school right now though.
Sent from your mom's smartphone
Updated OP. If you have any problems, just post and I'll help where I can. I'm no expert, I'm just good at following instructions.
Hey, thanks for doing this thread. How do you remove dual booting when you want your phone back to normal again? haha
Restore a nandroid. Or do a clean flash from recovery and you'll be on one ROM.
Sent from your mom's smartphone
If anyone can do a precise and accurate video tutorial for this, that would be awesome! I'm more of a visual learner.
That is way beyond my level of knowledge lol.
Sent from your mom's smartphone
thats pretty ill. i personally do not see a reason to do it, but i like that its possible, LOL

[Tutorial]DUAL BOOT Roms Patcher[COOLPAD Note 3 & Lite]

Coolpad Note 3 and lite are now officially supported by DualBootPatcher
Steps to use DualBootPatcher :-
# Downlad and install latest DualBootPatcher
apk from here
https://dbp.noobdev.io/
# Open it -> Go to roms in option
Grant all the permission,set the kernal
and update the ramdisk in primary rom.
# Go to settings and install boot ui.
# Now go to patch zip file -> Add flashable zip
# Select the rom.zip , googleapps.zip ,
patches.zip , addons.zip which you want to
use as secondary rom.
Select your device , data slot , (ext sd slot not
tested).
And apply patch.
# After patch completes install all the zip files
you have patched from twrp.
# If u want to use inapp flasher of
DualBootPatcher,
flash this zip before u use the app.
https://mega.nz/#!xhgQERbL!5UEPeMbbHU9kxLBmWLpUpsosRk4lGmtr0S3pWgkbdeU
#Note : works only if your rom supports init.d or su.d
# After the flash completes, hit reboot ==>> u
will be in the second rom.
# To switch rom :- Methods(any one works )
1. Using boot ui :u get option to switch rom during reboot
2. Select the rom in the App and reboot.
3. Install the boot.img in internal -> mutiboot folder from recovery and reboot
# If something goes wrong :-
Go to recovery -> install boot.img of primary
rom.
Note : 1. Not all the roms are tested.
Do At Your Own Risk
2. Note 3 plus also added but not tested
those who are interested can test and
coment here
CREDITS:-
#Chenxialong : For the incredible app
@Uday Hegde (For this Guide)
@kuberrocks96 (personally tested on Coolpad Note 3 Lite)
UPDATE : WORKING ON COOLPAD NOTE 3 , LITE AND PLUS
Working On Coolpad Note 3 as well
Note 3 plus try..
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
RaghuStar said:
Well got interested...did the steps all...
And given all permissions...
When I try to install ROM as secondary (tried cm 12.1) while installing rom I got error saying unable to symblink and other as failed to extract data file to /data...any idea how to fix this...
Thanks in advance
File uploaded for reference crash log and a screenshot..
Click to expand...
Click to collapse
did u tried to flash from recovery..?
Uday Hegde said:
did u tried to flash from recovery..?
Click to expand...
Click to collapse
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
RaghuStar said:
Oh well no..flashed it from the app...as secondary ROM..
And I was able successfully boot android lollipop stockrom and Nougat Resurrection remix custom ROM as dual..I had no problem with that...and for RR ROM I selected extsd slot...so basically I could install in SD card...but failed in other slots..(slot 1.2.3 or secondary did not work for me.) And I did not try in data...
Click to expand...
Click to collapse
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Uday Hegde said:
It is bcoz
Secondary slot is of system partition
and other 3 slots are of cache partition
as there is not enough space in all these 4 slots,it wont work.
And data slot is working for all roms.Extsd slot is working only for some roms as I tested.
And it is better to use twrp to flash.
no probleam if ur rom supports init.d (just flash the fix)otherwise u may face an assue of in switching rom,need to flash boot image of secondary rom manually.
Click to expand...
Click to collapse
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
RaghuStar said:
Well twarp is for primary ROM right!! How can I flash it for secondary ROM??? Is their any option for that...because if I want to flash gapps for my second ROM..all I did was first patching the ROM selecting same slot in which my RR ROM is present and then flashing the file by logging into the primary ROM..
Click to expand...
Click to collapse
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Uday Hegde said:
what the app does is it inserts some binary to handle the process of flashing into the zip files.
patch the zip files such as gapps or patches to the rom and give the same id as the rom,it will be flashed to ur rom(to which ro has that id).
and flashing the patched zip files from recovery will not touch the primary rom.binary will create create a chroot environment at /data/local/multiboot/slot-id/ and everything will be flashed into it...
Click to expand...
Click to collapse
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
RaghuStar said:
Thanks a lot bro...
It works in coolpad note 3 plus..so u can edit ur blog saying it is tested in cpn3+ also...all the best...
If I get any qustn I will post it...thank u very much bro
Click to expand...
Click to collapse
sure bro
Thanks sir for the guide
yadavdharmendar said:
Thanks sir for the guide
Click to expand...
Click to collapse
All thanks to @Uday Hegde
Unable to dual boot RR with MIUI 8.1
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
unable to update ramdisk on cpn3. why?
ripon_b said:
unable to update ramdisk on cpn3. why?
Click to expand...
Click to collapse
may be ur using nougat rom.
its bcoz of special characters in board name.
to solve
backup your boot.img
unpack it using any boot.img unpack tool
edit boot.img-board using text editor
clear all the lines in that file
repack boot.img and flash
now it will not fail to update
abhishek_patil said:
Am trying to dual boot RR with MIUI 8 but its showing same error that was posted by RaghuStar. Even tried by TWRP recovery, but it showing same error, what should I do?
What exactly going wrong?
Am using Coolpad Note 3 Lite
Click to expand...
Click to collapse
use data slot or external sd card
I have tried that also..
abhishek_patil said:
I have tried that also..
Click to expand...
Click to collapse
u have log file of the error..??
Uday Hegde said:
u have log file of the error..??
Click to expand...
Click to collapse
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
abhishek_patil said:
Actually it was deleted, but according to my research, for dual boot, ram disk should be updated in both ROMs, but I noticed a problem with nougat ROM, I am unable to update RAMDisk in Nougat ROM, so when I dual boot it with MIUI, it goes in Boot Loop. But how can I update RAMDisk in Nougat?
Click to expand...
Click to collapse
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Uday Hegde said:
check above comnts for update ramdisk in nougat roms.
but its not necessary to update ramdisk,it is required only to use boot ui.
Click to expand...
Click to collapse
Okay, i have following Questions.
1) Which software should I use to unzip img file.
2) I am unable to dual boot it with MM V010 on CN3L,
It showing same error posted by @RaghuStar.
3) Avoiding use of BootUI will prevent BootLoop?
4) Is there any effect of kernel version?

[PATCHER] DualBootPatcher for J510

WELCOME​
Dual Boot Patcher​
I am proud to present to you, Dual Boot Patcher for j510!​
Code:
Disclaimer:
I am not responsible for any bricked devices lost data or national disasters. Use at your own risk
Features:
Run two or more roms on your device at the same time!
Able to patch rom zips, custom kernels, gapps, supersu zips etc
Clean Material UI
Boot UI which allows you to select ROM at boot
App Sharing between Roms
Backup and Restore roms
Note: If the app is saying that this device is not supported and you have j510, edit your build.prop to set ro.build.product and ro.product.device to "j5xnlte". Then reboot. The app should be working. Do this only if you have j510. If you set the values improperly, installing a dual boot zip will hard brick your device.
TUTORIAL:
NOTE:Make a full nandroid backup before proceeding!!
Install your first ROM normally(from TWRP). It is recommended that if you want to multiboot an AROMA ROM, you should install it first(as primary). If you want to make your current rom as primary, skip this step.
Download and install the apk provided in the attachments.
Download the second rom.
Open the Dual Boot Patcher app, in the left swipe-in menu, select ROM section
It will ask you to set the kernel for Primary Rom. press Ok
Then go to "Patch zip file" menu, and click on the red "add" button
Then select "Add flashable zip". It will ask you to select a rom zip. Browse to your downloaded ROM and long-press to select it.
It will then ask you where to install it. You can Either Install it in "Secondary" which will install the Rom in system partition(use this if you have enough space on your system partition( at least 1.1 GB for AOSP roms and 1.8 GB for Touchwiz Roms). If you dont have enough space on your system partition, install it in Data or ext sd slot.(Note that installing in Data will take up space from your internal memory. DO not select the "multi slots"! they are for other devices
Click on OK. it will ask you the location of target file, just click on select to use defaults.
if you have any additional zips(such as gapps or supersu) patch them all using the above method. Select the same setting you used for the ROM!
After you have added all your zips, Click on the tick in the upper right corner and the patching will begin!
After Patching is done, reboot to recovery. DO NOT WIPE ANYTHING. Just install the zips you just patched(they will have "Dual" or "Data slot" written in front of their names.
After installation is complete, click reboot, and it will reboot to your newly installed ROM. Set up the rom normally. After setup is complete, install the DualBootPatcher apk.
Now you can select whichever ROM you want in the app. Just select it and restart!
From now onwards patch every zip with dual boot patcher before installing!
Boot UI
If you want Boot ui, follow these steps:
Go to roms section of the app. Press the 3 dots next to your first rom then scroll down and select update ramdisk. then press ok. It will ask you to reboot. just press reboot later
Repeat the same with other roms
Then go to settings and select install Boot ui.
Download Apk
DualBootUtilities
If anything goes wrong with the DualBoot keep the utilities zip in your sdcard. You can flash it in recovery(AROMA only). It allows you to wipe any rom installed on your device or switch to any rom.
Download Utilities
UPDATES
Update1:
Performance Improvements
Now you can restore backup to primary and secondary locations too(previously gave error)
Update2:
Added j5xnltexx to supported device codenames
Performance improvements
This app is not mine. I added support for dual boot on J5 2016.
This app is licensed under GPL. As per its requirements, here is the source code:
https://github.com/RIPT1DE/DualBootPatcher
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Boot ui not supported ?
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
This not work either
Moshifan100 said:
Hello. I looked at your GitHub, and you have made no changes to it.
You should do that, as currently the GitHub is a fork with absolutely no changes to the original one.
Click to expand...
Click to collapse
No changes to the master branch as I am keeping it in sync with the original developer's master. The changes are in branch j510fn_support.
Wizardlysense said:
Boot ui not supported ?
Click to expand...
Click to collapse
Bro change ro.build.product and ro.product.device in build. Prop to j5xnlte.
Wizardlysense said:
This not work either
Click to expand...
Click to collapse
Also if the above doesn't work send me the update.log
__riptide__ said:
Also if the above doesn't work send me the update.log
Click to expand...
Click to collapse
Here
Wizardlysense said:
Here
Click to expand...
Click to collapse
Did you give storage and root permission?
__riptide__ said:
Did you give storage and root permission?
Click to expand...
Click to collapse
Yup
Wizardlysense said:
Yup
Click to expand...
Click to collapse
Ok. Then can you send me a copy of your build. Prop?
Guyz, this is perfectly working for me.
Just follow the instructions.
@Wizardlysense I have edited my post with further instructions. Try those. If it's still not working, we will and figure it out.
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Incredible! Just incredible! Works fine with a5ux and lineage os!
GlitchWolf said:
Hello everyone !
I edit my build.prop but dont work... Help me if you can and thank you of the app
Thanks !
Click to expand...
Click to collapse
What is the error?
doc_elias said:
Work for me after edit build.prop
Boot ui auto booted to which ramdisk update last.no option for selection which one is to boot
Click to expand...
Click to collapse
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
gzdc said:
Incredible! Just incredible! Works fine with a5ux and lineage os!
Click to expand...
Click to collapse
Same here.. Great Work! Amazing!
__riptide__ said:
The boot ui has a countdown timer. There are two buttons on the boot ui. Clock the left one which is "cancel". It will then give you the option to switch rom
Click to expand...
Click to collapse
Everything working fine.

[app][official] DUALBOOT PATCHER FOR SAMSUNG GALAXY ACE 4 ( SM-G316HU/ S DUOS 3 )

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.
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 (Supported SM-G316HU. Such as Touchwiz Galaxy J3(Lollipop) & J100H(Kitkat), CM 11, 12, 13, MIUI, FlymeOS)
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What Can Be Done:
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
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 (greatlte) 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-20171004-greatlte-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.
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
Quote:
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.
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:
https://dbp.noobdev.io/downloads
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Galaxy ACE 4(SM-G316HU) Source:
https://github.com/chenxiaolong/DualBootPatcher/pull/1090
Known issues:
- You have to tell me !!!
Contributors
yshalsager, chenxiaolong, dbp007
Version Information
Status: Stable
[Reserved]
[Reserved]
ROMS
Which custom roms do have for this device SM-G316HU
please provide link @HWDEV
---------- Post added at 02:43 PM ---------- Previous post was at 02:07 PM ----------
can't update ramdisk
it shows 'failed to update ramdisk'
pulmit said:
Which custom roms do have for this device SM-G316HU
please provide link @HWDEV
---------- Post added at 02:43 PM ---------- Previous post was at 02:07 PM ----------
can't update ramdisk
it shows 'failed to update ramdisk'
Click to expand...
Click to collapse
Visit this link :
https://forum.xda-developers.com/ace-4/general/master-thread-samsung-galaxy-ace4-s-t3631541
HWDEV said:
Visit this link :
https://forum.xda-developers.com/ace-4/general/master-thread-samsung-galaxy-ace4-s-t3631541
Click to expand...
Click to collapse
Thats ok for roms
But what about failed to update ramdisk error
pulmit said:
Thats ok for roms
But what about failed to update ramdisk error
Click to expand...
Click to collapse
Give the screenshoots. & multiboot.log file.
HWDEV said:
Give the screenshoots. & multiboot.log file.
Click to expand...
Click to collapse
previously i was using rooted stock rom when it showed ramdisk error
then i used custom rom lineage os 14 the ramdisk updated successfully
i flashed secondary rom and it was flashed successfully
after flashing the secondary rom the device was not booting
so i wiped the system and flashed the custom rom
i will again use the app and try to resolve the issue

Categories

Resources