Latest LineageOS 15.1 release incompatible with Magisk

[Gynoid]

This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').

 

[simo6]

This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').

As a workaround if you flash a different kernel (i.e. Franco) prior to flash magisk everything working fine

 

[lihuihz]

the 0605 build also has the same issue. Is anyone has a solution for this trouble?

 

[choury]

I met the same issue, and I have to downgrade to 0521 with sideload.

 

[Gynoid]

Unfortunately the devs at Lineage don't seem to give a sh... about Magisk - I tried to raise the problem at their Reddit page, but my post and all subsequent users replies (people having the same issues) were deleted - and, true, LineageOS release 0605 still has that same issue. So the only solution If found is to root my Oneplus5 with LineageOS SU instead, but I still had a problem with the current release of Tasker which does not detect root when LineageOS SU is used. Luckily enough, the latest Tasker beta works fine with it.
So I'll live without Magisk for the moment.
Until I get rid of Lineage

 

[digger16309]

Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?

 

[Gynoid]

Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?

Unfortunately, the issue is still present in the 6/11 release, at least on my OP5 and most probably on OP5T as well. Regarding other kernels, I don't know and I will not start testing kernels - takes too much time.

 

[gurningchimp]

Unfortunately the devs at Lineage don't seem to give a sh... about Magisk

Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?

If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.

It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.

 

[Gynoid]

OK so just because it's free it should not be criticized? Is that your point? It should never make any progress? Well that's how "free" projects die. Hopefully their developers will be little more ambitious than that..

 

[batwingnz]

Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?

If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.

It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.

It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.

Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.

 

[gurningchimp]

It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.

Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.

I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:

 

[batwingnz]

I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:

Rooting it wouldn't help with that

 

[digger16309]

Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?

If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.

OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?

Using the food analogy...

A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.

Magisk has or is becoming the standard to root, isn't it?

 

[dragynbane222]

OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?

Using the food analogy...

A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.

Magisk has or is becoming the standard to root, isn't it?

You're thinking of SuperSU, lineage, for whatever reason, reinvented the wheel and rolled their own implementation.

 

[bisento]

OP5 Lineage 15.1 after 2018-05-21 results still in bootloader

the problem seems to persist - the last updates will always result in the device being stuck in the bootloader after flashing. I reversed the update by flashing the cheeseburger 2018-05-21-nightly over the latest (thank god for the working TWRP!) and it boots up normally. I checked up to 2018-06-11
How do we know if this is indeed a problem with Magisk (have v 16.0 installed)? Does somebody need more informations regarding the OP5 (cheeseburger) installs? Can I help in some way to resolve this problem (testing? log files?)
any hope for a resolve? The device works fine but I would like to be able to update regulary at least for security reasons (patched bugs)

 

[digger16309]

I installed LOS15.1 and I see it now. Was this also the case in previous versions, 13 and 14? I remember having to turn on root manually in LOS, then Cyanogenmod and flashing SU. But I think the developer of the custom 14.1 ROM I was using took it out of his ROM so I forgot all about it. Breaking Magisk is lame. I can manage without it, but I prefer the systemless Xposed option it provides.

 

[Dev-iL]

Did anyone try this with the LOS 20180618 build?

 

[Gynoid]

IMHO I don't see anything in the June 18 build changelog that would make me think it's gonna work any better than the previous builds. And on the Magisk side, there hasn't been any new release or beta for a while. So ...

 

[bisento]

Did anybody find a solution? Would upgrading Magisk 16.0 to 16.4 beta be worth a shot? How about deinstalling Magisk (via the deinstall-zip? or the deinstall option in the manager?) - would this enable the LOS update (as of today 2018-06-18-nightly)? And if yes, would it be safe to reinstall Magisk afterwards or is this door permamently closed?
I would give it a try myself but do not have a backup phone in case of bricking it and I need it for work... a report about a successful strategy would help a lot!

 

[Vanillezucker]

I flashed LineageOS 15.1-20180618-NIGHTLY-cheeseburger and Gapps Nano yesterday. After the reboot I installed the latest Magisk Manager.apk and flashed the latest sdk 27. I am now running LineageOS 15.1 with Magisk v16.0.
I didn't know about any problems there were before because this was the first time I flashed Lineage (had xXx - NoLimits). But I can't see any issues by now. It's working fine. I downloaded Youtube Vanced, Watchdogs Bootanimation and Xposed Framework (only gravitybox atm) which are all working.