yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ixtlan007:
OK, thank you very much for the reply :)

A friend is working on a solution to unlock the bootloader, if we succeed, I definitely let you know :good:
[Galaxy S 4 i9505 Original Android Development] Bigmar75:
Thank you very much [MENTION=4277844]chenxiaolong[/MENTION]!
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
[MENTION=4277844]chenxiaolong[/MENTION] But the rom containing the file system.new.dat as cm 12.1 and resurrection remix for s4 work with the patch?
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
Del
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
It is not stupid. My ROM and recovery read and write on it, but dual patcher app does not see it in the free space tab. Is there a recommended format for external SD card with dual patcher ?
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
Am a bit confused, the download button leads to 3 files, all from 2014 .. I read this thread to about September and didn't come across any mention ... which one do I install, or am I being directed to a wrong page ... the current version I have is 1777.g650158b ... please advise ... thank U.
[Galaxy S 4 i9505 Original Android Development] todivefor:
You want to go here. Those in the OP are probably the last stable release and are now way out of date.
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
Thank U so much indeed, until the version I have at present, I used to go to those links (just under a fortnight ago I think)... that aside, thank U yet again ... :) :good:
[Galaxy S 4 i9505 Original Android Development] todivefor:
I don't know if those old builds were before or after the major dualboot structure change. If you are under the old configuration, and try the new you have the potential to have problems. I don't remember the build number of the transition. Someone must have this information?
[Galaxy S 4 i9505 Original Android Development] gaww:
Are there any 6.0 AOSP ROMs that can be patched and installed on an S4 ? It would make an interesting ExtSD exercise if there is.
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
Thanks for the heads up .. I'll ask/look around and see if I can find something ... cheers mate ... :)
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
App sharing messed up my ROM! I have been using dualboot for some time with Albe95's LolliRom and S6 rom. Today I just want to try the app sharing. I checked those apps that I would like to share in both roms, now in the multislot rom there are many apps missing, including file manager and dualboot app itself. How am I supposed to restore from this? TIA.

I deleted the config.json file for both roms, but problem is not fixed.
[Galaxy S 4 i9505 Original Android Development] :
Any reason why I can't access the Android/obb folder on my main ROM? It keeps giving me an access denied issue when I try to do so.
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Hi, if I patch cm 12.1 and the majority of its derivated ROMs, when I flash I get a loop on the boot animation.. I tried every slot option, same result.. But if I patch and flash also a custom kernel (in particular Alucard), it fixes everything up and the boot finishes, it optimizes all the apps and Android starts, and everything works.. Am I the only one with this problem? As Primary ROM i have a 4.4.2 TW, if this helps..
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Did you do a ramdisk update (from ROM Settings in the app) from your 4.4.2 TouchWiz ROM? If not, that's probably what causes the issue. TouchWiz unfortunately changes the SELinux label on all of CM's files when it boots so only a custom kernel with SELinux disabled or set to permissive will boot. The ramdisk update adds some code that prevents TouchWiz from doing this.

Try updating the ramdisk from your primary ROM and then flashing CM (or it's derivative ROMs) again and let me know if you still experience the issue.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=6339852]Anubis22666[/MENTION] [MENTION=2688336]todivefor[/MENTION]

I apologize about the confusion about the download links. For whatever reason, the forum is not showing my latest edits in the OP. It's completely different from my latest edit from September 3rd in the edit history: https://snapshots.noobdev.io/misc/XDA/xda-developers - Post Edit History.pdf I've reverted it back to the correct version. Let's hope it stays that way.

Also, for anyone who downloaded the old "stable" versions, please uninstall it. A while back, my DevHost account (along with a few other people's accounts) was compromised. Though I've reuploaded everything that used to be on my DevHost account, no build other than ones obtained from https://snapshots.noobdev.io/ should be considered safe.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Is there anyone who actively uses global app sharing and individual apk (not data) sharing and would be really unhappy to see them gone? It is already extremely hard to get them working properly in KitKat and Lollipop and people still see many issues with it, like having apps randomly disappear. I've been studying the Marshmallow AOSP source for the past few days and from what I see, it will be much more difficult to implement these features, so I will not be putting in the effort to support them (which amounts to thousands of lines of code) in Android 6.0.

So the question is: should I keep them as-is and hide the options in Marshmallow, or should I remove them completely? Again, this does not affect data sharing at all; that is far easier to implement then apk sharing.

I'd much rather focus my efforts on things like data sharing (which will soon work live, ie. without rebooting) and backup and restore. It know it's always disappointing to have features removed, but sometimes, it's just not worth the effort to keep supporting them.
[Galaxy S 4 i9505 Original Android Development] mbonus:
The apk sharing was a pita to get to work for me, I ended up wiping and starting over, so I vote dump it entirely if it makes your life easier. :good:
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
You always have the right idea and all my devices will make pit stops here
[Galaxy S 4 i9505 Original Android Development] Droidphilev:
Hello again chenxiaolong

My opinion: dump the app shaaring completely. It's too hard to set it up IMHO. Backup/restore would be oh so much nicer.... :) Regarding the implementation of data sharing that you mention can you explain exactly which data? App data? If so will it be possible to disable? I already have problems with Play Music seeing shared data in /sdcard/android/data :) (has nothing with Multiboot, it's the same in Multirom)
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4277844]chenxiaolong[/MENTION] same here, tried once and didn't managed to make it work as should so i gave up.. Personally i keep most of my big sized apps on primary, secondary having only what i daily need.. Won't be such a problem (at least for me)..

I wanted to ask you something, i have an old phone at home (samsung s6810p) and i wanted to test dualbooting in it.. My main question is: can i patch the file using any device from the win32 app? Beside the build.prop line (ro.patcher) are there other things modified? And what are the odds to really work? Thank you for your awesome work!! Cheers!
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
dump apk sharing but not data sharing. I only tried the individual apk sharing does not work well with my s5 900f. some apks wont work on different android OS Keep data sharing.
[Galaxy S 4 i9505 Original Android Development] monkteo:
<<So the question is: should I keep them as-is and hide the options in Marshmallow, or should I remove them completely? Again, this does not affect data sharing at all; that is far easier to implement then apk sharing.>>

Never use it !

THX
[Galaxy S 4 i9505 Original Android Development] Anubis22666:
There's always apps like TB that can be utilised for such purposes .. before booting to the other ROM just back up app/data, and restore in the other ROM. I've been doing it ever since I started dualbooting, with nary a glitch or hassle.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
I also vote for dumping apk sharing because I had troubles with it.
[Galaxy S 4 i9505 Original Android Development] nds850:
Me too.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Time would be much better spent on Backup/Restore!
[Galaxy S 4 i9505 Original Android Development] Andycar:
And I also vote for data sharing only, without sharing individual apk.
[Galaxy S 4 i9505 Original Android Development] -MaD-:
+1 for data sharing and backup and restore!

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] nds850:
Has anyone successfully installed a TW ROM on the SD card?
[Galaxy S 4 i9505 Original Android Development] monkteo:
And any one manage to flash a supersu on a rom on SD card ? (patch of course)
[Galaxy S 4 i9505 Original Android Development] gaww:
App sharing is working pretty good on 4.4.4 nd 5.0.1 (Able V6).

If it is dropped to accommodate Android 6.0, could compatibility between the already flashed ROMs such as the above be maintained with the patcher version that will handle Android 6.0 ? Then existing app sharing between the older Android versions flashed with older Duelboot App would continue and Android 6.0 AOSP could be patched and flashed also with updated Duelboot app.
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Support requested for serrano3gxx

Hi [MENTION=4277844]chenxiaolong[/MENTION] ,

can you please add support for the Samsung S4 mini i9190, codenamed serrano3gxx ?

I'm attaching the tar file generated with the GetLogs zip flashed from twrp.

Thank you so much in advance!!!!
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Testing right now...

Mmmh now it fails flashing any 5.1 ROM/GApps.. It says that I have an incompatible ROM.. I'll attach the log in a while

Here it is:

EDIT: I was trying (as I always did) flashing cm as multislot 1; now I tried it as dual, it flashes fine but I still have bootloops :(
[Galaxy S 4 i9505 Original Android Development] physwizz:
I've given up on TW.

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

Both my SD card roms have supersu built in.

---------- Post added at 09:48 PM ---------- Previous post was at 09:33 PM ----------

on a different note, I found that I lost space on my ExtSD card if I wiped a rom from the app.

I don't lose the 2gig space if I wipe using the dualboot utilities zip from inside twrp
[Galaxy S 4 i9505 Original Android Development] karkasss:
Yes I have TW roms on data slot.
[Galaxy S 4 i9505 Original Android Development] corncobman:
First of all thank you very much for this, it's working perfectly on my S5 G900-F klte.

I'd like to ask if the S3 support includes the I9305 model? The reason I ask is that it has different hardware and you can't flash an S3 I9300 ROM on the I9305 and vice-versa.

Thanks.
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
If your device is not yet supported and you want your device to be supported please follow chen's instruction.

may be there is not enough space that is why you got boot loop. when the phone is boot it will need space to expand the system.img. try it on extsd so that you will have more space on your internal storage.
[Galaxy S 4 i9505 Original Android Development] corncobman:
I don't know if it's compatible which is why I'm asking. I haven't flashed anything yet.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
"Failed to run real update binary"

"Failed to flash zip"

This is what I'm getting when trying to flash already patched zip via both ways- inapp and recovery. Tried with different ROMs and using different locations, using Set Kernel option doesn't make sense, can anyone throw a suggestion?
[Galaxy S 4 i9505 Original Android Development] ktm_91:
But if I flash a custom kernel it works fine.. And I also tried not to flash gapps (so there's more free space) and I get the same result :(
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
try installing your app. if you can find your device there in the ROMs tab then it is supported. if not probably it is not. then you can try flashing the getlog.zip then post the logs here and chen will take a look at it.

have you tried updating the ram disk. ? click ram disk update multiple times to force update. if that won't work post your logs here. there is instructions below.

you mean custom rom right? yest it will work fine because mostly likely you flashed clean so there is a lot of internal space.

depending on the size of the rom you might probably needing a lot of space? did you post your logs yet?

https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150919.zip

If a multi-booted ROM is unable to boot, logs will be needed for debugging the issue. Please reboot into recovery without shutting down the device (ie. no removing the battery) and flash the GetLogs zip. This must be done immediately following the boot failure because some logs will be lost after a reboot. The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.

Also, state whether the ROM reboots or hangs at the manufaturer logo or the ROM's boot animation. If the ROM reboots, please state whether it reboots into recovery or not.
[Galaxy S 4 i9505 Original Android Development] Bigmar75:
This works awesome on sm-n920p. Thank you for supporting our device. I haven't tried app sharing yet but I will eventually and report back
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Ok, I'll explain it better than I can :P

WITHOUT updating ramdisk: in whatever slot I flash cm 12.1 (or any cm-based ROM), I get a loop on the cm logo animation at boot, it stays there forever. Now, if I flash a custom kernel (obviously in the same slot of the ROM), at the following boot it optimizes the apps (like I wiped Dalvik/ART cache, and I think this is what the install script of the kernel does), and finishes the boot normally, and I can use the system, it works just fine.

UPDATING ramdisk: I get the same problem as above: loop on cm boot animation.

I already attached a log, but it was the one saved in the internal memory, I think the one containing the text we see in the recovery during flash operations, now I'll recreate the problem and follow your instructions to get the "big" log and attach it to this post

I flashed the last nightly of cm 12.1 as multislot 1 without updating ramdisk, stayed like 5-10 mins on boot animation, forced a reboot into recovery and flashed the zip to save the log, and here it is:
[Galaxy S 4 i9505 Original Android Development] v00d007:
As I already pm'd you I'd really appreciate if you could do some more focus on that annoying boot lag when using cm12.1 roms as secondary.

App Sharing: I think what makes sense to save space and what really works is the sharing of the app (apk) from primary rom. The data sharing never worked well for me, I had lots if mess and also data loss with that.

@ all:

Could you please stop full quoting long posts?! It isn't really that hard to edit a little bit and to avoid polluting this (and other) threads with those masses of duplicated text!
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
[MENTION=5474102]ktm_91[/MENTION] : looks like the issue with kernels being too large once patched for their partition size. Maybe try installing to external SD if you have one
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
i recommend you to follow this instructions. i recreated this step and i was successful. the only missing here is updating ramdisk try to update it coz i failed on flashing when i did not. and i did used extsd. i was successful in flashing cm12.1 and blisspop rom. i did not flashed a custom kernel i just set the kernel on the secondary at its first boot.
[Galaxy S 4 i9505 Original Android Development] ktm_91:
[MENTION=1160716]bilbonotry[/MENTION], [MENTION=5322723]crazyraiga[/MENTION]

Just tried: patched cm 12.1 and flashed by recovery in the µSD, rebooted and.. nothing, same problem :(

P.S. I did everything with updated ramdisk
[Galaxy S 4 i9505 Original Android Development] TimAnd:
Hi [MENTION=4277844]chenxiaolong[/MENTION] ,

can you please add support for Huawei Ascend, in my case it's P7-L10? I'm attaching the tar file generated with the GetLogs zip flashed from twrp.

And if you do, which setting would be fine, dual, multi-slots, data-slots? I read Instructions for dual booting but I'm still not clear.

And I somewhat change my questions..
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
all slots would be fine. but I would recommend using extsd so it wont eat your internal storage.

assuming your device is supported.

download the latest dualboot patcher app. install and update ramdisk and reboot. when patching a rom you should put the rom in the internal storage just for patching and flashing purposes. after successfully patching it you can now flash the patch rom. btw when don't forget to set the kernel on your primary. if your successful in flashing go to ROMs tabs. select your custom rom then reboot. set up your secondary rom. install the dual boot patcher. set the kernel in your secondary rom. the you are good to go. you can switch rom in the ROMs tab by selecting the rom you want to boot.

I also recommend backing up your device.
[Galaxy S 4 i9505 Original Android Development] Andycar:
I managed to install TW ROM from Dr.Ketan (pre-rooted) on external SD of my Note 4 N910G without any problems.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Why 1st updating the ramdisk? It isn't necessary if u don't want to use app sharing. I never update the ramdisk of my 1st rom and atm I got (at least) no flashing or post flashing issues with secondary rom setup (just the annoying +30s boot lag...).
[Galaxy S 4 i9505 Original Android Development] nds850:
I had problems with TW ROM:s that weren't in the primary slot in the past but tried to install to the ext sd and it worked perfectly!

Now running two Note 5 ports and one 5.1.1 TW ROM on it :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi, does it matter if that my phone is not S4, but Lenovo K3 Note? I already updated ramdisk before doing anything within this app and says that ramdisk is up to date.
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
it matters. because if your device is not supported it might not work. you may wanna try it first while for you to find out if it is supported. if not just ask for the developer to get your device supported and wait until your device will be supported.

I don't know but I get flashing issues if I don't update. or there was something wrong that I didn't saw. but I am good now. still searching for the best rom that fits my preference. big thanks to this thread and to the developer trying for roms is now easy. xD
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Here are some screenshots of the error I'm getting when flashing zip and the log is attached below.
[Galaxy S 4 i9505 Original Android Development] monkteo:
Man you killing me, I will try again tonight (now I am at work)

THX

PS some info about your success ?
[Galaxy S 4 i9505 Original Android Development] corncobman:
Hi, I guess the i9305 isn't compatible. I tried to flash a file and it failed, so I have attached the logs from it below.

Thanks for the utility regardless and hopefully it will be supported in future.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5749514]v00d007[/MENTION],

After quite a bit of debugging, I finally found out the root cause of the boot delay issue. (Super-tedious because Android's /init doesn't log anything useful by default.) It is caused by CyanogenMod calling "restorecon_recursive /data" to reset the SELinux label on every file in /data. This is what takes nearly 20 seconds out of the 31 seconds before CM boots on my Galaxy S4. Older versions of the patcher (specifically, before 8.0.0.r1460.g3f4675b) unintentionally worked around this by removing that restorecon line (see: https://github.com/chenxiaolong/Dua...p/ramdiskpatchers/coreramdiskpatcher.cpp#L292). That is why you didn't see the issue before.

To confirm my suspicions, I manually removed "restore_recursive /data" from the kernel's ramdisk. CM then booted after a normal 10.6 seconds at the Samsung logo.

All in all, this is expected behavior in CM. The only proper workaround is to reduce the number of files on the internal storage. (In my case, restorecon was slow because Wechat created 78490 files in /sdcard/tencent for its chat history).
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
When I have my primary rom patched on my S6 touchwiz it takes noticeably longer to boot. Will look through external storage when I get a chance.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, cool, thanks a lot for your efforts on this! Will you now integrate this new knowledge into future patcher versions/ramdisk patching?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There was a bug in my uevent code where the hardware scanning thread wouldn't exit when it was supposed to and instead, waited for the next hardware event reported by the kernel before exiting. This could have caused weird delays in the boot process (though it varies from device to device). Could you try 8.0.0.r1780.g24a1c09 and see if it makes a difference? (If the ramdisk update feature works for you, that should be enough to get the latest changes.)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I was able to reproduce the bug where in app flashing from TouchWiz 4.4 may result in:

[V] Failed to destroy chroot environment. You should reboot into recovery again to avoid flashing issues.

I'll look into this tomorrow :)

EDIT: Also affects Moto G 2013 on Android 5.0 and the Nexus 5 on Android 5.1.

EDIT2: Oh man, there are quite a few issues in the error checking code for the installer. The joys of mixing C++'s true/false return values with C's 0 and -1...
[Galaxy S 4 i9505 Original Android Development] kotzir:
[MENTION=4277844]chenxiaolong[/MENTION] So do we need to do something to fix the issue (like removing restore_recursive on /data manually), or it is fixed by a patch of yours?
[Galaxy S 4 i9505 Original Android Development] mabuan:
I fished all steps, but when boot to data-stot it said "kernel is not seandroid enforcing" and boot loop at this stage. I have attached the log file. Please help me! My phone is Note 4 910L.
[Galaxy S 4 i9505 Original Android Development] physwizz:
I still can't get the TW ROM to work on extSD. It won't get past the samsung galaxy tab S screen.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
@chenxiaolong

Do the 'Dual Boot Patcher' supports the Galaxy S6 edge+ (SM-G928F) atm?

It works on my Galaxy S4 (backup phone) and my Galaxy Note 4. But i recently got me a Galaxy S6 edge+ where i don't know if the patcher works for it.
[Galaxy S 4 i9505 Original Android Development] mabuan:
Hi bro,

How did you do to make it work on Galaxy Note 4? What is your primary rom?
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Well, a good start is to read this :D: http://xdaforums.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211

And i used the SimplRom as my ROM on the Galaxy Note 4.
[Galaxy S 4 i9505 Original Android Development] mabuan:
Did it work on last Dualboot Patcher version? Or I must use r1026 version like in the guide.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Yeah. If it works on one version, it will work on newer versions aswell.
[Galaxy S 4 i9505 Original Android Development] ktm_91:
[MENTION=4277844]chenxiaolong[/MENTION]

Up :(

A thing that I didn't say is that with old versions (months, maybe even a year old) of the patcher it worked perfectly, same primary ROM..