App Name | Magisk v21.2 |
---|---|
Genre | Zip file |
Size | 5.9 MB |
Latest Version | 21.2 |
Get it On | |
Update | Dec 29, 2020 |
Package Name | Magisk-v21.2.zip |
Rating | 4.8 ( 457 ) |
Installs | 4827 |
Magisk v21.2 zip file download
Pre-Init
`magiskinit` will replace `init` as the first program to run.
– Early mount required partitions. On legacy system-as-root devices, we switch root to system; on 2SI devices, we patch fstab and execute the original `init` to mount partitions for us.
– Load sepolicy either from `/sepolicy`, precompiled sepolicy in vendor, or compile split sepolicy
– Patch sepolicy rules and dump to `/sepolicy` or `/sbin/.se` or `/dev/.se`
– Patch `init` or `libselinux.so` to force the system to load the patched policies
– Inject magisk services into `init.rc`
– Execute the original `init` to continue the boot processpost-fs-data
This triggers on `post-fs-data` when `/data` is decrypted and mounted. The daemon `magiskd` will be launched, post-fs-data scripts are executed, and module files are magic mounted.
late_start
Later in the booting process, the class `late_start` will be triggered, and Magisk “service” mode will be started. In this mode, service scripts are executed.
## Resetprop
Usually, system properties are designed to only be updated by `init` and read-only to non-root processes. With root you can change properties by sending requests to `property_service` (hosted by `init`) using commands such as `setprop`, but changing read-only props (props that start with `ro.` like `ro.build.product`) and deleting properties are still prohibited.
`resetprop` is implemented by distilling out the source code related to system properties from AOSP and patched to allow direct modification to property area, or `prop_area`, bypassing the need to go through `property_service`. Since we are bypassing `property_service`, there are a few caveats:
– `on property:foo=bar` actions registered in `*.rc` scripts will not be triggered if property changes does not go through `property_service`. The default set property behavior of `resetprop` matches `setprop`, which **WILL** trigger events (implemented by first deleting the property then set it via `property_service`). There is a flag `-n` to disable it if you need this special behavior.
– persist properties (props that starts with `persist.`, like `persist.sys.usb.config`) are stored in both `prop_area` and `/data/property`. By default, deleting props will **NOT** remove it from persistent storage, meaning the property will be restored after the next reboot; reading props will **NOT** read from persistent storage, as this is the behavior of `getprop`. With the flag `-p`, deleting props will remove the prop in **BOTH** `prop_area` and `/data/property`, and reading props will be read from **BOTH** `prop_area` and persistent storage.
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