Magisk: bootloop on magisk 17

[achozex]

device oneplus 3t
android 8.0
the latest beta was working perfectly

log :
https://drive.google.com/open?id=1ZAlSYL47wsekpJrdHQ9AuFIykR3Top4C

[sqdesign]

Same here on Oneplus 3 RR official nougat 7.1.2 build final.

[bogdan-radocea]

Same on pixel xl with android 9.

[mihirhpanchal]

same on mi A1 stock oreo 8.1

[evacakh]

Same on Samsung Galaxy A3 (2017) stock Nougat
Edit: I was able to fix it using the Patch Boot Image File method
Edit_2: Magisk is not recognized as installed in TWRP; when I try to uninstall magisk or flash Magisk modules

[bogdan-radocea]

I was able to install the latest magisk after using the magisk uninstaller.
Steps that should work:
1) flash-all.sh (flash-all.bat for windows) REMEMBER TO REMOVE THE -w FROM THE flash-all SCRIPT!!!
2) let the phone boot fully.
3) disable any lockscreen security (fingerprint, pattern, pin, etc.)
4) boot the twrp img file (latest is from 30 august 2018) using fastboot boot twrp-3.2.3-1-marlin.img
5) install the Magisk uninstaller zip from recovery
6) reboot the phone and let it fully boot.
7) boot the twrp img file (latest is from 30 august 2018)
8) install the twrp installer zip, reboot the phone and let it fully boot.
9) reboot to recovery and install the Magisk v17.0 zip file
10) reboot the phone and let it fully boot.
11) the phone should boot normally.
12) install the latest Magisk manager

[Wandang]

Just for the sake of completeness: Same on HTC 10

[bogdan-radocea]

Well, the issue is that you need the magisk uninstaller, even if you do a full flash (dirty)/upgrade over the older version. The v16.0 worked just fine in the past, but now it seems that v17.0 corrupts the system or boot partition somehow.

[Skimige]

Same on Mi 6 with MIUI 10 Stable (Android 8.0).

[Larpon]

Same on Pixel 1. Can someone please guide a complete beginner with Magisk how they recover from this?

[a-xin]

Related thread on xda: Bootloop after magisk update

[Skimige]

Maybe a way to temporarily out:

1. Go to your recovery.
2. Flash Magisk uninstaller (Backup your modules!), then reboot. Your device should boot normally without root & modules. If not, find your stock boot.img then flash it.
3. Remove all lockscreen security.
4. Reboot to recovery, flash Magisk v17.0
5. Reset lockscreen security & your modules.

[Larpon]

Got my Pixel working again with no fuzz following the Linux instructions from Bootloop after magisk update

Using twrp image from twrp-pixel-installer-sailfish-3.2.3-0.zip and the downloads from the releases in this repo

Thanks guys!

[Jviix]

Had the same issue, just uninstall Magisk with Magisk uninstaller and then install Magisk 17, also clean cache & Dalvik

[topjohnwu]

Fixed in ff3dad245721c7d01f2c4772c700dafbc6ba9ef9

[mikehardy]

@topjohnwu Resolved but it looks from the patch that anyone who installed MagiskManager v5.9.0 prior to installing Magisk v17 will need to uninstall then install cleanly, yes? Or does Magisk v17.1 install cleanly over Magisk v16 even if MagiskManager v5.9.0 was installed first?

[Crescendo-BLYAT]

1. Remove all lockscreen security.

why remove the lockscreen security?