yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
No worries I finally got everything running :) here is what I did (just a small list because I spent the last 6 hours getting it to work and it was worth it) I have ATT Beanstalk as my primary and then I backed up my kernel. Went into recovery and flashed the Fox rom(duelboot one of course) and then flashed 18.1GE kernel(duelboot as well) and then flashed Loki doki and then rebooted and boom it worked :) seriously couldn't be happier. :) thank-you for all your hardwork :) will be donating as soon as I can.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :D Okay, I admit it, I hate pushing the power button too...

CM has the reboot menu built in. Just go to developer options and check the "Advanced Reboot" checkbox ;)
[Galaxy S 4 i9505 Original Android Development] buggerritt:
I've found only 3 mentions of MF3 listed in this thread and the question I have didn't seem to be asked in them. I have an AT&T Galaxy S4 that just arrived with MF3 firmware (locked bootloader). Is this method compatible?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Check out version 1.0.1 of the Dual Boot Switcher app :D
[Galaxy S 4 i9505 Original Android Development] omnifarious:
Just a heads up, FoxHound 2.0 has been working for me with patched and updated ausdim kernel.
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Exact setup with me as well :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Check out version 1.17.1 :D
[Galaxy S 4 i9505 Original Android Development] schizovivek:
uh ohhhh

[MENTION=4277844]chenxiaolong[/MENTION] .. something went terribly wrong .. so here's the story ..

I had Rooted Stock MEA as my Primary ..

As you know I was trying to find a secondary whose GApps would flash correctly ..

After SlimBeam and JellyBeer I came across your ROM (noobdev) ..

When I tried to patch it through the patcher it said that the ROM already supports Dual Boot.

So then I went ahead and flashed it ..

The first message I got was "Dual Boot disabled" :(

When I saw that I was expecting the worst .. But I didnt wanna stop the flash in between .. Once the flash completed I rebooted .. (without Switching to Secondary)

Sadly my primary had been overwritten by the new ROM ..

I had an earlier Nandroid so i was pretty chill about this ..

Restored the Nandroid of everything but data .. ROM boots and I cannot see anything except the statusbar .. I cannot do anything, cannot expand the notifications nothing .. Only thing I can do is get the Power Off menu .. which has only Power Off and Restart :P

I have tried flashing the kernel too and nothing happened .. Gonna try flashing a few other kernels and get back to you on the progress .. (I know if I flash another ROM things would get sorted but I dont wanna do that .. at least as of now )

Need your help in sorting this out :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, that's where the issue is. My ROM has both of the single-boot and dual-boot built in. You need to flash the DualBootEnable.zip first, so it knows that you want it to be secondary.

I wish I made a nandroid before I made a mistake on my phone last time. I lost all my data (pictures and everything) :(

But since you do have a backup, it should be pretty easy to get your phone back up and running again. Here's what I suggest:

1. Wipe /system, /cache, and dalvik-cache using the recovery

2. Restore your backup

If that doesn't work, get to the Power Off menu and hold the "Power Off" option. You will see this:

Click OK to boot into safe mode. From safe mode, you should be able to copy your internal SD files to the computer so you can restore your /data backup and copy the files back.

Hope this works :fingers-crossed: Please keep me updated on the issue.
[Galaxy S 4 i9505 Original Android Development] schizovivek:
neither worked :( .. dont get any safe mode option... (i can get sounds playing .. means something is happenning .. but its like the OS is not able to produce the display for it .. its just black with status bar showing :eek: )

so I restored the data directly (very old nandroid had data) .. everything is back now .. just need to get things sorted now ..

do the dual boot related partitions still exists? If so how do i remove it and reset everything (wrt dual boot at least)..

also how to check on whether dual boot is still there or not? the dual boot utilities just shows total system space .. not the split..

thanks for your help .. need to clean up and sort out everything before doing a dual boot again :p :silly:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope, when you restore from backup, dual boot is gone (unless you did a backup when you had dual boot). :p
[Galaxy S 4 i9505 Original Android Development] RK:
Yes the error I posted happens after fixing binariesdir. The ramdisk patcher works if I drag IMG file into it. I get that error only when I try ramdisk replacement on a zip file.
[Galaxy S 4 i9505 Original Android Development] schizovivek:
I'm trying to get my phone back to the state it was in yesterday ... Long time for that .. Will try the dual boot the minute everything is back to normal .. You can expect me to bug you again then :D

One request .. Not sure if it's possible

Can the kernel/boot be patched in a way that the dual boot comes as an option while booting? (Rather than having to flash the dual boot zip)
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Alright so another question, when you say this do you mean IF we backup while we are dual booted, then we can return to the dual boot setup that we backed up from before whenever we want such as a normal ROM would?
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Recovery, without patching anything.. Just flash it
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yes, like that!
[Galaxy S 4 i9505 Original Android Development] Annunneo:
OK thanks guys.
[Galaxy S 4 i9505 Original Android Development] mitky82:
Is anyone try to dualboot latest miui 4.11.3? http://xdaforums.com/showpost.php?p=56554383&postcount=391

I patched file, program say is "ok" patched. Flash them with Goldfinger as primary and all things gone wrong :D

They flash file over primary rom :( i have nandroid and i test again. I think maybe i mistake somethnig, but when i patch file again, flash and bam... they flashed over primary again. I use files from first post v8. And i don't use program for first time :)

Now i will try with some v7 program, who i see i posts here
[Galaxy S 4 i9505 Original Android Development] monkteo:
I have on multislot1 an MIUI AOSP version 4.10.18 and work perfect, I thing your version it's an TW version and could by a problem (happens for my with an TW rom for multislot1)
[Galaxy S 4 i9505 Original Android Development] gaww:
update of ramdisk FC's Patcher

I had updated primary and on booting up opened 8.0 #99 snapshop that I had been using successfully for several weeks. On going to ROM settings, it indicated that ramdisck needed to be updated. It did not show app sharing as active even though I have been using it for weeks.

On letting it update the ramdisk, it would do everything but open ROM options - causing an FC when tried.

I have not found anything on this besides the problems with the Apha, but this had worked OK until today, but now am notable to app share at all.

Update - it seems to want to have both SuperSU amd Superuser installed - would not work with only SuperSU
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Is there a way to backup roms individually?
[Galaxy S 4 i9505 Original Android Development] gaww:
http://xdaforums.com/showthread.php?t=2491299

The Op is a bit dated - much of the current procedures are in latter pages. Not that many - study them carefully.
[Galaxy S 4 i9505 Original Android Development] vinipuh7:
Hi,

As the above screen says, I can not delete the folder with the file inside, even if I uninstalled the application.

Any help is appreciated.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Do you still have dualboot on your phone? Or just one?

If no, you can remove it.

If yes, in the case or you can't remove it, you could remove via aroma file manager in the recovery. You've not aroma file manager and you don't really know how install it, then you can use my mod (link in my signature). With this mod, you can use aroma file manager included inside, or install it for your recovery... your recovery should be this of PhilZ or TWRP.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
But it still works perfect - I use it a lot :D
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Same! :good:
[Galaxy S 4 i9505 Original Android Development] gaww:
Per the thread over there - it did not restore for me last time even with using aroma.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I tried to patch imperium rom v13.0, but I have this error. Any fix?
[MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] gaww:
I have patched and used this on Imperium v13 with no issues - both as patched primary and as Multiboot currently.

Did you patch with PC or the app? Also, what version did you use ?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I don't that's an issue with the rom but rather your PC environment, maybe your system or DualBootPatcher folder, a missed file or other.

What is your PC system?
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I use the pc version (you can clearly see it in the attachment)

DualBootPatcher-8.0.0-release

---------- Post added at 08:24 PM ---------- Previous post was at 08:21 PM ----------

It can't miss a file, it also does this on my phone with the dual boot app.

I have windows 8.1 PRO x64

I used this dowload (as seen on the first post of the imperium thread)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I also have this Windows, so not the issue.

---------- Post added at 11:50 PM ---------- Previous post was at 10:56 PM ----------

@FPSUsername

I downloaded your link to see, this zip should can to be patched, it's well for the S4. I don't understand why it can't.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Do you have a patched version of imperium v13 (i9505)?

If yes,

I don't know how your upload speed is, but could you upload it? Unless your upload speed sucks, the rom is 1.8gb :0
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It's true that I downloaded without to have thought to patch it... stupid, no? I gonna try it now...
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Look that!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
And that!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Take this zip (below), open it and open your, you will see that 3 folders are missing in mine. So drag and drop those of your in my patched zip. Tada!!! You will have quickly a patched zip.
[Galaxy S 4 i9505 Original Android Development] gaww:
I would suggest you install the latest patcher snapshot (link below). I have patched 3 versions of Imperium with it. You may also have had a bad ROM download.

https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Me too, I have their even given my results above. I just removed 3 folders inside to be more easy to download. :silly:
[Galaxy S 4 i9505 Original Android Development] Jared20098:
Hi guys, can anyone patch that new CyanogenMod 12 from AntaresOne and the GApps too? Thanks! Also where can I find the download for the newest version of the mobile app?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
This the latest version... there!

---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------

You can try this:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Did you try with DualBoot Patcher Snapshot 8.0.0 r99? I tried, the patcher works, however I didn't try to install it.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
I patched it no problem with 7.0.0r151 however it failed to install.

I have however managed to run multi boot alongside my patched ROMs and I have booted cm12 from ext SD. I'm having problems fishing gapps though!

Good to see L running on my s4 though :D
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What recovery? I believed to read that there was a problem with TWRP
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
TWRP - that comes with multiboot is working fine, confirm, I have cm12 booting on ext sd with gapps, whilst still running patched roms multibooting on internal sd with app sharing courtesy of Chen :D

so - we can have our cake and eat it :silly:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
OK!
[Galaxy S 4 i9505 Original Android Development] Sulaimanshariff:
I know this is goin to be too basic but im kinda confused im running pheonix v10 and i wanna flash cm12 so i thought I'd dual boot it and then i downloaded the dual patcher apk and dual noot utilities zip so after that opened dual boot patcher chose rom as pheonix v10,set kernel alucard and then patched the cm 12 zip file found it in internal storage as well cm12ltexxdual.zip and then the funniest part i dunno wt to do next itried flashing the patched zip via recovery gives error both twrp and philz help appreciated [emoji6]
[Galaxy S 4 i9505 Original Android Development] franzyroy:
We talk about of that (above), it doesn't work but you could try with MultiROM.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
I have MultiRom booting CM12 on both internal and ext sd (ext is laggy though!!)

Find links in my sig ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
Sounds interesting - especially since Chen said getting duelboot to handle 5.0 was going to be difficult. I was going to install it as primary and reinstall my primary ROM as secondary, but the above sounds interesting - did not know you could have both.

Can Multiboot be set up without blowing up duelboot (or does it have too be re-setup after) ? Also, how do they boot up - ie, does multiboot only show the primary, and after booting it up, then you can choose a duelboot ROM ?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
It's fine - I installed multiboot with 3 patched dual boot ROM's all up and running without affecting them at all, just follow the instructions in the op of multiboot by [MENTION=5464206]AntaresOne[/MENTION] - basically, multiboot sees the patched dual boots as primary and goes no where near them, when you boot you get a menu to continue booting into whichever patched ROM you are on, or boot into either your ext or int multiboot ROM's - I found ext multiboot to lag, int is fine though ;)
[Galaxy S 4 i9505 Original Android Development] monkteo:
So from my understanding in dualboot CM12 (without multiboot) it's not possible ?

I patch the rom (CM12) but not boot (i try multislot2) because i have SHOstock - primary, Dirty Unicorns - secondary and MIUI AOSP multi1.

Any suggestion ?

THX

error 6 ? what to do ?
[Galaxy S 4 i9505 Original Android Development] Sock12345:
Thanks for this :)

Are you also gonna make an apk version of it like you have made for the S4?
[Galaxy S 4 i9505 Original Android Development] lukas77:
I'd like to confirm it work like a charm on Galaxy S5 G900F (International)

I have TW rom as primary and CM12 as secondary.

Thank you kindly sir for this!

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] djmik21:
How did you patch the CM12 rom and gapps? What settings did you chose in the patcher?
[Galaxy S 4 i9505 Original Android Development] lukas77:
Settings to patch Galaxy S5 KLTE CM12

DualBootPatcher-9.0.0Alpha6-win32

ROM

Device: klte (Samsung Galaxy S5)

Preset: Custom

Auto-patcher: StandardPatcher

Has boot image: ticked (autodetect)

Ramdisk: klte/AOSP/AOSP

The rest is default

GApps:

Device: klte (Samsung Galaxy S5)

Preset: Google_Apps/gapps-cyanogenmod

That's it
[Galaxy S 4 i9505 Original Android Development] Annunneo:
Where is the version 9.0.0 alpha?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
However, if you use DualBootPatcher-9.0.0Alpha6-win32, all roms on the phone have to patch with this patcher, and also certainly, an binaries update. You aren't forced to repatch all the roms, but at least theirs kernels.

---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------

DualBootPatcher-9.0.0Alpha6-win32
[Galaxy S 4 i9505 Original Android Development] Annunneo:
Where can I download version 9.0.0?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There!

---------- Post added at 11:10 PM ---------- Previous post was at 10:54 PM ----------

[MENTION=5443170]jamboss[/MENTION]

To use these settings in DualBoot Patcher, you should rename the Cyanogen Mod 12 zip, otherwise the zip will be autopatched without you can make them.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
EDIT: New version attached. It should fix the crashes when used on pre-Lollipop ROMs.

The C++ patcher rewrite is finally complete (!!). Time to work full time on app and data sharing again :)

The APK attached to this post is a debug version of the latest patcher. Please test and let me know if there are any major bugs. If there are only a few minor UI glitches, expect a version with a "Materialized" UI on Thanksgiving! (And no, the final build will not be a 18MB APK :p)

(Please note: This is a

debug

build, so it will spam a huge huge bunch of crap into logcat, so you may want to close the app if you need to create logcats for other apps).

EDIT: 95% of the patcher is translatable now. The translation source files have be pushed to transifex.

Changes:

Ported to use the new libmbp patcher core

Many, many speed improvements. The patcher UI should load much faster and be much more responsive. Patching time (compared to 8.0.0 and below) should be decreased by at least 30 seconds (tested on AOSP ROMs). I've also seen the patching time for huge TouchWiz ROMs decrease by about 2 minutes.

The patcher's "tasks" card has been removed. The new patcher core does everything at the same time, so there's aren't really distinct "tasks" being performed.

The patcher now fully supports armv7 (ARM), armv8 (ARM 64 bit), x86 (Intel), and x86_64 (Intel 64 bit), so the patcher is ready for next-gen devices like the Nexus 9 :)

Added support for the Galaxy S 5 and Galaxy Note 3 (Galaxy Note 4 support coming once I get mine)

Known bugs:

"Update syncdaemon" is listed in the patcher selection spinner and if it's selected, then the partition configuration spinner is empty.

The update ramdisk feature for app sharing is broken.

Individual app sharing may be broken (global should still work)

For unsupported ROMs, the "StandardPatcher" autopatcher is not selected by default (**

make sure to select this when trying patch an unsupported ROM

**)

PS: If anyone has any advice on building Visual Studio projects from Jenkins, please let me know. I'm not too familiar with the VS command line tools.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Can't wait to try patching lollipop with this.

WELCOME back!
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
Welcome back! Hope school is going a bit easier on you.
[Galaxy S 4 i9505 Original Android Development] AskinSavascisi:
even when i flash GApps i dont get it in my 2nd rom ( CM12) .... ive tried to flash with patched zip and normal zip...

i also dont have ROOT on my secondary flashed rom? :D any help?

thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
After some time away, I come back .. I've successful to boot on CM12 like multislot2 with DualBoot Patcher 9.0.0 alpha6! :p
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Settings you used please
[Galaxy S 4 i9505 Original Android Development] franzyroy:
DualBootPatcher-9.0.0Alpha6-win32

ROM

Device: jflte (Samsung Galaxy S4)

Preset: Custom

Auto-patcher: StandardPatcher

Has boot image: ticked (autodetect)

Ramdisk: klte/AOSP/AOSP

The rest is default

GApps:

Device: jflte (Samsung Galaxy S4)

Preset: Google_Apps/gapps-paranoid

Kernel:

Alucard kernel

Preset by default
[Galaxy S 4 i9505 Original Android Development] gaww:
Tried to set it up following the OP. I have the patched TWRP and Multiboot istalled - plus the ROM manager app.

However - am nervous when the installation wanted to install or modify patched kernel to "primary" - which is the duel boots. As the patched kernel it wants to isnstll to primary is not compaatible with my 4.4.4 TW duel boot primary, I am not sure it it will blow up my whole duelboot setup.

Also, the OP said that on initial installation, it would set up partitions with sizes and I did not encounter that in the setup at all.

Would appreciate any further detail on the procedure you followed that did not mess up your existing duel boot. I am trying to setup CM 12 this way, as it is not patchable currently with duel boot snapshot.

Update - kept on redoing various steps, and it finally got so it rebooted into Duelboot primary, and then when opening boot manager and selecting the ROM to boot, it finally booted up.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes, that's not really that hard...

I'm stuck in rooting the cm12 though. When I install the patched supersu beta 2.27 it unfortunatelly installs on the first rom. I patched it like the the cm12 rom/gapps with 9.00 alpha6. I wonder if I couldn't put the su root files somewhere manually from within my 1st rom??
[Galaxy S 4 i9505 Original Android Development] croatia1:
Can anyone say me why I always get

Error executing update-binary in zip

when I try to flash secondary rom? I updated the SU-binary and checked everything at least eight times. Always getting the same error in TWRP. At least I managed to patch the GApps correctly, because it flashes the GApps.

My device:

klte (Galaxy S5 G900F)

Primary Rom: Wanam 4.4.2

Pozdrav

Croatia1
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Why not!
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well thanx for your spam here....
[Galaxy S 4 i9505 Original Android Development] v00d007:
On my TWz NE8 rom the patcher isn't able to patch any file at all. Always crashes.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I've a bug, impossible for the moment to have the root in CM12, I have to make others tests.
[Galaxy S 4 i9505 Original Android Development] gaww:
I tried the apk on CM12 and it closes immediately.

I tried the GUI and get an MSVCP.dll missing error.

Would like to get it working on CM12, as i have it on MUltiboot right now, but would rather run it with app sharing here.

Update - got past the .dll issue, but seem to have a 32 vs 64 bit problem on the PC.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Can you share the rom patch with dualboot on multislot2 ? and gapps ?

I try several time but I can't patch the rom .

THX
[Galaxy S 4 i9505 Original Android Development] MohamedN:
It doesn't patch anything, always crashes.
[Galaxy S 4 i9505 Original Android Development] monkteo:
I thought it happen only to me!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
When I come back at home tonight, I do it! ;)
[Galaxy S 4 i9505 Original Android Development] MohamedN:
No I have tried it on 4.4.2 tw and on ge

Opens fine but crashes whenever I try to patch anything..
[Galaxy S 4 i9505 Original Android Development] franzyroy:
There, the rom:

CM-12-20141123-UNOFFICIAL-jflte_multi-slot-2.zip

CM-12-20141124-UNOFFICIAL-jflte_multi-slot-2.zip

Gapps:

Gapps-LP5.0-20141109-signed_multi-slot-2.zip

Enjoy! :cool:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for letting me know about the crashes! It was just a matter of the patcher being compiled against Android L instead of an earlier API. I've been testing under Android L, so I hadn't noticed any issues. I'll make a new release ASAP :)