Pay attention to the details of Android decompilation-differentiate between jar packages and androidjar

Pay attention to the details of Android decompilation-differentiate between jar packages and androidjar

After obtaining the apk source code by using the decompilation tool, the next step is to copy the source code to restore the project. But what we get is the jar file. It is important to check the jar file and restore the android project. Next we will record the process of how to analyze the jar file.

 

1. decompile the apk to get the source code.

Here I have explained in detail in a previous blog: android decompilation Analysis

 

2. After obtaining the source code, you must have obtained several key files.

① Android manifest File

② Resource files under Res

③ Jar File

 

3. analyze the key jar File

(The obtained jar file)

At the beginning, I copied the source code of these class files and created the same package name class name in the android project. However, the source code is much larger. We can analyze the data carefully.

The Three Jar files framed in red are obviously different from the general source code files. In fact, they are five imported jar package files. They should be:

Android. annotation

Android. support. v4

Com. google. zxing

De. mindpipe. android. logging. log4j

Org. apache. log4j

 

The real source code is: com. xunlei. remotedownload. The remaining five jar packages are directly downloaded from the internet and then imported in import.

 

The problem is very simple, but I didn't see it clearly at the time. I spent some time adding third-party jar packages that I don't need to read for now, so I wrote a prompt for everyone.