Decompilation has been written by a lot of gurus, and I’ve done it again. First, I hope it can be more accessible, so that those who have not been exposed to decompilation can

Quick enough to get started. Second, I hope I can keep it in mind more, just like taking notes. I hope you can give me your support.

Tool is introduced

  1. Android decompilation typically uses three tools. Apktool, Dex2JAR, JD-GUI.
  2. Apktool decompiles XML resource files into viewable files. The class. Dex text has been translated into smALI files. Smali is a language read by the underlying Java virtual machine.
  3. Dex2jar Tool for converting class.dex files into JAR packages
  4. Jd-gui a tool that can read JAR packages
  5. Tools to address: ““

The instance

Here we take a CERTAIN TV as an example. Because I wanted to write a live video Demo and didn’t have the data, I had to use Fiddler to block requests. However, the address is not written directly into the returned request. My guess is to splice the returned data into the broadcast address. So let’s decompile and try it.

1. Apktool:

  • We unzip the APK file. This gives us the apK resource file and the class.dex file, the source code.

  • So we have the picture. But when you open up the AndroidManifest and layout XML files, it’s all gibberish. What if I want to see how the LAYOUT of this Apk is written. This is where apkTool comes in. Put the apk file we want to decompile into the apkTool folder for later use. The DOS window is displayed, and the ApkTool page is displayed.Apktool d File name apk

  • So now we have our compiled file. The XML file is now viewable, not garbled.

2. Dex2jar:

Flip the classes.dex file into the dex2jar folder. Enter the commands in the diagram to get the JAR file in the diagram, the source code.

3. Jd – GUI:

Open the JAR file through JD-GUI to see the source code.

The end:

It’s possible to decompile code like a, B, and C, and that’s because of the obfuscation that was added to the package to prevent decompilation.

So much for decompiling, it’s a little messy. Let’s make do, folks. I went to look at his source code.

Click a follow if you like, your follow is my biggest move.

Still the same words, wind and rain waiting for you here. Thank you, and I hope you all make progress, 3Q.

(As an aside, I’ve noticed that some companies like to put images in Drawable instead of MiPMap. For example, this project I decompiled is one. I don’t know where you like it.