-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start frida server: Unknown device though it is enrolled #32
Comments
Can you go to "Settings > Target device" and click on "Bridge" field ?
When the device is connected. Into bridge list, you can select how to communicate with your device. By default, the bridge is the bridge used during enrollment, most of time is 'adb+usb', but if you have configured ADB over TCP, you should see 'adb+tcp' too. I will investigate your issue |
And have you device into "Target device " list ? It seems there is not default device associated to this project. |
Ok that solves the issue. I didn't know you had to do that.
and then now I can click on the button that says to start the Frida server, and it's happy. Except ... it is not running :(
So, if I click on "run spawn" for example, it complains: I launch it manually. Then I get But ... when I launch another frida server I have there, version 12.8.20, it works :) at last... |
Unpacked my malware, at "no cost" :) [well, besides learning Dexcalibur] |
That why i anwser always : please wait the v1.0 XD I fully rewrote it in TypeScript and fixed lot of things. |
I remembered the reason is a known issue with frida-node. Because while a long time max major version of frida supported by frida-node was 12.x. At this moment, frida major version was 13.x. It's not still a problem, so i can remove version limit from packages.json |
On Dexcalibur, in the hook panel, I see that my Frida server is stopped and that I should click to start it. However, when I click, it fails to stop it and produces a log error "Unknow device. Device not connected not enrolled ?".
Of course, the device is enrolled :)
Frida server is indeed not started on the emulator (can't find it with ps).
The device is enrolled : Dexcalibur even uploaded
frida_server
in/data/local/tmp
.This is the error I get:
This is the Frida server I have on the emulator. I have the same version on my host.
Interesting: If I launch
frida_server
manually, dexcalibur's web interface still claims it has not started.There is only one emulator:
Desktop (please complete the following information):
** If you think this issue is related to your device, please fill following information:**
The text was updated successfully, but these errors were encountered: