Today we present you “Android Multitool” by Flextrick which makes it easier to decompile/recompile applications + jar framework files. You can also sign your apk by easily clicking a button.
- Winows OS XP / 7 / 8 / 8.1
- Installed Java on Windows
- Installed Microsoft Powerpacks
- Installed .NET framework
– Easy handling: Select your apk and push the “decompile” button!
– This tool makes modding much faster and easier, no cmd handling any more.
– You can read the log which is integrated in the tool to find your mistake in the error.
– ADB inside: Push files into your file system with a few clicks
It looks like this so far:
How to use this tool?
Here you go..
Well, first extract the AndroidMultitool folder to C:. Otherwise it propably won´t work
-copy your framework-res.apk and other files you want to mod in the “Files” folder (this folder is for all your files you want to mod, don’t pick files from any other location)
-Next you have to start AndroidMultitool.exe
-select your framework-res.apk and push the “install” button (check log for errors)
Decompiling and recompiling apk files:
-select the apk you want to mod/decompile and push the “decompile” button (check log for errors)
Note: You can check the “use baksmali” checkbox, then e.g. the useless .line text will be removed
-your decompiled apk will be located in C:AndroidMultitoolDecompiled_apk”apkname” as a folder
-if you want to compile your apk again, select your decompiled folder, check the “apk” radiobutton and compile it again (check log for errors)
!!!NOTE!!! After compiling you have to copy the AndroidManifest.xml and the META-INF folder from your old apk to your newly compiled one!! Otherwise you´ll get bootloop! (Don’t check the smali checkbox, it will create a classes.dex file from you smali files)
-your recompiled apk will be located in C:AndroidMultitoolCompiled_apk”apkname”
Decompiling and recompiling jar files:
-select in the combobox “.jar” (check the “use baksmali” checkbox for deleting the useless .line comments)
-select the “.jar” file you want to mod
-push the “decompile” button
-your decompiled jar file will be locaten in C:AndroidMultitoolDecompiled_jar”jarname”
-for recompiling you have to check the “jar” radiobutton and select the folder within your decompiled “.jar” file
-push the compile button
-your compiled jar file will be located in C:AndroidMultitoolCompiled_jar”jarname”classes .dex
-delete the “classes.dex” file in your “.jar” file
-copy the new “classes.dex” file you compiled in the “.jar” file
Signing apk files:
-select the “.apk” you want to sign
-push the “sign” button
-the signed apk file is located in C:AndroidMultitoolSigned_apk”apkname_signed”
You want to decompile many files from different devices or different android versions / frameworks? Tagging makes it possible!
– before installing your framework type in any tag (like “hero”)
– then install your framework and work normally
Android Debug Bridge
You want to push files with adb to your device? Follow these instructions:
Please klick on the “advanced” register in the tool
-push “check” to control if your device is ready
-if the device is not ready please follow the instructions, which are listed in the tool (device offline, no device…)
-if the device is ready, choose a file you want to push
-choose a path on the device, where the file should be placed later
-push the “push” Button
-alternately: press “Reboot device” to reboot your device and to let changes take effect
Alternate Link https://www.mediafire.com/?w8u0dlmz4dva0a9
Questions and answers:
Q: The programm does not start, it crashes.
A: Please install Powerpacks, this one: http://go.microsoft.com/fwlink/?Link…27&clcid=0x804
Q: What do you mean exactly with “!!!NOTE!!! After compiling you have to copy the AndroidManifest.xml and the META-INF folder from your old apk to your newly compiled one!! Otherwise you´ll get bootloop! ” .. I don’t understand.
A: You have to open your old apk (this one you selected for decompiling in the folder /files) and copy from that apk the AndroidManifest.xml and the META-INF folder to the apk you just decompiled and recompiled.
Q: I followed all steps in the startpost but I’m still getting this error: “apktool is not recognized as internal or external command”
What can I do?
A: Please refer to this post by @LasVegasRomeo: http://forum.xda-developers.com/show…&postcount=681
access files from all locations of the pc (you’re not limeted to the /Files folder)
add version number to the tool
add tag support (tagging allows multiple framework support)
small additions and fixes
support for Win7 / 8 / 8.1 (no extra versions)
add apktool b9
add different apktool, aapt and batch files
should solve some problems on de – and recompiling
Fixes for adb push
button to reboot device
many other fixes and code rework
SlimBean apktool (de)compiling also with inverted folders from trds)
ADB (AndroidDebugBridge for pushing files to your device)
Some Links in the tool for support and donation
Java JRE 1.7 is required!
Update apktool to v2.0.0
aapt is now included inside the apktool binary. Its not required to maintain your own aapt install under $PATH. (However, features like -a / –aapt are still used and can override the internal aapt).
Remove framework $HOME/apktool/framework/1.apk or manually update via (FrameworkFiles)
Eagle eye users will notice resources are now decoded before sources now. This is because we need to know the API version via the manifest for decoding the sources.
Smali/baksmali 2.0 are included. This is a big change from 1.4.2. Please read the smali updates here for more information.
-o / –output is now used for the output of apk/directory.
-t / –tag is required for tagging framework files
-advance / –advanced will launch advance parameters and information on the usage output.
-m / –match-original is a new feature for apk analysis. This retains the apk is nearly original format, but will make rebuild more than likely not work due to ignoring the changes that newer aapt requires.
After [d]ecode, there will be new folders (original / unknown) in the decoded apk folder.
original/ = META-INF folder / AndroidManifest.xml, which are needed to retain the signature of APKs to prevent resigning. Used with -c / –copy-original on [b]uild.
unknown/ = Files / folders that are not part of the standard AOSP build procedure. These files will be injected back into the rebuilt APK.
apktool.yml collects more information than before
SdkInfo = Used to re-populate the sdk information in AndroidManifest.xml since aapt requires it to be passed at runtime.
packageInfo = Used to help support Android 4.2 due to renamed manifest packages. Automatically detects difference between manifest and resources and performs automatic –rename-manifest-package on [b]uild.
versionInfo = Used to re-populate the version information in the AndroidManifest.xml since aapt requires it to be passed at runtime.
compressionType = Used to determine the compression that resources.arsc had on the original apk to duplicate on [b]uild.
unknownFiles = Used to record the name/location/compression type of non-standard files in Apk.
bigger UI for better overview
option to save log to a text file
other small fixes
complete code rework
folder structure for a better overview
decompiled, recompiled, signed files will be located in their own folder
no more messy file handling
added radio buttons for choosing jar or apk
some graphical changes
added info button in the “installing framework” section
Added ability to decompile and recompile “.jar” files
FolderBrowserDialog: If you push the “browse” button you are in the right directory now and needn’t to scroll and search the “AndroidApktool” folder
other small fixes
Added ability to sign .apk
Changed comboboxes to browse buttons
bigger log – screen