yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Delete
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Thank you again for looking at my problem although I might be the only user with OnePlus One.

I attached the log. I used latest patcher version.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Strange but not problematic !

I can't install it from recovery (PhilZ) on data-slot, but from red button in the patch everything was OK (patch 1607)

This is just a mention !
[Galaxy S 4 i9505 Original Android Development] nds850:
Just installed a ROM to the ext sd card and it is working flawlessly! Really impressed with the performance, great job [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] george stamatos:
Just installed second rom on ext sd on my tab 8.4, and it's working flawlessly! Thank you GREAT DEV!

Only thing is that I can't access ext sd folders. It seems it's not mounted. Maybe it's roms fault. No big thing
[Galaxy S 4 i9505 Original Android Development] Andycar:
Dear [MENTION=4277844]chenxiaolong[/MENTION], I flashed the latest CM12.1 nightly on mu Note 4 N910G extSdCard slot, booting up nicely, however in the Android interface I'm geting "unknown version/buid" ... Any idea?

Thanks so much for all new lovely features!
[Galaxy S 4 i9505 Original Android Development] Andycar:
The new extSdCard slot method is so cool! I even could mount system.img and modify it with ImDisk/ext2fsd in Windows, after that it still boots nicely from extSdCard slot! Wow :)

I noticed a strange thing...

If I have extSdCard slot in my multiboot setup (not necessarily active for boot), and power off my phone (N910G) and took extSdCard away, then try to boot to primary (TW) it would not boot to primary, but reboots to recovery.

However, if I insert back my extSdCard, the phone would boot normally.
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Can you please explain how to do that for data to be install in external sd?

Thanks!!
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
I am having a similar issue on my LG G3 (vs985). If I patch a zip file, flash it, reboot it sits there on the LG logo then goes into a kernel crash.

If I patch the same zip with v1460, it boots fine.

Attached are my logs.
[Galaxy S 4 i9505 Original Android Development] Andycar:
I'm not saying I've installed data to external. I don't think that putting /data and /cache on external is currently implemented. You've seen Chen's explanation post, haven't you? ;)
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Yes sir was a misunderstanding from my part thanks for the help!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll need to take a closer look to figure out why these issues occur after school. Could you send me the boot.img files in /sdcard/MultiBoot/ for every ROM where the external SD doesn't work?

As for the ramdisk issue issue, reboot into TWRP, tap install, go to /sdcard/MultiBoot/primary, tap the "Images" button in the bottom right corner, and flash boot.img.before-ramdisk-update.img. That will restore the kernel to how it was before the ramdisk update.
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
See this post http://xdaforums.com/showpost.php?p=46537673&postcount=544

Both ROMs have to be the same Android version and the secondary ROM has to have init.d support.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Thanks! Does the script file need a specific file extension? Also, how do I put the file in that directory? I put it on my SD card and when I try to copy it to system/dual/.... it just fails. Do I need to SSH into my phone?
[Galaxy S 4 i9505 Original Android Development] mkhattat:
No need for a specific file extension, just a name without file extension.

Do you have root? What is your file manager ? I've never used ssh for it. Just copy the script to /etc/init.d folder if you are on the secondary rom using root browser, fx or something else with root access. (You have to remount the folder in order to write into it)

PS: don't forget to set the permissions.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Thanks, I tried another root explorer called "Root browser" and now it worked.

Just one last question, what permissions should it have? Right now it's rwxrwxr-x

EDIT: Just saw that someone wrote "777". Thanks! It didn't work though so I guess the google edition doesn't have init.d support. :/
[Galaxy S 4 i9505 Original Android Development] mkhattat:
Removed
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
It says on the rom thread that it does have init.d support so I must be doing something wrong. I've got the right permissions and from the primary rom I put the file in system/dual/etc/init.d/ and the file is just called "run" without any extension. Both roms are running android 4.3

There is another file in the init.d folder called 99SuperSUDaemon . Is this ok?

I don't really need all apps on both roms, just whatsapp. It's so annoying because it needs to re-verify everything every time I switch between the roms.
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
I had the same problem with mine, the only difference being is that i had a 4.2.2 ROM as primary and the GE 4.3 by Jamal as secondary. I gave up on it and deleted the secondary ROM and ill be trying different 4.2.2 AOSP ROMS once they are patched.
[Galaxy S 4 i9505 Original Android Development] Obsidian_soul:
[MENTION=4277844]chenxiaolong[/MENTION]

Will this work for hyperdrive Rom?

from my KToons Hyperdrive X powered Galaxy
[Galaxy S 4 i9505 Original Android Development] mateopase:
Yup. You'll have to patch it by yourself using the instruction in the OP, but it'll work. Unless you mean running Hyperdrive as the Primary ROM, in which case you don't have to do anything but patch the secondary ROM.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Oh ok, then I guess I wont put much time on it right now. Both my roms are 4.3 and it still doesnt work.

If I either want to wipe the primary rom or the secondary but not both, I use DualBootUtilities right?

If I then want to flash either the primary or the secondary rom, do I just flash the primary rom as usual and secondary according to the instructions on the first page here?
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
yessir. Some 4.3's you need to format the data and system for some reason. Im not saying thats your problem exactly but its what comes to mind! Careful with that priamry wipe too.. oooo weee!
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
It must be the secondary ROM that doesnt support init.d then (i didnt look to see if it does)

Yes use dualbootutilites to wipe either rom

Yes flash primary as usual and patch secondary.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Ok, thanks!

That's the weird part, the rom does have init.d support.. At least the developer (jamal2367) says so. Its the 4.3 google edition rom that can be found here
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
id love to get some stock in my life bc my me7 is Bricked beyond belief.... as soon as i get it working again im always in to test things out! ps: anyone got a RIFF BOX, JTAG?? haha. ill send you my shizz and then test whatever yall want!!! thanks and keep up the good work!
[Galaxy S 4 i9505 Original Android Development] The1nonly1:
Have you tried any other 4.3 Google ROM, i think their is another one listed on the first page of this thread, I'm going to update to Omega 4.3 at the weekend.
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
How would one patch an aroma rom?

Sent from my PAC'd/touchwiz dual boot S4
[Galaxy S 4 i9505 Original Android Development] !Led*Eyes!:
I would imagine just que the modules.zip right after the rom and flash all at once. Then go through the set up process...
[Galaxy S 4 i9505 Original Android Development] shremi:
Hi Chen

Would it be posible to add support for ktweaker kernels other tan AOSP ????

I am currently trying to get everything to work on my att but it seems that is not that easy due to de locked bootloader so i am going to give it a try again tonight . On my girlfriends i337m everything was really easy.

TIA

Shremi
[Galaxy S 4 i9505 Original Android Development] ad346:
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] chenxiaolong:
Glad it's working for you! Unfortunately, the external SD doesn't show up if my mount parameters don't match your ROM's mount parameters exactly (the ROM will try mounting it, fail, and then not register that the card is inserted). I'll need to think a little bit about what information I need to fix this, but as a temporary workaround, you can access the external SD card contents at /raw/extsd with a root file explorer.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Really glad you're enjoying it :) The unknown version and build error occurs because Android can only see the raw image file in [External SD]/multiboot/[your ROM]/system.img. It doesn't have a way of seeing the contents inside. I should probably replace those with a better message.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm really happy it's working for you! :D

The reason it reboots to recovery is because you're still switched to the extsd-slot ROM. When it tries to boot, it can't find the card, so it's throws you back into recovery. If you switch to any other ROM beforehand, it won't do that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For anyone using extsd-slots on a Galaxy S4 (Snapdragon variant) or Note 4 (Snapdragon variant) and the external SD doesn't show up in the OS, please send me a link to the ROM (and custom kernel, if used). I know this issue happens for some people, but I don't know what info I need to fix it yet. I'd like to do some testing myself to figure out what's going on.

EDIT: Also need the size of your SD card, the filesystem on it (exFAT, FAT32, ext4, etc.), and whether you formatted it to have more than one partition.

Thanks!
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Can the dalvik cache can be deleted for primary and data slot without any problems? Because some how I'm running out of space in my internal and I can't find how thanks!!!
[Galaxy S 4 i9505 Original Android Development] bailey2408:
[MENTION=4277844]chenxiaolong[/MENTION] - All I can say is wow! Excellent job your'e doing here- one of the coolest and most responsive devs I've seen. I am an admitted flashaholic and the time it took switching from nandroid to nandroid was frustrating but I tolerated it (not to mention having to backup and restore data for games as I switched between roms- enter data sharing- whoo hoo!). Finally stumbled upon this and what a breath of fresh air. Running nicely on a t-mobile note 3 and just installed a tw rom to external with no issues (did take a long time as you stated) and can switch between extsd roms and internal roms seamlessly. I also finally purchased a 64gb card to replace 32gb due to this gem of an app. Please keep up the good work and development on this project!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! I'll have to take a deeper look to figure out what's going on. It's very odd how nothing related to dual booting is logged. Either the logging is broken or it's crashing very early. Both devices look like they're having the same issue, though the OnePlus crashes in 2 seconds vs 31 on the LG G3.

OnePlus One:

[ 2.491508] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 2.491511]
[ 2.491662] [<c010cc7c>] (unwind_backtrace+0x0/0xfc) from [<c0aa00a4>] (panic+0xa0/0x1f0)
[ 2.491746] [<c0aa00a4>] (panic+0xa0/0x1f0) from [<c018f47c>] (complete_and_exit+0x0/0x20)
[ 2.491793] [<c018f47c>] (complete_and_exit+0x0/0x20) from [<f6148000>] (0xf6148000)
[ 2.491878] CPU0: stopping
...

LGG3:

[ 31.483930 / 01-22 21:16:53.529] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 31.483935 / 01-22 21:16:53.529]
[ 31.483961 / 01-22 21:16:53.529] [<c010be7c>] (unwind_backtrace+0x0/0x11c) from [<c0b22a84>] (panic+0x8c/0x1e8)
[ 31.483977 / 01-22 21:16:53.529] [<c0b22a84>] (panic+0x8c/0x1e8) from [<c01a54c0>] (do_exit+0x370/0x7a0)
[ 31.483991 / 01-22 21:16:53.529] [<c01a54c0>] (do_exit+0x370/0x7a0) from [<c01a5968>] (do_group_exit+0x4c/0xb0)
[ 31.484001 / 01-22 21:16:53.529] [<c01a5968>] (do_group_exit+0x4c/0xb0) from [<c01a59dc>] (__wake_up_parent+0x0/0x18)
...
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Thanks for looking into it. I have zipped up the entire Multiboot folder from the sdcard. You can access it here.

I also have another small issue where the patched rom files don't flash in recovery. I use twrp. I saw someone else reporting this too. It flashes fine using the app. Attached the Multiboot.log file if you wanna take a look.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll take a look at the MultiBoot folder after work tomorrow. The TWRP flashing issue is caused by TWRP reporting the device as "meliuslte" instead of "melius" or "meliusltexx". I've update the list of codenames in 8.0.0.r1654.g121c158, so flashing from recovery should work now.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi chenxiaolong,

First of all thanks for implementing Melius!

I flashed 2 extra roms on my Melius. All goes well, roms boot fine but only 1 time. From the second time i boot in any extra installed rom all apps start FC'ing. I did not did the ramdisk thing in the primary rom and app sharing is not being used. Any idea what i do wrong?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Is your primary ROM a TouchWiz ROM? If yes, there's a very good chance that the init scripts are running:

restorecon_recursive /data

That resets the SELinux label on all the files in /data, which very likely causes the FC's because it touches files for other ROMs. If you do a ramdisk update from the primary ROM, it will prevent it from touching other ROM's files. You might need to wipe data for your two broken ROMs after doing this (this can be done from within the app).

EDIT: If the ramdisk update goes wrong, you can always undo it by flashing /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP (go to "Install" and hit the "Images" button in bottom right corner).
[Galaxy S 4 i9505 Original Android Development] nds850:
Tried the app on my Nexus 5 for the first time and it force closes when pressing "Patch zip file" in the menu. Using the latest version off the app and Android M preview 3.
[Galaxy S 4 i9505 Original Android Development] monkteo:
[MENTION=4277844]chenxiaolong[/MENTION],

any idea why it's not possible to flash MIUI on S5 (data-slot or secondary) I try and it's patch OK flash OK but remain hanging on MIUI logo (after Samsung logo)

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

Thank you for the fast help! The primary rom is not a TW rom (it's CM12.1 Temasek) but still your tip helped. Now that i did the ramdisk thing i thought i might as well just use app sharing. I enabled individual sharing in primary and secondary roms. In the primary rom i choose the apk and data for 1 app. This app is indeed in the correct folder /data/multiboot/_appsharing. Still it doesn't seem to be available in the secondary rom. Is it possible that this has something to do with the bug Silesh reported earlier (no ext sd. only in /raw)?

Since this is all new to us i have a few other questions if you don't mind:

-Can requesting the patcher for other devices be done or is this out of the question? I ask because it's in the S4 section.

-When doing your tip i saw "multiboot files" in wipe section in the app. What does this do?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Forget the phone I told you the other day(that Xperia) , I've bought a new one - the Lenovo K3 Note...

So, naturally, I want you to add support for this phone..

Required details:

ro.product.device=K50a40

Details about the partitions are attached.

Would really appreciate if you could do it..
[Galaxy S 4 i9505 Original Android Development] midi_1996:
I have some problem with app sharing, I dont know if I'm doing it wrong or it doesnt work as it supposed to do. What I do is I install app A on my primary rom, enable single app sharing, reboot, select the app from the list (apk+data), reboot, select the rom on my data-slot, enable app sharing, reboot => can't find the app, I install it from P.S, but it FCs as soon as I open it. Same happens if the app is alredy installed on both roms then I enabled its sharing. The all app sharing works but no data (I suppose it's how it should be, it was like that on every rom), and most of them FC!

So is it me who didnt understand the process of sharing the apps, or is it because my roms are from different APIs?

I'm on S5 SM-G900F with stock TW (5.0) and CM12.1 as data-slot rom (as my /system partition is full).

Thanks :)
[Galaxy S 4 i9505 Original Android Development] physwizz:
I found that some apps don't like being shared.

I also found that data sharing starts from fresh data. You could restore data using titanium backup after data sharing.
[Galaxy S 4 i9505 Original Android Development] midi_1996:
So I need to have both ROMs clean then do the sharing, right?
[Galaxy S 4 i9505 Original Android Development] side:
using latest cm12.1 nightly cant install AOSP of JDC team,as secondary.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've been notified by my hosting provider that they need to perform maintenance on their network switches, so https://snapshots.noobdev.io and https://jenkins.noobdev.io might be down for a little bit tonight.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5859390]tropenfrucht[/MENTION] [MENTION=2449563]Chevelle1768[/MENTION]

I looked a bit more into the logs and it looks like it might be crashing because /dev/console doesn't exist in the pre-boot stage. I've updated the patcher so that the files it creates in /dev are the same as what Android creates. If you wouldn't mind doing more testing, could you please try:

8.0.0.r1657.g13c3e37. This build has the changes I mentioned above.

The 8.99.11 debug attached to this post. This is identical to the 8.0.0.r1657.g13c3e37 build except that it doesn't log anything to the kernel log (there's a small chance that might be causing the crash). The debug version will install as a separate app and is named "Dual Boot Patcher (Debug)".

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you send me the /sdcard/MultiBoot.log file after a failed flash from Philz recovery? That should have the details on why it failed. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, man!! That means a lot :D :highfive:
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Please look into my device, sir

I would really appreciate that!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This should be fixed in the latest build (my hosting provider is down right now so I can't check the exact version). It was a stupid mistake on my part that caused the app to crash when it tried to list the contents of /sdcard/MultiBoot if the directory didn't already exist.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When it hangs on the MIUI logo, could you force reboot into recovery and flash the attached zip? It will save a bunch of logs to /sdcard/logs/[date and time].tar. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's actually a technical limitation. For data sharing to work, the app must be manually installed in every ROM first. I plan on adding a dialog that pops up on boot saying something like, "Hey, you enabled apk/data sharing from another ROM. Tap Continue to install these apps and complete the app sharing setup." There's also a lot of UI work I have to do to make this obvious (for example, having the /data/multiboot/_appsharing apks show up in the app sharing list).

If you're interested as to why this is needed, here's one example of what would happen if enabling shared apk/data in primary caused it to automatically show up in secondary:

You enable shared apk + data for 1 app in primary

Lets say that it was automatically installed to your secondary

When you boot into the secondary, Android sees the apk in /data/app (which is a link to /data/multiboot/_appsharing/app/blah.apk), but it's not registered in the app database (/data/system/packages.xml)

App sharing directories and apk links are created

App sharing code tries to fix permissions for everything in /data/multiboot/_appsharing, but cannot find this particular app's UID because it's not technically "installed" yet

Android "Optimizing apps" dialog appears, which actually installs the apk and assigns a UID for the app

Android, as part of its security features, will wipe the shared data because the UID does not match the permissions in /data/multiboot/_appsharing

User is unhappy because the app's data is gone :(

Yes, absolutely!

This deletes the /sdcard/MultiBoot/[ROM ID] directory which contains the ROM thumbnail, ROM name, app sharing configuration, and saved kernel.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you flash the attached zip and send me the tar archive it creates in /sdcard/logs/[date + time].tar? That will give me quite a bit more information (just in case your device needs some special hacks). Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I took a look at those files and it turns out they may not have all the info I need. Could you send me a link to the 3 ROMs you are using? Thanks!
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Primary ROM- Temasek cm12.1 : https://mega.nz/#!Np9FADqI!dyoWec1S-uFb66eCFSVQII1eXwzZHaTuDrv_Fzpz_44

Secondary ROM - Slimlp : https://mega.nz/#!BgUjmbJB!fJpGZM_93xrcDQEgrphopaHJgFhX81sp6IhWBUQKrCM

Data Slot 1 - XenonHD : https://mega.nz/#!NpNykZiR!uQxddIAyvMthjO1P8PSMMwyyLJYIB5xBEfbwOG2ynB4
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi [MENTION=4277844]chenxiaolong[/MENTION],

Thanks for all the explanations! I now understand what the problem is with individual sharing of apps.

To request a device: Is flashing the zip/doing what you ask provided here: http://xdaforums.com/showpost.php?p=62545656&postcount=6811 enough? Or do you need other/extra info?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You're welcome! The archive created by that zip you linked to should be all I need to add support for a new device.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Nice! Hereby the request:

Samsung Tab 4 10.1 wifi only with codenames "SM-T530" "Matissewifi"

The log is attached. Thank you for the efforts!
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Thanks for your efforts but neither one boots. I attached both logs.

By the way OnePlus One and LG G3 are both devices with a snapdragon 801 SOC. Maybe that's related.
[Galaxy S 4 i9505 Original Android Development] physwizz:
I'm looking forward to flashing ROMs onto the SD card but I can't do anything until I get my Tab S back.

The battery died and I took it back. Let's hope Samsung Australia fixes it under warranty.
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
Still does not boot. Now it sits on the LG Logo for about 30 sec then goes to black screen and does nothing, no kernel panic, no adb.