[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
I'm proud to present the first dual boot project for the Qualcomm-based Samsung Galaxy S4! This project started off as a feature in my ROM, but not anymore. This will allow any two ROMs (soon, three) 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/dual, /cache/dual, and /data/dual). Because of the way this is implemented, no changes to the primary ROM are necessary :D
A huge thanks goes out to all of the donators for supporting this project!
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 TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
It is very easy to add support for other kernels and ROMs. Let me know if you want support for another kernel or ROM :)
Download the patcher apk and run it. It's very straight forward--only has one button to press ;)
Double click PatchFileWindowsGUI.exe or drag the zip file you want to patch onto that file.
If it complains about msvcr100.dll missing, you'll need to install this: http://www.microsoft.com/en-us/download/details.aspx?id=8328
Make sure you have PyQt5 for Python 3 installed. This is the "python3-pyqt5" package on Debian and Ubuntu and "python-pyqt5" on Arch Linux. Then, double click PatchFileLinuxGUI or drag the zip file you want to patch onto that file.
The GUI is not supported on OS X yet. You can probably run the Windows version under Wine or Crossover though. Otherwise, you can use the command line version.
Windows (command line)
Drag the file you want to patch onto PatchFileWindows.exe
Linux or Mac (command line)
Change to the patcher's directory and run:
After patching the zip file, a new file_dualboot.zip file will be created. For example, patching ktoonsez's
would create a new
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher 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 Patcher 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.
Install the Dual Boot Patcher app again in the secondary ROM. If you have a locked bootloader, set the kernel for the secondary ROM (just in case).
Switch the ROM if something doesn't work properly?
Flash DualBootUtilities.zip. You will get a menu allowing you to switch to the primary or secondary ROM.
Wipe /cache, /data, /system, or dalvik-cache?
Flash DualBootUtilities.zip. You will get a menu that lets to wipe the respective partitions for either the primary or the secondary ROM.
It's important to not use the recovery's built-in wiping functions because they may delete files needed for the secondary ROM.
Update the primary ROM?
With version 8.0.0, the primary ROM can be patched so that it doesn't wipe the other ROMs when flashed. It also automatically sets the primary kernel. That is, most likely, the easiest method. The zip can also be manually edited by following the instructions below.
Edit META-INF/com/google/android/updater-script so that it does not format /system or /dev/block/mmcblk0p16 (because the 16th partition is /system)
Flash DualBootUtilities.zip before updating the ROM and choose Wipe Primary /system. If the primary ROM is AOSP-based, you will need to reflash Gapps.
Make sure to set the kernel as primary in the Dual Boot Patcher app
Alternative: Just flash the update as normal and then reflash the secondary ROM. It's a bit tedious, but it works and you won't lose any files/settings.
Update the secondary ROM?
Just patch the new zip and flash it
Flash a mod or custom kernel for the primary ROM?
Just flash it :)
If it's a custom kernel, make sure you set it in the Dual Boot Patcher app
Flash a mod or custom kernel for the secondary ROM?
If it's a custom kernel, just patch and install it.
If it's a mod or some other flashable zip, see the "How do I patch a zip file manually?" section.
How do I patch a zip file manually?
(My patches for the supported zips above can be found [here] if you'd like to see examples of how this is done)
Note: This has not been updated for version 3.0.0 of the patcher yet. The instructions below will still work, but auto-patching is a lot simpler.
The first thing to do is to download the dual boot helper script and place it at the base of the zip file (not in a subfolder): https://github.com/chenxiaolong/DualBootPatcher/raw/master/patches/dualboot.sh
Next edit the updater-script file: META-INF/com/google/android/updater-script and put the following lines at the top. This allows the helper script to be used.
Now, in order to make the zip file install to the correct location, you'll need to change all the lines that mount /system so that they use the dual-boot location. The helper script offers a convenient way to do this.
If see lines like one of the below:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/mmcblk0p16", "/system");
run_program("/sbin/busybox", "mount", "/system");
replace it with:
If you see any lines that format the /system partition, such as:
Now, if zip contains a kernel, you'll need to modify it's ramdisk. The easiest way to do this is to drag the boot.img onto useful/patch-ramdisk.bat if you're on Windows or:
if you're on Linux or OS X.
You will see something like this. Just choose the ROM/Kernel type (AOSP, Google Edition, or TouchWiz) and press Enter.
That's it! If it seems like a lot of work, you'll get the hang of it soon. The idea is to change the mount, format, and unmount operations so that they don't affect the primary ROM. Then the ramdisk is modified so that the needed files are loaded from the new locations.
I patched it manually and it worked! How do I include it in the patcher?
First of all, thanks for helping to add support for more ROMs! To include support for the ROM, I need two things: a patch and what I call a "patch info" file.
Generating a patch is easy. Make sure you have the original and modified files in the same directory structure as in the zip. You should have:
where 'a' has the original files and 'b' has the modified files. (Of course, you can name the two folders whatever you want)
If you're on Windows, just drag both 'a' and 'b' folders onto useful/generate-patch.bat that's included with the patcher.
If you're on Linux or Mac, just run:
./useful/generate-patch.sh /path/to/a /path/to/b
To create the "patch info" file, download this https://github.com/chenxiaolong/Dual...info/Sample.py into the correct subfolder in patchinfo/ (also included with patcher). Now, open the file with a text editor and change it to match your ROM/Kernel/etc. I've included comments on how to do that inside of the sample file :)
That's it! Just send me those two files and I'll include them in the next release :)
Moto X's optimized bionic and dalvik libraries installer
Fixes this error when a zip is unsupported:
AttributeError: 'NoneType' object has no attribute 'configs'
Add support for VirginROM (4.4 Kit Kat)
Add support for Dandroid (4.4 Kit Kat)
Add support for faux's Google Edition 4.4 jgedlte kernel
Add support for Gummy's Google Apps package
Google Edition ROMs have the ugliest ramdisk by far (err...I mean Google Edition 4.4 ROMs will now boot)
chmod.exe from Cygwin's coreutils in now included in the Windows build so the patcher can set the necessary permissions on the init binary in Google Edition 4.4 ROMs
Disable SELinux by default globally
Fix mediaserver crash caused by the removal of /system/etc/snd_soc_msm/snd_soc_msm_2x_Fusion3_auxpcm in jamal2367's Google Edition 4.4 ROM
Add support for Ktoonsez's Google Edition 4.4 kernel
Add support for Hell(y?)kat
Add support for multi-boot patching in the Android GUI
Update SuperSU patch to support version 1.80
Switch to CyanogenMod 11's mkbootimg and unpackbootimg sources
Add support for Google Edition 4.4 ROMs (ie. stop trying to patch the missing MSM8960_lpm.rc in the ramdisk)
Hack to allow the file chooser in Android 4.4 Kit Kat to work properly (in the Android version of the patcher)
Separate many functions into common.py to make patchinfo files simpler
Set compile target for the Android GUI to Kit Kat (API 19)
Add support for debug builds of the Android GUI so I don't have to sign test builds
Add support for removing those pesky device check asserts
Add support for using multiple patches (can combine auto-patcher with manual patch)
Fix broken patch generator in Windows (hopefully, we won't need it anymore though)
Removed by default for HellyBean
Searches through updater script to find mount, unmount, format, and delete lines and replaces them with the multi-boot equivalent.
Finds line that flashes the kernel and inserts line that takes a backup and stores it in the appropriate place for the dual boot switcher
All partitions will always be unmounted after installation so the phone is not in a weird state when flashing the next zip.
jamal2367's Google Edition
Ktoonsez AOSP, TouchWiz, and Google Edition kernels
Paranoid Android Google Apps
BaNkS' Google Apps
CyanogenMod's Google Apps
doomed151 Google Apps
SlimBean Google Apps (standard and aroma)
task650's AOKP Google Apps
MIUI's Google Apps
HTC Sense 5 port
MaKTaiL's Google Edition
Triple boot! (and quadruple and quintuple and ...)
Any auto-patched ROM is automatically supported
Requires version 2.0.0 of the Dual Boot Switcher app
Dual Boot Switcher supports up to 10 ROMs in addition to the primary and secondary
Patcher supports 3 ROMs in addition to the primary and secondary (unless someone wants more)
The Android GUI only supports dual booting for now
Partition configuration (where things are installed): https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/partitionconfigs.py
Introduced a new dualboot.sh script that keeps track of what has and hasn't been mounted
Terribly written updater-scripts aren't a problem anymore
Note: using the script outside of the patcher will cause the ROM to be installed as secondary
Note: I don't want to rewrite SELinux rules and compile a modified version of vold, so for now, the target /system must be on a different physical partition than the target /cache. Other dualboot solutions have worked around this by installing the ROM files to a loop mounted ext4 filesystem image
Installing ROMs to /data should work in theory, but will not be supported
What else? :p
Catch exception when file cannot be extracted
Add support for loki'd ChronicKernel
Add support for OmniROM's Kit Kat ramdisks
Add support for Paranoid Android 4.4 Google Apps
Fix syntax error in scripts/gendiff.py
unlokibootimg: struct can convert little-endian bytes to integers in Python 3.0 and Python 3.1 too
Don't use backslashes for filenames when generating patches from Windows
Add rushi.1986's patches for GoldenEye AT&T: http://forum.xda-developers.com/showpost.
Update Sample.py for bootimg variable
Add support for Ktoonsez's non-AOSP kernels
Add support for extracted loki'd boot images: https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/unlokibootimg.py
Add support for Loki'd ktoonsez's AOSP 4.3 kernels
Fix crash when script is run with Python 2 due to the code trying to encode a "UTF-8" string as "UTF-8"
Flush stdout when printing status messages because Python 2's print() doesn't do that automatically
Fix general patch for Kangabean and enable Loki ramdisk patching for it
Add support for IOKP
Use custom-compiled tar to fix extraction on ROMs that don't have tar with xz support
Fix status messages in patcher so the app doesn't appear to pause with no activity
Clean up app cache as soon as it's not needed anymore
Add support for GoldenEye (TouchWiz 4.3) for T-Mobile
Add support for loki'd Slim Bean
Switch to GNU patch because busybox's patch can't handle fuzz. There's no way in the world we could ever have 100% perfect patches, so busybox is not an option.
New Android app for patching files directly on the phone
Add script for generating patches
Add support for automatic ramdisk patching https://github.com/chenxiaolong/DualBootPatcher/commit/c8b63aa32ec0fc1c88b28ef76e335167c1e2f47e
Add LiquidSmooth ramdisk
Add support for LiquidSmooth
Add munchy_cool's 64-bit OS X unpackbootimg and mkbootimg binaries
Add support for OS X
Add support for Metaiiica's PAC-Man
Fix regular expressions for HellyBean and AOSP
Add rushi.1986's fix for the ramdisk replacement script: http://forum.xda-developers.com/showpost.php?p=46319181&postcount=458
Add support for ProBAM
Add support for HellyBean
Windows: Allow zip files to reside on a drive other separate from the patcher
replaceramdisk.py: Bug fix in variable name
Add support for Vertigo's AOKP
Add generic AOKP ramdisk
Add support for TriForceROM
Add support for iNTriNsiC (20130806 version)
Add support for Negalite
Add support for geiti94's Sense 5 port
Add support for Kangabean
Add support for Paranoid Android Google Apps package
Add support for Broodplank's AOSP
Add support for doom151's AOSP Google Apps package
Add support for Evil UnWizzed
Add support for ComaDose
Add support for JellyBeer
Add support for jamal2367's Google Edition ROM
Fix critical bug in the repacking of boot.img that may cause secondary ROM to not boot (duplicate files w/same name in zip)
Add support for AROMA Slim Bean Google Apps package
Optimize patcher script so only one full zip read and one full zip write is required
Add support for BaNkS's Google Apps
Add support for Carbon ROM
Add patched Carbon ramdisk
Use 0 context diff for paranoidandroid.dualboot.patch so it can apply properly to AOSPA's updater-script
Add support for FoxHound ROM
Add generic TouchWiz ramdisk
Update README with notice about free disk space
Bind mount /data/media during installation. It is bad practice for an updater-script to touch /data/media, but some ROMs do this, so we need to handle it
Add support for mounting secondary /cache in dual boot helper script
Update replaceramdisk.py to support version 1.7's change in ramdisk compression
regarding this dual booting, is there any possibility that the /data partition can be shared across both roms?
Sent from my GT-I9505 using Tapatalk 2
Originally Posted by chickentuna
+1 this would be awesome
Sent from my Galaxy Nexus using Tapatalk 4
It depends on what you mean by /data. Currently, the internal SD is shared. It's possible to share /data/app and /data/app-asec without too much trouble (so apps aren't downloaded twice). If you're looking to share /data/data (app settings), I don't think I'll implement that, as least not for all apps. I don't think it's a good idea to have to have a blacklist of apps that can't have their data shared, such as launchers.
I'm considering adding a new section to the dual boot switcher app so that you can choose which apps' data should be shared between the two ROMs
Current phone: Samsung Galaxy S4 SGH-M919 (T-Mobile) & Nexus 5
As some of you may remember, a while back we spoke about Secrecy, an effective file … more
27 Aug 2014
By Faiz Malkani
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?