Should I update to Magisk 25.2 after flashing 24.3

Search This thread

Curstantine

Member
Mar 24, 2023
7
0
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?

1679809141789.png
 

Fredin_

Senior Member
Feb 19, 2018
306
80
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

Member
Mar 24, 2023
7
0
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.
 
Last edited:

newt23

Member
Oct 6, 2021
20
4
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.
 
  • Like
Reactions: OldNoobOne

OldNoobOne

Senior Member
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?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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.
  • 1
    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.