About:
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.
Supported devices:
J500F
J500FN
J500G
J500H
J500M
J500Y
J5008
How to use:
Download and install last apk.
On the app, select "Patch Zip File" from the menu.
Tap on the FAB (+ icon) and select "Add flashable zip" and choose a (secondary) ROM that you want to patch.
Select a partition, and give an ID if required (lowercase letters and number only)
Tap on check icon at top right corner to confirm.
Go to ROMs (from the menu) and tap on bottom right icon, and select the patched ROM. Or can be flashed from Recovery
How to change ROM:
There are two methods:
Use the app:
Go to ROMs and select a ROM to boot taping on it
Use Boot UI:
Go to Settings and "Install Boot UI", next on each ROM (even primary) tap on 3dot menu and tap on "Update ramdisk. When a ROM is booted a menu will appear, cancel countdown and select the ROM to boot.
Partition Configuration:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: 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.
FAQ:
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:
https://dbp.noobdev.io/downloads/
Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Contributors:
@chenxiaolong
Source code:
https://github.com/chenxiaolong/DualBootPatcher
Official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
ISSUES
Recoveries
[OFFICAL] TWRP 3.1.1 by @vince2678 : wrong model name, returns with error fixed since 2017-06-20 build
TWRP 3.1.1 by @ganesh varma : Boot loops to recovery
ROMs
(Report any issues with ROMs)
Related
Hello to all! I want to know if someone makes to work dualboot f2fs with
devil recovery 6.0.4.5 and with
kernel Devil3.4_0.1.0-i9300-DUAL-20140209
when i format f2fs data and secondrom - restart
when i want to duplicate my first rom - restart
can't mount system on second boot menu
the recovery works with single rom f2fs partition but not dual
i use Smartdroid v4 and Smartdroid AOSP
Thanks for anser!
re
i got anser:
1. Install Devils recovery.
2. Install a rom to the first filesysten, preferrably the Sammy-based rom. Install a Devil2/3-kernel to it.
3. Make a nandroid backup of the Sammy rom to your external scdard.
4. Create a second filesystem in Devils recovery.
5. Restore your earlier made Sammy backup to the newly created second filesystem.
6. You now have two identical rom to choose from!
7. Clear the second filesystem to install a new rom.
8. Install the AOSP rom to the second filesystem. Install Devil 2/3-kernel.
9. Finished, choose from your two favorite roms!
BUT, there is a problem, Sammy-based roms doesn't seem to install in Devils latest recovery(error 7) so the above procedure should be made with the older Devils recovery on DerTeufel1980s OP. When everything is setup, ie you have made a nandroid of a working Sammy rom, you can upgrade to the latest recovery and choose which partitions should be formated to f2fs and restore selected backups with included Devil kernels to respective filesystem. If you run two AOSP roms this is not a problem, only if one is Sammy based!
Click to expand...
Click to collapse
i installed with succes dualboot f2fs with AOSP and something sammy based on devil recovery 6.0.4.5
-first i installed samy based rom with ext4 with kernel Devil3.4_0.1.0-i9300-DUAL-20140209 before restart.After than i made 1 system boot.
-custom backup
-format f2fs (i can't create the second image from dualboot menu if i restore sammy based on the first rom)
- after format i instaled ASOP 4.4.2 with preserve sistem f2fs, with no wipe at data and cache... instal Devil3.4_0.1.0-i9300-DUAL-20140209 kernel and restart. maked 1 sistem boot than RECOVERY inject gapps and then restart , maked another sistem boot (thats for open and works dualboot menu from recovery)
-RECOVERY -> dualboot -> create second image -> format sis , cache , data -> and than restored sammy based rom to secondrom on f2fs partition + Devil3.4_0.1.0-i9300-DUAL-20140209 kernel to be sure thats all ... that's a solution to have on dev 6.0.4.5 dualboot f2fs
AOSP + SAMMY BASED
formatting system to f2fs
hi ,
i am using agni kernel with carbon Rom i have formatted data .preload,cache to f2fs,but cannot get system formatted,can someone
point me to a tutorial to get it done ,please or explain it to me
Q&A for [ROM][STABLE] Slim CM7 #4 [19/12/2013][LINKS ADDED]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STABLE] Slim CM7 #4 [19/12/2013][LINKS ADDED]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My S5830i won´t boot up
Hi Guys,
its great to see, that there are still some users of this device and this rom. I try to flash a rom for the Ace for at least 7 Days now. I bricked it already, restored it with a full Stock firmware. I tried a lot of cm7 roms but none of them would boot up. I installed them like described. Recovery, wipe, install kernel reboot recovery install rom and gaps. After rebooting it stucks at the "Samsung Galaxy Ace" start screen. I already wiped Data and Cache after this, but it wont fix this problem. I would absolutely happy if someone could give me a hint what could be wrong.
Thanks for your help, cheers!
@NootYest, I am really concerned about the correct way you have been restoring your device back into stock firmware [ RFS partitions ] though. please follow my instruction @ post#6 for wipe flash-able zip packages , if you are doing other methods.
As for your problems , I am going to devise an experiment to force your partitions being transformed into EXT4, before flashing our CM Specific Basic Kernel. ( Method would apply only to CM7/7.2 based on kernel CM7 v4.0 (cooperVe). Do not use it on newer CM's please. )
Requirements :
SLIM_CM7.2_Cooperve #4
Temporary CWM for s5830i/c/M/s5839i devices , known as cooperVe.
CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]
EXT4 Formatter Tool
SLIMGapps by mathm2013 (Optional) >> This is an extreme bare bone Rom , check Dev section; his topic; for more instruction on how to flash this package.
1.. Copy them in the root of your SD card. ( Full back ; EFS partition back up; CWM back up is advised)
2.Boot into stock e3 recovery >> wipe data and flash your Temp CWM
3.cwm > wipe data > wipe cache > wipe dalvik cache
4.flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
5.Install kernel_CM7_v4.0_cooperVe .
6.When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
7.Wipe data, cache and dalvik
8.Go to "mounts and storage", and make sure /system partition is mounted (will show unmounted)
9. Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM.
10.Reboot
I am going to check on your progress later ,,,,,
ehsanotaku said:
@NootYest, I am really concerned about the correct way you have been restoring your device back into stock firmware [ RFS partitions ] though. please follow my instruction @ post#6 for wipe flash-able zip packages , if you are doing other methods.
As for your problems , I am going to devise an experiment to force your partitions being transformed into EXT4, before flashing our CM Specific Basic Kernel. ( Method would apply only to CM7/7.2 based on kernel CM7 v4.0 (cooperVe). Do not use it on newer CM's please. )
Requirements :
SLIM_CM7.2_Cooperve #4
Temporary CWM for s5830i/c/M/s5839i devices , known as cooperVe.
CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]
EXT4 Formatter Tool
SLIMGapps by mathm2013 (Optional) >> This is an extreme bare bone Rom , check Dev section; his topic; for more instruction on how to flash this package.
1.. Copy them in the root of your SD card. ( Full back ; EFS partition back up; CWM back up is advised)
2.Boot into stock e3 recovery >> wipe data and flash your Temp CWM
3.cwm > wipe data > wipe cache > wipe dalvik cache
4.flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
5.Install kernel_CM7_v4.0_cooperVe .
6.When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
7.Wipe data, cache and dalvik
8.Go to "mounts and storage", and make sure /system partition is mounted (will show unmounted)
9. Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM.
10.Reboot
I am going to check on your progress later ,,,,,
Click to expand...
Click to collapse
Hi ehsanotaku,
thank you for your reply!!!!! I did the trick! I tried different processes of installing cm7 and i think i know where the problem were.
First let me explain how i installed the rom. The Situation is a s5830i with Stock GB and an empty SDCard:
1. I copied the temporary cwm, the kernel, the cm7 and the gapps on the root of the SD
2. Reboot into stock recovery and start tmp recovery
3. Wipe data cache and dalvik
4. Install cm7 kerne and reboot recovery
5. Now I am in the new kernel recovery. There I go to mounts and storage, unmount system and format system
6. After formating system I installed the cm7, went back to mounts and storage and check if system is mounted
7. If system is mounted UNmount System
8. Install gapps, wipe cache and dalvik and reboot
The things i did in another way were formating system and unmount system before installation. So the update package had to mount the partition on its own. This process worked for me two times on two different devices. Perhaps you can add this to the main thread for future users.
Thank you!
@NootYest, I was going to recommend you to format your /System partition where your previous Android OS was resided, after your initial test. However this process is not necessary by default , when you are coming from stock GB -based OS ( unless you didn't revert back completely to your OLD RFS partitions as I did instruct ) . And for any modification/suggestion in regards of installation alternative methods please pm OP of ROM . I am just a regular novice helper @ XDA.
Have fun tinkering
I can confirm this works on a s5839i. Installed today on s5839i.
Any themes available for this rom as the packaged theme leaves a little to be desired, on all levels.
Oh dear this post seems to have been redirected to a different thread, so the question by the previous users in the other thread goes unanswered.
can you make a video on it pls pls ..............
kkaarann said:
can you make a video on it pls pls ..............
Click to expand...
Click to collapse
??
Thanks for this ROM
my 5830i was actually unusable on stock rom due to too many built in apps....This Slimcm7 rom actually solved my cell problem...too stable too light fluid performance.
Just on negligible issue is that sygic maps are not working on it but as i said its negligible.
Thanks developer for this wonderful rom
Hey people,
this shall mainly be a fast way to navigate users to necessary steps for diverse situations.
Instead of repeating the procedures over and over in each thread, this can be cited.
I will suggest you what I always do, and what I find safe and what I have good experiences with.
Still, you do everything at your own risk! So don’t complain to me if you mess something up by following my steps.
This well known phrase also counts here: “YOU are choosing to make these modifications”.
*********************
Preparations
Recovery
Make sure you are on the latest TWRP version.
Currently this is 3.2.3-0.
Backups
Before any of these procedures you should make a backup of every partition and save it at an external place – an usb stick, your PC, but not on your phone! Also copy the content of your entire internal storage at such an external place.
This will not always be needed and I will add more details of what you will surely lose when applying each method, but sometimes things just go wrong and suddenly your whole storage may be lost out of nowhere (happened to me more than once already).
A nice app that helps you restoring your apps and app data in a very quick way is Titanium Backup (get it from the Play Store). If you use the Pro version, you can restore everything basically with one click, so think about this way of backing up things as well (external copies are also advised here for obvious reasons).
Firmware
Make sure you are on adequate firmware for your ROM. Which firmware that is, must be taken from the respective ROM thread.
Adequate firmware needs to be present at any time before the actual ROM installation,
otherwise installation will fail, as the ROM expects a certain minimum to be present.
You will not need to always flash firmware again, when installing other ROMs or ROM versions.
The one you flashed last time sticks until you flash another.
A nice alternative to always flashing whole MIUI Developer versions are the zips offered by the firmware updater tool (just search through the xda topics).
*********************
So here we go with methods you should know:
***************
* Dirty Flash *
***************
Note that:
This is not recommended if the ROM maintainer or developer suggested a clean flash
If you wanna solve weird issues, you may try this first, but a Clean Flash or a Complete Formatting will probably help better
Use-cases:
You wanna install an update for a ROM you are momentarily on
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik and Cache
Flash ROM zip right on top of existing installation
(Optionally) Re-/flash root (re-flashing is not necessary for Magisk most of the time if you installed it before)
****************
* Clean Flash *
****************
Note that:
You will lose Gapps, settings, apps and app-data
Also recommended from time to time, even when a dirty flash would be sufficient
Some developers always prefer this method over a dirty flash
Use-cases:
You wanna flash a ROM from the same Android generation (e.g. both ROMs are from generation Nougat 7.1.2) you are currently on
You are experiencing issues after dirty flashing a ROM
Benefits:
Clean way of installation
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
***************************
* Complete Formatting *
***************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
You wanna flash a ROM of a different Android generation (e.g. switch from Nougat to Oreo)
You are experiencing weird issues, even a clean flash doesn’t solve
Benefits:
Clean way of installation
Good problem solver
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Format data (the one where you need to type “yes”)
Reboot to recovery to access the Data partition correctly again
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
****************************************
* Solve unable to mount Data error *
****************************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
TWRP suddenly shows the above error and even a Complete Formatting doesn’t help (or work)
Procedure:
Re-flash latest TWRP via fastboot (not from within TWRP)
Perform a Complete Formatting
********************
* Gapps Re-flash *
********************
Use-cases:
You want to change your current Gapps setup, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache and System
Flash ROM zip
Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Re-/flash root
********************
* Kernel Change *
********************
Note that:
This works for almost every kernel, but if the developer suggests another method, follow his
Use-cases:
You want to change the kernel, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
Reboot to System and let everything cool down for a minute or two
Reboot to TWRP
Flash new kernel
(Optionally) Re-/flash root
Wipe Dalvik and Cache
*******************************
* Stock Kernel Restoration *
*******************************
Use-cases:
You're on a custom kernel and want to switch back to stock one
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
(Optionally) Re-/flash root
Wipe Dalvik and Cache
********************************
* Splash Screen Restoration *
********************************
Note that:
A clean flash will not solve this
Use-cases:
Some kernel's or ROM's splash screen sticks and you wanna get rid of it.
Benefits:
Only takes a minute
You will not lose anything on your phone (except the splash screen ; ) )
Procedure:
Just re-flash your current firmware
*I usually go for Pico Gapps from opengapps.org, as they don't include anything I don't need or like, and add a couple of things from deltadroid by flashing them right after the Pico Gapps package. Some stock apps can be overwritten this way, so you don't have two for the same purpose (e.g. stock calendar and google calendar) and it results in a nice minimal Gapps configuration.
I’m open for corrections, questions or doubts! Please leave a comment in these cases!
last updated: 2018-08-20
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
HelpMeruth said:
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
Click to expand...
Click to collapse
Thanks!
And thanks for the info. So were these issues Magisk related only?
Phil_Smith said:
Thanks!
And thanks for the info. So were these issues Magisk related only?
Click to expand...
Click to collapse
iirc yes(there were SQL issues on the Magisk app), but I don't really follow superSU anymore since its been sold to some random company.
This is a very good guide.. Thanks mate
Hi guys
I have Motorola G 4G (Thea) that are trying to flash Lineage OS to alongside with OpenGApps. I have four zip files that I flash in a queue together. Two are the Lineage OS and OpenGApps, another one is an OpenGApps folder containing all my custom settings for the Aroma version that copies to the internal storage, and the last zip includes extra apps that built using the Android Zip File Creator. In regards to the extra apps zip I have some apps being installed to '/System/Priv-app' directory and the remainder installed to '/Data/App'. I want to keep the system apps as I would like to the apps to survive a factory reset or the use of safe mode. The problem I have is once the ROM boots up most of the apps are displaying the popup box 'stopped working' despite clicking the Wipe Cache & Dalvik button in TWRP at the end of flash. Is making a queue causing the problems and instead should I be wiping the Cache & Dalvik between each zip flash?
Many thanks
Will
Bump
Bump
Bump.
Sent from my LG-H930 using Tapatalk
the only rule you have to follow is to flash the rom file first all other things can be flashed after that
skip the 3rd file and check
and which version of gapps are you using
last file probably won't cause problems
Hi, just a quick tutorial. Some gsi requires a little additional step to flash gapps.
FIX
First of all download the gsi, and the gapps. I raccomend gapps pico.
Put the gapps in the phone memory, than flash the rom via fastboot or recovery.
-Go to recovery, select Wipe, Advanced Wipe
-select system squarebox then press repair or change system
-tap on Resize System, Swipe to Resize
-go back to the Recovery Main page, flash gapps,
profit. :good: