Originally Posted by mrrocketdog
so if you could change things in the real system it could possibly cause trouble with magisk's system?
No, if you are able to edit your device's "system" partition, Magisk should handle that gracefully.
This all gets confusing because Android is transitioning to a new way of handling partitions. This new method allows for adapting the size of a partition during a flash. For example, flashing a GSI system.img that is 2.6GB causes the system partition to get resized. Often, the same slot's product partition needs to be deleted first to give system the room to grow. But then, if you fastboot flash a stock "factory" image back on that device, the system partition shrinks and the product partition grows. It's pretty elegant.
It also introduces fastboot being moved to the user space. Which means fastboot is no longer really part of the bootloader
, but an additional location for the bootloader
to send you to with the correct command (fastboot reboot fastboot) - that actually seems kinda goofy on the surface.
But all of this really applies to a handful of Google certified Treble devices.
System as Root (SAR) applies to a larger grouping of devices and includes some Treble devices. All SAR really means is, as part of a security feature, system is no longer mounted at /system, but at / . / designates a "root" partition - which is not the same as talking about root privileges; the purpose of using Magisk or other root app. With SAR devices, / (or system) can not be mounted read/write without really
knowing what you're doing. This protects the system partition and requires the use of Magisk modules to bind mount over top of the unwriteable system partition.
There was a point, demarked by the release of Magisk 19.4
, the decision was made for SAR devices, Magisk would follow the Android lead. So devices that can mount and write to /system (older devices, custom ROMs, ect) still have trouble because system appears at /. There was a flurry of root file explorers updating so they could work within these constraints.
Was this more than you were asking?