- 29 Jan, 2018 3 commits
- 28 Jan, 2018 3 commits
- 27 Jan, 2018 4 commits
- 26 Jan, 2018 1 commit
-
-
topjohnwu authored
-
- 22 Jan, 2018 1 commit
-
-
topjohnwu authored
-
- 12 Jan, 2018 3 commits
- 11 Jan, 2018 2 commits
- 10 Jan, 2018 3 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
Shaka Huang authored
When both keepverity and keepforceencrypt are false, ‘e’ will be freed after removing ‘verity_key’ and segmentation fault might happened in strstr(e->filename, “fstab”) Signed-off-by:
Shaka Huang <shakalaca@gmail.com>
-
- 08 Jan, 2018 5 commits
- 01 Jan, 2018 4 commits
- 31 Dec, 2017 4 commits
-
-
topjohnwu authored
-
Shaka Huang authored
For certain device (e.g ZenFone 4 ZE554KL) there’s no sepolicy under rootfs and no a/b partition (implies no vendor partition) Magisk will failed to patch SELinux policy database and the system won’t boot up. In order to cope with this configuration the status of loading policy db needs to be checked, once it failed we have to mount the system partition and do patch_sepolicy() again. Signed-off-by:
Shaka Huang <shakalaca@gmail.com>
-
topjohnwu authored
-
topjohnwu authored
-
- 28 Dec, 2017 2 commits
- 25 Dec, 2017 3 commits
- 24 Dec, 2017 2 commits