Database Users

[Mini Guide] How to root 8.1

The current version of TWRP will not accept your pin/password on 8.1. Until we get an update to TWRP there are a couple of work arounds.
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
The other option is to get a thumb drive and a USB to C adapter from Best Buy or elsewhere. Put SU on the thumb drive, boot to TWRP img with fastboot as you normally do and then plug in the thumb drive to the phone. In twrp you will see an option to select storage, select the OTG USB Drive and you can install SU from there.

Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it

two_cents said:
Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it
Click to expand...
Click to collapse
Lol, you are right. Forgot all about that. Now I have two.

Fyi, just took the ota to Android 8.1 beta on my stock Pixel and Magisk 14.3 survived. Now have 8.1 rooted and all my modules up and running:laugh::good
Sent from my Google Pixel using XDA Labs

Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.

Alaadragonfire said:
Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.
Click to expand...
Click to collapse
I seems rock solid to me, and not seeing any major complaints.

Before I update can anyone confirm if ARISE will run on this?

quinejh said:
Before I update can anyone confirm if ARISE will run on this?
Click to expand...
Click to collapse
NVM I figured it out!! Lol

What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.

mflow said:
What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.
Click to expand...
Click to collapse
What version of Magisk are you using? I'm on 14.0 rather than 14.3.

ss4rob said:
What version of Magisk are you using? I'm on 14.0 rather than 14.3.
Click to expand...
Click to collapse
i'm on 14.3 now, i haven't tried 14.0 yet but i got problems with 14.0 on Android 8.0, so i moved to the beta channel.

Black crush
Would anyone be willing to do a test for me?
Can you restore the stock boot image, boot to system then look at the top right corner of this wallpaper with brightness on high, and in a dim room. You should see banding like the middle phone in this picture.
Then root with SR5-SuperSU-v2.82-SR5-20171001224502.zip and look at the same wallpaper. Let me know if the banding is gone and the transition is as smooth as the right phone in the picture.
You have to do the steps exactly as laid out, though. Having a modified boot image before flashing SuperSU does not produce this result, and neither does being on 8.0 or 7.1.2. It only happened in 8.1, and only after I flashed this SuperSU over the stock boot image...Magisk did not do the same thing.

Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?

bbs3223474 said:
Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?
Click to expand...
Click to collapse
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101

sliding_billy said:
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.

I used Magisk 14.5 (1456) to root the Pixel with no issues. I left SuperSU on the XL, and might put it back on the Pixel when the issue is resolved.
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
bbs3223474 said:
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.
Click to expand...
Click to collapse
Try Magisk.

I've successfully rooted 8.1 by following steps:
1. boot into TWRP 3.1.1-1
2. install the latest Magisk 14.5 zip from external storage (DOK)
without wipe and/or installing twrp installer

Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?

pavanmaverick said:
Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?
Click to expand...
Click to collapse
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.

phaino00 said:
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.
Click to expand...
Click to collapse
Huh! It didn't work for me when I tried it. It seemed to uninstall, but on rebooting, all the apps were still there. Is that not the case for you? Also, do you have a list of the apps you uninstalled?
Thanks.

Installed TWRP, no access to sdcard

I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.

Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.

hartleyshc said:
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
Click to expand...
Click to collapse
Thank you for your quick reply!
Is it bad that it is already flashed permanent? Or do I need to flash original recovery again?
I'll try and sideload it. Haven't done that before.

bokkoman said:
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Click to expand...
Click to collapse
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.

Funk Wizard said:
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Click to expand...
Click to collapse
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?

bokkoman said:
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
Click to expand...
Click to collapse
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:

Funk Wizard said:
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Click to expand...
Click to collapse
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.

bokkoman said:
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
Click to expand...
Click to collapse
As and when the update comes, just let the system download and install the zip. It will auto download and install the full zip when it detects root/system modifications, just make sure you uninstall/deactivate all mods/magisk modules/ substratum overlays before you update. You can check for easy instruction on the third post of the update thread. I will update the thread as and when the OTA is released.
Also you guessed it right the update will unroot the device so you have to root it again so you can either do the same sideload way or just do it from the magisk manager - uninstall - install ota (do not reboot) - install magisk to second slot - reboot :good:
I will again update the detailed instructions for easy understanding and and when we have the update :good:
Just stay subscribed to the update thread :good:

P2XL OTA + Magisk install before reboot = keep root

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

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

Anybody know if this worked smoothly with their Viper4Android app?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Android 10 and root?

I'm on Android 10. I unlocked the bootloader.. easy.. I downloaded the corresponding file for my device, software channel, version. Ran the boot img through magisk manager. So I have the patched boot img. Before I go further with trying to flash it through fastboot, I was wondering would this successfully root my device? I'm hesitant because I haven't came across anyone discussing there success in doing this with Android 10. I really don't want to proceed until I know I'm ok to go ahead. Thoughts?

Install Twrp, flash Magisk latest zip through twrp, done

HueyT said:
Install Twrp, flash Magisk latest zip through twrp, done
Click to expand...
Click to collapse
Sorry to butt in but that did not work for me. Rooting with magisk removed my installed twrp. Could that be a bug in android 10 or latest magisk?

fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery

HueyT said:
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
Click to expand...
Click to collapse
I was busy with other things and only just came back to this topic. I agree with you, HueyT, Magisk rooting
(which I do according to the Magisk directions which say to patch the boot.img and then flash it)
should not remove the permanent twrp installation on my phone. But it does
remove it on my phone! I've tried it repeatedly.
What I end up with is a rooted Moto G7 running android 10 and when I :
—power off completely
—volume down + power takes me to the stock recovery (not twrp)
—in that stock recovery if I go to the 'recovery' option I get the open android with red exclamation mark. Happens every time.
—long power hold then reboots phone to rooted android 10.
What I have not tried yet is to permanently install twrp again and then, in twrp install Magisk 23 zip. Maybe that will allow me to keep twrp installed.
Do you think so?
It is just frustrating because this is my main phone and I can't afford to mess it up.
Any other suggestions on how to keep twrp installed on the Magisk rooted phone greatly appreciated.
Thanks for replying.

Definitely

HueyT said:
Definitely
Click to expand...
Click to collapse
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?

Definitely

HueyT said:
Definitely
Click to expand...
Click to collapse
A man of few words...

Yep

maybeme2 said:
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Click to expand...
Click to collapse
That worked.
Rooting by installing Magisk.zip from within TWRP allowed me to both root and retain the TWRP installation.
Thank you HueyT.

NP

It's been two years but I did try injecting Magisk from within TWRP. I've also downloaded "factory" images and rooted those, them installed them. If I remember right, I did the injection method with this G7. It's the best way IMHO because the installed image is tailored your your device.
Over the last two years, the Pie around here has been fantastic.

shadow460 said:
Over the last two years, the Pie around here has been fantastic.
Click to expand...
Click to collapse
You can say that again. I've had several system crashes with 10, something I've never had with pie. Even after clearing cache, updating all apps, etc. So has my wife on her own unrooted G7 which just accepted Moto's own ota update to 10.
I do have a TWRP nandroid backup that I did just before flashing 10 and I've often considered going back to pie. But I worry about 'something' else going wrong like it did when moving to 10. It's my main phone and I can't afford to go through all I went through moving to a rooted 10. Wish I hadn't bothered.

Android 11 is live.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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