Database Users

[GUIDE] Root using Magisk, keep stock recovery for OTA

This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.

Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g

kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?

This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.

Ok, but is Xposed etc. possible?

kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

It is really works! Thank you!

gonna check this cause i wanna root the phone but keep enjoying updates

I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial

I bump this because it worked. Quite easy, clean and fast. Thanx!

I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?

masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.

Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?

it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module

Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.

Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??

I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.

Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)

Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse

Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.

how to root android p

Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version

Ss

joeeboogz said:
Ss
Click to expand...
Click to collapse
Too late , topjohnwu released magisk v16.1 here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Magisk manager isn't flashing for some reason so you have to go into the actual file path inside the zip. /common/magisk.apk and install it manually. The module devs need to update their code, but mine should still work.

Just noticed well If u need apk still it's in my drive along with zip

How do access your drive? I tried to go the Magisk route and it hung on the Google boot screen with the loading bar and eventually rebooted itself

can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....

Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
I did the same thing. I couldn't get it to boot back to my phone but I could boot back into TWRP. So I just wiped then restored a backup I had. Try that. Or worse case scenario just boot to bootloader and flash the factory.img again. That should over write anything you have on there now and allow you to boot successfully.

Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
This may be a little late, but go back into twrp and flash the magisk uninstaller located in the official forum. Then reboot. Then reinstall magisk again

This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?

petiolarissean said:
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
Click to expand...
Click to collapse
You need to use Xposed for P, which isn't even the roadmap I'm sure lol

If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?

x31234 said:
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
Click to expand...
Click to collapse
No.

are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*

AlPoo said:
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
Click to expand...
Click to collapse
Also waiting for this. Just searched for it but it seems the full image files are not online yet. And I don't know if twrp or the ability to root will still be there if I just uninstall magisk via the uninstaller zip in twrp, and then install the OTA from today?
EDIT:
fastboot the full dp2 image
do set-up process (don't set a PIN)
fastboot twrp 3.2.1.2 img
install twrp 3.2.1.2 zip
reboot recovery
install magisk 16.4 (16.0 won't work)
done
Tested with adaway and it works fine. I expected it to be harder to be honest but I'll take it.

joeeboogz said:
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Click to expand...
Click to collapse
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.

Jerreth said:
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Click to expand...
Click to collapse
I did the same but booted to 3.2.1-2 and it worked as well

I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot

madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
sometimes it takes a second or more reboots to get into the OS.

madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
Same here

Try flashing boot.img to both slots and redo the process
Sent from my Pixel XL using Tapatalk

P2XL OTA + Magisk install before reboot = keep root

Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.

Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?

Anybody know if this worked smoothly with their Viper4Android app?

This worked form me going from Android 9 with Magisk to Android 10

I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.

gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.

Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is

kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.

Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?

kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk

Anyone know how to get the native led configuration without using a custom rom or the lightflow app?

Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available

If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.

kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w

Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only

Android 11 is live.

Today just received update notification as below image. Downloading now, let see what are changes and improvements.

I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?

TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.

tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.

Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.

socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary

Anyone have the screen record enabled in power menu and how ?

khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop

monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.

V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?

monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.

V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?

SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.

Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )

hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?

V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions

I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.

Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.

V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.

Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.

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