yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] gaww:
There is not much room on S4's for roms, so that might be part if the problem. Even the S7 I have i s stretched to have both a s8 port and a s7 TW.

On that matter, in my S9 that you helped me setup, I have another stock based rom as data partition (I had 2 for a short while but dumped the first one).

First some reason i, cannot get patched Ultimate rom to flash. If I could, I would reflash a N9 port now and hopefully a S10 port later when one comes out.

Update - new version of Ultimate ROM was flashable after patched, so going to look at a Pixel experience and maybe the N9 port of I don't like it. They will be primary ROMs.
[Galaxy S 4 i9505 Original Android Development] gaww:
Try flashing with TWRP.
[Galaxy S 4 i9505 Original Android Development] Zulfi:
Same result form TWRP error 1
[Galaxy S 4 i9505 Original Android Development] gaww:
Then hard to tell. I am only able to install 1/2 of the roms I try even when they are similar
[Galaxy S 4 i9505 Original Android Development] gaww:
Simon - your modified App has stopped working - it FC's when selecting "rom". I think it is mbtool/ramdisk....

It was working great until now - have a number of roms up for weeks, but it doesn't work on any of them suddenly. Have to use utility zip to change roms.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Not just my self-compiled version FC's, every version does on some devices. This is not a bug in my version, its a generel bug in the official sources.

That means I am not able to fix this until Chenxiaolong fixes this in the sourcecode.

I am still running stock ROM with DBP and it works great. I havent tested other ROMs as primary, so I guess it only workes on a few ROMs.

Im sorry:(
[Galaxy S 4 i9505 Original Android Development] gaww:
Something just happened- there were some warnings about updating randisks. It must be at Chen's end that your compiled version crashed a day ago. I can't even use it on my primary rom.

I was wondering if your procedure would work on his current setup, ie. - resubmit the logs or something.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
On my phone it still works fine.

Guess this is because of the ROM you installed as primary.

I could compile a new version, but that would not change much because there have not been changes to the repo since February
[Galaxy S 4 i9505 Original Android Development] gaww:
View attachment 4739055

I started getting the above a few days ago. Coincidentally, I had been PM'ing an individual who was asking about duelbooting on a G965F and the last version you had posted. My problems started happening right about then. The first thing that comes to mind is if he tried to update ramdisk thru the ROM menu on the app, could that have messed it up? I had read many times not to do that.

Otherwise, could something else have happened related to that per the popup pic I attached?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
No idea to be honest, sorry:(
[Galaxy S 4 i9505 Original Android Development] gaww:
Fixed it. I had changed the build prop names from star2 to crown on a N9 port in data partition to try to get it to perform better.

Somehow, this got carried over to the prime rom (?) also, so the app did not find the device it looks for. Changed it back and it works again.

I only changed primary rom, but the data slot rom build prop also changed ?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Nice to hear that you fixed it.

You should be able to navigate to your data slot ROM in any file manager and change the build.prop manually I would say
[Galaxy S 4 i9505 Original Android Development] gaww:
I manually changed in the Primary ROM (I had originally done it in the data ROM only), but per the above - it also changed it in the data slot. I thought they were totally separate, but apparently not.

NOTE I went to my S7e, which has a Nougat S8e data slot and Oreo S7 primary. Their build.props are totally different (dream2 vs hero2) unlike the above. Don't get it.
[Galaxy S 4 i9505 Original Android Development] theman480:
Anyone having problems with Xiaomi Mi A1 ? Crashing when I tap the Roms tab. Can you help me?

Also when I try to flash the patched ROM on trwp, I have a " failed to create chroot twrp" error.

Maybe it's a problem with the Android pie update on mi a1?
[Galaxy S 4 i9505 Original Android Development] gaww:
https://github.com/chenxiaolong/DualBootPatcher/issues/1415#issuecomment-473709428
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Is your ROM treble based?

Because DBP dont support treble ROMs
[Galaxy S 4 i9505 Original Android Development] Rashid3006:
Installing different os

If i installed different android os, how to flash gapss? Example stock 8.0 n i install 9.0. need some guide
[Galaxy S 4 i9505 Original Android Development] Simon1511:
You can dowload the needed gapps at opengapps.org

Choose your device architecture (normally arm or arm64), then choose android 9 and the package you want to install (I normally choose pico because it only includes Play Store and Play Services, the rest can be downloaded from the Play Store).

The downloaded zip can be flashed and installed with DBP the same way you install a ROM
[Galaxy S 4 i9505 Original Android Development] ForForkSake:
Simon, do you think you can modify this slightly for s9 G960 please?

I updated apk to get it install but can't get it to boot
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Then I need the logs for your device.

You can flash getlogs.zip from dbp.noobdev.io/downloads in TWRP.

It will generate a tar file in internal storage (or sdcard?) that includes the needed log files. Just send this file to me and I will modify the patcher for S9
[Galaxy S 4 i9505 Original Android Development] ForForkSake:
Just PMd you a link. Let me know if you need any thing else.

Thank you :svetius:
[Galaxy S 4 i9505 Original Android Development] Simon1511:
How can I install magisk modules for a dual-booted ROM?

I have a second ROM in data slot with magisk installed. But how do I install modules for it?
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
Couldn't you patch the zip within the dualboot patcher, then flash it in the recovery?
[Galaxy S 4 i9505 Original Android Development] gaww:
I had done so in the past by just letting magisk install them directly. Haven't messed with recently.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Thanks I will try it out
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
Can i dual boot 2 roms with different android version? Like one with oreo and one with pie ?

I'm sorry if it's a dumb question, i'm a newbie xD Thx all.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Yes you can.

Thats what dualbootpatcher is supposed to do:laugh:

You can install every rom you want as long as its conpatible with your device
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
In theory, yes, but for me, I have never had luck on my phones. I tried on 3 or 4 of them.
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
Thx guys, i'll try my luck then on my Mi note 2 :D

EDIT: Just one other question, what if the second rom i want to flash needs a specific firmware base that is different from the one of the primary rom ??
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
I don't think it will work then unless you flashed it as primary and backed it up as an img and then flashed it as secondary.
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
I'm having some issues while trying to flash a secondary rom both by app and recovery.

I've attached the log file... if anyone can help me would be awesome :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Try installing to a different location like data or extsd slot
[Galaxy S 4 i9505 Original Android Development] carandcar:
In the several years I've been using dual boot I have never had this happen. There is a file on the root of my phone that I cannot delete and is preventing nandroid backups in twrp to completely restore.

The file is in /data/multiboot/data-slot-swap/data/data/com.android.vending/shared_prefs/finsky.xml (finsky is related to the playstore app somehow)

I have tried several root file explorers and even tried to flash back to stock to delete it and it's still there.

I am able to boot into dual roms but the playstore app will not open in the secondary rom.

Can anyone please help me with this? I have never seen anything like it.
[Galaxy S 4 i9505 Original Android Development] ahmedmoselhi:
i have mi max which version of dualbootpatcher work best for my phone??
[Galaxy S 4 i9505 Original Android Development] gaww:
If you are trying a "secondary" location, have you tried a data location?

Very little room on secondary.
[Galaxy S 4 i9505 Original Android Development] ahmedmoselhi:
i used the latest version of DBP and miui10-7.1 nougat as primary rom when trying to install any pie aosp rom and reboot the device boots to recovery no to the installed rom
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
As already suggested i tried to install both on data and extsdcard but always failing...
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
That was my main problem too. I wonder what causes it? [MENTION=7334446]simon151102[/MENTION], have you figured out from logs what causes it?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Have you tried a different ROM?

Made sure you patched it for the right device?

What error does DBP shows when trying to install this?

Log says:

xiaomi.verify_modem() failed to read current MODEM build time-stamp: 2

But I have no idea of what this means/how to fix this
[Galaxy S 4 i9505 Original Android Development] marcdw:
Boot into TWRP and use its file manager (from Advanced section) to delete the file. Or the vending directory altogether.

Are you using DBP's shared data feature thingy? Just wondering if the file is locked for some reason.

Moto G5s Plus XT1806, GZOSP v1.1, microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] carandcar:
Thanks for replying. I've tried to delete it in twrp and it still fails. I have tried the app share feature several times but never with the playstore app. It definitely seems locked. But why? Even reverting back to stock was not successful in deleting that specific file. Everything else gets deleted but it remains. [emoji22]
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
Just tried with a different rom, a pixel experience, patched it through the app because the winapp crashes evertime i select a zip file, and it ends up the same way. Wonder what's up with this modem error it gives...
[Galaxy S 4 i9505 Original Android Development] Simon1511:
It says "failed to read current modem build time stamp".

So it must be something with your modem.

Maybe try adding it to build.prop
[Galaxy S 4 i9505 Original Android Development] gaww:
I have had no success patching/flashing pixel experiences.
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
x

Yeah it's just that i have no idea of how to do it :(... don't even know what the modem is xD
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Ok I searched a bit on google about the error and most people say that its because the firmware is outdated.

So check if there is a newer version of your primary ROM and install it.

If it doenst work then try a custom ROM
[Galaxy S 4 i9505 Original Android Development] gaww:
I would use one if the stock based roms that include updated firmware first - don't ODIN one.
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
I am on miui eu latest dev build...so i think that the firmware is updated, maybe i should switch to stable ?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Give it a try, maybe stable works
[Galaxy S 4 i9505 Original Android Development] Gianluk99:
Just tried on stable and same error, seems like it just has to go this way xD thx for your help anyways :D
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I have a problem and maybe someone of you knows a solution to this:

My primary ROM is rooted with magisk. But when I install a ROM to data slot this ROM does not pass safetynet (even with magisk installed). But when I install a ROM to extsd slot I pass safetynet, but every ROM shows "issue with sd card" message and I cant acces it (formatting it makes no sense because my ROM is on it).

Is anyone facing the same problem or knows a solution?
[Galaxy S 4 i9505 Original Android Development] gaww:
I can't install on external - won't boot up. On data slot currently it is now just mirroring my primary. That's why I tried external.

At the end of the day, is it really possible for duelboot to work on S9 pie roms and not just mirror prime rom?
[Galaxy S 4 i9505 Original Android Development] twiztidditzwit:
How goes development?
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
Hi at all, is possible to add the support for Xiaomi Mi Mix 2S ?? :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Simon1511:
The devs stopped adding devices to the support list so you will have to add support for it om your own.

You can do it from source: https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-from-source

or with docker: https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-using-docker-images

or with TravisCI: https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-using-TravisCI

And for adding device support: https://github.com/chenxiaolong/DualBootPatcher/wiki/How-to-add-new-Devices-to-DualBootPatcher?

If you have problems building it or so we will help you
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Run again with --debug or -d so we can get more information about what is wrong
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
here the output (here begin the error)

[ 9%] File signing target 'sign_prebuilt_exfat_arm64-v8a'
Interruzione del processo figlio vincente 0x557d4f87e720 con PID 4831
Processo figlio vivo 0x557d4f87e720 (thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a) con PID 4833
-- Signing: /home/federico/workspace/dualbootpatcher-build/DualBootPatcher/build/thirdparty/prebuilts/exfat/1.3.0-1/arm64-v8a/bin/mount.exfat
/home/federico/workspace/dualbootpatcher-build/DualBootPatcher/build/thirdparty/prebuilts/exfat/1.3.0-1/arm64-v8a/bin/mount.exfat: Failed to open input file
140154834213760:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:74:fopen('/home/federico/workspace/dualbootpatcher-build/DualBootPatcher/build/thirdparty/prebuilts/exfat/1.3.0-1/arm64-v8a/bin/mount.exfat','rb')
140154834213760:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:81:
CMake Error at /home/federico/workspace/dualbootpatcher-build/DualBootPatcher/build/cmake/SignFiles.cmake:22 (message):
Failed to sign:
/home/federico/workspace/dualbootpatcher-build/DualBootPatcher/build/thirdparty/prebuilts/exfat/1.3.0-1/arm64-v8a/bin/mount.exfat

Interruzione del processo figlio perdente 0x557d4f87e720 con PID 4833
thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a.dir/build.make:57: recipe for target 'thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a' failed
make[2]: *** [thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a] Error 1
Rimozione del processo figlio 0x557d4f87e720 con PID 4833 dalla catena di esecuzione.
Interruzione del processo figlio perdente 0x56071c1c1c00 con PID 4830
CMakeFiles/Makefile2:91: recipe for target 'thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a.dir/all' failed
make[1]: *** [thirdparty/CMakeFiles/sign_prebuilt_exfat_arm64-v8a.dir/all] Error 2
Rimozione del processo figlio 0x56071c1c1c00 con PID 4830 dalla catena di esecuzione.
Interruzione del processo figlio perdente 0x55f26c3e2a10 con PID 4657
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2
Rimozione del processo figlio 0x55f26c3e2a10 con PID 4657 dalla catena di esecuzione.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Ah, I know what the problem is.

I have had the same problem on my system.

It automatically downloads needed prebuilts that are required for building.

I got this problem fixed this way:

Try building with docker. It will download the right prebuilts. You can then copy-paste them into your existing build

Prebuilts are in DualBootPatcher/thirdparty/prebuilts
[Galaxy S 4 i9505 Original Android Development] Simon1511:
You can also try cloning a different branch.

There is a branch without prebuilts, try them.

git clone --recursive [url]https://github.com/chenxiaolong[/url] -b remove-prebuilts

I can also send you the working prebuilts, I have them saved
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
yes, perfect! can you send me?? thanks bro ;)
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I will do!

I dont really know why cmake is not able to download the right prebuilts. Only docker can download the right ones. I will change to docker soon because its easier than building from source.

I will PM you a link when I uploaded them
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Today chenxiaolong ended the developement of DualBootPatcher as you can read here:

https://github.com/chenxiaolong/DualBootPatcher/blob/master/README.md

That means no support for treble, android Q and R
[Galaxy S 4 i9505 Original Android Development] marcdw:
Sad day. I'm an avid multibooter for some years now on three of my devices. I can't see myself running just one ROM. MultiROM support ended on two of them and now DBP on the third. I like older ROMs anyway so it doesn't hurt too much as long as I don't get the urge to go to Pie or later.

*sigh* The days of multibooting are at an end it seems. [emoji22]

ZTE Axon 7 A2017U, /e/ 0.6-n ROM, microG (NoGapps), Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] Mike0505:
+ 1 :'(

Using MR on Samsung Note 2 and Xiaomi MiMax

Big thank for Dev and all here for help and contribution:highfive:
[Galaxy S 4 i9505 Original Android Development] gaww:
He has left all the development to-date accessible to anyone who would like to pick it up. Would be great if someone did, but probably unlikely.
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
Hopefully someone continues it for a while. Probably not much chance though. I could see a new project rising that would take advantage of project treble and simply mount different images to system but gsi's are still a wip.
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
I always seem to miss out on the good things. I'm always just too late. Oh well.
[Galaxy S 4 i9505 Original Android Development] fefuzzo:
problem during flash

hi, i build from source the app for my Xiaomi Mi Mix 2s..

during the flash i have this error no file_contextsxiaomi.verify_vendor()

In attachments the log file.

Where is the problem??

Thanks at all
[Galaxy S 4 i9505 Original Android Development] gaww:
Yeah. It is still working on older android roms like on my s7+ but not for the new ones with the different rom structure.
[Galaxy S 4 i9505 Original Android Development] klorinczi:
Would be fine to make public anything you upload, so others can access it, too.

Could you share it on github?

Tapatalkkal küldve az én SM-N910C eszközömről
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I will do in the next few weeks.

The problem is that I accidently deleted my VM where my files were saved so I will have to start from the beginning again.

This will take me a few days, but I will tell you when Im finished
[Galaxy S 4 i9505 Original Android Development] gaww:
What are you working on ??
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Working on uploading my DBP files to Github with a detailed guide
[Galaxy S 4 i9505 Original Android Development] gaww:
I know Pie won't work, but will the revioys ROM structure work ie., use an N9 Oreo as a data partition DBP ?
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
This device that I've been trying to get this to work on is an Amazon Fire HD 10 running lollipop 5.1.1. kernel of 3.18.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Pie works as long as it isnt the primary ROM.

Dual booting Pie ROMs works but you need oreo or an older version of android as primary.

As far as I know not every pie-based ROM uses treble. The devices that got updates from oreo to pie dont use treble as far as I know.

It might be an option to try DBP on those devices.

Im sadly not able to test this because I dont own a device that runs pie

---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------

Did you tried to compile it on your own?
[Galaxy S 4 i9505 Original Android Development] ForForkSake:
I'll give it a shot later. Didn't know

---------- Post added at 08:23 PM ---------- Previous post was at 08:02 PM ----------

Its not currently Compiling due to an issue with outcome
[Galaxy S 4 i9505 Original Android Development] DragonFire1024:
Not yet. I am just now reading about it.
[Galaxy S 4 i9505 Original Android Development] gaww:
I had pie device with non treble roms and it didn't work. May try a non pie rom like n9 as primary and see if I can really flash a pie non-primary.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
This happens often but it can be fixed by executing

git clone [url]https://github.com/chenxiaolong/DualBootPatcher.git[/url]

(Without the thing at the beginning and end)

T...of timeout errors, but I will try again later
[Galaxy S 4 i9505 Original Android Development] ForForkSake:
Pretty sure I've tried that. I'll update my travis.yml when I get a chance later and let you know
[Galaxy S 4 i9505 Original Android Development] gaww:
What non-Pie ROMS come to mind to use as primary?

I may just use a relatively small one as primary only so I can use other current Pie roms as data partition roms so I can go back and forth between them.
[Galaxy S 4 i9505 Original Android Development] gaww:
Update- I tried the above with as oreo primary. I patched then flashed a pie data rom, but it would not really boot up - the primary did even though the ROM section said it was the one flashed.

Chen said getting pie to boot after flashing was the problem, which is still there apparently.
[Galaxy S 4 i9505 Original Android Development] marcdw:
Did DualBoot Patcher ever support early system mount? I figured Pie and Oreo (from late 2018) had that and thus not really bootable as secondaries. I know that's the case with MultiROM as the ROMs flash fine but will crash it when booting. I figure something similar with DBP?

LG G3 D851, crDroidAndroid v4.6 ROM, microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] clewis.it:
DBP does not support early system mount. If the ROM uses early system mounting even if you do not have a treble device, you would need to modify the boot image to remove the system fstab entries from the device tree (dtb) and add them to the fstab file. And you might need to modify an init.rc file.
[Galaxy S 4 i9505 Original Android Development] marcdw:
[MENTION=356908]clewis.it[/MENTION], yeah, I figured as much. On my Axon 7 with DBP I had two Oreo ROMs running, boot images pre-patched. That was awhile back though, currently running just Nougat ROMs.

Guess I have some work to do if I want to mess around with more recent Oreo/Pie. Thanks.

Moto G5S Plus XT1806, AospExtended v5.5 ROM, microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] marcdw:
Though I already knew about the project's EOL status I only recently realized the website was taken down also. For those who still mess around with older devices and ROMs the compatibility list was useful. Now that that's gone is there some other way to find such a list?

The website was still useful, not sure why they felt the need to remove it.

ZTE Axon 7 A2017U, AOKP 7.1.2 ROM, Radioactive v2.4 Kernel, microG (NoGapps), Multiboot, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Downloads can still be found here:

https://sourceforge.net/projects/dualbootpatcher/files/