App Name | Magisk v21.0 |
---|---|
Genre | Zip file |
Size | 5.91MB |
Latest Version | 21.0 |
Get it On | |
Update | Oct 03, 2020 |
Package Name | Magisk-v21.0.zip |
Rating | 4.8 ( 786 ) |
Installs | 1452 |
Magisk v21.0 zip file download.
Release Note: –
Long time no see! v21.0 is the largest release in Magisk’s history. It comes with full Android 11 support (tons of stuff had to be rewritten from scratch!), and a completely redesigned Magisk Manager. These are the reasons why this particular public release took me over half a year to wrap up.
To the end user, not much has changed other than the fact that Magisk Manager has completely changed its appearance. However developers should pay attention to some changes due to adjustments for Android 11. Full changelogs are too massive to fit, so here I’ll point out the main changes and links to updated documentations.
Frequently Asked Questions
Q: Why is X app detecting root?
Manually enable MagiskHide in settings (MagiskHide is no longer enabled by default). Also, there are known methods to detect Magisk, so your mileage may vary.
Q: I installed a module and it bootlooped my device. Help!
If you have USB debugging enabled in developer options, connect your phone to the PC. If your device is detected (check by `adb devices`), enter ADB shell and run the command `magisk –remove-modules`. This will remove all your modules and automatically reboot the device.
If unfortunately you do not have USB debugging enabled, reboot into Safe Mode. Most modern Android devices support pressing a special key combo at boot to enter Safe Mode as an emergency option. Magisk will detect Safe Mode being activated, and all modules will be disabled. Then reboot back to normal mode (the module disable state persists) and manage your modules through Magisk Manager.
Q: After I hidden Magisk Manager, the app icon is broken.
On devices running Android 9.0+, Magisk Manager will use a more advanced hiding method. It will install a “stub” APK that has nothing in it. The only functionality the stub app has is downloading the full Magisk Manager APK into its internal storage and dynamically load it. Due to the fact that the APK is literally *empty*, it does not contain the image resource for the app icon.
When you open the hidden Magisk Manager, it will offer you the option to create a shortcut in the homescreen (which has both the correct app name and icon) for your convenience. You can also manually ask the app to create the icon in Magisk Manager settings.
Magic Mount
The details of the actual implementation and algorithm of Magic Mount is omitted here, please directly dive into the source code if interested (`core/module.cpp`).
Even though the mounting logic is very complicated, the final result of Magic Mount is actually pretty simple. For each module, the folder `$MODPATH/system` will be recursively merged into the real `/system`; that is: existing files in the real system will be replaced by the one in modules’ system, and new files in modules’ system will be added to the real system.
There is one additional trick you can use: if you place an empty file named `.replace` in any of the folders in a module’s system, instead of merging the contents, that folder will directly replace the one in the real system. This will be very handy in some cases, for example swapping out a system app.
If you want to replace files in `/vendor` or `/product`, please place them under `$MODPATH/system/vendor` or `$MODPATH/system/product`. Magisk will transparently handle both cases, whether vendor or product is a separate partition or not.
SELinux Policies
Magisk will patch the stock `sepolicy` to make sure root and Magisk operations can be done in a safe and secure way. The new domain `magisk` is effectively permissive, which is what `magiskd` and all root shell will run in. `magisk_file` is a new file type that is setup to be allowed to be accessed by every domain (unrestricted file context).
Before Android 8.0, all allowed su client domains are allowed to directly connect to `magiskd` and establish connection with the daemon to get a remote root shell. Magisk also have to relax some `ioctl` operations so root shells can function properly.
After Android 8.0, to reduce relaxation of rules in Android’s sandbox, a new SELinux model is deployed. The `magisk` binary is labelled with `magisk_exec` file type, and processes running as allowed su client domains executing the `magisk` binary (this includes the `su` command) will transit to `magisk_client` by using a `type_transition` rule. Rules strictly restrict that only `magisk` domain processes are allowed to attribute files to `magisk_exec`. Direct connection to sockets of `magiskd` are not allowed; the only way to access the daemon is through a `magisk_client` process. These changes allow us to keep the sandbox intact, and keep Magisk specific rules separated from the rest of the policies.
The full set of rules can be found in `magiskpolicy/rules.cpp`.
It simply means unlocking the android operating system to grant access to the unauthorized section of the phone. Even though you own the handset, you don't have full authority over the phone. You just log in to the system as a user. But after you root it, you can do whatever you want with your device. Such as installing apps that unapproved, unlock the bootloader and remove unwanted bloatware, installing custom ROMs, and customize it furthermore as you wish.
It's kind of similar to apple jailbreak. And the most amazing part is android rooting can also be led to high performance and longer battery life. Well, now you know about rooting. Then what is the connection between android rooting and the Magisk Manager? Hang on, we are going to talk about it.
As they say it, it's a mask for android. Does that complicate things for you even more? well, if you are new to android rooting you probably have no idea that there are some struggles that have to be overcome when you have a rooted device. If you have a rooted android phone, you don't get OTA updates! Yeah, that's right. You have to unroot it, then get the update and root again. And some applications won't even allow running in rooted handsets. Especially banking applications.
That's when the Magisk manager apk comes to the rescue. It's a systemless rooting solution. It can cover the rooted system like a mask and you won't have to be bothered to go between rooting and unrooting. It doesn't affect the core code either. You can get OTA updates, use banking applications and do whatever you couldn't do from a rooted mobile phone.
Topjohnwu was a developer in the android developer team. He was the one who launched the Magisk Manager in 2016 as the best solution that can go through the android safety net. And since the first release to the latest Magisk apk version 23.0, he has been developing it adding convenient features, and upgrading it. So now we can go for Magisk manager apk download which has much more convenient characteristics than then.
There are a bunch of new characteristics that come with Magisk latest version 23.0.0. According to the Magisk manager GitHub page, we can expect more in the future because the developer planning to add more improvements in the future as well.
Now the design and implementation are much convenient in Magisk than earlier you don't have to download separate files for Magisk zip and Magisk manager apk. There is only one app now.
But before you do the Magisk manager apk download there are some things that you should take care of.
1. First go Magisk manager apk download for the mobile phone.
2. Enable the unknown sources to turn on un settings and then install the downloaded Magisk app
3. Now install it once more by clicking on the "install" button on the message you will see.
4. Actually that's all. Now you have installed it.
TWRP is a custom recovery solution for Android mobile phones. After you install this tool, you can back up the system and download thrid party firmware as well. Therefore make sure to back the system before starting to proceed.
In short, Yes. But it is legal as long as you root your android smartphone. Because many manufacturers allow it nowadays. However, rooting android tablets are illegal.
Since there are many users but never get complaints about malware, viruses, or any spam, we can assure you Magisk is a pretty good and safe rooting solution. Furthermore, it won't modify boot partitions or the system partitions. And neither install third-party applications without your consent.
Absolutely. It offers the facilities to download, install and manage the device completely free of charge.
It's compatible with all the android versions above 4.1 and 4.2 And your compressed boot image on an android mobile phone should be gzip compressed boot.img.
If you have installed the application externally, that might be the reason for this issue. Therefore it's better if you uninstall that and install Magisk apk to your device's internal storage.
Copyright © 2021 Magisk Manager - magisks.com