Question Magisk Update doesn't run very well :(

[Fre$h]

Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build

Fastboot mode doesn't report any bootloader version nor baseband version.

What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?

 

[Fre$h]

Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly

 

[djsubterrain]

It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.

I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.

 

[Fre$h]

For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?

Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^

 

[djsubterrain]

For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?

Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^

I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.

I'm not using any Magisk modules though, not going to risk that until we have a good recovery.

 

[djsubterrain]

Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use

I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either

 

[Shooter7889]

I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either

Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now

 

[netgar]

All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.

 

[Fre$h]

First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.

My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update

 

[netgar]

First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.

My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update

Thx bro...all good

 

[Fre$h]

This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.

Hope everything is now fixed