yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Guys, no offence but Whatsapp across multi roms will not work due to Whatsapp limitation. Moreover, app sharing feature is abandoned. If you still want to have further discussion, please do so via PM so as not to clutter this thread.
[Galaxy S 4 i9505 Original Android Development] Filip013:
OK. I take your point that App Sharing is abandoned and shouldn't be discussed in the main thread, but I still think that data sharing functionality is important for any one planning to use multiple ROMs.

As for WhatsApp limitation, I have to disagree. What I managed so far is to use Titanium Backup to backup data in my primary ROM and restore it in the secondary ROM. Even though Titanium Backup isn't specifically meant for that, it works just fine. I can use WhatsApp or any other app perfectly. The only hassle is that I have to manually backup and restore every time I switch ROMs.

[MENTION=4277844]chenxiaolong[/MENTION]

Since you are planning to remove App Sharing completely in a future build, have you given some thought to a possible replacement feature? I think that an app data sync feature might not be a bad idea (at least from a user perspective, I have no idea what goes on from the development side).

What I mean by that is keep app data folders separate but automatically sync them after selecting a different ROM in DualBootPatcher app. The drawbacks are that it would be time consuming, but it would certainly increase compatibility. It might even be possible to sync messages and call logs. What are your thoughts on this?
[Galaxy S 4 i9505 Original Android Development] bondro:
Knows someone where can be a problem? I tried everything to install rom to Secondary but it still finished with error. It keeps saying that there isn't enough storage even though I have 20 GB of free storage.

Thanks for any help or advice
[Galaxy S 4 i9505 Original Android Development] Eleo:
20GB storage in data slot or /system folder? /system folder has much less storage normally. Look at it from storage window of dual boot patcher app again.

Try installing to data slot. Probably you have 20GB free space in data slot rather than /system folder. Secondary slot writes in /system folder, data slot writes in internal storage
[Galaxy S 4 i9505 Original Android Development] bondro:
It was so simple, it works now :) .... I am sorry for my noob question.

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

Hey man, how's it going?

I have a couple users having renewed issues with the patcher and my kernel...and I'm guessing you and I might have some conflicting init procedures once again. Previously the only issue was a synapse one, which I'd solved by sleeping my uci script for 20 seconds if your init binary was present. This new issue isn't so clear cut...

Basically, using my kernel after a patch, my users experience an emergency reboot into recovery. I'll upload the log here, but it looks like either a race condition in setting up selinux, or perhaps a patch that has made it or tmpfs more stubborn regarding remounts. I've integrated a busybox install as well as a few other tricks dynamically set on first boot, so the conflicts could be any number of things. Anyhow, here is the log I received, please let me know if you've any insight into the issue.
[Galaxy S 4 i9505 Original Android Development] NeoTrantor:
Hi, I have CM 13 nightly (jfltexx) and would like to test dual booting but my phone is encrypted plus it uses the SD-Card as internal storage. Will this work?
[Galaxy S 4 i9505 Original Android Development] Kingzak34:
Hey everyone I'm currently user of a Huawei Mate 8 and I would like to add support for it but when I try to build from sources without modification it fails everytime does someone got a build working from sources recently?

Tapatalké depuis mon MEGA Mate 8 LineageOS !
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
Is BootUI compatible with Nougat yet or not?
[Galaxy S 4 i9505 Original Android Development] monkteo:
YES it is !
[Galaxy S 4 i9505 Original Android Development] pehoko:
Can I do flash firmware for my device with patched zip file or it is not rom dependent?
[Galaxy S 4 i9505 Original Android Development] jcrompton:
I've seen some of the past posts .... But none recent

I've had fortune with Magisk 10.2 and phh root with passing Safetynet, and playing PoGo but it seems that even with all the normal steps ROMs other than primary ROMs will not pass Safetynet. Is that everyone else's experience or is there a work around?
[Galaxy S 4 i9505 Original Android Development] bolt1502:
Please add the support Doogee x5 Max Pro https://xdaforums.com/showpost.php?p=70545216&postcount=11037
[Galaxy S 4 i9505 Original Android Development] Kingzak34:
Hey guys, I'm working to get this working on Mate 8, it works with CM Roms but not with Emui ones. It vibrates 5 times and send to recovery But problem is that once in recovery the touchscreen doesnt work until a proper kernel is flashed back (the one from primary for exemple) if I don't flash the kernel I'm stuck with the phone rebooting in recovery without touch working. So I can't have logs for those roms. If someone got an idea.

Tapatalké depuis mon MEGA Mate 8 LineageOS !
[Galaxy S 4 i9505 Original Android Development] Vihru:
Is this compatible with Oneplus 3T?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Recoveries work with touchwiz and volume up/volume down/home/power hardware buttons. Did you try those buttons to get recovery working when touchscreen is not working?
[Galaxy S 4 i9505 Original Android Development] carlsbad28:
How do I remove the multiboot option, say I just want to return to having only one primary ROM? Do I just wipe cache/dalvik and system using the default recovery?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Flashing unpatched zip from recovery actually breaks multiboot. But it does not remove the multiboot files. There is a zip for wiping multiboot files, I think [MENTION=4476875]kopitalk[/MENTION] shared them once
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Sometimes after my phone is shut down, I will boot it up....Then it sticks on splash screen for forever. I battery pull and boot again and it boots fine. What could cause that?
[Galaxy S 4 i9505 Original Android Development] Kingzak34:
Thanks for answer but actually on Mate 8 we only have TWRP so we can't navigate with buttons.

Tapatalké depuis mon MEGA Mate 8 LineageOS !
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Add feature to move ROM from data slot to extsd slot

Would be fine to have a feature to move ROM from data slot to extsd slot.

The reason is, that flashing to data slot is much faster than installing directly to the extsd slot.

When an OS is successfully installed to data slot, then could be possible to move to extsd slot to free up the space on internal memory.

Added an issue for this feature request on github.
[Galaxy S 4 i9505 Original Android Development] Eleo:
You mean any way other than backing up the rom on extsd slot and then restoring it on data slot? Because that one works
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Why to do a long backup & restore procedure, when moving to extsd slot would require just a few steps:

- one-time folder move (which contains system.img, boot.img & other multiboot files)

- rename multiboot folders to begin with "extsd-" name.

I think this can work.

Also needs to modify DBP GUI to have this feature.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
In data slots roms the file "system.img" does not exist. In place is the system folder explicitly, since ext4 supports Linux permissions. So system.img file should also be created
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I didn't know, that system.img is not available for data slots.

In that case system.img would be still have to be created, but together with this, initial flashing would be still faster.
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Yeah, I guess so. [MENTION=4277844]chenxiaolong[/MENTION] another suggestion I find interesting, would be to not need to patch zip files that will be installed by the in-app flasher itself. You would simply choose the common zip, DualBootPatcher would extract META-INF/boot.img and patch on-the-fly, then run it along with extracted zip files. I do not know if you've tried this, if it's too much work or maybe even impossible. Anyway thanks for your time and great work
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Are there any other Samsung Galaxy S4 i9505 users, who are flashing Cyanogenmod 13 to extsd slot, and takes 6-7 hours?

It seems to hang while at "Patching System Image Unconditionally" message, but after 6-7 hours, it finishes successfully. However it seems to be too long.
[Galaxy S 4 i9505 Original Android Development] pc boy:
Can anyone shed some light on Boot UI please?

Is it supposed to show up while booting?

I enabled it and nothing comes up!!

Plus I faced frequent freezes and reboots afterwards, now disabled it and checking to see if it is resolved.

Found and attached a log file in /raw/cache/multiboot/bootui

My device is kltedous and I have costum tw as primary and CM13.1 as Data slot, both working fine by far.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Just flashed patched [ROM][7.1.1_r9] Resurrection Remix N v5.8.0-20170109 for jfltexx to extsd successfully.

It took about 7 minutes to flash.

Then immediately flashed patched opengapps nano v7.1.1.

Updated ramdisk, rebooted, but got into TWRP recovery.

Next flash was just the ROM.

Then updated ramdisk and reboot.

Still 5 vibration and TWRP recovery.

Logs attached.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
[MENTION=5842851]Caio99BR[/MENTION]: how to use Travis CI, which you use to build Dual Boot Patcher? I don't know where should I start.
[Galaxy S 4 i9505 Original Android Development] :
By now I'm working on it (build fail due missing dependencies), you can quote me in my GitHub repo, since it's partially off-topic here :)
[Galaxy S 4 i9505 Original Android Development] pehoko:
Why if I do clean dalvik/cache only primary rom boots, others installed on data slot not?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Your non-primary roms are using primary cache partition to store their mutiboot cache files. If you wipe your primary cache partition, those other caches would be gone. How would you boot without cache partition? So if you want to wipe anything, use the provided dual boot utility zip or wipe using dbp in-app feature.

Read OP one more time.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
You should have let me know that you were trying to build. It's great that you have been trying but I have been wasting my time here just to build it for you. Good thing I saw your pull request on git.

Edit:

If you haven't finished your build, you can test this build. Remember since it's a debug version and unofficial, it'll show you the warning about it.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Also

See this line:

[ 17.437866] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*

The

/devices/platform/msm_sdcc.2/mmc_host/mmc2*

path for external sdcard simply does not exist.

I found only this external sdcard path:

/dev/block/platform/msm_sdcc.2/mmcblk1

on my Samsung Galaxy S4 i9505.

EDIT:

OK, I found the following path:

/sys/devices/platform/msm_sdcc.2/mmc_host/mmc2

But if this external sdcard path exists, why DBP didn't match the

/devices/platform/msm_sdcc.2/mmc_host/mmc2*

pattern in it?

EDIT2:

Strange, that when I look into directory /sys/devices/platform/ I see the following sd devices:

root@jflte:/sys # ls -la /sys/devices/platform/ |grep msm_sd
drwxr-xr-x root root 2017-01-21 12:57 msm_sdcc.1
drwxr-xr-x root root 2017-01-21 12:57 msm_sdcc.2
drwxr-xr-x root root 2017-01-21 12:11 msm_sdcc.3

EDIT3:

Also, when I check /system/etc/vold.fstab I see the following:

root@jflte:/system # cat /system/etc/vold.fstab
# ...
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host

The question is, shouldn't DBP want to mount

/devices/platform/msm_sdcc.3/mmc_host/mmc1*

instead

/devices/platform/msm_sdcc.2/mmc_host/mmc2*

???
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
[MENTION=4277844]chenxiaolong[/MENTION]

If I want to make a release build, what's to add in signing path in here?

-DMBP_SIGN_CONFIG_PATH=<signing config path>

Edit:

Got it, sorry for the trouble. :)

For anyone else looking for the answer. I just had to edit cmake/SigningConfig.prop.in accordingly and provided the path of this file.

Edit:

Even after this, always get password wrong error. The same issue as

https://github.com/chenxiaolong/DualBootPatcher/issues/276
[Galaxy S 4 i9505 Original Android Development] pehoko:
Tnx, manually creating cache path works for me, all roms boot properly ;)
[Galaxy S 4 i9505 Original Android Development] dvs14:
[MENTION=4277844]chenxiaolong[/MENTION] Please, add support meizu m2 mini (mtk 6735). View attachment 20161218.093725.tar.gz
[Galaxy S 4 i9505 Original Android Development] gaww:
Back up and running on 935f - 935t is not happy.

So far, have the OP's ROM up as primary and King ROM as data slot. Tried to do Bobcat Beta - it parched but failed - no boot image error. Not surprised, as it was a beta.

Also tried Echo official 7.0, but same error. Thought Echoe was being covered? I would think it would work as primary, but wanted to stay with the one above as primary.

Anyway - great work OP - glad to be back.
[Galaxy S 4 i9505 Original Android Development] :
I have compiled it i just updated sdk as told by you and the build was successfull thnx and sorry for wasting your precious time
[Galaxy S 4 i9505 Original Android Development] speter2:
I need help, i can't open zip files in the android app. It opens the zip file like a folder instead of selecting it. I tryed to use the windows gui but it instantly crashes with an error saying cant find windows...
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
To select a zip file, long-press the file, then tap "open" at the top of the screen.
[Galaxy S 4 i9505 Original Android Development] gaww:
Then it should take you back to the UI, and select the device and the location. It should go back and show the file name you selected and then save. You are ready to go
[Galaxy S 4 i9505 Original Android Development] pc boy:
[MENTION=4277844]chenxiaolong[/MENTION]

I can't run windows utility under win 8.1 64bit

The following error comes up each time I run the app

Update: It appears to be a problem with V9.....

I downloaded v 8.0.0.r2616.g784e86e and it works like a charm.
[Galaxy S 4 i9505 Original Android Development] physwizz:
Yes. I discovered this in my recent ROMs
[Galaxy S 4 i9505 Original Android Development] NicStock:
Support ZTE nubia z7max

Please organize support ZTE nubia Z7max. Thank you in advance.
[Galaxy S 4 i9505 Original Android Development] farovitus:
What's Boot UI ? [MENTION=4277844]chenxiaolong[/MENTION]

Am using Helios 7.0.2 ROM(with Apollo custom kernel) and RR ROM both boot ui installed in settings ,what to do now ? Help is appreciated
[Galaxy S 4 i9505 Original Android Development] pc boy:
Is there any way to revert a patched zip to its original state?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Unfortunately no. It was tried several times but with no luck
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
Well, if you delete your original rom you can revert but you need some practice with roms;

you must to go to the zip and:

-Delete all the folder multiboot

-Go to /META-INF/com/google/android and delete files update-binary and update-binary.sig and delete the extension .orig to file update-binary.orig (it`s a backup of your original)

-In the same folder must edit updater-script in two lines specifically; when it given a mount point to system like == 0

- And finally unpack boot with a tool like Android Kitchen and delete two files inside folder boot.img-ramdisk called mbtool and mbtool.sig and repack again.

- If you should preserve from your original zip before patch your updater-script and your boot.img all should be more easy
[Galaxy S 4 i9505 Original Android Development] gaww:
In the past, this app handled BobCat ROMs.

The BobCat OP has released a ROM based on official 7.0 - could you please add that to the list? Currently, it fails to apparently handle the boot image.

.
[Galaxy S 4 i9505 Original Android Development] dreawer:
[MENTION=4277844]chenxiaolong[/MENTION]

Thanks for your amazing work! :good:

Could you add the support for Xiaomi Mi 4c?
[Galaxy S 4 i9505 Original Android Development] gaww:
A general question - have noticed 7.0 TW Roms seem to flash ok but 7.0 GE's don't . Is that the case will all these ROM's?

Update - got a different version patched and running. Had to put it on ExtSD, as internal SD was running out of room. But for some reason, it can't access the ExtSD? It is visible on the Free Space page

Suggestions ??

Update - 1. Looks like it is a known issue since December - ExtSD loaded ROMs not recognizing the rest of the ExtSD.

2. I can see the SD in Root Explorer - it is /raw/ExtSD/. Is there any way to get this recognized elsewhere in the ROM as the External SD - which is otherwise shown as corrupted ?
[Galaxy S 4 i9505 Original Android Development] Filip013:
Hi [MENTION=4277844]chenxiaolong[/MENTION] I have a small feature request. My primary ROM is MIUI and it's very picky about permissions. In order for DualBootPatcher to be able to patch any ROM and save the file I have to go to installed apps and enable Documents, which are disabled after every reboot. Now, I've found a solution by using Tasker and performing the command "pm enable com.android.documentsui" every time I open DualBootPatcher (I also have to keep doing "setenforce 0" and "setenforce 1" because of SafetyNet :D ). But it would be nice if your app could just request write access once and remember it, like in file managers, Titanium Backup, etc.
[Galaxy S 4 i9505 Original Android Development] iagommc:
Someone can help me? My first installation of dual worked, but i tried everything and i'm getting erros to flash another rom. I already use clean dual zip, delete manually, wipe everything. My log in down below.
[Galaxy S 4 i9505 Original Android Development] honey216:
[MENTION=4313166]Filip013[/MENTION] BRo i can understand your situation we all are facing this same problem and till now i have not found this solution someone posted that if we flash or miui custom rom like (epic latest update 7.1.5 and xiaomi.eu rom) through twrp wiping all data system , system, cache and dalvik cache then might this problem will be solve please help us if you will find this problem:crying::good:
[Galaxy S 4 i9505 Original Android Development] Filip013:
I figured it out by now. I think the problem for me was that I needed to remove MIUI encryption. I used the format data option in TWRP. Go to wipe menu and press the format data button. This will wipe data and internal storage and remove encryption. Then flash SuperSU (which prevents encryption) and reboot. Everything should be working now. Good luck :good:
[Galaxy S 4 i9505 Original Android Development] Arty777:
Bugs. Please help.

Bugs. Please help.

i am use lenovo k3 note k50-t5 (K3-NOTE_1631DEV_rus_FINAL_VDT.zip)

DualBootPatcherAndroid-9.1.0.r136.ge7995287 Sat, 14 Jan 2017 19:44:25 -0500

ROM not booting (multi slot 1, K3NOTE_MIUI8_超强自定义_xposed_非常省电_高级设置.zip), GetLogs.zip - "drive.google.com/file/d/0Bx51E_WBQf77WDRxX1V5anVzX0E/view?usp=sharing"

second attempt

ROM not booting (multi slot 1, 联想-K50-T5_7.1.21_155461db1f_5.0.zip), GetLogs.zip - "drive.google.com/file/d/0Bx51E_WBQf77ZHRLN1JmWHRrQ0k/view?usp=sharing"

third attempt DualBootPatcherAndroid-9.1.0.r152.g2cb576d4-snapshot

ROM not booting (multi slot 1, miuisu_v5.0.2_K50-t5_6.12.29.zip), GetLogs.zip - "drive.google.com/file/d/0Bx51E_WBQf77T0VJR2dwN3pZRmM/view?usp=sharing"
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
BootUI is not up yet for Nougat?
[Galaxy S 4 i9505 Original Android Development] monkteo:
it's so hard to read just a few page ?

YES IT'S WORKING
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
People like you helps, so who needs to read all this stuff

Thanks mate

---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------

Btw Nougat as Primary & Marshmallow as secondary

Will bootui show up
[Galaxy S 4 i9505 Original Android Development] Eleo:
"who needs to read all this stuff"??:eek:
[Galaxy S 4 i9505 Original Android Development] welder73:
Hi guys,G4 H815 here,

I use DBP for a long time,I've always kept my stock rom intact and tested some other roms on data slot.

But now one debloated stock based rom appeared and I would like to try it but can I replace stock with it?Without loosing the second rom?

I mean,can I do that while I'm on the second rom?

Patch it for primary and flash it with DBP?

Or patch it for primary and flash it with Twrp?

Is it doable?
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
Yes you can patch the rom for upgrading primary and it can be installed from recovery or the second rom
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
I found something worng for my device

My device has resolution of 720*1280

Pantech Vega Iron ef52l

But the bootui.zip in cache has configuration for 1080 resolution phone.

I also checked the logs for anything unusual and I found the error for not loading the graphic system

Log and ui.xml attached
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
[V] Loading graphics system...

overlay_msm_old: backend_init() failed

Failed to load any backend

[E] Failed to load graphics system

This is the log for bootui.zip

Bootui never showed up for me
[Galaxy S 4 i9505 Original Android Development] welder73:
Ok but I don't want to upgrade the primary,I want to replace it...

So,nothing bad will happen when I wipe the primary (stock) system,data and cache?
[Galaxy S 4 i9505 Original Android Development] Eleo:
You can wipe primary (check all boxes like system cache multiboot files) then flash your "primary upgrade"-patched zip(s). It is just a name. It doesnt mean it only can "upgrade". And your primary will be replaced.

You should do this in recovery by using dualboot utilites for wiping and patched files flashed in recovery...or in dualboot patcher app booted on a different slot other than primary). I used both methods, both work on note 3.

Cheers

P.S. The time required for flashing zips into primary takes longer than other slots due to its location (/system). I have done this. Mostly you will wait for making system image before flashing and after flashing you will wait for writing system image into /system. Be patient.
[Galaxy S 4 i9505 Original Android Development] zaibansari20:
I didn't try anything like this

You have to patch the zip to update primary then you can use recovery utilities to wipe the primary rom and then install the patched zip
[Galaxy S 4 i9505 Original Android Development] welder73:
Thank you for your answer :good:

One more question,if I may?

I assume that everything will be ok and I'll boot to primary rom.

What will happen with the second one if I format internal sd card?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Do NOT wipe anything on recovery interface. Do either from dualboot utilities zip or from dual boot patcher app opened on any other ROM (other than wiped). And since you dont have wipe internal sd card choice on those, you cant wipe internal without damaging other ROMs. It is pretty straightforward. For further questions read OP and use search in thread.

Any wipe done on recovery interface and any unpatched zip flashed in recovery may/will damage every multiboot ROM.
[Galaxy S 4 i9505 Original Android Development] Borbingo Boy:
Android/obb permission fix?