Android Anti-compilation A note of detail----distinguish jar package

By using the Anti-compilation tool to get the APK source code, the next step is to copy the source restore project. But what we get is the jar file, how to see the jar file and then restore the Android project is very important. The following is a record of how I parse the jar file process.

1, anti-compilation apk get the source code.

Here I have a previous blog in a more detailed description: Android anti-compilation analysis

2, got the source code after a few key documents everyone must have got it.

①android's manifest file

Resource files under ②res

③ Jar file

3. After the key jar file is obtained, we analyze it

(The resulting jar file)

At first, I copied the source of the class file, and built the same name for the same package name in Android project, but the source code was much more obvious. A closer look, we can analyze it.

The red box three jar files are obviously different from the normal source files. In fact, they are five imported jar package files. should be:

Android.annotation

Android.support.v4

Com.google.zxing

De.mindpipe.android.logging.log4j

Org.apache.log4j

So you can know the real source code is: com.xunlei.remotedownload this source package. The remaining five jar packages are downloaded directly from the Web and import is OK.

The problem is simple, but the author did not see clearly at the time to add a temporary not to see the third-party jar package, so write out to everyone a hint.

Android Anti-compilation A note of detail----distinguish jar package