yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Weirdly, I also have it with DualBoot Patcher 8.0.0 r99, I've it on multi-slot 1 & 2, I also have noticed it's impossible to me to update the binaries, however the root works fine (at least for multi-slot-1 "Spirit rom", other is CM12 so maybe the issue with dualboot), I only can't go in supersu app for multi-slot-1, multi-slot-2 hasn't the root (problem solely with dualboot).
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Hi, can you also add rom icon customization to the patcher please? That would be great:)
[Galaxy S 4 i9505 Original Android Development] MohamedN:
That must be it because I have tried it now on cm12 and it patches fine.

However patching supersu zip file with the new apk(as multislot1) results is patched successfully but when flashing, it flashes on the primary rom
[Galaxy S 4 i9505 Original Android Development] lukas77:
apk patcher v9DEBUG works OK on S5 G900F on Android L. FC on KK.

Thank you sir.

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] gaww:
Do you by any chance have duelboot versions ?

I would guess there will still be the root/SuperSU issue since that won't patch.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No but it's no hard to make it, just follow this mini tuto:

Download the latest CM12 like cm-12-2014112x-UNOFFICIAL-jflte.zip

Rename it like that (for example): UNOFFICIAL-jflte.zip

Patch it with DualBoot Patcher 9.0.0 alpha6

To patch, use these settings

For the Gapps, in Preset, choose "gapps-paranoid"

That's all!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've updated the debug build in by previous post. It should no longer crash in pre-5.0 ROMs :)

http://xdaforums.com/showthread.php?p=57002549#post57002549
[Galaxy S 4 i9505 Original Android Development] franzyroy:
So it is possible to access to all settings with!

---------- Post added at 08:33 PM ---------- Previous post was at 07:45 PM ----------

After to have successful to patch and install CM12, I still had to root CM12, now it's GOOD!

My method

:

Go to another rom with supersu in data/app

Share it with CM12

Install this supersu patched (patched with DualBoot Patcher 8.0.0 r99)

Reboot

Update the binaries

Reboot

And now, it works fine! ;)
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Can you please provide a patched supersu for multislot 1

Tried here but doesn't work..
[Galaxy S 4 i9505 Original Android Development] franzyroy:
supersu 2.16 multi-slot-1
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I've been able to access the rom settings with, the new debug version, but still can't update the ramdisk, hope it will be fixed
[Galaxy S 4 i9505 Original Android Development] franzyroy:
However, I warn you that if you want the root is operational, you will have to use my tutorial above.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Failed as well

Given up and installed multirom

Rocking with best of both worlds now :cool:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You'd be the one missed step. But good for you if it works now with MultiROM. For the moment, I prefer to stay on my method.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Have managed to get it working with your method as well :thumbup:
[Galaxy S 4 i9505 Original Android Development] monkteo:
Your method it's PERFECT , work very good for my!

THX
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I don't understand :confused: Have you successful... or not?

Glad to don't be alone! ;)
[Galaxy S 4 i9505 Original Android Development] MohamedN:
At first I wasn't successful then repeating it following exact same steps and boom

Rooted and successfully installed binaries on my multislot1

Now I'm removing multirom

Thanks for your efforts :thumbup:

Edit:

Just wanted to say multirom is Amazing and well developed, I just like DualBoot more

Thanks for both awesome developers for such great stuff that keeps our phone alive
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I'm happy to help you! ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
I see that Slot 1 & 2 are working this way, but what about duelboot slot ?

I have patched CM11 and GAPPs with updated Alpha, but it will not handle duelboot SuperSU. I only have room in duelboot to do this, as the cache is pretty full already.

I have it ll working with multiboot, but would like to get it back to duelboot due to app sharing.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Sorry but I don't understand... or not completely! :( With DualBoot, it have also to work! You have no supersu to share?
[Galaxy S 4 i9505 Original Android Development] Wegaxas:
Lost Primary after accidental wipe of /system

Hi All,

i feel realy stupid, :crying: but i accidentaly wiped /system in the CWM Recovery. Yes yes rtfm.....!

But maybe some one can help me annyway.

Now i can`t switch back to my primary rom. (TW on I9295)

In the Dual Boot Patcher App (8.0) i just see my secondary rom (CM11 wich im currently in ) but i cant see my primary, to switch back to it.

i still see the primary.img in /MultiKernels though.

Is there any way to may be manually switch roms?

I couldn`t find anny thing via Google or in this thread, maybe i just overlook the right answer somewhere?

I`m sure not to bee the first idiot to make this mistake..... ? :confused: ?

i very much aprecheate your help!!! :angel:

Greets

Wegaxas
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Flash again your primary rom like primary upgrade!

Send to my GT-I9505

---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------

At least there is no TW rom (custom) for your model?! I don't know.

Send to my GT-I9505
[Galaxy S 4 i9505 Original Android Development] Wegaxas:
Hi franzyroy,

there is a 4.4.2 from Sam for the SG4 activ alias GT-I9295 / alias jactivelte and thanks to the ammazing work of [MENTION=3876105]spegelius[/MENTION] and the others in this Thread http://xdaforums.com/showthread.php?t=2658534 there is a CM11 nightly for my device. :)

The dual boot with TW and CM11 worked very smoothly, until i messed it up... ;)

I`ll try now a flash of the 4.4.2 TW from Sam. Well i guess i have to reinstall all the dual boot stuff again afterwards...

Stupidity needs to be punished.. :(

Thank you for the hint, i hade hoped i could fix my mistake without having to flash stock via odin.

Greets

wegaxas
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For info

:

When you've got the root with my method (like the original), you can now update CM12 without to have to do again the install of the root. It always is functionnal.

Enjoy! ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
I have have SuperSU, but cannot patch it for secondarily for CM12.

I used it to root CM12 in multiboot.

I need to get it patched for duel boot.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Do you want that (supersu 2.16_dual)? ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes - thanks !

How did you patch it? It crashes with the Alpha apk and I cannot try the PC Alpha Patcher, as it is apparently 32 bit and doesn't play nice with my 64 bit C++ drivers.

Update - I patched the CM12 as secondary with the Alpha apk and it indicated successful, but get error on trying to flash the .duelboot ROM in recovery.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
With DualBoot patcher snapshot 8.0.0 r99.

Send to my GT-I9505
[Galaxy S 4 i9505 Original Android Development] gaww:
Funny - I tried that also - but only with the #99 apk.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I also do it with the alpha version but I didn't test it because, before it didn't work, now I can't test it now because I am always rooted. However, it's patched, even with Windows 8.1 64bits. I patch with the PC app.

Otherwise, I patch it with the PC app.

Send to my GT-I9505
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi , I have a question ? tehnical question !

I now how to use dualboot (I have 4 rom on my phone) but I decide to keep only 2 rom permanently on my phone , and play on free slot with other rom so my question is ;

how to instal the rom's (I will instal an TW on primary) no doubt

and the secondary rom in what slot ?

secondary - multislot1 or multislot2 ? what is the best configuration ?

THX
[Galaxy S 4 i9505 Original Android Development] franzyroy:
My council (and also my choice/ config for me) is multi-slot-1, it avoids to limit the primary, mainly when it's a TW.

---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------

After multislot-1 or 2, it's the same thing.
[Galaxy S 4 i9505 Original Android Development] gaww:
Will the final version of 9.0 be usable on 64 bit Windows ? The Alpha debug is apparently 32 bit and does not play well with 64 bit drivers.I pushed a 32 bit version of msvcr.dll into the folder but it still did not work.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Maybe, I don't know, I didn't really test it (at least on the phone), it patchs on PC, I didn't test the patch on the phone.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Did you make the full wipes? It's apparently necessary.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
How can i update my ramdisk on secondary rom?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Block images can't be extracted in normal way, but you can install CM12 on your device and make a dump of /system. Next part is to rewrite the updater-script and rebuild ROM's tree (system->app/bin/etc...) then create the zip. Or, you may try to ask to S5 maintainer to disable block-based OTA and use the normal one.

Block-based OTA broke the hell (it's enabled by default in Lollipop's build system), that's why I build my CM12 for S4 in standard flashable zip

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I just took the final for my hardest class, so I should have plenty of free time to work on this now :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
New debug version of the patcher! Only one change this time: SuperSU should flash properly again.

The issue was that the SuperSU install script extracts some files using the recovery's standalone unzip tool (separate tool not normally used for flashing). It turns out that this doesn't support some parts of the zip file format (notably data descriptors), so the files couldn't be extracted. SuperSU's installer is now patched to include zlib's miniunzip tool, which can extract the zip files perfectly.

(Same warning as last time: debug builds will spam the crap out of the logcat ;))
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm guessing this is caused by SuperSU not being installed properly. Could you try again after patching with the new debug version? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you're using 8.0.0 of the patcher (or newer), long press the ROM in the switcher :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK, I'll try this afternoon.

Thanks! ;)
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Wiped my multislot1, reflashed just to try the new debug patching SuperSU

Working just like it should

Big Thanks!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You could only repatch the kernel, it have normally to do it.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Can't understand what are you referring to!

Everything is working fine here

I was just testing the new apk

Patching SuperSU before was not working for me

Now it works fine
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I only said you aren't forced to do all wipes, you could only repatch the kernel with debug app, normally it should also work.

That's all!

---------- Post added at 10:23 AM ---------- Previous post was at 10:21 AM ----------

You could, in more, repatch supersu in order to have again the functionnal root.
[Galaxy S 4 i9505 Original Android Development] monkteo:
I try to patch the 27 version Lollipop rom by AntaresOne with last debug but I could not pass by (80% of rom) where patch the boot.img . I try the previous debug and everything was OK.

THX
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Tried with dual boot... it's not flashing properly. .. also the latest debug version is failing around 75% with cm12.

Earlier debug version patched cm12 successfully. .. but gapps and super su are not patched correctly (not installing in dual) though it's say successful
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Hi

ON CM12 (MultiSlot2)

:

Impossible to use the sharing of apps, it doesn't want to update the ramdisk. Weirdly, it seems me that I could before!

Otherwise, impossible to patch Alucard kernel with the debug version

supersu can be patched.

On this one, the binaries is nevertheless updated.

ON SPIRIT (MultiSlot1)

:

Impossible to use the sharing of apps, it doesn't want to update the ramdisk.

Not try to patch Alucard kernel with the debug version

supersu has been patched and installed but doesn't work, it's always impossible to update the binaries on Spirit rom. For the Multi-Slot-2, I had patched supersu with DualBoot Patcher Snapshot 8.0.0 r99 and it has worked fine, maybe, I should do it for this Multi-Slot .

ON ECHOE (Primary)

:

No test to do on this one!

Maybe I have to patch all my kernels with the Debug version! Impossible like I said above.

I edited in red! :)

Send to my GT-I9505
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

There, few little feedback (above), I hope you'll find something, it's a bit the bazaar! ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
I have app sharing working on CM 12. Did not do much - primary was set up to share and duel boot slot (data) had been set up to share - apparently that carried over. Installed debug app version after.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Me too but not with Debug version.
[Galaxy S 4 i9505 Original Android Development] gaww:
I have debug version app on CM12.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Maybe too, I've a doubt but it was before, because now, it doesn't work. How did you patch your rom? Which DualBoot Patcher? It's perhaps this my issue.

---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------

What would be good is that we can use the Debug version to patch as many as shares and other, not the case, because it doesn't patch the kernel or Roms.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
I'm using Gummy in Dual and the latest APK refuses to update the ramdisk for app sharing although according to r99 App sharing is working...
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Guys, I'm on note 3. How can I update ramdisk on my secondary rom(slimkat 4.4.4)? Pls can you help me?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Good question, this is the issue for the moment, I've too.

What app do you use?
[Galaxy S 4 i9505 Original Android Development] gaww:
I used debuf app to patch CM12, but i would not do a GAPPs package - PA micro 5.0.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You have successful to patch CM12 with Debug version?! :confused:

---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------

Oh yeah... me too! :good:

No in fact, I thought! :( It blocks on the boot.img, like with Alucard kernel.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Tried 8 and the debug version. With v8 I can't even access rom settings.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Like me!
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I hope it will be fixed..
[Galaxy S 4 i9505 Original Android Development] gaww:
I cannot use the PC version on 64 bit PC, so only use the debug app. I am not sure if it was the latest one or the previous. Will find out when I try to patch he next CM12 nightly...
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yeah! :p

On 64 Bits PC, it works for me.... luckily! :laugh:

For the version, I know before, on the first CM12(s), at least the app sharing worked, I don't know for the patching, I didn't use it. I should perhaps re-patch all my kernels with tne 8.0.0 r99 snapshot, I wonder if this is with it that worked. :confused:

I hope that [MENTION=4277844]chenxiaolong[/MENTION] could make a PC app and phone app, the both concording. :good:
[Galaxy S 4 i9505 Original Android Development] monkteo:
Try with first debug (with first version I manage to patch CM12 version 27)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Give me the link please!
[Galaxy S 4 i9505 Original Android Development] monkteo:
http://xdaforums.com/showthread.php?p=57002549#post57002549
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Apparently, he has put the latest app instead of the version about you talked me! So I can't have the first app.

Evidence

:
[Galaxy S 4 i9505 Original Android Development] gaww:
Apparently I had been using an earlier app build as the latest will not patch CM12. I am guessing it was version 6 - anyone have a link to it?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You would mean alpha6? You want it?
[Galaxy S 4 i9505 Original Android Development] gaww:
No - it was earlier version - it is still there - going to try it again.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK but this version, it's not an apk!
[Galaxy S 4 i9505 Original Android Development] monkteo:
this is the patch !

PS I hope I don't bother anyone.

THX
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I found an old post to me which explained why I had any issues with DualBoot Patcher! ;) I wonder if I should... or not re-patch at least my kernels of all roms with DualBoot Patcher 8.0.0 r99.

---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------

No! But... Which version is it? First, second or third?
[Galaxy S 4 i9505 Original Android Development] monkteo:
First with what I manage to patch CM12 (I have no idea what version is)
[Galaxy S 4 i9505 Original Android Development] gaww:
I just tried it and no luck. I apparently used version 6 earlier but won't work on latest CM12

Update - used version on OP's post on page 450 and it patched CM12 latest and GAPPs. Now have to see if they flash OK.

ROM booting but GAPPS did not flash successfully. They were an early PA package and the package itself may be bad. Tried them due to smaller size - not much room in my system partition with a TW primary.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK, i can't say you! ;)

It seems me it worked fine with the latest snapshot, however I've a doubt with CM12, I don't believe to have installed it with the latest snapshot. Maybe, Echoe (primary) and Spirit (Multi-Slot-1) were installed with the latest snapshot, and CM12 was with the alpha6, and like that, it worked fine on CM12, I had the apps sharing which worked on CM12.... and also on Echoe and Spirit. I should test it to see.

---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------

For this to work properly, I think we need to have all Roms patched with the same PC or phone apps, and the phone app corresponding to PC app.
[Galaxy S 4 i9505 Original Android Development] lukas77:
[MENTION=4277844]chenxiaolong[/MENTION] Is it possible in near future to patch new CM12 ROMs with block update files eg system.new.dat and system.patch.dat?

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] mudmaster:
Thank You.

Is there a version for 64bit windows?:confused:
[Galaxy S 4 i9505 Original Android Development] lukas77:
It's running ok on my 64bit Windows 8.1 all I had to do is download 2 DLL files for 32bit Windows.

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] bv90andy:
Patching gapps didnt work?

I patched pa_gapps-modular-mini-4.4.4-20141121-signed and it appeared to work, it gave me a "pa_gapps-modular-mini-4.4.4-20141121-signed_dual" which i flashed after the rom, however it didnt say "not flashing as primary!" and the second rom doesnt have gapps.

ill try another package

edit: it's becoming clear now that it installed the package in my primary, chrome went missing and other apps think they've been opened for the first time.

And not even the full modular package works... Damn.

Anyone know of up to date gapps that work on AOSP that still work with the patch? (to be clear, the patcher did recognize the zip files correctly, it's just not doing its job.)

edit edit: the cyanogen apps worked.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Okay, flashing all my files with Windows alpha 5

Works best for me

Never failed patching any rom or Gapps
[Galaxy S 4 i9505 Original Android Development] bv90andy:
Interesting. I wonder what broke the app. Personally I like using latest versions, and stable at that. For now, the gyanogen gapps worked, so I'm set. Thanks for the input though
[Galaxy S 4 i9505 Original Android Development] gaww:
I tried that also. Then it indicated a 0xc000007b error after trying both 32 bit and 64 bit dll files. Did you also put yours in the folder to run it?

Also, if you can, could you upload and post the ones you used?
[Galaxy S 4 i9505 Original Android Development] mudmaster:
Managed to get it working. But I cannot find the link to Dual Boot Switcher download location anywhere. The screencaps on page 1 show this switcher is required to set the Kernel of first ROM as primary and then deploy the second one.

Thanks in Advance
[Galaxy S 4 i9505 Original Android Development] lukas77:
I also have those files in DualBoot folder.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For the line in red, I confirm, it works!

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

I don't know, not still tried, my battery is empty, I can't play with it! :p

If anyone want to test to confirm that, I invite him to do so
[Galaxy S 4 i9505 Original Android Development] gaww:
I deleted the ones I had and inserted yours and now working - thanks. I don't know what was wrong with mine - got them from Microsoft.

---------- Post added at 01:49 AM ---------- Previous post was at 01:41 AM ----------

I am now using version 8.0-99 for Primary and Multi3. Used Debug app to patch CM12 (now I can also patch with PC...) and switch back and forth between them. When on CM12 - have to manage with debug app - otherwise use snapshot.

App sharing works pretty good, but when I flashed GAPPs for 5.0 - its play store blew up my primary play store. .
[Galaxy S 4 i9505 Original Android Development] mudmaster:
Hi

Can anyone guide to the download link for the Dual Boot Switcher app that is required to set the Kernel of first ROM as default?

The download link on page 1 of this post has only the download patcher and the dual boot utilities link.

Thanks
[Galaxy S 4 i9505 Original Android Development] gaww:
It is part of the patcher app apk itself.
[Galaxy S 4 i9505 Original Android Development] mudmaster:
............... and I can't find the patcher App APK as well.

The files in the link are zips. I have looked inside the zips and they do not have any APK file inside. While the utilities file is flashable in TWRP the Dual Boot Patcher file is windows exe based file.

Is there a link I have missed?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Maybe another issue, CM12 problem, I don't know.