Open pellaeon opened 4 years ago
System information:
$ pip list
Package Version
-------------- ----------
certifi 2019.11.28
chardet 3.0.4
click 7.1.1
colorama 0.4.3
Flask 1.1.1
frida 12.8.16
frida-tools 7.2.0
idna 2.9
itsdangerous 1.1.0
Jinja2 2.11.1
MarkupSafe 1.1.1
pip 20.0.2
pprint 0.1
prompt-toolkit 3.0.4
Pygments 2.6.1
requests 2.23.0
setuptools 46.1.1
urllib3 1.25.8
wcwidth 0.1.9
Werkzeug 1.0.0
wheel 0.34.2
Python 3.6.9 on Ubuntu 18.04.4 LTS
$ uname -a
Linux AAA 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I am using https://github.com/ViRb3/magisk-frida . I just found that: If I run this on the phone:
$ adb shell
AAA:/ $ su
AAA:/ # killall frida-server
AAA:/ # /system/xbin/frida-server -D
I can get installed applications list normally, and spawn applications normally.
Are you sure that your module is up-to-date? Just fixed a bug that resulted in things failing if frida-server
was started from a boot script where LD_LIBRARY_PATH
was set to contain 64-bit libraries. (Which is the case on Android 10.)
I tried removing the magisk frida module and install it back to get the latest version, it still shows the same behavior as my original report. Magisk frida version: 12.8.17-1
I have same issues with latest magisk module and command frida-ps -U -a
Workaround with minor changes:
su
ps -A | grep frida
kill -9 <frida-server PID>
/bin/frida-server -D
Same issue here on Android Pie with my Oneplus 3 Installed with the latest Magisk Frida
frida-server --version
12.8.20
I have same issues with the latest magisk module (14.2.3-1)
Android 8.1
Found what caused this problem:
@oleavr Most likely the problem is due to the use of Secure Start-up
Detected the same issue on Android 12 Beta 5 with a Magisk module which has a Magisk-Frida idea as well. Trying to delay a bit the Frida launching a bit. I'll share more news when get it.
It seemed to be an issue with Magisk-Frida. Although there was a potential fix for it, I provided a safer workaround: https://github.com/ViRb3/magisk-frida/pull/18
When I execute:
It will always return:
When using the python binding, it is the same. Source code:
Returns message:
When running, I made sure there is only one USB device:
It seems that the problem exists within this file https://github.com/frida/frida-core/blob/master/src/linux/agent/system-server.js . So I tried to load it manually with:
Note that in system-server.js I had to replace
enumerateApplications
withenumerateapplications
.And then call it with test.py:
With this I was able to obtain the installed application list.
I was not able to debug it further because I don't know how to modify
system-server.js
and build a new frida that embeds the modifiedsystem-server.js
. If I'm able to modify it then I will be able to debug this problem further by printing values insystem-server.js
then check, etc.A little more background to this is that, I was originally trying to spawn application using
device.spawn(app_package_name)
in the python binding, but because of this problem, I can only attach but not spawn the app.I would be grateful if you can fix this problem (if you already know how), or just give me some direction on how to further trace the issue. Many thanks!