a sourceif it doesn’t open, thenSo, butoriginal source
Traditionally, to get root on a smartphone or tablet, it was necessary to place the su file (which is responsible for privilege escalation) in the / system / xbin / directory, that is, in the system partition. This action changed its hash sum, which made it impossible to install OTA updates.
Moreover, with the release of Marshmallow, Google took care of security, the foundations of which were laid in Lollipop, making it impossible to correctly install su in / system. Chainfire, developerSuperSU , began a search for workarounds, the result of which was quite unexpected.
Instead of placing su in / system, he injected it into the boot partition containing the kernel and the so-called RAM disk. The latter is an image of the file system, which is loaded into the RAM at the initial boot stage of Android. The RAM disk contains the basic system components that must be started before the / system partition is connected.
It turned out that if you implement su directly into the RAM disk, you can bypass all the Android defense mechanisms in one fell swoop and, in addition, ensure the normal operation of the OTA. This method of rooting was called systemless root (non-system root) and became the main SuperSU for devices running Android Marshmallow and Nougat. It should be noted that this method is also applicable to Samsung devices running on version 5.1 (or newer).
Non-root has its advantages and disadvantages. The main disadvantage is that it does not work on devices with a locked bootloader by default - of course, there may be workarounds, but they are specific to each device.
However, non-system root is more universal than the traditional one. In many cases, it does not break the OTA update. Non-system method is “cleaner”, since it does not add or change files in the / system section. This means that removing or hiding root will be much easier. After resetting to factory settings, the root access feature will be removed.
The last advantage is, of course, a double-edged sword. Most users would prefer that root access still remain, but to restore root access, you just need to flash the SuperSU file.
Magisk
The information presented above has one goal - to help understand that systemless is convenient and not scary. After all, Magisk uses exactly this way of working with the system. Next, we dwell on the features of Magisk in more detail.
So, Magisk is a utility that patches the boot section and makes it possible to install various system mods in systemless mode. It allows you to run scripts at different stages of mounting and replace files (for example, build.prop) even before mounting the / data section, hide root and Xposed from applications and services such as Android Pay, Samsung Pay or Sberbank Online, and also get OTA- Stock firmware updates.
However, the main advantage of Magisk is that when a RAM disk is modified, it only writes a bootloader to it, while the mods themselves are stored in the / data and / cache sections. As a result, after flashing it will not be necessary to apply all the mods anew, just install Magisk, and it will download them all automatically.
Other features are also worth noting: changing the bootloader state for other programs and the KNOX state for Samsung devices; several entry / injection points for developers, reliably guarantee pauses at boot until all changes work; post-fs (cache) mode, which is triggered before the / data partition is mounted, and allows, for example, changing bootanimation; removal of dm-verity, forceencrypt; built-in BusyBox, built-in ability to spoof the / etc / hosts file (to block ads).

in Z3, it was originally:

and recommend to do: