yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
Man you got some serious issues... You dont boot into secondary rom then set it's kernel to primary also especially if you just did that in your main rom...

You set it to secondary

And yes anyone can use ktoons kernel or any of the others.. it isn't the problem... You Are by not following clear instructions.

Let me lay this out for you...

Boot your phone to your Main ROM the open dual boot switcher set kernel to PRIMARY. Then patch whatever rom you want and or kernel as dual boot

. Then reboot install your patched rom and or kernel then let it boot once your up and running install dual boot switcher on that rom and choose the kernel as SECONDARY. If you did this correctly you won't have any issues.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Its pointless... He will just again complain that no one is helping him and ignoring him while he clutters up development thread. Instructions are there for a reason. Obviously like I stated he needs to read them and more.
[Galaxy S 4 i9505 Original Android Development] DiDA™:
Had some problems patching the GE ROM by Jamal so I used an older version of the Patcher (v3.2.2) and now it seems to be working fine.
[Galaxy S 4 i9505 Original Android Development] jova33:
Wow! I just updated everything, hadn't used the dual boot since last year, and this stuff just keeps getting better!

I'm on the VZW S4, so I used to have to manually patch EVERYTHING(kinda the reason I hadn't used it since last year), but this time I didn't have to. Everything worked seamlessly.

Keep up the good work!

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] Bejda:
You would not have been happy with a minimal or standard gapps pack then.. :)

The thing is all these apps are usually available on playstore and will be installed under /data (userspace,internal sd) while gapps install them under /system.

Big gapps packs doesn't really help when you want to dual/multiboot and are short of space under your system (for dual-boot) or cache partition (for multislot roms).

Maybe there's some good points having some apps under /system (e.g hangouts push notifications on aosp builds from what i guess i noticed) but usually unless it's modded apps not really + once one of these apps gets a playstore update the apk under system isn't used anymore and can be deleted without issue > the /data/app from market gets used instead.

If you have same apk version under /system/app and data/app the one under system is used.

If you have a more recent version under data it is used prior to the one you have as /system/app (that's where we have the "uninstall updates" choice under settings>apps,it deletes the /data/app for the system one gets used again).

Then unless you:

_Don't have playstore access to some of these apps in your country (and still we can find package installer versions>/data/app).

_Use a modded app (and then may want to skip market updates).

_Want to solve some specifics issues like, if I'm right,hangouts push notifications on our aosp/CM builds or whatever (btw if we check some of goo.im gapps recents changelogs we can see that some versions sometimes reintroduces Gmail,Google+ or others apps but every time with a functional reason).

=Maybe you don't really need to "load" your system with all these apps ("load your system" maybe isn't the good way to say it,i mean many apps under /system or not changes nothing to performances..just a matter of size here).

---------- Post added at 01:08 PM ---------- Previous post was at 01:00 PM ----------

If you prefer to be up to date ;)
[Galaxy S 4 i9505 Original Android Development] Hawlery:
Is it possible to support AOSB project too?

Thanks!
[Galaxy S 4 i9505 Original Android Development] bigpp85:
Bobcat has release a new Rom with Android 4.4 .Can you support the Rom for dual boot please?

Link:

http://xdaforums.com/showthread.php?t=2637584
[Galaxy S 4 i9505 Original Android Development] Bejda:
Try to provide rom's META-INF folder + boot.img to make the support process easier please :)

Edit: [MENTION=4389737]Hawlery[/MENTION],

AOSB was named ProBAM previously, while waiting for its new name to be supported you can rename the zip (replace "aosb" by "probam") and it's ok...actually i totally forgot it was my multislot3 rom lol
[Galaxy S 4 i9505 Original Android Development] bigpp85:
Bobcat kit kat Rom meta inf and boot img files.

https://www.dropbox.com/s/p098nh1fe...v1.0_MD5_87855489E637EE593677668330710FF0.zip
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I still haven't had a chance to test if TouchWiz 4.4 works, but if you want to test anyway, you'll need the latest experimental version for jflte from here: http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html You'll also want to use "patch-ramdisk-loki" since the zip has a boot.lok file.

If you prefer to use the GUI instead, choose these options:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It will be supported in the next version :)

If you want to try it now, an experimental version of the patcher will show up in here shortly: http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html

Otherwise, you can rename the file to "probam-..." instead of "aosb...".
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It will be supported in the next release :) If you want to try it now, an experimental version of the patcher will show up here in a few minutes: http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] RK:
I tried tw 4.4.2 ROM. It booted up but no cell reception and baseband unknown I m gonna try a different recovery and report back
[Galaxy S 4 i9505 Original Android Development] gaww:
Which tw 4.4.3 ROM did you try? I patched Echoe 14, but it is too big - will not boot up.
[Galaxy S 4 i9505 Original Android Development] jova33:
Where is this GUI patcher? This image gave me a semi, and I would've reported it on Facebook.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's PatchFileWindowsGUI.exe on Windows and PatchFileLinuxGUI on Linux (no OS X version yet). It's in the same zip as the patcher starting from version 4.0.0 :)
[Galaxy S 4 i9505 Original Android Development] jova33:
I'd say where's the donate button, but I've already donated. About to do so again. Thanks for the contributions to the community.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] DVDeus:
Hi.

I just wanted to be sure before proceed; I have patched my SlimBean 4.3 Final build. I guess the addon (gapps) does not need to be patched, right? I installed the APK, set the primary kernel. Now I am wondering, do I use this stock Samsung recovery? I have searched the thread to confirm it, but I rather ask here.

One more thing; this method does not void know warranty, right? :)

Thanks!
[Galaxy S 4 i9505 Original Android Development] DVDeus:
Anyone?:) I just need to know if I can use the stock recovery. Otherwise I have to flash CWM or TWRP, which will trip the knox flag, right?
[Galaxy S 4 i9505 Original Android Development] Bejda:
You need a custom recovery that will trigger 0x1 knox warranty void yeah.

You need to patch any zip that you wish to install to secondary or multislot rom,gapps for your secondary Slim rom needs to be patched as dual-boot zip then.
[Galaxy S 4 i9505 Original Android Development] DVDeus:
Thanks for that info. So there is no way to run custom ROM without triggering knox flag?
[Galaxy S 4 i9505 Original Android Development] gaww:
You have to patch the GAPPs. You can't flash anything with stock recovery other then oficial update.zip.

As for warranty - if you updated with factory firmware and have KNOX - installing a custom recovery will permanently trip it and void your warranty in N America. In Europe, based on posts elsewhere - by itself it does not. If you did not update and get KNOX'd - you can revert to stock if you need warranty service.
[Galaxy S 4 i9505 Original Android Development] RK:
I tried ShoStock v5.0b2
[Galaxy S 4 i9505 Original Android Development] DVDeus:
My phone was factory KNOXed, so I am stuck with it. I have checked with my official Samsung dealer, and warranty is not valid in case of 0x1.

Anyway, why would I need dual boot then? Because I have thought all that work here was done because of keeping the phone under warranty, which (now I know, tnx gaww) is wrong. Is there any other problem for me to just flash it directly to SlimBean? Can I go back to the stock jb or kk later? Of course, with that 0x1 flag unchanged.
[Galaxy S 4 i9505 Original Android Development] gaww:
You can always go back, but you cannot reset KNOX, which I believe be tripped when you install custom recovery (which you have to do to do anything).

Then - per the instructions in the OP (plus make sure duel boot is

enabled

, or you will flash SlimBean over your current ROM - make a nandroud first), also patch the GAPPs (and any kernel you may want to use) and go for it.

---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------

Thanks - will give it a look.
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=3019752]gaww[/MENTION],

Sorry but again the dual-boot enable zip is only available on Noobdev's thread cause it's only needed when one wants to flash Noobdev rom as secondary.

It's not needed for any others secondary rom as long as its zip is dual-boot patched.

Maybe something happened to you that lets you think so,not a big deal if you feel more secure on your side to flash it before updating any other secondary rom but it tends to give the impression that something is wrong or missing from OP which is not the case (many users would have noticed it i think).
[Galaxy S 4 i9505 Original Android Development] gaww:
I had thought I had run into an issue after I had updated primary a while back, but I have used noobdev so much that it might not have been with another secondary ROM - sorry for the confusion.
[Galaxy S 4 i9505 Original Android Development] Technical:
What does happen with apps moved to sdcard?

I mean, can they be used in the 2nd ROM?

What are the safer way to get this?

Thanks.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
This is awesome, I tried a while back but just had problems, I know think it may have been something to do with xposed as I was running a million modules and found it messed with other things too (it it may just be coincidence-I don't know). Anyhow, coming back and trying with all the latest updates I am delighted to now have 5 ROMs all loaded up and ready to go within a couple of clicks. Awesome, just awesome! Thank you for your work, I am very happy customer :)
[Galaxy S 4 i9505 Original Android Development] jova33:
This... is a good question... did you try it?

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] gaww:
Apps move to storage may free up more room for loading multi-ROMs, but I don't believe it has anything to do with sharing apps between the ROMs .

It might actually limit their being used in secondaey (or slot ROMs) IF moving there interferes with the user app sharing zips posted earlier in this thread.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Is it possible to make nandroid of ROMs in multi slots/dual boot? Come to that I seen to be struggling to make nandroid of primary, I have enough space, just clearing some more though to make sure.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
http://xdaforums.com/showthread.php?p=46641708

A regular recovery nandroid will make a nand of all Roms as is not single rom
[Galaxy S 4 i9505 Original Android Development] endwhysee.bk:
will this work for L720 for sprint s4. ?

Apologize if this has been answered , I was trying to read thru all but my kids are driving me crazy.. lol..
[Galaxy S 4 i9505 Original Android Development] Technical:
I was used to multiboot with RomSwitcher on a maguro phone and we have an option for apps sharing (and also, a troublesome option for app data sharing). It saves a lot of space.

Right now, I'm not able to test, but it will be good to have a word from the developers before. I'm afraid of messing all the phone... or, at least, lost all apps data and have to start all over again.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
TouchWiz 4.4 is now fully supported (with working baseband) in the latest

experimental

build :) http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html

I've personally tested the AT&T SHOstock (TouchWiz 4.4) ROM on my T-Mobile variant and everything works just fine. So starting now, I will accept requests for supporting more of these ROMs.

The experimental build should be able to patch most TW 4.4 ROMs with these settings (check Loki box if needed):
[Galaxy S 4 i9505 Original Android Development] Shanks:
I heard you develop a new dialer for slimkat, thank you so much boss
[Galaxy S 4 i9505 Original Android Development] gaww:
Can it be patched with app or only PC ?

Update - could not flash with the app. Also, could not flash with latest experimental either. It is apparently supported now, so the UI does not come up. It indicates it could not extract image.

I was able to flash it with earlier PC experimental with the settings in the post above, but once more, it will not boot (I had cleared out enough room in cache so there is still room after flashing it.

Am at a dead end now .
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Could somebody help me please - I seem to have got into a real mess trying to update my primary ROM - something seems to have happened to my recovery now even though I have done full wipe several times I can't seem to flash any new ROM's without getting 'unable to mount system' etc and ultimately FAIL. Then recovery goes weird and won't work again until I force power off and reboot to recovery - then when I wipe again and still dan't flash - the nandroid backup I have restores but I can't update even though I don't have any ROM's in dual boot/multi slots.

So - I'm back reading the OP and see this:

Update the primary ROM?

Edit META-INF/com/google/android/updater-script so that it does not format /system or /dev/block/mmcblk0p16 (because the 16th partition is /system)

I have no idea how to edit meta.inf so it doesn't update system or /dev/block

Please could someone help with this as I'm a bit baffled ATM - but love this dual boot system!
[Galaxy S 4 i9505 Original Android Development] Bejda:
The instructions you mentioned from OP (edit updater-script) are given to update your primary rom without wiping your secondary rom's system.They aren't really necessary as you could just update or flash another primary rom without modifying it and you'll just have to reflash secondary rom when you'll need it after otherwise secondary rom won't boot anymore (but you won't loose any secondary rom data,it's just that its system will be wiped then needs to be reflashed).

Your recovery issue seems to be another problem,what recovery and version is it?
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
TWRP - 2.5.0.2

I just flashed stock rom through odin then rooted again using cf auto root then flashed TWRP back again, thing is now when I go into recovery or at boot splash screen there is a message in red that I cant quite read but something about 'non enforcing kernel' - something else written in yellow underneath.

Still can't flash anything other than the ndroid I have - managed to install ROM to dualboot though.

So sorry if this is way OT, any help or direction to another thread much appreciated though.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Update your twrp version, should help in (m)any way(s):

http://www.teamw.in/project/twrp2/182

Red and yellow lines at boot are there cause you flashed a stock Sammy rom with knox bootloader and now are under a custom kernel.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Thank you for helping me - I can't help feeling like a bit of a chump flashing stock knox bootloader - I guess there is no coming back from that now?

Glad to say that I am now able to flash whatever I like in primary slot now - so, I would really like to learn what to edit in meta.inf so I can update in future without having to reflash second rom etc, I'm guessing if I have ROM's in the multi slots I would have to reflash those also?

Is it as simple as just deleting the whole file in the meta.inf updater script: 'META-INF/com/google/android/updater-script so that it does not format /system or /dev/block/mmcblk0p16 (because the 16th partition is /system)' ??

Thank you
[Galaxy S 4 i9505 Original Android Development] Bejda:
Multislot roms system lies under our device /cache partition so they shouldn't get wiped when flashing/updating primary but better check if primary rom updater-script doesn't command to wipe cache (mmcblk0p18).

Usually it's as simple as mentioned yeah,just delete the wipe system line of primary rom's updater-script but here,once edit done,you have to use dual-boot utilities zip to wipe primary system before you flash your edited zip. There's also for now an additional step required (can't find link,not enough time right now :o )

Frankly for now better flash your primary rom as it is and reflash you dual-boot patched secondary rom (keep it on sd) when you'll want to boot it again. It takes just the time to flash it,you loose nothing ;) (edit: you loose nothing except of course any system modification you brought to your secondary rom and as its system gets wiped at some point you have to reflash gapps also).
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Run out of 'thanks' for today - but thank you for helping me get my head around all this - so I just find (mmcblk0p18) in meta inf, delete that and then my multislot roms will be protected? If thats the case, I'm wondering if better to leave dual boot slot empty and just use multislots??

I found the backup and restore updater zips that OP recomends to flash before and after updating primary - could this be the extra step, and may that save the multislot ROM's?
[Galaxy S 4 i9505 Original Android Development] Technical:
How do I completelly uninstall (remove) the 2nd ROM?

Will just wipe options in DualBootUtility do it?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, that'll do it. You could also boot into your primary ROM and delete /system/dual, /data/dual, and /cache/dual manually.
[Galaxy S 4 i9505 Original Android Development] Technical:
Thanks. Indeed all folders are wiped (deleted). Except /system/dual-kernels.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
--delete wrong thread....

My bad
[Galaxy S 4 i9505 Original Android Development] *boy*racer*:
So I finally managed to dual boot but when back on my primary rom, auto rotation don't work. Although when on camera, the icons turns :-/.

Any thoughts why this may be happening?

Thanks
[Galaxy S 4 i9505 Original Android Development] endwhysee.bk:
Can someone please let me know if this would work on l720 . I would to try this. Thanks ahead.

O.Nice a Galaxy S4
[Galaxy S 4 i9505 Original Android Development] nicholi2789:
[MENTION=4277844]chenxiaolong[/MENTION]: Sorry I really hate to ask you this but I got to, Is there any way you can add support for a Google edition rom found here: http://xdaforums.com/showthread.php?t=2643031?? I've manually patched a few zip files here and there but I'm kinda nervous about patching a whole rom. Or could you just take a look at the updater-script that I manually patched to make sure it's okay? Thanks alot for all your work on this mod.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Should be supported already, what happens when you try to patch it and which DualBootPatcher version do you use?

---------- Post added at 08:45 AM ---------- Previous post was at 08:41 AM ----------

Probably not related to dual-boot, your primary rom is a Touchwiz 4.4 rom?

I guess it's a known issue on some roms, happens when you hot reboot and maybe reboot but not from a cold start/power on no? Or maybe something with Xposed..i don't remember well..

---------- Post added at 09:00 AM ---------- Previous post was at 08:45 AM ----------

I edited my latest answer to you for the "you loose nothing" part but I should check OP more often lol,all that I'm saying is there already :o

You could just have a primary and multislot* roms but as you can see some updater-script (yours here) wipes /cache also so same story: should be edited.

The thing ,and the purpose of these backup/restore zip, is that even if you edit your primary rom updater-script for it doesn't wipe system (and instead use dual-boot utilities zip that will preserve /system/dual) your secondary/dual rom may not boot after anyway due to some permissions issue. The backup zip saves some dual rom permissions and restore one set them again after. This doesn't happens with multislot* rom.
[Galaxy S 4 i9505 Original Android Development] nicholi2789:
I'm using patcher version 4.0.1 and it just says unsupported zip. It says that on both the apk and windows versions. I tried to manually patch it too but when I tried patching the ramdisk it says unsupported as well. Super frustrated. lol
[Galaxy S 4 i9505 Original Android Development] Bejda:
Here's the DualBootPatcher patchinfo part:

filename_regex = r"^(danvdh-GE|Dandroid).*\.zip$"

But I'm not sure it's a simple zip name mismatch here,maybe some changes in latest rom version (i see a change for updater-script on changelog).

Could you post META-INF folder and boot.img from the rom please, this way Chenxiaolong could have a quick look and maybe gives you a workaround,dunno..

Edit: Ah,i didn't see it was Verizon version,maybe different support is needed then indeed,sorry.
[Galaxy S 4 i9505 Original Android Development] nicholi2789:
It's okay. Thanks for trying anyways. I'm sure he will come out with something for it soon. He always is pretty prompt about support.
[Galaxy S 4 i9505 Original Android Development] Spiricore:
Any chance for Octo-Kat support? http://xdaforums.com/showthread.php?t=2493128

Otherwise I am happy as a clam for finding this. You are awesome! Thank you!!!
[Galaxy S 4 i9505 Original Android Development] chavdar:
As of late I am running into problems with the latest Phil's recovery. When I try to flash multi slot 1, the flash starts but shortly after the recover reports error and exits with status 7.

It happens on every multi slot 1 ROM. I have to flash an older version of the recovery to flash the ROM

So it clearly is an issue with the new recovery.

Does anyone knows why this happens?

Sent from the GT-I9505 Galaxy
[Galaxy S 4 i9505 Original Android Development] Bejda:
Most probably a bad zip/latest Philz version relationship if i can say (no errors for me with at least SlimKat and AOSB rom with latest 6.13.1 version).

Since Philz 6.09.6 many zip can throw out errors for differents reasons.

Could you tell which rom and version gives you errors and after status 7 error go into recovery advanced settings to show log and/or if not easily readable report error (will push a recovery.log file under /sdcard/clockworkmod/ , the error should be detailed at the end of this file).
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm in a bootloop following these instructions.

I'm sure I'm setting the 1st ROM (Slim ROM) into the app and patched 2nd correctly.

I've tested 2nd with CM Nightly and Omni (nighty too).

To return back from bootloop, I need to flash 1st ROM again.

What am I doing wrong?
[Galaxy S 4 i9505 Original Android Development] gaww:
What recovery are you using to flash? As from previous posts, many are having issues with some Philz versions. I had similar problems with latest TWRP (but most users didn't have issues with it), so switched back to earlier version.
[Galaxy S 4 i9505 Original Android Development] Technical:
I'm using TWRP 2.6.3.1. It worked last week. I really doubt it's the recovery.