A little less than a month ago we covered a big update to Magisk beta when it was brought up to version 13.5. That beta update focused on bringing back Busybox, although only to be used internally, and added some stock Samsung kernel workarounds for improved compatibility. Naturally, you can install the Busybox binary thanks to a convenient Module if you want to use it, but this update added it for internal use only.
As we typically see with new features being tested in the beta version, XDA Recognized Developer and Recognized Contributor topjohnwu has brought those two big changes to the stable channel today. So if you have had issues with Busybox or Samsung devices in the past then you may want to give version 14 a try and see how it works. Along with those two features, this update also brings a method of hiding the Magisk Manager application as well.
topjohnwu says the approach is pretty naive and there are still ways of detecting it, but it should work in many cases. The developer has also been working on a new installation method for ADB. This is useful for those cases where a device doesn't have a custom recovery (or maybe you just want to preserve the stock recovery for accepting OTA updates) and this has now been integrated into Magisk Manager.
So you can provide your stock boot image (in both raw image format or tar-ed up ODIN flashable format) to Magisk Manager and it will patch it so that you no longer need a custom recovery to install Magisk. For those interested in this new install method, be sure to check the updated installation instructions in the original post of the official XDA thread. This is a big update and also includes some new features for Magisk Manager, a new Magisk Module template and versioning scheme, a small update to MagiskHide and some work has been done to include support for the Google Pixel phones as well.
Check out this update in our Magisk forum
from xda-developers http://ift.tt/2gNL4ah
via IFTTT
No comments:
Post a Comment