Should I update to Magisk 25.2 after flashing 24.3

[Curstantine]

According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385

Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.

Should I continue? Since this is after the fact?

 

[Fredin_]

Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.

So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.

 

[Curstantine]

Alright, I'll update the thread if everything goes well.
Thank you!

 

[Curstantine]

Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.

Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.

 

[newt23]

I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.

Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.

 

[OldNoobOne]

I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.

Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.

Greetings Friend,
Can you attach the Dmverity Disabler zip?

 

[newt23]

Greetings Friend,
Can you attach the Dmverity Disabler zip?

 

[OldNoobOne]

Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?