yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Bejda:
That makes two times I see peoples putting their hopes about dual-boot shared data's on sms but I guess that's typically some system apps data's that can't be shared easily.

Maybe it's different for alternative market messaging apps I don't really know but for rom bundled Mms.apk we can see that TitaniumBackup use .xml for this and if you take for instance Contacts.apk and its affiliated apps data's you sometimes even can't bring data's from an aosp based rom to another aosp based rom. Let's say you flash AOKP coming from PA with nowipe you're likely to get an android.acore.process fc that will keep coming until you clear Contact storage data's and such...

Just to say that imho shared app's data's would only be possible for user's apps (/data/app) and if they share their data's (/data/data) the best would be for users to determine which apps share data's across rom's (just as Chenxialong said i guess lol).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're absolutely right about this. Just about every ROM stores SMS and MMS message differently. The databases are just too different. I highly doubt sharing messages will ever be possible, unless there's a third party app that can convert the databases to a universal format before rebooting :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I have gotten the current implementation to run on Android, but it really sucks. I will need to change it so that it only extracts files that need to be modified instead of the whole zip.

Because phone storage is so slow, the current patcher would take >45 minutes to patch a TouchWiz ROM.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Really glad you're liking it :)

One quick question: did the error happen with CWM or another recovery?
[Galaxy S 4 i9505 Original Android Development] ntajlis:
I'm using TWRP. I have no problem at all. As long as the supported rom and kernel get pass the patching process. Everything is working fine.
[Galaxy S 4 i9505 Original Android Development] Dualz:
On both dual boots I mentioned on my post earlier back, I used TWRP 2.6.0.0 and both worked fine.

I don't use 2.6.10 nor 2.6.30 as both gave me errors when flashing.
[Galaxy S 4 i9505 Original Android Development] davidep85:
I used last Cwm. maybe I did something wrong.. did you try all the root functions of slim Bean?

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Finally Friday...no school work, so more time to work on dual boot :)

Version 1.10 is now released. This adds support for BaNkS's mini-gapps core zip: http://xdaforums.com/showthread.php?t=2012857

I've also optimized the patcher script so the patching should be a bit faster now. It only needs to do one full read of the original zip file and one full write of the new zip file. This is the fastest it's going to get because the zip file format doesn't allow for deleting and modifying of files without recompression. It now only needs <10 MB of temporary space too :)

More versions will be released today as I add support for the other stuff on my todo list.

Changes: https://github.com/chenxiaolong/DualBootPatcher/commit/fbb0a552804830adbde3207b24d1e137104b08f4
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Dude it was already fast! Lol you're a beast bro. Any news on the triple boot? :P
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 1.11 now available:

* Fixes boot.img repacking bug in version 1.10.and 1.10.1

* Adds support for AROMA Google Apps for Slim Bean
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Triple boot will come after I add support for all the ROMs that people have requested :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 1.12 now available. Changes:

* JellyBeer support

* jamal2367's Google Edition ROM support

* ComaDose support

I don't have screenshots this time, but I did test all of them :)
[Galaxy S 4 i9505 Original Android Development] Tylog:
Great :) tomorrow I have finally time to test your dual boot. The past two weeks found no time for it. 'm curious how well it runs :)

Thank you for it.

GT-I9505 ~ SlimBean 4.3
[Galaxy S 4 i9505 Original Android Development] Bejda:
Please Mr,another one ;)

http://xdaforums.com/showthread.php?t=2397511
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Evil UnWizzed support now available in version 1.13 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Will do :)
[Galaxy S 4 i9505 Original Android Development] TheMorpheus:
Can I update the application without messing up the dual boot??

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Supported in version 1.14 of the patcher :)
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Runs perfectly man!
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Hi, I have this problem too, Touchwiz 4.3 and Solid Explorer + ES File Manager installed.. :(

The last working version of the patcher is 4.0.4
[Galaxy S 4 i9505 Original Android Development] peppe130:
I don't know why but sometimes, when you patch an aroma zip, the patcher get stuck

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Technical:
Is there anything we can do?

I won't even test to patch the file in the phone. It's almost 2Gb and the phone can't compete with Windows in this case.
[Galaxy S 4 i9505 Original Android Development] peppe130:
I think that the only way to patch an aroma zip is to do it manually

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] calebcabob:
patcher freeze

Yeah, I am on TouchWiz, but also have Solid Explorer, ES File Explorer and tried with X-Plore File Manager as well.

Thank you
[Galaxy S 4 i9505 Original Android Development] franzyroy:
And if you can again add the 'exit' button... thanks!
[Galaxy S 4 i9505 Original Android Development] fonetval:
Forced Close with Patcher > 4.0.4

Hi,

I confirm the same ForceClose with newer version than 4.0.4 (at least 4.1.2 and 5.0.2 I've tested) of the patcher...

Is there any risk to patch with the "old" 4.0.4 release ?

NB. I have RootExplorer, FX and ES Explorer installed.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No risk if it is supported. Namely, if it is a kernel / rom with F2FS, it should mandatory have at least version 5.
[Galaxy S 4 i9505 Original Android Development] Technical:
Well, I've patched Echoe, Phonix and Chaos without problems.

Also GoldenEye until version 32 got installed (although it does not have Arome installer at that time).
[Galaxy S 4 i9505 Original Android Development] fonetval:
Hi,

[MENTION=4277844]chenxiaolong[/MENTION] : Thanks for this Tuto. I'm not sure (because a lot of people have already read it...) but it seems that there's an error in post #1 in the section "Instructions for dual booting" : at point n° 2. "Open the app and set the current kernel as the primary kernel" I think that the "app" is not the Dual Boot Patcher (like the 1. said) but the Dual Boot Switcher no ?

I think you should replace Patcher by Switcher in point 1 and 8...

If I'm right, I have a question : at point 4 "Patch the Rom", is it important to have set the kernel (by Dual Boot Switcher) before patching ?

I hope that my newbie read isn't too wrong...

Thanks.

EDIT : Post obsolete since May 23th and the V 5.0.0. Beg you pardon (but Force Close for me with the 5.x, so I couldn't test/see it...)
[Galaxy S 4 i9505 Original Android Development] Phenom2122:
[MENTION=4277844]chenxiaolong[/MENTION] - I thought you would be interested to know, I am successfully running a dual boot on my S4 Mini. Haven't used it extensively yet but so far so good. Don't know why I didn't just test for myself to see if it works first :)
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
Thsi might have been reported before, but everytime I install gapps to any multi-slot, I constantly get force closes. I think it has something to do with permissions after the installation (not for shure I'm not really a rom an file expert). It has happened to me on CM and AOKP gapps. It is fine when installed to the secondary slot.

Edit: when I don't flash gapps the rom runs fine so it has to be something with the way gapps are patched. Patched using the 5.0.2 android app

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] peppe130:
The new Dual Boot's app is all in one and its name is Dual Boot Patcher.. Is not an error

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] calebcabob:
Link?:)

Do you or anybody have a link to the older versions of the patcher apk? I am interested in trying any previous versions in hopes that I don't get the force close. It might be my phone...i have tons of apps and tweaks installed at the moment.

Thanks!... To anyone who can share a link:)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There! ;)
[Galaxy S 4 i9505 Original Android Development] Phenom2122:
Ok I really apologise, because I know this must have been discussed somewhere in this thread, but I see no mention of it in the OP and I have now skimmed through many pages starting from the beginning and end. Could someone kindly recap for me? How does one go about sharing data between roms? Is this limited to only /data or is there a way to share /system as well? This would be useful if both my roms support the same gapps or to get rid of a duplicate email.apk or messaging.apk eg.
[Galaxy S 4 i9505 Original Android Development] fonetval:
[MENTION=5349944]calebcabob[/MENTION] : so, with the old patcher, you'll need the old switcher too

I did it yesterday, and it boots fine... I've not tested extensively other features of my new secondary ROM...
[Galaxy S 4 i9505 Original Android Development] Technical:
We all want this, but, this is generally dangerous and could bring a lot of apps errors.

At least, we could be able to share user apps data (if posible), not sharing the system apps (and data).
[Galaxy S 4 i9505 Original Android Development] Phenom2122:
But flashing custom roms in the first place is some sort of risk. Surely you would just have to know what sort of system apps and data to share and what not to? For example I use the Cyanogen email app but mainly run Carbon and Slim. And I can successfully backup and restore data between the two. There are many other 3rd party apps that I extracted the libs from and am successfully running as system apps in any rom I try. If this is possible, why would it not be just as simple to share these apps. Certainly there is a limit and I couldn't share my settings.apk but it depends more on what the app does rather then which partition it is in.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for testing, that's great news! So the patcher now works on the Galaxy S4, S4 Mini, and S4 Active, which is awesome :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the bug report! It's fixed in version 6.0.0 (coming out today ;))
[Galaxy S 4 i9505 Original Android Development] Technical:
Good! I was almost giving up on Goldeneye as second ROM because I cannot manage its updates. Really thanks.
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!

[MENTION=4277844]chenxiaolong[/MENTION] do you know how to solve it or is it a bug?

Verzonden vanaf mijn iPad met behulp van Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
At the moment, the patcher only supports Qualcomm-based devices. It's not compatible with the i9500's Exynos chipset.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It sounds like you ran out of space on /cache if only the multi-slots aren't working. Could you boot back into the primary ROM and use this app to see how much space you have on /cache? https://play.google.com/store/apps/details?id=ru.krikun.freespace
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) Are you talking about this ROM http://xdaforums.com/showthread.php?t=2764493 or this ROM http://xdaforums.com/showthread.php?t=2748022?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, that's strange. Would you mind making a logcat for me? You can do that with this app: https://play.google.com/store/apps/details?id=scd.lcex Just open Logcat Extreme, then open the patcher and make it crash, go back to Logcat Extreme and tap the save button.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For the next version, the exit button will still be hidden by default (because Google recommends against exit buttons), but if you tap and hold the logo, it will show up again :) (and it will stay there until you clear data)
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Sure, here it is: https://www.dropbox.com/s/g5yhvyqjg97v2gb/Log_2014-06-01_10-35-46.txt

;)

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I understand! ;)

However, you said:"the exit button will still be hidden...". On the actual version, there is no exit button even by tapping and holding the logo, right?
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
I checked it and I had more than a gig of free space on cache with AOKP on the multi-slot 1. But I tried it with some other roms and I think it is someting with the AOKP gapps. I'm running this right now, with every rom installed fully working, without force closes, and still 685mb available on the cache partition:

Primary: TouchWiz 4.4.2 NB9, SuperSU 1.99

Secondary: ParanoidAndroid 4.3 BETA 7, with stock PA gapps package, SuperSU 1.99

Multi-slot 1: CyanogenMod 11 M6 with CM gapps package, SuperSU 1.99

Multi-slot 2: OmniROM 4.4.2 2014-06-01 nightly with stock PA gapps package, SuperSU 1.99

Surprisingly both roms in multi-slot 1 and 2 work fine, even with gapps, but when I install AOKP with the AOKP gapps package I get constant force closes making it unusable (can't even go past setup wizard)

If I only install AOKP, without gapps, I have no problems, everything works, but it is kind of useless to me as I really need gapps.

I tried installing it in multi-slot 1, 2, tried to first let it boot and then install gapps, I tried patching the zip with the custom preset, the CM gapps preset, AOKP gapps preset, but it never works. I don't know if it works in the secondary slot, and I'm not gonna try that because I use the rom that is currently installed to that slot alot. I will try to install AOKP on slot 3 but with a different gapps package (CM, PA,...) and report back.

I don't think it has anything to do with free space: I have 100mb free on system, 2gb on data, 685mb on cache,...

It has to be something with the AOKP gapps package, or the way it is patched, as CM and PA gapps work fine on their corresponding rom.

Edit: It still gives force closes when installing AOKP with CM and PA gapps. I really have no idea why. I will try to install Carbon ROM or PAC-rom to see if this is an AOKP-only problem for me

Edit 2: I tried installing SlimKat with its corresponding gapps package, that worked as well so the problem has to be with AOKP. It only happens on AOKP, when installing gapps
[Galaxy S 4 i9505 Original Android Development] calebcabob:
I just happened to flash a new ROM this weekend...so I tried the patcher app afterwards and it was a SUCCESS! :) ...not sure what was up with the last setup I had.
[Galaxy S 4 i9505 Original Android Development] royredman:
Hi. Is there any way we can backup different ROM slots instead of just the whole group of ROMs? I want to he able to only backup my second ROM so I can try installing other things without having to restore the whole system
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
In the first post there is a link to another tread of someone who made a backup utility. It has an app and a zip. I haven't tested it, but I would first try the zip as it is an aroma installer that should be able to backup all roms individually.

Edit: this is the link:

http://xdaforums.com/showthread.php?t=2491299
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yes, it exists, you should just find it on this thread... I don't remember where it is! :(

---------- Post added at 07:00 PM ---------- Previous post was at 06:54 PM ----------

There is even an app here.

---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------

@dafonehacker

Ooops, I didn't see your link, it's the same that the one I put... sorry!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, the feature is not in version 5.0.2. It will be in version 6.0.0 (releasing today once I figure out the TouchWiz file chooser issue) :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Could you tell me what ROM (and which version) you were running where it failed?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK... Thanks! ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! :) I think I know what's wrong now. Could you tell me which ROM (and ROM version) you are running so I can test it?
[Galaxy S 4 i9505 Original Android Development] ktm_91:
DjeMBeY's stock MK8 (4.3) deodexed http://xdaforums.com/showthread.php?t=2250824 with talexop kernel 1.3 ;)
[Galaxy S 4 i9505 Original Android Development] calebcabob:
Yeah, I was running Bonestock 4.3 v2.1 - strange too, I've never had any compatibility issues with any Bonestock ROMs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn it, couldn't release the new version today :( I need another day to fix TouchWiz 4.3 crashing issue (which, by the way, was a dumb mistake on my part :p).
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No problem, we can wait! ;) Thanks!
[Galaxy S 4 i9505 Original Android Development] calebcabob:
I just realized I never specified that the new ROM I had success with was actually a TouchWiz 4.4.2 ROM...but it sounds like you are already confident with it being just a TouchWiz 4.3 issue... Just wanted to reassure you with that info. Nice work, seriously!! Your apps are so smooth and freakin PRO!!

---------- Post added at 07:13 AM ---------- Previous post was at 07:00 AM ----------

I just have one more question for anyone who might know, I have my two ROMs installed. I'm just wondering if I need to run the aroma Dual-Boot Tool each to lime I want to switch to booting the ROM I'm not currently running. I noticed there is some mention of there being a ROM selection option available (after the SAMSUNG logo) when first powering on the phone. I can't seem to get to that screen. I have the Switcher app installed in both ROMs. Any ideas? Thanks! :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
No option at boot belongs to another multiboot solution ;)

You simply use DualBootPatcher apk (choose rom) to switch roms (or on previous versions the dedicated DualBootSwitcher apk).

DualBootUtilities Aroma zip is more a security tool,if a rom doesn't boot for any reason you still can switch to another from recovery.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the confirmation! I actually found out that I not only broke it for TouchWiz 4.3, but also for any ROM older than Android 4.4. D'oh!

Anyway, it's fixed (just had to change a single digit in the code) and I'm preparing the next release now :laugh:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 6.0.0 is now released! As usual, let me know if there are any issues.

Changes:

First of all, the patcher got a bit smarter again :) If you're patching an unsupported file, the first thing you'll notice is that there is no longer a loki option. The other thing you probably notice is that the boot images are now autodetected by default. The patcher is now able to intelligently find all the boot images in a zip and determine if they're loki'd. This new autodetection stuff is available on Android, PC, and command line.

The crashing issue on pre-Android 4.4 ROMs is finally fixed! If you care about the technical details, read on :)

The issue began when I updated Python for Android to 3.4.0. Python 3 has optional support for the non-POSIX system call futimens(). This was added to Android's bionic C library in 4.4: https://android-review.googlesource.com/#/c/63321/. My mistake was compiling Python 3 with the Android 4.4 NDK toolchain. Python 3 ended up being built with support for futimens() and when it was run on older systems, it crashed because /system/lib/libc.so didn't provide that function. Anyway, the fix was to use Android 4.3 NDK toolchain instead. (Also, Python was updated to 3.4.1 for this release).

Minor changes:

If you tap and hold the logo on the main screen of the Android app, the Exit button will show up in the navigation drawer again. Also, the Android app will now show an error message if no file manager is installed, instead of just crashing.

More technical changes:

Fixed dumb C programming mistake in the Linux launcher executable where the PATH environment variable was modified while it was being searched, causing qtmain.py to run with PATH=/usr/local/sbin (or whatever the first directory in PATH is). This caused the patcher to fail with an unhelpful error message when it looked for the 'patch' executable and couldn't find it.

unlokibootimg was updated so that a gzip header with a non-zero timestamp are preferred, but if one doesn't exist, it will fall back to other gzip headers with a zero timestamp. This fixes a boot image extraction issue with some older versions of faux kernel for jflteatt.

All of the patchinfo files have been updated to use a new PatchInfo(!!) class, instead of the old, ambiguous FileInfo class.

dualboot.sh is now free of warnings from shellcheck

If anyone was using the new automated mode of the 'patch-file.sh' script, '--bootimg auto' can now be passed to enable the autodetection features.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Can you add support for omega rom?

And what should be done to revert everything to stock?
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Great! Now it works perfectly for me! :D

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Guys - a little help please (and a bit of patience if this has already been answered). I have echo rom in first slot, Danvdh GE in second slot which I successfully backed up and restored using the backup/restore script, now I am trying to put slimsaberkat in multi slot 1 - primary and dual work well, however when I put slim in multi 1 and then try and boot into it this boots into primary rom and ends in bootloop on rom splash screen. When I go back into utilities zip and switch to primary that works, dual works, just can't get into multi 1 even though when I try and switch on the app I can see slim in multi 1 - what could be the problem?

Any help, much appreciated :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
Ah i was about to warn you but i didn't had time,didn't had time to report by here as well until now..

Same story for me SlimSaberKat as multislot2 > keeps booting on primary after flash (and yeah our Touchwiz primary rom shows a slight ingratitude towards the new kernel that we offer lol). It seems the issue is with Alucard kernel,if you patch latest Alucard zip same issue occurs.

I had to patch KT kernel as multislot 2 and flash it for SlimSaber boots fine but well,it kinda breaks the purpose of flashing Kantjer's build without its default settings/bundled kernel.

[MENTION=4277844]chenxiaolong[/MENTION] :)

All seems fine,updater-script and all,ramdisk seems edited as well (at least boot.img size differs once patched) but it always boot as primary kernel.

boot.img before patch:

https://app.box.com/s/42758pwd60ch9t11dtvu

Once patched:

https://app.box.com/s/si90vd23uwjvu58hmf0h

Using 6.0.0 patcher apk version.