yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
What should I do if I want to make a backup of the primary rom first? It seems the ordinary recovery will backup both roms, and [MENTION=3145598]rlorange[/MENTION]'s app will only backup second rom.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Sorry, I don't know of a way to backup primary other than normal recovery.
[Galaxy S 4 i9505 Original Android Development] Mussels84:
Long time no see, thread. I thought this was S4 only until recently, so i'm back to screw around one my second N4.

I've patched the CM 12.1 nightly i wish to install, but when i flash the patched zip in recovery it gets stuck on

[MultiBoot] Creating chroot environment

and the loading bar freezes and then nothing happens. any ideas>
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I made a lot of improvements to the patching speed before, but this latest change is a whole new kind of improvement :)

This is what we're talking about. On my laptop (with a Samsung 850 Pro SSD), patching time was cut from 66 seconds to 6 seconds (90% reduction) for a CM12.1 nightly. The Android build needs some more testing, but we should be seeing similar improvements there as well.

[youtube]RovaLAGLJbE[/youtube]

EDIT: I'm going to have to brag about this. The new code can patch a 1.5 GB TouchWiz ROM is 18 seconds (on PC) :D
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Absolutely, brag on Brother...you should!!!! Great work!
[Galaxy S 4 i9505 Original Android Development] skivnit:
Can't wait to test on the s6 edge. No cm yet
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Yess it is gonna have the fastest boot time on the S6 Edge. Lmao
[Galaxy S 4 i9505 Original Android Development] v00d007:
Which snapshot version are you talking about? I'd like to test it but in the past most of your automated builds were broken somehow, as we already discussed here...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1137.g0c44f3b or newer. The newer snapshots should be relatively stable compared to the pre-8.0.0.r1000 snapshots. All of the major restructuring and changes are complete. I'm only working on app sharing, bug fixes, and speed improvements before the next stable release.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Would it be possible to install roms to /data? We in the s6 edge don't have any aosp roms and 2 touchwiz are too big?
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
please check the PM
[Galaxy S 4 i9505 Original Android Development] nds850:
Did a backup in twrp. When restoring it and wiping cache the phone boots into secondary ROM and all works well but when I want to switch to primary ROM in the app I get a bootloop.

Is there anything I can do to get into my primary ROM?

Edit: Solved it by flashing another kernel :)
[Galaxy S 4 i9505 Original Android Development] haoyangw:
[MENTION=4277844]chenxiaolong[/MENTION]

Weirdly I had two problems with DualBoot Patcher snapshots, one with the utilities flashable zip(4.0 snapshot 1) and one with the app(r1153). When I click 'switch to' for secondary with the utilities zip in recovery it tells me there is no secondary kernel, even though there is. I booted up primary and used the DualBootPatcher app to switch to secondary successfully, which shows that secondary kernel existed. For the patcher app, when I go to App Sharing settings I get a blank screen. I have already patched ramdisk as app requests but I forever get a blank screen when I go to App Sharing settings. Everything else works fine. Any ideas why? Am I the only one with this problem :P
[Galaxy S 4 i9505 Original Android Development] Technical:
Can we test it or it is not (yet) working?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's very close to being done. I won't give an ETA (because I'll probably miss it by twice as long), but here's an idea of what's left:

Shared APK is only updated on initial install. App updates don't make it into the shared directory

Apk and data sharing is not disabled when an app is removed (for that particular app)

Shared data is not used until reboot if app is removed and reinstalled

Enabling and disabling apk or data sharing requires a reboot. I don't know if it's feasible to make this change happen live yet

Paid app sharing (just apk, not data) is not supported

No UI for configuring app sharing in the app
[Galaxy S 4 i9505 Original Android Development] v00d007:
App sharing isn't really that important for me (and maybe others too?). Instead I'd loved to have the other features work 100% so I get a really reliable multiboot constellation without danger of being destroyed by the next action I make...
[Galaxy S 4 i9505 Original Android Development] HampTheToker:
I'd say it's pretty vital for those of us that have a ton of apps installed. It also cuts down on storage space so that's one less thing to worry about when choosing a multi-boot setup.

I'm eagerly awaiting it's return, personally.
[Galaxy S 4 i9505 Original Android Development] Technical:
Yes, that's the major problem: storage when we have a lot of apps installed and, of course, the easier to not having to install apps twice :cowboy:
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ok I have a reworked backup & Restore app.

You WILL have to uninstall the old version first.

Multi boot 1 is ready to test

Re-patching for a specific ROM for note4 recovery now should work for all future versions of patcher app

https://www.dropbox.com/s/858exmi0dqx749j/Multboot_Backup_Restore.55_sign.apk?dl=0

And yes I will add the ability to backup just the primary ROM and restore.

It will be recovery zips most likely
[Galaxy S 4 i9505 Original Android Development] tomaasz:
CM12.1 as second on S5 (klte)

Hello

I would like to try install on my S5 (klte) as second CM12.1 (by [MENTION=3322708]albinoman887[/MENTION])

My primary rom is based on stock Zombie ROM S6 UNDEAD Edition V5.1 by [MENTION=5697686]scholz123[/MENTION]

1. Can I patch the ROM (CM12.1) by last DualBootPatcherAndroid-8.0.0.r1153.g273f075-snapshot.apk ?

2. What Preset should I select ?
[Galaxy S 4 i9505 Original Android Development] Racinghart91:
I don't see the menu to make it a bootable zip? Any help please
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Wish we had more space on the s6 edge system partition. Debloated and it still won't flash lol damn touchwiz
[Galaxy S 4 i9505 Original Android Development] v00d007:
1st of all are you aware of the low cache partition space problem? To really install multiboot systems, when one of it is a bloated TW rom, you'll have to repartition the S5 first to get more space for cache. Search for instructions here at xda.

---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------

...haha, that's one of the reasons I'll never buy a S6 (Edge)...
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
I want to repartition stuff
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I just tested 55 and all was successful. The app recognized all multi-slots, (dual, slot-1, slot-2 & slot-3) with valid ROMs. It also detected previous dual backup as valid. Able to backup slot-1 (external sd) then restored with no problems.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Great thanks for testing. It's nearly there then! Just discovered it fails to make the multiboot folders if they're not there for restore... I'm gonna neaten up the interface a bit too.
[Galaxy S 4 i9505 Original Android Development] gaww:
Ditto here. I am constantly juggling SDcard (hardly any room on it), and APPs to SD, etc. since loosing app sharing - so it is not a minor issue.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Since we can only dual boot on the Note4 and it has 32GB internal storage app sharing is not really an issue for me
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=3145598]rlorange[/MENTION], backing up works with both TW (I used Kushan02 v4.0) and CM-12.1 roms. I noticed while performing the restore if you click on the dark gray box for Multi-1 it will bring up dual options but if yo click in the light gray area where backup info is then the multi-1 functions appear. See screenshot...

Same applies when performing backups.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Ah yeah lol thanks I'm going to switch back to a menu format soon. Now that I've figured out how to detect screen resolution and make two scenes depending. Thanks for the tip.

So backing up primary ROM should be easy I've got the code already from my old old version.

Also try selecting a patched zip and patch for a chosen slot it should run fine in recovery and bypassing aroma for note 4 users
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I'm not really sure how to do that...
[Galaxy S 4 i9505 Original Android Development] rlorange:
I'll add more info popups to guide.

Tap the top button it will search your storages for any patched file.

Scroll and long-press the one you want to patch.

It will bring up slot selections. Then you can choose to make a copy of it and re-patched or modify the existing zip.

Then you'll have a zip with dual_ or multi1_ etc at the beginning of the file!

Pretty sweet. No complete unzipping necessary. Cm12 zips take seconds TW zips maybe 1.5 minutes it will give you info.

I'm planning to allow merging of mods into ROM zip files in the future...
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Yeah...I figured it out after replying.
[Galaxy S 4 i9505 Original Android Development] rlorange:
Sweet. You got the note 4?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Nope, SPH-L720

Edit: I'll be darned, it worked!
[Galaxy S 4 i9505 Original Android Development] rlorange:
Yeah pretty neat eh?

Chen's using a similar technique i believe to do the patching now.

---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------

Thanks for testing the multi-boot stuff. It's a bit messy now tho need to clean up the ui and add info prompt mini tutorials

---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------

There's a quick reboot app stashed inside the app! Install with the very top button. Its stand alone or accessed through the main app
[Galaxy S 4 i9505 Original Android Development] Suzano-Sho:
EDIT: Disregard...The other thread didn't mention the DualBootUtilities....
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hey Chen for the future you might want to look into Gokhan morals multi boot solution.

He simply made img containers in data which were mounted by a modified init.

One of my very first apps was to shrink these containers since they had to be made initially the same size as the system partition... for some reason.

This is the most basic code he used to create the image. My first introduction to Linux terminal commands... memories

dd if=/dev/null of=/data/media/.secondrom/newsystem.img bs=1M count=512; #(or any other size you like)

mke2fs /data/media/.secondrom/newsystem.img

mount -o remount,rw /

mkdir /1

mkdir /2

mount /data/media/.secondrom/system.img /1

mount /data/media/.secondrom/newsystem.img /1

cp -a /1/* /2

umount /1

umount /2

mv /data/media/.secondrom/newsystem.img /data/media/.secondrom/system.img
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
I'll test on S6 edge :D
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Trying to patch slimbean weekly says supported but then fails right away any idea?
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Jamal google edition...

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
was it just a normal .txt file you used or something else?

I cant copy the file i made. it says something about permissions but i can see in ES file explorer that the folder is read write.

EDIT: copied the file to the /etc/init.d folder but doesnt look like its worked. Play just wants to re download all my apps again from the store. do my apps need to be on internal memory or memory card and what permissions do i need to set and where?
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
Sorry for sounding a bit thick :eek: but I cant get this to work. Could you produce a step by step guide on how to do it? :D
[Galaxy S 4 i9505 Original Android Development] mkhattat:
Does your secondary rom support init.d?

By the way if it supports init.d do the following:

1. Create a text file and copy and past these two lines:

#!/system/bin/sh

mount -o bind /raw-data/app /data/app

2. Save it under a name (you don't need to use any extension, just a name) and using a file browser, like root browser or your favorite file browser with the ability to access to the root folder, copy the created file to the /etc/init.d folder.

4. Set the permissions to 777. It means read, write and exec for all. (most of the file browsers have the ability to set the permissions if yours not you can use the terminal emulator by using the chmod command).

5. Restart your secondary rom.

PS: you can't use your already installed apps in the secondary rom anymore, only apps that are installed in the primary rom.

PS2: if something went wrong and you couldn't boot to secondary rom: switch to primary rom then go to /system/dual/etc/init.d and then remove the script.
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
I followed your guide to the letter but still it wont work, I cant see any of the apps that are installed on my primary ROM on the secondary ROM. I'm using the Google Edition ROM by Jamal which has a init.d folder already in it so I'm guessing it should work.

This is what I did:

1. Created a file called 'apps' (not a .txt file, just a normal file) with the two coding lines above.

2. On my Primary ROM, copy the 'apps' file to /system/dual/etc/init.d and set the 'apps' file permissions to 777 using root browser.

3. Reboot into secondary ROM

When I go into the secondary ROM it tries to re download all my apps again as its not seeing them in the primary ROM apps folder.

All of my primary ROM apps are installed to the internal storage.
[Galaxy S 4 i9505 Original Android Development] mkhattat:
Hmm.. It seems your secondary rom can't mount the app folder.

Do you have busybox on your secondary rom installed? Would you run the mount command (without any argument) in terminal emulator and see if it works (you should see all the mounted points).
[Galaxy S 4 i9505 Original Android Development] Sushibagel:
i haven't really thought to check but if I install an app on the secondary rom it won't install to the primary correct?
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
Ive just installed busybox to the secondary ROM and restarted but didn't do anything. Ive just downloaded Android terminal emulator. What is the exact command i should run and and in what ROM?

ill post back tomorrow with results as I don't have time now.
[Galaxy S 4 i9505 Original Android Development] mkhattat:
If you install an app on the secondary rom or vice versa, it will be installed also on the primary rom and you can use it just like other apps.

Run these commands on your secondary rom and send me the results via pm maybe I can help you.

su

mount
[Galaxy S 4 i9505 Original Android Development] taxi333:
support omnirom

please add support for omnirom. Here's the link:

http://xdaforums.com/showthread.php?t=2483622
[Galaxy S 4 i9505 Original Android Development] DreenHotdog:
Hey I want to say thank you very much to you for supporting Kangabean into the dual boot! :D id like to make another request. Can you pleaaaase add support for this one?

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

It is an official touchwiz 4.3 for the S4 I9505. Thanks and you're amazing! Keep up the good work! :good:
[Galaxy S 4 i9505 Original Android Development] 13silencer13:
Can you add support for gs4 blackbox rom here's the link thank you

http://xdaforums.com/showthread.php?t=2429072
[Galaxy S 4 i9505 Original Android Development] scott62185:
Question: I know we're not supposed to wipe in recovery but use the dualboot utilities zip instead. Do we have to flash that each time we flash a rom?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I would highly recommend it lol. Most roms wipe the system partition and the dalvik and cache, but most don't wipe the data. So if that's something you wanted to keep through an update, give it a try.

So far, after I've changed my primary rom, I've had to reflash the secondary because of the partition wipe. Not to much of a big deal lol

Sent from my dual boot PAC'd/touchwiz S4
[Galaxy S 4 i9505 Original Android Development] scott62185:
Okay, got it. another question: I just flashed an update to my primary rom and when I flash a custom kernel with it (ktoonsez), I'm getting some weird reactions from my rom-all the colors are orange-ish and I get a multi-clolored screen pop up occasionally (incidentally, when i just flash the rom without the kernel I don't get the problem). Do you think that has to do with dualboot?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I would definitely say that's kernel related because dual boot only affects the secondary rom. All it does, pretty much, is change the mount points and kernel switching, in a very genius way lol.

Sent from my dual boot PAC'd/touchwiz S4
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
Guys if you use the stock ROM as before .. which I have to remove system applications? ps. It is the same if the rom is cooked?

there is any of you who has the google edition of jamal as a second ROM?

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
u0_a84@jgedlte:/ $ su
root@jgedlte:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /raw-system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /raw-data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /raw-cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/raw-data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/raw-data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/raw-data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/raw-data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/raw-data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
root@jgedlte:/ #

Not sure if the pm sent.
[Galaxy S 4 i9505 Original Android Development] RK:
[MENTION=4277844]chenxiaolong[/MENTION] is there a patched touchwiz 4.3 ramdisk? Or would I be OK using the 4.2 one?

EDIT: I tried the 4.2.2 touchwiz ramdisk with ktoonz 4.3 touchwiz kernel and got a bootloop! I guess I will just wait for you to make a ramdisk for ktoonz 4.3 touchwiz..

I am looking to install THIS Touchwiz 4.3 ROM as secondary from THIS thread
[Galaxy S 4 i9505 Original Android Development] rlorange:
What that code no it's just an example lol
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
I meant if he felt the need to introduce I will test since no rom is small enough to flash 2 touchwiz at the same time
[Galaxy S 4 i9505 Original Android Development] Suzano-Sho:
Is there another way to flash DualBootUtilities aside from TWRP? Everytime I try to, it freezes up my phone...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When I first worked on supporting Lollipop, I added support for this. (In fact, the code is still there and it still works!) I spent a LOT of time working on making ext4 images work properly, but a few kernel bugs broke everything.

The problem is precisely with the resizing. More than half of the devices supported by the patcher have unpatched old kernels. Many manufacturers (maybe AOSP itself, I can't remember) enable the uninit_bg ext4 option when creating an ext4 image to speed up the e2fsck process. Unfortunately, many devices' kernels don't contain this patch (http://www.redhat.com/archives/dm-devel/2012-June/msg00029.html) leading to the kernel miscalculating the number of free blocks in the image, resulting in a really broken image after a resize.

This was almost always reproducible by simply flashing a ROM, rebooting, flashing a gapps, and rebooting again. You'd end up with an irreparable image.

That's why I ended up not using that method (although it is *super* nice for backup, etc.). By the way, which device did you have when you tried that method? I'm guessing it was unaffected by these bugs :D

EDIT: The initial size has to be the size of the system partition because that's what the filesystem images expect (eg. system.new.dat on Lollipop). It's like how you can't backup a 500 GB hard drive and restore it on a 250 GB SSD without resizing the partition first, even if you're only using eg. 50 GB of the space.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll build you a test version that supports installing to /data over the weekend. It's super easy for me, just 17 lines of code (yes, I counted :D)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Holy hell you are amazing!! We just got the 5.1.1 ota today and [MENTION=448423]eosphoros[/MENTION] already has a rom