Develop Bugs

Boot-To-Root Boot-Loop

My setup
Pixel XL from Verizon
Bootloader unlocked
Bootloader Version 8996-0121001-1611091517
Baseband 8996-012511-1611190200
Android 7.1.1 NOF26V
Kernal 3.18.31-g367e645 Dec 7, 23, 2016
Twrp Version 3.0.2.0 RC1
I have tried following this guide to get root access https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
My steps are
1. boot phone into fastboot
2. from pc run fastboot boot boot-to-root.img
3. the phone reboots
4. Phone is stuck with the 4 colored dots jumping over each other
5. i've given this screen up to 30 minutes with no results.
6. Forcing a reboot causes the same issue
7. Flash stock android via the official google factory image method
I have attempted this other method as well http://www.theandroidsoul.com/root-pixel-xl-magisk/
But after TWRP says it's successful, i boot into my OS and there is no supersu and if i manually install supersu, it says no root access.

You are doing it the old way that was for 7.1.
You want SU 2.79 SR3
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
And you want TWRP RC1.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
I would not install TWRP at this point. So copy SU to your phone. Then boot to TWRP.
Fastboot BOOT twrp.img
With twrp.img being the correct name of the file. Then in TWRP install the SU you copied.

The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?

Larzzzz82 said:
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Click to expand...
Click to collapse
You boot it, always.
If you want to install it you copy the twrp ZIP to the phone. Boot it with the TWRP image file then install the twrp zip from within twrp.
Gotta be done that way. Partition layout has changes, they are a bit intertwined now.
I dont install TWRP anymore.

That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.

Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
That might be doable, I am not a ROM guy. Root and kernel only....and I always got a PC.

so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.

steber04 said:
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
Click to expand...
Click to collapse
Exactly.

Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
You don't need a PC if you just install TWRP.

TonikJDK said:
Exactly.
Click to expand...
Click to collapse
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?

steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
What files are you pushing that you cannot just load directly with the device powered up?

steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
You will need fastboot, so you can fastboot boot twrp. I don't push the SU zip with adb, I just copy/download it to the phone before I reboot into Fastboot. Make sure you get Fastboot from Google, not the Minimal one.
https://developer.android.com/studio/releases/platform-tools.html

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result

Guide to root motorola g stylus

QUICK STEPS TO ROOT MOTOROLA MOTO G STYLUS USING MAGISK
Just Remember*I just want to warn you that, Rooting will void the warranty of your smartphone
Rooting will block the OTA updates
1.First of all, please download and extract the ROM on your computer.
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
2:*Now, connect your moto g stylus with a micro USB cable, and copy only the boot.img file from the extracted folder to your Motorola moto g stylus device storage/memory.
3:*Now you need to Launch Magisk Manager.
4:*After that, you will see a popup window that will ask you to install Magisk.
5:*Finally please select INSTALL and choose to install it again.
6:*Now Please press on “Patch Boot Image File
7:*Navigate to internal storage and select your phone’s boot image that you transferred earlier.
8:*Wait for a couple of seconds. Magisk will start patching the boot image.
9:*Once the boot image has been patched, copy the “patched_boot.img” from the internal storage and replace it in the same extracted ROM folder on your PC.
10:*Now you can follow the second step to flash the patched boot image file.
Next, you need to enter the following commands step by step:
First of all, you need to Flash the “patched_boot.img” to install Magisk and root your Motorola moto g stylus: fastboot flash boot patched_boot.img
You can also use the devices with A/B partition system, with the following commands:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
After that, you need to replace [patched_boot.img] with the same boot image file that you have already downloaded with the .img.
Now you will see the flashing process have has started. Now, run fastboot and reboot
HOW TO VERIFY IF YOUR MOTOROLA MOTO G STYLUS HAS A SYSTEMLESS ROOT?
Download and install the Magisk Manager app APK, and launch it.
If you want to verify that you have a systemless root, check the top of the screen and if you see all options with Green Tick which means you have successfully rooted and bypassed SafetyNet.
Sent from my moto g stylus using Tapatalk

surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.

It definitely works for the metro by TMobile version.

himesh82 said:
surprised to see no comments on this topic. I am thinking of getting this phone but only if there is a root method for it.
Click to expand...
Click to collapse
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.

dafunk60 said:
I got root by using magisk to patch the boot image. I purchased the phone directly from Motorola's website. If you get a version where the bootloader can be unlocked (some carrier versions apparently cannot be unlocked) you can root without much trouble.
Click to expand...
Click to collapse
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.

himesh82 said:
I am based in Uk and will order from their website.
How easy it is to use as It has been afew years i tried rooting and will need a super easy guide.
Click to expand...
Click to collapse
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.

Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed.
Still confused regarding your points
1 - where can i find the boot.img
2 - how do you patch using magisk
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Thank you
dafunk60 said:
I found it to be super easy using magisk, provided you have a PC to flash the patched boot.img to the phone via fastboot. I use the Lenovo Rescue & Smart Assist software on the PC to download the ROM from Motorola. You need to ensure the ROM you're downloading is the same version running on your phone. Using a boot.img from a different version will cause issues.
1. Copy the boot.img to the phone.
2. On the phone, patch the boot.img you just copied over with Magisk Manager.
3. Copy the patched magisk_patched.img back to your PC.
4. Connect to the phone via adb. (There's an adb.exe in the Lenovo Rescue & Smart Assist install directory "C:\Program Files (x86)\Rescue and Smart Assistant".)
5 . Reboot the phone to the bootloader with the following command on the PC:
Code:
adb reboot bootloader
6. Flash the patched boot image with the following command on the PC:
Code:
fastboot flash boot magisk_patched.img
7. Reboot the phone with the following command on the PC:
Code:
fastboot reboot
Once rebooted you can use Magisk Manager to hide root, check the SafetyNet status, etc.
Click to expand...
Click to collapse

himesh82 said:
Thank you for your help on this. I rooted my moto x4 long time ago and the process has definately changed......
Thank you
Click to expand...
Click to collapse
You're welcome.
himesh82 said:
1 - where can i find the boot.img
Click to expand...
Click to collapse
In the Lenovo software you can choose a download location. The default appears to be "C:\ProgramData\LMSA\Download". In that directory you'll see a "RomFiles" folder which contains folders for the different ROM versions it has downloaded. SOFIAP_RETAIL_QPR30.80_58_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml or SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml for example. You can find the boot.img file within those folders.
The QPRD30.80_58_3 boot.img file is located in "C:\ProgramData\LMSA\Download\RomFiles\SOFIAP_RETAIL_QPRS30.80_58_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Some people share links to the ROM files but I prefer to get mine from Motorola.
himesh82 said:
2 - how do you patch using magisk
Click to expand...
Click to collapse
Google's your friend on this topic, https://www.xda-developers.com/how-to-use-magisk/
himesh82 said:
Also do you not need to unlock boot loader and bypass the verification and why do you need to hide root after?
Click to expand...
Click to collapse
You do need to unlock the bootloader, unless you have the private key Motorola uses to sign images . Just follow the instructions on the Motorola website. Unlocking the bootloader & rooting are two separate things. You need to unlock the bootloader to allow the hardware to boot unsigned images, such as a patched boot image. Root provides applications root access to the Android OS.
You typically want to hide root as some apps won't function if they detect root, mostly banking & video streaming services I believe. It's not a requirement however.

Thank you again. I will take a good look at the guide and then decide if it is something that I can attempt

Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help

Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Does rooting wipe all the user data and apps?

nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
---------- Post added at 06:43 PM ---------- Previous post was at 06:37 PM ----------
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
I honestly don't know. When I did the steps from op I unlocked the bootloader then rooted. I never booted into system. I can't check now because I'm running havoc os gsi and the op method doesn't work on gsis. I tried and it didn't boot but when I flashed the stock boot.img all my setup was still the same. Hope that helps some.

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Do you have a carrier model? You might be flashing the wrong boot.img although I'm not sure if theres anything different between then

No I bought the unlocked model from best buy cuz I know carrier models usually aren't rootable. Can some one post a link to the right boot.img
Here is my build number QPRS30.80-58-3 and my device info is in the pic TIA for any help

nokia4life2017 said:
Wait DOES THIS WIPE ALL THE DATA?? I CANT get a clear answer. Supposedly the "official" unlocking through Motorola does but this is the Magisk method and I'm hoping it doesn't wipe the user data or apps.
Also how do you root AFTER you unlock the bootloader?
Does rooting wipe all the user data and apps?
Click to expand...
Click to collapse
There are instructions on rooting in these forums, even in this thread.
Unlocking the bootloader forces user data to be wiped (aka factory reset).
Rooting with Magisk does not wipe user data.
Unlocking the bootloader and rooting are two separate things. Unlocking the bootloader allows unsigned images, such as a modified boot.img, to be run on the device. Rooting provides applications root level access to the Android OS.
---------- Post added at 02:19 AM ---------- Previous post was at 02:10 AM ----------
Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
It sounds like the boot image you're flashing does not match the version of the ROM on the phone. From your subsequent post, it looks like you're running QPRS30.80-58-3. Where did you get the boot.img file that you patched? You can use the Lenovo Rescue software to download the ROM files right from Motorola. These will contain the entire ROM, including the original boot image. Details are in the posts preceding yours. Flash the original boot.img & see if the phone boots. If it does, patch that image with Magisk & flash to obtain root.

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
Try fastboot flash boot boot.img. When i did the stot a and b method i lost touchscreen etc
I bought a second stylus and the root method is different. So I fastboot flash the image (not to slots) and it worked but when the screen goes off the touch screen isn't responding.

I got it to work by using the assistant mentioned above. And using the fastboot flash magisk_patched.img or fastboot flash boot magisk_patched.img I can't remember which one at the moment but it automatically flashed both A and B slots with no problems. Also is TWRP available for the G Stylus?

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
i just had the same thing happen to me. But i went to the assistant software and tried to rescue my device and it failed. Did you get it to work and how exactly did you get it working?
Edit: I just got it rescued and Im back up and running. Now I just need to figure out how not to repeat whatever mistake I just made and to get my device rooted. Did you ever figure out what you did wrong?

JimmyJurner said:
It definitely works for the metro by TMobile version.
Click to expand...
Click to collapse
Without unlocking the Bootloader?
*edit*
Cancel that, Just Unlocked my MetroPCS Moto G Stylus's Bootloader
*edit* *edit*
FYI : There is a new build for the RETAIL Channel from 7/21 : mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/

Growking99 said:
Can someone help me idk what I'm doing wrong but when doing the steps mentioned above boot b is flashed automatically and when my phone reboots I have no service, my screen doesn't work, it hangs for minutes at a time and randomly reboots. Please help
Click to expand...
Click to collapse
I am having the same issue while in fastboot, the device reboots bootloader every 20-30 seconds. I had to wait till the screen went off before hitting enter to get OEM Get_unlock_code.

[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

Question Just want to start over!!

Ok so im a little frustrated and hope someone can put me in the right direction. My first mistake was flashing the wrong build. I was rooted on the nov build and flashed The decmber update but i flashed the US build and got a bootloop.(i have the Canadian variant). then i flashed a magisk patched boot image not realizing i had installed the wrong build and of course that wouldnt boot. Luckily i could still acess fastboot so i flashed the correct build without erasing data and boom it booted. yippee right? So then i patched the boot.img with the correct canary build of magisk and then adb reboot fastboot followed with fastboot flash boot and the patched img. but im back to a bootloop. So I flash the original boot.img and im back but no root. My brain is now mush!!! i need someone to hold my hand and tell me how to just clean slate everything and reoot.

wulfgarfang said:
Ok so im a little frustrated and hope someone can put me in the right direction. My first mistake was flashing the wrong build. I was rooted on the nov build and flashed The decmber update but i flashed the US build and got a bootloop.(i have the Canadian variant). then i flashed a magisk patched boot image not realizing i had installed the wrong build and of course that wouldnt boot. Luckily i could still acess fastboot so i flashed the correct build without erasing data and boom it booted. yippee right? So then i patched the boot.img with the correct canary build of magisk and then adb reboot fastboot followed with fastboot flash boot and the patched img. but im back to a bootloop. So I flash the original boot.img and im back but no root. My brain is now mush!!! i need someone to hold my hand and tell me how to just clean slate everything and reoot.
Click to expand...
Click to collapse
Deactivate your magisk modules. I had a bootloop because of a mod by tulsadiver

P6P said:
Deactivate your magisk modules. I had a bootloop because of a mod by tulsadiver
Click to expand...
Click to collapse
sorry im not in a bootloop. i reflashed the boot.img and im back but a patched boot img wont work i get a bootloop.

wulfgarfang said:
sorry im not in a bootloop. i reflashed the boot.img and im back but a patched boot img wont work i get a bootloop.
Click to expand...
Click to collapse
Yes i know. But when you flash a patched boot.img your modules will be activated automatically. On stock boot.img they're deactivated because of missing magisk.

That sounds awesome but how can i deactivate the modules if i cant access them?

wulfgarfang said:
That sounds awesome but how can i deactivate the modules if i cant access them?
Click to expand...
Click to collapse
Dunno if there is an easier way but I did:
1. Flash patched boot.img
2. Turn off device
3. "adb wait-for-device shell magisk --remove-modules"
4. Connect your phone to computer and turn it on.
5. Phone tries to boot and the command should be accepted
6. Wait until the command worked and the phone boots up without issues

P6P said:
Dunno if there is an easier way but I did:
1. Flash patched boot.img
2. Turn off device
3. "adb wait-for-device shell magisk --remove-modules"
4. Connect your phone to computer and turn it on.
5. Phone tries to boot and the command should be accepted
6. Wait until the command worked and the phone boots up without issues
Click to expand...
Click to collapse
P6P said:
Yes i know. But when you flash a patched boot.img your modules will be activated automatically. On stock boot.img they're deactivated because of missing magisk.
Click to expand...
Click to collapse
My god man! Thank you so much. I could not do it as outlined above but I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.

wulfgarfang said:
My god man! Thank you so much. I could not do it as outlined above but I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.
Click to expand...
Click to collapse
I'm glad to help.

Step 1: Long press the power key until the Google logo appears on your Pixel.
Step 2: When the Google logo disappear & the animation starts, press & hold the volume down button until your phone boot into safe mode.
Step 3: You can see safe mode at the bottom left corner.
This will disable all magisk modules and then reboot

Solved....thanks everyone! I did it through safe mode and it worked im rooted again. And i also had the tulsadiver mod. I never thought about a module causing the issue until you mentioned it. Thank you again.....I dont have to start over. Two days of thinking and annoying my wife is over.