- Joined
- Jan 8, 2019
- Messages
- 56,612
- Solutions
- 2
- Reputation
- 32
- Reaction score
- 100,454
- Points
- 2,313
- Credits
- 32,640
6 Years of Service
76%

GDA(GJoy Dex Analysizer)
Most reverse engineers mainly use Java decompiler, commercial Dalvik decompiler Jeb, and smali2java to analyze Android APPs. Java decompiler is based on Java bytecode, including JD, JD-GUI, jadx, and others. smali2java is a decompiler based on the Smali code. They have their own shortcomings, such as the Java decompiler depends on the conversion of dex2jar. For complex, obfuscated or packed apks, there is a problem of translation failure. smali2java decompiles Smali code which should be translated from DEX with apktool, so it increases the difficulty and error rate and decreases the speed of manual analysis. In addition, their interaction is poor, which increases the difficulty of manual analysis. Although the commercial Jeb has better interactivity, it is easy to death when analyzing a large-sized APP with the Multidex, and it is very expensive for me…
Changelog v4.0
Fix the bug that all nodes were deleted when searching the class tree
Fix the bug that inheritance methods or members cannot cross-reference #91
Fix the problem that the parameters/return-value are not displayed during data flow analysis #91
Fix the problem about the python plug-in #92
The constant propagation algorithm is optimized to correct the error of code output #90
Optimize the expression output and correct several errors of code output #90
The variable declaration and expression are further optimized
Fix some crash bugs.
Add translation utility for strings (with Google and Youdao).
To see this hidden content, you must like this content.