yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] peppe130:
[MENTION=4277844]chenxiaolong[/MENTION] Are you still alive?? :D There are news?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
I'd guess he is unless his ghost is pushing commits, snapshot version is up to 8.0.0 r99 and last changes on 17 Aug ;)
[Galaxy S 4 i9505 Original Android Development] v00d007:
What's the problem when updating a kernel of the secondary rom? I patched the latest alucard kernel, flashed it to update my 2nd rom (cm11-20140729), but got stuck in bootloop afterwards... Have I forgotten to do something important?
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm with 2.0.2... But I really doubt this would be the problem...
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
try patching 2 and make sure you download superSU app from play after flashing if it's not there and update primary, there are issues for 2.0.2 seriously, and anyway, there is nothing useful in there for us, it's all for L now ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
If you are app sharing, there is some back and forth issues - mostly with paid apps (root explorer, XDA Premium, etc.) and in all cases, SuperSU will not share and needs to be separately installed? I tried using playstore, but it usually will not update the binary.

I have flashed version 2.01 without issues on duel boot and multi ROMs.

---------- Post added at 02:44 PM ---------- Previous post was at 02:13 PM ----------

When you select a ROM to patch, it will open a menu. Go down to Preset, and see if the ROM (same for kernels) you are patching is shown on the list - select it if its there, then tap to start patching.

If it is not there, go down to Ramdisk. it is set to ASOP as defualt, so if different, select yours from list. The start the patching.

For GAPPs, look in Preset. If you don't find it, just try patching as-is.

I am pretty sure this will work for you.
[Galaxy S 4 i9505 Original Android Development] Thirsk:
Can anyone get the latest snapshot apks working? All the latest ones keep force closing on opening. Stable 8.0 apk works fine though.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
same here, 8.0 r90 working fine though
[Galaxy S 4 i9505 Original Android Development] Thirsk:
So it turns out that the latest snapshot apks just don't like my Omega TW 4.2.2 rom.. When running it on 4.3 or higher, all latest apks work fine (didn't realise there was a firmware requirement?).
[Galaxy S 4 i9505 Original Android Development] gaww:
I just updated to check - had been on #96, which worked OK. So does #99, but you have to make sure it gets superuser (using SuperSU), or it will not run.

Update - just saw you latter post. I have not had 4.2.2 up since early this year, but surprised that is giving you issues, as other posters are still using it.

In order to use app sharing, and new features like Free Space, you will need to use the latest. I would check to see if you are having a superuser issue.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Really, did I miss something massive? Or did you mean apk sharing?
[Galaxy S 4 i9505 Original Android Development] gaww:
Wishful thinking...
[Galaxy S 4 i9505 Original Android Development] v00d007:
I solved this. I first patched the kernel zip with v8.00 r40 which did something wrong but didn't post an error. v8.00 r99 sais it's unsupported but after selecting the right profile aosp/alucard the patching succeeded and so did the flashing.

Btw: alucard is the best kernel I've tested so far in battery life performance when selecting the alucard governor. Also the fastest in bootup time (30s).
[Galaxy S 4 i9505 Original Android Development] Technical:
Reporting the situation:

1. On dualboot, any AOSP ROM I'm testing use its internal su (Omni, Slim, Carbon, Nameless), not any patched+flashed SuperSu (2.0 or 2.0.2).

2. On multiboot, Slim and Omni lost root. Flashing patched SuperSu (2.0 or 2.0.2) gives nothing. No root.

3. On multiboot, Nameless keep root, but does not mount sdcard1, what is a no-no for me.

So, something is weird.

Each time I flash, I wipe all with DualBootUtilities.zip.

Is there anything more radical to "restart" the situation?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, I'm still alive :laugh: I'm working on something big that isn't quite complete, so I can't push the code to gihub (so no snapshots will be built) ;)
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
what do you do exactly after flash and boot? What happens when you open up superSU app?
[Galaxy S 4 i9505 Original Android Development] gaww:
Since you wipe, do any of the ROMs that lost root have it set off as default in development options like Saberslim does? I had been dirty flashing it, but installed it clean, forgot about that, and lost root. Changed settings and it was back.
[Galaxy S 4 i9505 Original Android Development] peppe130:
I'm curious :)

Last week I found the way to install Custom ROMs via Mobile Odin without tripping the Knox. I wrote the guide in S4 General section. It's still in testing but for me and for my testers works perfectly. In next days I will try to flash a patched custom rom, obviously TouchWiz ;)

A question.. The patcher works also with stock kernel?
[Galaxy S 4 i9505 Original Android Development] Technical:
I flashed SuperSu (.zip) after ROM. The app does not appear in some ROMs.

I'll try to download via Google Play and install, but, sometimes, it fails to update the binary.

---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------

Thanks but not following you... I mean, I'm not understanding. The option in the development section is for ADB root and not for the device root. Am I wrong? Can I block root just with that option? Anyway, my option is always app and adb root there...
[Galaxy S 4 i9505 Original Android Development] gaww:
The patcher handles the stock kernel in the ROM - that is why the Ramdisk is set, either by the custom settings or manually if Custom setting is not used.

Question - are the ROMs flashed with Mobile Odin or are they ODIN .tar files ?
[Galaxy S 4 i9505 Original Android Development] Bejda:
Slim rom (and it's the only one i know) has root access disabled by default on first install or after wipe data.

Gaww just thought it could have something to do with your issue.

Btw Nameless rom already use SuperSu maybe SuperSu app isn't visible on app drawer but is available through rom's settings,no need to install it again unless it's a little outdated version that you would prefer to update (2.01 atm while 2.02 exists for instance).
[Galaxy S 4 i9505 Original Android Development] peppe130:
Mobile Odin ;)
[Galaxy S 4 i9505 Original Android Development] gaww:
Sorry - was not clear. I meant file type - zip, .tar, or other ?
[Galaxy S 4 i9505 Original Android Development] peppe130:
Zip file, a modded zip file :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
Thanks for the advice, I managed to patch the ROM, but it goes into Boot-Loop after the install.

Can you give me some more advice? (During the install, it said something about "Binary Update")
[Galaxy S 4 i9505 Original Android Development] gaww:
Which ROM ?
[Galaxy S 4 i9505 Original Android Development] monkteo:
this one (http://xdaforums.com/showthread.php?t=2557353)

and another GE from a friend who made a custom rom GE base, in bout case after the patch and install I get a boot loop.

THX
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
You need to chose custom settings, for Dandvh I used Google experience/dandroid - works fine
[Galaxy S 4 i9505 Original Android Development] Technical:
Even using DualBootUtilities some settings (app shared) seems to be "remembered".

I wipe all of secondary and multi-slot1 but when I install a new ROM, three of four app that I shared some weeks ago got installed in the first boot.

We should be able to start from scratch (or clean these residual settings), don't you think?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It seems me to have seen an identical issue after have uninstalled an app and rebooted.
[Galaxy S 4 i9505 Original Android Development] gaww:
Is your fiend's ROM the one you patched as secondary? If so, I would suggest using it as primary and the Danvdh ROM as secondary. It is supported and should be flashable with no issues.

---------- Post added at 02:32 PM ---------- Previous post was at 02:25 PM ----------

Are you using global sharing or individual app sharing?

On first boot, nothing should happen until you install the patcher apk, select sharing options, and reboot. If you don't wipe secondary and multiboot data before booting, then these settings and many apps will come forward.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Sorry for misunderstanding but my seating is;

primary - SHOstock-i v8.0 (TW)

secondary - C-Rom v7.1 (AOSP 4.4.4)

and I want to flash on multislot1 my friend GE rom or Danvdh GE rom (right now I have on multislot1 SOKP v1.0)

THX
[Galaxy S 4 i9505 Original Android Development] Technical:
I used, in the past, individual app sharing and that's what is reviving I think.

Now I use global sharing, and the app are there BEFORE I set global sharing just after the first boot.

No, some (few) app are there just after the first boot. I've tested a lot of times. The patcher apk is there among them (others are Apex Launcher, Titanium Backup, Timely, and some other).

It shouldn't be that way, should it? I mean, the data is not the installed app. Data will be there, orphan, not linked to any app.

Besides this, I'm sure I wiped all (including data) before flashing and booting.

Some info seems to be kept at primary ROM. :o
[Galaxy S 4 i9505 Original Android Development] gaww:
That may be.

I remember I had to install the patcher apk, set up the app sharing, and then reboot to get my apps loaded. But I am not 100% sure when I first set up SaberSlimK in a different Multi slot if anything came over at first boot.
[Galaxy S 4 i9505 Original Android Development] eclpsues:
Im sorry for asking this but where is the link for the apk file for the phone to set the primary and secondary room kernel?
[Galaxy S 4 i9505 Original Android Development] Technical:
https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] eclpsues:
thanks!
[Galaxy S 4 i9505 Original Android Development] gaww:
TWRP backups

This may have been covered before, but cannot find it.

When making a "normal" backup with TWRP, I generally only include boot, system, and data. However, will that capture the MultiROMs, or must cache be backed up also?

When I recently opened backup, it showed the used sizes in the partitions, and cache had about 2gb - which is what the size function in the patcher app shows also.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hey all, I wonder if any can help me with this?

I just thought I'd like to use vpa and installed the apk and opened it up, tried to install the driver and reboot but it still days I need to install the driver so I'm guessing it's getting installed in primary?

Tried cf lumen also and found the same thing, I always used to use cf lumen and I think I managed to get it working on multi boot quite some time ago but then it stored working and I must interest, but now I'm interested again.

Do any of you have any experience, knowledge or solutions for this?
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
I've had viper installed on primary for quite some time. It's one of the things that I always install after a new rom flash. Pre-8.0 versions of the patcher would give me problems installing viper on dual and multi slots, but that's all been cleared up since 8.0. The driver would install, but after a reboot I'd have to do it all over again. It never stuck.

Trying installing on primary first, then dual or multi and use any patcher version 8.0 or better.
[Galaxy S 4 i9505 Original Android Development] Bejda:
I did same rom switch shortcuts tasker apps i once made for primary and secondary rom but updated now for multislot 1,2 and 3.

All links here:

Primary: https://app.box.com/s/auncb9kj6dy58gdnt021

Secondary: https://app.box.com/s/hzkm7bplkvzoikc0ksdl

Multislot 1: https://app.box.com/s/pemvfsc1eab7kn6eigwn

Multislot 2: https://app.box.com/s/bqxqg3hip48hgwjrvf80

Multislot 3: https://app.box.com/s/pbt4r7ayqnzkpfodihon

Note: They aren't apps with interface like i once did for the [MENTION=5650065]peppe130[/MENTION] edition ;)

It's just shortcuts, mean if you open the app once root access granted it will immediately and without confirmation reboot to desired rom if corresponding boot.img is found under /sdcard/MultiKernels.

It's more to be used as..shortcut then mainly along with an app like SideControl,SwypePad,etc..

Only "interface" is a pop-up saying "no ****.img found" if corresponding boot.img isn't found, it won't reboot and you just tap the pop-up for it disappear.

Behaves a little bad with superuser,under some circumstances it won't find the boot.img under sdcard although it is there while it always works with SuperSu.

To put it shortly: SuperSu strongly recommended.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
OK, maybe I'm being dumb, got viper to install driver in primary but still no joy in multi 1, cf lumen didn't install the first time and the second it gave boot loop at Sammy logo :(

Are the drivers available as standalone zips that we can patch?

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

Awesome work Bejda, thank you :D
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
https://www.dropbox.com/s/ppwk16q5bxvpzgd/libv4a_fx_ics.so?dl=0

Drop that in /system/lib/soundfx and change permissions then reboot.

I never did figure out exactly why it wasn't working before. I installed a newer version of chen's patcher and it worked. Oh, and make sure you're using viper version 2.3.3.0. I believe I was using an outdated version before as well. That might be the reason why it isn't installing. I just remembered that I updated viper as well.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Errm, I don't seem to have a 'soundfx' in /system/lib ?

Do I don't just drop that time in with all the other libs then?
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
Well, that's odd. I guess you could try. It couldn't hurt anything. If it doesn't work you can delete it.

What rom are you trying to install on?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
SlimSaberKat

Edit : I was being an idiot and looking with my eyes closed apparently lol. Just found the sound fx folder and dropped the file you have in there, thank you - going to reboot and see what happens now :)

Oop, need to reset permissions, I guess to the same as the other files in that folder?

Edit: nope, rest permissions, go to viper, agree to install driver, reboot, open viper, still getting driver needs to be installed message?

Edit: updated something in settings fx?? And now managed to install driver but now realising this massive ot (sorry everyone) will take this to viper forum now, thanks for your help hemp :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since I haven't been on XDA for a while, I wanted to give a quick progress update :)

Version 9.0.0 is coming along nicely so far. The patcher's core is undergoing significant changes, so this release is taking quite a bit longer. Here are some improvements and new features to look forward to:

The actual patching (first four steps before the progress bar moves) has been significantly optimized. The time has been cut from 3~15 seconds (for large ROMs, of course) down to 50~500 milliseconds.

The zip compression code is getting ported to use libarchive, which could potentially cut the entire patching time by 50%

The latest ROM support files will be downloaded by the patcher so I can add (or fix) support for ROMs without having to wait for a new version of the patcher :)

Some more stuff...
[Galaxy S 4 i9505 Original Android Development] npzinho:
EDIIIIIIIT.

I do not know if it would work normal because I "would select" the kernel as "currenty" 1st or 2nd.

But I changed manually in the folder "/ system / dual-kernel" and then just select the ROM and not the kernel, as it did before and it worked normally.
[Galaxy S 4 i9505 Original Android Development] zhuchella:
Can U add the support for:

1. http://xdaforums.com/showthread.php?t=2306650

2. http://xdaforums.com/showthread.php?t=2303239

3. http://xdaforums.com/showthread.php?t=2281738

Thank U
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Do you plan on using TW as your primary ROM? I'd recommend it because there are tons of mods and other zips for TW and it isn't really practical to patch each and every one of them.

Anyway, I've added support for Infamous in version 1.4.1 of the patcher :) I haven't tested it because my TW ROM isn't the secondary one, so I'm not sure if it works yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) MIUI will have to wait until I get home. My school blocks the Hotfile website. I'll take a look at Foxhound first.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Which Paranoid Android ROM are you looking at? This one? http://xdaforums.com/showthread.php?t=2329550

EDIT: Now supported in version 1.4.2 of the patcher:
[Galaxy S 4 i9505 Original Android Development] blood_talon:
Hey, thanks for the quick reply and support!

I am not sure I caught you. Do you recommend using TW custom ROM as secondary one? If yes, I dont mind switching to a GE rom as primary then install a TW one as secondary. Thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem :D

Sorry, I should have been more clear. I recommend using TW as the primary. Lots of the custom kernels and mods for TouchWiz are flashed via recovery and it would be a pain to patch them all.

With TW as the primary ROM, you can flash anything just like you did before :)
[Galaxy S 4 i9505 Original Android Development] :
Im on touchwiz mh1 stock kernel and somewhat debloated I followed the instructions and used the stock 4.3 rom you posted the link to, I used the patcher it was successful than I set the 1st kernel with the app on my touchwiz rom, rebooted, flashed the patched 4.3 rom and after it was done my s4 stayed on the first samsung bootscreen, I tried switching roms with the app but when I reboot it still goes to the touchwiz rom
[Galaxy S 4 i9505 Original Android Development] Ausboy 2011:
So can this work with adam kernel?? Great job by the way :D
[Galaxy S 4 i9505 Original Android Development] zhuchella:
Thank U. Do U tell when will do ?
[Galaxy S 4 i9505 Original Android Development] blood_talon:
OK, that's clearer now. Btw, you did mention to have enough space under /system. How much roughly do I need with a TW rom as primary in order to install another one?

Also, step 4 is:

Patch the ROM (see the "How to use the patcher" section). In that section you explain how to patch the kernel. Do I have to patch also the secondary ROM? Then flash both the patched kernel and ROM?

EDIT: OK, I just tried to patch a ROM and got an error saying unrecognized kernel, so I guess the patcher is only for the kernels.

EDIT2: I gave it a shot.

-I am currently using XTREMXPERIA rom (TW) with Infamous kernel 2.0. I installed the Dual Boot Switcher app and set the primary kernel. No issue.

-I patched the Infamous kernel and got a new zip.

-In recovery, I installed that patched kernel then installed secondary GE rom (Unwiz v2).

-When booting up, it boots on secondary ROM. Then I get many FCs..

I am now restoring.

Which steps did I do wrong? Also, how to select the ROM at startup?

Thx.
[Galaxy S 4 i9505 Original Android Development] kendragon:
how can I patch rom?
[Galaxy S 4 i9505 Original Android Development] emu1982:
Would it be possible to add ausdim kernel? Would really like to give this ago, great work by the way :)

http://xdaforums.com/showthread.php?t=2342298

Thanks
[Galaxy S 4 i9505 Original Android Development] kendragon:
how many mb of free space we need to install second rom?
[Galaxy S 4 i9505 Original Android Development] XeoNoX:
thanks you sir.
[Galaxy S 4 i9505 Original Android Development] mgbotoe:
for clarification, this work on tmobile yes? sorry...just the last one that came out tmobile wasn't supported...
[Galaxy S 4 i9505 Original Android Development] XeoNoX:
yes it will, thats what "on all Galaxy S4 variants!" means. Make sure you read the instructions carefully. (most of all make sure you have the right kernel) good luck.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I have MIUI booted up now :) Unfortunately, it's doing something weird with the internal storage, so I will have to fix that before I release it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I will add support for Audism ASAP :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since all ROMs have different sizes, the best way to find out how much space the second one will take is to extract the zip file and see what the size of the files are.

Also, the ROM does, in fact, need to be patched. The project started off as a kernel patcher, so some of the OP might still say kernel. I'll go fix that right now :)

Regarding the FCs, the two main causes would be running out of space on /system (needed files cannot be installed properly) or an incompatible kernel. From what you said, I'm assuming you're trying to use the Infamous kernel with a Google Edition ROM? I may be wrong, but I don't remember Infamous being compatible with Google Edition ROMs. If you only want to use the kernel with your TouchWiz ROM, then the kernel does not need to be patched.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I had to flash several times in order for it to boot (even as a primary ROM). An old version of MIUI used to also do that, but I never found out why that happened.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ktoonsez's updater-script is actually pretty well-written and it sets the needed permissions automatically :good:

If you've used a newer version of CWM, you'll see that the fix permissions option is no longer available. Every ROM is different and there isn't really one set of permissions that will work for all of them. This is even more true if an ROM has SELinux in enforcing mode. Fixing permissions would most like cause the ROM to need to be reflashed.
[Galaxy S 4 i9505 Original Android Development] schizovivek:
It's there mate ..

As for the gapps .. Is this the one from your ROM thread? Coz from the date it looks like that .. If it is then this doesn't work on JellyBeer .. Got a lot of FCs .. (i think coz It's 4.3)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah that's the one from my ROM thread.

I'm not sure what to say about the issue. The file is there, but the recovery log says that it can't find it:

about to run program [/tmp/dualboot.sh] with 4 args
run_program: execv failed: No such file or directory
[Galaxy S 4 i9505 Original Android Development] Bejda:
I had this error too when i tried to manually patch IceColdJelly rom (the one you just add with 1.17 patcher version ;) ).

Probably nothing related but its boot.img wasn't supported so i pushed a patched KT kernel boot.img + modules into the zip but then had this same error no matter what i tried.

Actually the only thing that got installed in the process was the boot.img, after reboot my secondary rom was still the same but now with KT kernel (without its modules then,so no wifi for instance).
[Galaxy S 4 i9505 Original Android Development] schizovivek:
No issues mate ... Thanks for your help .. It might be recovery related?

Trying another combination now ... What is a lil shocking is that no one else here has tried flashing gapps 4.2.2???

[MENTION=3648432]Bejda[/MENTION] ... What recovery you using?