yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] gaww:
You have to unpair and repair the same device only every time you switch ROMs, so don't understand the factory reset need.

---------- Post added at 03:06 PM ---------- Previous post was at 02:59 PM ----------

If you wiped and reinstalled your ROMs as you indicated you have to do, you could restore only data with TWRP first, and before rebooting, wipe all other data partitions for Primary and Mutislots with the patcher utilities zip. That would leave you with only secondary data. Then flash secondary and other ROMs.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Will try this, thanks!
[Galaxy S 4 i9505 Original Android Development] v00d007:
The backup&restore v1.1c from [MENTION=3145598]rlorange[/MENTION] does the job you want right now in presence. I'm using it quite often, it works pretty well.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Well, i tried to but it fails installing. The app tries to install 'rlbbox' but says this is not succeeded and closes afterwards. :(
[Galaxy S 4 i9505 Original Android Development] v00d007:
hmm... sounds like it doesnt have root rights to me...(?) checked supersu?
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
sure, root is not the problem. everything is granted
[Galaxy S 4 i9505 Original Android Development] v00d007:
The only thing else I know that prevents apps from installing s'thing to sd card is the system reserving some space on data partition. TW i.e. stops downloads sometimes when going under the 1Gb mark. So maybe check how much space you've got left on data partition/sdcard.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry for being away for a while again. I was out of town for my birthday and had lots of stuff to do for school and work when I came back :) I should have some time tonight to look through the last few pages of this thread.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Space isn't the problem either. I've sent a PM to rlorange. Wait and see i guess.

wb chenxiaolong!

BTW: if a backup/restore feature is implemented wouldn't it be better that everything is stored /data/media/0? AFAIK that way the secondary roms are not backed up anymore by TWRP while taking a backup of the primary rom. As i understand now a nandroid backup of a primary rom can get seriously big when the user has, let's say, 3 or 4 secondary roms, or am i wrong? Just a thought, nothing more :)
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=803530]Droidphilev[/MENTION]

Did you try to install it manually?

put the apk to data/app

in a folder named

"com.gmail.rlorange.dualbkup-1"

name the apk base.apk

perrmissions 755 folder, 644 for apk

put the rlbbox.tar to sdcard

reboot
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi,

The app itself installed fine. It was rlbbox that refused to install. Will try to put yours manually on the device and report back. Thanks!

EDIT: it seems that the app tries to extract the .tar to /data/local/rlbbox and it's that step that seems to fail
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, as the files in that folder are all linked to busybox maybe your busybox is somehow missing or corrupted..?
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
No idea. Will install busybox (again)

EDIT: can this backup app also work in secondary roms or does it have to be in primary rom?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
One of [MENTION=3145598]rlorange[/MENTION] later backup apps worked for secondary roms....can't remember which ver#.
[Galaxy S 4 i9505 Original Android Development] v00d007:
No, as far as I know it works with the primary rom only, cause it can't copy anything from active systems parts.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
ok, thanks for the nfo guys!
[Galaxy S 4 i9505 Original Android Development] rolexconfuse:
Welcome back chenxiaolong, I hate to blast you with some more problems but here I am doing it lol.

I have my primary OS and my secondary OS (CM 12.1) running with no problems. Now there is a new update for the primary from Samsung for the phone but it's a full version jump (50.2 to 5.1.1)

When I was on 1 OS (kit Kat) and went to 5.0.2 I went through ODIN so I had root afterwards. But now since I have 2 OS on the phone how do I do this? Should I patch the new offical rom from Tmobile and then load it through ODIN to install?
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Just to make sure i don't screw up anything and because i couldn't find anything about it in the topic here. So, my question is: Does the 'Dual Boot Patcher' supports the 'Samsung Galaxy S6 edge+' yet?
[Galaxy S 4 i9505 Original Android Development] Edde3d:
That version is in the drop down for phone selection so I believe it is. The S6 and edge

Kickin it on my VS985
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Thanks for the fast answer :good:.

Remember that the S6 edge+ isn't the exact same phone as the S6 edge as the S6 edge+ have 1 GB more RAM than the S6 edge & S6 have. So that alone might need some code changes i believe (correct me if i'm wrong).
[Galaxy S 4 i9505 Original Android Development] Edde3d:
Where you go to patch file from the left hand side. But sadly it says s6 reg. So it's not the plus

Kickin it on my VS985
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Ok :).

Yeah, i figured out where the list of supported devices was, so i removed that question in my earlier post.

So as for the support for the S6 edge+, i think we need a confirmation from the op or the app developer if it's supported or not. Or if it will be supported later if it's not supported yet.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Can you add support for the d2can i747m Canadian s3 variant? Should be the same partition table as d2att.

Thank you

You now support every device I own except the note2 i317m
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
It has already been added : https://github.com/chenxiaolong/DualBootPatcher/commit/0086496a3aed143541548be2a1d2ce80879d04f9
[Galaxy S 4 i9505 Original Android Development] nutpants:
Strange, I'll check what version I was running (I think 1751 or 52)

But I got the error d2can not recognized when I was setting the kernal for the secondary Rom (everything worked fine with the primary att Rom I had in)

I'll report back with the results from the newest version tomorrow

Have you ever thought of adding your fantastic app to fdroid?
[Galaxy S 4 i9505 Original Android Development] bchiu:
Can't see the patched ROM?

Hi All,

I am using |ROM|★GOLDENEYE★|►XXUHOD7 LOLLiPOP TW◄|5.1.15|★ on my Canadian S4 I337M.

3.4.0 S4 AEL KERNEL 4.3

I installed the Dualboot. Then I go to the in-app patcher, and patched the same ROM |ROM|★GOLDENEYE★|►XXUHOD7 LOLLiPOP TW◄|5.1.15|★ .zip

then I try to add the zip to the ROMs. After everything completed, I still don't see an secondary ROM from the ROMs sections. It only has the primary ROM.

Any idea?

THANKS.
[Galaxy S 4 i9505 Original Android Development] bchiu:
Any idea would help! Tia
[Galaxy S 4 i9505 Original Android Development] todivefor:
Where are you patching second TW tom to (secondary/dual, slot-*, data). Having 2 TW roms normally does not work unless patching one to data or sdcard (no experience with sdcard).

I am assuming that when you say "then I try to add the zip to the ROMs" you mean you used in app flasher to flash rom? If that is the case, try flashing through recovery.
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
guys but I can put a rom with 4.2.2 and a rom with 4.3?:rolleyes::confused:
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
yes, I had a stock touchwiz 4.2.2 and a 4.3 GE ROM
[Galaxy S 4 i9505 Original Android Development] ad346:
ive posted this before, but no reply yet. Im running AICP which is a 4.3.1 AOSP based Rom, and i wanna also run Foxhound rom.

Im using a Mac and i havent been able to get past the patching part, ive pasted below the error message i get.

Can someone with enough experience kindly inbox me the steps to do so? sorry im a noob :p

When using a mac, i cant seem to patch the file... ive pasted below what i type into the terminal and what it gives me back...

Macintosh:~ a***$ ./patch-FoxHound_Diamond_Dogs_3.0_By_Snakes_GT-I9505.sh /path/to/FoxHound_Diamond_Dogs_3.0_By_Snakes_GT-I9505.zip

-bash: ./patch-FoxHound_Diamond_Dogs_3.0_By_Snakes_GT-I9505.sh: No such file or directory
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
IceColdJelly for me doesn t go..installation aborted...:(why?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Basically, to put it short, I'll probably put the source code and file(s) on Github. Then I assume chenxiaolong will incorporate that into a new version of the patcher or something. I'm honestly a little confused myself, as it isn't completely clear.

If not, I might dedicate an XDA thread to just uploads of patched ROMs and kernels while leaving credit URLs to the developers.

Anyways, my best guess. Chenxiaolong told me that he'll be releasing version 2.0 of his patcher script soon that automatically patches the ramdisk and leaves less work for us to manually patch these ROMs. I'll probably start when he releases it. Anyways, yeah. Just some thoughts so far!

---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------

Yes you can. Your game data, downloads, saves, etc will be available to both ROMs, but as far as your /system partition and apps, they are not.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
What's the best way to go back to just 1 Rom ?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I think you must to make the wipe cache, wipe dalvik cache and wipe factory reset, format system, and install the rom that you want.
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
I'm a little confused on the manual patching thing

Hey I am not sure about the manually patching zip files thing. You told us to replace code at certain areas, and I think it would be easier to understand if it was more specific. Just for some understanding, which lines would I replace with the dualboot.sh run program code?

Here is some source for the Omega v13 ROM:

This is the updater-script file:

http://pastebin.com/fMZSAdXW

Where would I replace code with [MENTION=4277844]chenxiaolong[/MENTION] ?
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
QUOTE]

Bro...please use paste bin lol
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've only used a Mac for about 5 minutes at an Apple store, so this might now be 100% correct. What you want to do is change to directory of the patcher first. In the terminal, type in:

cd

then navigate to the patcher folder and drag the little folder icon in Finder into the terminal

Then type in

./patch-file.sh

and drag the file you want to patch into the terminal.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Did you download the jfltexx version? (or whichever one is for your device?) The updater-script checks to make sure you're installing on the right device.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here is the comparison between the original file and the modified one: http://www.diffchecker.com/1r00y8ul

A ROM typically deals with the system, cache, and userdata partitions, which are mounted at /system, /cache, and /data, respectively. With a device where the partitions can't be changed, like the Galaxy S4, the idea is to install the second ROM into a folder within the first ROM. If you use a root file explorer a take a look at those partitions, you'll see that the second ROM is actually installed in:

/system/dual

/cache/dual

/data/dual

The updater-script needs to be modified to install to those locations. That's the reason I have a dualboot.sh script. If you want to install some files into /system, what it does is mount the "real" system partition at /raw-system and then mount the dual boot folder to /system. So what you have is:

System partition on internal storage -> /raw-system

Dual boot folder /raw-system/dual -> /system

The part where I talk about replacing code is where that mounting step happens. You first look for the lines which mount the partitions normally. For example, Omega has this:

mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");

Which means "mount the 16th partition on internal MMC storage 0 to /system". You replace that with the dual boot equivalent, which is

run_program("/tmp/dualboot.sh", "mount-system", "ext4", "/dev/block/mmcblk0p16");

or you can use the line below, which means "partition by the name 'system'". I prefer this since it's clearer than saying 16th partition.

run_program("/tmp/dualboot.sh", "mount-system", "ext4", "/dev/block/platform/msm_sdcc.1/by-name/system");

Lots of ROMs have some sort of wiping steps built in (such as the wiping of cache). From the dual boot layout I mentioned above, if you want to wipe the secondary cache, for example, just delete the dual-boot cache folder /raw-cache/dual. In other words, replace all of the wiping code in the updater-script with something simple like:

delete_recursive("/raw-cache/dual");

Of course, since the partitions are mounted specially, they need to be unmounted in a special way. The dualboot.sh script also handles this, so just change the unmount lines:

unmount("/system");

to the dual-boot equivalent

run_program("/tmp/dualboot.sh", "unmount-system");

The last thing you need to do is to set the secondary kernel. This copies the kernel to /raw-system/dual-kernels so that the dual boot switcher app can switch to the secondary ROM. If you omit this line and switch to the primary ROM, the primary kernel will be installed, overwriting the secondary kernel. When you want to switch back to the secondary ROM, the app won't be able to find the kernel.

This line actually needs to go before the unmount line for /system because it copies files to that partition:

run_program("/tmp/dualboot.sh", "set-secondary-kernel");

I hope this makes things a little clearer :D
[Galaxy S 4 i9505 Original Android Development] rlorange:
@ chenxiaolong pmed you mate about python for Android :)
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
This actually makes much better sense now! Thanks for your time!
[Galaxy S 4 i9505 Original Android Development] ad346:
wow you're amazing. thank you so much man, going to try this the moment i get home from work... :cyclops:
[Galaxy S 4 i9505 Original Android Development] Tinasintunes:
Just wanted to say.... I LOVE THIS!!!! I'm using the script to share apps which is just great!
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Anyone want to manually patch a Rom for me I am so lost?
[Galaxy S 4 i9505 Original Android Development] bibymon:
I have patched PAC latest nightly(vertigo) and flashed.. Everything went fine and i booted in the secondary rom.. Then i switched to primary.. After that I'm unable to go to secondary.. It will boot only in primary.. I have tried flashing switch to secondary zip from the utilities.. Still booting in the primary.. Any ideas??
[Galaxy S 4 i9505 Original Android Development] _Sofos_:
Have you set the kernel for the secondary Rom once you rebooted into it?

Sent from my S4 using TT2.
[Galaxy S 4 i9505 Original Android Development] bibymon:
Thanks.. I have read few pages back n saw this :) now i set the kernel as the secondary's kernel & it's switching fine now :)
[Galaxy S 4 i9505 Original Android Development] omnifarious:
When I try to install a secondary ROM on my d2xar it is identified as d2lte for some reason and then the binary fails. I don't have the s3 in my hand as I am at work but later today I'll try to flash and get logs afterwards. Maybe simply adding d2lte to the list will fix this issue?
[Galaxy S 4 i9505 Original Android Development] monkteo:
THX all OK
[Galaxy S 4 i9505 Original Android Development] gaww:
If I am reading the above correctly, i don't know why you would want to flash exact same TW ROM as secondary.

Regardless, there is normally not enough room to flash two TW ROMs in the combined primary/secondary partition (unless flashing to SD Card opens up more space).

If you wanted to install it to secondary and later add a smaller AOSP ROM as primary, you could wipe the system and see if just reflashing the secondary works - then flash a new primary.
[Galaxy S 4 i9505 Original Android Development] nutpants:
Yep, it was my own bone head move..

I installed the newest to the primary

And when I booted to the secondary I installed an older ver.

All the time thinking in my head I had triple check it was the new version...

It's working fine..

I've had this issue many times my s3 is Canadian but many of the roms are the att that I flash,my s4 flashes can, att, and 9505 roms, my note 2 flashes can and att and I think other roms. My mega is Canadian, but the roms are all international 9205 roms (as there only minor support for any others) my galaxy s is running a hacked international and my s5 is running a international or a north American Rom.

And with each different Rom it identifies differently.

It's why I love this dual booter, I can run my favorite oem and aosp Rom

---------- Post added at 08:47 AM ---------- Previous post was at 08:37 AM ----------

When you say you added it you mean you flashed either in the app or from recovery right?

Any error messages ?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4891276]monkteo[/MENTION], I am having the same enjoyment as you....just thought I'd share.......
[Galaxy S 4 i9505 Original Android Development] bchiu:
I was trying to test out the dual boot and the only ROM file I got was that one so I try to flash it to the secondary. Yes I mean I flash the ROM when I said I added the ROM. I tried the in app flasher it only took like 10 sec. It did says ROM created with aroma can only be flashed via recovery. So I try flashing it in recovery as I was told. Then flashing proceed went okay. However when I tried to boot my phone after the flash it rebooted at the Samsung logo and booted back into recovery. I had to restore my boot partition in order to bring my phone back to life. Since you said the secondary won't fit. So I tried patching the ROM zip file into ext SD card location. I went into recovery and flash it there. Same thing happens. My phone reboots at the Samsung logo. So u restored the boot partition again to fix my phone. Now when I open up the dual boot app I can see secondary and the ext SD card ROM. But when I tried to switch it them it says failed to switch to ROM.

Please help. Thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Marshmallow can now boot on 8.0.0.r1758.g76e040f (woot!)

Still have some issues to sort out though. Switching ROMs and setting the kernel works. Detecting the current ROM and performing a ramdisk update currently do not work due to SELinux changes (which should be easily fixed when I get a few hours of time with nothing but my laptop and my brother's Nexus 5 :p).

EDIT: This is without root of course, since that requires editing the SELinux policy on Android 6.0 (or a custom kernel).
[Galaxy S 4 i9505 Original Android Development] royredman:
Awesome job man. Really appreciate your hard work! I'm not trying to bug you but did you get my message about updating the ramdisk and installing a second ROM doesn't seem to work on the nexus 6? Sorry to bug you about it, but I'm super excited to get back into the dual boot goodness again.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am trying to run dualboot on my Nexus 7. I have cm based rom as primary (optipop_grouper-ota-2015-06-25). This is an AOSP rom with data and cache F2FS and system ext4. I installed Twisted-grouper-build.2.0-20150926 as data-slot. This is similar to the primary, AOSP. My data-slot rom booted OK, but seemed a little slow. I tried to share my apps as I allowed all my apps from primary to be restored to data-slot. The share all button was selectable from data-slot, but grayed out in primary. In any event sharing all did not work. I tried sharing individual apps and data, but they always acted as independent. I ran into some problems, so restored a backup and am back to primary only.

I am going to try again, but have some questions before starting over. Since primary is EXT4-system and F2FS-data and cache, this could cause problems. If I DB the second rom as secondary/dual, system in the secondary rom will go to system and therefore both will be EXT4 as I want. Unfortunately, I don't think there is enough room (format of zip is system.new.dat and 360MB and I have 207MB free). If I patch to data-slot, system will go to data, which is F2FS, and therefore system of data-slot rom will be F2FS. Is this going to cause me a problem? Options?
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, it's nice that youre back on stage ;)

Could we please stay a bit longer with serious problems with cm12.1, as there is still the huge >30s boot lag when setting it up as secondary? We already talked about that. Do you have any news on that problem? It really kills my nerves atm because hot booting isn't reliable for some apps with latest cm12.1 builds.
[Galaxy S 4 i9505 Original Android Development] gaww:
Can you see the primary in the app? Also, when you boot up, are you in the ext SD location now, and which ROM did you try to switch to?
[Galaxy S 4 i9505 Original Android Development] salas_27:
Hi, welcome back.

Well, since you are back I want to tell you something: I was trying to dual-boot with the newest patchers and it was impossible to make it work. But when I used the version from may 5th 2015 it worked. The difference between those is that the old one just patch the zips and don't set the roms in a partition.

My device is a LG g3 d850.
[Galaxy S 4 i9505 Original Android Development] Zehlek:
I get this error
[Galaxy S 4 i9505 Original Android Development] bchiu:
I can see the primary in the app. I was trying to switch to ext SD
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the GetLogs zip from https://snapshots.noobdev.io/ when it auto-reboots into recovery and send me the file it creates in /sdcard/logs/?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I don't use any bluetooth devices, so I'm not too sure, but doesn't Titanium Backup have the ability to backup and restore Bluetooth pairings? Could you back it up in one ROM and restore it in another?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's nothing I can do about t the 30 second delay right now. Like I said last time, the multiboot code already stopped running and exited 10 seconds into the boot process. It's CM that's hanging for the remaining time. This bug only affects the Galaxy S4 (as far as I know) and I'm not knowledged enough to debug weird issues like this. :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You ran out of space on /system. You're ROM simply won't fit in the secondary slot. Try installing to a data-slot.

[W] /raw/system/multiboot/dual/system/xbin: Failed to create directory: No space left on device
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you flash the GetLogs zip from https://snapshots.noobdev.io/ when it takes you back to recovery and send me the file it creates in /sdcard/logs/? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Once backup and restore is implemented, the backups will be stored in /sdcard/MultiBoot (most likely). It will also include the ability to backup the primary ROM to avoid the large nandroid issue :) I can't really put the ROMs themselves in /data/media/0 though because Android changes the SELinux labels on all of the files in there.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If CM12.1 was installed to the secondary (dual) slot and you flashed the official ROM with Odin, then CM12.1 is gone. The data should still be there though, so repatching and reflashing CM should get things working again :)