yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much!!

I must say that you are really responding very quickly!!

To be quite frank, I haven't rooted my phone yet (it's fairly new).. Then, why in the world, did I ask you to add support for my device?? I just wanted to make sure it supports it, so that I could root. I don't want to root unless your awesome software works on my device as there aren't many good ROMs for this phone..

Sorry to have bothered you, but I'll definitely try this as soon as I root my phone, I'm sure..

Thanks again
[Galaxy S 4 i9505 Original Android Development] Indha Lezzio:
Hi all

Firstly I'd like to greet the OP. I do not what's better: the app or ur behaviour, whatever is the winner just have to say: CONGRATULATIONS

I've been testing the app and 've been able to install more than one rom but i still do not get the point of how to use app sharing properly. I've tested several approaches but i never get what i think that is pretended: open the app in any rom using the same data.

Would somebody kindly show me the (best) way to share apps and its data between roms? And secondly, Is it possible to share paid apps?

TIA and cheers
[Galaxy S 4 i9505 Original Android Development] Andycar:
Thnaks for the clear explanation. I was wondering, if we use simple "global" sharing, is there a technical possibillity to set the same UIDs on the data folders of each globally shared app?

Do you think this can be done?
[Galaxy S 4 i9505 Original Android Development] nutpants:
Can you support meliusltecan mega 6.3

Partition table is slightly different from European model

Partition table

pastebin.com/1juzNUVv

If you need any other info just ask.

Thank you.
[Galaxy S 4 i9505 Original Android Development] kotzir:
[MENTION=4277844]chenxiaolong[/MENTION] can you add support for my loganre? (Galaxy Ace 3 LTE) Here is the relevant commit
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] it seems that since a few versions this can't dual boot TW ROM's on the Exynos Note 4 (same ones it was able to), the phone remains at the "Samsung Galaxy Note 4" boot logo for about 1 minute and then reboots to recovery, even did a full wipe of all my ROM's, no TW ROM boots.

I will post the logs from the zip later today, unfortunately can't do this right now.
[Galaxy S 4 i9505 Original Android Development] sronweb:
You are right. I had the same experience. I noticed a message in the phone about a third part app modifying the kernel or bootloader (I can't remember) but finally I get no success to restart primary rom (TW) on my phone which is S4 i9505.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Any chance you could send me the boot.img file in /sdcard/MultiBoot for the broken ROM? I think it would be far easier for you to test changes if I send you modified boot.img files vs. repatching and reflashing the entire ROM again.

Also, could you could how many seconds it takes from when you turn on the device until it boot loops? Is it consistent? Since it's crashing so early and not logging anything useful, I'd like to go for a brute force approach to debug this. I'll add a few sleep statements in the code so that, for example: it it takes 5 seconds longer, than it finished searching for devices; if it takes 10 seconds longer, then it finished mounting filesystems; and so on.

Thanks!
[Galaxy S 4 i9505 Original Android Development] nds850:
[MENTION=4277844]chenxiaolong[/MENTION]

Sent you a donation for your work. I really appreciate it :)
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
I have attached the boot.img (just remove the log in filename). Just noticed something strange, primary and data-slot are the same room (for testing). But boot.img of primary is 16 MB and boot.img in data-slot is 8,18 mb.

I counted the time. From the vibration when turning the phone on it's 7 -8 seconds until it starts again.

Another question. Is it possible to flash a patched anykernel? I mean a kernel that comes without ramdisk and takes the ramdisk from the ROM? The most popular custom kernel for OnePlus is such a kernel.
[Galaxy S 4 i9505 Original Android Development] gaww:
I have not had any issues with TW ROMs in my S4 other than being sure they are not larger than the partition they are being flashed to. Currently have a 4.4.4 TW primary and a 5.0.1 TW Multi ROM. So your issue is not TW related but something specific to your setup.
[Galaxy S 4 i9505 Original Android Development] empat:
Hi! Congratulations for this fantastic work! Great job!

I have a tiny question: I have a note 4, using a TW rom as the primary, and a AOSP as secondary. Is it possible to update the app, to benefit from the last improvements, without a full wipe of the roms? I searched for this information, but didn't find anything.

Thanks, and congratulations once again!
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I have the trltetmo and I couldn't get dirty unicorns to boot from the external. And I do have more than 2 partitions
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I've attached a modified boot.img that pauses for 5 seconds at various points. It should take 5, 10, 15, 20, 25, 30, 35, or 40 seconds longer to bootloop depending on how far it gets along the boot process.

The difference in the boot.img size is normal. When a patched ROM/kernel is flashed, it unpacks the boot image and adds a file named "romid" to the ramdisk (which contains "data-slot-1", etc.). The newly packed file it creates in /sdcard/MultiBoot will have the correct size. But when you use the Set Kernel function from the app, it just dumps the entire boot partition, so the file size will be larger.

Regarding anykernel, there should be no problems flashing that. Since it modifies the ramdisk, you'll need to switch to the desired ROM before flashing it. Otherwise, another ROM's ramdisk will be affected.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I think I may have found an issue with the FAT32 mounting that may cause the card to not show up (I just noticed that your card was FAT32 from the logs you last sent me). Let me see if I can find another SD card so I can do some testing.

EDIT: Successfully reproduced, tested, and fixed in TouchWiz on my Note 4. Once I make sure it's fixed for AOSP-based ROMs, I'll make a release.

EDIT2: Fixed in 8.0.0.r1662.g7378554! You'll need to update the ramdisk from the app.
[Galaxy S 4 i9505 Original Android Development] gaww:
You can update the app without doing anything if you have an app newer than 8.0.0.r436 (which is pretty old).
[Galaxy S 4 i9505 Original Android Development] empat:
Thank you very much for the information! So I just install the new apk above the old one, correct? Regards!
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes - have done so a few times.

If you want to flash ROMs to the external, you probably need to repatch the ROMs I believe but have not tried that yet. The data stays on the internal.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
From the first vibration when turning the phone on until the OnePlus logo disappears and it vibrates again are exactly 11 seconds. I grabbed the logs and attached them.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Huh, if that's the case, it doesn't look like it's getting past the argument parsing step. I originally added some code so that running "/init --help" would show some help text. I've disabled that in this boot.img so hopefully it gets a little bit further.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
You're a genius!! It's booting now!

It took ages to get past the OnePlus logo because of the pauses and I got more and more nervous ;)

I have to bow my head and say thank you again.
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Great news. Thanks. I will test and report back.

Update: [MENTION=4277844]chenxiaolong[/MENTION], can you add melius3g & melius3gxx to the Mega Intl version for the next release? Partition is similar to the lte version.

Update 1: Cannot switch roms from any rom apart from primary rom. Get the error shown in the attached screenshot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Will be added in the next release :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
No problem at all! Let me know when you're ready to root your phone :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks!! :highfive:

App sharing is still somewhat of a pain to set up properly. To use shared data, for say, Chrome: From the primary ROM, install Chrome, check shared data from the app sharing settings, and reboot. Now Chrome (in Primary) will look like you cleared its data because the data folder is now set to a new location in /data/multiboot that can be accessed by every ROM. Now from the secondary ROM, install Chrome, check shared data from the app sharing settings, and reboot. Chrome in the secondary ROM will use that same data folder. Of course, it doesn't have to primary and secondary. It can be any two (or more) ROMs.

If you have any questions, feel free to ask ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The global sharing options just literally mount the /data/app and /data/data directories from the primary ROM to a multi-booted ROM. If we want the UIDs to match, we would need to copy the /data/system/packages.xml file from the primary ROM, but that would break system apps. Unfortunately, Android's package management system isn't very flexible with how it works.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done in 8.0.0.r1662.g7378554 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Cherry-picked to master branch and will be in 8.0.0.r1665.gaed06ef.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you for the support! :highfive:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Absolutely! Just install the latest version of the app.

Also, if you patch, for example, a CM nightly with the latest app, and flash it, you automatically get the latest changes.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! Thanks so much for being patient and helping with the testing! The changes have been included in the latest build (8.0.0.r1662.g7378554).

[MENTION=2449563]Chevelle1768[/MENTION]: Would you mind checking to see if this build also fixes the issue on the LG G3?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, I know for sure multiple partitions won't work right now. I might try adding support for it tomorrow though. When you boot into Android or Recovery, which partition does it mount?
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
genius dev!!!

you are a genius man thanks for all your work!

now the only thing that needs is data in the external sd and I dont know if you want to change the name to something else because is not just a dual boot patcher anymore is more than that.

maybe MBM Multi Boot Manager?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Well I use link2sd to mount my ext4 partition, so it mounts both on boot because I need more space for my apps.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Many thanks for your feedback. It's an important confirmation for me then I will check in the next days.
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
I'm on note 3(hlte) and every time I update the ramdisk I get a bootloop, any idea how to fix it?
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi all!

Thanks for the new build chenxiaolong! Some reports:

Melius:

Installed 1655 on primary and updated the ramdisk. Extsd is seen after a reboot! I flashed a rom (a Silesh.Nair build i used with earlier builds of Dual Boot Patcher but of course i patched the rom again with 1655) to extsd. Also this rom sees the extsd. The only (new) problem: i installed the apk in the secondary rom to be able to switch to the primary. When trying to select the rom i get following error: "could not determine the boot partition because this device's codename 'melius_intl' is not recogized". I used Dual Boot Utilities to switch to Primary. What is new in Dual Boot Utilities is that it now sees only my primary rom. Maybe it has something to do with the name change from 'Melius'?

Thanks for all the hard work!

EDIT: Matissewifi works fine. Problem was the primary rom.

EDIT: for the Melius problem: the rom i have installed was also patched with 1655 not with older apk's just to be not confusing
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Latest build I can't update Ramdisk
[Galaxy S 4 i9505 Original Android Development] Silesh.Nair:
Try the attached zip file.
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Works Silesh. TA! Only the problem with switching inside the app left now.
[Galaxy S 4 i9505 Original Android Development] nilesh.remo:
im on s4(gt -I9505) first rom primary(official tuchwiz 5.0.2 built no. LRX22C.I9505XXUHOD7) i trying to install secondary rom(jdcteam cm12.1 letest built ) failed to install pls help. .what's rong with me ..i am also try data slot ..sorry for my bad eng...attach log file
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] here is the recovery log, the multiboot log and last kmsg from my failed TW boot, if you need other things tell me.
[Galaxy S 4 i9505 Original Android Development] Indha Lezzio:
From ur kind words i understand that i just have to share only data in primary, then reboot, now is when i switch and install apk in other(s) rom(s) and then share its data. Is that correct? (Just in order to be sure)

So i assume that sharing the apk is not (yet?) a good idea?

1000 thanks :highfive: I think ur app is not well known yet. It's amazing buddie!!!
[Galaxy S 4 i9505 Original Android Development] empat:
Hi! Asking again for some advice!

I am trying to share apps between two different roms. On a note 4,one of them is TW, the other one AOSP. when I try to share the apps on the primary one (TW), it says it doesn't have mbtools, that I have to update the ramdisk. I am using the last version of the app. Any ideas about how shall I proceed?

Thanks and regards!
[Galaxy S 4 i9505 Original Android Development] nutpants:
On the Canadian mega 6.3 i527m

I hang after flashing the second Rom, hang after ramdisk upgrade.

Logs attached

If you need anything else let me know.
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Anyone get a lot of app crashes on app share? I just did a clean install, used titanium, and enabled app sharing. When I rebooted, a had a lot of issues with my apps fc
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
So if I want to flash an anykernel for data-slot i have to switch to the data-slot rom and reboot before i flash the kernel? In-app flashing or recovery?

Flashing instructions for the kernel are as follows

(dirty) flash rom and flash kernel in same recovery session, no reboot inbetween
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

Like I use no longer, I tried to translate to the best I could, the french, sorry for the possible errors!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The kernel for the ROM you're using is bigger than the boot partition. The end of it (at least 8.7 KB) is being chopped off. I'm surprised it's actually booting. Unfortunately, there's nothing the ramdisk update feature can do if part of the kernel is missing.

08-30 08:40:46.678 21504 23771 E libmbp : Ramdisk image exceeds boot image size by 8704 bytes
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Starting from 8.0.0.r1671.g4c4448e, DualBootUtilities is built as part of the snapshots. That way, it's always up-to-date with device support.

Regarding the broken switching, that should be fixed by simply updating to the latest apk. If it doesn't work, let me know, and I'll do some debugging :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
You ran out of space on /system when you tried to install to secondary. Does data-slot also fail? Do you have the logs for that?

failed to mkdir /system/app/webview/lib/arm: No space left on device
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The Exynos Note 4 has a /proc/last_kmsg??? (Sorry, I have to recompile the Snapdragon Note 4 kernels just to enable this feature, which is quite annoying...)

Do you have an sdcard inserted in your Note 4? I think I may have found an bug in the extsd-slot code where the device will not boot if the sdcard is removed.

EDIT: Fixed in 8.0.0.r1674.g1719d9d
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That's correct! :) The shared data was just an example. You should be okay to check the box for shared APK as well.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The ramdisk update option in the ROM Settings part of the app. Once you do that and reboot, you'll be able to access the app sharing settings.

If, for whatever reason, your phone no longer boots after the ramdisk update, you can undo it by: rebooting into TWRP, tapping "Install", tapping "Images" (bottom right corner), and flashing /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img
[Galaxy S 4 i9505 Original Android Development] george stamatos:
If the ramdisk is not updated, is it a problem? Switching roms just fine, everything ok, but on my tab pro8.4 I cannot update primary rom ramdisk [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
By hanging, do you mean it hangs at the Samsung logo? If so, when it hangs, could you force a reboot into recovery (without shutting down**) and flash the attached zip? The zip will dump a bunch of logs to a .tar archive in /sdcard/logs/. Thanks!

**Some Samsung devices clear the last_kmsg log when the device is powered off, so if you could reboot it without pulling the battery, that would be great. You can usually force a reboot by holding down Pwr + Vol Down for 10 seconds (and then the normal Vol Up + Home to get into recovery).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Okay, if you have to dirty-flash the ROM in the same recovery session, then there's nothing to worry about. Just patch the ROM and anykernel and flash both in the same session :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you very much! :highfive:
[Galaxy S 4 i9505 Original Android Development] nutpants:
Attached zip?

No I don't get the boot logo. Just a black screen

Same black screen after flashing 2nd Rom or doing a ramdisk upgrade

And yes I can reboot with the power button

(Holding it for ten seconds to force a reboot)
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
http://www.mediafire.com/download/7fbfolly4i20hjr/20150831.140931.tar

thank you very much, I hope it is useful

Enviado desde mi Lenovo K50t5 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, sorry, forgot to attach it!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Nope, it's not a problem. Updating the primary ROM's ramdisk to use mbtool enables app sharing and on some devices where TouchWiz screws up SELinux labels for other ROMs, fixes that issue. If your current setup works and you're happy with it, don't worry about updating the ramdisk.

BTW, the ramdisk update log says you were updating it for extsd-slot-cm12, not primary.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Added support in 8.0.0.r1677.g3b693ff. I've never tested this on a device with a mediatek SOC, so I don't know if it will work or not.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
I did have an sd card in my device and only the TW ROM's were not booting, AOSP was booting ok.

Will try that version tomorrow and report back.
[Galaxy S 4 i9505 Original Android Development] nutpants:
I went back and found the zip previously posted

So here is hoping it works

Flashing the back up of boot img in the multi boot primary folder gets me booting my primary again

The logs add I could get them

I updated ram disk tried a log flashed secondary rom, tried a log and I'm not really sure where the third one came from, our maybe where the first one came from...but I know I started with none...
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Successfully patched s6 rom 5.1.1
[Galaxy S 4 i9505 Original Android Development] FeyoMx:
thanks for the great job, but unfortunately does switching between roms

I leave the logs to see if something can be done
[Galaxy S 4 i9505 Original Android Development] empat:
Thank you once again for the app, and your kind and efficient support. Really appreciate that.

Regards!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Thank you so much!!

I must tell you that this phone has two versions - K50-T5 (International and Chinese version) and K50a40 (Indian version) - but they both are the same device.. But their ro.product.device should be different. Will that be problem why switching ROMs didn't work for [MENTION=5087169]FeyoMx[/MENTION]??

Thanks a million times..
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hi chenxiaolong,

Switching roms inside the app works again, thank you!

Regarding the app sharing *again* (sorry for bringing it up again but i want to understand this system): i did the chrome example you gave and it worked. The answer you gave about enabling "app" tells me that this setting does nothing. Or am i wrong? I mean: i installed chrome in both roms and enabled "data" sharing in both roms so data is centralized. Enabling "app" sharing should be ok you wrote above but what's the use of this setting? Currently doing nothing?

Thanks!

Forget the edits. Found the problem. It was a problem with assert lines in zips. Sorry.
[Galaxy S 4 i9505 Original Android Development] Andycar:
It seems I reported it already. Anyway, will try with the new version. Thanks!
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] it still doesn't work and even more it gave me an error on flashing zips patched with the new patcher about being unable to execute the update binary and even kernel zips formated my system partition and left it empty (why and how?) also I forgot to say that in TW ROM's I can't set kernel or update the ramdisk, which was happening before and it still does.

Ataching multiboot log only as last kmsg and anything else is not useful for trying to boot with an empty system partition (yes, I actually did it before checking my partition was in fact empty, lol).
[Galaxy S 4 i9505 Original Android Development] Chevelle1768:
I can confirm that they can boot now. :highfive:

Couple of other things thou.

Trying to update ramdisk gives me boot failure (needs to bump boot.img)

Would be nice to include a ".nomedia" with in the boot.img directory (So gallery doesn't scan for images)
[Galaxy S 4 i9505 Original Android Development] empat:
Hi!

Just to report, I tried the described method. It was impossible to boot after that, and also impossible to revert back using TWRP as suggested. I restored a nandroid backup to get things normal again. I am using a Galaxy Note 4, TWRP 5.0 as the primary ROM, AOSP 5.1 as the secondary one.

Will keep trying! Otherwise, everything working perfectly! Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What error does it give when switching ROMs or does it fail with no error? I'm not seeing anything out of the ordinary in the logs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, both of those are in the list so they should work... unless I made a typo: https://github.com/chenxiaolong/Dua...09521511820bd44/libmbp/patcherconfig.cpp#L583