1. Decompile = After compilation, they are respectively
The smali directory is compiled back into classes.dex file
The res directory is compiled back into resources.arsc file< /p>
2. Back to the compilation sequence
When back compiling, the "source", that is, resources, will be checked first
When you localize the file, an error occurs in the modification (a symbol is missing) No),
Then the compilation will automatically skip compiling the res folder and directly compile smali.
So, if smali (classes.dex) has not been Chineseized, it is recommended that you delete this folder.
This will greatly speed up compilation.
3. Error 1
During Chinese translation, some symbols are often accidentally deleted, such as "<" ">" symbols and so on.
< string name="app_name"File Manager
These small errors will cause errors in the compile-time translation check.
So when translating into Chinese, pay attention to proofreading and then compile again.
It is recommended to use some advanced text editors that support syntax highlighting view.
4. Error problem 2
Recently, it was discovered that after some APK files are decompiled, even if they are recompiled directly without Chinese translation, errors will occur.
Possible reason 1. There is an extra "\" (\@) in front of the @ symbol in the XML file syntax after decompilation.
Use a text editing tool to directly replace \@ with @ , should be able to solve it.
It is recommended to use the latest version of the decompilation tool.
5. It is recommended that you use the new version of the APKTool tool.
Of course, if the new one has problems, you can also try the old one. The Chinese version of the system files is emphasized again
2. There is no need to sign the system files after they have been translated into Chinese. You can just replace the translated files directly.
The main thing is that the system files are placed in the system directory, and there is no need to read the signature again to obtain permissions, which is already advanced.
2. Packaging Instructions
1. Usually after the Chinese version is compiled, all files in the APK will be automatically generated, or *.APK files will be automatically generated.
However, it is recommended that you do not use this file directly. Instead, use the substitution method to replace your Chineseized file,
For example: resources.arsc, if the picture has been modified, etc. Wait...
2. Many people use "WinRAR" or "Good Compression" to decompress or compress APK files, which is not recommended here.
I hope everyone will install the compression tool 7-Zip, which has the best support for the zip format. And it’s very convenient.
You don’t need to re-associate the apk, just right-click to open it. Just drag and drop the replacement in, and it will be OK. Return to the compilation error problem
(1. It prompts an error in the last line of strings.xml, check whether the symbol is wrong;
In Chinese Sometimes, some symbols are often accidentally deleted, such as "<" ">" symbols, etc.
(2. Prompt strings.xml Most The top contains an error in the first line of Chinese code, the encoding format is wrong, and it is converted to UTF-8;
(3. An error occurs in public.xml, check the modified arrays.xml to see if there are any code errors;
p>
2. Everything works fine but cannot be compiled back
There is another situation where the latest version of apktool can decompile an apk file normally, but cannot be compiled back without any modifications.
This is something to note. You can try using a lower version of apktool to decompile, and then use a higher version of apktoo tool to recompile.
Here we recommend the tool APKDB, which is very convenient. You can select the version of apktool when decompiling.