yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] gaww:
No - it is duelboot.

When you update an app in duel or Multi slot, it carries back to the primary and other slots, so apparently Android 5.0 apps that are installed will cause issues with 4.x.x ROMs, as they are not compatible.

The fix was to install the apps manually in each slot just like SuperSU - then they don't misbehave. I had to reinstall Play store in both Primary and Slot3 after installing Play Store 5.0 in patched duelboot CM12. If it had been part ot the system apps rather than user, it probably would not have been an issue
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For CM12 (Multi-Slot-2):

Patched CM12 with DualBoot Patcher 8.0.0 r99... No problem!

Installed this CM12 patched... Fail

Same for Alucard kernel

So, patched again with alpha version to see... I'll tell you more tonight or later!

OK, it doesn't seem however to have this issue! :confused:
[Galaxy S 4 i9505 Original Android Development] gaww:
Normally thy are both there, but the Alpha 9.0 links have been posted separately. On page 453, the OP posted the apk for 9.0 that worked for me.

For the snapshots, they are both here:

https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Any one able to patch super su for cm12, please share the file for multi slot 1.

I pat hed cm12 and gapps bank using first alpha...but super su is not working with first and second debug version
[Galaxy S 4 i9505 Original Android Development] phooeyllama:
https://www.dropbox.com/s/b4z0mwueiz3bphl/UPDATE-SuperSU-v2.37_multi-slot-1.zip?dl=0 /URL]
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For Primary (Echoe v37.1):

Patched the latest Echoe with DualBoot Patcher Snapshot 8.0.0 r99 (PC app)

Installed this Echoe (above, of course)

Rebooted

Updated the ramdisk of DualBoot Patcher Snapshot 8.0.0 r99 (apk)

rebooted

Now, DualBoot Patcher Snapshot 8.0.0 r99 (apk) works fine, no FC(s)

For Multi-Slot-1 (Spirit rom):

Patched the latest Alucard kernel with DualBoot Patcher Snapshot 8.0.0 r99 (PC app)

Installed this kernel

Rebooted

Now, DualBoot Patcher Snapshot 8.0.0 r99 (apk) works fine, no FC(s)

For Multi-Slot-2 (CM12):

Patched and installed CM12 (build 12 03) with DualBoot Patcher alpha6, doens't work with the snapshot 8.0.0 r99

Patched and installed Alucard kernel with DualBoot Patcher alpha6, doens't work with the snapshot 8.0.0 r99

Patched and installed supersu with DualBoot Patcher snapshot 8.0.0 r99, forced however no root

Installed DualBoot Patcher snapshot 8.0.0 r99 (FC in rom settings)

Installed DualBoot Patcher Debug, works but impossible to update the ramdisk, I think it's normal because CM12 is patched with the alpha6

So impossible to access to the apps sharing

Conclusion, all isn't good but it's better.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
If I'm not mistaken I believe the zip was for Patcher[Dual Boot] application "Multi Boot Slot 1" and not for Multirom....
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Sorry its typo..I have tried it in multi boot slot 1 only.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I will download supersu 2.37 and patch for multi slot1...

[MENTION=2477260]`SBR`[/MENTION], try this one and see if it works for you.....
[Galaxy S 4 i9505 Original Android Development] `SBR`:
will try later and post the update.

did you tested yourself.. just incase anyone has success..

As i'm able to patch multislot 1 using the latest debug version, but when installing it's not updating in the Multi-slot 1 rather it's deleting the binary from my Primary rom.

i have to reflash Primary Super su to get root.
[Galaxy S 4 i9505 Original Android Development] mudmaster:
Gapps issue with Temasek 5.0 as secondary - S5

Patched the Gapps as multiboot for the secondary ROM Temasek on my S5.

TWRP fails to flash it each time.

Seen multiple posts reporting it but no single fix
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What app?
[Galaxy S 4 i9505 Original Android Development] mudmaster:
I mean I am unable to flash the GAPPS on the secondary ROM slot.

Patched as directed using the DualBootPatcher-9.0.0Alpha6-win32_RELEASE.zip

Conifguration used -

Patcher - Multi Boot Patcher

Config - Dual Boot

Present - Custom

Auto Patcher - Standard Patcher

Exactly like the Temasek ROM except unchecked the "has boot image" (BTW tried with that as checked as well.).

Gapps used - pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip
[Galaxy S 4 i9505 Original Android Development] lukas77:
Use Preset: gapps-cyanogenmod

Works for me.
[Galaxy S 4 i9505 Original Android Development] nabeelmoeen:
Using patcher version 9 and 8 can't get patched cm 11 to install parallel to TouchWiz ROM.

I keep getting the (Status 7) slink symlink errors.

Note: available space in system partition 0.29 Gb
[Galaxy S 4 i9505 Original Android Development] MohamedN:
You need to free up some more space

Heavily debloat your tw rom..
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You haven't to choose custom in preset but gapps-cyanogen.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I tried with these Gapps apps, it doesn't work, I opened it, only it's normal, the folder building is completely different, it's Androd 5.0 building, we should ask [MENTION=4277844]chenxiaolong[/MENTION] to add it in his app... except that I think chenxiaolong is already trying to make us an app which works with this Android building.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Guys, I get always systemui fc, when I install cm12 on dual. Can you help me? I'm using alpha6 on pc to patch the rom, other versions won't work on note 3. Am I using the wrong Gapps? Which should I use?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
At the beginning... or all the times?

Gapps LP5.0 works fine.

---------- Post added at 04:29 PM ---------- Previous post was at 04:03 PM ----------

Otherwise, there are more recent there.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
with gapps, just after I try to access scurity settings, and then all the time.

without gapps right after boot, and all the time

thx, I try these.

edit: tried both... obviously its not a gapps related problem, but I managed to set everything up and now after the first reboot I always get systemui fc all the time:(

p.s. the rom is odexed, maybe because of that?
[Galaxy S 4 i9505 Original Android Development] darkassain:
took a few minutes to find out why supersu wont install

in short it wont work because it mounting system to late, he (chainfire) is doing all kinds of work on cat'ing the system (needed to find the exact android version needed), moving apps, of which there isnt any as the "extracting part" (where the dualboot mounting is done) is way way later

the quick and dirty way to it is to mount it yourself (not hard if you have the knowhow) delete the mounting commands in the updater-binary, push the new supersu package and then install

the more simpler way is by push the dualboot script to tmp (dont forget to the do the good ol chmod 777) and then rewrite the script moving the mounting to the beginning

both have worked for me..;)

TLDR; patcher needs to be rewritten (chanfire changed a few things)

might see if i have time to clean up (install without user intervention) and post a zip

EDIT: Zips posted for slot 1 and 2, enjoy..:p
[Galaxy S 4 i9505 Original Android Development] `SBR`:
good to see it worked for you, could you share the modified Zip..

i tried earlier by changing the script command, it failed in recovery itself. :(
[Galaxy S 4 i9505 Original Android Development] darkassain:
check again, just posted zips...;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I confess not to have looked the reason! :silly:
[Galaxy S 4 i9505 Original Android Development] benjamen50:
So this sounds straight forward. I patch both the zip files (CM11 nightly rom zip and Gapps Kitkat) then flash them in recovery, this should then flash CM11 and Gapps to the second rom. Is this correct? I already set CM12 as my primary rom / kernel.

I've got dual boot working, but which Super SU patched zip do I flash for second rom? slot 1 or slot 2?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It depends to your location choice for the second rom!

For Dual, supersu have to be patched like Dual

For Multi-slot-1, supersu have to be patched like Multi-slot-1

For Multi-slot-2, supersu have to be patched like Multi-slot-2

---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------

How are patched your CM11 nightly rom zip and Gapps Kitkat?

Dual

Multi-slot-1

Multi-slot-2
[Galaxy S 4 i9505 Original Android Development] benjamen50:
I Put CM11 And Gapps kitkat on Dual. Well I installed SuperSU by installing the apk from the Google play store, seems to be all working fine. Never mind. But theres one problem. The sharing apps from primary rom seems to be not working for me for some reason. I guess because 5.0 Android L handles apks differently and cannot share with 4.4.4 CM11.

Thank you for this dual boot so much! I can finally use 5.0 and 4.4.4 together.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For the apps sharing... You all understand! :good:Structure is completely different.
[Galaxy S 4 i9505 Original Android Development] benjamen50:
Edit: Never mind
[Galaxy S 4 i9505 Original Android Development] illikkalshahid:
anyone able to dual boot cm12?

i have tried cm12 antaresone rom as secondary rom, but installation always fails even if patching is successful. is there any solutions?
[Galaxy S 4 i9505 Original Android Development] benjamen50:
This is why I installed the CM 12 antares rom as a primary rom and another rom such as CM11 as a secondary rom to reduce the chances of having conflicts or problems with the roms.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
CM12 is installed like Multi-Slot-1, no issue, all works fine. I patched it with DualBoot Patcher 9.0.0 alpha6, I patched it like I described before here.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Has anybody managed to run cm12(temasek) as secondary on note 3?
[Galaxy S 4 i9505 Original Android Development] gaww:
I have it working O as secondary. If you have a TW ROM as primary, you may not have enought room In some cases, you can flash it but it won't boot (been there - lol).

Use Duelboot utilities to see how much room you have in system after you have flashed it (or tried to). IN my case above, it was zero.
[Galaxy S 4 i9505 Original Android Development] illikkalshahid:
I couldn't even flash.. Got some error. I have patched the zip. But fails to patch
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Yes you can backup and restore you entire dual boot setup, but you have to make sure you back up everything and then restore everything when you decide to do so.
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Oh okay, alright. So we just go on a full-on backup? Do we have to boot into both of the separate ROMS and then backup or do we boot into just the primary and do a full backup? And when you say restore everything, do you mean to just make sure that I don't do an advanced restore, but instead a full on restore?
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Shouldn't matter. Because secondary rom is stored within the primary rom, so if you make a backup it will backup everything as is. And when you restore make sure to restore all the partitions you saved from the backup (boot, system, data, cache, I also include recovery and preload for dual boot backups just in case although I'm not sure those last two are necessary. )
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahhh, I think I know why. Could you try adding this:

file_info.bootimg = "boot.img"

right before these two lines?

print("")
print("Replacing ramdisk with " + file_info.ramdisk)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's a way to choose the ROMs while booting for the Galaxy S3, but this is something that only a really good kernel dev could implement for the Galaxy S4 :p The graphics drivers are part of the ROM, so the developer needs to know how to directly communicate with the GPU in order to show a menu (at least that's how I understand it). And of course, that means the same kernel has to be used for both ROMs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's exactly right. A backup will always restore your phone 100% to the state it was in before :good:

EDIT: Oops, [MENTION=5294952]marcoxx626[/MENTION]'s answer above is much better :)
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hey mate have you thought about having a backup/restore feature for 2nd ROM only in the dual boot utilities app?

Also maybe backup primary ROM kernel to internal SD The only mistake I made which took an effort to fix was I formatted /system by accident flashing a non patched zip and lost dual boot kernel images

Edit: my data was intact but my recovery was still reading the dual boot layout and I could nt switch to primary kernel cos it was wiped
[Galaxy S 4 i9505 Original Android Development] omariscal1019:
Does this work on the sprint gs4
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I must really be stupid :) When I first started working on dual booting I thought about what the best place for the kernels would be: /system, /cache, /data, or external SD. I wonder why I didn't think of the internal SD... :confused:

I just need to think of the best way to transition to using the internal SD. I'll probably have the app move the kernels automatically the next time the ROM is switched.

EDIT: Actually, could you give me a situation where having the kernel on the internal SD would help? If you flashed a non-patched ROM by accident, you would need to flash the primary and secondary ROM again anyway.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
You can use the online nandroid app which let's you backup only the current ROM that is running. In other words, you don't have to boot into recovery to make a backup. So if you're on the secondary rom, open the online nandroid app and it'll make a backup of just your secondary rom. I figured this out by accident when I was actually trying to use the app to backup both lol
[Galaxy S 4 i9505 Original Android Development] SkizzyNinja:
EDIT: Didn't read the op well enough like a noobynoob

sent from my all Alpha no Beta S4
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
It would be much better if you used alpha as your primary rom because:

1) its pretty large

2) has a complicated aroma script without a non wipe option

3)aroma is a pain in the A to make compatible for dual boot lol

Best option would be to use Alpha as your primary so it doesn't have to be patched and use your aosp/aokp/pa rom as secondary because plenty of these are already compatible, and if they aren't it's much easier for Chen.

Edit: I'm assuming the other rom you're flashing is not touchwiz because no other touchwiz rom can be dual booted alongside Alpha, even if it was a super debloated touchwiz rom. That's because once the zips are unpacked they would take up more than 2.9 GB which is the limit for your total system partition. Sorry for the long post :p lol
[Galaxy S 4 i9505 Original Android Development] SkizzyNinja:
No need to apologize. Your explanation is perfect and thank you for correcting me and for the advice. Yes the other ROM would be PAC mans lol. But every you made sense so thank you for clarifying. My first post is no invalid :beer:

sent from my all Alpha no Beta S4
[Galaxy S 4 i9505 Original Android Development] 88exp88:
Would this work with the sprint variant?
[Galaxy S 4 i9505 Original Android Development] SkizzyNinja:
Almost 100% sure you can

sent from my all Alpha no Beta S4
[Galaxy S 4 i9505 Original Android Development] ntajlis:
Yes it will work. I already test out a number of 4.3 rom. I have it working since day 1 of OP patcher release.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Well glad I helped!
[Galaxy S 4 i9505 Original Android Development] RK:
That did not work. I had to add

file_info.bootimg = "boot.img"

to replaceramdisk.py as you suggested AND move the

files_to_patch = files_in_patch(file_info.patch)

line inside an if statement as:

files_to_patch = ""
if file_info.patch != "":
files_to_patch = files_in_patch(file_info.patch)

in patchfile.py right after the lines (182 and 183)

def patch_zip(zip_file, file_info):
print("--- Please wait. This may take a while ---")

Now it works! :)
[Galaxy S 4 i9505 Original Android Development] gaww:
If I go back and forth between single ROM nandroids and duel boot nandroids is it necessary to first flash enable duelboot or disable duelboot as appropriate ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Awesome, thanks! :D I've included the fix in version 1.17.3: https://github.com/chenxiaolong/DualBootPatcher/commit/c672fb42ef4b697c1e7466a2b55057a795f8c705
[Galaxy S 4 i9505 Original Android Development] gaww:
Which version Patcher?

You have to use 9.0 Alpha PC or apk for CM12. If apk, it has to be version 6.0 that is about 17 mb (last one was much smaller).
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I also think that's a lack of space in the system partition, you should rather install it like Multi-Slot-x.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Will there be an update due to lollipops new structure?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
He worked on that, now I don't know.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I just tested the apk version for android 8.0.0.r378 and patching is working correctly but it crash opening "rom setting" option. Back to r99 for the moment. I'm with S4 with CM11 as secondary rom.

Thanks the great support Chen!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I didn't see this new Snapshot... Thanks for info ! ;)
[Galaxy S 4 i9505 Original Android Development] sronweb:
You are welcome! Can you test it too? I could patch today's Cm11 nightly using the default settings but finally I cannot flash it because I got a message on the recovery that the rom is not compatible. No issue using previous patcher (r99).
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK, I already tested a bit, I'll try more tomorrow. Rom settings doesn't work but I think it's normal.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Testing r382 now!!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
With this one, I've successful to patch the Alucard kernel for CM12. I have to wait for its installation, my battery is empty.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Sorry for the annoying question guys, but where can I get the snapshots? Any link?
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Thank you sir.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Doesn't work! :(

Edit

:

It installs it without issue but it stuck on Samsung logo.

Edit 2

:

With the alpha6, it works fine.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Anyone tried patching latest ge lollipop by danvdh?
[Galaxy S 4 i9505 Original Android Development] omnifarious:
I used r382, patched to multi-slot-2 and got a boot loop. I'll try later today when I'm on lunch
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Try with DualBoot Patcher 9.0.0 alpha6, it should work.
[Galaxy S 4 i9505 Original Android Development] Chikov:
How do you delete the MultipleKernels folder? (I'm no longer using dual boot, after full wipe ecc), tried everything root explorer and all, it says could not be deleted
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Via recovery...
[Galaxy S 4 i9505 Original Android Development] amieldl143:
Bro.. Can you pm me the the dual boot patch.. Dunno if I have alpha 6.. I have dual boot debug.. Tried it. I flashed enable dual boot file then used dual boot patch 9 debug. Says not supported but patch gpe s4 ROM from dan anyways.. It flashed the main and I had to flash back to tw ROM...thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Below
[Galaxy S 4 i9505 Original Android Development] gaww:
I was not able to patch with that version, but dis do with an earlier one. See link below:

https://www.dropbox.com/s/8vm2rp0lvr85b3w/Android_GUI-debug.apk?dl=0
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Does it matter, whether the rom is deodexed or not?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I haven't successful with it.

The rom should be in the list of the app, if the Dev didn't add it, the patcher will not work... normally.
[Galaxy S 4 i9505 Original Android Development] dicko101:
Cm12 lollipop

Hi guys, I keep getting error in... (status 6) when I try to install a patched version of cm-12-20141215-OPTIMIZED-jflte.zip, its recognised by the patcher app, was going to try manually patching but thought I'd ask here first, any suggestions? Thanks.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No issue with the alpha6 app posted more up, however, I use a small feint, I rename the zip in order that patcher doesn't recognize the rom, like that, I set my own settings

cm-12-20141215-OPTIMIZED-jflte.zip renamed in OPTIMIZED-jflte.zip

Launching to Dual Boot app (alpha6)

Select my renamed file

In preset, I choose "Custom"

I also tick "Has a boot img"

And to finish, in Ramdisk, I select "jflte/AOSP/AOSP"

Normally, when you would patch a unknown file, the settings have to be already defined like that!
[Galaxy S 4 i9505 Original Android Development] dicko101:
Thanks franzyroy, I'll try that and get back with the result.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
;)

I forgot, in the "auto patcher" box, you should take "Standard" ! :silly:
[Galaxy S 4 i9505 Original Android Development] dicko101:
No luck unfortunately, I did read somewhere about editing the paths in the updater script, but I couldn't find the lines they referenced in the guide, not sure what's going on, would try to just flash the original zip as primary to see how that goes but I don't want to over write my primary.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What is your jflte model? jfltexx or another?
[Galaxy S 4 i9505 Original Android Development] gaww:
I patched latest CM12 5.0.1 "successfully", but when flashed - it would not complete the flash. For now, use the tweaked PC zip (with .dll's added to folder and it flashed and came up OK.

I have been doing it as duelboot, and if flash GAPPs also, with app sharing - some of them (play store, play services in particular), they take down the 4.4.4 TW primary and 4.4.2 multislot versions and it takes some time to get them working again - which then usually knocks out the Cm12 app again.

I had tried multiboot setup, which setup OK, but as the primary was the 4.4.4 TW, and as it need to have a "patched" kernel setup for it (and none of the offered ones were 4.4.4), that setup just did not work out - so went back to duelboot - which from the above - has its own issues.

CM12 is not and probably would not be my daily, so not really concerned with not using GAPPs right now, but wold hope there is a fix somewhere down the road for the issues caused by app sharing.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For me, no issue with the flash of CM12, with my method.

No issue (or almost), I've 3 roms, 2 are patched with DualBoot Patcher Snapshot 8.0.0 r99 (PC), 1 is with the alpha6 (PC), on the first 2, "DualBoot Patcher Snapshot 8.0.0 r99" app works for the apps sharing and also all the rest, even with the third CM12. In fact, there is only the apps sharing which doesn't work on CM12, no matter, I can do it with the 2 others roms.
[Galaxy S 4 i9505 Original Android Development] dicko101:
According to Dualbootutilities, my model number is jfltexx, I'm not too concerned about getting this particular rom working, just really want a real lollipop rom.