Database Info

Android 10 update TWRP not booting

Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk

Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?

I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?

equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk

Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk

Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).

First fastboot stucked
Second no partition found
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GM1911 using Tapatalk

You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.

redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.

Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.

links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997

hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!

hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?

Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1

hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.

branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10

hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.

redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.

hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.

redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.

[Q][RECOVERY][3.4.0-0][kane] Official TWRP & Root for Motorola One Vision

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root & TWRP 3.4.0 for Android 10.​
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.

Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.

No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk

I think something's messed up with my phone by transitioning from the older TWRP to the newer one
Edit: My device fails to fastboot boot twrp after I try reflashing the entire firmware. I think it has something to do with the edited vbmeta file I was using before, because it boots when I flash the patched vbmeta file this TWRP doesn't need.

ilia3367 said:
After almost a year, the official TWRP for Motorola One Vision has finally arrived!
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Click to expand...
Click to collapse
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good morning,
Currently, I have installed the version you patched, 3.3.1.
Can it be installed from the "unofficial" version: https://forum.xda-developers.com/showthread.php?p=80352223?.
Does it give a problem, or does it work perfectly?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839

daekdroom said:
The official TWRP instructions do not mention it, but you still need the patched vbmeta file for booting TWRP. Also, encryption is not working as of QSAS30.62-24-10 and 62-24-7 ROMs. I ended up going back to this TWRP version https://forum.xda-developers.com/one-vision/how-to/twrp-3-3-1-0-root-updated-kane-troika-t4102839
Click to expand...
Click to collapse
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards

daekdroom said:
Has anyone succesfully decrypted data when booting TWRP? I've wiped after installing the ZIP and I cannot decrypt data there. I've tried changing device password from PIN to pass, as it requires me to type a password in TWRP, and I still can't decrypt there.
Click to expand...
Click to collapse
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
gonzo1963 said:
Good afternoon,
Has anyone tried to install this TWRP starting from a firmware "no touch" ("clean install")?
Regards
Click to expand...
Click to collapse
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.

Nevil Sebastian said:
Decryption may or may not work with different OS releases, it's mentioned in TWRP downloads section of this device.
---------- Post added at 07:16 AM ---------- Previous post was at 07:05 AM ----------
Yes, from what I heard it doesn't boot through fastboot boot either with patched vbmeta or clean ROM. If you are rooted, you can use magisk module TWRP installer, but after flashing you will loose root access asusual or you can flash recovery ramdisk through existing recovery. Also don't forget unofficial builds.
Click to expand...
Click to collapse
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good morning,
From what I understand it doesn't work well in either case, does it?.
So what is it for, is it better to use the old "patched" TWRP: https://forum.xda-developers.com/showthread.php?p=82629961?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
You can use whichever build you want. We should wait until everything gets solved slowly.

Nevil Sebastian said:
You can use whichever build you want. We should wait until everything gets solved slowly.
Click to expand...
Click to collapse
Good morning,
Thanks for the reply, but ...
This new and official TWRP, does it work 100% or not?
Regards

I did the Instruction to install TWRP and geting Root.

Do I have to unlock my bootloader first before doing this? I just noticed we finally have a custom ROM for the One Vision! This finally makes it worth while to unlock, install TWRP, install a custom ROM and root this thing finally!

alphalog said:
No problems here.
adb fastboot boot twrp_3.4.0-0.img and then flash twrp_3.4.0-0 zip in TWRP.
Havoc OS booting fine.
Gesendet von meinem Phh-Treble vanilla mit Tapatalk
Click to expand...
Click to collapse
[How do you install HavocOS? Is there any ROM source?]

delete this

HourlongTuna5 said:
[How do you install HavocOS? Is there any ROM source?]
Click to expand...
Click to collapse
Havoc-OS GSI
Havoc-OS Generic System Image for all devices
www.pling.com
[email protected]

So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??

tin0o said:
So which TWRP do you recommend? The latest version (3.4.0-0)? Or the older version (3.3.1-0) ??
Click to expand...
Click to collapse
3.4.0-0 (for gsi and stock image)

Download TWRP for kane
Download TWRP Open Recovery for kane
eu.dl.twrp.me

ilia3367 said:
Root & TWRP 3.4.0 for Android 10.​
Page on the official TWRP website https://twrp.me/motorola/motorolaonevision.html
Installation Instruction
1. Download twrp-3.4.0-0-kane.img and twrp-installer-3.4.0-0-kane.zip TWRP, patched vbmeta.img and Magisk-disable-dm-verity-v20.4.zip (see in the attached files).
2. Copy files:
- twrp-3.4.0-0-kane.img and vbmeta_patch.img to the folder adb with the adb & fastboot drivers;
- twrp-installer-3.4.0-0-kane.zip, Magisk-disable-dm-verity-v20.4.zip on SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash vbmeta C:\adb\vbmeta_patch.img
Code:
fastboot boot C:\adb\twrp-3.4.0-0-kane.img
The phone will load into TWRP.
4. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install twrp-installer-3.4.0-0-kane.zip.
5. Go to "Wipe" and press Format Data for deencryption. Enter Yes on request. We go to TWRP Main Menu and reboot again in Recovery.
6. Go to "Install". Click on "Select Storage" button, select Micro SDCard, OK. Install Magisk-disable-dm-verity-v20.4.zip.
7. Reboot into the system.
Click to expand...
Click to collapse
Hi....
Should i use this method for android 11 ?

[RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 3

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse

Frequently Asked Questions (FAQ)
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP zip from twrp.me
Magisk app
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install TWRP zip in Magisk app
Install Magisk "to Inactive Slot (After OTA)" in Magisk app
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites (for stock images, see attachments to post #3):
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP image or TWRP zip from twrp.me
Magisk apk (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip. Make a note of the slot to which the zip is installing (you will need this after the next step).
Install TWRP image using "Install Image" (check "Flash to both slots" option), or flash TWRP zip to retain TWRP.
Open the Reboot menu in TWRP and switch to the slot to which the zip installed from step 4. Reboot to system now, or go to the next step.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse

Stock Boot/DTBO/Recovery Images

Keep up the good work m8 @Captain_Throwback :highfive:

Great job!

Reserved

sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?

Woohoo! Excellent!
Sent from my ASUS_I003D using Tapatalk

about twrp
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.

chacho_2me said:
sup guys. been a long time that i havent installed twrp.
jiz wanna ask if i have twrp if OTA is still possible?
Click to expand...
Click to collapse
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.

Captain_Throwback said:
This happened to me before when my device data partition got corrupted. You'll have to do a RAW flash that uses fastboot -w to clean up the corrupted data. Then TWRP should work. Unfortunately that is unrelated to TWRP.
Click to expand...
Click to collapse
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now

Monsibd said:
hey there, thank you so much my man you fixed my mobile! you rock!! <3
however now theres a new problem after doing the Fastboot -w, i installed the twrp but i cant mount the data partition because it asks for password (which there shouldnt be cause i just reset the phone) and after restarting into the system and setting it up, I get the same results as before (the twrp loading screen shows and reboots back to system).... so yea kind of lost now
Click to expand...
Click to collapse
Where is the recovery log from the TWRP boot where it was prompting for password? The OP clearly states that a log should be included with any issues. Do me a favor and try flashing the TWRP attached and let me know if it boots.
https://drive.google.com/file/d/1-2qBUqYv0AWnvqDmxIY2DqRqwG5dSwHg/view?usp=drivesdk
If it does, I can adjust the TWRP image linked in the OP. If it doesn't, I'll definitely need a log to understand the issue, and your device details.

So I did some testing, and it appears that if you're not on the latest .58 firmware, then TWRP may not boot successfully. Can anyone that has had an issue with booting TWRP please report their device variant and firmware version? If you're not on the latest, please update and then try TWRP.
WW 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/...US_I003_1-ASUS-17.0823.2007.58-1.1.9-user.zip
CN 2007.58 Full Firmware: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS661KS/UL-ASUS_I003_1-CN-17.0823.2007.58-1.1.45-user.zip
If that doesn't work, let me know.
EDIT: Actually I need to check again. I think I broke my TWRP tree so it may not be the kernel at all :/

Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?

Captain_Throwback said:
Well, unlocking the bootloader means you won't get an OTA from ASUS anymore, but that has nothing to do with TWRP. When a new OTA becomes available, you will be able to flash the full firmware file in TWRP, if that's what you're asking.
EDIT: Installing TWRP won't prevent you from being able to place a firmware file on the root of your storage so that the system updater will detect and install it, either. That process happens outside of recovery so flashing TWRP is unrelated to it. However note that after flashing an OTA update, TWRP will need to be flashed again, as the OTA will write stock recovery to the slot where the OTA is installed.
Click to expand...
Click to collapse
so basically installing twrp can still be overwritten when flashing original firmware from asus
.thanx sir

Monsibd said:
Hey sorry for taking such a long time to reply, life happened to me.
I am on the latest firmware (cn_17.0823.2007.58)
I am sorry as I didn't send the recovery log, I will be testing the latest twrp you attached for me with the Google drive and let you know the results shortly :good:
Edit: the same happens with this twrp file too, it just shows the loading screen and boots to system directly, would you want me to clean flash and then do the recovery all over again with the logs?
Edit 2: by any chance would be able to get hold of the stock_recovery.img or do you know any way to flash the stock rom without recovery? FYI my version is cn_17.0823.2007.58 ,will recovery from any version work though?
Click to expand...
Click to collapse
So maybe there is some difference with the CN device that's causing this issue. Everyone it's working for is running WW firmware. Not sure what's different with the CN firmware, but that's unsettling.
Since the full firmware file is available, you can just use payload dumper to get the stock recovery image.
And yes, a clean flash with logs would be great, thanks!

Monsibd said:
hey guys, i have tried to install the twrp but after installing using the powershell whenever I try to restart to recovery it just shows the twrp loading screen and restarts back to the phone, so basically I dont have any recovery anymore
Click to expand...
Click to collapse
same as you im on the latest ww firmware tencent games variant and rooted

bouyhy01 said:
same as you im on the latest ww firmware tencent games variant and rooted
Click to expand...
Click to collapse
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.

Captain_Throwback said:
So yours is Tencent converted to WW? I'm going to build a TWRP with the CN kernel and if that makes any difference. There must be something different with the Tencent variant that's causing the kernel panic.
Click to expand...
Click to collapse
thank you very much captain i'll be waiting for it to test

How To Guide Gaining root access on New Oxygen OS A12 for the op9.

Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
Just sharing what I've learned. Have to patch boot.img and vendor boot.img and flash out of folder in sdk on desktop.Then use vb_meta.img to disable verity flash. Guide above has to be followed to a T. Even though it's for the Chinese version Color os works fine on Oos... Patch boot.img /vendor_boot with magisk 23.0. This way magisk hide and modules work. If you patch with canary version of magisk you loose both. I'm attaching stock boot, vb_meta vendor_boot.img files for the Global unlocked op9. Files are from new A12 os. Btw 23.0 works perfectly on A12. If this helps hit the like button; it's free.
0p9 partitions..A 12 - Google Drive
drive.google.com

This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.

allenjthomsen said:
This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.
Click to expand...
Click to collapse
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
I can verify that my method works 100% on build C.36 of A12, because i am currently running it and have redone the steps multiple times to make sure nothing happens that could be bad ,the steps i have listed above in the previous post work perfectly and still let me have root currently, and i have only patched the stock boot.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.

allenjthomsen said:
If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.
Click to expand...
Click to collapse
How does one undo the disable verity with stock vb_meta after flashing back stock boot.img and vendor boot.img ,I still couldn't take internal Google ota today. Failed after I tried restoring both of those.

Anyone knows if the new oos12 is actually "stable"? Haha

infamousvincci said:
Anyone knows if the new oos12 is actually "stable"? Haha
Click to expand...
Click to collapse
Yes all the small issues I had are corrected in today's am build.

mattie_49 said:
Yes all the small issues I had are corrected in today's am build.
Click to expand...
Click to collapse
I talk to you in TG bro. Its me, the one that has a op9 that doesnt read sim on oos12. Hahaha

mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.

mizarddo said:
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.
Click to expand...
Click to collapse
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked

mooadeer said:
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked
Click to expand...
Click to collapse
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
It helps a lot thank you I just got my oneplus 9 and it's on the latest update C.47 and I don't have too much experience with onePlus or even the new android devices I'm a little bit outdated didn't use root and stuff sins the android 5 that's why I'm a little bit confused I don't want to break it

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
Update following your instructions everything is Ok done with rooting thank you
LE2113 on C.47

mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
from where can I download boot.img for version:
LE2113_11.C.47: LE2113_11.C.47_1470_202203102118
Thanks and best regards

Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
you mean boot image from OP? My question is how I get that file

aldoc01 said:
you mean boot image from OP? My question is how I get that file
Click to expand...
Click to collapse
Yep, stock boot images can be extracted from full zips with tools (payload extractor).
Also, i have a collection, check it out.

_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...

EtherealRemnant said:
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...
Click to expand...
Click to collapse
If you don't jump magisk across from A11 you have to disable verity with vb_meta partition as well to gain permanent root on A12. This I know it's my post.

[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.