Database Info

Systemless Root without custom recovery | Shield Tablet 5.3 ROW

I'm wondering if anyone tried to root Shield Tablet with Magisk without custom recovery? In the guide it says you have to patch the stock boot.img. I'm just a bit worried since the stock boot.img you can download from Nvidia is for firmware 5.2 and I have the 5.3 OTA on my tablet.
I want to do the following:
"Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the*latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select*.img.tar. For normal users leave it as the default*.img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in*[Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img"

This method hasn't any sense for our tablet. If you don't want install twrp you can do "boot only" twrp.
Make full backup and flash Magisk.zip.
fastboot boot NameOfTwrp.img

dzidexx said:
This method hasn't any sense for our tablet. If you don't want install twrp you can do "boot only" twrp.
Make full backup and flash Magisk.zip.
fastboot boot NameOfTwrp.img
Click to expand...
Click to collapse
Thanks! This was a better method! I successfully installed Magisk without installing twrp.

erik90 said:
Thanks! This was a better method! I successfully installed Magisk without installing twrp.
Click to expand...
Click to collapse
What is the point in not installing TWRP? TWRP is much more functional in every way than stock recovery.

redpoint73 said:
What is the point in not installing TWRP? TWRP is much more functional in every way than stock recovery.
Click to expand...
Click to collapse
I just wanted to root my Shield Tablet and still be able to receive OTA´s if there will be any more.
Don´t have the need for custom recovery since I like the tablet stock with exception for root, I tried a few custom roms but there was always some bugs.
One feature from stock I can´t live without is the Button Mapper, it´s amazing that it works with all bluetooth controllers that I have tried.

erik90 said:
I just wanted to root my Shield Tablet and still be able to receive OTA´s if there will be any more.
Click to expand...
Click to collapse
The OTAs install properly with TWRP and root.

Official TWRP for Moto Z3 play has been released on TWRP site

https://www.xda-developers.com/motorola-one-power-moto-z3-play-twrp/
Support Status: Current
Maintainer: kaneawk, erfanoabdi
Code Name: beckham
Device Tree / files
NOTE: Monthly security updates may break
decryption of /data in TWRP. MTP does not
work at this time, but you can use adb to transfer files.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoz3play.html

The new twrp works fine

Hopefully this means more support in the future. Did you flash or boot? Curious if it will bootloop if I flash the img

Installation:
If you do not already have TWRP installed: Download twrp img. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot twrp.img
This will temporarily boot TWRP on your device.

I'm aware of how to boot TWRP on my device. I was wondering if it would be possible to *flash* it though. As I understand it you need the TWRP zip compiled and was wondering if you got that working or not for this device.
Booting is fine for now but I need to have TWRP as recovery for bootloops when I don't have my PC available
Edit for spelling

what works
I have downloaded the twrp.img
I ran fastboot boot twrp.img
I have downloaded magisk 17.1 and flashed it via twrp
Installed Magisk Modules: AdgaurdDNS, Greenify4Magisk, and Viper4Android FX
what doesn't work
installed xposed framework via magisk -> caused bootloop

Pretty sure it's an Xposed bug because Xposed bootloops on any device that's got 8.1 with latest patches

So if we can unlock the bootloader, and boot to twrp, can we not install supersu from there? Or am I understanding this wrong?

Magisk is superior in about every way. Also super su isn't being developed anymore

Ah, I'll look into it more. My last phone was forever old, and my only option was SuperSU. Thanks!

please any help update the download TWRP file, because in github the developers say mount vendor is working, but the file in twrp webpage its old.

Has anyone tried booting this on the Sprint version

Help me plz
hello, Im trying to install the twrp recovery but i cant, its happing a error
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.999s
and i dont know how to solve, please help me

Trwp can't be installed on this device as far as I know. Available twrp is for booting purposes only.
Fastboot boot twrp.img
Click to expand...
Click to collapse

Whenever I use the command fastboot boot twrp.img, it boots just fine but if I try to use fastboot flash recovery twrp.img, it gives me an invalid partition name recovery error. I am trying to root the device. To my understanding, if you just boot into TWP, its only temporary. I guess my question is, is flashing the .img necessary and if so, why is it giving me this error? I got the .img from the offical website, its in the same folder as fastboot, and even boots right up if using the boot command so the image isnt corrupt. Any suggestions?

You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.

?

darkdaemon32 said:
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
Click to expand...
Click to collapse
So can I root this device without installing TWRP? I want to continue using my mods (which I believe TWRP will break) and I don't really care about the custom recovery at this point but want root access for a few select items like AdAway.

There isn't even a way to currently INSTALL TWRP on the z3. The only way to use twrp is with fastboot boot. And you use this to temporarily boot to twrp and flash the magisk installer zip for root. Magisk is systemless and doesn't modify system so you should be able to use all apps that detect system modifications such as gpay etc.

Would anyone help me? I saved the Magisk file to internal memory, but when I try to install TWRP (fastboot boot twrp.img) the internal memory files are encrypted.
How do I decrypt these files so I can do the Root?

Rooting for March Update?

Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.

lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer

rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.

lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.

rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute

Won't let me simend the link

rob420p,
Please provide links.

rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?

I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.

lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?

I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY

marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!

lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:

Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks

max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952

I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.

max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....

Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now

[Guide] Flash Magisk on Android 12

Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images")
Some users have reported that booting (instead of flashing) the patched boot image works and makes root temporarily available but i didn't have any success with that.
The phone booted up but root didn't work.
I won't explain how to unlock the bootloader or set up adb here.
!Warning! This will wipe your phone so take a backup!
Also i do not take any responsibility if you break your device.
And if anything goes wrong just factory reset your device using the Android Flash Tool or by following this tutorial.
Here's what i did to get Magisk v22.0 working on the first developer preview of Android 12:
Install A12 with disabled AVB & dm-verity:
Make sure USB-Debugging is enabled in developer-options and you have authorized the pc you're using on your phone.
Boot your phone into fastboot mode.
You can do this by turning it off and then starting it by holding Power + Volume Down
until fastboot mode appears or just adb reboot bootloader
Go here and click on the link for the Android Flash Tool.
(I didn't copy the link directly so i don't have to update it everytime google releases a new update)
It should ask you to allow the website to access ADB Keys. Click Ok.
If the website somehow doesn't work, try using Google Chrome.
Select your Pixel 5. If it's not showing up click add device.
Click on the edit symbol (pen) in the box where the selected build is shown.
Make sure Wipe Device, Disable Verity and Disable Verification are checked.
Install and boot the phone when it's finished.
Patch & flash boot.img
Download and install the Magisk Canary App from GitHub.
Download the factory image from here and extract boot.img from it.
(Inside the downloaded zip-file is another zip file containing the boot image)
Copy the extracted boot.img to your phone and open the magisk app.
Click on Install -> Select and Patch a File and let it do its magic.
Copy the magisk-patched boot image that should be found in your phones download folder back to your PC.
Reboot into fastboot mode as i explained earlier and flash the patched boot image.
(fastboot flash boot magisk_patched.img)
Then reboot the device.
Now root should be working. If it bootloops and says your phone has to be factory reset, do it.
If for some reason you still get an AVB-Error and end up stuck in fastboot mode just flash the stock image and try to patch it again.
This is my first post on here and i didn't have much time but i'm glad if it helped at least one person.

Thanks for create this post.Works perfect,

Ivixmax said:
Thanks for create this post.Works perfect,
Click to expand...
Click to collapse

Hey, thanks for this. FYI @LazerL0rd (zest kernel) detailed here (click on the spoiler) how to do this with just the command line and factory images and without the need for the AFT.
edit: formatting

I keep on getting the AVB-Error to no end.

new beta magisk not working

morpheus620 said:
new beta magisk not working
Click to expand...
Click to collapse
Make sure to disable verity & verification and use magisk canary, not beta

okay. is working. sorry für the misstake.

morpheus620 said:
okay. is working. sorry für the misstake.
Click to expand...
Click to collapse
Alles gut

Anyone able to get safety net to pass on Android 12?

greenlight63 said:
Anyone able to get safety net to pass on Android 12?
Click to expand...
Click to collapse
Unfortunately no, universal safetynet fix 2.0.0 by kdrag0n makes basicIntegrity pass but since the update to dp3 CTS still fails.

Dirty flashing newer factory images will restore the verity and verification state, so when you patch the kernel with magisk it will fail to boot again.
Installing a verity and verification disabled image without wiping from the web based flasher will also corrupt your data and not let the phone boot, forcing you to wipe.
Wonder what the flags are for flashing factory images with verity and verification state off and giving the ability to continue on without wiping and being able to boot the magisk patched kernel again.
fastboot update --disable-verity --disable-verification image-redfin-spp3210325.010.zip maybe?
Or prepatch the boot.img before flashing it with fastboot, and then flashing it back before rebooting from after flashing the factory image as an update?

tauio111 said:
Dirty flashing newer factory images will restore the verity and verification state, so when you patch the kernel with magisk it will fail to boot again.
Installing a verity and verification disabled image without wiping from the web based flasher will also corrupt your data and not let the phone boot, forcing you to wipe.
Wonder what the flags are for flashing factory images with verity and verification state off and giving the ability to continue on without wiping and being able to boot the magisk patched kernel again.
fastboot update --disable-verity --disable-verification image-redfin-spp3210325.010.zip maybe?
Or prepatch the boot.img before flashing it with fastboot, and then flashing it back before rebooting from after flashing the factory image as an update?
Click to expand...
Click to collapse
Don't know but sounds interesting. I just use
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after every update

Works like a charm Android 12 pixel 4a 5g

I just installed the newest Public Beta via OTA. Can I root? I was rooted on 11 before and just enrolled in the beta program and installed it via OTA. Without factory reset or reflash. Now I tried patching boot.img via Magisk Manager, but it wont boot. I mean it boots, but wont unlock phone to homescreen. I'm locked out of my phone. Reverted back to stock PB1 boot image. Any ideas without factory reset?

THEVAN3D said:
I just installed the newest Public Beta via OTA. Can I root? I was rooted on 11 before and just enrolled in the beta program and installed it via OTA. Without factory reset or reflash. Now I tried patching boot.img via Magisk Manager, but it wont boot. I mean it boots, but wont unlock phone to homescreen. I'm locked out of my phone. Reverted back to stock PB1 boot image. Any ideas without factory reset?
Click to expand...
Click to collapse
I just tried it using the canary build and it won't boot either. It gets stuck at the Bootloader screen and shows "Failed to load/verify boot images". Maybe we need to wait for an update to for Magisk?

QuickInfo said:
I just tried it using the canary build and it won't boot either. It gets stuck at the Bootloader screen and shows "Failed to load/verify boot images". Maybe we need to wait for an update to for Magisk?
Click to expand...
Click to collapse
Did you try it according to the manual from the first post from @myhuky3?

kafisc said:
Did you try it according to the manual from the first post from @myhuky3?
Click to expand...
Click to collapse
Not yet, I'll wait until the end of the beta program before I reset it. I can get temporary root by booting into the patched Magisk boot image

Following the OP it worked great on the public beta been running it since last night its awesome thank you for the guide

delete

[Help!] Can't root my OnePlus 7 Pro

Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?

even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.

altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.

¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?

altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!

OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?

Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?

i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!

altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?

¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.

Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.