[DISCONTINUED][PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!

Search This thread
By:
Advanced…
E

ewangw

Senior Member
Oct 27, 2013
51
13
King George
chenxiaolong said:
When you're booted to Android or recovery, are you able to manually mount /firmware?

Code: 
mkdir -p /firmware
mount -t ext4 /dev/block/bootdevice/by-name/modem /firmware

If that doesn't work, what about after a repair of the modem partition?

Code: 
e2fsck /dev/block/bootdevice/by-name/modem

I really can't think of anything else that might cause the problem.
Click to expand...
Click to collapse

@chenxiaolong,

First off, thanks for all your help in troubleshooting this issue.

I ran the commands in term. emulator and in TWRP and I got a message that the device or resource is busy in each case. When I loaded AICP 12.1, I had to sideload it as my main ROM, but /firmware did fail at first until I wiped my cache. Once I wiped cache it loaded, including /firmware, with no problem. Not sure why that works.

Currently, I have AICP12.1 in primary and CM14.1 and CypherOS sitting in my data slot. To get the SIM working, I just copied my firmware folder from AICP to the other Nougat ROMS and that seems to do it. I'm cool with this workaround until something can be figured out.
 
  • Like
Reactions: chenxiaolong
chenxiaolong

chenxiaolong

Senior Member
Sep 29, 2011
2,993
7,482
asterix14 said:
This line in updater-script MIUI


Log and miui_update file attached
Click to expand...
Click to collapse

Mike0505 said:
This time I only tested miui weekly from xiaomi.eu 6.11.24 in data slot which was failed previous time. :)
In app flashing again to much time to verify zip and on flashing failed. In twrp also flashing failed.
Miui is not ready for cooperation :confused:
Logs attached
Thank You !
Click to expand...
Click to collapse

Thanks for the logs! Can you give this test build a try and see if it resolves the issue? https://github.com/chenxiaolong/DualBootPatcher/pull/315
 
  • Like
Reactions: Mike0505 and rifle007
chenxiaolong

chenxiaolong

Senior Member
Sep 29, 2011
2,993
7,482
gc_geforce said:
No worries, I will try this and see what happens and forward the logs.:good:

chenxiaolong, How do I get the log from the patcher as it was able to patch the rom zip file but failed trying to flash it with 9.1.0.r0.g6e3c82c, when it was verifying it gave an error -1

This is GREAT! so I could not install the zip file via the patcher APP 9.1.0.r0.g6e3c82c, BUT I rebooted into recovery and tried flashing the new patched zip in TWRP and reboot, and it worked!!! it is booting into the newly installed ROM from EXTSD on my G900W8 S5. I am not sure what is wrong why it errors out trying to verify the zip in the patcher app. Also I noticed that when in the TW ROM from EXTSD it thinks the I have a corrupted SD Card. is this because the ROM is booted from the SD CARD?
Click to expand...
Click to collapse

Great! Glad you got it working! Can you post a screenshot of where you're seeing "error -1"?

The external SD showing as corrupted is caused by tripping a security feature in the TW kernels. It only happens when booting from an extsd-slot. At the moment, the only way to fix that is to use a custom kernel that has the security feature disabled.
 
  • Like
Reactions: yfriday14 and gc_geforce
gc_geforce

gc_geforce

Senior Member
May 17, 2009
545
130
Canada
chenxiaolong said:
Great! Glad you got it working! Can you post a screenshot of where you're seeing "error -1"?

The external SD showing as corrupted is caused by tripping a security feature in the TW kernels. It only happens when booting from an extsd-slot. At the moment, the only way to fix that is to use a custom kernel that has the security feature disabled.
Click to expand...
Click to collapse
I will change the kernel, easy fix, here is the screen shot it did not say error - 1 this time
d40cd06ac87abfc7e33e70a371ae3432.jpg


Sent from my SM-G900F using XDA-Developers mobile app
 
chenxiaolong

chenxiaolong

Senior Member
Sep 29, 2011
2,993
7,482
gc_geforce said:
I will change the kernel, easy fix, here is the screen shot it did not say error - 1 this time
d40cd06ac87abfc7e33e70a371ae3432.jpg


Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse

Since you have it working, it's not really a rush, but when you have some time, would you mind updating the app to 9.1.0.r13.g3d9b503 and trying again? You don't have to repatch or flash anything. Just add a zip to the in-app flasher so the verify zip process runs. It will create a new log file at /sdcard/MultiBoot/logs/verify-zip.log. Thanks!
 
gc_geforce

gc_geforce

Senior Member
May 17, 2009
545
130
Canada
chenxiaolong said:
Since you have it working, it's not really a rush, but when you have some time, would you mind updating the app to 9.1.0.r13.g3d9b503 and trying again? You don't have to repatch or flash anything. Just add a zip to the in-app flasher so the verify zip process runs. It will create a new log file at /sdcard/MultiBoot/logs/verify-zip.log. Thanks!
Click to expand...
Click to collapse

I can do this tonight for you!
 
  • Like
Reactions: chenxiaolong
R

rifle007

Member
Feb 29, 2016
35
14
chenxiaolong said:
Thanks for the logs! Sorry, I made a super dumb typo in the code and made it unmount /cache instead of mounting it. There's a new test build available at: https://github.com/chenxiaolong/DualBootPatcher/pull/315
Click to expand...
Click to collapse

Still same and when i added mount option in updater-script MIUI it can flash with succesfully
run_program("/sbin/mount","/cache");
package_extract_file("META-INF/com/miui/miui_update", "/cache/miui_update");
set_metadata("/cache/miui_update", "uid", 0, "gid", 0, "mode", 0555, "capabilities", 0x0);
run_program("/cache/miui_update");
delete("/cache/miui_update");
run_program("/sbin/umount","/cache");
Click to expand...
Click to collapse

sorry i use the patched zip from old app, now its work
 
Last edited:
  • Like
Reactions: chenxiaolong
gc_geforce

gc_geforce

Senior Member
May 17, 2009
545
130
Canada
chenxiaolong said:
Since you have it working, it's not really a rush, but when you have some time, would you mind updating the app to 9.1.0.r13.g3d9b503 and trying again? You don't have to repatch or flash anything. Just add a zip to the in-app flasher so the verify zip process runs. It will create a new log file at /sdcard/MultiBoot/logs/verify-zip.log. Thanks!
Click to expand...
Click to collapse

Here is the log for you, and 9.1.0.r13.g3d9b503 did the same as my first screenshot of when the verify fails.
 

Attachments

  • verify-zip.log
    24.8 KB · Views: 7
nicesoni_ash

nicesoni_ash

Senior Member
May 26, 2012
6,103
10,955
127.0.0.1

Attachments

  • 20161129.111036.tar.gz
    352.4 KB · Views: 7
911-Future_Maker

911-Future_Maker

Senior Member
Jan 5, 2013
1,568
1,127
9.1.0 builds are live, hell yeah. :p Thanks @chenxiaolong.

---------- Post added at 09:14 ---------- Previous post was at 09:09 ----------
asterix14 said:
In this test build the problem still exist ApplyParsedPerms: removexattr of /cache/miui_update to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata: some changes failed
Click to expand...
Click to collapse

Every time I see this error I'm in-app flashing. When trying the zip in recovery it flashed successfully. Not really a problem of the patcher, but it's more like rom dependable issue.
 
  • Like
Reactions: chenxiaolong
911-Future_Maker

911-Future_Maker

Senior Member
Jan 5, 2013
1,568
1,127
@Eleo Strange storage issue, seems related to TW ROMs. Chen is working hard fixing the things up for the new TW 7.0. Can you look what's going on in the /raw dir? Find the path for the /system and /data partitions for both extsd roms and report their size. They are located in:
Code: 
/raw/images/extsd-slot-xx
/raw/data/multiboot/extsd-slot-xx
Could you also tell me the size of the system.img images in /extsd/Multiboot/extsd-slot-xx?
 
Last edited:
Eleo

Eleo

Senior Member
Apr 16, 2012
16,404
14,772
Essen, Germany
Google Pixel 3a XL
Google Pixel 6
911-Future_Maker said:
@Eleo Strange storage issue, seems related to TW ROMs. Chen is working hard fixing the things up for the new TW 7.0. Can you look what's going on in the /raw dir? Find the path for the /system and /data partitions for both extsd roms and report their size. They are located in:
Could you also tell me the size of the system.img images in /extsd/Multiboot/extsd-slot-xx?
Click to expand...
Click to collapse
Ok. I wiped the primary and extsd slot 1 to save up some space in sdcard. Right now I only have extsd slot 2 active and only 2.5GB is used by system data. Will try backing up present ROM, then restore the previous s7edge port from recovery then will try installing dualboot and restoring dualboot backup from external sd to have primary and extsd slot. And will boot to extsd slot ROM to know how much space I have filled with system data and also look at the directories you pointed out.
Thanks

Sent from my SM-N930F using XDA Labs
 
tomaasz

tomaasz

Senior Member
Feb 21, 2012
608
139
49
Zabrodzie
Hi,

Thanks for great tool
Could you check in my log why after I "set kernel" (with info "Successfully set the kernel") again and again I revive tip "The kernel has not yet been set for the current ROM. Would you like to set the kernel now?" ?
And after using "Update ramdisk" I always receive communicate "Failed to update ramdisk" ?

My device is S5 SM-G900F klte
TWRP 3.0.2-0
Rom: TW 6.0.1 DarkLord N7 V 4.5 by @ufo (I've added line ro.patcher.device=klte)
with [KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel v 2.4

?
 

Attachments

  • ramdisk-update.log
    226.6 KB · Views: 11
You must log in or register to reply here.

Similar threads

invisiblek
[ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies for the Qcom Intl Galaxy S4 (jflte)
Replies
7K
Views
1M
NewbieGamingYT
NewbieGamingYT
invisiblek
[ROM][Official][4.3] CyanogenMod 10.2 for the Qualcomm Intl Galaxy S4
Replies
4K
Views
775K
T
thefuzz4
AntaresOne
  • Poll
[ROM][5.0.2][STABLE] AntaresOne & Alucard24's optimized CM12 builds [EOL]
Replies
6K
Views
2M
meowmeoe111
meowmeoe111
-+BB+-
[JDCTeam][6.0.1][12 March][OMS-Substratum] The Android Open Source Project MOB31T
Replies
8K
Views
1M
S
satpakCA
gharrington
3Minit Framework 0.1 TW 4.4.2 [09/07/14][MODS][THEME][MORE]
Replies
7K
Views
998K
J
Jochen K.

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 754
    chenxiaolong
    chenxiaolong
    This project has been discontinued. See https://github.com/chenxiaolong/DualBootPatcher/blob/master/README.md for more details.


    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 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 :D

    Donators

    A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.

    See all of our supporters here: https://gist.github.com/chenxiaolong/3f3fb485cbd0cb77c4281941433ec54d

    It patches...

    • Custom kernels for dual boot support
    • ROMs so that they can be installed as secondary
    • Google Apps packages for AOSP-based ROMs
    • SuperSU so that it can be used in the secondary ROM

    NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.

    How to use the patcher


    Android

    Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.

    Windows (GUI)

    Double click DualBootPatcher.exe and choose the file you want to patch.

    --------

    After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's

    KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip

    would create a new

    KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip


    Instructions for dual booting


    Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.

    The patcher offers several locations for installing ROMs:

    • Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
    • Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
    • Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
    • Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
    • 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.

    With that said, let's get to the "how to"!

    1. First, boot into your primary ROM and install the Dual Boot Patcher app
    2. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
    3. Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.

    There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.

    Flashing from recovery

    To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.

    In-app flashing

    To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.

    A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://xdaforums.com/showthread.php?t=2491299


    How do I...?


    Switch the ROM if something doesn't work properly?
    You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.

    If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​

    Wipe /cache, /data, /system, or dalvik-cache?

    The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".

    Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.

    NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​

    Update the primary ROM?

    Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​

    Update a non-primary ROM?

    Patch and flash the zip exactly like how you did it the first time.​

    Flash a mod or custom kernel for the primary ROM?

    Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​

    Flash a mod or custom kernel for a non-primary ROM?

    Just patch and flash it :)​



    Downloads:


    [LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip


    Donations:

    Donations are not required, but are greatly appreciated :D Donators will have their names listed in a nice big font on this post and will also be listed in the README file of the patcher.


    Source code:




    XDA:DevDB Information
    Dual Boot Patcher, Tool/Utility for the Samsung Galaxy S 4

    Contributors
    chenxiaolong

    Version Information
    Status: Testing

    Created 2013-09-17
    Last Updated 2014-07-29

    XDA:DevDB Information
    [DISCONTINUED] Dual Boot Patcher, Tool/Utility for the Samsung Galaxy S4

    Contributors
    chenxiaolong
    Source Code: https://github.com/chenxiaolong


    Version Information
    Status: Testing

    Created 2013-09-17
    Last Updated 2019-05-17
    View
    302
    chenxiaolong
    chenxiaolong
    Reserved

    EDIT: Funny how people are thanking this reserved post :D
    View
    130
    chenxiaolong
    chenxiaolong
    Reserved

    Changelog:





    • Version 5.0.2
      • Fix bug in regex that may cause "errors=remount" to become "errwrs=remount" for my noobdev ROM leading the init binary to fail

    • Version 5.0.1
      • Fix issue where the mount script would not be executed in the init scripts of ktoonsez's kernels
      • falcon is the Moto G, not the Moto X


    • Version 4.1.3
      • Add support for EHNDROIX
      • Add support for WanamLite
      • Sort ramdisks and presets in GUI

    • Version 4.1.2
      • Add support for Echoe v20

    • Version 4.1.1
      • Add support for Echoe v18


    • Version 4.0.4
      • Update to version 1.7.28-2 of the cygwin library (for Windows)
      • Add support for OctOS
      • Add support for NamelessROM
      • Add support for Tquetski's MIUI
      • Automatically comment out check_icd in init.rc of TouchWiz 4.4 ramdisks (initial work to make stock init binary dual-boot capable)

    • Version 4.0.2
      • Remove generic boot.img support. Use the GUI patcher or patch-ramdisk script instead.
      • Add support for patching unsupported boot.lok files by unifying the file type detection code in the CLI and GUI programs
      • Add support for BlackBox 2.2
      • Add support for Echoe v14, 14.1 (untested)
      • Add support for jamal2367's Google Edition version R1.1 final
      • Add support for jamal2367's old Android 4.2.2 build
      • Add support for LiquidSmooth Kit Kat
      • Add support for AOSB
      • Add support for Bobcat Google Edition
      • Add support for SHOstock (TW4.4 tested)
      • Fix bug where the newly flashed kernel for devices needing loki is not saved properly
      • Fix modem partition mounting in TouchWiz 4.4 ROMs -- Fixes unknown baseband bug


    • Version 3.2.2
      • Added support for:
        • Carbon's Kit Kat ROM
        • Omnifarious's ROM
        • Kangakat
        • BAM-Android
        • Infamous Google Edition
        • Echoe Google Edition
        • Echoe TouchWiz
        • Official MIUI (TouchWiz-based)
        • Moto X's optimized bionic and dalvik libraries installer

    • Version 3.2.1
      • Fixes this error when a zip is unsupported:
        Code: 
        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

    • Version 3.2.0
      • 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
    • Version 3.1.1
      • Add support for Ktoonsez's Google Edition 4.4 kernel
      • Add support for Hell(y?)kat

    • Version 3.1.0
      • Add support for multi-boot patching in the Android GUI

    • Version 3.0.1
      • 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)

    • Version 3.0.0
      • 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
      • Add auto-patcher
        • 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.
      • Auto-patched ROMs
        • GoldenEye
        • CyanogenMod
        • HellyBean
        • PAC-Man
        • ProBAM
        • AOKP
        • IOKP
        • AOSP
        • SlimBean
        • Paranoid Android
        • AICP
        • Carbon
        • JellyBeer
        • Omni
        • Gummy
        • Vanir
        • Dirty Unicorns
        • jamal2367's Google Edition
        • Ktoonsez AOSP, TouchWiz, and Google Edition kernels
        • Faux kernel
        • Ausdim kernel
        • Adam kernel
        • Infamous kernel
        • Triforce ROM
        • 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
        • MIUI ROM
        • Foxhound
        • HTC Sense 5 port
        • MaKTaiL's Google Edition
        • Kangabean
      • 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
    • Version 2.5.3
      • Catch exception when file cannot be extracted
      • Add support for loki'd ChronicKernel

    • Version 2.5.2
      • Add support for OmniROM's Kit Kat ramdisks
      • Add support for Paranoid Android 4.4 Google Apps
      • Fix syntax error in scripts/gendiff.py

    • Version 2.5.1
      • 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://xdaforums.com/showpost.
        php?p=46950654&postcount=801
      • Update Sample.py for bootimg variable
      • Add support for Ktoonsez's non-AOSP kernels

    • Version 2.5
      • 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
    • Version 2.4.3
      • Add support for IOKP

    • Version 2.4.2
      • 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

    • Version 2.4.1
      • Add support for loki'd Slim Bean

    • Version 2.4
      • 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.

    • Version 2.3
      • New Android app for patching files directly on the phone

    • Version 2.1
      • Add script for generating patches


    • Version 1.18.1
      • Add LiquidSmooth ramdisk
      • Add support for LiquidSmooth

    • Version 1.18
      • Add munchy_cool's 64-bit OS X unpackbootimg and mkbootimg binaries
      • Add support for OS X

    • Version 1.17.5
      • Add support for Metaiiica's PAC-Man

    • Version 1.17.4
      • Fix regular expressions for HellyBean and AOSP


    • Version 1.17.2
      • Add support for ProBAM

    • Version 1.17.1
      • 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

    • Version 1.17
      • Add support for Vertigo's AOKP
      • Add generic AOKP ramdisk

    • Version 1.16.2
      • Add support for TriForceROM

    • Version 1.16.1
      • Add support for iNTriNsiC (20130806 version)

    • Version 1.16
      • Add support for Negalite

    • Version 1.15
      • Add support for geiti94's Sense 5 port

    • Version 1.14.2
      • Add support for Kangabean

    • Version 1.14.1
      • Add support for Paranoid Android Google Apps package

    • Version 1.14
      • Add support for Broodplank's AOSP
      • Add support for doom151's AOSP Google Apps package

    • Version 1.13
      • Add support for Evil UnWizzed

    • Version 1.12
      • Add support for ComaDose
      • Add support for JellyBeer
      • Add support for jamal2367's Google Edition ROM

    • Version 1.11
      • Fix critical bug in the repacking of boot.img that may cause secondary ROM to not boot (duplicate files w/same name in zip)

    • Version 1.10.1
      • Add support for AROMA Slim Bean Google Apps package

    • Version 1.10
      • Optimize patcher script so only one full zip read and one full zip write is required
      • Add support for BaNkS's Google Apps

    • Version 1.9
      • Add support for Carbon ROM
      • Add patched Carbon ramdisk

    • Version 1.8.1
      • Use 0 context diff for paranoidandroid.dualboot.patch so it can apply properly to AOSPA's updater-script

    • Version 1.8
      • 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


    • Version 1.6.3
      • Add support for Adam kernel (UNTESTED)
    • Version 1.6.2
      • Add support for Ausdim kernel (UNTESTED)

    • Version 1.6.1
      • Add support for Slim Bean ROM

    • Version 1.6
      • Add new script for replacing the ramdisk in boot.img

    • Version 1.5
      • Add support for MIUI

    • Version 1.4.2
      • Add support for ParanoidAndroid

    • Version 1.4.1
      • Experimental Infamous kernel support (UNTESTED)

    • Version 1.4
      • Initial support for Google Edition ramdisks
      • Add support for MaKTaiL's Google Edition ROM

    • Version 1.3
      • Minor fixes in preparation for public release
      • Update README with supported files and convert line endings to rn (thanks Windows!)

    • Version 1.2.6
      • Add SuperSU support

    • Version 1.2.5
      • Add AOKP support

    • Version 1.2.4
      • Add ChronicKernel support

    • Version 1.2.3
      • Add support for Vertigo's PAC-Man

    • Version 1.2.2
      • Add support for CyanogenMod's Google Apps

    • Version 1.2.1
      • Add support for official CyanogenMod nightlies

    • Version 1.2
      • Add faux kernel support

    • Version 1.1
      • Add Windows support
      • Newly compiled mkbootimg.exe and unpackbootimg.exe to support Windows' separate text and binary file I/O modes
      • Add a portable, minimal version of Python 3 for Windows
      • Use newer GNU patch from MSYS for Windows

    • Version 1.0
      • Initial release (Linux only)
      • Supported kernels: ktoonsez AOSP 4.3
    View
    30
    chenxiaolong
    chenxiaolong
    Sorry everyone, I will continue to unavailable for the near future. I'm currently involved in a new project at work that is a very significant career goal for me, so I'm dedicating all my time and energy towards it. I'm not allowed to say any more than that, but it's why DualBootPatcher hasn't gotten much activity lately. Rest assured that the project is not dead!

    In the little free time I had in the past few weeks, I made some pretty important changes to the core of the patcher. The most significant one is probably libmbbootimg, a new boot.img file parser. It is much more secure than the current code (in terms of handling malicious boot.ing files) and is somewhere around 600% faster. It will be noticeable when loading the list of ROMs, switching ROMs, updating the ramdisk, etc.

    I know a lot of people have jumped in and submitted pull requests while I was gone. Thanks to everyone who has done so; it's much appreciated! I will be reviewing and merging those PRs ASAP.

    And as usual, thanks to everyone in this thread for helping each other out!

    Cheers,
    Andrew
    View
    29
    chenxiaolong
    chenxiaolong
    hisname said:
    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
    Click to expand...
    Click to collapse

    chickentuna said:
    +1 this would be awesome

    Sent from my Galaxy Nexus using Tapatalk 4
    Click to expand...
    Click to collapse

    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 :)
    View

New posts