yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The only log I can see is the one for flashing aoscp_h811-3.1.3-20161129-weekly_extsd-slot-test.zip. This is the one that hung at "patching system unconditionally". It looks like it ran out of space:

write failed: No space left on device

but the ROM's installer didn't fail and just kept trying again and again. (It made the log file > 600MB after extracting the tar.gz file!)

Can you try repatching the file with version 9.1.0.r42.g802803a and flashing from recovery? Be sure to choose "LG G4 (T-Mobile)" when patching, not "LG G4". Please attach the logs if it continues to fail. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just flash the GetLogs zip from https://dbp.noobdev.io/downloads/ and send me the tarball it creates in /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is cause by a security feature in the TouchWiz kernel and might not be fixable.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Same with me. I have try 3 different sd card with different capacity. After install the rom its goes with sd card corrupt need to be fix. Verry annoying to have such issues. I thought i can try save space by extsd method but have to go back dataslot to have stable usage. Any good idea to solve this issues? Really want to try with TW with at least 5rom in extsd since i have extra card on hand.
[Galaxy S 4 i9505 Original Android Development] welder73:
I've tried at least 10 versions of Dual Boot Patcher,t he newest,some test builds but ONLY 9.0.0.r64.ge3c4da6-SNAPSHOT works fine on my Lg G4 (H815).

I mean,i can patch zips with any of them but only with this one I can flash the roms...
[Galaxy S 4 i9505 Original Android Development] pehoko:
I was trying to patch MIUI rom official for my phone.
[Galaxy S 4 i9505 Original Android Development] dikime:
Hey, just a quick check-in (no logs provided, very sorry about that):

Sometimes when I switch from primary to multi-slot-1, a random app is uninstalled from multi-slot-1 ROM. It's always 1 app, install time doesn't matter, and I'm not sharing any data/apps between the two ROMs. Switching from multi-slot-1 to primary doesn't cause this ever. I'm not running any other ROMs to verify if other slots (/system, /data, /extSD cause this).

It's not a big problem since I use Titanium Backup, but I'm just posting in case someone else noticed or has a fix.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
[MENTION=4277844]chenxiaolong[/MENTION]

Thank you this worked. Having a problem though. Stock Android 7.0 was just released for t mobile h830 and it seems it won't dual boot. I patch the rom zip and supersu to flash as a secondary rom (data slot) as I did with stock 6.0.1. After flashing I reboot and when it reboots it either loops on message that device can't be checked (unlocked bootloader message) or it loops at the boot animation (but instead of lg boot animation that it should be with stock rom it's RR (primary rom) boot logo. I booted back to twrp and flashes get logs and attached them in post. Also people on stock 7.0 are saying that when they run app it states mbtool failed to start. I asked them to run get logs to upload as I believe it may be due to bootloader changing from 6.0.1 to 7.0, not sure though. Anyways thanks for your work.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I just have a chance to test 9.1 on my s4, but unfortunately all builds failed to update mbtool on my S4. Also they failed to change backup folder (not sure if these two things are related).

9.0 works fine.

Update: It seems it's rom-related. Now I have two roms on this S4, all versions are working well on one rom. The one that 9.1 doesn't work is WickedX v11.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Lol man, this is a version released a month ago. Yesterday I tried the 9.1.0.r38 and it was working fine on me.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
9.0 is quite stable for restore and backup section. No problem on freezing or stucking issues on it.
[Galaxy S 4 i9505 Original Android Development] Jimm85:
Hello can you tell me why you may write an error when installing the firmware on from versions 9.1.0 to 9.1.0r43 : failed to symlink:/proc / self/fd 54 or 53 or 50 or 52 depends on what firmware sees. The device Xiaomi Redmi 3 Pro (ido).Sorry for my English.
[Galaxy S 4 i9505 Original Android Development] welder73:
I know man,but that's the only version working fine for me... :confused:
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Try to flash in recovery, also provide a log.
[Galaxy S 4 i9505 Original Android Development] Jimm85:
Through rekavery sew through program no. Log mbtool?
[Galaxy S 4 i9505 Original Android Development] draymond1987:
Deleted

---------- Post added at 03:01 PM ---------- Previous post was at 02:32 PM ----------

Sorry for deleting my last comment. I wanted to make sure I flashed the zip, correctly. I formatted both internal and external, last night. I used R42 and R43, but now I can't flash on the /data partition either. I used the same ROM as primary, from when I couldn't flash to ext, but could on /data. I just set the kernel and didn't update the ramdisk before I flashed a secondary ROM. Thanks for your help!

https://drive.google.com/open?id=0BztXnxaH5yHhaGpERzMyWVNOZzA
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
Here you go I attached it
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I'm trying to port Nougat 7.1 to K6000 Pro and I'm using the patcher for debugging (yes it's a ton useful) :)

I repacked the boot.img and replaced the kernel with my stock kernel, also fstab replaced. Unfortunately it's not booting, but the good sign is that it vibrates 5 times and goes to recovery, so there is a sign of life! Looking at the last_kmsg log there is a Selux policy issue.

[ 10.833046] <5>.(5)[1:init]SELinux: avtab: invalid type or class
[ 10.839170] <5>.(5)[1:init]mblog: /sys/fs/selinux/load: Failed to write sepolicy: Invalid argument
[ 10.840511] <5>.(5)[1:init]mblog: /sys/fs/selinux/load: Failed to write SELinux policy
[ 10.877410] <5>.(5)[1:init]mblog: /raw/images/extsd-slot-sd1: Failed to mount: : No such device
[ 10.878500] <5>.(5)[1:init]mblog: Failed to mount image for extsd-slot-sd1
[ 10.879775] <5>.(5)[1:init]mblog: /raw/images/extsd-slot-sd2: Failed to mount: : No such device
[ 10.880864] <5>.(5)[1:init]mblog: Failed to mount image for extsd-slot-sd2
[ 10.881738] <5>.(5)[1:init]mblog: Skipping external SD binaries wrapping
[ 10.882648] <5>.(5)[1:init]mblog: JSON error on line -1: unable to open /raw/data/media/0/MultiBoot/data-slot-data5/config.json: No such file or directory
[ 10.884372] <5>.(5)[1:init]mblog: /raw/data/media/0/MultiBoot/data-slot-data5/config.json: Failed to load config for ROM data-slot-data5
[ 10.885938] <5>.(5)[1:init]mblog: Enable appsync: 0
[ 10.890326] <5>.(5)[1:init]mblog: Running executable: /sbin/file-contexts-tool
[ 10.896109] <1>.(1)[219:file-contexts-t]random: file-contexts-t urandom read with 20 bits of entropy available
[ 10.928140] <0>.(0)[1:init]mblog: /file_contexts.bin: Failed to decompile file_contexts
[ 10.937254] <0>.(0)[1:init]mblog: /data/.layout_version: Failed to set SELinux context: Operation not supported on transport endpoint
[ 10.939078] <0>.(0)[1:init]mblog: Not mounting empty tmpfs over: /data/security/spota
[ 10.962734] <0>.(0)[1:init]mblog: Policy version: 30
[ 10.963414] <0>.(0)[1:init]mblog: /data/media/0: Malformed context string: unlabeled
[ 10.964378] <0>.(0)[1:init]mblog: /sepolicy: Failed to apply policy patch
[ 10.974467] <0>.(0)[1:init]mblog: Failed to patch /sepolicy

I'll be thankful for any help here.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Those looks like SELinux denials, may be this link will help.

https://source.android.com/security/selinux/validate.html
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=4277844]chenxiaolong[/MENTION], I downloaded the test build 9.1.0.r40, it installed properly and set kernel for primary. I was able to patch a rom for data and for ext sd slots, patch and Install of patched roms appeared to work with no problems. I could not boot into either slot, phone always booted back to primary rom. I updated ramdisk and got 5 vibrations and rebooted to recovery. I have attached all of the logs I could find. Thanks for your time.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Chenxiaolong:

The RestoreBackup.zip I already open it and just want to confirm if the details I enter is correct for the zip flashable?

Pls have a look if you are free time. I wonder if I have wrong detail on it. Thx.
[Galaxy S 4 i9505 Original Android Development] Ralf_AM:
Confused about How To Use

Hello,

at the first post of this thread there is an explanation how to use the patcher but some things i don't understand.

1.)

Can anyone tell me where to get the "DualBootPatcher.exe" because at the download site of the patcher i only find

- the patcher *.apk and a "DualBootUtilities.zip" but no Winodws *.exe file

2.)

Ok, but how can i patch a rom for "primary" if the primary rom is already installed on my smartphone ?

a) should i copy the primary rom *.zip file to my smartphone, download & install the "Dual Boot Patcher app", patch that rom *.zip file as primary and then flash the patched file with TWRP over my alreday installed rom (which is the same rom as the one i have to patch) ?

b) how can i patch the primary rom if i have no rom installed on my phone (only TWRP is still on the phone after i deleted Cache/Data/System/Internal Card partitions with TWRP to get a completely clean phone before installing the 2 roms for dualboot) - because i can't find the "DualBootPatcher.exe" for Windows (GUI) to patch the rom first on windows and then transferring it with 'adp push' to the internal sd card of the phone (or installing it with 'adb sideload')

3.)

Must i install "DualBootUtilities zip" on the phone or should i do that only if

(Is this the only purpose of that file ?)

4.)

Can i delete/uninstall the secondary installed rom of a dualboot and how can i do that ?

5.)

Should the patched 2 roms, the SuperSU and GAPPS be installed in a special sequence or doesn't that matter ?

Hopefully anyone can help me :confused:

My phone is a LeTV Le Max 2 (x820) and i want to dualboot the Bshuy2003 and Mokee roms.

Greetings from Germany

Ralf
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Thanks, I'll look into it.
[Galaxy S 4 i9505 Original Android Development] TaiNguyen142:
Support samsung docomo J sc-02F(JS01LTE)

Hello, how to add my device to be supported?

My device is js01lte (SC-02F), I have to use the Note3 hlte to dualboot. This problem only temporarily, so I try to be supported on dualboot app. Please tell me how to add my device? thank you.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Read here:
[Galaxy S 4 i9505 Original Android Development] rifle007:
[MENTION=4277844]chenxiaolong[/MENTION] i have problem with build started from r42 , flash rom with patched zip from build r42 always failed same with r43 . But tried to patched zip from build r40 i can flash with success. Here the logs
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Would you mind to keep the app sharing codes in the code tree? And just disable displaying the related menu, to be able to enable later easily.

Just in case anybody wants to compile to still use it personally. Like me :)
[Galaxy S 4 i9505 Original Android Development] monkteo:
Maybe it's not a bad idea (personal I use it for WhatsApp, Tapatalk, Telegram, and another 1 or 2 and it's OK)

THX
[Galaxy S 4 i9505 Original Android Development] v00d007:
I got a problem with a rom.zip that I patched for secondary some time ago, of which I don't have the original file anymore and it's also not available online anymore. So I tried to repatch it for use as primary but unfortunately the produced zip is always broken. So isn't there any other way to get the original zip state back again? The zip was originally patched with patcher v8.00.1777 and I tried 1777 and others up to the latest , but no success.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION]: could you check this issue?

Resurrection Remix v5.8.0 (CM14) flashing error #323.

Logs are attached:

https://github.com/chenxiaolong/DualBootPatcher/issues/323
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
Okay so you can disregard about dual boot not working on stock 7.0, as the people reporting this issue were not doing things right, sorry about that. I upgraded to stock 7.0 and have run dual boot without any issues other than the 1st part of my earlier post. Some reason I can not run stock as secondary. Every time I try cm as primary and stock as secondary it will just hang as cm logo forever, even though I'm booting the lg stock rom...
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hi, update the ramdisk for all roms. It should boot to any slot no problem after doing that.

---------- Post added at 22:43 ---------- Previous post was at 22:39 ----------

Sorry no way to revert to the original zip, we'll need some kind of magic to bring it back. Patching twice with whatever version you choose will always lead to failure.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Is it somewhat normal that if I switch Roms, from like let's say cm 13 to a tw rom, that it might stick on boot animation and having to battery pull and reboot? That's what happened...I switched from temsaskek to aryamod and I had to battery pull. It rebooted normally after that. Thanks.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Omg. Lol.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This is not at all related to DualBootPatcher, but I know several people here are using an international S7 Edge (SM-G935F) on T-Mobile. Well, I just got WiFi calling, VoLTE, RCS, and LTE video calling working on the latest Nougat firmware. Stay tuned for more details!

Screenshots:

OS version:

WiFi calling enabled:

Video calling welcome screen:

VoLTE and WiFi calling settings:

Ongoing WiFi call (notice green WiFi calling icon):

Completed first successful WiFi call:

Ongoing call with VoLTE (notice 4G LTE icon in status bar):

Ongoing video call over WiFi calling:

RCS messaging (notice "read" status):

(Pinging [MENTION=3019752]gaww[/MENTION])
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
I was able to flash boot image before ramdisk update to get back into my primary rom.[/QUOTE]

Can I know how do you do to flash the boot image get back your primary rom? I would like to know since I facing issues similar with you sometimes. And how is the capacity for the boot image?

---------- Post added at 04:47 AM ---------- Previous post was at 04:44 AM ----------

This is often I faced when I switch between tw Rom. But nothing on affect to my rom system and it's works like charm.set kernel update ramdisk as well as.so we might just go with it.
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Can I know how do you do to flash the boot image get back your primary rom? I would like to know since I facing issues similar with you sometimes. And how is the capacity for the boot image?

Look in folder /multiboot/primary using twrp flash image, flash either boot.img or boot.img.before-ramdisk-update.img
[Galaxy S 4 i9505 Original Android Development] Steven1962:
Hi, can the patcher work with 128 gb sd card or is it a known issue? The patcher doesn't see any backups on the card. The path is also strange: if I choose sdcard1 I get mnt/media-rw/3360-3460... I am on note3 n9005. Thanks in advance
[Galaxy S 4 i9505 Original Android Development] andyfmking:
Thank you for the assistance. The code worked once. But after a week, it went back to its previous behavior. Running the code again then restarting has no effect anymore.

I was dualbooting with OOS 2.2 (Oxygen OS Marshmallow) for the OnePlus three. I have wiped the second ROM (OOS) and tried the code again but still no effect.

The current Resurrection Remix ROM (Marshmallow) is set as primary with SELinux enabled and ElementalX kernel which came by default with it without any tweaks. I'm running Xposed too with systemless root .

Any other idea for a fix?

Edit: I'm also using Magisk V6. Could that be the cause of that unexpected behavior?

Edit 2: Found the culprit. Looks like Magisk doesn't play nice with this. I forgot I had Magisk, when I came to remember it then I remembered it created links to paths in the storage that might conflict with this dualboot as they both seemed to created their own paths.

Sorry for the inconvenience. I wish I remembered this earlier. Now everything is working as expected.
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
OnePlus 3 Nougat RR as secondary

When i try to install Resurrection Remix N as secondary Rom or in Data Slot i become this error can anbody help me?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Still would like to know if me seeing that sha checksum error will have any ill affects? I read in this thread that its happened to others. Thanks.
[Galaxy S 4 i9505 Original Android Development] kopitalk:
No ill effect but make sure you set kernel after booting into that rom and the error will disappear for good.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
What about when I had to battery pull when I switched to the tw ROM?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Strange, I have never encountered that before. To me whether switching using the app or utility zip, the reboot after that is always without a glitch.

My setup now,

primary - CM14.1 by christer12

data-slot-1 - AryaMod N7 v2.1 (TW 6.0.1) with ShinTo L22A05 kernel

data-slot-2 - MagMa NX TU (TW 6.0.1) with DarkLord N7 v1.1 kernel
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Set kernel worked. Thanks. Do you have a T-Mobile note 3 by chance?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Nope, international hlte N9005 here.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
I was looking at ROMs ur running. These can be flashed to tmo note 3 right?
[Galaxy S 4 i9505 Original Android Development] kopitalk:
For tmo? I don't know, man :laugh: Better check with respective threads.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
edit the updater-script deleting this line

abort("E1001: Failed to update system image.");

Installation in recovery recommended. Also install in data slot not in secondary.
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
where Can i find the "updater-script"??
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Open the rom zip. It's located in META-INF\com\google\android
[Galaxy S 4 i9505 Original Android Development] pehoko:
I still can't install MIUI as secondary rom with any dualbootpatcher version, anyone have success?
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
How can I change backup directory ?

When I always want to restore my backup it's always need to be in the multiboot internal storage. Can I change it directory to SD card?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Sure, check the settings, the option is there. :p
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Sorry have to say try patch it in data slot not secondary.

---------- Post added at 04:41 PM ---------- Previous post was at 04:32 PM ----------

Whem flashing the boot image in twrp there are written on flash in 2 option:

Boot

Recovery

Which 1 is needed?

And the boot image only 9mb?
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
thank you but doesn't work stuck in the OnePlus bootlogo
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Use option "Boot" for boot image, Recovery is for twrp image and the like.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Did you flashed in recovery?
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
yes and as Data slot
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Oh, there is a problem then. :( Grab a log please.
[Galaxy S 4 i9505 Original Android Development] add_pl:
I have same problem

My log.
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
this Log File? this time i tried it with cm14.1 but same result do you have WhatsApp or so? and thanks for the help
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No, download the GetLogs-20161128-1.zip from https://dbp.noobdev.io/downloads/, flash the zip in recovery and attach the tar.gz file it created in /sdcard/logs
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
here
[Galaxy S 4 i9505 Original Android Development] pehoko:
I mean other ROM, not slot position. I have tried every type of slots, no difference.
[Galaxy S 4 i9505 Original Android Development] gc_geforce:
[MENTION=4277844]chenxiaolong[/MENTION],

Everything is working great with my G900W8 S5 and the CM13 as a EXTSD slot, the one thing I need to do is update superSU zip and flash it systemless. Is this supported with the "Patcher"? that I just have to patch the .zip files and then flash it that it will work?

Thanks
[Galaxy S 4 i9505 Original Android Development] Eleo:
I have done flashing patched supersu on data slot-1 and it worked. If that helps you
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Once again had a freeze on reboot. Another battery pull. Ugh. After pull, it booted.
[Galaxy S 4 i9505 Original Android Development] Mike0505:
[MENTION=4277844]chenxiaolong[/MENTION]

Realy sorry for report that, because today realized with version https://github.com/chenxiaolong/DualBootPatcher/pull/309 - 9.0.0.r163.g3956d6c installing non miui rom works

and with newest versions installing non miui roms not working.

It's my error because when was testing new versions I only tested miui roms which was not working with that version. :crying:

So seems to me when is installing miui roms achieved then was installing non miui roms broken. :confused:

Logs with version 9.1.0.r43 when installing miui working and non miui rom not working attached

and also atached multiboot log with version 9.0.0.r163 when installing non miui roms working
[Galaxy S 4 i9505 Original Android Development] corsicanu:
[MENTION=4277844]chenxiaolong[/MENTION] having some problems with backup and restore on latest (r43) version.. My backups are on external sd, and since you changed external sd in app to /mnt/media_rw/path doesn`t see anymore the backups. It simply says "No backup found".. Being on data-slot- trying to restore backup from internal it says "read only system" on /raw/system and fails. Also tried to give root access to mount by itself as rw everything with no luck, being on data slot like i said.. Also 2 - being on primary with latest build (r43) can`t see backups on external. Reverted to r18 and it mounts sd without media_rw path and it sees all the backups and can be restored to any slot (restored successfully to data slot), but from data slot with r18 can`t see the backup..Tell me what logs or things to provide, cause i need this :D. A5 2015 - stock TW-MM. Cheers!
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

no idea on this?

http://xdaforums.com/showthread.php?p=69940254
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Broken how? It won`t flash or it flashes but doesn`t boot? If it flashes and won`t boot - download and flash kernel after flashing the rom. If it won`t flash, investigate the error. My personal guess would be the broken symlinks in updater script. Upload the zip and send me the link via pm and i`ll try to help. Cheers!

LE: Did you tried to flash it as slot, backup, and restore to primary?
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Why sometimes it's happen executing error when flashing primary zip files? For data slot it might be no issues at all .