[Help] Using Magisk on a Dual Booted custom rom - Magisk

Hi all, I rooted my phone's primary rom using Magisk, and I flashed a secondary rom using Dual Boot Patcher. I would like to pass safetynet on the secondary rom as well as keep root, but so far all I could flash on my second rom is a Dual Boot Patcher patched SuperSU zip file. When I tried to patch and flash Magisk, it failed to mount system. All help is appreciated, thanks a lot.

@TCUofficial try patching the boot.img of secondary ROM with the ADB Magisk Manager method explained in official Magisk thread.

Related

Magisk deleted EVERYTIME after flashing

I'm in a Lenovo with LineageOS, and everytime I flash a nightly (update), the root is gone, I have to flash Magisk again.
Is there any way to keep Magisk installed after an update?
Thanks
Every time you update, the Magisk modified boot image is overwritten by the ROM's stock boot image. Since the Magisk modifications are done to the boot image, this means Magisk is removed.
Solution:
Make sure to use a ROM with working addon.d or simply flash Magisk manually after every update.

Stock boot img problem with magisk

I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
! Boot img patched by other programs
! please restore stock boot img
Click to expand...
Click to collapse
I don't have any custom rom, i'm actually oos 5.0.3. I first try to root but dm-verity was triggered and then followed all the steps to disable it.
Any solutions?
Nube420 said:
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
Click to expand...
Click to collapse
Magisk is a root zip. It sounds like you are flashing SuperSU and Magisk. You can only use one or the other, not both!
Reflash stock ROM (or at least stock boot.img). Then flash Magisk. That's it.
Getting the error message that boot.img is modified is normal and expected in your case. SuperSU patched the boot image. Now Magisk is looking for the stock image to patch, and finding a patched one.

boot-loop after flashing patched boot image with twrp and sp flash tool.

Hi I this is my first post in xda so pardon me for any mistake.
I am facing some issues while rooting my phone with magisk
I have Micromax q372 unite 3 (2015) running android lollipop v5.0 and I am trying to root with magisk v6.0.
So first I tried to flash magisk zip directly with twrp 3.0.2-0 recovery but it showed an error- unable to unpack boot.img
So I patched boot.img file using magisk manager and then tried flashing it with twrp and my phone went into boot-loop (i was unable to use adb method)
so I renamed patched_boot.img to boot.img and replaced this with an original boot.img file in my firmware and flashed the whole firmware using sp flash tool
and I got into boot-loop again. (I know how to solve boot loop.)
So how to root with magisk now.
- there is no new version of twrp available for my device.
- adb method not working.
- flashing original boot image also not working.
Please help me.

Need help installing TWRP with Magisk

Hello everyone!
I just rooted my Galaxy A30 using Magisk. From what I have understood in my experience rooting this. This phone doesn't have a ramdisk so Magisk basically only boots when I do the recovery key combo. So I was wondering, Is it possible to install TWRP on this device since Magisk is basically hijacking the recovery to run. If it is possible, could someone guide me on how to install it while preserving Magisk?
Thanks in advance
The only way is installing TWRP via Odin. And then flash Magisk.zip

Root not working after flashing Magisk patched boot.img on Samsung GT-I9300

It's a bit of an older phone but I cannot get root properly working on my Samsung GT-I9300 using Magisk. I need Magisk to hopefully get some banking apps working again on my LineageOS 17.1 custom ROM. I downloaded Magisk v25.2 (Latest) from github, patched the boot.img from the installed ROM: lineage-17.1-20200717-UNOFFICIAL-i9300.zip, all with no errors.
Instead of using fastboot I renamed the patched magisk_patched-25200_eb1Em.img to boot.img and created a tar file from it so I can flash it with Odin3 v3.14.1.exe (AP checkbox) as I did for the twrp recovery image. After this some signs of root access are visible. Root Checker Pro even shows my device as rooted. Still it says that the su binaries are missing and Magisk keeps showing as not installed. I even tried CF-Auto-Root-m0-m0xx-gti9300.tar through odin and/or flash UPDATE-SuperSU-v2.46.zip through the installed twrp recovery but the results stay the same.
Wat can I do more to get it working?

Categories

Resources