- 10 Apr, 2019 3 commits
-
-
topjohnwu authored
-
topjohnwu authored
We upgrade compileSdkVersion to Q, but keep targetSdkVersion as 28. The reason is because targeting Q will no longer allow us to execute native binaries in an app's private data, which Magisk Manager relies a lot for performing stock boot image patches in non rooted environment. For more information regarding this issue, check this link: https://redd.it/b2inbu Some workarounds has been discovered (https://github.com/termux/proot), however for the time being there is no point to introduce these huge hacks just for targeting Q, which we don't benefit anything.
-
topjohnwu authored
-
- 09 Apr, 2019 8 commits
-
-
topjohnwu authored
-
Lukas Novotny authored
-
Rom authored
-
vvb2060 authored
-
Ingan121 authored
-
topjohnwu authored
Output format will be the same as input
-
Ian Macdonald authored
-
topjohnwu authored
Close #1314
-
- 08 Apr, 2019 6 commits
-
-
topjohnwu authored
-
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 2 commits