For clarrification purposes, we do not need to do anything with the gapps correct? just flash it in recovery when flashing second rom?
[DISCONTINUED][PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
- Thread starter chenxiaolong
- Start date
-
- Tags
- dualboot dualbootpatcher
Any zip file that you want to install for the second ROM needs to be patched. :good:
Currently, the gapps at http://get.cm/gapps is supported and works with most AOSP-based ROMs. (AOKP gapps is supported too)
EDIT: Oops, I meant http://goo.im/gapps
Last edited:
Oh i see, the link doesn't work btw i get this.....You are doing great here! I'm surprise it did not show up on the front page
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/tornado-2.4-py2.7.egg/tornado/web.py", line 1037, in _execute
self.prepare()
File "/usr/local/lib/python2.7/dist-packages/tornado-2.4-py2.7.egg/tornado/web.py", line 1487, in prepare
raise HTTPError(self._status_code)
HTTPError: HTTP 404: Not Found
By the way, out of curiousity I decided to use the patch script use to patch the roms....I used it on the gapps instead. Im not sure if this is accidental discovery, or if the dualbootpatcher can patch any zips for the second rom.
I went on to compare the updater scripts and i got this, I compared it to the instruction for manual patching and everything is the same! So i am thinking the patchscript can patch anything without us doing it manually? Just wanted to share, im grabbing the gapps from the link...just to be on the safe side loool. But let me know!
PHP:
ui_print("...4.3 Gapps for AOKP...");
ui_print("Installing for SECONDARY OS/ROM");
package_extract_file("dualboot.sh", "/tmp/dualboot.sh");
set_perm(0, 0, 0777, "/tmp/dualboot.sh");
run_program("/tmp/dualboot.sh", "mount-system", "ext4", "/dev/block/platform/msm_sdcc.1/by-name/system");
run_program("/sbin/busybox", "umount", "/data");
run_program("/tmp/dualboot.sh", "mount-data", "ext4", "/dev/block/platform/msm_sdcc.1/by-name/userdata");
show_progress(1, 15);
delete("/system/app/Provision.apk", "/system/app/CalendarGoogle.apk", "/system/app/Phonesky.apk", "/system/app/GoogleBookmarksSyncAdapter.apk");
delete("/lib/libgoogle_recognizer_jni.so");
ui_print("Copying Files...");
package_extract_dir("data", "/data");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/tmp/dualboot.sh", "unmount-data");
run_program("/tmp/dualboot.sh", "unmount-system");
ui_print("Installation complete!");
I have patched latest cm10.2 nightly & flashed.. Everything went fine.. Using tw as primary rom with Latest phils recovery..
Thanks a lot..
Between is there a way to get the apps shared between two roms..? I mean those installed in primary rom is not shown in secondary..
Sent from my GT-I9505 using Tapatalk 2
Thanks a lot..
Between is there a way to get the apps shared between two roms..? I mean those installed in primary rom is not shown in secondary..
Sent from my GT-I9505 using Tapatalk 2
Review
So i have been crazy about dual boots for a while and I can SAFELY say, I just found one! BTW, I flashed the gapp files created by the dualbootpatcher...
I successfully booted between both roms with no issue. My second rom was task AOKP rom. No force close. Instruction is easy to follow (but being me, I like to clarify If i get mix message from something).
Thx!
So i have been crazy about dual boots for a while and I can SAFELY say, I just found one! BTW, I flashed the gapp files created by the dualbootpatcher...
I successfully booted between both roms with no issue. My second rom was task AOKP rom. No force close. Instruction is easy to follow (but being me, I like to clarify If i get mix message from something).
Thx!
Great, Installed this as second rom
http://xdaforums.com/showthread.php?t=2422582 and works! only camera in second rom doesn't works, I don't know why
Sent from my GT-I9505 using xda premium
http://xdaforums.com/showthread.php?t=2422582 and works! only camera in second rom doesn't works, I don't know why
Sent from my GT-I9505 using xda premium
Not quite automatic yet; I don't want the program to miss something and suddenly /system is wiped
In case you're interested, the program applies this patch for the gapps I mentioned: https://github.com/chenxiaolong/DualBootPatcher/blob/master/patches/cyanogenmod-gapps.dualboot.patch
Awesome, glad you got it working!
It is very easy to enable app sharing (no data) between the two ROMs. However, I need to test how the second ROM would react to incompatible apps (like what would happen in AOSP saw TW apps).
Glad you got it working
If something is unclear, feel free to ask. I know I'm not the best at explaining things
Great. Was waiting for something like this.
Nice work, mate. :thumbup:
Will try it soon.
Nice work, mate. :thumbup:
Will try it soon.
Wow if you can do that, it will be awesome! My only request for that would be MMS lol, already had two incidents were i forgot i texted the person on the other rom and they responded while i was in the other lmaoooo was like "what are you talking about" moment haha.
Hey I don't want to bother you for each different GE ROM. How do I modify the patcher to accept a GE ROM other than the untouched one you added support for? I'll make sure the ROM I want to try has a stock GE kernel so that It can use your ramdisk.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Great work! Will try it in a few days.
One question: I will install PAC Man ROM as secondary ROM, do I need to Wipe System before installation? Using the WipeSystemSecondary.zip?
Thanks!
One question: I will install PAC Man ROM as secondary ROM, do I need to Wipe System before installation? Using the WipeSystemSecondary.zip?
Thanks!
Since all ROMs have different sizes, the best way to find out how much space the second one will take is to extract the zip file and see what the size of the files are.
Also, the ROM does, in fact, need to be patched. The project started off as a kernel patcher, so some of the OP might still say kernel. I'll go fix that right now
Regarding the FCs, the two main causes would be running out of space on /system (needed files cannot be installed properly) or an incompatible kernel. From what you said, I'm assuming you're trying to use the Infamous kernel with a Google Edition ROM? I may be wrong, but I don't remember Infamous being compatible with Google Edition ROMs. If you only want to use the kernel with your TouchWiz ROM, then the kernel does not need to be patched.
Here is what I am looking for on my i9505: Primary rom XTREMEPERIA_S4_V5 with Infamous kernel 2.0, secondary rom: Evil_UnWizzed_v2 with default kernel from its Aroma installation (I think it is Ktoonz kernel).
So I understand properly, I need to patch all kernels and ROMs?
Thanks!
All patched ROMs will automatically wipe the secondary system. So just patch and flash
Give me a couple minutes and I'll modify the patcher so it can do the ramdisk replacement part only. Then you can modify the updater-script for your specific ROM.
Done! Checkout version 1.6
What you want to do is edit the updater-script like I describe in the OP and then drag the boot.img (or the zip itself) onto useful/replace-ramdisk.bat in the patcher.
Please let me know if it works, thanks!
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
754This project has been discontinued. See https://github.com/chenxiaolong/DualBootPatcher/blob/master/README.md for more details.
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-1730213030Sorry 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,
Andrew29
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
