Latest Magisk 16.4 comes with improved Magisk
It's been a significant time from now since the last form of the considerable Magisk landed with included highlights. Yet, that is going to change now as another rendition is discharged with much enhancements and sure in the engine changes. Truth be told, there are numerous progressions that the most recent Magisk beta 16.4 conveys to the table, aside from the much-anticipated help for Galaxy S9/S9+.
Important is the enhanced MagiskHide execution. As you exceptionally understand, the MagiskHide conceivably sidesteps the Google's SafetyNet. However, Google SafetyNet check strategy and Magisk have a long history of getting away with tomfoolery, the last was fruitful in monitoring SafetyNet a large portion of the circumstances.
Be that as it may, gone days are on which certain rumored application engineers executed there possess Root-Detection strategies that the Magisk neglected to sidestep until the emergance of past Magisk 16.3. What's more, with this new discharge the engineer, Topjohnwu has reinforced the MagiskHide highlight to such an extent that the expanding measure of applications that run gadget check/root location in a different administration, which was under the radar of MagiskHide's are presently included as the objective.
Aside from the enhanced MagiskHide, the Magisk 16.4 fixes certain issues with the Magisk on Android P. Alongside the Magisk 16.4 the Magisk Manager has likewise been refreshed. The most recent Magisk Manager conveys the rendition number 5.7.0, maybe, a significant knock from the past v5.6.4. The entire changelog of the most recent Magisk and also Magisk Manager is given beneath.
Changelog
Magisk v16.4
– [Daemon] Directly check logcat order as opposed to recognizing logd, should settle logging and MagiskHide on a few Samsung gadgets
– [Daemon] Fix startup Magisk Manager APK establishment on Android P
– [MagiskPolicy] Switch from AOSP u:r:su:s0 to u:r:magisk:s0 to counteract clashes
– [MagiskPolicy] Remove pointless sepolicy principles to diminish security punishment
– [Daemon] Massive re-outline/sbin tmpfs overlay and daemon start up
– [MagiskInit] Remove magiskinit_daemon, the genuine magisk daemon (magiskd) might deal with everything itself
– [Daemon] Remove post-fs organize as it is extremely restricted and furthermore won't chip away at A/B gadgets; supplanted with basic mount in post-fs-information, which will run ASAP even before the daemon is begun
– [General] Remove each of the 64-bit parallels as there is no reason for utilizing them; all doubles are currently 32-bit as it were.
– [resetprop] Add Protobuf encode/decipher to help controlling hold on properties on Android P
– [MagiskHide] Include application sub-benefits as concealing targets. This may essentially build the measure of applications that could be legitimately covered up
Magisk Manager v5.7.0
– Add application alternate routes for Android 7.1+
– Bump insignificant module minMagisk necessity to 1500
– Adjustments for new sepolicies on v16.4+
– Fix crashes while reviving the online report
Important is the enhanced MagiskHide execution. As you exceptionally understand, the MagiskHide conceivably sidesteps the Google's SafetyNet. However, Google SafetyNet check strategy and Magisk have a long history of getting away with tomfoolery, the last was fruitful in monitoring SafetyNet a large portion of the circumstances.
Be that as it may, gone days are on which certain rumored application engineers executed there possess Root-Detection strategies that the Magisk neglected to sidestep until the emergance of past Magisk 16.3. What's more, with this new discharge the engineer, Topjohnwu has reinforced the MagiskHide highlight to such an extent that the expanding measure of applications that run gadget check/root location in a different administration, which was under the radar of MagiskHide's are presently included as the objective.
Aside from the enhanced MagiskHide, the Magisk 16.4 fixes certain issues with the Magisk on Android P. Alongside the Magisk 16.4 the Magisk Manager has likewise been refreshed. The most recent Magisk Manager conveys the rendition number 5.7.0, maybe, a significant knock from the past v5.6.4. The entire changelog of the most recent Magisk and also Magisk Manager is given beneath.
Changelog
Magisk v16.4
– [Daemon] Directly check logcat order as opposed to recognizing logd, should settle logging and MagiskHide on a few Samsung gadgets
– [Daemon] Fix startup Magisk Manager APK establishment on Android P
– [MagiskPolicy] Switch from AOSP u:r:su:s0 to u:r:magisk:s0 to counteract clashes
– [MagiskPolicy] Remove pointless sepolicy principles to diminish security punishment
– [Daemon] Massive re-outline/sbin tmpfs overlay and daemon start up
– [MagiskInit] Remove magiskinit_daemon, the genuine magisk daemon (magiskd) might deal with everything itself
– [Daemon] Remove post-fs organize as it is extremely restricted and furthermore won't chip away at A/B gadgets; supplanted with basic mount in post-fs-information, which will run ASAP even before the daemon is begun
– [General] Remove each of the 64-bit parallels as there is no reason for utilizing them; all doubles are currently 32-bit as it were.
– [resetprop] Add Protobuf encode/decipher to help controlling hold on properties on Android P
– [MagiskHide] Include application sub-benefits as concealing targets. This may essentially build the measure of applications that could be legitimately covered up
Magisk Manager v5.7.0
– Add application alternate routes for Android 7.1+
– Bump insignificant module minMagisk necessity to 1500
– Adjustments for new sepolicies on v16.4+
– Fix crashes while reviving the online report
Comments
Post a Comment