topjohnwu
1e94517a72
MagiskHide is coming back strong
2019-06-27 00:28:34 -07:00
topjohnwu
98f60216ac
Temporary disable MagiskHide by default
...
Latest Android Q beta does not like when zygote is ptraced on
boot. Disable it for now until further investigation.
2019-06-25 23:32:07 -07:00
topjohnwu
e29b712108
Start Magisk in SAR
2019-06-25 23:31:59 -07:00
topjohnwu
a462435f2f
Load custom sepolicy
2019-06-25 21:34:02 -07:00
topjohnwu
911b8273fe
Fix typo in sbin clone
2019-06-25 03:35:25 -07:00
topjohnwu
09935e591a
Proper SARInit test
2019-06-25 03:34:54 -07:00
topjohnwu
4a212dba35
Early mount partitions in SAR
2019-06-25 02:47:16 -07:00
topjohnwu
aac9e85e04
More Q cleanup
2019-06-25 02:38:34 -07:00
topjohnwu
bb67a837d3
Adjust class structures
2019-06-24 01:50:47 -07:00
topjohnwu
6cde695194
Remove Q dirty hacks in SARCompat
2019-06-24 01:31:42 -07:00
topjohnwu
a1a1ac0bbb
Add sbin overlay to system-as-root
2019-06-24 01:21:33 -07:00
topjohnwu
9ec8bc2166
Boot MagiskInit as actual system-as-root
...
WIP, no customization. DO NOT USE YET!
2019-06-23 15:14:47 -07:00
topjohnwu
28cd6a75e7
Add missing functions in bionic
2019-06-23 14:54:48 -07:00
topjohnwu
4cc7aced15
Add new util function
2019-06-23 03:53:41 -07:00
topjohnwu
1058aeb04f
Label current SAR impl as compat
...
The current system-as-root magiskinit implementation (converting
root directory in system partition to legacy rootfs setup) is now
considered as backwards compatible only.
The new implementation that is hide and Android Q friendly is coming soon.
2019-06-22 03:18:45 -07:00
topjohnwu
cfec0db947
Delay mounting sbin overlay
2019-06-22 03:14:33 -07:00
topjohnwu
5c7f69acaa
Separate SAR and legacy implementation
2019-06-16 12:45:32 -07:00
topjohnwu
f1d9015e5f
Move load kernel info out of class
2019-06-15 22:25:09 -07:00
topjohnwu
e8d900c58e
Fix typo
2019-06-15 18:12:12 -07:00
topjohnwu
a6241ae912
Fix magiskboot unpack option parsing
2019-06-15 16:15:12 -07:00
osm0sis
ee407472cf
magiskboot: allow forcing no recompression on ramdisk.cpio
...
- when input image had a compressed ramdisk magiskboot had no way to force the repack with the uncompressed ramdisk.cpio since it does not formally recognize cpio as its own format, so add a switch to support forcing repacking to any possible ramdisk format regardless of input image
2019-06-10 21:57:39 -07:00
osm0sis
f341f3b2dd
magiskboot: accept forcing recognized but unsupported format compression
...
- when input image had a different supported format (e.g. gzip) magiskboot would not accept a manually compressed ramdisk or kernel in an unsupported format (e.g. lzop) despite being able to recognize it, so instead would double compress using whatever the input format was, breaking the image with, in effect, a ramdisk.cpio.lzo.gz
2019-06-10 21:56:51 -07:00
Ian Macdonald
8513946e09
'magiskboot hexpatch' will exit with status 1 when nothing patched.
2019-06-10 21:41:40 -07:00
nonnymoose
8ebd9c8927
Use original file type when creating device nodes
2019-06-10 21:41:17 -07:00
topjohnwu
c1602d2554
Support execute commands in magiskhide env
...
Credits to #1454
2019-06-04 22:27:19 -07:00
topjohnwu
9f8d4e1022
Properly isolate mount namespace
2019-06-04 21:21:27 -07:00
topjohnwu
4fcdcd9a8a
Detect UID from data directories
2019-06-03 23:32:49 -07:00
topjohnwu
7918fc3528
Support building individual applets
2019-05-30 21:17:58 -07:00
osm0sis
bf58205b0a
magiskboot: be clear lzop is not a supported compression format
...
- keep detection and always display detected format type to fascilitate external support
2019-05-30 20:31:24 -07:00
vvb2060
76c88913f9
Ensure Magisk environment normal
2019-05-27 16:29:54 -07:00
topjohnwu
a3a1aed723
Don't check zygote in busy loop
2019-05-27 16:27:19 -07:00
topjohnwu
81aa56f60f
Support EROFS system-as-root devices
...
Close #1381
2019-05-27 15:19:28 -07:00
topjohnwu
ae24397793
Try to wait if block device is not ready
...
Close #1459
2019-05-27 15:01:49 -07:00
topjohnwu
3b0f888407
Minor update for parsing uevent
2019-05-27 02:55:46 -07:00
topjohnwu
845d1e02b0
Separate magiskinit components
2019-05-27 00:29:43 -07:00
topjohnwu
5d357bc41f
Remove unused function
2019-05-26 22:01:42 -07:00
topjohnwu
6a54672b13
Cleanup unnecessary functions
2019-05-26 03:05:23 -07:00
topjohnwu
3d9a15df44
Remove unnecessary '--' in magiskhide
2019-05-26 02:59:38 -07:00
topjohnwu
449c7fda2f
Enable proc_monitor test in debug mode only
2019-05-26 02:53:28 -07:00
topjohnwu
8b7b05da68
Separate hide policies
2019-05-26 02:47:57 -07:00
topjohnwu
92400ebcab
Process monitor minor tweaks
2019-05-26 02:35:12 -07:00
topjohnwu
23d3e56967
Add new util function
2019-05-25 21:42:51 -07:00
topjohnwu
6785dc4967
Disable verbose ptrace logging
2019-05-25 21:42:24 -07:00
topjohnwu
dad20f6a2d
Update zygote namespace
...
Close #1492
2019-05-25 18:30:43 -07:00
topjohnwu
bb15671046
Sleep when there is nothing to wait
2019-05-25 18:17:25 -07:00
topjohnwu
21984fac8b
Add API for running independent proc_monitor test
2019-05-25 16:08:53 -07:00
osm0sis
90ed4b3c49
magiskboot: clean up remaining unneeded ELF detection bits
...
- default for no format match is UNSUPP_RET (unsupported) so there is no needed to explicitly detect ELF still
2019-05-24 02:46:35 -07:00
Chris Renshaw
290a17a764
magiskboot: fix bootimg hdr v2 checksum generation
...
- new AOSP dtb section was missing from HASH_update
2019-05-24 02:46:35 -07:00
osm0sis
2ff5d9606b
magiskboot: add support for remaining Nook HD pre-image loaders
2019-05-19 17:38:41 -07:00
topjohnwu
80cd85b061
Try to use broadcast for su logging and notify
...
In commit 8d4c407, native Magisk always launches an activity for
communicating with Magisk Manager. While this works extremely well,
since it also workaround stupid OEMs that blocks broadcasts, it has a
problem: launching an activity will claim the focus of the device,
which could be super annoying in some circumstances.
This commit adds a new feature to run a broadcast test on boot complete.
If Magisk Manager successfully receives the broadcast, it will toggle
a setting in magiskd so all future su loggings and notifies will always
use broadcasts instead of launching activities.
Fix #1412
2019-05-13 02:01:10 -07:00
