yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Eleo:
Are you requesting a ROM or asking for device support for DualBoot? If you are requesting a device support please share getlogs.zip. If you are for other intentions, please post in relevant thread.
[Galaxy S 4 i9505 Original Android Development] mbr007:
Ok. Thanks.
[Galaxy S 4 i9505 Original Android Development] monkteo:
to do what ? can you be more specific ?
[Galaxy S 4 i9505 Original Android Development] dimuthu7:
I have send log cat with previous and i am try to install as dual jdc 8.1.0 rom and its fail.here is the log cat.s4 i9505.primary is tw wizcyan.
[Galaxy S 4 i9505 Original Android Development] necoman51:
Please add support for Acer Liquid Z530

Logs - https: //yadi. sk/d/ Ieo5DUup3PY76a - Clear the spaces

I did load the logs on yandex.disk because I don't know how to load on xda-developers
[Galaxy S 4 i9505 Original Android Development] Lola22i:
To use app sharing it ask to update the ramdisk .. but the update failed

Here is the log
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Can you provide edited magisk.zip?
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Thank you..

Finally I'm able to use magisk v14.3 after editing updater-binary.

Edited magisk v14.3 has been attached..

Tested it in Lineage 15.0 alpha build of lenovo k6 power in external sd slot.

Edit: This edited magisk works only if rom is in EXTERNAL SD SLOT.

NOT working if in data (internal storage) or secondary (dual) slot.

:(
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
What you said to edit in util_functions.sh has been already there in common/uti_functions.sh

What exactly needed to be edited?

Or can you please provide edited magisk.zip

As i added those three rm lines in updated-binary but that edited magisk works only if rom is in external_sd_slot.

Thank you.
[Galaxy S 4 i9505 Original Android Development] vczilla:
Are you sure you modified util_functions.sh ?

The change is quite small but really crucial ( basically replacing grep $1 by grep " $1 " ).

Because that's one of the reasons why Magisk wasn't installing on a data slot.
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Yes.. it has been just modified.. as i saw that change before few minutes.. i tested it but not working on dual & ext sd slot now.. don't know what I'm doing wrong.. can you attach modified util_functions.sh here?
[Galaxy S 4 i9505 Original Android Development] vczilla:
Probably nothing, I just tested it with a data slot so I might have overlooked something.

I don't think I can attach files yet, I'll try.

A good trick is to add this to updater-script:

set -x

That way every command executed is logged ( in Multiboot.log ).
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Sadly this too not working.
[Galaxy S 4 i9505 Original Android Development] vczilla:
You're gonna have to join your Multiboot.log.

Don't forget to add the set -x line to updater-script
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
If you're on telegram, can we talk there..? it's more convenient.. I'm [MENTION=2748018]drbat[/MENTION]hman
[Galaxy S 4 i9505 Original Android Development] unhappy666:
Support

Hello there! Could you please make it work on Cubot Dinosaur?:o
[Galaxy S 4 i9505 Original Android Development] vczilla:
Sorry dude I'm not.

Just attach your Multiboot.log and I'll try to figure out in my spare time
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
No problem..

I've added set -x at the end of updater-script of magisk.

Logs attached..

(Not able to attach log file, so just attached screenshot)

Thanks.
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Attempted again after editing with mixplorer.. logs attached
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Idk, but the issue with data & dual may be due to system is not in the form of system.img in data & dual rom, while in ex sd, it's in system.img form.. ?
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Finally, I found out the way.. to use magisk perfectly in non-primary ROMs of Dual boot patcher..

Guide is here.

https://xdaforums.com/apps/magisk/guide-t3703596

Hopefully it will work with all ROMs!

Tested in my Lenovo k6 power in data ROM.

:)
[Galaxy S 4 i9505 Original Android Development] gaww:
I simply patch and flash old version, then flash and then let it update - works every time.
[Galaxy S 4 i9505 Original Android Development] vczilla:
Well, this Multiboot.log is for an install to data-slot-1.

Since you didn't add the set -x command there's no log of all the commands issued.

The install fails because Magisk tries to mount /data and /system and fails because Dual Boot is not intercepting the mount command.

Meaning Magisk's busybox is still probably there.

If you'd be so kind to attach the patched Magisk you used, that'd be helpful.

Cheers
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
I've attached ext-sd-slot-2 patched which has been modified as same as that data-slot-1 magisk.. attaching this as that data-slot-1 file has been deleted by me..

Between i added set -x in the end of updater-script..
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Which old version?

Can you attach that old version of magisk or put a download link..

Thanks.

---------- Post added at 08:17 PM ---------- Previous post was at 07:40 PM ----------

Well, thanks for advice.. i patched Magisk 12.0 & flashed then updated.. working fine.
[Galaxy S 4 i9505 Original Android Development] vczilla:
Thank you.

So the reason it's not working is because of where you made the changes.

In update-binary you added the three commands to remove Magisk's busybox's mount, umount and reboot after updater-script gets called thereby not enabling DBP to intercept these and do its bind mounts.

You have to insert these lines before that.

A good place is just after the export PATH line, like so:

$BBBIN --install -s $TMPDIR/bin
export PATH=$BBDIR:$PATH
rm $BBDIR/mount
rm $BBDIR/unmount
rm $BBDIR/reboot

Same problem with the set -x command.

It has to be issued at the start of updater-script.

If it's added at the end nothing is gonna get logged since everything has already run.
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Thank you very much. :)
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
After editing magisk according to your advice, it's working.

Now some issues related to magisk modules..

1. If non-primary ROM is dual, flashing any magisk module which contains app/priv-app leads to either boot loop (tried in lineage) or system ui crashes( in aospa).

2. If non-primary ROM is data or ext-sd, flashing magisk module which contains app/priv-app causes nothing. I mean no bootloop but there's nothing to gain too.. e.g. i tried greenify4magisk, it has been flashed successfully but when rebooted, there's nothing in spp drawer, nor in system. No greenify app. Magisk shows greenify4magisk in Module list but there's nothing in app drawer/system.

Though Modules which do not have app/priv-app, they worked perfectly like i tried Module which changes Bootanimation and it worked.

Note: this happens in all three methods of flashing magisk in non-primary ROMs.

1. Edited magisk 14.0/14.3

2. Patched boot method

2. Flashing old magisk (12.0) then updating it after boot.

Edited magisk is attached.

Kindly look in this issue.

Thanks.
[Galaxy S 4 i9505 Original Android Development] waleeds1:
Boot ui doesn't show up for me, my phone directly boots to the rom. My device is supported for boot ui and I have updated ramdisk for both the roms.
[Galaxy S 4 i9505 Original Android Development] amitpartial:
Redmi 2 prime HM2014818 is not supported
[Galaxy S 4 i9505 Original Android Development] ksigit:
[MENTION=4277844]chenxiaolong[/MENTION] please add support for moto g5s plus (XT1805, sanders)..
[Galaxy S 4 i9505 Original Android Development] vczilla:
There's still one thing preventing it from working and it's due to how Magisk tries to mount its mirrors. I've been trying to find a workaround but I'm afraid this one would require submitting a patch to Magisk's developer.
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Yes.. in saw mrror was empty in non-primary ROM.. hopefully you'll find out the way to fix it. :)
[Galaxy S 4 i9505 Original Android Development] riazh172:
Working on s4 Docomo

Thanks for your app I managed to get it working on a galaxy S4 Docomo also known as SC-04E Codenamed as jfltedcm

Thanks Again
[Galaxy S 4 i9505 Original Android Development] vczilla:
For your entertainment ladies and gents here's a patched version of Magisk, with the mirror mount stuff working.

My usual modules are working with it but your mileage may vary.

Basically in order to force Magisk to bind mount the already mounted /system we trick it into thinking our device is a skip_initramfs device, by inserting a mount point called /system_root and bind mounting the / rootfs.

It only works pretty early during the init process.

All of this is just a really bad and fragile hack, a real patch is gonna have to be written and submitted at one point.

The necessary modifications are thus:

diff -dru mk/META-INF/com/google/android/update-binary mk-patched/META-INF/com/google/android/update-binary
--- mk/META-INF/com/google/android/update-binary	2017-11-18 06:27:38.266119091 +0000
+++ mk-patched/META-INF/com/google/android/update-binary	2017-11-18 06:43:50.976118720 +0000
@@ -25,6 +25,13 @@
echo $BB_X86 | $EXBIN > $BBBIN
fi
$BBBIN --install -s $TMPDIR/bin
+
+#multiboot
+rm $BBDIR/mount
+rm $BBDIR/umount
+rm $BBDIR/reboot
+
+
export PATH=$BBDIR:$PATH
if $INDEP; then
shift
diff -dru mk/common/boot_patch.sh mk-patched/common/boot_patch.sh
--- mk/common/boot_patch.sh	2017-11-18 06:27:37.866119091 +0000
+++ mk-patched/common/boot_patch.sh	2017-11-18 06:43:51.116118720 +0000
@@ -193,6 +193,7 @@

cpio_add 750 init.magisk.rc init.magisk.rc
cpio_add 755 sbin/magisk magisk
+ cpio_mkdir 777 system_root
fi

mv init.magisk.rc.bak init.magisk.rc 2>/dev/null
diff -dru mk/common/init.magisk.rc mk-patched/common/init.magisk.rc
--- mk/common/init.magisk.rc	2017-11-18 06:27:37.906119091 +0000
+++ mk-patched/common/init.magisk.rc	2017-11-18 06:43:51.156118720 +0000
@@ -1,5 +1,8 @@
# Triggers
-
+on fs
+ chmod 0777 /system_root
+ mount none / /system_root bind rec
+
on post-fs
start logd
start magisk_daemon
diff -dru mk/common/util_functions.sh mk-patched/common/util_functions.sh
--- mk/common/util_functions.sh	2017-11-18 06:27:37.856119091 +0000
+++ mk-patched/common/util_functions.sh	2017-11-18 06:43:51.076118720 +0000
@@ -164,9 +164,9 @@

is_mounted() {
if [ ! -z "$2" ]; then
- cat /proc/mounts | grep $1 | grep $2, >/dev/null
+ cat /proc/mounts | grep " $1 " | grep $2, >/dev/null
else
- cat /proc/mounts | grep $1 >/dev/null
+ cat /proc/mounts | grep " $1 ">/dev/null
fi
return $?
}
[Galaxy S 4 i9505 Original Android Development] staurosthess:
I can't install batman s8 port in data slot...my phone is s7 edge
[Galaxy S 4 i9505 Original Android Development] Eleo:
This looks like the issue to me
[Galaxy S 4 i9505 Original Android Development] staurosthess:
Ooooo thanks man....i look again
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
Nice work.. all modules I'm using are working well.. i tried it in secondary ROM. Thanks. :)
[Galaxy S 4 i9505 Original Android Development] gaww:
Have patched and flashed thkg1994 IronMan n8 ported ROM on my 935f.

It would only boot with the stock kernel and not with the IronMan modded kernel. With the latter, it flashed ok up to final boot but then gave an error 1 and would not boot.

It must be the modded kernel - can this be setup here?
[Galaxy S 4 i9505 Original Android Development] touseef773:
i cant able to switch roms on samsung s7

when i switched it pop appears that rom switched successfully but after restart its the same rom
[Galaxy S 4 i9505 Original Android Development] monkteo:
IronMan for 935f you mean S7E ? can't find it , some link ? THX

update ramdisk and set kernel
[Galaxy S 4 i9505 Original Android Development] touseef773:
how to update ramdisk i try to update ramdisk in dualboot patcher but there is error ramdisk failed to update
[Galaxy S 4 i9505 Original Android Development] monkteo:
what rom you have primary,

what model of phone have

what is the secondary rom ?????????????????
[Galaxy S 4 i9505 Original Android Development] gaww:
The trouble was this Rom, which can be used on s7 s8, and n8 had an optional kernel only for n8, so it crashes when selected for a s7.

The op (same as batman) has not moved it over to xda yet as it is a beta - but a very good one. It is available in their forum.
[Galaxy S 4 i9505 Original Android Development] touseef773:
mintorous s8 port v20 primary rom

samsung s7 flat

secondary rom is wr paranoid port n8
[Galaxy S 4 i9505 Original Android Development] monkteo:
because the primary it's a port you need to modify build.prop

(ro.product.device and ro.product.name.)

with - herolte
[Galaxy S 4 i9505 Original Android Development] touseef773:
only right herolte???
[Galaxy S 4 i9505 Original Android Development] monkteo:
Sorry I don't understand your question?
[Galaxy S 4 i9505 Original Android Development] touseef773:
its works mate thankssss

one more question how can i change the primary rom kernel and is it effect on dualboot
[Galaxy S 4 i9505 Original Android Development] edyny1:
Can someone please tell me why everytime i flash a new kernel into primary rom, the data-slot rom does not wants to boot and it just stays stuck at splash-screen? And i have tried flashing different kernels into dataslot and nothing, i also go back to primary and set kernel, update ramdisk and nothing...
[Galaxy S 4 i9505 Original Android Development] monkteo:
By on primary go to recovery and flash the kernel , no effect on other rom.

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

After flash kernel re-update ramdisk, work for me.
[Galaxy S 4 i9505 Original Android Development] dimuthu7:
Is anyone flash leanage 15 as dual boot rom with tw primary rom
[Galaxy S 4 i9505 Original Android Development] lee480:
Hey friends I'm currently on a Oreo ROM. When I try to flash a ROM in Dual Boot Patcher is crashes. I've attached the crash log. Pls help :crying:
[Galaxy S 4 i9505 Original Android Development] Letrix:
Can this be ported?

If its yes, how can I do it? Thanks
[Galaxy S 4 i9505 Original Android Development] vivekchharia:
I cant install open gapps on the secondary rom. Any help please & thank you.

Details:

Redmi note 4

Primary ROM - resurrection remix 5.8.5

Secondary ROM - lineage os 15
[Galaxy S 4 i9505 Original Android Development] yshalsager:
You can check everything in DBP Wiki ;)

https://github.com/chenxiaolong/DualBootPatcher/wiki
[Galaxy S 4 i9505 Original Android Development] dr.bathman:
I like dual boot patcher, it's very nice tool to use multiple ROMs.. but it would be nice if app do patching & flashing both together instead of manual patching then flashing zip. Actually patching multiple files is somewhat boring & time consuming particularly when you're custom ROM user & used to use multiple ROMs like 3-4 at a time & also patched files uses much storage space. So if patching & flashing can be done automatically just by selecting any zip, it can save much time & space.. useful particularly for devices which don't have dedicated external sd card slot. Thanks a lot. :)
[Galaxy S 4 i9505 Original Android Development] flyxiii:
I always get "Failed to update mbtool. Many operations, such as switching ROMs will not work." ? I have granted root permission but still doesn't work on my OnePlus 3T...
[Galaxy S 4 i9505 Original Android Development] Hayo Tee:
Device: S3 T-mobile.

The main system is stock 4.3 and multi-1: MokeeOS 7.1.2.

I can't access the folder "obb" on the Multi-1, but the main works fine. If I turn SElinux to permessive, then I have access, but the game crashes. How can I fix it?
[Galaxy S 4 i9505 Original Android Development] monkteo:
primary rom ?

secondary rom ?
[Galaxy S 4 i9505 Original Android Development] pinomelizzi:
s it possible to become a rom from secondary to primary without re-installing everything?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yes. Backup your secondary slot using DBP app. Click on flash ROM. Choose "from backup". Select your backup. Select the slot "primary". Restore to primary.

You need to do this booted on a ROM slot which is neither primary nor the secondary that you are moving.

This question has been answered several times already (like here with screenshots).

PLEASE use SEARCH button before posting next time

​
[Galaxy S 4 i9505 Original Android Development] pinomelizzi:
it is impossible to install this ROM or even RR 5v8.5
[Galaxy S 4 i9505 Original Android Development] pinomelizzi:
sorry for double post, I wanted to tell you this too
[Galaxy S 4 i9505 Original Android Development] flyxiii:
I can't even flash a patched ROM zip file so there is no secondary ROM. But primary is stock ROM OxygenOS 5.0 Android 8.0

[IMG="screenshot of the error I get when I go to 'ROMs'"]https://image.prntscr.com/image/D0aFr9dsRj6LGFCOo4S84A.png[/IMG]
[Galaxy S 4 i9505 Original Android Development] Exaskryz:
Does anyone have a good video tutorial on installing this?

I am confused because the original instructions instruct us to Patch on Windows to create a xxx_dual.zip ROM image. Then it tells us to Patch on Android to create your secondary ROM? Do we patch that same ROM, or is it that you can choose to patch a ROM on Windows or on Android?

I have TWRP already, and that's about as far as I am with this tutorial. Clearly I'm missing something terribly obvious, perhaps because I'm reading too far into the instructions.

Thanks in advance.

Edit: I mean, what is this for?

I see no mention of where you're supposed to use DualBootUtilities.zip anywhere. Following a video tutorial on this, they don't use it. But I'm getting errors! Ahh! Error is:

Any insight?

Edit: Added attachments. There is a 61 KB Multiboot.log file in the top level of my internal storage but I cannot move that file, copy that file, or upload that file.
[Galaxy S 4 i9505 Original Android Development] Mr. Lokkevit:
You can patch a flashable zip from the Windows Program OR from the Android App.

And the Utilities zip is an Aroma zip, which you can flash in recovery to switch roms, in case you can't boot the second rom.
[Galaxy S 4 i9505 Original Android Development] Exaskryz:
OK, thanks.

Sounds like this app isn't compatible with my phone or my OS for whatever reason. I've got the flashable zip created, but it just doesn't work. And if I can't even get the point where I have two roms installed, then I don't need to worry about not booting the second rom.
[Galaxy S 4 i9505 Original Android Development] Mr. Lokkevit:
Check if you have enough space. If you are positive you had enough (maybe like 2gb+), look at the Multiboot.log.
[Galaxy S 4 i9505 Original Android Development] Exaskryz:
The Multiboot.log doesn't even open!

I've got 10 GB free space on Internal storage and another 18 GB on External storage. Plenty of room. The error is given in my previous post, it doesn't appear to be amount lack of storage. It's that there's no multiboot files after I patch! I'll actually try patching on windows...

Edit: Patching with Windows made no difference. Exact same error screen, just with a differently named .zip file. Somehow it "failed to extract multiboot files from zip". Looking at the source code here: https://github.com/chenxiaolong/DualBootPatcher/blob/master/mbtool/installer.cpp, it's literally because it can't find the multiboot files...

Looking closer to it, I'm missing this file in the .zip archive: META-INF/com/google/android/update-binary.orig ... It's this function that fails:

bool Installer::extract_multiboot_files()
{
std::vector<util::ExtractInfo> files{
{
"META-INF/com/google/android/update-binary.orig",
_temp + "/updater"
},
{
"META-INF/com/google/android/update-binary",
_temp + "/mbtool"
},
{
"META-INF/com/google/android/update-binary.sig",
_temp + "/mbtool.sig"
},
{
"multiboot/bb-wrapper.sh",
_temp + "/bb-wrapper.sh"
},
{
"multiboot/bb-wrapper.sh.sig",
_temp + "/bb-wrapper.sh.sig"
},
{
"multiboot/device.json",
_temp + "/device.json"
},
{
"multiboot/info.prop",
_temp + "/info.prop"
},
};

And I am looking at the .zip archive and find the "update-binary" and "update-binary.sig" files. But I don't have the "update-binary.orig" file.

I've got the other 4 files in the multiboot folder.

How can I resolve this? What is this .orig file? Can I just copy and paste the "update-binary" file and rename it to "update-binary.orig" ??

Apparently the .orig was what I thought it may be, a backup file:

So it sounds like I can totally just cheese this by putting in even a 0-byte update-binary.orig file. But that's also under the assumption that I am getting the Message "Failed to extract multiboot files from zip" because one of these files was not present. I'm going to bed to give time for someone to yell at me that this is a bad idea before proceeding with my idea of a fix.
[Galaxy S 4 i9505 Original Android Development] superchandan007:
failed to update ramdisk

hello. im getting failed to update ramdisk error.

im using galaxy s7 with note 8 port

log is attached
[Galaxy S 4 i9505 Original Android Development] fmotta:
Is It possible to add support for OnePlus 5t? Regards

Inviato dal mio iPhone utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Exaskryz:
I just described the file situation. I'm missing a file that I imagine actually has no impact on the patching process, but the code expects it to be present. (I think it is flawed logic.)

I did look at the prompt; in fact it's all written out above with nice colored highlighting that (nearly) matches the original (changed yellow->green due to bright background on forums). It of course was not successful. I can't boot to the second rom because the Tool won't flash the second rom. It errors out very early in the process, saying it made 1 attempted action before quitting.

The original ROM (before patching it) works. Because I just flashed it on Saturday (2 days ago). I still have only one ROM. Only one ROM. There is no second ROM. I want there to be a second ROM. But the App refuses to flash the second ROM and gives an error. If I reboot my device, everything is normal.

My device is a Motorola Moto G4 which is said to be supported. https://dbp.noobdev.io/supported_devices.html#device_info_125 -- Motorola Moto G4 & G4 Plus Edition

However your screenshot gives me worry. Because I don't have an updater-script file either! In fact, I'll add in screenshots of my folder. As you can see, I don't have a "system" folder, and the ROM files itself are at the top level of the .zip.
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
You said that you flashed before your "original" rom (I guess like only rom), did you mean your stock rom? I guess that you have just a rom stock zipped but it needs to be a flashable zip, no matter if it´s based on your stock or is a custom but although in app from pc says that can patch an odin file (for Samsung devices) in this case you need to have a zip containing updater-script inside your meta-in folder. And if you haven´t any of this files in the screenshot uploaded then doesn´t work.

I think that you have some unnecessary files in your zip, if you will not update bootloader? recovery...
[Galaxy S 4 i9505 Original Android Development] Exaskryz:
Spell it out for me. Please.

I have a stock rom.

I run the DualBootPatcher.exe on the stock rom.

Does the DualBootPatcher not create a flashable zip? Or am I retarded? What's the point of the DualBootPatcher if it doesn't make you a zip file you can use?

Can anyone else give some information on this? I think me and SubwayChamp are speaking past each other.

My Stock Rom was downloaded from http://s65.filefactory.com/get/f/28...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip