yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] GigilinE:
Hi, when i want patch ramdisk i have this error

INFO DEVICE:

PORT NOTE 8 7.1.1 FOR S7 EDGE

BUILD.PROP S7 EDGE

10-24 11:09:48.139 30447 30447 D ViewRootImpl@ba31103[RomDetailActivity]: ViewPostImeInputStage processPointer 0
10-24 11:09:48.141 30447 30447 D ViewRootImpl@6a3980b[Toast]: dispatchDetachedFromWindow
10-24 11:09:48.143 30447 30447 D InputTransport: Input channel destroyed: fd=79
10-24 11:09:48.143 30447 30447 W SemDesktopModeManager: unregisterListener: Listener is null
10-24 11:09:48.248 30447 30447 D ViewRootImpl@ba31103[RomDetailActivity]: ViewPostImeInputStage processPointer 1
10-24 11:09:48.834 30447 30447 D ViewRootImpl@ba31103[RomDetailActivity]: ViewPostImeInputStage processPointer 0
10-24 11:09:48.910 30447 30447 D ViewRootImpl@ba31103[RomDetailActivity]: ViewPostImeInputStage processPointer 1
10-24 11:09:48.915 30447 30447 D SwitcherService: Added runnable com.github.chenxiaolong.dualbootpatcher.switcher.service.CreateRamdiskUpdaterTask@3904d73 to thread pool: default
10-24 11:09:48.947 30447 30614 D CreateRamdiskUpdaterTask: Creating ramdisk updater zip for primary (version: 9.3.0.r79.gaa381cdb-SNAPSHOT)
10-24 11:09:48.958 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: ThreadedRenderer.create() translucent=true
10-24 11:09:48.961 30447 30447 D InputTransport: Input channel constructed: fd=82
10-24 11:09:48.961 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: setView = DecorView@25d0960[RomDetailActivity] touchMode=true
10-24 11:09:48.962 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: dispatchAttachedToWindow
10-24 11:09:48.981 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: Relayout returned: oldFrame=[0,0][0,0] newFrame=[37,1098][1403,1546] result=0x27 surface={isValid=true 504481906688} surfaceGenerationChanged=true
10-24 11:09:48.981 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: mHardwareRenderer.initialize() mSurface={isValid=true 504481906688} hwInitialized=true
10-24 11:09:48.984 30447 30470 D mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [1590x672]-format:1
10-24 11:09:48.990 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: MSG_WINDOW_FOCUS_CHANGED 1
10-24 11:09:48.990 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: mHardwareRenderer.initializeIfNeeded()#2 mSurface={isValid=true 504481906688}
10-24 11:09:48.990 30447 30447 I InputMethodManager: startInputInner - mService.startInputOrWindowGainedFocus
10-24 11:09:48.991 30447 30447 D InputTransport: Input channel constructed: fd=88
10-24 11:09:48.991 30447 30447 D InputTransport: Input channel destroyed: fd=78
10-24 11:09:49.003 30447 30447 D ViewRootImpl@9277963[RomDetailActivity]: MSG_RESIZED_REPORT: frame=Rect(37, 1098 - 1403, 1546) ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
10-24 11:09:49.031 30447 30447 D ViewRootImpl@ba31103[RomDetailActivity]: MSG_WINDOW_FOCUS_CHANGED 0
[Galaxy S 4 i9505 Original Android Development] MaheshTechnicals:
When I try to flash Gapps for secondary Rom it says Error. How to flash Gapps plz Guide me
[Galaxy S 4 i9505 Original Android Development] Ryan1469:
Ok. But do you have any idea why i am getting the error as shown in pic whenever trying to flash a rom patched in dataslot.. ie system, data, cache image file is false.
[Galaxy S 4 i9505 Original Android Development] mbr007:
Backup is not working for tmobile.
[Galaxy S 4 i9505 Original Android Development] monkteo:
what is the error (what happen)
[Galaxy S 4 i9505 Original Android Development] monkteo:
try change the location were you save the backup (from dualboot-seting)

and update the ramdisk
[Galaxy S 4 i9505 Original Android Development] blixer:
That's no error!!! It only shows that your rom isn't installed to system but data.

Everything is fine!!! You can reboot now to dataslot or primary... whatever you want :cowboy:
[Galaxy S 4 i9505 Original Android Development] blixer:
Open the "Multiboot" folder in your storage. Can you see a folder "backups" there? If not create this folder and you will be able to backup all your roms.

Had the same 'problem' months ago.

Good luck!
[Galaxy S 4 i9505 Original Android Development] blixer:
double post :p

can someone delete it? Thanks in advance
[Galaxy S 4 i9505 Original Android Development] mbr007:
Thanks. It's working now.
[Galaxy S 4 i9505 Original Android Development] idank555:
hey, i'm using lenovo vibe p1 with stock mm for primary rom.

but, when i flash any rom to data slot for secondary rom, i cant get root to work.

i've already try flash patched BETA-SuperSU-v2.72-20160510112018 for secondary rom but didn't work.

can you help me?

sorry for my bad english
[Galaxy S 4 i9505 Original Android Development] Fiko92:
Hey, I have a problem.

I'm using an SM-N9005 (Note3 international) and my primary rom is RR 5.8.4 and an working secondary Rom on Data1 is parandoid Android Android Version 5.1 i can change the Roms without problems. So now i want to install a stock odex Rom without Root in data 2.

I can install the Rom with in app flashing without problems but I cant Boot into the Rom and if I try to install the same Rom with twrp it didnt work i got this error

mbtool/rom_installer: Failed to bind mount /raw/cache/multiboot/data-slot-0/cache to /chroot/mb/bind.cache [\hide]
[Galaxy S 4 i9505 Original Android Development] echo246:
Hi,

I recently dual booted my stock Samsung s6 g920f nougat 7.0 ROM with the 7.1.2 resurrection remix ROM. However, while I can pass the safety net with magisk on the first ROM, I fail the test on my 2nd RR ROM. Please help me as I can't seem to solve the issue and I need to be able to pass safety net in order to use apps like Snapchat :)

Thanks for any suggestions :)
[Galaxy S 4 i9505 Original Android Development] BruteHydra264:
Is there anyway to change a romantic that is in data-slot and move it to primary without wiping apps and storage?
[Galaxy S 4 i9505 Original Android Development] manish11165:
Can you make your boot ui like grub4android instead of twrp like boot ui please.
[Galaxy S 4 i9505 Original Android Development] gaww:
I have used these and others with aroma with no difficulties
[Galaxy S 4 i9505 Original Android Development] Ryan1469:
Can you tell what version of dual patcher you are using and what roms you are using. Ta

---------- Post added at 06:21 AM ---------- Previous post was at 06:19 AM ----------

Still not working for me. When i try to boot to secondary rom from dual patcher app , it says cannot switch rom.
[Galaxy S 4 i9505 Original Android Development] FrankySahertian:
First of all Thank you chenxiaolong for this Great App. Bean using it for a while. Help me alot to choose different roms. ?. But i've a request could you fix DBP UI for xiaomi MI5? It can be install.. It's there when booting up but i can't access it.. Can't touch anything.. so i couldn't change rom from booting. Two MI5 user also confirm that the ui doesn't work. Could you please fix it? That will be great ?
[Galaxy S 4 i9505 Original Android Development] Milano_:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks for the Amazing contribution.

As a S7 edge user with Note 7 Port rom, I'm getting the following error: "Could not Determine the boot partition because this device's codename 'gracelte" is not recognized".

any suggestions how to solve this?

thanks
[Galaxy S 4 i9505 Original Android Development] monkteo:
post #12561
[Galaxy S 4 i9505 Original Android Development] smjhh:
any new for flashing oero as secondary rom ?
[Galaxy S 4 i9505 Original Android Development] edyny1:
What is the reason "safetynet fails" with Magisk Manager on data-slot rom?
[Galaxy S 4 i9505 Original Android Development] staurosthess:
Data slot super su
[Galaxy S 4 i9505 Original Android Development] gaww:
Safetynet fails on all other ROMs then primary ROM with Magisk.
[Galaxy S 4 i9505 Original Android Development] se@wind:
Can someone please help me? I have tried both an Honor 8 and Honor 6x with Dual Boot Patcher now and they both fail when trying to install the patched zip, I have tried secondary, multi slot, data slot, and extsd slot. I have also tried flashing in TWRP and it has failed as well. The log/pictures below are from an Honor 8 FRD-L04C567B388 unlocked/rooted with primary rom EMUI 5.0.1 Android 7.0, latest twrp-3.1.1-1-frd and SuperSU-v2.82-201705271822. OpenKirin's RROS v5.8.4 For Honor 8 is what I have been trying to dual boot, it works fine if I don't patch it and flash it as the primary. I have also tried to dual boot OpenKirin's LineageOS 14.1 for Honor 8, I don't have the log but I believe I had the same problem.

The errors that show in Dual Boot Patcher app during flash are:

Warning: No file_contextsTarget: 1498674457

E1001: Failed to update system image.

[MultiBoot] Failed to run real update-binary

[MultiBoot] Failed to flash zip file.

My photos aren't showing up and I can't add my MultiBoot.log , I think it's because I don't have 10 posts

Would really appreciate some help, I have bought 2 phones just to try to get Dual Boot Patcher to work and have had no luck......
[Galaxy S 4 i9505 Original Android Development] BJumperBR:
Hi, I'm having problems trying to install Magisk v14 on my Redmi 4 Prime (RR ROM).

Error message:

************************

* Magisk v14.0 Installer

************************

- Mounting /system, /vendor, /cache, /data

- Device platform: arm64

- Constructing environment

- Found Boot Image: /dev/block/mmcblk0p21

- Unpacking boot image

MagiskBoot v14.0(1400) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/mmcblk0p21]

KERNEL [11499690] @ 0x80008000

RAMDISK [3643772] @ 0x81000000

SECOND [0] @ 0x80f00000

DTB [0] @ 0x80000100

PAGESIZE [2048]

NAME []

CMDLINE [androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci earlycon=msm_hsl_uart,0x78af000 androidboot.selinux=permissive buildvariant=userdebug]

COMPRESSION [gzip]

Decompressing to [ramdisk.cpio]

- Checking ramdisk status

MagiskBoot v14.0(1400) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

! Boot image patched by other programs!

! Please restore stock boot image

- Unmounting partitions

Updater process ended with ERROR: 1

I was able to install Magisk v12 successfully.

Any hints?
[Galaxy S 4 i9505 Original Android Development] DodoGTA:
Magisk no longer supports SuperSU

Note: Welcome, 1280x720 (HD)! :D
[Galaxy S 4 i9505 Original Android Development] FrankySahertian:
You must edit updater-script that's in the custom rom-installation zip file (all base cm or aosp rom). To do that

Use any file manager that can see through inside that zip file.. I'm using total commander app.

1. Go to folder META-INF/com/google/android/

2. And extract that file updater-script (make a backup of this file incase it didnt work on your device, I'm using mi5 and it work)

3. Now edit that file. Inside that updater-script, delete first line from word assert to ; (before next assert word), safe it and push and overwrite the original updater-script

4. Run again dualboot patcher, do patch and flash it.

Hope it work

If you still confuse on step 3..please share ss on inside updater-script scrip here.
[Galaxy S 4 i9505 Original Android Development] se@wind:
There is not 2 assert words in that script, only 1 at the beginning. If I delete the word assert to the first semicolon ; I would be deleting this:

assert(getprop("ro.product.device") == "hi3650" || getprop("ro.build.product") == "hi3650" || getprop("ro.product.device") == "frd" || getprop("ro.build.product") == "frd" || getprop("ro.product.device") == "FRD" || getprop("ro.build.product") == "FRD" || getprop("ro.product.device") == "FRD-L02" || getprop("ro.build.product") == "FRD-L02" || getprop("ro.product.device") == "FRD-L04" || getprop("ro.build.product") == "FRD-L04" || getprop("ro.product.device") == "FRD-L09" || getprop("ro.build.product") == "FRD-L09" || getprop("ro.product.device") == "FRD-L14" || getprop("ro.build.product") == "FRD-L14" || getprop("ro.product.device") == "FRD-L19" || getprop("ro.build.product") == "FRD-L19" || abort("E3004: This package is for device: hi3650,frd,FRD,FRD-L02,FRD-L04,FRD-L09,FRD-L14,FRD-L19;

Is that correct? I still can't upload files on XDA so I'm going to pm you the updater-script.

Thanks for the help!
[Galaxy S 4 i9505 Original Android Development] FrankySahertian:
Please see your PM.. I really hope it works.. Don't do it if you're not sure of it cause its a bit different in MI5.. I'm not force you to do it. ?. Please do backup everything that important in your phone before it. Do with your own risk.
[Galaxy S 4 i9505 Original Android Development] borgmanjayce:
I definitely want to try this out, but at the same time I was wondering if EchoeROM is supported by this app or not.
[Galaxy S 4 i9505 Original Android Development] chickentuna:
If you install echoe as primary there shouldn't be any issues. You just need to find a compatible secondary rom but if you're gonna use echoe as primary, chen would need to make it compatible with the patcher
[Galaxy S 4 i9505 Original Android Development] Bejda:
Not at the moment but support is only needed for rom you want to install as secondary or multiboot.

If you're on Echoe rom right now you can just keep it,no need to re-install or wipe anything,you just install secondary or multiboot rom on top.

While on Echoe you just Install dual-boot switcher app and set current kernel as primary rom. Once done you patch any supported rom you want and flash it (just to say the basic starting point, follow op for the whole detailed process).
[Galaxy S 4 i9505 Original Android Development] borgmanjayce:
I might give it a go as EchoeROM keeps being flaky at times lately and I don't want to have to keep on wiping and reinstalling it all the time when I could be installing a secondary ROM such as Paranoid Android or Foxhound instead and using that in case of any problems with EchoeROM as my main ROM.
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
help...

I think I cannot go back to my primary ROM.

I did all the step.

Is there a way to recover my TW primary ROM?

I really don't want to reinstall the ROM.

Since I will lose my data.
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
If you install the rom again without wiping, you won't lose any of your data. Or you could just install a different kernel to boot back, just make sure to back it up once you're back in tw
[Galaxy S 4 i9505 Original Android Development] Bejda:
Give precisions please if you need help.

You're on secondary/multiboot Rom and when you choose primary rom through dual-boot switcher app or dual-boot utility cwm zip and reboot it still boot to secondary/multi?

If that's the case i'd say you forgot to set current kernel as primary rom with dual-boot switcher app before flashing secondary rom.

Anyway it's pretty rare to loose any rom's data here, either it's a set kernel problem as I mentionned above or it's rom /system that got wiped and if you flash rom again /system is back and you see that its /data are still here,untouched.

If you flash again your primary touchwiz rom you will for sure boot into it right after without data loss. Then you set current kernel as primary and will have to reflash your secondary rom also (cause flashing primary rom again will wipe secondary system but here again secondary rom data should be safe/untouched).
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
I was thinking to flash the kernel for my TW.

Since I used stock official 4.3, I have to flash it via Odin right? And Odin will wipe my data automatically.

BTW, where can I get stock kernel for 4.3 MJ7?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
I haven't seen any stock kernels by themselves. Either reflash the rom, or get a custom kernel. I would try to avoid Odin if you don't have to use it. It's harder to see what's in the tar file and where it's going
[Galaxy S 4 i9505 Original Android Development] Bejda:
You may find it by here: http://xdaforums.com/showthread.php?t=2250824

But indeed why not give a try to a touchwiz 4.3 cwm zip custom one such as this: http://xdaforums.com/showthread.php?t=2297379
[Galaxy S 4 i9505 Original Android Development] rejanmanis:
Just flash Ktoonz kernel 4.3 TW, and Viola... back to my primary ROM.

Thank you guys.
[Galaxy S 4 i9505 Original Android Development] gravedigger76:
Hi Guys,

I'm on ATT S4, and currently running KangaKat by IB4STID as my primary ROM which is Google Edition 4.4 ROM

I would like to add IB4STID's GoldenEye as my secondary ROM.

This is a TW 4.3 ROM.

Has anyone tried this setup before? Will it work?

What steps do i need to follow to get this working? Sorry this is my first time diving into a dual boot on this one.

Any help is greatly appreciated.

Thank you
[Galaxy S 4 i9505 Original Android Development] Bejda:
Don't forget to set it as primary rom kernel via dual-boot switcher app.
[Galaxy S 4 i9505 Original Android Development] YaKoStar:
Is there any way to have Omega rom as secondary?
[Galaxy S 4 i9505 Original Android Development] RK:
I am running the same exact setup. It works. I am even sharing user apps between the two...
[Galaxy S 4 i9505 Original Android Development] alvin551:
How do you share the apps between them?
[Galaxy S 4 i9505 Original Android Development] RK:
Just add this to an existing init.d script of the secondary ROM, OR make a new init.d script with these lines in it:

mount -o bind /raw-data/app /data/app

mount -o bind /raw-data/app-lib /data/app-lib
[Galaxy S 4 i9505 Original Android Development] Buddyjohn:
i did not rename the rom. try it with the jfltecan version. of dirty unicorn.

i redownloaded the kernels fresh and the patched. redownloading dirty unicorn and going to test again.

EDIT: i realized that link i gave did not include the canadian version, this is the link of the one i was trying to patch:

http://dirtyunicorns.com/dusite/devices.php?d=jfltecan

EDIT2: redownloaded the canadian version of du, i got unsupported zip. and i did not rename it

EDIT3: I also took a look at patching gummy rom, freshly downloaded nightly and i got a bad zip error
[Galaxy S 4 i9505 Original Android Development] XxmentxX:
Hei Dev thanks for your great work i'm very happy :) how do I install your rom as sencondary rom? I wanna try it!!
[Galaxy S 4 i9505 Original Android Development] Shanks:
Read here my friend and good luck http://xdaforums.com/showthread.php?t=2447534

---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------

Can you also share application data? Thanks in advance man
[Galaxy S 4 i9505 Original Android Development] se@wind:
Well I took the risk and tried what you sent through pm but unfortunately no luck.... it looks like I have the exact same error messages except Warning: No file_contextsTarget: 1498674457 changed to Warning: No file_contexts
[Galaxy S 4 i9505 Original Android Development] Dogfree213:
Hello ! Can you please add these 5 phone models in support of DualBootPatcher. All very much hope that these devices will add to the support.

Write to me in messages I send logs
[Galaxy S 4 i9505 Original Android Development] se@wind:
Looks like I'm able to attach files now! I feel like a part of the community ha ha! Please help me solve why I can't install roms on the compatible Honor 8 FRD-L04...

I have attached the updater-script from the rom, and both multiboot.log's when I try to install in TWRP and DBP. The errors displayed when I attempt to install are:

Dual Boot Patcher:

Warning: No file_contextsTarget: 1498674457

E1001: Failed to update system image.

[MultiBoot] Failed to run real update-binary

[MultiBoot] Failed to flash zip file.

or

TWRP:

[MultiBoot] Failed to flash zip file.

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/RR-N-v5.8.3-20170628-frd-Unofficial_dual.zip'

Thanks
[Galaxy S 4 i9505 Original Android Development] garvit girotra:
here is log file for failing the ramdisk update on my lenovo a6000 plus running aosp extended version 4.4 32 bit os every time i try to update the ramdisk it show error and create a log for that please check that
[Galaxy S 4 i9505 Original Android Development] xdamami:
Mi5X primary Miui9

Secondary want to install Mi A1 Port fail flashing.
[Galaxy S 4 i9505 Original Android Development] dogfree321:
Hello ! Can you please add these 5 phone models in support of DualBootPatcher. All very much hope that these devices will add to the support.
[Galaxy S 4 i9505 Original Android Development] dadi11:
[MENTION=4277844]chenxiaolong[/MENTION] can you update dual boot patcher with the latest 8.0 changes? so it doesn't fail on checking device assert

https://github.com/omnirom/android_bootable_recovery/commits/android-8.0
[Galaxy S 4 i9505 Original Android Development] vczilla:
I wrote a post on how to get Oreo builds working with DBP that you can find there:

https://xdaforums.com/showpost.php?p=74373698&postcount=242

Also if you're using a data slot sdcardfs will not work correctly by default.

From what I can gather it's due to the way then emulated partitions are mounted because if you remount them manually ( namely /mnt/runtime/read/emulated and /mnt/runtime/write/emulated ) it'll fix it.

Finally it's possible to actually flash Magisk on a non primary ROM.

The reason why it's not been working is due to the way Magisk uses an embedded busybox whereas dbp just intercepts the one in /sbin to intercept calls to the mount, umount and reboot commands.

If you erase these three ones from the custom Magisk busybox directory it'll then work.

You can do so by adding these three lines to Magisk's update-binary:

rm $BBDIR/mount

rm $BBDIR/umount

rm $BBDIR/reboot
[Galaxy S 4 i9505 Original Android Development] garvit girotra:
After the latest 102 release ramdisk update still fails in lenovo a6000
[Galaxy S 4 i9505 Original Android Development] garvit girotra:
After the latest 125 release only update ramdisk fails else boot ui and set kernel works perfectly fine only ramdisk have error
[Galaxy S 4 i9505 Original Android Development] edyny1:
Why is the reason that when i flash a new kernel on primary rom, the data-slot rom no longer boot? It stay stuck on the samsung splash screen.

---------- Post added at 04:22 PM ---------- Previous post was at 04:15 PM ----------

Where exactly do we find the custom magisk busybox directory and the Magisks update-binary???
[Galaxy S 4 i9505 Original Android Development] vczilla:
In the magisk.zip you flash when you install Magisk.

Just unzip it and the two files of interest are under this path:

META-INF/com/google/android/

There'll be two files updater-script and update-binary.

The second one is actually a text file containing Magisk's busybox that's been ASCII encoded. This file is quite big so some text editors would choke on it.

But that's fine because updater-scriot gets called by update-binary during the installation process so just add them three lines there and rezip it.

Or use MiX because it allows to do in place modifications of zips without having to extract them.

Addendum:

Also you should note that the way Magisk detect if a partition is mounted is buggy so you'd need to edit this function as well:

is_mounted() {
if [ ! -z "$2" ]; then
cat /proc/mounts | grep $1 | grep $2, >/dev/null
else
cat /proc/mounts | grep $1 >/dev/null
fi
return $?
}

which you can find there:

common/util_functions.sh

and replace it with this:

is_mounted() {
if [ ! -z "$2" ]; then
cat /proc/mounts | grep " $1 " | grep $2, >/dev/null
else
cat /proc/mounts | grep " $1 ">/dev/null
fi
return $?
}
[Galaxy S 4 i9505 Original Android Development] dimuthu7:
How i fix this i have on thread.my primary ia wizcyan s4 4.1 rom and tryied secondary jdc 8.1.0 dp rom.
[Galaxy S 4 i9505 Original Android Development] Eleo:
We cant know unless you share us the created "multiboot.log" file. It is in root of your internal memory
[Galaxy S 4 i9505 Original Android Development] dimuthu7:
Sorry my mistake
[Galaxy S 4 i9505 Original Android Development] dimuthu7:
Pls can somone help me i am realy intrest
[Galaxy S 4 i9505 Original Android Development] mbr007:
Please add Infinity Note8 MagMa v1.0. Thanks.