Don't flash Magisk 17.0+ ***on STOCK ROM***

[rzarectha]

Updated OP since this thread became useful to track if magisk works with our stock ROM.

The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.

I suggest that you change the update channel to custom and set the address to 127.0.0.1

For the most recent Magisk version:

I tested 19.3 on B01 oreo and it still bootloop.

Thanks for checking @mickey36736

 

[raystef66]

It bootloops

I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.

 

[rzarectha]

I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.

mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build

update: it bootloops on stock no matter what channel (stable/beta) you get it from.

I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.

 

[Oki]

mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build

update: it bootloops on stock no matter what channel (stable/beta) you get it from.

I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.

You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.

 

[Prophet 5]

Not only on stock...

I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.

 

[rzarectha]

I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.

use the uninstaller zip first

 

[koftheworld]

Try 17.1. supposedly solves the bootloops.

 

[trevor68]

bootloops are easily fixed by using the uninstaller first.

 

[KwesiJnr]

Try 17.1. supposedly solves the bootloops.

Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7

 

[koftheworld]

Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7

You have to use the uninstaller first and then flash 17.1.

 

[pnin]

Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:

 

[koftheworld]

Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:

Did you use the magisk uninstaller? If not, just reflash your bootloader

 

[marcdw]

Did you use the magisk uninstaller? If not, just reflash your bootloader

Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.

That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]

Dark ROM. FTW. [emoji41]



ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy

 

[pnin]

I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).

Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...

I have even had to restore recovery through fastboot mode now. :silly:

 

[amphi66]

I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors

 

[DrakenFX]

Using stock anything above and v17.0 will bootloop using stock,

Just my 2cents, if that your issue just do the following:

-Download v16.7 first in case you don't have it yet, and move it to the SDCard.

* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.

 

[marcdw]

Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...

I have even had to restore recovery through fastboot mode now. :silly:

Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...

/data/magisk
/data/magisk.img
and files in /data/adb/

Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.


Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy

 

[pnin]

So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).

Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).

I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.

 

[christoophat]

So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).

Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).

I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.

I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.

 

[rzarectha]

New beta version released. Still bootloop