Skip to content

Instantly share code, notes, and snippets.

@zysyyz

zysyyz/gist:adb4a5be69f786c631350f69a5a95d5f

Forked from strazzere/gist:506a592b44c9d228d697
Created June 6, 2018 06:47
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save zysyyz/adb4a5be69f786c631350f69a5a95d5f to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save zysyyz/adb4a5be69f786c631350f69a5a95d5f to your computer and use it in GitHub Desktop.
Download ZIP
Attaching to fast loading JNI/native code from an Android app without debugging the Dalvik code
Raw
gistfile1.txt
The original issue was that some applications (ex. packers) launch the JNI/native code too fast for a person to attach an IDA Pro instance to the process. The original solution was wrapping the jni code with your own "surrogate" application so you could load it slower.
New process is to launch the Android/Dalvik activity with the debugger flag;
#am -D com.strazzere.different / .MainActivity
Which will cause the "Waiting for debugger..." mode to start. This starts the process, allowing you to attach IDA Pro to the process for the native code.
Next attach a jdwp debugger and continue;
jdb -connect com.sun.jdi.SocketAttach: hostname = 127.0.0.1, port = 8700
Drop the jdb conneciton and let the Android application run as it normal would.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment