A simple tutorial on the change of apk for millet people

Start Program:

Double-click ApkIDE.exe to start the program. If the XP system does not start it, please click here to download the install. NET Framework 2.0.

To configure the JDK:

The first time you start, the software will automatically find the JRE installation directory in the system, if not found will prompt you to configure the SDK, you can click the menu [tool]-[Configuration SDK] To configure the JDK, as shown below. The JDK installation path must be configured (and cannot be modified if it is not configured), and the Android SDK is random (some features require it, such as DDMS, but none of these functions are related to modification).

Tip: JDK recommended use of JDK1.6 (or JDK6), JDK1.7 (or JDK7) different computers may have some minor problems, especially small memory computer (these problems see the FAQ, if you use the jdk1.7 when there is a problem and the trouble can be used jdk1.6). In addition, from the APK 2.4 start must use JDK, no longer support JRE (JDK is the development tool, JRE is just ordinary users running Java program tools). Click here to go to the official JDK download page.

Open the APK file you want to modify:

Click menu [Project]-[Open APK] Select the apk file you want to modify (note: The file name must consist of only letters, numbers, underscores, spaces, dots, etc., which cannot contain Chinese or other Asian characters).

The new modification continues the old job:

When opening a apk file, the APK is first parsed (including its name, package, permissions, and so on, and then generate its working directory of the same name according to the package name of the APK application, and if the working directory already exists, apk to ask if you want to decompile the APK again. Note here that the existing working directory is usually the working directory that you generated when you modified the APK application, and if you want to continue with this modification, click [No] to continue using it, or recompile to get a completely new source code.

Tip: If you want to continue your old job but have been delayed by the "yes" button, don't worry, the deleted directory is thrown into the system dumpster, you can go to the system Recycle Bin directly. When recovering, note that if you have previously successfully dex2jar the application (which is done automatically by the software when you decompile the APK, but may fail for some reason), you will see two directories with the same name in the Recycle Bin and right-click them to recover. (Note: This feature is valid for APK version 2.1 or later)

Modify APK

Now you can use the software search, replace and other functions to modify the source code, such changes include Chinese, to advertising, renaming, replacement resources, pictures, XX and so on. Each icon button in the following figure has a hint text, you can hover the mouse over the button to display text hints. Specific instructions will write a separate article to explain in detail, basically there is no difficulty.

Here are some small features that are not explained:

(1) On the file tree, or on the list of files obtained after the search, hold down the SHIFT key and click the right mouse button to directly display the operating system menu.

(2) in the "Input Output panel Group" Search results panel, the search results list in the form of labels separately, the mouse hover on the label will display the search results corresponding search conditions.

(3) The files in the first build directory under the working directory will not be searched (since this is apktool compile-time and not directly related to our modifications).

Compile into apk:

When the modification is complete, click the menu [Compile]-[build apk] to repackage the source code into a apk file, and the newly generated apk is stored in the same sibling directory as the original APK, with the name "Apkide_" beginning.

To get the generated apk:

Click the menu [Compile]-[get generated apk] to navigate directly to the directory where APK resides in the resource browser.

Direct Test APK:

This requires a menu command under the menu [ADB], if you have connected your device to your computer or opened the Android emulator directly on your computer, you can click the menu [adb]-[installation generated APK] to directly install the APK to the device or emulator, and then you can use the ADB logcat To observe its health.

If you find that ADB-related commands do not work, you can use the ADB devices command to see if the device is connected successfully (you can enter "ADB devices" directly in the command window of the input Output panel group), or you can use the menu [Tools]-[dalvik Debug Monitor Service] (DDMS) to test, of course, these are something, also beyond the scope of this article.

Finish the work! The most basic use of the steps here, you can continue to see how the master is the use of apk to change the rationale, recommended: Zpsemo of the "apk cracked" abnormal "cracked"