[GUIDE] Modifying your own files - Galaxy S II General

There's certainly a lot of choice out there when it comes to firmware, however, I've found that a lot of custom ROMs on XDA include a lot of themes that I'm not really interested in.
Usually, when I find a modified file with the feature that I'm looking for, it also includes something else that I don't want. I've also seen a lot of posts in threads where people ask "Great! Can you make this mod for firmware version XXX?"
So I've decided to create this guide, it will show you how to look for changes to the files that developers post, so you can merge it with the file from your phone.
Prerequisites:
Latest Android-SDK downloaded and installed, with directories added to your PATH
Java runtime enviroment >= 1.6
Apktool, install instructions are on the page of this link
WinMerge installed
Your ROM is deodexed
In this example, I'm going to add Rawrat's green icons to my phone, but I don't want to add his modified transparant notification drop down. Rawrat at the time only provided files for XXKG6 but my personal ROM is based on XXKH3.
1. Create the following directory structure (this doesn't have to be named exactly as I have, it just keeps the files organised I find):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Download the developers modified files and place them in "Modded ROM files" - in my example, this is framework-res.apk and SystemUI.apk
3. Ensure USB debugging is enabled, connect phone via the USB cable. In windows command prompt, change directory to "Current ROM files" and pull the following files:
Code:
adb pull /system/framework/framework-res.apk
adb pull /system/framework/twframework-res.apk
adb pull /system/app/SystemUI.apk
You have to pull the framework-res.apk & twframework-res.apk if you're modifying most system applications. SystemUI.apk is the file I'm editing in this example. If you're modifying different ones to me or more, then pull those as well or instead of.
4. Whilst command prompt is in the same directory (Current ROM files), you'll need to install the framework files for Apktool to use:
apktool if framework-res.apk galaxy
apktool if twframework-res.apk galaxy
Click to expand...
Click to collapse
5. If the above worked correctly, you should have a message from apktool saying the framework was installed to 1-galaxy.apk and 2-galaxy.apk and your files should have been pulled into "Current ROM files":
6. Whilst command prompt is in the same directory (Current ROM files), we'll need to decompile the *.apks:
Code:
apktool d -t galaxy framework-res.apk framework-res
apktool d -t galaxy SystemUI.apk SystemUI
I'm not modifying twframework-res.apk, I just pulled that as it's a dependant file, so no need to decompile this unless it's one of the files the developer edited.
You shouldn't get any errors and it was successfully decompiled if it looks like so:
7. In command pompt, change to "Modded ROM Files" directory and decompile the developers files that we placed there earlier:
Code:
apktool d -t galaxy framework-res.apk framework-res
apktool d -t galaxy SystemUI.apk SystemUI
8. Now that we've decompiled both the current files on the phone and the modified ones, we're going to use WinMerge to compare the directories:
Open WinMerge and go to file -> open
For the left pane, click browse and browse to your "Current ROM files" folder, then framework-res, then click open
For the left pane, click browse and browse to your "Modded ROM files" folder, then framework-res, then click open
Check "Include subfolders" then click OK
8. Once WinMerge has compared the directories, go to view and make sure only the following is ticked in the top part of the view menu:
This basically shows all the files that are different between the two directories.
9. Now, we're going to look down the list of files that are different and copy them from right to left (Modified file to current file)
Exercise some caution here especially if you're applying the mod to a file that's from a different Samsung firmware. Usually when applying a mod to a different firmware version, you'll notice a lot of strings.xml differences listed. This is because Samsung have updated the translations for different languages. So don't copy these over.
Regarding other xml files, apktool inputs some entries into drawables.xml and public.xml so these files also show up as different. Again, don't copy these over.
Developers do make changes to xml files, either way, to ensure you're not over writing older xml documents with new ones, just right click the file and compare. As you can see, opening bools.xml, I can see there's a difference to:
Code:
<bool name="config_animateScreenLights">true</bool>
As Rawrat changed this to false to enable CRT-Off animation, I want this animation on my KH3 ROM. So I'm going to right click bools.xml and copy right to left.
Warning! Again, when dealing with two files from two different firmware bases, NEVER EVER copy any .smali files. This is because Samsung would have made changes most likely. Instead, compare the files as above and manually change the .smal file in the left pane with the changes the developer made. You can then save the file.
10. Repeat the WinMerge steps for the other decompiled application folders, in my example, I did the same for SystemUI.apk and to ensure I was only copying the green icrons for signal, WiFi and mobile data; I right clicked the different *.png files and chose open right with registered application. This opens the .png with your default image editor.
11. Go back to command prompt and change directory to your "Current ROM files" directory. Use apktool to compile:
Code:
apktool b framework-res
You should not receive any errors, apart from warnings about there not being any translation. Those errors are normal.
Obviously, compile all the other .apks too!
12. In Windows Explorer, navigate to the "Current ROM files"/framework-res/dist folder
This is the location of your newly compiled framework-res.apk with the changes you made. Open this apk with your archive editor (WinRar, 7zip, WinZip etc). Keep this open.
13. In Windows Explorer, navigate to the "Modded ROM files" folder
Open the original framework-res.apk with your archive editor, then drag the META-INF folder and AndroidManifest.xml file from the original .apk to the other archive editor window that has your modified .apk open.
Replace the files on your phone with the new ones!

wonderful guide for newbies like me. I am already off to start my first project.
Thanks once again.

This is AMAZING!
thank you very much! will be trying this very soon

Oh man, you are doing it the hard way!
APK Manager Ver 5.0 - Makes Modifying Ur Apk A Breeze (Windows/Linux)

designgears said:
Oh man, you are doing it the hard way!
APK Manager Ver 5.0 - Makes Modifying Ur Apk A Breeze (Windows/Linux)
Click to expand...
Click to collapse
That only serves the purpose of decompiling and building the application package in this example (obviously it can do more than just that), which replaces writing two commands per package. I wouldn't exactly call that the hard way around.
But yes, you can use APK Manager.

Mekrel said:
That only serves the purpose of decompiling and building the application package in this example (obviously it can do more than just that), which replaces writing two commands per package. I wouldn't exactly call that the hard way around.
But yes, you can use APK Manager.
Click to expand...
Click to collapse
Just wait until you do that 100 times a day when a new firmware hits
APK Manager is a time saver.

Advice on this for porting KG6 cam hack to KH3?

Thx for this guide and your time!! :-D

Related

[Tutorial]How to edit smali files // ZIP Kit prepared for you ^^

Tools needed :
My KIT for SMALI files (using options for each step )
Notepad++( Hexadecimal editor for *.xml )
This is an example of a smali file changed (in this case, Global.Actions.smali located in android.policy.jar)
_______________ Power Menu modded (smali changed) ______________
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open my zip kit ( recomended in a Theming Folder for example with apkmanager and all files you would like to mod )
What you get :
Baksmali
Baksmali ( executable Jar File )
Command.exe ( Shell file )
Notepad text with the two commands for decompile and compile already made for you ( just copy and paste into command.exe )
Smali
Smali ( executable Jar File )
1. So the only thing you need is to place your apk in the smali kit folder
2. To Decompile :
Code:
java -jar baksmali.jar -x yourfile -o classout
(classout folder can be renamed to whatever you want, doesnt matter until you dont forget to change the name too in the second command)
3. Make the modifications you want for smali files
4. To Compile again :
Code:
java -Xmx512M -jar smali.jar classout -o classes.dex
5. Copy and paste the file classes.dex into your apk _ you will overwrite the old one.
Thanks to Rafalense
Enjoy it
Thanks mate, it might be useful for some trick i'm gonna test.
Hi,
thanks for the guide and the advice.
But does the apk manager the smali decompile and compile too?
Could you give some hints where you can change what in smali?
Apk manager 4.9 and Smali/Baksmali
affmalg said:
Hi,
thanks for the guide and the advice.
But does the apk manager the smali decompile and compile too?
Could you give some hints where you can change what in smali?
Click to expand...
Click to collapse
Sorry for the late answer, have been busy with the last release of my theme
Apk manager decompile/compile xml files for apk
Smali/Baksmali decompile/compile smali files for apk
I am preparing a Tuto for both but a good start will be to check here and here
Yorzua said:
Apk manager decompile/compile xml files for apk
Smali/Baksmali decompile/compile smali files for apk
Click to expand...
Click to collapse
Okay now i got that
I am preparing a Tuto for both but a good start will be to check here and here
Click to expand...
Click to collapse
I know them both and they have been very helpful
But i would like to know more about things like that you deleted the powermenus headline.
I you have time could you look a that.
I just can't compile the apks any more, so my theme can't get an update
Apk manager 4.9 on xp windows
affmalg said:
Okay now i got that
I know them both and they have been very helpful
But i would like to know more about things like that you deleted the powermenus headline.
I you have time could you look a that.
I just can't compile the apks any more, so my theme can't get an update
Click to expand...
Click to collapse
affmalg said:
Hi guys,
I am using Apk manager 5.0 with the latest updates and apk tool 1.3.1
I want to decompile, edit and recompile my SystemUI.apk.
My Roms framework-res is set as 1.apk
Decompiling of SystemUI.apk works (no errors)
To check that compiling works, i edit nothing, just removed the "-v4" from the drawable-hpdi folder.
I assume that the must be something wrong with the resource, the framework-res.apk which i placed as 1.apk
"Resource is not public" is the error.
Does anyone no how to solve this?
The curious thing is that with the previous version of the rom it worked when i was making my theme a week ago.
Now it doesn't work any more
Click to expand...
Click to collapse
If you follow my Tuto, you should always use apk manager 4.9 editing framework as you want to mod xml __ even better with XP rather than any windows else.
Apk manager is not needed to decompile/recompile png's
you just forget zip and use instead 7zip which allow you to directly drag any file you want to another zip without decompiling/compiling.
Another rule is that you cant drag a xml from a zip to your hdd folder.
you must decompile the apk first. if the xml is already modded, then you can drag it everywhere and re-drag it where you want.
Never set framework-res as 1.apk
apk manager does everything for you, you just need to decompile,
set always level of compression to 0 in order to avoid issues during compilation work on the framework folder decompiled and just compile.
If you proceed step by step, you should be fine.
Note that systemUI.apk gives a lot of issues during decompilation
Smali files are included in systemUI so better use my tool for smali's files
Last one, i will prepare a tuto to take out the title in Power menu soon
If it helps you, please hit the thanks button
Sorry, a little OT, what's the name of the font?
font in my screenshots
grotesque02 said:
Sorry, a little OT, what's the name of the font?
Click to expand...
Click to collapse
The font in the screenshots is : Veggie burger
Hope it helps you
Thanks, and sorry for OT
Thread closed upon OP request.

[Guide] XML editing for framework(pictures included) Updated 240214

Hi all XDA members, today I am going to show you how to edit xml files in your framework-res.apk so you can edit auto - rotation on lockscreen or CRT - Animation. This does not apply to the Arc only, most Android phone's framework can be edited this way except maybe Samsung or HTC phones which have an extra resource file. This guide contains screenshots and is meant to be noob friendly so everything is self explanatory, you don't need a rocket scientist to explain everything.
What you need:
Framework-res.apk you want to edit
Apktool
Notepad++ is recommended for editing XMLs.
7-zip
So let's get started:
1. If you want to edit the framework file, naturally you should have extracted it from your phone. If you have not done so, the framework-res.apk can be found in system/framework/framework-res.apk(requires root access)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Place the file into apktool directory
4. Press shift and right click the directory(don't select any file, just press shift right click in the empty space of your apktool directory, you should see "Open command window here")
5. You should see a command window like this:
6. Type this command: apktool if framework-res.apk. You should get a response like this:
7. Now type this command:apktool d framework-res.apk. This will decompile your framework-res.apk so you can access the xml files.
8. Go back to your apktool file. You should see a new folder called framework-res(Yes, please take a good look. I circled it for your sake.)
9. Open the folder. go to res/values/bools.xml
10. Right click on file, select edit with Notepad++
11. Now open in Notepad++, you can edit and choose the functions you want to add just by editing the boolean with "true" or "false"
That's it, you are now ready to choose if you want auto rotation lockscreen or enable CRT animation.
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
At the request of some users, I have updated the thread with the compiling and signing steps as well, so please continue reading.
12. Firstly we need some files to sign the apks, so go to your original framework-res.apk, right click -> 7 zip -> Open Archive
13. Extract the folder "META-INF" and the file "AndroidManifest.xml" from the framework-res.apk
13a. Alternatively, you can find the files in <your framework-res folder> -> Original // No "<>" symbols, please see attached screenshot
14. Before we compile the framework, please rename the folder to avoid any conflicts with the existing framework-res.apk
15. Type this command: apktool b <your framework-res folder> and press Enter // No "<>" symbols, please see attached screenshot
16. You should get a response like this:
17. Go to <your framework-res folder> -> dist -> framework-res.apk // No "<>" symbols, please see attached screenshot
WARNING! DO NOT PUSH THIS FILE INTO YOUR PHONE YET. IT HAS NOT BEEN SIGNED AND WILL CAUSE A BOOTLOOP IF YOU PUSH IT TO /SYSTEM. PLEASE CHECK THAT THESE FEW STEPS HAVE BEEN COMPLETED BEFORE PUSHING IT TO /SYSTEM
18. Right click the file, go to 7-zip -> Open Archive
19. Select the files you extracted or received from step 10 or 10a
20. Drag and drop into 7-zip. You will get a warning message. Press "Yes".
21. You should have both files copied into the apk. You have signed the framework-res.apk and the file is OK for use.
22. Push the framework-res.apk into /system/framework, set RW-R--R-- permissions and reboot.
That's it. Your phone should be functioning normally and the changes you did internally should take effect.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
Also, please PM me or comment if you have questions.
If the question has been asked before, please read the previous posts if there are any.
Repeat questions will not be entertained.
popthosegaskets said:
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
Click to expand...
Click to collapse
Would be better keeping it all in one thread.
Sent from Myushi
XperienceD said:
Would be better keeping it all in one thread.
Sent from Myushi
Click to expand...
Click to collapse
Ok, thanks for the feedback
僕のLT18iから送られてきた
did you ever manage to get round to posting a recompiling guide??
Inside 4ndroid said:
did you ever manage to get round to posting a recompiling guide??
Click to expand...
Click to collapse
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
popthosegaskets said:
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Inside 4ndroid said:
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Click to expand...
Click to collapse
Ok... I shall redo this guide.
僕のLT18iから送られてきた
Thread content updated per user request.

[Tutorial] Set Default Theme When Building Rom

This tutorial is for people building roms based on CyanogenMod only !
This tutorial will explain how to use a custom CyanogenMod apk theme as the default when building roms
Things you will need
1. Java JDK and Java JRE installed
2. ApkTool - Download
3. Notepad++ - Download
4. Theme apk file
5. Your custom rom
Step 1
Download and extract apktool into a folder on the root of you drive, call the folder apk
Once extracted you you have three files like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2
If you have already packaged your rom use something such as WinRAR to extract it to a folder.
Once extracted it should look similar to this
Step 3
In your rom folder navigate to system/framework and look for the framework-res.apk file
It should look like this
Step 4
Copy the framework file to your apktool folder
Your apk tool folder should now look like thisView attachment 2484553
Step 5
Now copy your theme into the same folder
The folder should now look like thisView attachment 2484556
Step 6
Run command prompt and enter the following commands
Code:
cd C:\apk
Code:
apktool if framework-res.apk
Code:
apktool d <whatever your theme apk is called>.apk
Your CMD windows should now look like this
Step 6
Go back to your apktool folder and now you should have a folder called <your theme name>.apk
It will look like this View attachment 2484571
Step 7
Go inside that folder and open AndroidManifest.xml with Notepad++
Step 8
Once you open this file you need to look for two strings, they should look similar to these ones
Step 9
Once you have found these strings minimize the Notepad++ window and navigate back to your rom folder
Now navigate to system and open build.prop with Notepad++ and add these two lines
Code:
persist.sys.themeId=~~~~~~
persist.sys.themePackageName=+++++++++
Replace "~~~~~" with theme id from AndriodManifest.xml
Replace "+++++" with package name from AndroidManifest.xml
Mine would look like this
Now save build.prop
Step 10
Go to your rom folder and navigate to system/app and copy your theme apk inside of this folder
Now zip your rom back up and flash it
When your rom boots you should now see you custom theme
Note
If you cant get apktool to work and it keeps saying something along the lines of "java is not an exacutable command"
Make sure you have installed the Java SDK and Java JRE and navigate to C:\Program Files (x86)\java
and you should see a folder called "jdk1.7.0_45" or "jdk" with different numbers after it
Now go to control panel and on the right hand side click "Advanced System Settings"
Then click "environment variables"
Under "system variables" create a new variable and call it JAVA_HOME
In variable value put the path of your java sdk folder so it would be
C:\Program Files (x86)\Java\jdk<what ever numbers are here on your pc>
Or 32 bit users
C:\Program Files\Java\jdk<what ever numbers are here on your pc>
Now before you save the environment variable put the path in speech marks like this
Now save and reboot
And for CM12.1 its possible? Or CM11?? I try but not work :/

[Guide] How to make a Multilang package for official Motorola’s rom (4.4-)

How to make a Multilang package for official Motorola’s rom (4.4-):
What do you need? – Skills, patient, knowledge & time.
ONLY UNLOCKED BOOTLOADER & rooted device - if you dont have the firmware.
1. You need the same version of android (4.4.4, 5.0, etc) Nexus, GPE or Android One system apps.
Where do you find this? – In the system dumps – find in XDA’s thread or try Google search. If you dont found, try the factory images and you extract the system.img.
2. Install Android SDK with API 21 for the Lollipop systems & Java SDK.
3. the latest apktool.jar with aapt.exe & apktool.bat. Find it here. After download copy to C:\Windows path.
If you do not have access to C://Windows, you may place the three files anywhere then add that directory to your Environment Variables System PATH variable.
- security step 1: after the copying restart your sytem
- security step 2: install the framework-res.apk ---
a.) Put the apktool.jar & the framework-res.apk (grab from the downloaded system\framework folder) in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
b.) Open a command in this folder (like with TotalCommader ’cmd’ command) and type:
apktool if framework-res.apk
and press Enter
- if everything ok you see this:
Framework installed to: /users/…/apktool/framework/1.apk
4. I use BDFReak Advanced Apktool 4.1.0 for the process. Download & extract.
5. Copy the necesseary files to the extracted AdvancedApkTool 2-In folder.
- for example this is the necessary files:
app:
Bluetooth
Calculator
CellBroadcastReceiver
DeskClock
DownloadProviderUi
TelephonyProvider
- framework:
framework-res
- priv-app:
Contacts
ContactsProvider
Dialer
DownloadProvider
Keyguard
Launcher2
Mms
Settings
SettingsProvider
SystemUI
Teleservice
6. Run the Advanced ApkTool.exe – and Install the framework
- after then decompile the apps. The decompiled apk’s folders are in the [3-out] folder.
7. Delete the not necessary folders:
You need only the [res] folders from the decompiled apps and the [raw-] + [values-] folders from this parent folder. Save this folders!
Remains only the [raw- ] and the [values- ] folders.
Example: framework-res.apk\res\raw-HU,
framework-res.apk\res\values-HU
This folders contains the language .xmls & etc for the multilang apps.
After this process you have to save the decompiled apk’s folder to another folder. For example „Nexus 5.0 Extracted apps”.
8. Now you have to copy the system apps from your Motorola device to the AdvancedApkTool [2-In] folder and after decompiled the files.
9. Go to the „Nexus 5.0 Extracted app” and copy the corresponding app’s [res] folders to the Advanced Apktool [3-Out] folder apps.
No overwriting!!! Skipp all the existing folders, xmls!
10. Next step: Recompile the apps.
11. For safety I copy the original .apk's [META-INF] folder + AndroidManifest.xml to the new .apks, overwriting the existing ones.
(The original .apk is te [2-IN] folder, the new .apk is in the [4-OUT] folder. )
Now You are Done!
Next step - Making a flashable package.
I do not take any responsibility. Use at your own risk.
Nice work bro [emoji106]
▪◼ Tapatalk ♦ Moto G ◼▪
Good job
All this work with adding values folders isn't really hard but it takes time and I respect you for been doing this for a long time already.
S0bes said:
Good job
All this work with adding values folders isn't really hard but it takes time and I respect you for been doing this for a long time already.
Click to expand...
Click to collapse
Thank you very much! Previously, I started on the basis of your work. In the last few package with this method only 30 minutes the process, but there are too many other things prevents (another system.img, extract, files from another rom, etc...)
Thereafter I will focus only on the 2013 X.
Hi, are there any changes in your guide for 5.1 android?
machaj25 said:
Hi, are there any changes in your guide for 5.1 android?
Click to expand...
Click to collapse
As soon as I do for a multilang pack for the Moto G 2nd gen 5.1 (not released yet) or the "new" Moto G i refresh the OP.

APK Tool For Windows

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
APKTOOL FOR WINDOWS
First and foremost thanks to @iBotPeaches for his dedication to Apktool!
Because I can double-click more accurately than I can type, I made this up to avoid having to use command line and speed up modding the couple of apks that I try to keep up on. Maybe it'll help a few others speed up their process too.
Now, this is a Windows based GUI for Apktool. No command line needed. That said, you should be very familiar with already using Apktool via command line so you know the process that it follows and the corrective measures needed should errors pop up. You need to have the exact same setup as Apktool (Java in your environment path and current Java version AND relevant frameworks installed via apktool!! ). All that this does is provide a simple Windows style menu for the process. You can very easily update apktool.jar as @iBotPeaches updates it. Also, if you would like to add any switch to the decompile or compile command other than the typical (which is what I used) you can just modify the corresponding .bat file located in SupportFiles that APKTool For WIN calls on.
See the attached screenshots in the following post for the easy to follow layout and it's capabilities. It will install frameworks/etc, decompile, compile (with or without original manifest and meta-inf), sign (with testkey or your personal one), and display an apktool log.
As this directly uses apktool.jar, it will have the same quirks/issues such as this current one:
10/18/2016 - for apktool v2.2.1 regarding v2 signed apps - LINK​
V4 - As I was posting this, I noticed there was an update to apktool.jar (v2.2.1) which I updated the file to reflect. I modded several apps with the earlier version but only attempted two apps with the updated one (didn't see any issue with either app but I'm still on MM). I haven't looked more in depth at this V2 signed apps issue yet to see if I can modify the signing.bat to account for it (it's 230am). I will update it if there is.
V5 - (1) Updated apktool.jar to 2.2.2 if you haven't already yourself and (2) added java version info in your log file on Decompile routine to help identify a beginners issue on determining whether or not you have java installed in your path
Copy apks to the "APKs_To Decompile" folder.
Copy your framework-res, twframework-res, systemUI as needed to the folder "Frameworks".
Install frameworks.
Running the APKTool For WIN.exe select Install Frameworks
Decompile.
Select Decompile .apk
Choose your apk.
Decompiled app will be in the Decompiled folder.
Compile.
Select Compile
Choose your app to compile.
(One backup will be automatically created if there is an existing one to be safe in the decompiled app's folder)
Choose to copy the original manifest and meta-inf if desired
Compiled apk will be in the Compiled folder
Sign.
Select Sign APK
Choose the apk to sign.
Choose to sign with the testkey or with your personal key (help file is included in the zip for initial setup for using your own key)
Signed apk will be in the Signed folder
APKTool Log
If an Error message is displayed after decompiling or compiling you can check the log.
It's also beneficial to clear the log sometimes.
reserved for future use, faqs, issues
hmmm......after being away for a while i'm checking back to see if anyone had issues with trying to use this....and.......
not a single issue/question/comment with nearly 100 downloads. you guys are GOOD!!! (unless y'all think it's pointless and are being too kind to comment )
in the next few days, i'll use it a bit more in depth with the updated source and see if anything needs tweaking
Great tool !! I like it , this is solve my problems.
thank you so much , please keep it up.
Small update - V5
1. Updated to apktool 2.2.2 in case you haven't already done so yourself.
2. Added your java version info to the log generated when you run a Decompile routine to help beginners identify whether or not java is in the required path

Categories

Resources