yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The procedure you're following is exactly right. This is probably something I'll have to flash myself and do some debugging on.

EDIT: Do you still have the MultiBoot.log file on the internal storage? That might give me some hints on what's going on.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll take a look at the ROM. Do you still have the MultiBoot.log file in your internal storage? If so, could you send it to me? I'll at least be able to tell if something failed during the installation.

EDIT: Just wondering, do you have TWRP 2.8.7.1? It's listed as one of the requirements for the ROM.
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Dear [MENTION=4277844]chenxiaolong[/MENTION] could you add opportunity for filter in individual sharing app list for shared apps, for apps with shared data and for no shared apps?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Now I've installed the rom as primary, that worked without any issues. It seems that the rom was too big for being the Secondary rom. Here is the log, but I don't know if that is the right log as I flashed it as primary now succesfull.

I removed some unnecessary lines to match the 30000 charakter limit. Marked them with [...].
[Galaxy S 4 i9505 Original Android Development] v00d007:
Isn't [MENTION=417657]nutpants[/MENTION] having the same problem as I also mentioned some days ago, namely that the recent patcher builds got problems with kitkat roms? Have you maybe not tested kk compatibility for a while cause all is focused to LP?

btw: I will test older builds like 436 when I got some time for that, I don't need the app sharing feature you're working on so hard anyways.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The problem is that I upgraded my S4 to the lollipop bootloader already so KitKat ROMs don't boot (for me), regardless if I'm dual booting or not. I still test KitKat on my Nexus devices, but those are very different from the S4.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh yeah, that is the successful log. Glad you got it working in primary! If you have a space issue in the future, you could install as data-slot. Those are installed to your /data partition (internal SD).
[Galaxy S 4 i9505 Original Android Development] v00d007:
Hmm, I can't confirm that. I successfully restored a backup with 1st kitkat Tw and 2nd cm11 (old dualboot version), and both booted with the LP bootloader (OD7).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're right, I apologize. That was my experience with the Note 4, not the S4 (jfltetmo doesn't even have Lollipop yet). I was able to reproduce the boot hanging issue on my S4 with pretty much every KitKat ROM. It happens because the dalvik cache couldn't be generated.

For app sharing to work, mbtool proxies the connection between the framework and installd. installd is responsible for installing apps (well, part of it) and creating the dalvik cache. Apparently, on KitKat, the framework sends an empty 0-byte message to installd. This is explicitly not allowed on Lollipop so my proxy code kills the connection whenever it encounters this. That's what's causing the boot to hang. I'll have to take a look at the KitKat source code to see what's the best way to fix this.

EDIT: This is caused by the multithreaded dalvik-cache feature. https://github.com/CyanogenMod/andr...mmit/8124b181d4b5a3a44796fdb0e3ea4e4171f102c7 Depending on how it's implemented, I might need to disable app sharing on these ROMs.

EDIT2: This is something I can fix if I can reliably detect which ROMs have this feature. I just need to proxy an "id" field (representing the message) to installd.

EDIT3: Fixed in 8.0.0.r1459.gbf1bfa7
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, try to install in dualboot on my S5 (MIUI V6) not succeed , but after that I can't install nothing in dualboot (I try temasek and blisspop on secondary and dataslot1)before that work OK,

it patch ok, start to install but remain at boot image.(I even restore an backup and try dualboot but nothing)

What to do ? Help
[Galaxy S 4 i9505 Original Android Development] v00d007:
Wow, v1459 made it, thanks a lot man! But why are nearly all patching profiles gone?
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
Did that exactly but still it didn't work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem! :) I guess you're talking about the presets? I deleted all the ones that are just using the default settings. They used to be necessary before custom patching was supported, but now they're only needed for files that need special care during the patching process.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Try booting into primary and deleting /sdcard/MultiBoot. Then set the kernel for primary and try flashing again.

EDIT: If you could attach /sdcard/MultiBoot.log, that would be great. That'll give me the details of why it's failing.
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
Sir is there any way to install a stock 4.2.2 ROM and the Imperium ROM at the same time? Please help me. I9505 by the way.
[Galaxy S 4 i9505 Original Android Development] monkteo:
I hope this is it !

THX

PS this is the rom (http://xdaforums.com/galaxy-s5/unified-development/rom-wip-27-9-14-t2889474)

THX again
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Hey, I just installed CM12 as secondary rom. My primary is TouchWiz based. Now I switched rom to boot into my sencondary. BUT: I wanna use my primary rom instead, so I tried to switch it back, but it does not work. Everytime it boots into my secondary rom. How can I boot into my primary? Is there a way? Maybe I made a mistake as I set the kernel for primary after flashing CM12 but before rebooting. Thanks for help!

Edit: I just flashed with TWRP the flash boot.img file in MultiBoot folder. But it boots into secondary rom :/ Then I tried to flash the file boot.img.before-ramdisk-update.img. Now it seems to boot into my primary rom, but I get a bootloop :/ What to do?

Edit 2: I just patched a custom kernel and installed it for primary. Now it works :)
[Galaxy S 4 i9505 Original Android Development] v00d007:
Flashing the kernel for the specific Rom is always one of the last options. Just never forget to SET THE KERNEL for the active rom BEFORE switching to another. But there's also another ultimate option to manually put the correct boot.img to the sdcard/multiboot/xxx folder from within a revoverie's file manager (TWRP or Philz+aromafm). You've to extract the Boot.IMG form the kernel.zip or Rom.zip before.

Edit: then you have to switch to your preferred rom with the dualboot utilities, I prefer snapshot 4. 6 has wiping bugs.
[Galaxy S 4 i9505 Original Android Development] gaww:
---------- Post added at 11:51 PM ---------- Previous post was at 11:40 PM ----------

[/COLOR]

I have done that in the past. Imperium will have to be installed as a multiboot, as there will not be enough room for a secondary. Be conservative in

choosing options in Aroma (plus user apps) - there is not a lot of space to use (2.1 gb approximately).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think snapshot 7 should fix some of the wiping bugs. Just stupid mistakes on my part :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Starting from 8.0.0.r1460.g3f4675b, the device dropdown box in the patcher will automatically choose your current device by default :)
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Allow me to ask a stupid question - From where it pulls the device name? I think you should let a manual option because there are some roms that show another device. Norma Rom for Note 3 show as device G9250 and has everything moddified, as i read, for the theme store to work without problems..

Thank you for your awesome work! Cheers!
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hi, found another file related MultiBoot

Hope you can find a fix for my

THX
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes, cool and as always you could really serve lots of other developers as a great example....
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
So what you did was use the STOCK as PRIMARY then the Imperium not as Secondary but as Multiboot? OK thanks. Then you flashed the Imperium Kernel?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh the device selection is still there, it just selects the device specified by ro.product.device (from build.prop) by default instead of the first item in the list. Just saves two extra taps for choosing the device every time you want to patch a file ;)
[Galaxy S 4 i9505 Original Android Development] monkteo:
[MENTION=4277844]chenxiaolong[/MENTION], any idea about my problem ?

please help my

THX
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes to the above - plus I also patched and flashed his S5 Port on top of it.

Remember to patch everything before flashing including the primary (and set kernel on it first)
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

I can not flash patched by android app file of CM 12.1 on my S5 900F (klte)

Is it visible for you in log why it is ?

BR, tomaasz
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I'm sorry but what exact stock ROM did you use and what patch did you apply? Or you mean just apply the kernel of the stock first? And after that flash the Imperium, Kernel, and the S5 patch? Correct?

You mean I should also patch Primary? Do you have a flashable zip file of the stock 4.2.2?
[Galaxy S 4 i9505 Original Android Development] tomaasz:
I think I know now.

It was because recovery .

I used original TWRP.

When I switched to custom TWRP by ktoonsez, it was able to flash.
[Galaxy S 4 i9505 Original Android Development] gaww:
I used two different US TMo based stock 4.4 ROMs - Cardhd 33,2 last. Patched it as primary, flased it, booted up and immediately set its kernel as primary before setting up next ROM.

With the Patcher APP, patched Imperium 4.4 2, his latest 4.4.2 kernel at the time, and also patched the S5 zip.

I then flashed the patched

ROM. S5 zip, and kernel

and booted up. It worked well, and then I set up app sharing, which worked pretty good then between 4.4 ROMs If you use a 5.x LL ROM as primary, then you have to be careful with app sharing - recommend only using individual app sharing, as global sharing seems to have some issues.

The reason you patch primary is if you have to flash it again, and if its install script wipes cache - it won't wipe out your MultiROMs, which I carelessly have done a few times.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll take a look at the errors and logs a little bit later tonight. Right now, gotta move my stuff to this new baby :D
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have that exact same one. Works great!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is likely something I could fix. The recovery is probably compressed differently. Any way you could link me to the exact recovery that didn't work? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The log indicates that the ROM was successfully flashed. I don't see anything that failed in there. When you said it was hanging at the boot screen, did you mean the Samsung logo or the ROM's boot animation? Also, did it auto-reboot into recovery?

Did everything break only after you tried installing MIUI?
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
What I really wanted to use is the stock rom 4.4.2. I guess CarHD is a custom one. This is the exact stock rom I wanted to use.

http://xdaforums.com/galaxy-s4/general/i9505-downgrade-5-0-lollipop-to-4-4-2-t3052472
[Galaxy S 4 i9505 Original Android Development] monkteo:
Hanging at rom logo, after MIUI trying yes, and I restore my backup

---------- Post added at 05:00 AM ---------- Previous post was at 04:58 AM ----------

And no reboot in recovery just hanging to rom logo.

THX
[Galaxy S 4 i9505 Original Android Development] gaww:
Stock TW as primary should work the same - just patch, flash, and set kernel. You can keep it as is or patch and flash another 4.4.2 TW kernel on top of it - but then you would have to set that kernel also.
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
I am really sorry but I really could not understand it. I know how to flash that but I don't know how to patch that. Anyway, I think I should give-up.
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

What happened to the compatibility with cm12.1? I patched/installed cm12.1-20150720-jflte with v1459 to multislot-1. But it gets stuck in 1st boot. S4 gets really warm but no boot success after 20min...
[Galaxy S 4 i9505 Original Android Development] sronweb:
I have the same configuration and same phone (jflte) and I have patched CM 12.1 as multi slot1 without problems. So the patcher is compatible. I would reinstall after wiping system and cache using the dual boot utilities (version 4 is last one working for me).
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

I tried everything, it's gotta be a new bug. Not even flashing a custom kernel makes it work. Haven't had that issue for quite a long time, I think it was with the very early builds of cm12...
[Galaxy S 4 i9505 Original Android Development] 1stichiban:
Hi bro, have you downloaded the dualboot patcher app from the link provided in the OP? you can "patch" the zip files you want to flash as dual, multi-slot, etc.?

;)
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
Yes Sir. Installed that both on my PC and on my I9505. But what I didn't get is how to flash the primary stock ROM because the ROM itself is just flashable via ODIN. There is no way to patch it as primary because it is not a zip file that is flashable via recovery or maybe I just didn't get it clear.
[Galaxy S 4 i9505 Original Android Development] monkteo:
It's not mandatory to patch primary rom !

I never patch primary rom, only secondary or multislot1,2,3
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
Oh I see. But I already tried patching the Imperium Kitkat version as Secondary and even Multislot1 but still it was unsuccessful. Patched the ROM as multi, then the S5 patch for the rom, then the kernel. Maybe the primary ROM that I am using now is not really good for dual boot.
[Galaxy S 4 i9505 Original Android Development] monkteo:
If you have S5 (like my) in multislot 1,2 or 3 it's practically impossible to install (because the direction to install it's in catch and the catch on S5 it's around 250Mb so it's not space) any way, in the last 1 or 2 weeks I can't install nothing in secondary or data-slot, no idea way.

Mai by [MENTION=4277844]chenxiaolong[/MENTION] help us
[Galaxy S 4 i9505 Original Android Development] SaschaHa:
Just an idea for future releases. Wouldn't it be useful, if user apps could be used from multiple roms? So maybe there could be used another folder for apps which will be mounted into the app partitions of the selected roms. So we could use all our apps in both or more roms without the need to install them twice. Would that be possible if we create mount scripts?
[Galaxy S 4 i9505 Original Android Development] ROBSONMEG:
Can't update primary rom don't know why I patched the zip and tried to flash it and it won't do anything says can't be flashed on rom that is in use.
[Galaxy S 4 i9505 Original Android Development] gaww:
I am assuming you are on a S4 not a S5. The Stock TW would not impact your being able to patch and install to MUlti.

What Patcher version did you use?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
If you are trying to flash from within the current (primary) rom it will not work. You would have to boot to recovery and flash primary ( patched zip) from there.
[Galaxy S 4 i9505 Original Android Development] kees1982:
I had succesfully created a dual boot for JDCteam AOSP 5.1 ROM as secondary.

But after flashing an update, which I also patched, it looks like 'data' of the secondary ROM was wiped and all settings were gone. What did I do wrong?
[Galaxy S 4 i9505 Original Android Development] todivefor:
JDCteam roms (my experience is with AntareOne's CM 12.1 optimized) has a line in their updater script:

run_program("/tmp/install/bin/format.sh");

This script formats system as either EXT4 or f2fs. The dualboot patcher translates this incorrectly into format data and system. You need to delete the line:

run_program("/update-binary-tool", "format", "/data");

from the patched updater script.
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
Yes I am using S4 I9505 not S5. I was just referring to S5 theme patch of Imperium. I am using 8.0.0.r1429
[Galaxy S 4 i9505 Original Android Development] gaww:
Per the post a few back responding to you - how did you try to flash ? If with recovery, which one? If you have tried to flash before a few times, your cache (where multiROMs go) may be full. Wipe cache with recovery and try flashing again. I have been using a recent TWRP..
[Galaxy S 4 i9505 Original Android Development] kees1982:
Mmm, indeed. I compared the patched and unpatched zip and the patched one contains a format of 'data'. Tnx for the explanation!
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Just downloaded the latest AntaresOne CM 12.1 but as before when I edit out that line in my patched file it fails to install. Not sure what I do wrong :confused:
[Galaxy S 4 i9505 Original Android Development] -MaD-:
I'm on emotdroid 7.2 with emotdroid R17 kernel on my note 4 (F) and get this.

Any log I can provide? Where can I find it - who can help me? On prior version of the rom and the patcher it worked.

I know the rom is not the actual version, but everything works and I have no reason for an update. Just want to play with some AOSP roms...

Gesendet von meinem SM-N910F
[Galaxy S 4 i9505 Original Android Development] todivefor:
Phil, I have had problems like that at times. I think it has something to do with signing or something. If I extract the updater script, make changes, and then rezip, it never works for me. If using 7-zip, I browse the zip and pull the updater script, modify it, and then drag back/replace it works. This kind of replaces the file without extracting and rezipping. Maybe someone can explain what the difference is.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Ah right.

I'm using my iMac I'm guessing you are using Windows. I'll have to find something that allows this or boot it into Windows and try your way :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have a macbook pro, but run parallels for windows. If someone can explain how to rezip with the changed updater script you will be all set. In the meantime, link me to your file and I'll make the change.
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
This is what exactly I did. Flashed the stock 4.4.2 using SPFT since there was no way to flash it because I don't have a flashable zip of the stock rom. So after flashing the primary and rooting it. I installed the DualBootPatcher-8.0.0.r1429.gcc233fe on my phone. Then I patched Imperium, the S5 theme patch included, and the kernel. Then I set the Kernel of the stock 4.4.2. Then flashed the Imperium, s5 theme, Imperium Kernel. There must be something wrong with what I've been doing.

I'm using Philz by the way.
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
hello brother, in note 3 some kernels cant be patched. it keep on giving error patching failed. please check this post,. i believe you can fix this, if you get time please consider our request.

thanks in advance.
[Galaxy S 4 i9505 Original Android Development] gurumachaz:
Primary : Audax Rom - Shinto Kernel

Data slot 1 : Darkera's S6 port Rom. - DarkQueen Kernel

Works perfectly.*

No bugs detected.

No lags.

Thank you a million [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Galaxy S5 (klte 900F):

Primary : CM12.1

Secondary: BlissPop

Working for now, but the Gapps I have (from CM repos) doesn't want to be patched for some reason (for secondary slot).

NVM, downloaded Gapps from here and worked all good :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
Try to patch it from the rom (from the slot)work for my.

1.TW Echoe

2.Temasek CM12.1
[Galaxy S 4 i9505 Original Android Development] gaww:
I forgot - did the flash fail or the boot? In any case, I would try to flash with TWRP. I used it to flash serveral versions of Imperim and S5 patch with it with no problems using TWRP.
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
The flashing of Imperium ROM as Multi then the S5 Patch as Multi were both successful. The Kernel failed.
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
Works perfectly on Samsung N910f, Dr Ketan L4 Rom as Primary with Emotion kernel (R18, latest release) and CM Remix as Secondary. Only issue is the 'update ramdisk' (share apps) when I try it in the primary rom. Any suggestions.

Thank U.
[Galaxy S 4 i9505 Original Android Development] gaww:
Then you have a small problem - just the kernel.

Make doubly sure you have selected one that is set up for your carrier and your version of android. Use a patched kernel zip between flashing different kernels, as some of the system files can be otherwise carried.over.
[Galaxy S 4 i9505 Original Android Development] peppet:
I'm on n910f, dr k l3 as primary and resurrection ad secondary. Share apps likr a sharm in secondari. I've A problem to boot into primary. How i can do it?

Inviato dal mio SM-N910F utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] gaww:
Did you set Primary kernel before you flashed Secondary?

If not, you will not be able to boot into primary Quick fix is to flash a primay kernel and then set its kernel. Or, patch Primary ROM and reflash.
[Galaxy S 4 i9505 Original Android Development] peppet:
Thanks. No, i can set primary kernel in any way but at this moment i update a primary ROM and finally swap work well.

Is There a way to choose the roms on boot (like PC dualboot)?

Inviato dal mio SM-N910F utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
It will always boot to the last used rom, you can alternate within the patcher app or dual boot utilities in recovery.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Major behind-the-scenes update coming tomorrow. It should fix many boot hanging issues and issues where the bundled kernel won't boot. Stay tuned!
[Galaxy S 4 i9505 Original Android Development] rlorange:
God damn you are a dedicated mofo!! Once of the last of the old school devs left on xda...
[Galaxy S 4 i9505 Original Android Development] arealmanzter_2:
But did I do the right thing? I mean what I did was just flash the stock via ODIN then root and flash Philz. Then install the patcher. Then patch the Imperium rom, s5 patch, and Imperium Kernel. Then to start everything I set the rom of the stock 4.4.2. Then flash the Imperium, S5 patch, and Kernel? Because I need to make sure there was no problem with the previous step I've taken. Not really sure if I did the right thing. There is no need to patch the Primary, right?
[Galaxy S 4 i9505 Original Android Development] gaww:
Everything is right except flashing the kernel on the Imperium ROM. You don't need to patch primary - just makes it easier to update it down the road.

I would wipe the Imperium ROM with the Patcher utility and flash Imperium and the S5 patcher again and boot up. If all is running fine - stick with it for a while aad focus on app sharing.

When your setup is working good, make a complete backup before you try a kernel on Imperium (it comes with a pretty good kernel however).