search

FrenchYeti / dexcalibur

[Official] Android reverse engineering tool focused on dynamic instrumentation automation leveraging Frida. It disassembles dex, analyzes it statically, generates hooks, discovers reflected methods, stores intercepted data and does new things from it. Its aim is to be an all-in-one Android reverse engineering platform.
Apache License 2.0
1.06k stars 126 forks source link

Devices listing bug #48

Open 0xbadb0d00 opened 3 years ago

0xbadb0d00 commented 3 years ago

Hello, sometimes Dexcalibur shows Devices ID with a simple "*".

This means that it doesn't correct recognized the device, simply because it launched the adb devices listing command, that returned a string like " daemon started successfully " and it get the first character as a correct Device ID.

To let it works with a workaround, I modified that piece of code to call device listing two times, in this way:

AdbWrapper3 js

Hope it helps other guys and developers

FrenchYeti commented 3 years ago

Hey, thank you :)

FrenchYeti commented 3 years ago

Commonly, this case happens when user runs "adb" commands from terminal and from dexcalibur. Since Dexcalibur come with own ADB binary, when dexcalibur executes ADB command, it must restart daemon.

0xbadb0d00 commented 3 years ago

Commonly, this case happens when user runs "adb" commands from terminal and from dexcalibur. Since Dexcalibur come with own ADB binary, when dexcalibur executes ADB command, it must restart daemon.

The strange behaviour is that before this happen Dexcaliur correctly launched the "adb kill" command, and so, I am expecting that id already restarted it's correct server, but anyway it tries to restart adb server also when you launch the device listing command