Database Users

How can I remove Magisk?

I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?

Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.

@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.

Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)

@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.

Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update

So how to root Android 10?

If we don't have TWRP,
How do we root the device?

Magisk has the option to patch a boot.img file. Technically, you could:
1. pull the boot.img file from the A10 OB1 zip
2. copy it to the phone's internal storage
3. install latest magisk manager, click on install - patch boot.img - choose the boot.img
4. copy the patched boot.img to a pc with ADB and USB drivers
5. put the phone in fastboot mode, sideload the boot.img
I have no idea if this would work, but you could give it a go. I believe that someone else already made a guide for exactly this here in the OP6T forum.

Refer to the twrp thread for OB 10.
https://forum.xda-developers.com/oneplus-6t/help/how-to-flash-twrp-android-10-beta-1-t3986345
Either do the OTA local upgrade and magisk uninstall then install to inactive slot method, or use the boot patch which there is another thread on that on the ROM Dev section.
I used the first, worked fine. But there is no supported twrp yet. Only magisk root is officially supported on Q.

Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.

g4seb said:
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
Click to expand...
Click to collapse
Yes, likely because the update flashed to the inactive, and there is no recovery now. So...if you want recovery, only way is to full wipe and do a MSM or flash all and wipe with older stable.
OP support/forums made announcements on their thread on what will happen with upgrading, or rolling back.
They have a rollback file you can download if you want it all working again including recovery. But you will get wiped as mentioned, and be back on the last stable and firmware. Then you can twrp and root all over again.
That is Beta testing for you!!

Root disappears after a while

Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong

aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?

c_86 said:
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
Click to expand...
Click to collapse
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...

aktap said:
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
Click to expand...
Click to collapse
After which point should i do it?

I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app

c_86 said:
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
Click to expand...
Click to collapse
Okay i'll try
Thank you for your help

aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.

elmarian756 said:
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
Click to expand...
Click to collapse
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?

aktap said:
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
Click to expand...
Click to collapse
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it

dladz said:
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
Click to expand...
Click to collapse
I rooted my phone again, without LP the system is stable. Thank You for Your help!

Good good.
Tbh there is no reason to use that app. And now it causes a lot of crap anyway, best to avoid it

Can't patch boot.img after updating to 11.0.5.5

Good day fellow XDA members,
I recently updated my 8 Pro to 11.0.5.5 and forgot that i should not have rebooted it. (Worst idea ever, i know)
I had Root with Magisk before, but now I don't obviously.
So I thought to myself, that this shouldn't be a problem just flash the patched_boot.img anew and i'll have Root again.
Well that was certainly not the case.
I tried just about anything I could find on some Forums the last two days, but couldn't get the device rooted.
What i tried:
Several boot.img from XDA and also patched my own boot.img from the extracted payload with every Magisk apk from 21 onward(Also beta and Canary).
The old patched boot.img i used before the update.
Horizon bootloader
There is obv no Magisk module present anymore to disable/delete.
I also have EdXposed installed.
Everytime i tried something other than the original boot.img i got either a bootloop or a crashdump screen.
Can i get root back without fully wiping my 8 Pro?
If yes, how?
If not, how can i backup everything because some Data from some Apps is crucial to me and is not saved in the Cloud.
Thanks in advance
Dead1y_Wolf

I'm on the same boat I did direct install instead of install to inactive slot

Just follow my guide, change the payload dumper you're using, use the latest version of magisk
Bare in mind that you need to match the version used to create it.
Also don't flash the image. Just boot it.
Make sure modules are removed beforehand.
If that still fails then use the ADB magisk removal command then proceed.
I've booted, flashed, directly installed and updated then installed a lot and have never had a single problem..
So the process is correct..

Install TWRP via official app after you have root with magisk?

Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards

only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)

alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files

you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.

alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery​
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?

let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)

alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version

you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json

alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )

look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json

alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version

refer to post #8

Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time

wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371

alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)

With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com

alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.

WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?

patch the tar file