[Google Pixel 2 XL Guides, News, & Discussion] drumst1x:
I've had my phone rooted with Magisk for years. First time I'm stuck. Hoping someone can help me.

Was on Android 10 with Magisk.

1. `adb reboot bootloader`

2. `flash-all.bat` (I removed the `-w` from the file, attempting to NOT have to wipe)

3. Let it reboot and settle (finish the "installing pixel" or whatever notifications come up)

4. `adb reboot bootloader`

5a. (First time here I made a mistake: `fastboot boot twrp-installer.zip` (using 3.4.0-1)

- rebooted back to bootloader / I realized I made a mistake

5b. (correctly this time) `fastboot boot twrp.img`

6. typed in my pin and successfully decrypted

7. install -> twrp-installer.zip

8. reboot to system

9. Uninstall magisk manager real release (20.4)

10. Install magisk manager canary (confirm on Canary release channel)

11. "install" magisk (this downloads `Magisk-e66b0bf3(20425).zip`)

12. `adb reboot recovery`

13. install magisk.zip

14. reboot system

In the last step above, I attempt to reboot to system. I see the "bootloader is unlocked - power to pause" warning screen, then the Google logo for a split second, then it goes right back into the bootloader. No matter how many times I try to restart to system from bootloader and/or go into recover then into system, i keep ending up back at the bootloader when I restart.

After my misfire in step 5a, I never re-flashed the entire image, just re-"boot"ed into twrp.img.

In line with what some people have mentioned here, I saw that I had some modules installed from older magisk. I think there were 3 (magiskHidePropsFolder, Busybox, and something else I can't remember). In hopes that this would fix my issues as well, I rebooted into recovery, and using advanced -> file manager deleted /data/adb/modules (all 3 of those folders), then reinstalled magisk from Recovery and rebooted (saw this method in another thread). Same thing, ended up at Bootloader.

Something I noticed each time I tried flashing (either twrp or magisk) from recovery -- after the flash completes, it says "Updating partition details...". I get 2 lines in red:

Failed to mount '/system_root' (Invalid argument)

Failed to mount '/vendor' (Device or resource busy)

I've seen in the past that an error mounting /system is a common thing to see as of Android 10, but that it doesn't affect anything. Unsure if the same is true for these two above messages, or if those can possibly lead me to some hint about solving this?

I'm really trying to avoid removing the -w and trying it all again ... as a last resort I'd do that, but I'd really like to try to see if there's somethign else I can try first to get this working without the wipe.

Also a note: everything works FINE in android 11 right now, it's just I have no root. So I don't know if a bad USB cable or anything could be the cause of this. Magisk and Magisk Manager were both downloaded directly from the phone itself (no USB cable at all). And since Android works fine....?

Thanks in advance, everyone!

**edit** if it helps, here are my fastboot and adb versions:

adb:

Android Debug Bridge version 1.0.41

Version 30.0.4-6686687

fastboot:

fastboot version 30.0.4-6686687