- 08 Apr, 2019 5 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
The root nodes are /system and /vendor. Adding new files into these directories, although works on some devices, mostly bootloops on many devices out there. So don't allow it, which also makes the whole magic mounting logic much easier and extensible.
-
topjohnwu authored
-
topjohnwu authored
-
- 07 Apr, 2019 1 commit
-
-
topjohnwu authored
-
- 06 Apr, 2019 11 commits
- 05 Apr, 2019 6 commits
-
-
vvb2060 authored
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
Samsung does not like running cmd before system services are started. Instead of failing, it will enter an infinite wait on binder. Move APK installation to boot complete to make sure pm can be run without blocking process.
-
topjohnwu authored
- 04 Apr, 2019 3 commits
- 03 Apr, 2019 4 commits
- 02 Apr, 2019 2 commits
- 01 Apr, 2019 3 commits
-
-
topjohnwu authored
Close #1281
-
topjohnwu authored
Forseeing the future that more and more A only system-as-root devices would have similar bootloader behavior as the latest Samsung devices (that is, no ramdisk will be loaded into memory when booting from the boot partition), a solution/workaround has to be made when Magisk is installed to the recovery partition, making custom recoveries unable to co-exist with Magisk. This commit allows magiskinit to read input device events from the kernel to detect when a user holds volume key up to toggle whether system-as-root mode is enabled. When system-as-root mode is disabled, magiskinit will boot with ramdisk instead of cloning rootfs from system, which in this case will boot to the recovery.
-
topjohnwu authored
Just for convenience, nothing special here
-
- 31 Mar, 2019 5 commits