yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Technical:
[MENTION=4277844]chenxiaolong[/MENTION]

Is it possible to save the settings (1st and 2nd kernel) that allows we to restore from recovery (dual boot utilities)?

Right now, you need to return to the ROM and set the kernel manually.

But if we have 2 zips to be flashed (before and after the ROM flash), can it be there all the times? I mean, when you configure the 2nd kernel, even flashing a new 1st one, you can restore the 2nd only with this saved info.

Thanks.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Hello :)

I'm not sure i understood well your concern but you only have to set kernel on primary rom every time you flash a new primary rom or a new kernel for that primary rom.

Others roms use patched zips,patched zips that sets kernel automatically. It's not needed (except maybe on some specifics situations) to use patcher app to set kernel on secondary and multislot 1,2,3 roms.

I don't think i tested this already but i bet that you can even flash a new secondary/multislot rom or kernel and right after,still on recovery,use DualBootUtilities zip to boot on another (for instance if you just wanted to flash a new secondary/multi rom or kernel but don't have time at this very moment to boot on it go through first installation process or whatever and would prefer,for now,to reboot on another already installed rom.....Not sure i understood myself well here lol).
[Galaxy S 4 i9505 Original Android Development] Technical:
We have to... but, isn't there other automatic option for us?

If you not reboot to the second (recently) installed ROM and set the 2nd kernel, you couldn't boot that ROM at all. That's the problem. You can't use DualBootUtilities and return there later afaik.
[Galaxy S 4 i9505 Original Android Development] gaww:
Omega is too big.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Really "a priori" we don't have to use the app to set kernel for secondary and multislot's roms.It is automatic and done by patched updater-script+dual-boot.sh in the patched zip.

I just tried.

Had a new version to flash as multislot 2 rom.

I used DualBootUtilities zip to wipe multislot 2 system (which also delete /sdcard/MultiKernels/Multislot 2 boot.img)

Flashed my new multislot 2 rom but right after,still on recovery then,used DualBootUtilities zip again to switch to my secondary rom.

On this secondary rom i could use DualBootPatcher app to switch to multislot 2 successfully and finish my multislot 2 rom installation.

Again i don't know our goal here lol but what i told you (and imagined for the second part) was right :)
[Galaxy S 4 i9505 Original Android Development] Technical:
Indeed it failed to boot in my case. Extremely bloatware.

[MENTION=4547867]MohamedN[/MENTION]

Flashing DualBootUtilities you can wipe everything there and restore the 1st (and eventually unique) ROM.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Can we add support for Danvdh's 4.4.3 rom please? :) Thanks!
[Galaxy S 4 i9505 Original Android Development] gaww:
You don't impact the primary if you wipe the secondary system only with the utility. If you wipe /system in recovery you will wipe both.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for letting me know! I pushed 23 commits yesterday that fix this (which also have the side effects of F2FS support and ease of adding support for other Qualcomm devices ;))

http://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
[MENTION=4277844]chenxiaolong[/MENTION] anything on my aokp problem? It always gives force closes when installing aokp +aokp gapps to a multi slot. I checked and it has nothing to do with available space. It happens on aokp only though. All other roms I tried work great with gapps. I don't know if this happens on the secondary slot too. When no gapps are installed the rom works, but when I install them things get broken very badly. Could you look into that please?

Edit: with version 6 of the patcher, aokp doesn't even boot anymore. And it doesn't recognize the aokp gapps package and the preset for it gives an error. I had to use custom, but aokp bootloops, even without gapps. I also think it messed with my primary rom because some apps dissapeared but after rebooting they where back but out of order.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] Bejda:
Works perfectly now :good: (in case you wondered lol, thank you again for all).
[Galaxy S 4 i9505 Original Android Development] gaww:
I patched SlimSaberKat 5.6 with latest patcher with the commits and it would not boot up (tried to boot primary) until I flashed multislot2 KT Kernel Also wanted to try the kernel.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Same as me with 6.0.0 version but all fine with snapshot one.

i just choosed Slim preset as patch and it's ok.
[Galaxy S 4 i9505 Original Android Development] gaww:
I will try that. Did you use the PC or the APP ?

Update,

I tried APP again with preset - still will not work. Will try on PC.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
+1 :D

Got slimsaberkat with alucard booting prefect in multi slot 2. Interestingly, earlier when I tried to flash ssk with kt into secondary I could flash rom only but not gapps for some reason (that was with patcher 6)

Is my understanding right that if I want to upgrade my primary rom I can use dual utilities to clean cache and dalvik and then flash rom normally in recovery, if I had arom in secondary I would need to reflash rom into system but multi slots 1, 2 and 3 would be untouched by flashing primary?

Many thanks chenxiaolong for developing this truly awesome tool, and all for testing thus far - very happy customer here :cool:
[Galaxy S 4 i9505 Original Android Development] gaww:
If the updater script wipes /system, it wipes secondary ROM. if it wipes cache, it wipes all MultiROMs.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
OK thank you - still a little confused, so does that mean I would need to reflash all roms in multi slots then?

So, I want to use the before and after scripts and edit the rom updater script by don't really understand the instructions :

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)

Flash DualBootUtilities.zip before updating the ROM and choose Wipe Primary /system. If the primary ROM is AOSP-based, you will need to reflash Gapps.

Download the two zips here and flash the appropriate one before and after the primary ROM's zip: http://d-h.st/users/chenxiaolong/?fld_id=30845#files

I don't understand what to edit in : META-INF/com/google/android/updater-script so that it does not format /system or /dev/block/mmcblk0p16

Please could someone explain more easily understandably for a beginner like myself.

Also - alucard just updated his kernel again and the same problem is back with booting back to primary etc, last kernel 2.2.7g works fine though :good:
[Galaxy S 4 i9505 Original Android Development] gaww:
lol - on your Also - no wonder it won't work - tried it 3 times . Opps - did it on PC and the latest SlimKat booted.

On reflashing all Multislot ROMs - yes. You are dirty flashing as data is intact, but depending on whether or not you need to reflash GAAPs, kernels, and misc ROM mods - it can be easy or a pain.

You want to eliminate the format or delete recursive system or cache lines from the scripts, but I have not been able to successfully flash a modded script with aroma. I have modified updater scripts on primary ROMs that have aroma, and for some reason, it looks like it works as I step through, but it doesn't actually flash them (I did do so with a debloated TW ROM without aroma and it flashed and worked).
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
That's ok, I'm using wannamlite so no aroma for me - so what and how do I have to edit the meta inf please?
[Galaxy S 4 i9505 Original Android Development] gaww:
\META-INF\com\google\android\updater script

delete_recursive("/system");

delete_recursive("/cache");

Delete lines like this or any that say to format these partitions.

As for unzipping and rezipping – can’t help there, as this is apparently where I am having issues.
[Galaxy S 4 i9505 Original Android Development] Bejda:
[MENTION=4277844]chenxiaolong[/MENTION]

When i want to edit a cwm zip with Xplore file manager it still works fine with original but gives me error with patched zip. I don't think it happened in the past, i guess would've noticed but not sure..

On operations like open zip/copy a file out>edit> push it back/repack zip it gives:

I could as well just edit zips and repatch again but i wonder if it makes sense to you. Tells you something? :)
[Galaxy S 4 i9505 Original Android Development] Technical:
I've flashed appshare while dualbooting.

All my apps are shared between the 1st and dual boot ROM.

But when I move the apps to sdcard (Clean Master or any othe app2sd app) it only appears on the ROM that it got moved to sdcard.

Is there a way to create the links between the ROMs and got the moved apps on both ROMs?

Thanks.
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
Maybe using link2sd and an app partition on your sd card? It doesn't work with native app2sd because there is some protection to avoid piracy on apps moved to the sd card, so that they van only be used with one rom, or something like that.

Verzonden vanaf mijn iPad met behulp van Tapatalk
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Could you give us a link to 'appshare' please, it looks interesting.
[Galaxy S 4 i9505 Original Android Development] Technical:
I also try to find the files again and have a lot of difficulty.

When I search, the closer I get is http://xdaforums.com/sitesearch.php?q="I updated my app share cwm zips"
[Galaxy S 4 i9505 Original Android Development] `SBR`:
I tried flashing the danvandh ge edition using patcher 6, but the viper 4 android is not working with it asking to install driver again. When I install as primary ROM it's working perfectly. Could you verify what was causing the issue
[Galaxy S 4 i9505 Original Android Development] Mussels84:
Echoe rom has a new GE 4.4.3 rom out that i'd like support for dual booting.

What files do you need uploaded to get this added in [MENTION=4277844]chenxiaolong[/MENTION] ?
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Only GE roms have the issue, flashed cm and aosp V4A installed fine with dual or multi boot

Also tried with echo GE rom, V4A is not installing. .

Is it some thing to fixed with ramdisk?

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

It's booting with using windows patcher

Custom preset

Google edition as ramdisk....

But have issue in installing v4a
[Galaxy S 4 i9505 Original Android Development] Mussels84:
my echoe download was corrupt, thats why i had issues. not patchers fault.
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Ate you able to install v4a driver, could you confirm this after reboot?
[Galaxy S 4 i9505 Original Android Development] Mussels84:
testing now.

my guess is that it installs to the primary roms location, its not dual-boot aware.

edit: no, it asks for install every boot. it either doesnt work on 4.4.3, or it doesnt work on secondary roms. i guess only the maker of v4a will know that, or be able to fix it.
[Galaxy S 4 i9505 Original Android Development] `SBR`:
Thx for confirming.

It will work in dual and multi boot, I have tried with other aosp roms. Only thing it failing is GE rom on multi boot.

If you install as GE as primary rom, it works well.

I think it should be related to ramdisk patching. ..chen will have more knowledge on this
[Galaxy S 4 i9505 Original Android Development] Mussels84:
k well lemme know if you find a fix, as it will be relevant in the echoe GE thread as well.
[Galaxy S 4 i9505 Original Android Development] GRBull:
Can someone explain me the instructions please because i went over to the OP a couple of times and didnt understand some of the terms there. So you might call me blind and stupid but im just being careful because i think this might cause a bootloop that i can't fix and i already did the patcher.apk and the utility through recovery. So my secondary boot was liquidsmooth. Primary is goldeneye then when i went to the recovery to flash utility i switched over to secondary then i flashed the files needed like gapps kernel titanium backup. Then suddenly i see my bootanimation of what appears to be, goldeneye. I dont know what caused this so just letting you know what is my scenario and by the way its my first time to post in this thread.

Посланный от GT-I9505 помощью XDA Премиум 4 мобильное приложение
[Galaxy S 4 i9505 Original Android Development] franzyroy:
What was your kernel? What version of patcher do you use?
[Galaxy S 4 i9505 Original Android Development] GRBull:
My kernel is Kt Kernel, patcher is 6.0.0 the latest version.

Посланный от GT-I9505 помощью XDA Премиум 4 мобильное приложение
[Galaxy S 4 i9505 Original Android Development] franzyroy:
How have you patched Kt kernel? Automatic or with preset?
[Galaxy S 4 i9505 Original Android Development] remorema:
This APP is freaking awesome.

Installed following instructions and it works great. I only have one question and one issue.

Installed patched wanamlite as secondary having google edition 4.4.3 as primary. And ended up with just 22MB free in system partition. Ufff that was close.

The question is: would installation abort if I ended up having no room left on system partition? Or will it install until it fits and then end up missing system files upon booting?

Only issue so far is the camera not working on secondary wanamlite ROM. Is it ROM/kernel related or does it have something to do with dual boot setup?

I configured primary kernel as primary as mentioned in instructions and then after booting secondary for the first time I also setup secondary kernel as secondary with dual boot patcher. I don't know if this secondary kernel setting was needed or not but I supose so because primary kernel is ktoonsez for GE Roms.

Tks for your help and for this amazing tool.

Enviado do meu GT-I9505G através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hey chanxialong , please could you have a look at supersu 1.99r4, I can't get it to patch no matter what iI do , also if you have time latest alucard aosp 2.2.7l link in my signature , many thanks :)
[Galaxy S 4 i9505 Original Android Development] GRBull:
Automatic I think? Because when I entered the app, it said that primary and kernel on the left sidebar. Then I just tapped on it, thinking that it will st it as primary.

Посланный от GT-I9505 помощью XDA Премиум 4 мобильное приложение
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You've patched the KT kernel with the apk, right? You haven't choosen preset in the app, right? I ask because I had got the same issue with DualBoot Patcher v5.02. I thought it set, but it seems it still exists.

If you do it with apk, after to have selected the KT_kernel.zip, you have to choose in "preset" box jflte/kernel/AOSP/ktoonsez (there where it's written "custom") . And finally patch.

If you do it with PC app, modify its name otherwise it will do it in automatic, rename it kernel.zip for example. Like that, at a moment, you'll have a windows with the same option than apk. You'll put jflte/kernel/AOSP/ktoonsez instead of custom. And finally patch.
[Galaxy S 4 i9505 Original Android Development] remorema:
anyone got their hands on that script to share data/app from the first to secondary rom ?

I found a version of it for i9305 bu seems mount points are diferent.

I think our i9505 uses /dev/block/mmcblk0p29 as data

best regards,

remorema
[Galaxy S 4 i9505 Original Android Development] v00d007:
I'm a bit confused. I can't find the description say something about WHAT has to be done with other os's than android to get all working... The screenshots on the other hand tell me that some things have to be done on a Windows system...

But my most important question is:

After all patching - HOW DO I GET a second rom INSTALLED???
[Galaxy S 4 i9505 Original Android Development] Mussels84:
windows and android can be used to patch an existing rom or kernel.

these are then installed like any other rom or kernel, via your custom recovery.
[Galaxy S 4 i9505 Original Android Development] v00d007:
But how does i.e. cwm know where to install? Is it all stored in the patched rom zip file and works automatically?
[Galaxy S 4 i9505 Original Android Development] Mussels84:
well thats the entire point of the patching, so yes.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Will all the changes be reverted and the 2nd rom be deleted if I let cwm restore a previous made single-rom backup?
[Galaxy S 4 i9505 Original Android Development] remorema:
If you restore a single rom backup. You'll loose second rom. So yes it completly erases everything second rom related including the rom itself

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm downloading it now and will add support for it in the next version :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure, will do :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm glad you like it :D

As far as I know, both TWRP and CWM will continue as if there's nothing wrong. The only way you can tell if it ran out of space and failed is by looking at the logs. As for the camera, that's currently a bug in the dual boot setup. I haven't figured out why that happens yet.

Setting the secondary kernel is done automatically when you flash a patched ROM or kernel. The only time you need to do it is if you have a locked bootloader (AT&T/Verizon) and need to flash loki-doki.
[Galaxy S 4 i9505 Original Android Development] remorema:
I end up switching the ROMs. Sammy as primary and went for CM11 as secondary. And all works fine now.

The most amazing thing with this app is that we can use default unpatched kernels.

In my previous phone(p880) kernels had to be kexec patched for multi boot to work.

Dual boot is way better IMO.

Congrats for your awesome work.

With a little script to share data/app it would be even better but having things separate isn't that bad and has its advantages.

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] Mussels84:
manual patching worked just fine, so its only an auto detect option thats needed really.

oh and they have seperate kernels released now as well - same deal. so an AEL GE kernel option would be great.
[Galaxy S 4 i9505 Original Android Development] remorema:
Can you look at this script and port it to use with i9505.

I would like for it to work with CM11 as secondary.

Its not that hard. I dont do it myself cause Im unsure of the mount points.

Can you please give it a try?

I think first to lines are not needed. We should only need to mount data/app as data/dual/app and the same goes for app-sec

http://xdaforums.com/showthread.php?p=32662356
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
Concerning v4a not working on 4.3.3 GE in /system/dual, I can confirm using ViPER4Android_FX_v2315 is WORKING. V4a made a special warning in the next version:

Note: FX v2.3.2.5 onwards:

1. Fully support x86 platform, but not fully optimised yet. (Using VHS+/Convolver may increase battery usage)

2. Fully support true octa-core devices.

3. Correctly-installed Busybox is required before installing V4A.

If you see V4A installation pop-up loop, its probably due to incomplete root.

Maybe comparing why v2.3.1.5 is working but not v2.3.2.5+ may help you to fix the problem cause I also get the same problem on a Dandroid GE 4.3.3 Rom.
[Galaxy S 4 i9505 Original Android Development] Mussels84:
someone else did complain of root problems actually, that is entirely plausible. for now i'll take that as the cause. (i'm not using that rom, i was merely helping test it out for the devs)
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
:good::good:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
You've a thanks button! ;)
[Galaxy S 4 i9505 Original Android Development] `SBR`:
thx for the update...I'll try with lower version by any chance do you have link to that version.

below are my observation.

if you install GE as primary V4A is working, but only dual is not working with latest version, so it shouldn't be a root problem.

if they have changed something at v4a application it may be a cause, but the latest version is working perfectly in Aosp roms...

kt has added some fixes to GE edition, that I'll try it and see it solve the issue.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For the secondary ROM, you'll want to mount /raw-data/app to /data/app. If want to use the method mentioned in the link you gave, the init script would be:

#!/system/bin/sh
if [ -d "/data/app" ]; then
rmdir /data/app
fi
ln -s /raw-data/app /data/app

I haven't tested it yet, but I'd prefer this method since the method above will fail if you already have something in /data/app:

#!/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

As for /data/app-asec, I wouldn't recommend sharing that. The paid apps there are stored in encrypted containers and I don't believe there's an easy way to share the encryption keys.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hey guys, guess what I just fixed for TouchWiz 4.4 ROMs? :D :D Coming soon to version 6.1/7.0.

EDIT: Video recording is also fixed!
[Galaxy S 4 i9505 Original Android Development] remorema:
Let me guess camera firmware update and a working camera on secondary slot?!? :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hi [MENTION=5617909]dafonehacker[/MENTION], I've fixed the boot loop issue in the next version of the patcher. As for the gapps issue, could you check the space on both /system and /cache? Even though everything is installed to /cache when you use multislots, as the ROM boots, all the optimized dex files are stored in /system. With a gapps package as large as the AOKP one, the optimized dex files could easily take up 300MB. If /system fills up, it is very possible that apps on the primary ROM will disappear or fail to run.
[Galaxy S 4 i9505 Original Android Development] dafonehacker:
Well, I'm not using the dual boot patcher right now, but I think if I remember correctly /system had over 100mb free after I installed the rom. I did find it strange though that the PA gapps worked fine, as I think they are way bigger, and I actually had 4 roms at some moment, with only aokp acting strange with the gapps. I will check it tomorrow when I have some time.

EDIT:

I forgot: I stopped using the patcher for a while because I wanted to try cyanogenmod with f2fs. Will it hurt if I try while on f2fs? Or could that cause additional problems? My data and cache are f2fs and system is ext4. I don't have the time to completely reformat my phone to ext4 right now. If I just patch aokp, the gapps and a custom kernel for f2fs support (in my case KT-SGS4) should it work like it would on ext4 then?

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] remorema:
Regarding space issues I have to say that stock ROM deknoxed and debloated + cm11 with PA gapps micro modular works great. I end up with over 200MB in system partition and all is working flawless.

I'm still looking to test the app share script but I'll leave that for when I have to update secondary ROM and do a clean install.

This tool is freaking awesome and I cannot thank you enough chenxiaolong :)