yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] klorinczi:
Did anyone successfully build Dual Boot Patcher apk with Docker?

I get this error:

Also posted problem here:

https://stackoverflow.com/q/52915760/4523359

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] marcdw:
Searching means using the search feature. It does not mean reading through 1350 pages. Big difference. Know the difference. It'll help next time someone suggests searching. As a senior member I'm sure you know that already. ?
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
Pls clean this searching topic... Sometimes u get nice and relevant answers immediately on posting questions rather than searching. So i guess nothings wrong with post while searching. :good:
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
Can anyone confirm this? Dbp failed backup on jota+. Tried on lineageos15.1 and RR, both Oreo. I uninstalled the apk and the backup went through on both ROMs..:confused:
[Galaxy S 4 i9505 Original Android Development] klorinczi:
This is a known backup problem.

Unfortunately DBP has a bug with doing backup of files having UTF-8 filenames.

I would also like to have it fixed.
[Galaxy S 4 i9505 Original Android Development] Eleo:
So you say that users have to help you again and again even though it was answered repeatedly but you should not bother to search in thread for 5-10 minutes? Wow...

​
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
shhh. that level of thinking. u don't need to answer if u don't want to.I'm not forcing you to answer my questions. If u don't have relevant answer to reply to a question, just don't mind it. sigh
[Galaxy S 4 i9505 Original Android Development] klorinczi:
Good news!

Yesterday chenxiaolong was active again.

Welcome back!

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] Nenphy:
BUG

I noticed that everytime i click on my rom to install (after patched) the app crashes,so i downloaded the oldest version of dualboot that i found on the site and now it's installing normally,if something else happens i will tell you. My zenfone is Z00A,i posted here because it's the main topic linked to the website,my cellphone is on the compatible list. Good Work btw
[Galaxy S 4 i9505 Original Android Development] Nuovo Imperium:
Error

Hi Team,

I have no luck using DBP. I have a Xiaomi Redmi 5 Plus 4/64 with MIUIPro 10 8.10.25, 7.1.2 ROM and wanted to try the latest RR Oreo 6.2.1, 8.1.0. Downloaded the zip and first it failed with a very common issue. I deleted 'assert lines' and the progress moved on, but later stopped with another message and I haven't found a solution yet. Any guess?
[Galaxy S 4 i9505 Original Android Development] marcdw:
I could be wrong but as far as I know Oreo as secondary is still not doable. At least not without a modified boot image / kernel. Someone will correct me if that's no longer the case.

Question: Looking at the name of the RR zip you're flashing. Not familiar with the "dual" suffix that it has. Is that one of the destinations you patched it for?

LG G3 D851, Candy v6.0 ROM, LineageXTD-R7 Kernel, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] Nuovo Imperium:
You are probably right, Marcdw. Browsing comments, it looks like almost anyone have problem installing any Oreo ROMs. Too bad, because even Oreo will be outdated soon. If I'm really dedicated, I will probably need to wipe MIUIPRo, install Oreo as Primary and use MIUI ROMs (7.1.2) as secondary. Which is also not long term plan, because MIUIPro also will be soon Oreo-based...

The "-dual" tag was added by DBP by default and was saved next to the original zip.

Thanks! :)
[Galaxy S 4 i9505 Original Android Development] B0bby1985:
Does anyone know if there's a working version for the pocophone F1?. I tried searching but no avail. Many thanks
[Galaxy S 4 i9505 Original Android Development] marcdw:
Not supported. It was kind of / sort of released when DBP stalled. List of supported devices is here...

https://dbp.noobdev.io/supported_devices.HTML

Moto G5S Plus XT1806, OmniROM, microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] Eleo:
Please ask [MENTION=6084385]yshalsager[/MENTION]. He did xiaomi dualboot patcher compatibility.
[Galaxy S 4 i9505 Original Android Development] yshalsager:
Unfortunately as Oreo is not working properly with current DBP versions, there's no use of trying it with new xiaomi devices.
[Galaxy S 4 i9505 Original Android Development] kullurumanoj:
Hey ,

Can anyone tell me why I'm getting this error while installing patched zip through twrp and my device is mido. Tried on redwolf and also latest twrp build

Error : Updater process ended with error :1

script aborted: E3004: This package is for "mido" devices; this is a "".

Attached logs

Thanks in advance
[Galaxy S 4 i9505 Original Android Development] jer194:
Check this (or search for 'This package is for') ...
[Galaxy S 4 i9505 Original Android Development] marcdw:
I see there have been several updates to DBP this month. Nothing major as far as new devices or any hint of Oreo support but nice to see work resuming on it.

Just thought of something. In recent months Oreo ROMs have introduced early system mount. When booting such ROMs they crash MultiROM big time. For the sake of argument let's say DBP was working fine with Oreo. Quite sure that the early system mount thing would be a problem.

Using MultiROM on my Moto G5s Plus with several Oreo ROMs. Per above, not the later builds. The device is also supported by DBP which is odd given that the device has only had Oreo custom ROMs. I don't see or recall seeing any Nougats, other than stock, to multiboot.

Me thinks the multibooting days are at an end.

LG G3 D851, Mahdi v2.9 ROM (4.4.4), microG (NoGApps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] tsqr121:
huawei
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
I'm having this problem. Any ideas?Edit: I posted in the wrong thread!
[Galaxy S 4 i9505 Original Android Development] Rahul927472927:
Does it work for the kalilinux or nethunter as a secondary rom.......

Plzz help am using Lenovo zuk z2 plus
[Galaxy S 4 i9505 Original Android Development] China2058:
The application crashed. Micromax A310。Please solve this problem.
[Galaxy S 4 i9505 Original Android Development] marcdw:
That's not how this works. Full ROM and android version? Logs? Checked github for known/related issues? Tried a different version?

LG G3 D851, PAC-ROM 6.0.1, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] theleftykid:
Can you please add support to LG V20 H990DS please. I tried the latest version but I could not install the patched zip as it's only supported for H918. Thank you.
[Galaxy S 4 i9505 Original Android Development] siMp0lMaN:
what does error code 200 mean? tried to patch kernel and it gives me code200.. tia
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I have a question: Im having an A5 2017 Exynos version. The patcher officially supports the A5 2017. But does it supports the Snapdragon or Exynos model?
[Galaxy S 4 i9505 Original Android Development] AliceOff:
Samsung Galaxy a5 2017

Why not works on android 8? just < 8
[Galaxy S 4 i9505 Original Android Development] De_A:
Has anyone got it working on the Galaxy Project Rom for the Samsung Galaxy S7 flat with Oreo (The Galaxy Project 2.5.1 as Primary rom)?

I got it installed (after removing the device ID check) and it installed fine. But then I got the 5 vibrations when booting (Primary rom (The Galaxy Project, Oreo) as well as the second slot rom (Lineage 14)).

After restoring only the Boot image via TWRP I got back to normal, but no dual rom unfortunately.

Used the latest DPB of december 15th.
[Galaxy S 4 i9505 Original Android Development] iam2luckyy:
How can i flash Gapps to the secondary rom?

Can i do it through the TWRP?
[Galaxy S 4 i9505 Original Android Development] pocketrule:
Yes, you can :svetius:

You should (always) read first post, there's a description how to
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Hey, I have an issue with building the app with TravisCI.

When I try to build it, I get an error after 5-10 minutes:

The command "docker run --rm -i -e USER_ID=$(id -u) -e GROUP_ID=$(id -g) -v "$(pwd):/builder/DualBootPatcher:rw,z" -v "${HOME}/.android:/builder/.android:rw,z" yshalsager/dualbootpatcher:9.3.0-4-linux bash << EOF

Does anyone knows how to fix this?
[Galaxy S 4 i9505 Original Android Development] clewis.it:
Does anyone know the command to start the mbtool manually without opening the dualboot patcher app?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Can anyone build the apk and utilities for me?

Im getting errors with every method: Building from source gives me an error (I dont know the exact error at this moment). Travis also isnt able to build it.

With docker using manually generated images, I only get an error that says "JAVA_HOME is not set", but it is set.

When using the images from chenxiaolong, I get an error that says "The C++ Compiler Clang++ is not able to compile a simple test program" (I didnt installed Clang++, it is using the one from Android NDK).

So this means, that Im not able to build it.

I wantet to build it for the A5 2017 Exynos version, which only difference to the Snapdragon version is a different architecture (arm64-v8a instead of armeabi-v7a).

The Snapdragon model is officialy supported, but the exynos not.

So can anyone build it for me?
[Galaxy S 4 i9505 Original Android Development] lxwx:
Your /system is read only. you have to unlock it.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Am I the only one who is not able to build the app with the build methods?

All of them are giving errors
[Galaxy S 4 i9505 Original Android Development] marcdw:
That was way WAY too much. For future reference don't post large logs like that. Attach them, or put them online and post a link, or upload logs to hastebin/pastebin and post a link.

LG G3 D851, Paranoid Android 7.3.1, NanoDroid, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] 그랖조닛:
Im sorry

next time i will upload it somewhere and give the link
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
Does dual boot not patch Oreo or pie roms? Because none seem to work on both my phone's.
[Galaxy S 4 i9505 Original Android Development] marcdw:
I believe it'll patch Oreo just fine, whether or not it flashes or boots is something else. I believe for Oreo to work one needed a kernel pre-patched to work with DBP. I have a couple of older Oreo ROMs as secondaries on my Axon 7. Can't test anything newer due to bootstack requirements/restrictions. Plus I'm not sure how DBP handles early system mount that was added to Oreo last year.

I'm quite sure Pie is out of the question altogether.

LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] Antidote03:
So there is no hope for poco phone f1 even in pie(android 9) ?!!
[Galaxy S 4 i9505 Original Android Development] yshalsager:
Yeah. Unless it's updated, which is taking a lot of time.
[Galaxy S 4 i9505 Original Android Development] hacker12:
Dual booting 64 bit ROMs on the Moto G5

Can 64 bit ROMs be dual booted using DBP, since the architecture listed on the DBP site is armeabi-v7a, but the device has a 64 bit SoC. Maybe it would be possible to make separate versions for 32 and 64 bit ROMs?
[Galaxy S 4 i9505 Original Android Development] marcdw:
I suppose so. On my Axon 7 the stock ROM is 32-bit (I believe) but the custom ROMs are 64-bit.

Moto G5S Plus XT1806, balanceOS 2.0, MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] matkali:
why dualboot patcher is not support oreo for samsung phones?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Im successfully booting Oreo and Pie ROMs on my oreo based Samsung device
[Galaxy S 4 i9505 Original Android Development] clewis.it:
Are you using those ROMs as an unpatched primary? Or in secondary, data slot, etc?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Im using Stock ROM with Android 8 as primary ROM. Secondary and cache slots are to small, so Im running Pie ROM in data slot.

Only extSD slot isnt working, vibrates 5 times at start and boots to recovery.
[Galaxy S 4 i9505 Original Android Development] gaww:
Are you using TW or AOSP rom in data slot ? Also, which version of Duelboot Patcher are you using ?

I had given up trying to patch oreo on my S7 and now my S9+ some time ago.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
To be honest, Im using a self-compiled version of DualBootPatcher based on the official sources from last week I guess.

Primary ROM is TW with android 8 and Im using PixelExperience based on Android 9 in data-slot.

My device is A5 2017 Exynos (Exynos version is not official supported).
[Galaxy S 4 i9505 Original Android Development] gaww:
Is the self compiled version one of the latest, or basically the same as one you could point at. Or, if you have a zip of it that you could shared it would be greatly appreciated.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Its similar to the official builds, but with support for my device.

I can attach the link to the apk if you want.

I also could send you my source folder, but I think there is no difference to the official sources(did not changed anything except the devices).
[Galaxy S 4 i9505 Original Android Development] gaww:
If you knew the closest official build(s), I could try one first. Of course if it (probably) doesn't have S9's supported, it would not work.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Dont know the closest build, Im sorry.

But I could try to compile it from latest sources with S9 support (but you must send me your logs).
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Mate, how you have Oreo and Pie support? :D

I have Naougat as primary ROM, is it possible to flash Oreo or Pie? Can you tell me what should I do? I have Galaxy Note 3. Should I edit kerner before or what? :)
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I dont know why Oreo and Pie ROMs are working for me. I dont even know if the sources already got Pie support.

But I can say is that Pie is successfully dualbooting for me.

I will try some more Pie ROMs, maybe its a bug or so.

And I dont edited my kernel or so, I just built the app like its guided in the DBP wiki.?
[Galaxy S 4 i9505 Original Android Development] PhoenixGamer:
As Moto g5, g5 plus and g5s plus are supported, please also add the moto g5s to the supported list. i used the app on my p8 lite, but now i got a g5s, and i`m not shure if i could use the g5 mode
[Galaxy S 4 i9505 Original Android Development] consumimur:
is it possible for dbp to work on a A/B device ?
[Galaxy S 4 i9505 Original Android Development] MisiekDP:
Huh, I need to test it, maybe dualbooting Oreo or Pie is working for me too ?
[Galaxy S 4 i9505 Original Android Development] gaww:
Sorry been busy with other stuff. What are the specific logs you are referring to (been a long time since messing with things like this)?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I mean the getlogs.zip you can get from https://dbp.noobdev.io/downloads/

Flash the zip in recovery and it will generate a new folder in internal storage with a .tar.gz file in it. If you extract the .tar.gz file, you will get a few folders with .log files in it. From the log files we can get the block devs that are needed for supporting a new device
[Galaxy S 4 i9505 Original Android Development] gaww:
Is sending a the file attached here safe - just ran it ?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Yes, just attach it to your post.
[Galaxy S 4 i9505 Original Android Development] gaww:
I only saw 4 logs
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Its easier if you attach the whole .tar.gz file, not every single item in it^^
[Galaxy S 4 i9505 Original Android Development] gaww:
Sorry...
[Galaxy S 4 i9505 Original Android Development] Simon1511:
No problem?

Will compile a version with S9 support in the next days.

But I dont guarantee that it will work without problems (on my self compiled version I cant boot from sd card).
[Galaxy S 4 i9505 Original Android Development] gaww:
In any case it will be greatly appreciated.

I miss chenxiaolong being here and developing. I was one of the first ones to use the original Duelboot on my S4.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I finished building a version with S9 Plus support built from the latest sources.

Patcher: https://drive.google.com/open?id=1NDy3srdnHumt0fXPkhJh4imaAbgR1Chz

Utilities: https://drive.google.com/open?id=13HBbrT-ATCosIT7vNX1PlJ6bI8bpydSh

Hope it will work for you :)

Also a note for everynone who is reading this thread

DualBootPatcher supports Android Oreo and Pie, but devices based on project treble arent supported by the patcher!

So everyone except for treble users should have oreo and pie support when using the latest builds.
[Galaxy S 4 i9505 Original Android Development] gaww:
Thanks - will try latter after several beers have run their course.

Also, not familiar with project treble...?
[Galaxy S 4 i9505 Original Android Development] clewis.it:
Thanks for the explanation. I actually use a note 4, so I don't think project treble is involved there. However, I can verify that AOSP Oreo and Pie ROMs for my phone use the early mount method to mount /system. I have tried to edit the boot image dtb, but it leaves the phone hung at the boot animation when I try to separate the dtb files and re-append them.
[Galaxy S 4 i9505 Original Android Development] gaww:
Holy s__t - it worked.

Just to try it I patched another TW Pie ROM similar to the "Prime" Rom I had installed. Couldn't reboot the Primary after flashing and booting the Data slot one, but realized i had not set its kernel yet, so restarted with utilities and set kernel (had already set the other one) and now can go back and forth as I last did on my S7e.

Question - You said above that we can use latest builds - will new builds affect the device's duel boot capability ?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
No, it shouldnt affect the capability of dual booting.

What I meant is that I dont know since when pie roms are supported.

With latest builds I mean the ones I built, official patcher doenst support our devices.

But nice to hear that it worked for you?
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
I tried a marshmallow rom on my LG g3 and it got an error 1 so I don't know if I am doing it right.

As for my a5 I never could try dual booting on data slot as it is stuffed full of apps. Anyone know what error 1 means?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Do you get the error on both devices or just in the LG one?

And when do you the error? When flashing a ROM on extsd slot?
[Galaxy S 4 i9505 Original Android Development] rys1903:
good

nice job
[Galaxy S 4 i9505 Original Android Development] marcdw:
When you get the Error 1 what else does it say on the screen? You're best bet is to check the Multiboot logs that are generated. If flashing in TWRP save the recovery.log via TWRP's Advanced menu.

Doing a web search on Error 1 doesn't come up with much. Mostly Magisk related but there have been others related to incomplete zips or not enough space in /system. The G3 has a rather large partition there so that's not it.

Were you installing the MM ROM as a secondary? I noticed on my Axon 7 that DBP needs a good amount of work space when doing its business.

But consult any logs. Best way to know what's going on.

LG G3 D851, AospExtended v5.7 ROM, NanoDroid-microG (NoGapps), MultiROM, XDA Legacy
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
I have tried ext sd and data slot on the lg. My Samsung a5 I can only test extsd because internal storage is almost full. Anyway here is a screenshot from the a5. (Says the same on the g3 as the a5.)

I get the error when flashing on either slot.
[Galaxy S 4 i9505 Original Android Development] marcdw:
[MENTION=9069680]iloveoreos[/MENTION], screenshot shows that your Samsung device isn't recognized properly, resulting in an Error 7 in the logs. Once that happens everything else fails. I've seen a lot of posts where that happens. I'm sure others will help on that front. On my Axon 7 it is/was required to remove the assert lines from the updater-script before patching so never experienced that error myself.

I'll have to look again later at your G3 log. Are you trying to flash one of those MIUI patch ROMs? Just curious.
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
I tried to dual boot the MIUI rom as it is marshmallow and therefore should work. But it didn't. I looked at the logs but I am not knowledgeable enough about them.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
As [MENTION=6046143]marcdw[/MENTION] said, it does not recognize your device (have had this problem on some roms too).

But its easy to fix: Extract the roms zip file and go to folder META-INF/com/google/android and open the updater-script file with a text editor.

Then remove the first lines starting from "asserts" (without the ") until the first semilocon (I mean this ; ). Save the file and repack it as a zip.
[Galaxy S 4 i9505 Original Android Development] SnowFuhrer:
Ok, I will try.
[Galaxy S 4 i9505 Original Android Development] gaww:
I have been trying for several hours to patch and install another ROM on my S9+.

One problem is that it is a Note9 Port, so even when i flashed it un-patched as primary ROM, your modified Duelboot app would FC when selection "ROM" - like before.

I changed the buildprop device names to S9+ (start2lte, etc and model to G965U. Then The Duelboot app worked OK again.

I thought changing the names in the zip and flashing it to a data partition would work, but it kicked out when flashing without doing much. I thought maybe the above would help, but there was no "asserts) in the updater-script.

I had also tried flashing it without patching as per the above after changing the buildprop. However, when I switched the data slot to where I had flashed a patched S9+ ROM successfully, on booting it ended up the same as the N9 primary ROM ???

So I have a real mess - lol, and have run out of ideas.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Dont you have a G965U? Though you have one because everything from the logs was similar to it.
[Galaxy S 4 i9505 Original Android Development] gaww:
No - I must have been on a G965U Modded ROM when I created the logs. I have a G965F/DS (only use SIM 1). The first ROM I tried and was successful with the patcher was a G965F build.prop.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Im sorry, didnt knew that.

Will compile a new version with that fixed
[Galaxy S 4 i9505 Original Android Development] gaww:
I should have thought of it. Was surprised as the Dev is in Germany and would have thought he had one also.

Thanks a bunch.

PS - had tried flashing a ROM, backing it up with Duelboot App, then after wiping everything and restoring the other ROM, then restoring the first ROM but sent it to a Data partition. I have backups of both ROMs in different folders, but it still installed the primary ROM again in the data partition rather then the one I had chosen ?
[Galaxy S 4 i9505 Original Android Development] Simon1511:
Im confused :confused: . Can you explain this a bit easier? xD
[Galaxy S 4 i9505 Original Android Development] gaww:
I tried backing up two roms with the duel boot app. On my s7, I could restore them with the duelboot app, but in different partitions .

Couldn't do it here, as it somehow reinstalled the wrong app. Since I couldn't patch and flash the data partition rom I wanted, I tried a back door that used to work.
[Galaxy S 4 i9505 Original Android Development] Simon1511:
I will test this on my A5, could be a bug in my build
[Galaxy S 4 i9505 Original Android Development] gaww:
Again- appreciate it.

Note - it worked perfect with the 965F ROM I tried first.