yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Bejda:
Maybe with a different script but even this one doesn't seems to work anymore:

#!/sbin/busybox-static sh

/sbin/busybox-static mkdir -p /raw-data/app /data/app

/sbin/busybox-static chmod 0771 /data/app

/sbin/busybox-static chmod system:system /data/app

/sbin/busybox-static mount -o bind /raw-data/app /data/app

If confirmed i don't know if there will still be a way "out of kernel".

Chenxiaolong will probably know more about it and tell us which possibilities stands :)

[MENTION=5528810]Jimsilver73[/MENTION]

Don't hesitate to ask if you face some difficulties with ramdisk edit,PM or whatever..or why not here if it helps others.

I promise I'll try to be clear and concise :laugh:
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
OK, found the multi boot sh file in the ramdisk and uncommented the relevant # you indicated.

Now how do I repack the booting to use in my patched kernel please?
[Galaxy S 4 i9505 Original Android Development] remorema:
Thats it then. I configured it from scratch on both ROMs cause I'm really not into titanium backup.

I have to say that's the only thing I have to point out after a couple of days playing with this tool. And its a very very easy fix.

As I told earlier this tool is freaking awesome and now that I got the script running for app share and was able to Mount external obb on both ROMs, I can easily say its rock solid for daily usage.

I go back and forward on TW and CM and have zero issues with apks.

Either I update an app from primary or secondary , its all good when I boot to the other one.

The only big question is: how much time can I keep it like this and don't start messing around with other stuff :laugh:

Its funny how we lose more time playing with ROMs than we do with games. :crazy:

Now go watch some soccer you freaks :p
[Galaxy S 4 i9505 Original Android Development] Bejda:
You type

./repackimg.sh boot.img

It will produce a image-new.img which is the edited boot.img

What I've done after on my side was,while using another rom, to put this .img under /sdcard/MultiKernels folder,rename it accordingly (secondary.img for you) and use DualBootPatcher.apk to switch to this rom.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Thank you, I managed to work it out - I just renamed boot.img and it sends to be good.

Need to get my head round what you suggest here once I've had some sleep I think - small steps = big leaps for me ATM :)
[Galaxy S 4 i9505 Original Android Development] Bejda:
I tried again with Kantjer's 5.8 build but this time used a cwm zip to install the kernel.

If you're on same rom version you can use this dualboot zip,it went fine for me:

(Note: Only for SlimSaber build,may misbehave if flashed on another rom as modules are removed from the zip)
[Galaxy S 4 i9505 Original Android Development] Technical:
Hope he could give us some of his time on this :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Bejda:
If really there's no other solutions than passing through kernels to share these partitions and if Chen is ok with that i guess it would be "easy" to add a simple "patch kernel as share-apps ready" option but the amount of possible combinations may make it too loud and a pain in the patch to implement.

Right now for instance i preferred to share my multislot-2 data/apps with multislot-1 as both are aosp (..and SlimKat builds lol).
[Galaxy S 4 i9505 Original Android Development] remorema:
I'm missising something here.

Why go to all the hassle of patching individual boot.img's when a simple init script will do the job.

Oh and by the way. As expected titanium did the job for what's app messenger. Its now working on both roms without re-registering ;)

Go Portugal!!!!!

Edit: hey guys I'm using hall monitor for s-view function and it works OK. I'm wondering what app/mod you guys use for s-view on non Samsung roms.
[Galaxy S 4 i9505 Original Android Development] RK:
Because the init scripts don't seem to work if your secondary ROM is 4.4.3
[Galaxy S 4 i9505 Original Android Development] remorema:
And other scripts work? Its weird.

4.4.2 works ok. It must be something related to how system mounts partitions at boot.
[Galaxy S 4 i9505 Original Android Development] reiter123:
Selected the wrong kernel. What to do

I've selected "set kernel as primary" by mistake while running the secondary ROM and it was then impossible to reboot into primary ROM. => This results in a situation where you are only able to run the secondary ROM. (the primary is overwritten)

I just post this (it might be already in the thread) to help anybody who got in that situation like me late night yesterday to find a "help":

If you have a nandroid backup (maybe pre Dual boot installation) in ClockworkMod Recovery (CWM) just do the following:

- Select extended Restore

- Select only Boot

=> Thats it you are back in a working Dual boot scenario :) :laugh:
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=5528810]Jimsilver73[/MENTION]

Not sure but i guess i did a stupid mistake with the previous Iink,was a multislot-1 kernel trying to share apps from primary rom on secondary something like this :confused: :o

Here's one for latest SlimSaber 5.9 build as secondary rom and that will use primary rom's data/apps:

https://app.box.com/s/wv1zeqhqz7ue36tbmjma
[Galaxy S 4 i9505 Original Android Development] gaww:
This is really easy - just reflash primary kernel and it should boot up OK. Don't forget to set it as primary again. I have done this a few times myself - lol.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Bejda - than you so much for showing me how to edit ramdisk - I now have 5 ROMs up and running all sharing the same apps and all seems to be working well with a full tb backup I still have 1.5gb to spare, that's pretty good I think seeing as one of those is a tw!

I managed to edit two ROMs boot.img also so got stock kernel in omni and brood :D

Oh - just realised that new installed apps aren't automatically showing up in the other ROMs. Any ideas how I can get that bit working anyone?

Edit : oh oh, it gets worse - I seem to have completely lost Google Play services in dual slot (tried reflashing gapps) it seems you may be right Bejda, maybe it is more trouble than it is worth :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah, I completely forgot about the dualboot.sh script. I'll have that fixed in the next version. I might try formatting my userdata and cache partitions as f2fs to see if I can fix some of the other issues.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since this is the most requested feature by far, everyone can look forward to this in the next version :) It requires no init.d support in the ROM or kernel. As usual, no guarantees that this will work though since apps are not always compatible across ROMs.
[Galaxy S 4 i9505 Original Android Development] gaww:
Have not used it in awhile, but I think when you add new apps to primary, you have to run the zips again. And you have 4 of them - lol.

---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------

Sharing paid apps sounds interesting - expecially if it will work with Copilot GPS
[Galaxy S 4 i9505 Original Android Development] arifqur:
Brother that is a really nice feature.

Man it would be hard to migrate to any other phone simply because of the Dual/Multi-Slot mod that you have so brilliantly developed.

P.S.: Please let us know which phone you plan on upgrading to so that we can buy the same and hope that you develop this super Mod for that phone also.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Well actually maybe i could have get used to it,i find this pretty useful and handy finally lol.

It only share apk's,that's one of the reason it never really interested me, but that way i only have to batch restore app's data with Titanium (TB saves on sdext btw), it's undeniably faster than batch restore apps+data.

For me all is fine i do it that way on multislot-1 boot.img for it works with multislot-2 and 1,both aosp (on Touchwiz primary rom i have a pretty different set of apps installed,i don't really want to share all this with my others aosp roms ).

# Eventually, maybe share /data/app

/sbin/busybox-static mkdir -p /raw-data/multi-slot-2/app /data/app

/sbin/busybox-static chmod 0771 /data/app

/sbin/busybox-static chmod system:system /data/app

/sbin/busybox-static mount -o bind /raw-data/multi-slot-2/app /data/app

Apps gets automatically installed on both rom for me as it should and i can't see why it would produce some GooglePlayServices issues at first sight but well let's wait for Chenxiaolong's magic now :)
[Galaxy S 4 i9505 Original Android Development] remorema:
[MENTION=4277844]chenxiaolong[/MENTION] can you please add suporte for PureNexus-Danvdh-GE-4.4.3-06102014-INT.zip

I would like to test that one in multi-slot-1 to keep it clean without APP sharing ;)
[Galaxy S 4 i9505 Original Android Development] lilila:
Thanks. Any plan to support patching ColorOS 2.0 for I9505?

I tried to install ColorOS at dual slot and every time it boots up, the initial setup screen appears. Looks like the data partition is not preserved after reboot.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
:confused:

I have been running danvdh's ROM since it was 4.4.2 to the present day on multi slot 1.

Perhaps you still have data lurking in that slot, it happened to me with my secondary slot, all other slots worked fine though, and it made no difference no matter how many times I used dual boot utilities to fully wipe the second slot, finally I formatted the SD card and everything is fine now.

---------- Post added at 07:27 PM ---------- Previous post was at 07:21 PM ----------

Thanks bejda, I might try that, maybe it's a tw incompatibility thing. What actually happened was that everything was running sweet in all ROMs until I went back to my primary slot tw and discovered Google play had disappeared. So I flashed banks minimal gapps and that got my play back and that's when my problems started on my other ROMs.

Maybe I just wait for chenxiaolongs magic - or, I may mess some more lol.
[Galaxy S 4 i9505 Original Android Development] remorema:
I never user multi slot. the app doesnt reconize danvdh's ROM you probably patched it manually
[Galaxy S 4 i9505 Original Android Development] Bejda:
Download patcher .zip version and check /patchinfo/jflte/ROMs/GoogleEdition/dandroid.py file to see which supported name the patcher expects.

I'm pretty sure that if you remove "PureNexus-" from the rom zip name it will be stated as supported and patched fine.

And anyway,patcher apk has custom patches support now,once zip is stated as unsupported simply choose jflte/ROMs/GoogleEdition/dandroid as custom preset should work just fine as well,did you try?
[Galaxy S 4 i9505 Original Android Development] remorema:
TKS Bejda. Custom dandroid worked flawless. I didnt associate the names ;)
[Galaxy S 4 i9505 Original Android Development] peppe130:
[MENTION=4277844]chenxiaolong[/MENTION] [MENTION=3145598]rlorange[/MENTION] Why don't you combine the Dual Boot Patcher App with the Dual Boot Backup App? So there will be an all in one App! All in the same app

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] :
Thanks for the massive updates! Can you please add support for PA GApps? http://xdaforums.com/showthread.php?t=2012857
[Galaxy S 4 i9505 Original Android Development] blood_talon:
Thanks, mate! I will give it try!

EDIT: Install went flawlessly. Need to test more to see if any bugs. It would be great if we could have a prompt when booting the phone in order to choose which ROM/kernel to boot. :)

Anyway, thanks again!
[Galaxy S 4 i9505 Original Android Development] bulgareli:
Chenxiaolong,

Can you add support for this Gapps?

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

The latest complete PA Gapps (pa_gapps-full-4.3-20130926-signed.zip)

Thanks!

Enviado de meu GT-I9505 usando Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] kosako17:
Please can you add support to Htc One rom port?

I have tried myself to add support but gives me error with a script :S

Enviado desde mi GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] TorpedoGirl:
I've installed a ROM in dual boot but I don't like it, so...is there a way to remove it?

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] bulgareli:
Boot in primary ROM first. Then reboot into recovery mode and use the helpful zips wipe system secondary ; wipe data and cache secondary.

Enviado de meu Nexus 4 usando Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] Kaito95:
Hello,

is there any support for CyanogenMod 10.1 (Stable) ? i tried it but it's not working. Could you make support for CM10.1 please? :D

thanks in advance :)
[Galaxy S 4 i9505 Original Android Development] munchy_cool:
Hey buddy,

I thought you have added support for carbon but I am still getting an error.

./patch-file.sh CARBON-JB-NIGHTLY-20130928-0702-jfltetmo.zip

Unsupported zip

edit

I have wrong version of utility ...downloading newest one :)

edit 002

new error on mac

./patch-file.sh CARBON-JB-NIGHTLY-20130928-0702-jfltetmo.zip

Detected Carbon Nightly ROM zip

Using patched Carbon ramdisk

--- Please wait. This may take a while ---

Failed to run command: "/Users/munchy/desktop/dualboot/patcher/patcher/scripts/../binaries/unpackbootimg -i /var/folders/mr/hkr5g3y10p52bghj2rpv1vfm0000gn/T/tmpADu0_G/boot.img -o /var/folders/mr/hkr5g3y10p52bghj2rpv1vfm0000gn/T/tmpHizEFN"
[Galaxy S 4 i9505 Original Android Development] bamserl:
627mb free space o /system isn't enough for i9505-ge-untouched-4.3-JWR66Y.S003-v2.zip

after install, which went fine, there are only 8kb free on /system and my s4 has no imei within the 2nd rom.
[Galaxy S 4 i9505 Original Android Development] loco-:
Hi guys,

what do you do, when you accidentally set the secondary kernel as primary kernel?

I don't want to lose my data from primary rom. The utilities.zip doesn't help.
[Galaxy S 4 i9505 Original Android Development] bulgareli:
It never happened to me, but I think you can set the correct kernel another time, and it will overwrite the old kernel.

Make a backup just in case...

Enviado de meu Nexus 4 usando Tapatalk 4
[Galaxy S 4 i9505 Original Android Development] RK:
The utilities won't help.

Flash the correct primary kernel in recovery and reboot. You should reboot right into the primary ROM.

If you don't have the kernel, flash the primary ROM again WITHOUT a data wipe. You will boot back into primary ROM. This way you may loose the secondary ROM entirely though..
[Galaxy S 4 i9505 Original Android Development] loco-:
Ok thank you guys, i'll try it. I don't care about the secondary rom.
[Galaxy S 4 i9505 Original Android Development] RK:
You have both the Roms on the phone in different places. Which ROM you boot into is decided by which kernel is there in the /boot partition. So all you need to do is to flash the correct kernel to the /boot partition. That is, grab the kernel zip file and flash in recovery as usual...

The primary and the secondary kernels are stored elsewhere on your phone. When you select primary ROM in the switcher app, all it does is grabs the kernel marked primary and moves it to the /boot partition. Similar for secondary.

Now since you selected the secondary kernel as primary, you have two copies of the same kernel marked primary and secondary. So no matter which ROM you pick in the app, you are going to end up with the secondary kernel in the /boot partition.

Hence, just flash the primary kernel like usual and then set it as primary when you boot into primary ROM

:)
[Galaxy S 4 i9505 Original Android Development] knightsh:
I'd like to give this a try as well. On the T-mobile S4 running Wicked v7 found here: http://xdaforums.com/showthread.php?t=2265998 Can support be added? If using as primary, if I read correctly, it doesn't need patching? Only the secondary rom, which I plan on using Slim Rom or the GE. Slim already has support listed in the op, is that all S4 variants? Thanks for any help/direction on running this successfully!
[Galaxy S 4 i9505 Original Android Development] rlorange:
Just like to say THANK YOU SOOO much for this wonderful mod mate!! Works perfectly!! I just had to mess with Folder Mount app a bit to get it working but it's brilliant...

I missed dual boot terribly from my old S3 days but no longer.

Amazing idea. Amazing dev. Flawless implementation :)
[Galaxy S 4 i9505 Original Android Development] rlorange:
I'm using TW 4.2.2 as my primary and tried GE 4.3 and cm10.2 as secondary rom. Anyone tried using Folder mount across this type of setup? It's not working for me... I can change the pairs but they just bug out again after a reboot
[Galaxy S 4 i9505 Original Android Development] knightsh:
Well, decided to give it a try. Using wicked v7 as primary. Patched Slim Rom 4.3 and the Aroma Slim gapps and flashed in recovery. All is good. No problems except Aroma installer was a little buggy, probably nothing to do with Patcher. Can you take a look at the regular Slim Gapps(not the AIO)? They weren't compatible which is why I had to use the Aroma version of Slim Gapps. Lovin' this! Thanks to all involved!
[Galaxy S 4 i9505 Original Android Development] Bejda:
Yeah i once had same question but it works answer is here:

http://xdaforums.com/showpost.php?p=45560831&postcount=1952
[Galaxy S 4 i9505 Original Android Development] rlorange:
Oh yeah! Thanks heaps man. Really enjoying discovering how this mod works... Very clever dev i must say!!!
[Galaxy S 4 i9505 Original Android Development] gaww:
I tried to patch both SlimSaberKat 4.4.3 and 4.4.4 with the 7.0 r8 and r9 Windows GUI, and it would not ever start. It worked OK on 7.0 r1.

Ditto with latest KT kernels. I think the GUI's just don't work. I downloaded it twice.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, at the moment, the experimental versions only work on Linux. I will fix support for other operating systems once I finish up the app sharing features.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The next version of the patcher will also support sharing individual apps. With this method, space is saved while retaining flexibility. If, say, you share the primary ROM's Facebook app with 3 dual booted ROMs, you can uninstall the app from any ROM and it will remain in the other 3... and still only uses the amount of space occupied by one copy of the app :D
[Galaxy S 4 i9505 Original Android Development] RK:
Sounds like magic :)
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
That is totally awesome...and it will also work on nexus 5? ;)
[Galaxy S 4 i9505 Original Android Development] remorema:
That is awesome. I end up giving up app share because I didn't want all the apps showing on both Roms.

If you can make this by selecting what apps you want to share prior to applying app share patch it would be very interesting.

Tapatalked from I9505 Google Edition
[Galaxy S 4 i9505 Original Android Development] Technical:
AMAZING!

Even with 4.4.3 that is already bringing issues with Appshare at the moment.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You won't need to flash any app sharing zips or copy any scripts, just open the patcher, check the checkboxes for apps you want to share, and that's it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, it will work on every device supported by the patcher :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Awesome!!! :laugh:

However, I have a question, I did not care if it has already been posted elsewhere. if this is the case ... sorry!!

If we make a wipe data in a rom, what does happen for the others?
[Galaxy S 4 i9505 Original Android Development] Bejda:
You can do all the wipe you want on any rom as long as you use DualBootUtilities.zip for that.

Otherwise if you wipe data from recovery you loose all your others roms data.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For DualBoot Utilities, I already know it. I asked about of the new feature to DualBoot Patcher, the sharing to apps for all roms. If that's the same apps which are shared for all roms, there is a risk with the "wipe data", even by DualBoot Utilities.

---------- Post added at 12:46 PM ---------- Previous post was at 12:42 PM ----------

In more, [MENTION=4277844]chenxiaolong[/MENTION] should update Dualboot Utilities, I think.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you wipe data from one ROM and apps are individually shared, those shared apps will remain in the other ROMs :)
[Galaxy S 4 i9505 Original Android Development] sronweb:
What about sms and call log? It's possible to share them? Thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Hi,

Thanks... Good.

Envoyé depuis mon GT-I9505 avec Tapatalk
[Galaxy S 4 i9505 Original Android Development] remorema:
Will it work both ways? Right now I have most of my apps installed on secondary.

Would be cool to select a few to share with primary :)

Tapatalked from I9505 Google Edition
[Galaxy S 4 i9505 Original Android Development] sronweb:
Sharing apps will be very important for us especially considering the possible switch to ART runtime which require more space for the apps.

:good:
[Galaxy S 4 i9505 Original Android Development] Technical:
[MENTION=4277844]chenxiaolong[/MENTION]: how would it handle the Google Account? I mean, right now, when you share the apps you have 2 options:

1) or you use the same Google Account and your "new" phone will be the 2nd (or other) ROM, i.e., when you browse Google Play in your PC you can't install in the 1st ROM as only the other appears. The "solution" would be delete the account from main ROM, reboot and create it again (but, in this case, you can't install in the 2nd ROM (using the PC).

2) or you can use another Google Account but then, the apps are not in your account but as being installed by 3rd party sources. You also lost all your paid apps (and some free that restricts).

The paradise would be share the apps and the Google Account as you're really using a 2nd ROM in the very same phone. Something is telling me this is not technically possible. Can you confirm?

Thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, the Google Account issue is something I want to fix, but I'm not sure how to. As you saw, Google is detecting both ROMs as the same phone, so whichever one was signed in last is the one that works with the Google Play website. The best way to fix this is probably to have both ROMs show up as separate devices in Google Play. Since all the Google services are proprietary, it may take me a while to figure out how to do this though.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It is theoretically possible, but I would need to add a bit of code to work around the SELinux limitations in stock TouchWiz ROMs. I'll think about adding that once this feature is stable :)

EDIT: I take that back for now. I have to do some hacking around to make sure updates don't "unshare" the apps and this only works on the non-primary ROMS.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That would be very difficult to do because SMS and call logs are stored differently in each ROM. (This is probably why backup apps, like TitaniumBackup, are updated so frequently too)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The initial implementation seems to be working as expected :)
[Galaxy S 4 i9505 Original Android Development] gaww:
Which version is that on? Also, just trying to patch with r9 app FC's - is that also the same issues as on the Windows version?
[Galaxy S 4 i9505 Original Android Development] remorema:
Hey guys. Im using the latest pure nexus as secondary ROM in my dual boot setup. The thing is every time I reboot time and date are wrong and they need network to auto correct itself. Is it ROM related or something with the dual boot patcher?

The thing is with my previous setup using cm11 m7 as secondary it also happened. So what am I doing wrong here? :(

Tapatalked from I9505 Google Edition