Develop Bugs

Phone keeps rebooting into twrp (3.2.1 official)

I've updated to the latest 3.2.1 twrp for our devices and it keeps rebooting into twrp even though i tell it to reboot to system. I've also updated to magisk 14.6

equlizer said:
I've updated to the latest 3.2.1 twrp for our devices and it keeps rebooting into twrp even though i tell it to reboot to system. I've also updated to magisk 14.6
Click to expand...
Click to collapse
Did you.....
Fastboot the stock boot.img
Then fastboot the new twrp.img
Then flash the new twrp.zip
Then custom kernel (optional)
Then flash magisk.zip?????

doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?

equlizer said:
doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?
Click to expand...
Click to collapse
I skipped the first 2 steps when upgrading and just rebooted into current twrp flashed new twrp, kernel and magisk. Profit

Dielahn said:
I skipped the first 2 steps when upgrading and just rebooted into current twrp flashed new twrp, kernel and magisk. Profit
Click to expand...
Click to collapse
That's what i normally do to but something else happened along the way. Oh well, it's fixed now

equlizer said:
doh! lemme try that
EDIT: Fixed! so you have to do these steps each time you want to update twrp?
Click to expand...
Click to collapse
I don't necessarily know if you need to this procedure every time. However, given the fact that recovery now resides in the boot.img, I just think it's a little more prudent to start with stock kernel/recovery before trying to modify it. :good:

Tried to root Pixel XL 2 and it keeps rebooting in twrp
I am a novice at this, but first ran "twrp-3.2.1-2-taimen.img. from cmd prompt.
Then using TWRP installed " twrp-pixel2-installer-taimen-3.2.2-0.zip" everything was fine.
Then installed "Magisk-v16.1(1610).zip" and now keeps rebooting to TWRP.
I can get to fastboot and rerun twrp-3.2.1-2-taimen.img, but then cannot find the zip files to install or flash.
any help greatly appreciated!

bsinkoff said:
I am a novice at this, but first ran "twrp-3.2.1-2-taimen.img. from cmd prompt.
Then using TWRP installed " twrp-pixel2-installer-taimen-3.2.2-0.zip" everything was fine.
Then installed "Magisk-v16.1(1610).zip" and now keeps rebooting to TWRP.
I can get to fastboot and rerun twrp-3.2.1-2-taimen.img, but then cannot find the zip files to install or flash.
any help greatly appreciated!
Click to expand...
Click to collapse
If your post is correct, it appears your using two different twrp's?? Anyways, lets try this. Make sure your screen lock is set to swipe or none. Then fastboot twrp 3.2.2-0.img. Once in twrp, flash the twrp 3.2.2-0 installer zip, then flash your magisk zip and see what happens. Flashing a custom kernel is also recommended after you flash the twrp.zip, and before you flash your magisk zip :good:

Badger50 said:
If your post is correct, it appears your using two different twrp's?? Anyways, lets try this. Make sure your screen lock is set to swipe or none. Then fastboot twrp 3.2.2-0.img. Once in twrp, flash the twrp 3.2.2-0 installer zip, then flash your magisk zip and see what happens. Flashing a custom kernel is also recommended after you flash the twrp.zip, and before you flash your magisk zip :good:
Click to expand...
Click to collapse
I just wanted to create an account to say THANK YOU! I had the same exact issue, and your solution worked. I did not realize I needed to reflash magisk zip.
So again, thank you @Badger50

Pre-rooted Boot Image OP7T Global HD65AA 10.0.6

Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T Global (not Indian or European) version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own Global OP7T.
Link : https://androidfilehost.com/?w=files&flid=302500

has anyone tried this one yet?

xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?

damn i want to do it but i am afraid some of my apps will stop working cause idk if magiskhide will work at current time

xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.

23333 said:
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
Click to expand...
Click to collapse
ty for the reply i might grow a few and give it a shot hopefully magiskhide is working so certain apps cant detect that i am rooted

I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure

xrelic7 said:
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
Click to expand...
Click to collapse
Are you using Global or Indian HD65AA ? Not getting an option to directly install means somehow the patched image did not boot and the original imaged booted.

imakul8 said:
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
Click to expand...
Click to collapse
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.

zeusofyork said:
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
Click to expand...
Click to collapse
Yes, that's what I have.

1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
Click to expand...
Click to collapse
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?

ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
Click to expand...
Click to collapse
You're right. Just skip that step 3.

imakul8 said:
You're right. Just skip that step 3.
Click to expand...
Click to collapse
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.

ricksrod said:
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
Click to expand...
Click to collapse
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you. ?

imakul8 said:
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you.
Click to expand...
Click to collapse
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?

ricksrod said:
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
Click to expand...
Click to collapse
Just the first two. Not recovery mode.

imakul8 said:
Just the first two. Not recovery mode.
Click to expand...
Click to collapse
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?

ricksrod said:
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
Click to expand...
Click to collapse
Stable is working for me, but good that you got it working. ?

Can someone check if magisk hide is working properly? Thanks

Jeens99 said:
Can someone check if magisk hide is working properly? Thanks
Click to expand...
Click to collapse
It works. Snapchat and my banking app don't like root. They're working fine.

TWRP adb sideload error

Hi,
Can somebody pls recommend a link for sm-505fn with TWRP that actually works on ADB sideload?
I've installed a version 311, but the adb sideload just hangs when you start it. the pc doesn't recognise any adb devices.
I need this to install dmverify or multidisabler, before running system for first time - so system doesn't trip Knox again with result of KG STATE PRENORMAL.
Please also advise if better to install dmverify or multidisabler to prevent problems.
1. Not sure to install DMVerify
https://forum.xda-developers.com/gal...0-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/gal...ption-t3919714
thanks

lawmanukdc said:
Hi,
Can somebody pls recommend a link for sm-505fn with TWRP that actually works on ADB sideload?
I've installed a version 311, but the adb sideload just hangs when you start it. the pc doesn't recognise any adb devices.
I need this to install dmverify or multidisabler, before running system for first time - so system doesn't trip Knox again with result of KG STATE PRENORMAL.
Please also advise if better to install dmverify or multidisabler to prevent problems.
1. Not sure to install DMVerify
https://forum.xda-developers.com/gal...0-100-t3966636
or
2. Multi-disabler?
https://forum.xda-developers.com/gal...ption-t3919714
thanks
Click to expand...
Click to collapse
Multidisabler

muhamet said:
Multidisabler
Click to expand...
Click to collapse
Hi,
Can you recommend a different TWRP to install, where sideload ADB works?
Otherwise I won't be able to transfer multi-disabler to a50 and flash it.
thanks

lawmanukdc said:
Hi,
Can you recommend a different TWRP to install, where sideload ADB works?
Otherwise I won't be able to transfer multi-disabler to a50 and flash it.
thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199

Hi Muhamet,
Thats the version of TWRP I've already installed.
Is there another version that works with sideload adb?
If not, I'll try to use usb otg to transfer files instead.

lawmanukdc said:
Hi Muhamet,
Thats the version of TWRP I've already installed.
Is there another version that works with sideload adb?
If not, I'll try to use usb otg to transfer files instead.
Click to expand...
Click to collapse
if adb sideload isnt working it might b an issue with your pc/cable if its working for everyone else

muhamet said:
Multidisabler
Click to expand...
Click to collapse
I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
I can install stock again but what is solution to above problem later.
1. Is there a better disabler that works
2. Would installing custom ROM help?

lawmanukdc said:
I installed multi disabler and then magisk.
Rebooted twrp into official ROM.
Multi disabler didn't work.
On reboot, phone had KG prenormal again and refused to boot due to twrp installation.
I can install stock again but what is solution to above problem later.
1. Is there a better disabler that works
2. Would installing custom ROM help?
Click to expand...
Click to collapse
Just follow this:
Flash stock rom,enable USB DEBUG,boot stock recovery,wipe data factory reset,reboot bootloader,flash twrp (without magisk patch),boot twrp recovery,flash dm verity,flash rmm prenormal,flash multidisabler,FORMAT DATA,reboot recovery,mount system,advanced/file menager/system root/system scroll down and you will rename recovery-boot.p to recovery-boot.p.bak and reboot system now you will have twrp.For magisk you will need SHRP RECOVERY.Just contact me on telegram KI3IL3LMA i will send you all what you need.

Very helpful thanks
I've sent a pm to you

TWRP Recovery, Android 9 Pie

Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!

Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions

Yes, you are right. I just patched boot.img

thanks, it worked perfectly for me.

Thanks a lot, not a lot of development and love on this device, I just wanted to say some of us really appreciate this.

SaiLas said:
Warning! Warning! Warning!
All yours Data and files from internal storage will be lost. So make backup all what you need before continuing​
First read Bootloader Unlock and Root Instruction
So your bootloader is unlocked and you want TWRP-recovery on yours V35.
1. Download the necessary kernel
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
Boot+TWRPv3.3.1-V35-Pie-ULM20E.img - boot.img from V350ULM20e firmware
2. Flashing
a) Via Root: if you already have unlocked bootloader and root just copy downloaded f-or-e.img on internal sdcard, run CMD on PC and type
adb shell
su
dd if=/sdcard/_downloaded_.img of=/dev/block/bootdevice/by-name/boot_a
or
dd if=/sdcard/_downloaded_.img.img of=/dev/block/bootdevice/by-name/boot_b
reboot recovery
b) Via Qfil: all you need to know is here Bootloader Unlock and Root Instruction
3. Go to recovery ( via buttons or adb reboot recovery )
In recovery you will see a message that the data is encrypted and you need a password, which you not have.
Click cancel, agree to change system files.
In main menu click Install and select attached file Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
In Wipe menu swipe right, then go back, Format Data - type "yes"
Install latest Magisk.zip
Reboot - System
Done!
Click to expand...
Click to collapse
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?

What's the benefit without ROM's for rooting your phone? Magisk modules?

notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
Hey thanks!

X-Nemesis said:
What's the benefit without ROM's for rooting your phone? Magisk modules?
Click to expand...
Click to collapse
Yes. On my V30 I've never installed a custom ROM. Rooted stock firmware when the TWRP custom recovery (gift by itself for backups), Magisk mods, Xposed mods. You can tweak yourself without having to install a ROM.

During flashing, you may see error messages about 'unable to unmount vendor'. This is fine as long as the zip flashing doesn't fail halfway.
Click to expand...
Click to collapse
realllllllllllly important. I kept getting unable to mount xx (one of vendor system systemroot randomly) and didn't notice it meant the magisk sticked until I gave up and was ready to settle with no twrp.

YUP
notanymore said:
Can bootloader be unlocked on ATT V35 V350AWM I can't find it anywhere? There seems to be some talk it cannot be done?
Click to expand...
Click to collapse

SaiLas said:
Yes, you are right. I just patched boot.img
Click to expand...
Click to collapse
links dont work
Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware

SaiLas said:
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
Click to expand...
Click to collapse
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build

zfk110 said:
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.
Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
Click to expand...
Click to collapse

Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.

Excelstar said:
Did you wipe your data after flashing the files?
The same happened to me once, I solved that by flashing via upgrade the stock firmware, and then re-rooted.
Click to expand...
Click to collapse
I just went back to TWRP and used his boot.img to flash within TWRP to boot's partition and then I was able to boot without any issues, I was thinking the same, but it looked more work to do.

kaneorotar said:
Edit:
New Instructions in English: https://github.com/kaneorotar/LG-V35-Tinkering-Instructions/blob/master/README_EN.MD
Original:
I see that you are using my TWRP build.
Here is my original instructions (mainly in Chinese but has enough English to make sense): https://github.com/kaneorotar/LG-V35-Tinkering-Instructions
Click to expand...
Click to collapse
Just wanted to say thanks for the updated instructions. Worked like a charm.

Hello, can you help me with the TWRP file for the LG V350AWM?

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you