Closed uintdev closed 7 years ago
Interesting. Do you get any SE Linux avc: denied in adb logcat. E.g:
adb logcat | grep avc
?
It returns the following:
W/adbd ( 4943): type=1400 audit(0.0:23): avc: denied { read } for name="selinux_version" dev="mmcblk0p7" ino=168006 scontext=u:r:adbd:s0 tcontext=u:object_r:security_file:s0 tclass=file permissive=0
W/run-as ( 4950): type=1400 audit(0.0:24): avc: denied { getattr } for path="/dev/pts/0" dev="devpts" ino=3 scontext=u:r:runas:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=0
W/run-as ( 4950): type=1400 audit(0.0:25): avc: denied { use } for path="socket:[55996]" dev="sockfs" ino=55996 scontext=u:r:shell:s0 tcontext=u:r:runas:s0 tclass=fd permissive=0
SELinux strikes again..
Sorry for the delay. I guess you could try what is outlined here: https://github.com/timwr/CVE-2016-5195/issues/47 e.g don't use the Makefile and just run the commands manually:
adb shell '/data/local/tmp/dcow /data/local/tmp/run-as /system/bin/run-as'
adb shell
/system/bin/run-as
That did the trick. Now it is in the same situation as issue #47 (context is 'u:r:shell:s0'). That's progress.
Issue: After successfully exploiting, I am taken to the shell but if I press enter (doesn't matter what the command is), it kind of hangs. You could press the enter key as much as you want and it would go to the next line each time but it looks (visually) as if it's still waiting for output infinitely with the blinking cursor. Using CTRL+C is one way of getting out of the entire thing. I had tested the
reboot
command but that did nothing whatsoever. The actual unit was responsive the entire time. So nothing like kernel panics ended up happening (unlike half of the time with KingRoot).System information:
MAKE TEST:
MAKE ROOT: