yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] v00d007:
So, what! Just try and see. You can always go back to the backup (you made before). I did that already on some unsupported devices.
[Galaxy S 4 i9505 Original Android Development] gaww:
You have about 2.84 gb in primary/secondary system and only 2.13 gb for multiROMs in cache.

That said, your setup should work but the stock ROM needs to be in primary, as it would not fit elsewhere. Imperium should fit in as a multiROM - I had it installed that way with a stock based TW in primary.
[Galaxy S 4 i9505 Original Android Development] MaxMusaab:
I would like to know what does it mean that the app patches a custom kernel? Does that mean what i think it does and by running dualboot we are no longer on the stock kernel or does it just adjust some stuff? Also, what would happen if i wanted to flash a custom kernel, would that mess with the dualboot? Or do i just patch it as well after i flash it? Lastly, app sharing does something with ramdisk? What does that mean, and is it reversible? Oh and is there a way to completely remove dualboot patcher and all signs of it? Do i just delete the rom and multi boot files and proceed to just uninstall it?
[Galaxy S 4 i9505 Original Android Development] Phk:
Hello all,

Can someone tell me where are the partitions from Secondary rom stored? I mean, how does this dualboot handles the system data app partitions, and changes between them?

Thanks
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Hey [MENTION=4277844]chenxiaolong[/MENTION] me again from the S6 Edge. Pretty much everyone is unified here so could you add in G920T/F and G925F. The patcher won't work until I edit the build.prop if I'm on those roms lol
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1433.g4a4633f :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, for some reason, it can't open the recovery image. Could you send me a link to the exact recovery you flashed? I think this should be an easy fix.

[W] Failed to open recovery ramdisk: Unrecognized archive format
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That really depends. If the developer of the ROM is smart and uses the "/dev/block/platform/.../by-name/..." paths in the updater-script, then there's a very little chance of anything bad happening. But if it accesses the partitions by number ("/dev/block/mmcblk0p##"), then it could really screw up the device.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure :) This is an exynos device right? Could you run the following command in the Terminal Emulator app (or adb) and upload the partitions.txt file?

su -c 'ls -lR /dev/block' > /sdcard/partitions.txt
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure! Could you give me the codenames you want me to add? Right now, the patcher recognizes "zerolte", "zeroltetmo", and "zeroltexx".

Btw, do international ROMs work on the T-Mobile S6 Edge? If so, that's *way* better than the Note 4 lol
[Galaxy S 4 i9505 Original Android Development] peppe130:
Here you are :D https://app.box.com/s/5m54n24as124n8jajl743a8hhcr6vlad

The model is: SM-N7505
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Wow, the partition layout is actually the same as the Exynos Note 4 and the Galaxy Tab S 8.4 (Wifi). Who would've thought? ;)

A new snapshot with support for the Note 3 Neo will be available in a little bit.

EDIT: 8.0.0.r1437.gb11bd61
[Galaxy S 4 i9505 Original Android Development] virulentt:
zeroflte and zerofltetmo are the ones from the regular s6. Also, i think they works with a unified kernel, otherwise it bootloops. But still if they managed to make the unification it's pretty similar. It's unified for all variants for both edge-non-edge. See for yourself : http://xdaforums.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development
[Galaxy S 4 i9505 Original Android Development] silvercat:
Since there is no official twrp for s6 edge international version we had to flash the recovery recompiled by few developers.. Now I updated the recovery to newer version everything started to work.. Thanks anyways :)
[Galaxy S 4 i9505 Original Android Development] royredman:
Does anyone know if this works for the nexus 6?
[Galaxy S 4 i9505 Original Android Development] v00d007:
btw, mr chen: is ist possible to patch a kitkat rom, i.e. cm11, to use ART instead of dalvik directly when installing? I wanted to get the latest cm11 nightly to replace the cm12.1 rom on secondary slot. ??
[Galaxy S 4 i9505 Original Android Development] peppe130:
Thank you very much Chen :)
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I am currently using this ROM i9505XXUGNK2_Repack_XEF_@EDZAMBER which is a KK 4.4.2. I would like to use this as my PRIMARY ROM and IMPERIUM KK 4.4.2 as my SECONDARY ROM. Is there a need to wipe date first before proceeding with the dual boot process? Sorry I really don't get it. Should I also patch the ROM which I would like to use as PRIMARY or just the ROM that I will be using as my SECONDARY?

I was able to install the Imperium Lollipop version as Secondary but I could not boot into it. It shows Unknown status.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
If you have a kernel for Imperium (stock) or other compatible kernel for Imperium, patch it as secondary (dual) and flash, should boot.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi,

Thanks for great app.

Could you add memory of last selection for fields in "Patch Zip File"?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Does the app check what device the running ROM is for and what device the ROM I want to switch to is for?

I am asking because I am running a ROM ported from the S6 as my primary now and just can't switch ROM's from the app anymore in that ROM, it always gives a popup with "FAILED to switch ROM".
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
Hi [MENTION=4277844]chenxiaolong[/MENTION] can you please add support for the note 3 Exynos version it would be great if you can do that. Thanks in advance. There is so many of them want to have your dual boot mod. It's a humble request. We know you are busy but please if you can add support it would be much appreciated.
[Galaxy S 4 i9505 Original Android Development] Sanesh Munde:
Thank you very much for the patcher app.[emoji4] [emoji4]

Now my device is officially supported for dualboot. [emoji41] [emoji41]
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

My search here found several reports of failure installing a patched xposed framework to i.e. dual rom (error executing...). Any solution for that?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes it does. If your build.prop file shows the device as the S6, you'll need to add the following to your build.prop file (replacing jfltetmo with the device you have):

ro.patcher.device=jfltetmo
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It is technically possible, but I'd like to keep patched ROMs free of any customizations. If you want to downgrade from CM12.1 to CM11, you'll need to wipe that ROM first because the data is not compatible.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done :) 8.0.0.r1439.g2cffb82

EDIT: Crap, actually not done. Power went out in the house. Need to go restart my build server.

EDIT2: Okay, now it's building.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] great to hear and yes with the s6 and s6 edge all roms are interchangeable lol. Also I'll have to get back to you later on today with the code names. At work for another 2. Hours
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Which zip are you trying to flash? The latest official build "xposed-v66-sdk21-arm.zip" is working for me.
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
thanks a lot bro we all are really thankful to you. please check this and suggest if any thing needed. again thanks a lot

http://xdaforums.com/galaxy-note-3/themes-apps/guide-dual-boot-note-3-t3091764

also some roms are not supported what we have to do. we cant use the dual boot patcher app to switch between rom n cant set kernel in some roms.
[Galaxy S 4 i9505 Original Android Development] Blackiisky:
When you have the time can you add support for the Verizon Note 4, Sm-N910V trltevzw. It works fine for the developer editions. Thank you
[Galaxy S 4 i9505 Original Android Development] gaww:
Which type of ROM are you patching - AOSP, CM, TW?.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done. 8.0.0.r1440.gd0d9081
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll take a look after work today. Most of the time, if switching ROMs/setting the kernel doesn't work, it's because the ro.product.device value in build.prop is not in this list: https://github.com/chenxiaolong/Dua...2edf26db0a1bfa7/libmbp/patcherconfig.cpp#L471
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
thanks a lot for the replay, and i understand why its not supported. is their any thing we can do to get it working. if i change the build prop then it could make problems in the rom like updating the apps and some apps may not work etc. so......

and one more thing why are you not changing the name of the project from Dual Boot to Multi Boot coz it can do that now.

thanks again.:good::good:
[Galaxy S 4 i9505 Original Android Development] todivefor:
Support Galaxy S6 Sprint

[MENTION=4277844]chenxiaolong[/MENTION] could you please add support for Galaxy S6 Sprint. FYI, Sprint S6 and S6 Edge have same partition layout, but significantly different from S6/Edge TMO. I am not ready to test yet, but hopefully soon.

Code name: zerofltespr
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes it's that one. But I'm using Philz Touch, not TWRP.

---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------

I tried to flash the xposed bridge to a cm12.1 rom which runs as secondary.

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

Do you mean to wipe the 1st rom?? The 2nd one's data I wiped of course.

EDIT: I meant I did a full wipe of the 2nd rom of course...
[Galaxy S 4 i9505 Original Android Development] tomaasz:
[MENTION=4277844]chenxiaolong[/MENTION] could you please you add memory of last selection for fields in "Patch Zip File"?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
He did not mean "wipe that first ROM" but "first, wipe that ROM, then" install cm11 :D
[Galaxy S 4 i9505 Original Android Development] gaww:
If 12.1 is 5.1, don't think the SDK zip works with it yet.
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
Hello all, can someone help me. this is the only active thread i could find with support for Dual Boot Patcher.

I was dual booting fine. Offical Tmobile touchwiz on rom 1 and CM on Rom 2. But then I decided to use cyangdelta to apply an update to CM. Anyway the update to CM was fine. I had no errors and it booted fine. What I didn't try was to boot into ROM 1. I did that today and found that it won't boot into ROM 1. It just keeps booting into ROM 2, I'm not sure what I did but I like fix this so I can boot back into the Stock Tmobile Rom
[Galaxy S 4 i9505 Original Android Development] Phk:
[MENTION=4277844]chenxiaolong[/MENTION] sorry to ask again, but where is the secondrom stored and how to backup it or delete it?

Thanks!
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I believe you will need to patch whatever kernel is used for the secondary rom (whichever slot) it will then boot into cm.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry, I don't quite understand what you mean? If the ro.product.device value is "hlte..." and it's not currently in the patcher's list, I can add it. If the ro.product.device value is another device (like in a ported ROM), then you can add "ro.patcher.device=hlte" to the bottom of build.prop.

The only reason I haven't renamed the project yet is because I'm lazy :D There are lots of places where I need to change the strings.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Wow, that's new even for Samsung. The Note 4 had different partitions tables across variants, but it only affected the "hidden" partition.

I've added support for zerofltespr (and zeroltespr) in 8.0.0.r1442.gf1d964b. Feel free to test whenever you're ready.

https://github.com/chenxiaolong/DualBootPatcher/commit/c1b4cb4613fbbb4b3f14aca7a5809041c07a3e8f
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The secondary ROM is stored in:

System: /system/multiboot/dual

Cache: /cache/multiboot/dual

Data: /data/multiboot/dual

Multiboot files (kernel, configs, icon, etc.): /sdcard/MultiBoot/dual

By deleting those 4 directories, the ROM will be completely gone. Alternatively, you can can click the menu button for the ROM in the app and choose "Wipe ROM".
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
After running CyanDelta, did you patch the new zip that it created?

The first thing I would try is to boot into TWRP, tap Install -> Images (bottom right corner) -> goto /sdcard/MultiBoot/primary -> flash boot.img. If that doesn't work, you may need to flash a kernel for the primary ROM again.
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
I did patch the new zip that was created, it had dual at the back of it. I also did flash the boot.IMG but it did not work. It stills boot to cm even though it says it switched ROMs.

Where would I get the kernel for primary ROM? Would any version of the stock kernel work or would it have to be a custom one?
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
thanks a lot for the replay. and thanks for the help.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yep, I already thought that was a misunderstanding...

So, [MENTION=4277844]chenxiaolong[/MENTION] there's still that problem: the cm11 installs but then 1st boot never ends. Also flashed a patched kernel afterwards, same result.
[Galaxy S 4 i9505 Original Android Development] virulentt:
I tried your last snapshot and it seems like you've changed the Galaxy s6 Edge to be both S6 and S6 edge. Unfortunately, the model has a different number. zerolte is zeroflte. You may have forgotten the F :D thanks for your support again <3
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
I can boot into the secondary ROM already. My problem was that I couldn't boot into the default Primary ROM (which is the stock Official Rom).

But after some digging around it looks like I manage to fix the problem. I downloaded the same rom version that I had installed on the primary. Extract the boot.img from it, copied it over to my SD card, booted into tWRP, choose the boot.img and flashed it. After boot up it went into my primary. I then tried switching to the secondary and then back to the primary. All worked.

Only thing is in the primary it's tell me that I need to update the RAMDISk as it doesn't have MBTOOLS. I'm wondering if this is safe to do
[Galaxy S 4 i9505 Original Android Development] peppe130:
[MENTION=4277844]chenxiaolong[/MENTION] The Patcher doesn't work on Note 3 Neo.. Kernel is not set properly. The flash ends successfully but the ROM doesn't boot (it get in softbrick and reboot itself in recovery mode).. I flashed the ROM in the data slot. DualBootUtilities can see the ROM in the data slot but it can't wipe the ROM (I had to remove it manually).. Any fix for this? :)
[Galaxy S 4 i9505 Original Android Development] v00d007:
But you are aware of that this is still a S4 thread, are you?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I always update the RAMDISK, but then I share apps. I believe you only need to update the RAMDISK if you intend to share apps.
[Galaxy S 4 i9505 Original Android Development] peppe130:
Yes I am.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Pretty much any stock kernel should work. I would definitely use a stock kernel unless you wanted a custom kernel.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, would renaming to "zero" be better? I'd like to keep them combined since I heard that the partition layouts are the same for the S6 and S6 Edge (except Sprint versions) :D
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] I was just about to ask if you could add in zeroflte and zerofltetmo
[Galaxy S 4 i9505 Original Android Development] virulentt:
I mean the name is correct, the thing is that when i patch a rom, it wouldn't install because it only looks for zerolte, zeroltexx and zeroltetmo. You should add zeroflte, zerofltetmo and zerofltebmc
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Cool, that's actually good. Reboot into recovery is actually something mbtool does when it fails to mount the partitions. When it autoreboots into recovery, could you pull /proc/last_kmsg with adb or flash the attached zip?

Thanks for the info regarding DualBootUtilities! I'll take a look and see if I can find out what's up :)

EDIT: Which ROM were you flashing?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahhh, I'm a dumbass. Will fix right now :)

EDIT: 8.0.0.r1450.g56018f5
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
[MENTION=4277844]chenxiaolong[/MENTION] so I used the boot.IMG file from the T-Mobile ROM. Flashed it and that worked.

I do have a question about app sharing. Do both ROMs have to have the same app installed? Or can one rom have the app installed and just share it enabling the other ROM to see it.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Thanks going to test now. Do I have to repatch my rom
[Galaxy S 4 i9505 Original Android Development] -Mr. X-:
I'd like to give this a go on my Galaxy S6, could you please add the Canadian variant of it "zerofltebmc" it has the same partition layout of the "zeroflte".
[Galaxy S 4 i9505 Original Android Development] peppe130:
Sure I can! But since the device is not mine, I don't know when I can provide you the log :) Thanks in advance!
[Galaxy S 4 i9505 Original Android Development] sronweb:
yes, for the individual apps you should install on both rom first then you can share them. if the app is not installed you will not see in the list. I don't recommend global share except when you don't mix TW and AOSP roms.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! 8.0.0.r1453.g5e00e08 will be coming down the pipes soon.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Thanks. Is it true that individual sharing requires installation of app twice, on both roms?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] virulentt:
Seems like patching a rom works now, installed on my canadian variant but refuses to boot. it returns to TWRP.
[Galaxy S 4 i9505 Original Android Development] -Mr. X-:
Thanks i'll give it a shot. I manually changed my device to zeroflte last night so i could try anyhow. I cant seem to get a second rom to boot. If i select it in the android app and reboot it just boots back to primary. If i try to boot it right after flashing in TWRP, it just boot loops and i have to flash an unpatched kernel zip back and then primary boots.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Just saying its worked for me.multiple.times on a g925t
[Galaxy S 4 i9505 Original Android Development] nutpants:
First off let me say thank you for this project.

I was running wamanlite 442 on a Canadian s4 as primary and liquid smooth 3.2 444 as my secondary. I installed both months ago and both were working great.(patched with an early stable)

I wanted a clean fresh start on my s4 so I wiped everything except the external SD and reinstalled with a new snapshot (1433 I think or close to that).

Now no matter what I do I boot loop after flashing liquid smooth as secondary.I have started from scratch with everything.

I have patched both ROMs on the s4 and everything looks good there. I have wiped everything many times. I'm using twrp 2840 or 2860. I patched the wamanlite touchwiz as primary, I patched liquid smooth as secondary.

I wipe everything ,flash the first rom, boot first ROM set Kernal, flash second ROM.. Hang at splash screen for over ten minutes every time.

Tried flashing second ROM from patcher and setting kernal.. Hangs the same..

Any one else still using liquid smooth 3.2 444?

Am I missing something?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That is correct. There's not much I can do to avoid that for app data sharing to work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That means that the partitions failed to mount for some reason. Could you flash the attached zip when it auto reboots into TWRP? It will save some logs into /sdcard/logs/ on the internal storage. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, could you give be a link to the ROM you're trying to flash? I don't have an S6 or S6 Edge, but I can check to see if there are any peculiarities in the ROM.

By the way, you can always switch ROMs by flashing the DualBootUtilities zip from https://snapshots.noobdev.io/ (inside the blue box).
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
[MENTION=4277844]chenxiaolong[/MENTION]

---------- Post added at 07:33 PM ---------- Previous post was at 07:29 PM ----------

[/COLOR [MENTION=4277844]chenxiaolong[/MENTION] - thanks for clearing up the info about the app sharing. Since you have to install the app on ROMs before sharing can happen, what's the advantage of app sharing? It doesn't seem like its going to save space or anything.
[Galaxy S 4 i9505 Original Android Development] -Mr. X-:
I tried the dual boot utility as well. this is the rom i was trying to flash. http://xdaforums.com/galaxy-s6/development/rom-xtrestolite-deodexed-mod-edition-1-0-t3094423 it seems to be placeing the rom properly in the /system i can brows to it and it looks proper file hierarchy wise.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
https://snapshots.noobdev.io and https://jenkins.noobdev.io are temporarily going down for server OS updates.

EDIT: Fully updated and patched with latest security updates :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
I'm about to get this going and take these logs so we can find out why the S6 won't boot :D
[Galaxy S 4 i9505 Original Android Development] liquidguru:
Would it be possible to add support for the Note 4 N910H, tre3g. It is exactly the same hardware as the N910C, trelte. Only the modem is different, the ROMs and kernels are interchangeable between both models. When I run the app on my phone it tells me it could not determine the boot partition because the device's codename 'tre3g' is not recognised.

Thank you
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Hey I've some issues when I try to install a TW rom as secondary (dual). I patched it with the latest app before. I got this issue: "failed to run real update-binary"

I've found some posts with the same issue, but no answer how to solve it.

Any idea?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The true reason it failed is due to the "symlinks: some symlinks failed" error above it. Could you send me the MultiBoot.log file it created? I'm guessing it ran out of space on /system when installing.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! tre3g should now work in 8.0.0.r1457.gf11fc8c.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Once you have the app installed in both ROMs and you enable sharing, the apk files will be changed into hard links, effectively using the space of one copy of the apk. This will be especially noticeable if you enable sharing for a few large apps. The free space will go down when you first install them, but will shoot back up again after you enable sharing and reboot.