Magisk v26.2 Change Log Detailed and How to Update

preview_player
Показать описание
John Wu has released the first public beta of Magisk v26.2 so I can go over all of the changes and show you how to update.

~~~~~

Video Description
~~~~~~~~~~~~~~~~~
It's been a few months since John has released a new version of Magisk but now you can install or update to version 26.2. So today I'll be going over all of the new changes that went into it while also showing you how to update your Magisk install.

#android #googlepixel #samsunggalaxy #magisk #androidapp #androidapps

MagiskBoot can also directly handle AVB 1.0 signing with verification without having to do it via Java.

The socket for Magisk's Daemon now has a fixed path in MAGISKTMP.

ResetProp is another thing that received a bit of work with version 26.2 as it can now print property context. It also has the ability to only print persistent properties from its storage. And it can now properly set persistent properties that bypass property_service.

The MagiskSU binary now supports two different -g arguements, with it working as both a lowercase and an uppercase. And it has the ability to switch the mount namespace to PID with the -t option.

MagiskPolicy received a few changes with this update as well. John Wu was able to fix Magisk's ability to patch extended permissions while also adding support for more syntax for those extended permissions. It can now print out the loaded sepolicy rules as well.

Lastly, there has been some work done with the Magisk app too. With the changelog mentioning that it can now patch the boot image after loading in the full ROM zip file. This seems like a big feature that could change the way some people install or update their custom ROM files.

I could see this being useful with those who want to root their custom ROM update before installing it. . .rather than rooting the custom ROM again after the update has been installed.

These are the initial changes that are happening with version 26.2 of Magisk. John could do some additional work with this update before it gets pushed to the stable build, but these are the big changes happening right now.

This update is currently in open beta and you can try it out right now.

We can install this update on devices that are currently rooted by opening up the Magisk application.
Diving into the Settings area of the app
Making sure we're on the Beta channel here.
And then going back to the main page of the app.

You will see the prompt to update the application first.
And then we can update the actual binaries of Magisk that is currently installed.

And be sure to reboot when it's finished so the changes can actually go into effect.

If you don't have Magisk installed on your device yet. You can download this APK file for version 26.2 from GitHub and sideload it via a custom recovery like LOS recovery or TWRP.

I'll be sure to link to this page here for those who may not be familiar with where to download this update.
Version 26.2 of Magisk will likely stay in public beta for a week or two while John waits for the community to report any bugs they may have noticed.

It will then get pushed to the stable branch once he is confident there aren't any critical issues with it.

Mentioned Links
~~~~~

Step by Step Tutorial
~~~~~~~~~~~~~~~~~
1. Intro [00:00]
2.

As an Amazon associate, I may earn a commission on sales from the links below.

The Gear I Use
~~~~~~~~~~~~~~~~~
Рекомендации по теме
Комментарии
Автор

For my pixel devices i don't use root anymore but it's always usefull to have a place where we know we can grab the needed info. thanks a lot :)

eduardolopes
Автор

Worked like a charm on my 512GB Note 10+ 5G! Your clear, concise instructions are excellent. Thank you!

djshotty
Автор

Great video that show here. Do more of this! <3

TotalWarriorLegends
Автор

Hi! I have Magisk Module 23.0 installed on my phone for the past 2 years, I haven't updated it to latest version fearing it might affect my root and IMEI Patch. My question is, is it safe to update Magisk?

TheGreatLashari
Автор

"-Flashing new boot image
blockdev: /dev/block/mmcblk0p28: Permission denied
! /dev/block/mmcblk0p28 is read only
! Installation failed"

What could be the issue?

princek.
Автор

Brother, I have a boot burning or boot update problem without using TWRP, help.

mustafaeren
Автор

Do not update Magisk if your root is working perfectly fine and if your Zygisk and Ramdisk says NO, do not update

brandenwatkins
Автор

Could you explain (maybe through a tutorial video regarding) the first improvement 'MagiskBoot extracting boot.img from payload.bin'? How is this possible, how to do this?

hansssie
welcome to shbcf.ru