yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's in the paths here: https://github.com/chenxiaolong/DualBootPatcher/blob/master/libmbp/devices/asus.cpp#L37, but nothing was creating it. That symlink line I mentioned in my last post doesn't run until all the multiboot code has finished.

Anyway, hopefully it is fixed in 8.0.0.r2128.gead0e4f :)

Relevant commits:

https://github.com/chenxiaolong/DualBootPatcher/commit/9bf971df76c7da8697d00b9cd1d30ba455d15087

https://github.com/chenxiaolong/DualBootPatcher/commit/91325010c8bd9dc038fec7238cb59b3cdf6c94c1
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, I'll build a zip for you try tonight :)

Yep, reading from an SD card causes far less damage than writing and the system images are created in such a way that most data can be read sequentially.

6AM... please don't tell my parents :D
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
i used r2130 and it works fine, i tried to use two stock ROMs an it works fine

i used data-slot 1 but after rebooting to 2nd ROM, i installed the apps manually

and app sharing i enabled it in Primary ROM and rebooted to 2nd ROM and installed the app but no data

when i enabled the option in 2nd ROM and rebooted to primary it works but i lost app data

everything is fine or im missing something ?

ill try to install cm13 also :D

Thanks :)

Edit:

I can't flash ROM to external sdcard

Log

https://drive.google.com/file/d/0B0ODjuZvMeEvMXFVTURpZmNzQVU/view?usp=docslist_api

Screenshot

Edit 2:

AICP didn't boot up, i used data-slot 2 ?

logs

https://drive.google.com/file/d/0B0ODjuZvMeEvSXhHUjVma3hiMDg/view?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] kykint:
With your latest updates to the patcher, my kernel now works well even after updating ramdisk :)

Thanks mate!
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Now Added a ScreenShoot

Just a remember: Error 14 in patcher Chen.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5207461]Salman A.[/MENTION]: I just found out that strace is not supported in some TWRP kernels, so I have a zip for you to test :) It doesn't do anything except creating /sdcard/strace.log.

EDIT: Dude, we're getting close to solving the system.new.dat issue you originally reported. I was able to flash the "CM_121_MDSTEAM.zip" ROM you linked to a while back on my old Galaxy S4 (but I obviously can't boot it) :D I had to rework a bunch of code to get this to work because of Lenovo's crappy update-binary lol. But in the end, I think we will have made DualBootPatcher much more robust.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please post /sdcard/MultiBoot/patch-file.log right after it fails to patch. Without the log, there's no way I can know what went wrong. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Glad it's working for you! :)

The app sharing settings really needs to be redesigned or rephrased to make the functionality more clear. When you enable app sharing, all it does it make Android load the app data from /data/multiboot/_appsharing/data, instead of the usual /data/data. If you have the option enabled in every ROM, then they will all load app data from /data/multiboot/_appsharing/data. Your old data is not copied to the shared folder, so that why it appears you lost your data. For now, you'll want to use Titanium Backup after you've enabled the option.

Should be fixed in 8.0.0.r2131.ga08aaeb. mbtool didn't recognize that ASUS mounts SD cards at /storage/MicroSD.

Hmm, I don't see a kernel log in there. Where did it hang (device logo or ROM animation)? Did it autoreboot to recovery?
[Galaxy S 4 i9505 Original Android Development] AL_IRAQI:
I asked about App sharing for debugging reasons i thought there was something wrong with it, after another reboot same shared in both ROMs.

It hang at device logo and it didn't reboot to recovery, i tried more than 10 ROMs 5.1 & 6.0.1 all them works fine without any problems

Thanks for your work and i wish that i can give you something in return, currently im broke [emoji23]

Sent from my ZF²
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I

I'm almost crying with happiness. I knew you will fix this.. Thank you so much :o :highfive:

I'm attaching the strace.log.

I'm ready to test anything you give. :D

Thank you so much for all your hard work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
New debug build for you to try :D strace didn't crash on your device, but it gave completely meaningless output lol. Oh well, back to guess-and-check method.

For this debug build, please try flashing a ROM that uses system.new.dat and don't modify the updater-script file in the zip.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Finally, it installs :) :victory: giving no errors whatsoever though I didn't take a log.

But, new issue :( Now, the ROM seems to be installed without problems. The build and android version is shown in the Dual Boot Patcher app. So, it should be installed. But it doesn't boot. It passes the first phase of the bootsplash but doesn't reach the bootanimation and has weird bug. I kept it on to know if it's booting but it didn't. And when I booted to the primary ROM, my internal memory is almost full!!! This ROM's data used 1.72 GB!?! I've got to go. Or I'll be late for school. I'll give reports after I come back.

EDIT: I'm attaching the logs made by the GetLogs.zip so you may understand.

It seems to be the ROM's issue. Tried flashing Flyme OS and works perfectly fine :o

Finally!!! Thank you so much again and again. I really wish I could donate. Oh, I were older.

Also, [MENTION=4277844]chenxiaolong[/MENTION], can these changes be merged into the snapshot version??

I'm keeping the logs so that you can see what the issue was. The ROM has no issues when installed on primary. Many are using it as daily driver.
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
I installed Dual Boot Patcher on my Samsung Galaxy S4 (International GT-I9505 Qualcomm variant) yesterday with Albe95’s TW Lollirom v6.0 as the primary ROM and Resurrection Remix M v5.6.1 as my secondary ROM.

The whole process was easier and smoother than expected and works perfectly.

The only issue I had was installing Gaaps on the secondary ROM, I patched the zip and installed successfully… but once I switched to the secondary ROM I got loads of continues messages about Google Play and Settings have stopped. You click ok on the message box but they keep appearing and don’t allow access back into the ROM. I tried different Gaaps including the Pico version.

Does anyone know what I’m doing wrong?

Also my phone is a 16Gb version and therefore only has around 1Gb free, is there a way to install a secondary ROM on SD Card and what would be the limitations?
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Had similar problem solved using patcher utility to wipe the secondary ROMs data/cache/dalvik
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
Thank you very much, that worked perfectly :)
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
New problem. :( I had dirty flashed that ROM then. I tried wiping caches and data after that, but the ROM still won't boot. So, I thought I would clean install it after wiping everything. I checked all the tick boxes, all of them, including system and multiboot files, but it's the old problem. I have 2.7 GB of system data on my SD card now. But this could have been solved by deleting the FILE000 in FOUND.000 like the last time. But guess what? It's not there! No new files there. Only the old FILE001.CHK of only 16 KB.

So, is there any other folders where this kinda files go? I checked LOST.DIR. No luck.

Thanks.

I forgot to tell that when I deleted FILE000.CHK last time, I didn't delete the FOUND.000 folder. So, I deleted it and it appeared again hidden with FILE0000.CHK in it. Sorry to bother. :)
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
I only have 350Mb of free space remaining on the internal storage, can I install the secondary ROM to SD Card?

Samsung Galaxy S4 (Qualcomm International GT-I9505)
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
You can install to an extsd-slot, which installs /system/ to SD card but you will still need space on internal storage for /data/ qnd /cache/
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Install and run App Cache Cleaner from Play Store and also move all personal files to SD card. The patcher has options to install to external SD but that is only the system part.
[Galaxy S 4 i9505 Original Android Development] Arsh@:
Is gt-i9500 exynos variant supported?

Is gt-i9500 exynos variant supported?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Yes, it is. Why don't try downloading the app and see?
[Galaxy S 4 i9505 Original Android Development] Hipped_Orange22:
Hi [MENTION=4277844]chenxiaolong[/MENTION] i am using latest snapshot i.e 8.0.0.r2132.g6b20dff. i can dual boot betwwen LP 5.0 TW and 6.0.1 MM CM13...the problem is that when i use "Individual app sharing", whatsapp app on secondary rom i.e cm 13, whatsapp app crashes :( i tried all of january builds and none of them are working. Please look into it and fix it. Thank you!

My Phone:- samsung galaxy s5 g900f
[Galaxy S 4 i9505 Original Android Development] f41lbl0g:
I've been trying to download the new systemless supersu beta but the app crashes when flashing it. Has anyone got systemless supersu working on their device using the patcher?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've written up a very technical description on how the multiboot installation process works behind the scenes if anybody is interested :D https://github.com/chenxiaolong/DualBootPatcher/wiki/[mbtool]-ROM-installer
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just pushed a fix in 8.0.0.r2137.ge522749. :)
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
I have the same issue on GT-I9505. When i go back to the primary TW rom all the data for WhatsApp is lost but if i unselect sharing for WhatsApp it works in the primary rom but not in secondary CM.
[Galaxy S 4 i9505 Original Android Development] whitenoyz:
I have read several posts but couldn't find any solution.

Flashed new cm13 for oneplus 2 and working but how to gain root to that secondary rom?

Tried to patch and flash supersu with no luck...

Any help?

Thank you

Enviado desde mi ONE A2003 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] dsmitty166:
Hey Guys,

Need a little insight here. I'm using this on the nexus 6P, however I can't seem to get stock based roms to boot on the secondary or any data slots. I can successfully install AOSP based ROMS on these slots, but stock just hangs in the boot animation.

Here's what I have done.

Decrypted nexus 6P

Installed MultiBoot app

Patched Primary and booted in

Set Kernel

Updated RAMDISK

Patched Secondary ROM

Flashed Secondary ROM

Is there something that I'm missing for the stock variants not to boot?
[Galaxy S 4 i9505 Original Android Development] jroq8400:
It's not just WhatsApp but also tested Facebook from CM13 is not able to read the shared data folder.

First I thought it was incompatible data with 5.x but the apps were not able to start even with no other data present.
[Galaxy S 4 i9505 Original Android Development] bnwg:
I think it's nothing deal with multiboot.

For CM you need to enable root access from developer options...if I recall correctly.

---------- Post added at 11:37 PM ---------- Previous post was at 11:25 PM ----------

Please see the explanation for data sharing from OP as below (I think OP has updated in the first post as well).

"What the data sharing does is redirect where Android loads the data from. Normally, Android loads the app data from /data/data/[app]. When data sharing is enabled, the data is loaded from /data/multiboot/_appsharing/data/[app] (which is accessible to every ROM). That's why you appeared to have lost your old data. Actually, if you uncheck data sharing, Android will use your old data again."

Having said that after enabled the data sharing from the primary ROM first time you will need to restore the data (e.g. TB).

I've tried booting between custom TW 5.1.1 and CM13 with data sharing for whatsapp and facebook (actually more than that) and it works flawlessly. No crash for whatsapp. LINE will crash though. But whenever restoring data for LINE it will crash so it's the matter of the app itself not multiboot.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
What error is given? Attach the log so that the dev can see what the issue is.

I've no issues. The latest update has also fixed the flashing of systemless supersu.
[Galaxy S 4 i9505 Original Android Development] whitenoyz:
my mistake, i just had to activate root access from CM13 using the developer options menu.

Thanks
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Thank you and good to hear it's working for you. I must be missing something on the CM13 side because I am able to share fine between 5.x roms.
[Galaxy S 4 i9505 Original Android Development] MBariya:
+1 systemless root also working for me on r2138 build, tested on CM13.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Can anyone with MTK device share his experience with the latest builds?

[MENTION=4277844]chenxiaolong[/MENTION] Hi, can you confirm that the changes in the code you made in the latest debug version(Android_GUI-debug_installation-rework_8.0.0.r2138.g9687c21.apk ) are merged to the latest snapshot build?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Yes, system.new.dat ROMs finally flash without any issues.!! All credits to Chen.

No, I shouldn't think so.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yay, awesome news friend!! We'll finally say goodbye to the boring editing of the updater-script. Lol I'll wait for the changes to be merged in the snapshot build and will update.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5207461]Salman A.[/MENTION]

[MENTION=5048731]911-Future_Maker[/MENTION]

Merged in 8.0.0.r2147.ge56cf26 :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yay! Updating right now!! Cheers! :D
[Galaxy S 4 i9505 Original Android Development] diogo.sena:
[MENTION=4277844]chenxiaolong[/MENTION]

i'm trying to use cm12.1 for lgg3 d855 as a secondary, the installer gets stucks at "patching system image unconditionally"

using both twrp and the builtin installer in the very latest app version ( r2147 )

I'm currently using cm11 as secondary without problems.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
log

Here is the log, it says that the zip is bad and it isnt. I can flash it on twrp, maybe some kind of new compression method??

01-22 00:21:50.710 22101 22101 I Timeline: Timeline: Activity_idle id: android.os.BinderProxy@41c917d0 time:125302126

01-22 00:21:51.780 22101 22969 D PatcherService: Android GUI version: 8.0.0.r2138.geaa9990-SNAPSHOT

01-22 00:21:51.790 22101 22969 D PatcherService: libmbp version: 8.0.0.r2138.geaa9990

01-22 00:21:51.790 22101 22969 D PatcherService: Patching file:

01-22 00:21:51.790 22101 22969 D PatcherService: - Patcher ID: MultiBootPatcher

01-22 00:21:51.790 22101 22969 D PatcherService: - Input URI: content://com.android.externalstorage.documents/document/primary%3ADownload%2F0B3vBKWqY-uX-QkdCd3BpQ1F1Yzg.zip

01-22 00:21:51.790 22101 22969 D PatcherService: - Input name: 0B3vBKWqY-uX-QkdCd3BpQ1F1Yzg.zip

01-22 00:21:51.790 22101 22969 D PatcherService: - Output URI: content://com.android.externalstorage.documents/document/23AE-2F7C%3Adata-slot-stock6.zip

01-22 00:21:51.790 22101 22969 D PatcherService: - Output name: data-slot-stock6.zip

01-22 00:21:51.790 22101 22969 D PatcherService: - Device: lgg3

01-22 00:21:51.790 22101 22969 D PatcherService: - ROM ID: data-slot-stock6

01-22 00:21:51.800 22101 22969 D PatcherService: Input file descriptor is: 57

01-22 00:21:51.800 22101 22969 D PatcherService: Output file descriptor is: 65

01-22 00:21:51.820 22101 22969 E libmbp : miniunz: Failed to move to first file: UNZ_BADZIPFILE

---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------

For me works like a charm but the installation in the data slot takes me about 5 minutes and the updater script dont have any status info. Maybe is not stuck, you need to wait a little bit more.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Do you have a link to the zip? I can take a look, but I'm not sure I'll be able to fix the issue. (I have very little knowledge of the internal structure of zip files.)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
CM13 has root built in. You just have to enable in Android's developer options.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Everything you did seems correct to me. If the stock ROM already reaches the boot animation, then the only way to determine what's wrong is to create a logcat during the boot process since the multiboot code completes before Android starts booting. Unfortunately, adb is disabled by default in stock Nexus ROMs, so we'll need to edit the boot.img file to enable it. Are you familiar with doing that?

If I had to guess at what the core issue is, I'm guessing SELinux is the culprit. But until I see the logs, I can't say for sure.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll look into this. That fact that it can't read the shared data folder most likely means SELinux is interfering (which should be an easy fix).
[Galaxy S 4 i9505 Original Android Development] dsmitty166:
Yeah let me see what I can do.

I'm guessing it's an selinux item too thanks for the reply
[Galaxy S 4 i9505 Original Android Development] MBariya:
SElinux need to be permissive to share data between ROMs.

Keeping it enforcing is creating issue like..WhatsApp gives fc, all other apps not showing older data...etc.

So keep selinux permissive for now..all work normal.

Tested with TW 5.1.1 and CM13 based roms
[Galaxy S 4 i9505 Original Android Development] physwizz:
I'm running 2092 on my primary (tw 4.4.2) and 2035 on my secondary ExtSD ROM (SlimLP) .

I can't get 2092 to work on my secondary. I can't see the ROMs and I get the error message "Could not connect to mbtool"
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
My TW roms show as "SE for Android Status" as Permissive, but i still can't share Whatsapp across TW or CM roms... keep getting FC.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Sure! Here:

[D855] ~ UNIQ ROM 1.0 ~ [ V30B - 6.0 Marshmallow ] this is a stock based rom

https://drive.google.com/file/d/0B3vBKWqY-uX-QkdCd3BpQ1F1Yzg/view?usp=sharing

And here the stock ROM just open the zip and extract the d85530b.zip

https://mega.nz/#!BMsmXIIL!pU_6Xu5iYC7PZ8CFzFA8UxmRocixgFskKb_r3mRS3KE

Thanks!
[Galaxy S 4 i9505 Original Android Development] MBariya:
Both ROM must have SElinux permissive, not only single ROM. You should have both TW and CM should permissive.
[Galaxy S 4 i9505 Original Android Development] jir591:
Has anyone been able to create and run a ROM on external USB storage? Every time I try I get an error saying there is not enough space on the external storage even though there is plenty of space.
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
Both my primary and secondary ROMs are TW and both have SE Linux set to Permissive. Whatsapp sharing is enabled on the primary ROM afterwards i rebooted back into primary ROM and Whatsapp asks me to verify account again. So i did this and rebooted into the secondary ROM which asks to setup Whatsapp. Each time i switch ROMs i have to setup again.
[Galaxy S 4 i9505 Original Android Development] MBariya:
Ok. I didn't checked that with TW rom. Just counter check again in Dualboot app, is it showing "shared data" written below whatsapp?? As shown below. I am asking you just for counter check. Not to trouble you.

Again check, is whatapp folder created as shown in below location?? As shown in SS.

/raw/data/multiboot/_appsharing/data/com.whatsapp.

I am just helping out you, dont take it negative.
[Galaxy S 4 i9505 Original Android Development] jroq8400:
Thank you for all your work!

Confirmed that I am able to share apps with CM13 after I changed SElinux to permissive. (Using 2130)

---------- Post added at 08:57 PM ---------- Previous post was at 08:48 PM ----------

This is the process that works

- install app in ROM A (don't open it)

- share app in ROM A DualBoot

- reboot back into ROM A

- open app and configure it (you are now using the shared folder)

- boot into ROM B

- install app in ROM B (don't open it)

- share app in ROM B DualBoot

- reboot back into ROM B

- now open app and you should see the same config data you did in ROM A (because you are now also using the shared folder)

And yes confirmed you need SElinux Permissive at least on CM13 based ROMs
[Galaxy S 4 i9505 Original Android Development] jp007_uk:
Thanks that worked perfectly... now using Whatsapp across both TW ROMs.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
My friend is not able to update it at all, nor does it lead to bootloop. The ramdisk-update.log is not logged either. [MENTION=4277844]chenxiaolong[/MENTION] Any help? Also, is updating ramdisk not necessary for the multiboot to work? Will logs of GetLogs.zip help? Also, please add t03g to Note 2 device codenames.

Thanks :)
[Galaxy S 4 i9505 Original Android Development] pvsgh:
That's exactly what said, don't update ramdisk with mbtool, you would get bootloop. I don't specific details why it doesn't work, but I am able to boot into both the installed ROMS without any problem.
[Galaxy S 4 i9505 Original Android Development] monkteo:
sorry to bother you but it's normal the system to by so small ?

what happen if I want to install in secondary ? not working, normal so that why I ask ?

right now I have only the primary rom !

THX
[Galaxy S 4 i9505 Original Android Development] jova33:
Go back a few pages. Someone mentioned doing it for user apps

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] jerrah:
can someone dumb this down for me lol like to 3rd grader talk. dual booting works great, i just dont wanna have to download the apps again on kangabean
[Galaxy S 4 i9505 Original Android Development] Dugan1017:
Anyone have any tips for ways to share data like text messages and call logs between primary and backup ROMs?

TW has the option to backup some data to the cloud using your Samsung account, but obviously I can't restore that data if I boot into my secondary ROM (IOKP).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, this is something that will probably never happen (at least automatically). ROMs are free to store data however they like as long as the APIs don't change. Even if you didn't kind don't it manually, I don't know of any backup and restore solution that works for both touchwiz and aosp. Like you said, the Samsung account doesn't work in aosp :(
[Galaxy S 4 i9505 Original Android Development] jova33:
https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts

Works for SMS, not MMS. Used to work for the call log, but if you try it now, going from TW to AOSP, your dialer will force close until you erase all call logs from in that app.

Sent from your mom's smartphone

---------- Post added at 02:11 AM ---------- Previous post was at 02:00 AM ----------

How do nandroid backups work with this? If I make a backup in recovery, will it backup both ROMs?
[Galaxy S 4 i9505 Original Android Development] rlorange:
Yes I made an app which will backup and restore just your second ROM. Find it in the app and mods section :)

---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------

Sms backup and restore app works between AOSP and TW :)
[Galaxy S 4 i9505 Original Android Development] jova33:
Well, TWRP backed up both ROMs. Just backed up and restored to test. Do you have a link for your app/mod? I don't frequent this area of the S4 forums. I'm on VZW, they like to keep us separate.

Sent from your mom's smartphone