Cannot start frida server: Unknown device though it is enrolled
See original GitHub issueOn 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:
Error: [FRIDA HELPER] Unknow device. Device not connected not enrolled ?
at Function.startServer (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/FridaHelper.js:199:19)
at /home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/src/WebServer.js:918:52
at Layer.handle [as handle_request] (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/layer.js:95:5)
at next (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/layer.js:95:5)
at /home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/index.js:335:12)
at next (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/express/lib/router/index.js:275:10)
at jsonParser (/home/axelle/.nvm/versions/node/v12.20.0/lib/node_modules/dexcalibur/node_modules/body-parser/lib/types/json.js:101:7)
This is the Frida server I have on the emulator. I have the same version on my host.
1|generic_x86_64:/data/local/tmp $ ./frida_server --version
14.1.3
Interesting: If I launch frida_server
manually, dexcalibur’s web interface still claims it has not started.
generic_x86_64:/data/local/tmp # ./frida_server
There is only one emulator:
$ adb devices
List of devices attached
emulator-5554 device
Desktop (please complete the following information):
- OS: Linux Mint 20
- Node JS version: 12.20.0
- Dexcalibur version (see ‘package.json’ or output) : 0.7.3
** If you think this issue is related to your device, please fill following information:**
- Android version: 8.0 x86 emulator
- Rooted
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Unpacked my malware, at “no cost” 😃 [well, besides learning Dexcalibur]
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:
Error: Unable to connect to remote frida-server: closed]
. But maybe you can consider that as a different issue.I launch it manually. Then I get
[Error: Unable to communicate with remote frida-server; please ensure that major versions match and that the remote Frida has the feature you are trying to use]
. Looks like Dexcalibur is not expecting this version (14.1.3)…But … when I launch another frida server I have there, version 12.8.20, it works 😃 at last…