-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
9c531ef
commit 7b718ce
Showing
16 changed files
with
57 additions
and
96 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,5 +13,4 @@ zipalign/*.jar | |
tools/tag_list | ||
*.zip | ||
Instructions | ||
apk-utility/ | ||
x |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,24 +1,34 @@ | ||
## APK Utility v2.3 | ||
# Apk Utility v2.4 | ||
|
||
![image](tools/menu.png) | ||
|
||
APK Utility is for decompiling, compiling, zipaligning, and signing apk and jar files. The utility also has the ability to tag your frameworks. This is a very good feature if you want to install frameworks for multiple different devices without having to remove one for the other. | ||
Apk Utility is for decompiling, compiling, zipaligning, and signing android apk and jar files. The utility also has the ability to tag your framework files. This is a very useful feature if you want to install framework files for multiple different devices without having to remove one for the other. Basically a tag is a label to distinguish between multiple devices' framework files. | ||
|
||
## Usage | ||
Tested on ubuntu & xubuntu | ||
|
||
Tested on ubuntu & manjaro | ||
For 64 bit systems only | ||
|
||
1. Make sure to have java 8 installed. | ||
2. Make sure the "apku" file has execute permissions. | ||
1. Make sure to have java 8+ installed on your computer. | ||
2. Make sure the `apku` file is executable. | ||
3. Place all your apk and jar files in the input folder. If zipaligning only, place them in the zipalign folder. | ||
4. Execute the file as follows in a terminal: `./apku` | ||
5. optional - Use the "Add Desktop Shortcut" option for quick access. | ||
5. Optional: Use the "Add Desktop Shortcut" option for quick access. | ||
|
||
**To use tags, install your framework files with tags(menu option 2).** | ||
|
||
## Framework Files | ||
|
||
As you probably know, Android apps utilize code and resources that are found on the Android OS itself. These are known as framework resources and [Apktool](https://ibotpeaches.github.io/Apktool/) relies on these to properly decode and build apks. | ||
|
||
Every [Apktool](https://ibotpeaches.github.io/Apktool/) release contains internally the most up to date AOSP framework at the time of the release. This allows you to decode and build most apks without a problem. However, manufacturers add their own framework files in addition to the regular AOSP ones. To use apktool against these manufacturer apks you must first install the manufacturer framework files. | ||
|
||
**To install framework files use menu options 1 or 2.** | ||
|
||
## Project Page | ||
|
||
https://techstop.github.io/apk-utility/ | ||
|
||
**Resources** | ||
- [apktool](https://ibotpeaches.github.io/Apktool/) | ||
## Resources | ||
|
||
**Special Thanks To:** | ||
- Connor Tumbleson | ||
- Ryszard Wiśniewski | ||
- [Apktool](https://ibotpeaches.github.io/Apktool/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.