Is this systemless?
edit: sadly it does not work
it does work lol.. im sure more testers will confirm.. posting a screenshot then saying it doesnt work doesnt help us help u in figuring out whats goin on with ur attempt..
yes, it is systemless.. until vzw users find a way to unlock the BL i highly recommend not modifying system or other partitions that are verified on boot bcuz u could hard brick/bootloop and with locked bl end up with no way to revive it.
Basically mostly inspired by tjw github as theres a small section that talks about installing root in daemon only mode.
This means the magiskinit file is pushed to a folder created on data partition. To have minimal impact he uses the odm partition since theres not much use for it by the system and odm/bin is in the path.
magiskinit64 binary is used to create magiskpolicy and magisk binaries. Magiskpolicy patches sepolicy for magisk. Magisk binary is used to start the magisk daemon. su and resetprop are linked to the magisk binary so that when an app calls su it can be granted root. The magiskmanager needs to b installed as it is the root manager, without it if u try to call su the request will b denied.
the folder with the files is on data partition which is bind mounted over /odm.
This creates a "systemless" approach. Only the dir on data is ever modified. Even if u pushed say some binaries to /odm/bin they are actually being written to data..
this is a very basic method.. magisk obviously does a lot more when installed properly but due to the locked bl root can only b installed in daemon mode for now. This means no modules or other stuff. It is basically using the temproot to get a magisk temp root so u can use root apps and not b limited to using a terminal or adb only for root stuff.
We tried installing root in other directories such as /system/bin but of course this causes instability in its current state. odm was the easiest least evasive place we tested to push magisk for now.
its a start.