Magisk Receives an Update to v12, Fixes Samsung Bugs, Adds Core Only Mode, and More

It’s been close to two months since the last big stable update was released for Magisk, and the developer actually received a lot of complaints about that update. At the time, Magisk Manager was at version 4.25 and it had begun crashing on a lot of Samsung devices. The issue was so widespread on Samsung devices that XDA Recognized Developer topjohnwu reached out to the community to ask for help regarding the issue. Thanks to the community, the developer was able to figure out the issue and fixed it in some test builds.

Thus the big update here is that Samsung devices should no longer see Magisk crash on their devices like it did before, and they were even able to add in some Samsung specific features too. For example, version 12 of Magisk adds support for Samsung permissive kernels, and it will even fake KNOX to 0x0 if MagiskHide is enabled. topjohnwu also made some changes to the sepolicy live patcher, and has moved it from the post-fs-data mode to the service mode.

This change was mainly done for Samsung devices as well and requires 20-80KB of ramdisk size (where it was previously 1-4KB), but that still isn’t very large. Another big addition here is choice of setting Magisk to More Only Mode. This was added to address the complaints about Magisk having too many features. It can be enabled in Magisk Manager and will limit the modification to root + boot scripts, as well as MagiskHide.

Here’s a summary of the more important changes listed below, but you can find the full change-log here.

  • [General] Move most binaries into magisk.img (Samsung cannot run su daemon in /data).
  • [General] Move sepolicy live patch to late_start service This shall fix the long boot times, especially on Samsung devices
  • [General] Add Samsung RKP hexpatch back, should now work on Samsung stock kernels.
  • [General] Fix installation with SuperSU.
  • [MagiskHide] Support other logcat am_proc_start patterns.
  • [MagiskHide] Change /sys/fs/selinux/enforce(policy) permissions if required Samsung devices cannot switch selinux states, if running on permissive custom kernel, the users will stuck at permissive If this scenario is detected, change permissions to hide the permissive state, leads to SafetyNet passes.
  • [MagiskHide] Add built in prop rules to fake KNOX status Samsung apps requiring KNOX status to be 0x0 should now work (Samsung Pay not tested).
  • [MagiskHide] Remove all ro.build props, since they cause more issues than they benefit…
  • [MagiskBoot] Add lz4 legacy format support (most linux kernel using lz4 for compression is using this).
  • [MagiskBoot] Fix MTK kernels with MTK headers.
Check out our Magisk forum!



from xda-developers http://ift.tt/2nIDvTo
via IFTTT

Comentarios

Entradas populares de este blog

Los usuarios de Apple, los que más dinero gastan en compras online

Lawnchair and Hyperion launchers add Sesame Shortcuts integration

These are the best Black Friday 2019 deals in Canada! 🇨🇦