About Android's anti-compilation tool, I believe that everyone is not unfamiliar
such as Apk-tool,dex2jar
Apk-tool to decompile a layout file
Http://code.google.com/p/android-apktool/downloads/list
Dex2jar used to decompile Dex into a. jar Package
:http://code.google.com/p/dex2jar/downloads/list
Generated jar packages can be viewed with Jd-gui (provided the code is not obfuscated)
But suppose that the apk we extracted from the ROM does not decompile the source code.
Since the Android system accelerates the startup time of built-in applications, Dex is extracted from the APK to optimize to Odex (both are executable files)
So this requires that we first convert Odex to Dex and then decompile.
This requires the use of the following four files:
:http://code.google.com/p/smali/downloads/list
Only in the anti-compilation Odex when the source files are not enough, you also need to rely on the Odex ROM inside the framework. Depending on the situation, the simplest way is to odex all the copy of the framework
The following is a red-rice ROM, for example, to decompile the phone resource
Shown
Place the dependent Odex file under the system\framework.
Enter Java-jar baksmali-2.0.3.jar-d./system/framework-x phone.dex
The out directory is generated normally
Re-enter java-jar smali-2.0.3.jar out/-o classes.dex
The Class.dex of the package generation is what we want.
The following is a sample of the resource files tested
http://download.csdn.net/detail/geniuseoe2012/7352757
Heart than action, hurry to try it!
Android anti-compile Odex file