yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
From Multiboot log:

Cleaning up and setting metadata...
ApplyParsedPerms: chown of /system/app/ConfigUpdater to 0 failed: Read-only file system
ApplyParsedPerms: chgrp of /system/app/ConfigUpdater to 0 failed: Read-only file system
ApplyParsedPerms: chmod of /system/app/ConfigUpdater to 493 failed: Read-only file system
ApplyParsedPerms: lsetfilecon of /system/app/ConfigUpdater to u:object_r:system_file:s0 failed: Read-only file system
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
[D] Child exited: 7

[E] /mb/updater returned non-zero exit status
[D] [Installer] Filesystem unmounting stage
[D] Running command: [ /update-binary-tool, unmount, /system ]
[MultiBoot] Failed to run real update-binary
[D] update-binary-tool: Unmounted /system
[D] Running command: [ /update-binary-tool, unmount, /cache ]
[V] update-binary-tool: Ignoring unmount command for /cache
[D] Running command: [ /update-binary-tool, unmount, /data ]
[V] update-binary-tool: Ignoring unmount command for /data
[MultiBoot] Copying temporary image to system
[E] Failed to mount /dev/block/loop0: Invalid argument
[MultiBoot] Failed to copy /data/.system.img.tmp to /system
[D] [Installer] Cleanup stage
[MultiBoot] Failed to flash zip file.
[MultiBoot] Destroying chroot environment

I attached full Log to post above
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Just a quick question....does patcher have root permission?
[Galaxy S 4 i9505 Original Android Development] Edde3d:
Edit: sorry thought you were asking a question...

Sent from my VS985 4G
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
My phone is rooted and the .APK works fine in other installed Roms, patched PA fine and the Gapps files but TWRP fails as above :(
[Galaxy S 4 i9505 Original Android Development] todivefor:
I had that system r/o before. For the life of me, I can't remember how I resolved. Try TK-gapps and wipe system before flashing. Or wait for [MENTION=4277844]chenxiaolong[/MENTION] or someone smarter than me.
[Galaxy S 4 i9505 Original Android Development] gaww:
Easy way to check is to run the Utility zip and check the statues of each partition on the first page. If system is filled up (even though it did not finish installing), room is the issue.

What are the size of the primary you are trying to flash? After wiping primary system with the utility, how much room is left in system compared to the primary size (it is zipped - you would need to compare it to the unzipped ROM size).
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Appears it was something to do with the Gapps, Rom reinstalled with tk-Gapps and up and working :good:

See above there was no problem with space it was just some issue with my Gapps it appears :cool:
[Galaxy S 4 i9505 Original Android Development] gaww:
global app sharing bug

I have given up trying to share apps globally between 4.xx TW and 5.xx TW ROMs. For some reason in that mode, Play Services and sometimes Play Store gets messed up after switching back and forth between the ROMs. I had the same thing happen when I tried the early 9.xx Patcher Alpha. These apps are not shared, but something is leaking back and forth between them

Had to restore a back up - could not get them sorted out by wiping system and reinstalling. So far, individual app sharing seems OK
[Galaxy S 4 i9505 Original Android Development] nattanarcilla:
Dual Boot Mokee

Has anybody tried to dual boot mokee OS?

I tried but no success.

log says:

[Multiboot] Here we go!

some files are modified, package corrupted.

[Multiboot] Failed to run real update-binary

The patchrom preset used was jflte/ROMs/AOSP/cyanogenmod-based

I can flash the original zip package as primary ROM but neither in dual or data slots.
[Galaxy S 4 i9505 Original Android Development] todivefor:
This was a dirty flash. I have since flashed by wiping /system and it worked fine. Of course, I have also wiped everything and it worked. Once I get it all setup, I will backup and try dirty flashing again.
[Galaxy S 4 i9505 Original Android Development] v00d007:
1st of all I don't know which patcher version I used at that time. Just take the ones that were recent when f4k pushed out his unofficial builds of cm12. I selled my S4Mini some mpnths ago...

And don't be so worried about anything. There's no way to hardbrick a phone with such actions. But I also wouldn't advise you to re-partition or do something like that, there's really no need to do such risky things. Just do a full nandroid backup with 'philz touch' and if something goes wrong you'll be back to where you started with just 3 taps... ;)
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
[MENTION=4277844]chenxiaolong[/MENTION] Any news on this?

Thank you.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi

Thanks dev for this great tool!

What is better for installation of new apps? Primary rom or others?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] gaww:
If primary is your daily - that is probably the best choice if you are app sharing. otherwise, it doesn't make a difference.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
No difference really apps will show up on both installed roms if you are app sharing. Another reason why this method is so convenient
[Galaxy S 4 i9505 Original Android Development] tomaasz:
I have some problems with apps sharing.

After switching from secund to Primary Rom doesn't see all apps.

Reboot to Primary helps, and I can see them again but I lose my shortcuts on desktop and apps being not shared and I need share them again.

Have you got similar situation ? Is any method for improve this ?

At the moment I use 3 roms Primary (TW) + Data-slot-1 (CM) + Data-slot-2 (Bliss) in my Galaxy S5 900F (klte)
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
App Sharing becomes a bit more complicated when sharing between so many roms, such as 3 or 4 roms for example. There will be slight issues here and there but it is doing its best to share properly between 3 roms. If you are using a launcher such as Nova launcher you can create backups of your icon layouts. Use the same launcher between roms and restore the backup of your icon layout between roms. May help you with the icons disappearing on desktop so you do not have to manually set up your home screen again, save you some time.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Thank you for information and idea for backup and restore of icons.

This issue I had also with 2 roms.

And Icons are not only problem. Second one is that after this, it is needed do again individual apps share because they lose "Shared APK"

This is only my feedback. I really appreciate great work of [MENTION=4277844]chenxiaolong[/MENTION]

It is really amazing tool! I use this, I will use and I'm really happy that I can use it great patcher!

All the best for you
[Galaxy S 4 i9505 Original Android Development] silvercat:
Hey [MENTION=4277844]chenxiaolong[/MENTION] , after updating twrp to newer version (2.8.7.1) the dual boot has stopped working, it says invalid device id while trying to flash the secondary rom or any other patched zip file. I tried to flash via new recovery but with same result. It worked with older twrp though ..my phone is S6 Edge I version but the new twrp is based on F Version.. could it be because of this its give invalid device id error ?:confused: or adding a support for S6 Edge I variant in dual boot patcher app would do the trick ?
[Galaxy S 4 i9505 Original Android Development] peppe130:
Hi Chen could you add support for Note 3 Neo? :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi , I notes you have 3 rom on , so I wonder, why I cant instal nothing on multislot1?

i try 2-3 time , but on secondary install perfect (on exS4 I manage to instal 3 rom without problems) the app tell my I don't have space (on primary I have an TW debloated)

THX
[Galaxy S 4 i9505 Original Android Development] tomaasz:
I used data-slot (s), not multislosts

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] monkteo:
Sorry my mistake I didn't notice !

But can you tell my , it's better to install in data-slot ?

THX
[Galaxy S 4 i9505 Original Android Development] tomaasz:
I don't know what is better but data-slot is good, enough.

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] silvercat:
I'm not able to flash any file after patch. It keeps failing everytime
[Galaxy S 4 i9505 Original Android Development] sronweb:
What about using r1388 version of the patcher? I flash from TWRP recovery and is working fine but I never tried to flash from the patcher.
[Galaxy S 4 i9505 Original Android Development] silvercat:
It was the same result with previous version.. What version is your twrp? Mine is 2.8.7.1
[Galaxy S 4 i9505 Original Android Development] sronweb:
I'm with 2.8.7.0 from Antares one which was available in the TWRP thread.
[Galaxy S 4 i9505 Original Android Development] silvercat:
Ok so which phone do you have?

Bcuz mine is s6 edge sm-g925i
[Galaxy S 4 i9505 Original Android Development] ad346:
Hi guys,

Okay I'd like to dual boot thing my phone, at the moment im running the aicp rom but i also wanna flash a TW rom, so that i can have the stock samsung camera app and the others, can anyone suggest some nice efficient TW roms for this? 4.3 stock samsung i believe isnt available yet except for a leak but will be soon...
[Galaxy S 4 i9505 Original Android Development] Hecatrice™:
For example that applications? after you deleted them?

it also has installed DualBootUtility?

Inviato dal mio GT-I9505 con Tapatalk
[Galaxy S 4 i9505 Original Android Development] mkhattat:
I suggest you Echo ROM ( http://xdaforums.com/showthread.php?t=2372286)

I installed it as my primary ROM. It's fast, smooth and also the latest 4.3 version without Knox bootloader.
[Galaxy S 4 i9505 Original Android Development] gaww:
Omega v13 4.3 will be out real soon - I will be trying it as primary soon thereafter.

Would be great if it (v13) and a modded stock TW ROM could both be used, but I assume they are too big (even is debloated) to fit on the system partition.
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
I didnt delete any System apps, just move them to user apps using the /System/app mover from Play store.

These two threads will help you decide what to move

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

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

The DualBootUtility isnt needed to install a sceondary ROM; its only needed if you cant boot into the other ROM or used to wipe the /system or /cache.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
They would have to be super debloated

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] gaww:
Both Omega and Wicked can eliminate most or even all with Aroma installer, but Aroma has about i gb of languages wheich can de removed manually but takes a lot of doing - too bad that can't be done with Aroma.

Having stock based 4.2 and Omega v13 4.3 would be a great combination though.
[Galaxy S 4 i9505 Original Android Development] neilk:
Hi chenxiaolong,

Will the patcher work with i9500, I have the latest 4.3 stock rom rooted, and I am trying to patch pac_i9500_4.3.Build-1_20131002-151820. I only get an error when trying to patch...

Please help, let me know what and how I can test (if this is not only for the i9505 variant)

Thanks

Neil
[Galaxy S 4 i9505 Original Android Development] Nick0703:
It won't work with the i9500. Only with Qualcomm-based S4.
[Galaxy S 4 i9505 Original Android Development] tylerholbrook:
http://xdaforums.com/showthread.php?t=2492021

Any way to get the aicp to dual boot? Thanks
[Galaxy S 4 i9505 Original Android Development] klsmalls1:
Ok I am running into the following situation:

My Primary ROM is Alpha 11 with KToonz Kernal,

When I install my secondary ROM (Liquidsmooth) everything works fine except access to my 64gb card.

When I try and flash a new ROM (KT or Chronic 4.3) it boots up, but then the ROM is completely screwed up ( cannot access anything period)

Not sure whats wrong, anyone else had this problem?

Any recommendations?
[Galaxy S 4 i9505 Original Android Development] ahoslc:
I was in Eclipse Touchwhiz but then installed the Dualboot App set the kernel. I then patched Slimbean weekly rebooted into CWM and installed it. On reboot I get Yellow Verizon Triangle saying system software not authorized?
[Galaxy S 4 i9505 Original Android Development] ad346:
is the new omega 4.3 supported? http://xdaforums.com/showthread.php?t=2253528

if so, would someone be so kind as to just guide me through how to patch etc and dual boot this onto my phone?(in an inbox)

im currently running aicp, and id like that to remain as my primary rom.

Also, does the omega rom have the default samsung apps and features working? such as the samsung camera and the smart scroll etc features?
[Galaxy S 4 i9505 Original Android Development] 13silencer13:
Can we get support for omega rom v13 here's the link

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

Thank you
[Galaxy S 4 i9505 Original Android Development] gaww:
How is your card formatted ? If ExFat, which works with KT kenel, it may not work with Liquidsmooth.
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Why would Slimbean not patch for S4 VZW the Tmobile Slimbean patched fine but that won't work for me.
[Galaxy S 4 i9505 Original Android Development] feelpt:
[MENTION=4277844]chenxiaolong[/MENTION]

Great job...

Is it possible to add support for VANIR AOSP? http://xdaforums.com/showthread.php?t=2485089

It's based in AOSP latest builds, so I believe it should be working... I'll try and let you know

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

Edit : Just tried to patch rom zip and said unsupported zip
[Galaxy S 4 i9505 Original Android Development] tylerholbrook:
Okay so I am pretty sure I got my ROM patched from someone else uploading the patched files I needed to swap with the original ROM. Anyone have a patched KT 4.3 kernel for cm they'd like to share?? It's for aicp 4.3
[Galaxy S 4 i9505 Original Android Development] KristianKenneth:
Installed Echo ROM v5 4.3 as my primary and patched PAC MAN rom latest build as secondary. Followed instructions properly and whenever I choose to boot on second rom on the app even in AROMA utilities I still end up booting on my primary rom which is TW.
[Galaxy S 4 i9505 Original Android Development] Bejda:
Could be some mess with "set current kernel as.." option.

Try to set current kernel as primary while on Echoe rom,flash again your patched PAC it should boot on secondary rom then set your current PAC kernel as secondary and see..
[Galaxy S 4 i9505 Original Android Development] sronweb:
S4 i9505 (international version).
[Galaxy S 4 i9505 Original Android Development] ade_k012:
Hi Chen, thanks very much for this fantastic patcher.

I have used this dual boot patcher since version 7, and my configuration is like this:

- primary: TW

- secondary: PAC Rom 4.3 (I am failed to move on to PAC KitKat, even PAC Lollipop due to the greatest feature in PAC JB Hybrid Mode & Halo :D)

- multiboot-1: MIUI 4.4 KitKat

long time didn't check this thread, I've found that you have implemented data sharing, which is very great feature.

So I try your new ver 8. 1388 snapshot patcher to patch my PAC ROM 4.3 as multiboot2 (my primary ROM is TW LL Imperium 9.0). I could patch the ROM successfully, but not with the PA-GAPPS, so I try generic gapps & finally it success.

Problem occur when I flash them. I try to flash them using dual boot patcher (ver 1388). ROM flashed succesfully, but when i boot to the rom, i lost my IMEI, so i could not use it because it has no network signal. and then I try to flash it with CWM, also Philz, but I got error status 1 (installation aborted, asserted failed bla bla bla). With previous patcher i used (ver 8.00 r99) I've never failed to flash this PAC ROM. may be some changes you made in the patcher make this error happen. But finally i've found that the error Status 1 caused by updater-script, so i delete the first line in the script and voila, I could flash the PAC ROM 4.3 as my multiboot2 ROM. and the happiest things is I could switch from my primary ROM (LL TW) to my PAC ROM 4.3 (as multiboot) without re-install and restore my Whatsapp & BBM contact and chats. The Data is shared between ROM.

this is very great experienced.

thank you very much Chen

myphone S4 i9505
[Galaxy S 4 i9505 Original Android Development] nikomedes:
LG G3

hi,

although this is Samsung forum this app may be used for LG G3 too. I have a question I try to instal CloudyG3 2.5 rom via dual pacher, I get an error message something like that;

"ZIP files using the AROMA installer can only be flashed from recovery"

do you have any idea to solve this?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
OnePlus One

Could you add "A0001" as codename for OnePlus One additionally to "bacon"?

Btw. Update ramdisk on oneplus results in bootloop.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm nearly a month late, but I'm subscribed to both threads now :D I really appreciate you creating the threads!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Since I'm on and off this forum a lot (sometimes weeks at a time), I figured I'd give an explanation. I'm sure many of you have seen really good projects here on XDA that have been abandoned due to developers' work contracts for their day jobs (eg. philz recovery). Many tech companies have a policy where you must assign copyright of all side projects to the company in order to prevent you from developing, eg. a competing product in your spare time. At the place I work, I was able to negotiate so that I could keep my copyrights for all of my existing open-source projects on the condition that the projects would not impact my day job and that I would not work on them when I'm working on large work projects.

Anyway, just wanted to let you guys know that I'm not dead (and this project is not dead) :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
pepper (Sony Xperia Sola) should now be supported in 8.0.0.r1424.gda07303
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
(Shameless self-promotion)

Not sure if anyone has played around with the "bootimgtool" program included with the PC version of the patcher. If you mess with boot images/kernels a lot, it can make your lives a lot easier. It can handle plain boot.img files, Loki'd, bumped, and Sony combined boot/recovery images. It's a replacement for mkbootimg/unpackbootimg, but does a hell of a lot more.

Eg.

Extract a boot image and repack it. No need to specify any addresses, page sizes, or other values (though you can if you want).

bootimgtool unpack boot.img
bootimgtool pack -p boot.img new_boot.img

Extract a boot image and pack it as a Loki'd or Bump'd image

bootimgtool unpack boot.img
bootimgtool pack -p boot.img -t loki lokid_boot.img
bootimgtool pack -p boot.img -t bump bumped_boot.img

Swap out the kernel in the boot image

bootimgtool unpack boot.img
bootimgtool pack -p boot.img new_boot.img --input-kernel /path/to/some/other/kernel/zImage

(Sony specific) Unpack and repack combined boot/recovery image

bootimgtool unpack kernel.elf
bootimgtool pack -p kernel.elf -t sonyelf new_kernel.elf

And a lot more! See:

bootimgtool --help
[Galaxy S 4 i9505 Original Android Development] Sanesh Munde:
[MENTION=4277844]chenxiaolong[/MENTION]

Can you please check my device Samsung galaxy s4 mini duos GT I9192

ro.product.device=serranods

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
I had been wondering were you went. Had me a bit worried but I did remember a conversation we had before about your new job opportunity that's really great news, congratulations once again. Also happy to here you were able to come to an agreement. Things have been going well even with some of the new device support you added. Glad to hear you like the threads I made, thought they may help spread the word along with help add support for those who may have questions specific to some of those devices.

Just noticed the latest release. Time to give it a look see.

Thanks a lot. ?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
I have questions about app sharing, as I had tried it a little while ago but was not convinced. Is it possible to keep already installed app data ? When I tried to share apps, the common data created was empty. Also what about restoring data with titanium backup and the like for shared apps ? Thanks
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I am planning to try this to my I9505. I am on Imperium 4.2.2 Rom now and I want my second ROM to be the stock 4.2.2 ROM. Is it possible?
[Galaxy S 4 i9505 Original Android Development] Edde3d:
You can try. But from my experience stock roms don't like to run as secondary for some reason. That's how it is on LG g3 anyway.

Kickin it on my VS985
[Galaxy S 4 i9505 Original Android Development] sronweb:
As Chen explains on the first post is a question of space. Stock ROM is the larger size demanding rom. You can see that the installer of a Touchwiz is more than 1Gb versus around 250 Mb of the CM or other AOSP roms:

"Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.

Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.

Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.

Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app."

Anyway just make a nandroid backup first and you can try everything!;)
[Galaxy S 4 i9505 Original Android Development] hertzschi:
Please two short questions, I didn't find the answer in searching the thread:

Is it possible to dualboot a cm11 as secondary on a TW Lollipop Rom as primary?

CM11 shows only bootanimation since hours :(

How can I switch back to primary, if the secondary is currently active, but doesn't boot?
[Galaxy S 4 i9505 Original Android Development] animelover:
You can use DualBootUtilities.zip via Recovery, if you had set the primary kernel beforehand.
[Galaxy S 4 i9505 Original Android Development] hertzschi:
OK, Thanks.

I'm back on my primary rom now.

Has anyone succeeded with installing a KK Rom as secondary with a TW Lolli as primary?
[Galaxy S 4 i9505 Original Android Development] todivefor:
I am pretty sure I have done that. Sometimes when I got in that situation, I had to flash a kernel. Try patching and flashing Ktoonsez or Alucard's KK kernel.
[Galaxy S 4 i9505 Original Android Development] animelover:
Do they both work on MIUI 6 based on TouchWiz?
[Galaxy S 4 i9505 Original Android Development] todivefor:
I believe KT has both AOSP and TW versions, but believe Alucard is only AOSP, check their threads. MIUI, I have no idea. The person was asking about CM11.
[Galaxy S 4 i9505 Original Android Development] hertzschi:
thanks, will try this and feedback
[Galaxy S 4 i9505 Original Android Development] peppe130:
Chen could you add support for Note 3 Neo? What do you need?
[Galaxy S 4 i9505 Original Android Development] v00d007:
Quite often the patcher does work on devices that aren't "officially" supported. Just do a full backup and try the most similar device profile.
[Galaxy S 4 i9505 Original Android Development] peppe130:
The partition table is different!