![]() ![]() If you go the smali route, you might want to try APK Studio, an IDE that automates some of the above steps to assist you with decompiling and recompiling an apk and installing it on a device. Note that apktool does not sign the resulting apk, so you'll need to take care of that just like any other Android application. Once you're done, you can easily package the apk back up with apktool again. smali files, as described in this question. dex files with Android's dx compiler, and then use baksmali (smali disassembler) to convert the. class files with javac, then convert your. You can read and modify the smali or even replace classes entirely by generating smali from new Java source (to do this, you could compile your. Once you've got apktool installed, you can just point it at an apk file, and you'll get back a smali file for each class contained in the application. I've found that the easiest way to do this is with apktool. The other major alternative is to disassemble the bytecode to smali, an assembly language designed for precisely this purpose. Note that if the source has been obfuscated with proguard, the resulting source code will be substantially more difficult to untangle. In other words, you can read the source, but you can't really modify and repackage it. ![]() ![]() The resulting source is useful to read and understand the functionality of an app, but will likely not produce 100% usable code. You can do this easily with dex2jar and jd-gui, as fred mentions. To clarify somewhat, there are two major paths you might take here depending on what you want to accomplish:ĭecompile the Dalvik bytecode (dex) into readable Java source. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |