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

[SkaboXD]

Thanks for warning us, i was close to flash it.

 

[greyhamism]

Any updates to this?

Currently on 16.6, and most of my modules need 17+ to update. On the Oreo B12 Beta.

Cheers

 

[kraljan66]

Hi all....today I made update of MAGIS(probably to 17...i´m not sure nr of version) and now has a bootloop...problem is I can not get to TWRP!....I see only boot logo, then restart and boot logo again = after that 3x red led....
I was on Nugat b12 this rom: https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3842931
any idea?

hehe it looks like DFU brick....fck brick after magisk update....fck fck.

 

[Predatorhaze]

Hi all....today I made update of MAGIS(probably to 17...i´m not sure nr of version) and now has a bootloop...problem is I can not get to TWRP!....I see only boot logo, then restart and boot logo again = after that 3x red led....
I was on Nugat b12 this rom: https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3842931
any idea?

hehe it looks like DFU brick....fck brick after magisk update....fck fck.

i dont even understand why you update magiks on that rom.Ray even mentioned only 1 magisk works.
Maybe you should try instal twrp again trough EDL or something (edltool)
i believe this is not really a brick,can be solved trough edl.But maybe im wrong

 

[kraljan66]

At the moment have only win10 or linux...and have a problem with qualcom driver...so will taste it with my old PC WIN7....so we will see...

 

[GodOfPsychos]

I just remembered, this bootloop issue also happened for some pixel devices on magisk v17 (or higher). It was once in the xda news (sadly i can't seem to find the article). In the news it stated that topjohnwu fixed that issue in the canary builds. Maybe you can try out those. Just beware that they can be unstable.

Here is the official thread to the canary channel:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

How to add the canary channel to magisk:
In the official thread click on release channel and copy the browser browser url (https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json)
Now go into magisk settings and go to update channel. Change it to custom and paste the copied url there.

Idk if it works or not. But in case something happens, there is also a canary uninstaller linked in the canary channel thread

 

[rzarectha]

I just remembered, this bootloop issue also happened for some pixel devices on magisk v17 (or higher). It was once in the xda news (sadly i can't seem to find the article). In the news it stated that topjohnwu fixed that issue in the canary builds. Maybe you can try out those. Just beware that they can be unstable.

Here is the official thread to the canary channel:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

How to add the canary channel to magisk:
In the official thread click on release channel and copy the browser browser url (https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json)
Now go into magisk settings and go to update channel. Change it to custom and paste the copied url there.

Idk if it works or not. But in case something happens, there is also a canary uninstaller linked in the canary channel thread

Thanks a lot for the tip.

I flashed it on B02, unfortunately it has the same behavior. Boots up to the "your software is corrupted" screen then reboots. Over and over.

It's good it's being looked into though, let's hope!

 

[Dodgexander]

Guys please take the time to note you also have the issue to try and get it fixed:
https://github.com/topjohnwu/Magisk/issues/729

https://github.com/topjohnwu/Magisk/issues/758

 

[bluenote73]

Guys please take the time to note you also have the issue to try and get it fixed:
https://github.com/topjohnwu/Magisk/issues/729

https://github.com/topjohnwu/Magisk/issues/758

18.x is out, have you tried it? I'm lazy and hoping to save myself the trouble of finding out it doesn't work.

 

[jeboo]

18.x is out, have you tried it? I'm lazy and hoping to save myself the trouble of finding out it doesn't work.

Magisk 18.0 still bootloops with stock B20 kernel. However, it works fine with the custom asder kernel.

 

[dodo34]

Magisk 18.0 does not work with A2017G Stock Rom Oreo. Any solution ?

 

[klałn]

Magisk 18.0 does not work with A2017G Stock Rom Oreo. Any solution ?

To use Magisk 17.0+, use modified kernel by asderdd.
It works on latest B19(A2017) and B03(A2017G) ROMs.

 

[dodo34]

That is for US Modell and stability is questionable.

 

[Dodgexander]

18.x is out, have you tried it? I'm lazy and hoping to save myself the trouble of finding out it doesn't work.

It doesn't work and the issue remains open on GitHub.

 

[garryb]

Magisk 18.0 still bootloops with stock B20 kernel. However, it works fine with the custom asder kernel.

hey how are you? sorry guys to bump up this post @jeboo
please do you use discord i need your help with aboot on a samsung j415fn if you can message me back here i would really appreciate the help.

 

[rzarectha]

Hello guys! Magisk 19.1 Stable is out now.
Anyone had the chance to test it on stock? I would but I'm at work and I don't have access to a PC with adb

 

[Predatorhaze]

That is for US Modell and stability is questionable.

not true

 

[rzarectha]

not true

I revived the thread because it's relevant for us to discuss if Magisk 17+ is now viable on our stock ROMs.

Thanks for your contribution. You started to argue with a post 228 days old.

 

[rzarectha]

I will answer my own question. Unfortunately, the latest stable magisk is causing a bootloop for oreo b03

 

[joaocandeias]

I will answer my own question. Unfortunately, the latest stable magisk is causing a bootloop for oreo b03

Thanks for the feedback! I was about to update magisk