yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] klorinczi:
Finally I was able to install Magisk v16 to Resurrection Remix Nougat v5.8.5 by patching the boot.img with Magisk app itself, in internal sdcard /multiboot/extsd-slot-rr585/.

Make sure you make backup of boot.img before patching it. Also switching to another rom from TWRP, then back is required to update the rom links.

I will create an install tutorial later.

Sent with Tapatalk from my Samsung Galaxy Note 3 SM-N9005
[Galaxy S 4 i9505 Original Android Development] tomaasz:
Later means never

Wysłane z mojego SM-G950F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] inspired55:
What does failed code 200 mean
[Galaxy S 4 i9505 Original Android Development] blackphanter:
Hi Guys!

I need a little help. I have a natrium device (mi 5s plus). I can install miui global to primary and i can install in data slot any custom miui roms. So on I can install primary aex rom to primary and i can install miui global to data slot. But everytime I tried to but miui i got bootloop. if I formated data i would face the same issue when i install aex at primary and i later booted in miui. Does somebody know how can i solve this problem?

I wannna use both rom. I am aware of that i can't install twisted way, i mean oreo rom can't install as data slot rom.

Please help me.

Thanks.
[Galaxy S 4 i9505 Original Android Development] pehoko:
Can I do flash primary rom without losing other roms, otherwise how to restore rom from dbp backup?
[Galaxy S 4 i9505 Original Android Development] rick_hxc:
Hi [MENTION=7863395]vczilla[/MENTION] can you make this mod using magisk 16 version?

Thanks!
[Galaxy S 4 i9505 Original Android Development] yshalsager:
docker images updated to v9.3.0-5 based on Fedora 28

https://hub.docker.com/r/yshalsager/dualbootpatcher/tags/
[Galaxy S 4 i9505 Original Android Development] tulipon:
Hello there, this app is great, but i have a problem, after wiping from the app three roms installed in the data partition didnt recover the used space. Tried wiping the data partition from recovery but the space remains lost. Any advice to get back the lost space? btw my device is a redmi 5 plus (vince) and I were using stock miui global as primary rom.
[Galaxy S 4 i9505 Original Android Development] gaww:
Use the app to eliminate all components of each rom one at a time.
[Galaxy S 4 i9505 Original Android Development] tulipon:
Alll the roms were deleted (using the app wipe menu) and dissapeared from the app list, also the mutiboot folders are no longer in the data partition but looks like the space they were using is not available anymore.
[Galaxy S 4 i9505 Original Android Development] marcdw:
How is it that you're determining that the space is unavailable? You say "looks like" which doesn't specify anything. Space available has not changed (the before and after)?

There's no info on how much reported free space you had before wiping and after.

What happens if you trim. May or may not help but try this from TWRP's terminal...

fstrim -v /data

Reboot and see what it looks like.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
[Galaxy S 4 i9505 Original Android Development] helmiazrin:
Problem flashing miui as primary rom

I'm having problem flashing miui as primary rom. I've attached screenshot of the flashing error. Hope someone can help me.

Thanks
[Galaxy S 4 i9505 Original Android Development] hxq88:
Guys, my primary is samsung touchwiz base on Oreo, device S7edge, and i installed AOSP 7.1 as in data slot as second rom. but i cant switch back primary rom after boot in to second rom got bootloop, and app sharing was not worked also.

My install step is: open app > set kernel and ramdisk for primary > reboot > install patched zip as second rom > boot to second rom, set kernel and ramdisk > return to primary and got bootlop ( idk why but manual flash boot image storage in data/dualboot not work, i only can restore primary rom via unmodify boot image from kernel zip :D)

Correct me which step i was wrong. Thanks anyway.

edit: i've just read a port rom ( my primary is a port) need edit built prop. My build prop edited to hero2lte (s7e) already.
[Galaxy S 4 i9505 Original Android Development] tulipon:
I determine it looking the info provided by two apps called diskusage and diskinfo, both report 23,4 G size data partition where used to be a 28 G partition.

I did what you suggest from recovery console:

fstrim -v /data

/data: 20331958272 bytes trimmed!

then rebooted but get bootloped the first time, the second time booted ok but those 4 and a half G are still missing.

Also tried formatting again the whole partition but no positive results.

Thank you for your advice, any other idea will be welcome.
[Galaxy S 4 i9505 Original Android Development] gaww:
My 935F partition is 24.65, but do not recall what it was before. Also, I think I recall that OREO changes partitions some, but don't know if you have updated to that at some point.
[Galaxy S 4 i9505 Original Android Development] gajju.m:
Can someone give me DualBootPatcherAndroid-9.2.0.r199.gcfbba1c6

This version's utility zip.

Thanks in advanced
[Galaxy S 4 i9505 Original Android Development] Eleo:
Here you go.
[Galaxy S 4 i9505 Original Android Development] gajju.m:
Magisk won't update it give error.

I attached screenshot.
[Galaxy S 4 i9505 Original Android Development] Eleo:
You canNOT flash patched magisk zip with DBP or recovery since magisk v12. It is nothing new. You need to edit script yourself or find an edited magisk zip and flash it. There were many such edited magisk zips shared in this thread. Why not search and find them? You can also find procedure with which you can edit magisk scripts if you want to do it yourself.

And next rime, attach multiboot.log (mentioned in your screenshot) as attachment. Your screenshot does not contain logs. Without logs no one can help you
[Galaxy S 4 i9505 Original Android Development] tomaasz:
I try for lost few months to use DualBoot with stock based Oreo roms on my S8 dreamlte. But not success. Is it possible for someone of you?

Wysłane z mojego SM-G950F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] edyny1:
How can i able to boot a rom that is installed in extsd-slot?

I have flashed different kernels but no luck booting it. It stays at splash screen and after a few moments it vibrates like 3 times then it goes to recovery...

My others rom i have installed in data-slot those boots ok but no luck with extsd-slot

S8+ G955F
[Galaxy S 4 i9505 Original Android Development] fishersfish:
You should see the logs or flash your patched magisk zip in recovery to see what happens.

:confused:Strange, Magisk_v16.4.zip patched by Dualboot Patcher v9.3.0.r527 works fine( works with data-slot-android 7 and android 8,no checking module ), but patched by the latest Dualboot Patcher doesn't(make all data-slot ROMs unbootable), it's inreasonable.

Magisk v14 patched by Dualboot Patcher worked for me all the time (no checking module) before I switched to Magisk v16

PS:

DualbootPatcher(ver 9.3.0.r593~9.3.0.r636 )'s settings crash on LOS 15, so you guys would better not try to install those versions on Android 8.x.

DualbootPatcher ver 9.3.0.r640~ works on Android 8.x now;
[Galaxy S 4 i9505 Original Android Development] pehoko:
[MENTION=4277844]chenxiaolong[/MENTION] can you do add phone as supported device as I created one DBP debug and seems working fine?
[Galaxy S 4 i9505 Original Android Development] gaww:
Do it the easy way - patch and flash 12 or 13.0 and then let the app update itself and then let it update magisk. Have done it dozens of times.
[Galaxy S 4 i9505 Original Android Development] 5ud0:
I see latest commits are related to support for oreo. Does Dualboot patcher support oreo roms now?
[Galaxy S 4 i9505 Original Android Development] tomaasz:
doesn't

I tried on my S8

---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------

doesn't

I tried on S8
[Galaxy S 4 i9505 Original Android Development] fishersfish:
Crash log of the latest DBP

It seems that the latest DBP running on Android 7 will be OK (Not tested).

Here is the log. View attachment crash.log
[Galaxy S 4 i9505 Original Android Development] marcdw:
That is correct. Latest (607?) works on my Nougat ROMs but not on Oreo.

Moto G5S Plus XT1806, FrankenROM Oreo, MultiROM, Tapatalk 4.9.5
[Galaxy S 4 i9505 Original Android Development] marcdw:
Anyone ever have a backup take forever?

I backed up a Nougat ROM and it was fairly quick. The second ROM, Oreo, has been going on a few hours now. Lost half my battery already. Ugh!

EDIT: Well, looks like I got screwed. Axon 7 is the phone running DBP. After the hours-long backup successfully finished, I wasn't able to do another backup. It failed. I then discover I can no longer write to my SD card. Went into three ROMs and checked. Nothing.

I wanted to delete the directory of the failed backup. I'm asked to select the sdcard but then told I didn't select one when I did. As I back out of the operation I'm asked if I still want to delete said directory. Of course it fails.

Went into TWRP and deleted the directory. Back in the ROMs, though, it's still there.

Flashed [MENTION=4544860]osm0sis[/MENTION]' sdcard permissions fix to no avail.

Now what? I had this problem ages ago on an old JB era Samsung but forgot how I fixed it (it's still in service).

Ugh. Just noticed that second backup was not successful despite what DBP said. The data.tar.lz4 file is 0 in size. It was that data backup that was taking hours.

Moto G5S Plus XT1806, MultiROM, Tapatalk 4.9.5
[Galaxy S 4 i9505 Original Android Development] osm0sis:
Sounds like you need to format data and boot up on stock firmware to get it to set everything up correctly again for you.
[Galaxy S 4 i9505 Original Android Development] marcdw:
Thanks, Sir [MENTION=4544860]osm0sis[/MENTION]. Yeah, I figured that but was hoping otherwise. Even my trusty Roehsoft Partition Toolkit couldn't help.

Thing is, I was in stock when I was doing the backups. I had plans to update the stock firmware and wanted to take precautions since the ROMs reside in /data.

Axon is a pain in the rear with bootstack this and bootstack that.

I've got extra flash drives and microSD cards (use via OTG adapter) so maybe I can still get the ROMs backed up.

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[Galaxy S 4 i9505 Original Android Development] zubair1836:
I'm using S4 GT-I9506, Running Magma NX VX1 as primary.

The Problem I'm facing is when I flash MIUI v8 in data slot and try to boot it: Phone goes to Download mode saying "Could not Do normal boot".

So, I tried flashing MIUI's kernel after flashing the ROM, It booted up but Wifi could not be turned on in MIUI (dala slot).

P.S. It's not ROM/ Kernel issue as I've tried this ROM & Kernel in primary slot: Everything works fine.

Any Suggestions what I'm missing here?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Is the patcher treble compatible, someone tried to run treble rom?
[Galaxy S 4 i9505 Original Android Development] Veselchak787:
remove thise massege. please.
[Galaxy S 4 i9505 Original Android Development] eccko:
Hi, when I try to install patched ROM, TWRP give me error: 7 (I want install Ressurection remix 6.0 or any other rom)

When I try install patched ROM from App again not work.

My codename device - ks01ltexx My phone - Galaxy S4 International GT-I9506

I currently using LineageOS 15.1 from kyasu.
[Galaxy S 4 i9505 Original Android Development] eccko:
How did you do that works for you on I9506?
[Galaxy S 4 i9505 Original Android Development] marcdw:
On my Axon 7 I have to remove the assert lines from the updater-script in each ROM. Maybe try that and see what happens.

Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3
[Galaxy S 4 i9505 Original Android Development] pehoko:
I can't install supersu

7.530972000+03:00][381:381][V] mbtool/installer: ROM ID: data-slot-v9
[2018-06-10T15:02:17.530999000+03:00][381:381][D] mbtool/installer: [Installer] Chroot set up stage
[2018-06-10T15:02:17.942272000+03:00][381:381][D] mbtool/switcher: Attempting to switch to data-slot-v9
[2018-06-10T15:02:17.942346000+03:00][381:381][D] mbtool/switcher: Force update checksums: 1
[2018-06-10T15:02:19.938432000+03:00][381:381][D] mbtool/switcher: Updating checksums file
[2018-06-10T15:02:19.948412000+03:00][381:381][V] mbtool/installer: Successfully switched to target ROM
[2018-06-10T15:02:19.948616000+03:00][381:381][V] mbtool/installer: Patching ramdisk to undo init modifications
[2018-06-10T15:02:19.949098000+03:00][381:381][D] mbtool/installer_util: Patching boot image
[2018-06-10T15:02:19.949135000+03:00][381:381][D] mbtool/installer_util: - Input: /dev/block/bootdevice/by-name/boot
[2018-06-10T15:02:19.949160000+03:00][381:381][D] mbtool/installer_util: - Output: /dev/block/bootdevice/by-name/boot
[2018-06-10T15:02:19.950337000+03:00][381:381][D] mbtool/installer_util: - Format: android
[2018-06-10T15:02:20.366714000+03:00][381:381][E] mbtool/installer_util: /dev/block/bootdevice/by-name/boot.aIZGud/ramdisk.out.QW6icC/device.json: Cannot extract through symlink /dev/block/bootdevice/by-name/boot.aIZGud/ramdisk.out.QW6icC/device.json
[2018-06-10T15:02:20.871757000+03:00][381:381][W] mbtool/installer: Failed to patch boot image. Continuing anyway...
[2018-06-10T15:02:20.878901000+03:00][381:381][D] mbtool/installer: [Installer] Filesystem mounting stage
[2018-06-10T15:02:20.880271000+03:00][381:381][D] mbtool/installer: [Installer] Installation stage

any suggestion?
[Galaxy S 4 i9505 Original Android Development] eccko:
I tried to install other systems like. LOS 13, LOS 14, RR 7.1.2 but it still does not work.
[Galaxy S 4 i9505 Original Android Development] pehoko:
What exactly this program do to boot.img's of installed roms? Thanks!
[Galaxy S 4 i9505 Original Android Development] KaMyKaSii:
Modify the startup scripts to load the system from different locations, thus enabling dualboot
[Galaxy S 4 i9505 Original Android Development] pehoko:
Yes this is well known, but what exactly, mbtol - exists in boot.img and other things... I need to "rape" some things but without mbtool modifications.
[Galaxy S 4 i9505 Original Android Development] yayakuya:
every time I try to patch ROM, it can't be choosed...

the zip always opened by file manager (not choosed)

any clue what happened?

-----edit-----

here's the screenshot of two zip files (ROM & Magisk)

both are zip in extension but look it up, the logo in the middle are different

and i can pick/ choose Magisk to patch but not the ROM (as i said, it opened... not choosed)
[Galaxy S 4 i9505 Original Android Development] yayakuya:
ok I've done it patched ROM by windows app

but again... when i start to flash it, i can't...

it's opened instead of choose... wth :confused:
[Galaxy S 4 i9505 Original Android Development] zubair1836:
It's not DBP (DualBoot Patcher) issue, It's your File Manager that's going wrong.

Try the Files.apk by Google. It works fine for me.
[Galaxy S 4 i9505 Original Android Development] yayakuya:
where i can find it?

I've tried two file manager downloaded from playstore but give me same result

using root explorer crashing the app
[Galaxy S 4 i9505 Original Android Development] zubair1836:
always mention your Android version when reporting an issue.

Especially when asking for an app.

Moreover, Just google: "Files.apk by google" and download the one for your android Version. Good Day :good:
[Galaxy S 4 i9505 Original Android Development] yayakuya:
sorry for it... using RR nougat on Nexus 6

just downloaded it, i think i have it already and it's updated

the files.apk i used is by Google btw
[Galaxy S 4 i9505 Original Android Development] zubair1836:
And you select This File manager when Choosing zip in DBP app?
[Galaxy S 4 i9505 Original Android Development] yayakuya:
it's selected by default when i click "add flashable zip"

so i try to freeze it and download another file manager apps... but no luck

-----edit-----

the files.apk by Google can only pick zip files that should be downloaded by phone

and the ROMs I've got are copied from my laptop... that's why the zip files i was mentioned on earlier post give the different types (middle logo)
[Galaxy S 4 i9505 Original Android Development] zubair1836:
Then You should go for TWRP.

i.e. Flash the patched zip using TWRP, It works fine.
[Galaxy S 4 i9505 Original Android Development] yayakuya:
so i just flash it without wipe anything?

the patched ROM will be flashed to be a secondary

am i right?
[Galaxy S 4 i9505 Original Android Development] zubair1836:
Yes, Read the Orginal Post. It is clearly mentioned.
[Galaxy S 4 i9505 Original Android Development] yayakuya:
thank you for your help and time

really appreciate it :good:

will try it ASAP and let you know
[Galaxy S 4 i9505 Original Android Development] sumitarora2:
You have to long click on zip file and then open button appear , just click on that button and it will work.
[Galaxy S 4 i9505 Original Android Development] yayakuya:
what the heck... it's working now :o

i thought that will be just opened like it was... I've done that before but not click that fcking OPEN text :silly:

anyway, thanks m8 :good:

-----edit-----

the way I flash with TWRP didn't work (using patched ROM by windows)

give me such errors
[Galaxy S 4 i9505 Original Android Development] yayakuya:
btw, my system space only 300+MB free

i think that's the reason why
[Galaxy S 4 i9505 Original Android Development] Eleo:
https://xdaforums.com/showthread.php?t=2447534&p=71294740
[Galaxy S 4 i9505 Original Android Development] h.m.k.:
I am trying to flash for multi-slot-1(cache) RR6.1.0 Rel2 Oreo from Buff99 and break with error "Warning: No file_contextsE3004". I9505, TWRP 3.2.1.0, primary ROM Machinex 4.3, DBP9.3.0.r716, Magisk16, build.prop OK. Where is problem?
[Galaxy S 4 i9505 Original Android Development] zubair1836:
Mentioned a hundred times, Oreo ROMs not supported.

Please search before posting an issue.

---------- Post added at 05:21 AM ---------- Previous post was at 05:17 AM ----------

Low space could be the reason. But the Attached error doesn't say so.

You have to open the updater-script from patched zip and remove the assert lines at the beginning (Probably first 2,3 lines which end at ; (a semicolon) ).

Then, Save it --> Flash.
[Galaxy S 4 i9505 Original Android Development] marcdw:
The No file_contexts thing can be ignored.

The build.prop doesn't really matter as device identification (when flashing ROM) is read from the updater-script (assert lines at the beginning).

On my Axon 7 I have to remove those.

As pointed out though, Oreo is not supported out of the box. I have Oreo secondary ROMs running which is made possible using kernels patched for DBP use.

Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3
[Galaxy S 4 i9505 Original Android Development] sudipta08sarkar:
Not working on tissot (mi a1).

Showing " could not determine the boot partition because this device code name tissot not recognized "
[Galaxy S 4 i9505 Original Android Development] Eleo:
Try searching the thread with "device not recognized" keyword
[Galaxy S 4 i9505 Original Android Development] sudipta08sarkar:
Already searched all the thread named "device not recognized" , and added "ro.patcher.device=codename ( that is tissot) " but not working, can you please help me for tissot device?
[Galaxy S 4 i9505 Original Android Development] HWDEV:
Supported Device Deleted

Huawei Y3 (2017) CRO-U00 Deleted from device list recently after release of 9.3.0.r711.g2959f931 Tue, 12 Jun 2018 22:25:19 -0400. Please add the device again.
[Galaxy S 4 i9505 Original Android Development] gaww:
Which kernels can be patched for DBP use with OREO ? Also, can it use dbt app?
[Galaxy S 4 i9505 Original Android Development] jungle35:
I get this error when trying to flash ANYTHING patched by the app

MultiBoot] - ailsa_ii

[MultiBoot] This device is 'axon7'

[2018-06-17T05:36:30.046052000-05:00][510:510][D] mbtool/installer: [Installer] Cleanup stage

[MultiBoot] Failed to flash zip file.

[MultiBoot] Destroying chroot environment

[2018-06-17T05:36:30.047595000-05:00][510:510][E] mbtool/installer: Failed to unmount /chroot/system: Invalid argument

[2018-06-17T05:36:30.047732000-05:00][510:510][E] mbtool/installer: Failed to unmount /chroot/cache: Invalid argument

[2018-06-17T05:36:30.047874000-05:00][510:510][E] mbtool/installer: Failed to unmount /chroot/data: Invalid argument

[2018-06-17T05:36:30.047955000-05:00][510:510][E] mbtool/installer: Failed to unmount /chroot/efs: Invalid argument

[2018-06-17T05:36:30.049661000-05:00][510:510][E] mbtool/installer: Failed to unmount /chroot/sbin: Invalid argument

[2018-06-17T05:36:30.069607000-05:00][510:510][E] mbtool/installer: /efs: path not mounted

Seems to be a simple name mismatch but how can I fix it?
[Galaxy S 4 i9505 Original Android Development] marcdw:
I think any kernel can be patched if one wants to. For my ZTE Axon 7 there is a user who has patched a few kernels from a few ROMs. Obviously just for that device.

Here's the post he referenced in getting Oreo kernels to work with DBP.

http://xdaforums.com/showthread.php?p=74373698

Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3
[Galaxy S 4 i9505 Original Android Development] mbr007:
Please add OnePlus 6. Thanks.
[Galaxy S 4 i9505 Original Android Development] matheusgcdj:
Add Moto Z2 Force XT1789 please.
[Galaxy S 4 i9505 Original Android Development] eccko:
Not working, I try to flash on RR v.6.0.0 and I get only error. I try flash LOS 14.1 on secondary.

Device - ks01ltexx

And when I try to flash DualBootutilities TWRP get Lagg and reboot to system.......
[Galaxy S 4 i9505 Original Android Development] Eleo:
That is normal. I believe you use latest TWRP. But latest TWRP does not support aroma installer, which is used by dualbootutilities.zip.

As I already told you, we use this app to multiboot 7 different ROMs in s4 (ks01lte). So there is no problem in app. Probably your setup is wrong. Since you didnt provide us enough data, I could only diagnose why dualbootutilities didnt work. For your other problems we need you to provide us enough info.
[Galaxy S 4 i9505 Original Android Development] eccko:
It's work (DualBootUtilies) with only 2.8.7.0 AND it's work. BUT there is no solution for me. When I use latest TWRP, I mean version 3.2.1.1 there I get lag and reboot to system. When I try flash on 2.8.7.0 My "patched" .zip TWRP give me error 1. When I try in .zip /multiboot/device.json in line "ks01lte" and change codename to "ks01ltexx" I get Error in TWRP. :rolleyes::rolleyes:

P.S I add to attachments SS.
[Galaxy S 4 i9505 Original Android Development] Eleo:
It does NOT lag. Latest TWRP just DOES.NOT.SUPPORT.AROMA INSTALLER.

That is it. If you want to use aroma installer, then you will need to flash twrp2.8.7.0.zip before each time you need aroma installer. And once you are done, flash twrp3.2.1.zip and continue flashing your other zips.

Pretty simple:eek:

Of course 2.8.7.0 does not work with latest rom.zips. And why do you need dualbootutilities? Just flash zips to correct slots and you are done

:eek:

Thausands of s4 users use this app every day.
[Galaxy S 4 i9505 Original Android Development] eccko:
I can't flash any patched zip. :eek: See my SS higher.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Where you attached multiboot.log after unsuccessful flash? We cant diagnose a screenshot. Attach multiboot.log from root of your internal memory after unsuccessful flash. Read:

https://xdaforums.com/showthread.php?t=2447534&p=76129604

And also provide info about what slot you patched zips? And many many more. We need info to diagnose. It is not simple as you think.

You just need to rename your build.prop from ks01ltexx to ks01lte (or just remove device restriction from zip that you flash). That is what the zip is programmed to understand.
[Galaxy S 4 i9505 Original Android Development] eccko:
I try to flash "patched" zip as secondary.

I do rename in build.prop from ks01ltexx to ks01lte.

Sorry for my english. :(

EDIT: After change in build.prop I get the same error in TWRP ( Error - 1, SS higher)