Database Info

Hello! Need some help with apktool.

Hello! I'm new to the forum and a casual android modder. I've really enjoyed digging into the Android world and have learned a lot from the forum. I was working with apktool and ran into a bit of a problem. I searched and found a post indicating that the environmental variables had to be tweaked which I did but this did not resolve the problem.
Thanks in advance,
-Adam
Environmental variables:
PHP:
C:\>echo %PATH%
C:\DMI\WIN32\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime Alternative\QTSystem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\QuickTime Alternative\QTSystem\;C:\Program Files\ZipGenius 6\;C:\PROGRA~1\JPSoft\4dos; C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools
apktool commands (minus a few more lines of errors for length):
PHP:
C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>apktool d framework-res.apk
I: Loading resource table...
I: Decoding resources...
W: Cant find 9patch chunk in file: "drawable-mdpi/status_bar_header_background.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-mdpi/statusbar_background.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-mdpi/status_bar_close_on.9.png". Renaming it to *.png.
I: Copying assets and libs...
C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
libpng error: Read Error
ERROR: Failure processing PNG image C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\drawable-mdpi\status_bar_close_on.9.png
libpng error: Read Error
ERROR: Failure processing PNG image C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\drawable-mdpi\status_bar_header_background.9.png
libpng error: Read Error
ERROR: Failure processing PNG image C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\drawable-mdpi\statusbar_background.9.png
C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\values\public.xml:3342: error: Public entry identifier 0x1080252 entry index is larger than available symbols (index 594, total symbols 43).
C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\values\public.xml:3342: error: Public symbol drawable/APKTOOL_DUMMY_0252 declared here is not defined.
.
.
.
C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res\values\public.xml:3340: error: Public symbol drawable/zz_stat_sys_signal_5_cdma declared here is not defined.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\DOCUME~1\Owner\LOCALS~1\Temp\APKTOOL1107807157838832304.tmp, -x, -S, C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res, -M, C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\DOCUME~1\Owner\LOCALS~1\Temp\APKTOOL1107807157838832304.tmp, -x, -S, C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\res, -M, C:\Documents and Settings\Owner\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more

I also need some help with apktool. I'm trying to get into changing xml files on my Droid X. I've been able to successfully use the tool to decode apk files but i've heard that you can use it to decode xml files. Every time I try to do that though I get an error.
Included is a capture of the code I type in and the erros i'm getting with the xml file. I am trying to manipulate the simple eri.xml file that Verizon uses.

@adam-c
Could you upload original apk and zipped dir with decoded app? What is in these drawable-mdpi/status_bar_header_background.9.png, etc. files in decoded app? Are there both status_bar_header_background.9.png and status_bar_header_background.png (without ".9") files, but first one is empty or what?
@homes315
For now you can't decode single xml file - decode whole apk instead.

I have been searching for two days, and have tried everything I could find to figure this out, to no avail.
Could someone please help me get the apktool working on my computer?
when I enter apktool I get:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/object
From what I can tell I have my CLASSPATH and PATH set up correctly.
Any help would be greatly appreciated.
BTW, I am running Windows 7 64bit

framework-res.apk from ics leak decomplie/recomplie

anyone else had luck w decomplie and recomplie the stock framework-res file with apktool
It works if i start messing with other apks in the rom but not the framework.
I am missing something?
apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: /root/tools-apk/framework-res/res/drawable-sw600dp-hdpi
invalid resource directory name: /root/tools-apk/framework-res/res/values-w720dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw600dp-land
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw600dp-w1024dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw360dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-w480dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw600dp-w1280dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw600dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-sw400dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-w500dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-w360dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-h720dp
invalid resource directory name: /root/tools-apk/framework-res/res/layout-w600dp
invalid resource directory name: /root/tools-apk/framework-res/res/values-w600dp
invalid resource directory name: /root/tools-apk/framework-res/res/layout-sw400dp
invalid resource directory name: /root/tools-apk/framework-res/res/layout-sw600dp
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL2832548951564014427.tmp, -x, -S, /root/tools-apk/framework-res/res, -M, /root/tools-apk/framework-res/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(An drolibResources.java:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib .java:301)
at brut.androlib.Androlib.buildResources(Androlib.jav a:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL2832548951564014427.tmp, -x, -S, /root/tools-apk/framework-res/res, -M, /root/tools-apk/framework-res/AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(An drolibResources.java:191)
... 6 more

http://www.hive11.com/android/framework-res.apk heres the file

Works perfectly fine for me...
Sent from my Liberty using XDA

what version of apktool are you using

Newest, I believe
Sent from my Liberty using XDA

yeah this ones tricky...
lets call one oldapktool.jar and one apktool.jar
get in a directory with oldapktool.jar and framework-res.apk
rename oldapktool.jar to apktool.jar
install ur framework "apktool if framework-res.apk"
decompile ur framework "apktool d framework-res.apk"
????
overwrite apktool.jar with newer one (its 1.4.3)
compile ur framework "apktool b framework-res"
dont ask me why the older one does it. i have too many copies of apktool and aapt that i have to mix and match to take apart and put togeather apks.

still not working and aapt is there and the path is set right dont get it

mhx said:
still not working and aapt is there and the path is set right dont get it
Click to expand...
Click to collapse
are you on windows?

no linux ubuntu

Try with apktool 1.4.1
I have successfully decompiled it and all ICS apks I'm at school. im on windows though I have a procedure to do it
Sent from my SAMSUNG-SGH-I727 using xda premium

Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\mike>cd Desktop\forum
C:\Users\mike\Desktop\forum>dir
Volume in drive C has no label.
Volume Serial Number is 1E40-0F67
Directory of C:\Users\mike\Desktop\forum
03/29/2012 05:48 PM <DIR> .
03/29/2012 05:48 PM <DIR> ..
12/07/2011 09:38 PM 3,090,514 apktool.jar
03/29/2012 05:05 PM 8,272,966 framework-res.apk
03/29/2012 05:18 PM 2,676,027 oldapktool.jar
3 File(s) 14,039,507 bytes
2 Dir(s) 63,445,483,520 bytes free
C:\Users\mike\Desktop\forum>java -jar oldapktool.jar if framework-res.apk
I: Framework installed to: C:\Users\mike\apktool\framework\1.apk
C:\Users\mike\Desktop\forum>java -jar oldapktool.jar d framework-res.apk
I: Loading resource table...
I: Loaded.
I: Decoding file-resources...
I: Decoding values*/* XMLs...
I: Done.
I: Copying assets and libs...
C:\Users\mike\Desktop\forum>java -jar apktool.jar b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'gps_assisted_data_download' has no default translation in
C:\Users\mike\Desktop\forum\framework-res\res; found: ko
aapt: warning: string 'policydesc_allow_htmlemail' has no default translation in
C:\Users\mike\Desktop\forum\framework-res\res; found: en_US
aapt: warning: string 'policylab_allow_htmlemail' has no default translation in
C:\Users\mike\Desktop\forum\framework-res\res; found: en_US
aapt: warning: string 'wifi_p2p_pbc_go_negotiation_request_message' has no defau
lt translation in C:\Users\mike\Desktop\forum\framework-res\res; found: es
aapt: warning: string 'wifi_p2p_pin_display_message' has no default translation
in C:\Users\mike\Desktop\forum\framework-res\res; found: es
aapt: warning: string 'wifi_p2p_pin_go_negotiation_request_message' has no defau
lt translation in C:\Users\mike\Desktop\forum\framework-res\res; found: es
I: Building apk file...
C:\Users\mike\Desktop\forum>
so forget the aapt.exe and .bat from the zip i gave you.
for me its defaulting to the one in my system32 dir which is the latest from the android sdk. dont use any of the aapt from apktool. update your aapt via android sdk (for me its using sdk manager.exe which grabs all the sdk tools, not sure on ubnix)
then try it again
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
M0D1441 said:
Try with apktool 1.4.1
I have successfully decompiled it and all ICS apks I'm at school. im on windows though I have a procedure to do it
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
the one included in the zip i gave him is actually apktool1.4.2.31e6dc5 (oldapktool.jar)
i found i have to mix and match apktools and aapts depending on ics or gb apks and framework and systemui are even worse

It's weird it works for any other file in the rom except for this 1

compile with 1.4.3 and decompile with 1.4.2

i havent been able to decompile crap...

i got it working in windows but not linux
http://forum.xda-developers.com/showthread.php?t=1427959

yeah full time linux user here. I only fire up the windows machine if i need ODIN.

i use windows for desktop and do most of my dev work on a dedicated linux colo or my cloud server
{
"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"
}
i need lots bw!

mhx said:
i use windows for desktop and do most of my dev work on a dedicated linux colo or my cloud server
i need lots bw!
Click to expand...
Click to collapse
did you delete classes.dex before decompiling?

[TOOL][WINDOWS][LINUX] MoKee OpenSource Theme Fixer v2

If you are a MoKee OpenSource user, you will realise that the theme chooser is borked since MK43. Themes that used to work can't be used anymore, and if applied, the whole system will crash. A few months has passed since then, and now, we are glad to say that the solution is HERE AT LAST!!!
The Problem:
In MK43, we separated some parts of framework-res.apk into mokee-res.apk to ease development. However, this also broke theme chooser. Themes cannot find the resources they want to redirect anymore, but the weird thing is, certain themes could still function normally. So the long journey of debugging started, but no results....till recently, we found this:
https://code.google.com/p/tmobile-themes/wiki/NewGlobalThemeEngineDesign
The main point is at:
Resources are generated in the 0x0a package scope. This is designed to separate them in the AssetManager's ResTable. The framework currently uses 0x01 while application packages normally use 0x7f. The aapt tool was modified to support assigning arbitrary package scopes and so you must use the aapt tool found in the themes tree for building your own themes.
Click to expand...
Click to collapse
After decompiling a few problematic themes, res/values/public.xml was found to be populated with 0x02. The T-Mobile Theme Engine originally accepted only 0x0a, but CM made some changes so that others can be accepted as well. However, due to the major changes in MoKee, the changes lost its effect. Therefore, we have to revert to the default 0x0a. To achieve this, we need to recompile the theme APKs with custom made apktool and aapt.​
Requirements:
Must install JRE 1.7, you can get it here:
http://www.oracle.com/technetwor ... nloads-1880261.html
Windows users please follow this after installing: http://javarevisited.blogspot.co ... java-windows-7.html​
Windows Tutorial:
1. Download mokee-theme-fixer_[version number]-windows.zip and extract the folder named "mokee" in it.
{
"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. Open the "mokee" folder and you will see a few more folders. Place the APKs you want to fix into the folder named "input".
3. Run "mokee.bat" and let the magic happen!
4. If successful, the fixed APKs will be in the "output" folder, now named "done-[original name].apk".
Linux Tutorial:
1. Download mokee-theme-fixer_[version number]-linux.zip and extract the folder named "mokee" in it.
2. Open the "mokee" folder and you will see a few more folders. Place the APKs you want to fix into the folder named "input".
3. Execute "mokee.sh" and let the magic happen! (Remember to cd to that directory if using Terminal)
4. If successful, the fixed APKs will be in the "output" folder, now named "done-[original name].apk".​
Note:
1. The Windows version was developed and tested in Windows 8.1.
2. The Linux version was developed and tested in Ubuntu 12.04 LTS.
3. If you cannot execute the Linux version, please chmod 755 mokee/mokee.sh and mokee/tools/aapt.​
Credits:
Apktool developers:
- @Brut.all
- @iBotPeaches
win-bash (bash port for Windows) (too lazy to write a batch script...)
GNU utilities for Win32 (too lazy to write a batch script...)
Ultimate Packer for eXecutables (UPX)
Changelog:
Code:
[U]v1:[/U]
- Initial release
[U]v2:[/U]
- Fixed aapt not accepting uppercase letters and reduced size with strip and UPX
- Reduced size of Windows executables with strip and UPX
Downloads:
mokee-theme-fixer_v2 (Windows & Linux)​

Got following error when try to convert hue theme, any idea?
Code:
--------------------------------------
MoKee OpenSource Theme Fixer v1
Copyright 2012-2014
--------------------------------------
--> Processing HueWhiteKat_4.4.apk... <--
I: Using Apktool 2.0.0-Beta8 on HueWhiteKat_4.4.apk
I: Loading resource table...
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: framework\1.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling...
I: Copying assets and libs...
I: Copying unknown files/dir...
I: Copying original files...
I: Using Apktool 2.0.0-Beta8 on HueWhiteKat_4.4.apk
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
res\xml\com_alensw_PicFolder.xml: Invalid file name: must contain only [a-z0-9_.
]
res\xml\com_alensw_PicFolder.xml: Invalid file name: must contain only [a-z0-9_.
]
res\xml\com_keramidas_TitaniumBackup.xml: Invalid file name: must contain only [
a-z0-9_.]
res\xml\com_keramidas_TitaniumBackup.xml: Invalid file name: must contain only [
a-z0-9_.]
res\xml\com_quoord_tapatalkHD.xml: Invalid file name: must contain only [a-z0-9_
.]
res\xml\com_quoord_tapatalkHD.xml: Invalid file name: must contain only [a-z0-9_
.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.Androl
ibException: brut.common.BrutException: could not exec command: [tools\aapt.exe,
p, --min-sdk-version, 16, --target-sdk-version, 16, --version-code, 31, --versi
on-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp\APKTOOL4753921697499202546.tmp
, -x, 10, -I, framework\1.apk, -S, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\
res, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\AndroidManifest.xml]
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:434)
at brut.androlib.Androlib.buildResources(Androlib.java:362)
at brut.androlib.Androlib.build(Androlib.java:285)
at brut.androlib.Androlib.build(Androlib.java:258)
at brut.apktool.Main.cmdBuild(Main.java:236)
at brut.apktool.Main.main(Main.java:88)
Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not
exec command: [tools\aapt.exe, p, --min-sdk-version, 16, --target-sdk-version,
16, --version-code, 31, --version-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp
\APKTOOL4753921697499202546.tmp, -x, 10, -I, framework\1.apk, -S, C:\mokeeThemeF
ixerv1\tmp\HueWhiteKat_4.4.apk\res, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4
.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:470)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:415)
... 5 more
Caused by: brut.common.BrutException: could not exec command: [tools\aapt.exe, p
, --min-sdk-version, 16, --target-sdk-version, 16, --version-code, 31, --version
-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp\APKTOOL4753921697499202546.tmp,
-x, 10, -I, framework\1.apk, -S, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\re
s, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:89)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:464)
... 6 more
Done if no errors above!
Press enter to exit...
Terminate batch job (Y/N)?

antutu said:
Got following error when try to convert hue theme, any idea?
Code:
--------------------------------------
MoKee OpenSource Theme Fixer v1
Copyright 2012-2014
--------------------------------------
--> Processing HueWhiteKat_4.4.apk... <--
I: Using Apktool 2.0.0-Beta8 on HueWhiteKat_4.4.apk
I: Loading resource table...
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: framework\1.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling...
I: Copying assets and libs...
I: Copying unknown files/dir...
I: Copying original files...
I: Using Apktool 2.0.0-Beta8 on HueWhiteKat_4.4.apk
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
res\xml\com_alensw_PicFolder.xml: Invalid file name: must contain only [a-z0-9_.
]
res\xml\com_alensw_PicFolder.xml: Invalid file name: must contain only [a-z0-9_.
]
res\xml\com_keramidas_TitaniumBackup.xml: Invalid file name: must contain only [
a-z0-9_.]
res\xml\com_keramidas_TitaniumBackup.xml: Invalid file name: must contain only [
a-z0-9_.]
res\xml\com_quoord_tapatalkHD.xml: Invalid file name: must contain only [a-z0-9_
.]
res\xml\com_quoord_tapatalkHD.xml: Invalid file name: must contain only [a-z0-9_
.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
res\xml\vStudio_Android_Camera360.xml: Invalid file name: must contain only [a-z
0-9_.]
Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.Androl
ibException: brut.common.BrutException: could not exec command: [tools\aapt.exe,
p, --min-sdk-version, 16, --target-sdk-version, 16, --version-code, 31, --versi
on-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp\APKTOOL4753921697499202546.tmp
, -x, 10, -I, framework\1.apk, -S, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\
res, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\AndroidManifest.xml]
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:434)
at brut.androlib.Androlib.buildResources(Androlib.java:362)
at brut.androlib.Androlib.build(Androlib.java:285)
at brut.androlib.Androlib.build(Androlib.java:258)
at brut.apktool.Main.cmdBuild(Main.java:236)
at brut.apktool.Main.main(Main.java:88)
Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not
exec command: [tools\aapt.exe, p, --min-sdk-version, 16, --target-sdk-version,
16, --version-code, 31, --version-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp
\APKTOOL4753921697499202546.tmp, -x, 10, -I, framework\1.apk, -S, C:\mokeeThemeF
ixerv1\tmp\HueWhiteKat_4.4.apk\res, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4
.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:470)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:415)
... 5 more
Caused by: brut.common.BrutException: could not exec command: [tools\aapt.exe, p
, --min-sdk-version, 16, --target-sdk-version, 16, --version-code, 31, --version
-name, 4.4, -F, C:\Users\XX\AppData\Local\Temp\APKTOOL4753921697499202546.tmp,
-x, 10, -I, framework\1.apk, -S, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\re
s, -M, C:\mokeeThemeFixerv1\tmp\HueWhiteKat_4.4.apk\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:89)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:464)
... 6 more
Done if no errors above!
Press enter to exit...
Terminate batch job (Y/N)?
Click to expand...
Click to collapse
Owh, that's caused by having capital letters in the package name...have to patch aapt for that but haven't found out how...

Worked for (Holo Glass Beta) theme on my Maguro..Thanks!!

antutu said:
Got following error when try to convert hue theme, any idea?
Click to expand...
Click to collapse
Fixed aapt and usable now...
So with that, v2 is released! Changelogs and links in first post!

yes it's working :good: :good:
you just made my day

well can some one help me out here ?? pls
i followed each and every step ( theme chooser !!)
downloaded everything converted the file
and yes it was successful
but whats the actual procedure to replace the app??
i tried moving the new system app to /system/app folder it was successful
but when i go to settings and hit theme am getting unfortunately system stopped
also tried several reboots and also tried to delete the system Themechooser.apk
no use now cant even access my theme choose option
the part of converting files is perfect am assuming
bt transfer to mobile is causing me probs
thanks in advance

*Facepalm*...you are supposed to convert the theme apk you want and install as normal...not Themechooser.apk... don't touch that at all...and don't cross post please...

I have here is off

I have several errors during the extracting process of mokee-theme-fixer_v2-windows.zip. I have Win7 64bits.

lolo696 said:
I have here is off
Click to expand...
Click to collapse
Corrupted APK...
Primokorn said:
I have several errors during the extracting process of mokee-theme-fixer_v2-windows.zip. I have Win7 64bits.
Click to expand...
Click to collapse
Redownload...corrupted zip...

Ryuinferno said:
Redownload...corrupted zip...
Click to expand...
Click to collapse
Still the same. No error with v1 though...

Primokorn said:
Still the same. No error with v1 though...
Click to expand...
Click to collapse
Already tested...no issues here...try using another program like winRar

This theme works perfectly on my Tmobile S3 with latest nightly
Sent from my SGH-T999 using Tapatalk

can any one recompile this cm11 theme for me
https://www.dropbox.com/s/rctpn20me...r_icons_v19.apk?_e_pi_=7,PAGE_ID10,8751703549
i don't have pc
thanks in advance
Sent from my LG OPTIMUS 4X HD using Tapatalk Pro

akshay.mehta9 said:
can any one recompile this cm11 theme for me
https://www.dropbox.com/s/rctpn20me...r_icons_v19.apk?_e_pi_=7,PAGE_ID10,8751703549
i don't have pc
thanks in advance
Sent from my LG OPTIMUS 4X HD using Tapatalk Pro
Click to expand...
Click to collapse
I'm sorry, this theme does not work. The other theme function properly. I do not know why. [emoji780][emoji780][emoji780]
Best regards

varadinum said:
I'm sorry, this theme does not work. The other theme function properly. I do not know why. [emoji780][emoji780][emoji780]
View attachment 2629603
Best regards
Click to expand...
Click to collapse
varadinum said:
I'm sorry, this theme does not work. The other theme function properly. I do not know why. [emoji780][emoji780][emoji780]
View attachment 2629603
Best regards
Click to expand...
Click to collapse
no matter but which themes are working without recompile
Sent from my LG OPTIMUS 4X HD using Tapatalk Pro

This is a beautiful Mac Theme
Best regards

At last.. working like a charm, thank you!
Subscribed!
Win8 x64

Hmmm....one question....can we use our own rom framework-res.apk for this fixer?

[Tool] WhatsApp ADB Patch

UPDATE:
This app is now obsolete as there is now a workaround to re-enable ADB using WhatsApp Key/DB Extractor.
SUMMARY:
The purpose of this script is to patch new versions of WhatsApp so the ADB backup method will continue to function.
This will allow apps such as Helium or Crypt Key File Extractors to continue backing up WhatsApp data over the ADB.
PREREQUISITES:
O/S: Windows Vista, Windows 7 or Windows 8/8.1
Java - If not installed: Download Java
Old WhatsApp MUST be removed from your device
INSTRUCTIONS:
Extract WhatsAppADBPatch.zip maintaining the directory structure.
Download latest WhatsApp.apk from: https://www.whatsapp.com/android/
Copy WhatsApp.apk into the same directory as ADBPatch.bat.
Drag WhatsApp.apk onto ADBPatch.bat.
Install the created WhatsApp_Patched.apk on your android device.
AUTHOR: TripCode
THANKS: Brut.all / iBotPeaches (Apktool) and Lionello Lunesu for FART (Find And Replace Text)

i get this error
this error keeps coming

m.a.r.k.i.94 said:
this error keeps coming
Click to expand...
Click to collapse
I think you are running WhatsApp Key/DB Extractor and not WhatsApp ADB Patch?
In any case your issue is because the latest version of WhatsApp blocks adb which is why this thread exists.

TripCode said:
I think you are running WhatsApp Key/DB Extractor and not WhatsApp ADB Patch?
In any case your issue is because the latest version of WhatsApp blocks adb which is why this thread exists.
Click to expand...
Click to collapse
sir
1.i downloaded latest whatsapp from website
2.patched the apk with the ADB patch
3.removed the existing one i had in my phone and installed the patched apk
4.then i went on to extract the key file using WhatsApp Key/DB extractor. i get the error then

m.a.r.k.i.94 said:
sir
1.i downloaded latest whatsapp from website
2.patched the apk with the ADB patch
3.removed the existing one i had in my phone and installed the patched apk
4.then i went on to extract the key file using WhatsApp Key/DB extractor. i get the error then
Click to expand...
Click to collapse
Double check that you have installed the patched apk. If still no joy try using WhatsApp-Key-DB-Extractor which some people have more success with.
Also, remember to take a manual backup of your whatsapp database after you install whatsapp (this process creates the crypt key). Another thing you could try is simply install an older official version of whatsapp that do not block adb and run the key extractor on the older version. Once you have the key you can then upgrade to the new version. Your key will stay the same.

I am getting error when tried to install whatsapp after the patch.
It seems like client has been updated please install the version from playstore. Whatsapp not letting me to activate.
Thanks,
-Sri

When trying to patch the newest Whatsapp-Version (2.11.491), I got the following errors. 2.11.481 worked.
Code:
C:\Users\xxx\WhatsAppKeyExtract>ADBPatch.bat WhatsApp.apk
I: Decompiling APK
I: Using Apktool 2.0.0-ec3fbf-SNAPSHOT on WhatsApp.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: C:\Users\xxx\apktool\framework\1.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling classes.dex...
testCleaning up unclosed ZipFile for archive C:\Users\xxx\apktool\framework\1.apk
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
I: Patching AndroidManifest.xml
I: Recompiling APK
I: Using Apktool 2.0.0-ec3fbf-SNAPSHOT on WhatsApp
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_corrupt_installation.xml:7: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_corrupt_installation.xml:12: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_incorrect_app_release_version.xml:8: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_insufficient_storage_space.xml:8: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_spam_warning.xml:5: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\activity_spam_warning.xml:8: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\backup_restore.xml:22: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\backup_restore.xml:23: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\qr_code.xml:5: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\qr_code.xml:11: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\voip_activity.xml:4: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\layout\voip_activity.xml:40: error: No resource identifier found for attribute 'fontFamily' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\xml\widget_info.xml:2: error: No resource identifier found for attribute 'initialKeyguardLayout' in package 'android'
C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res\xml\widget_info.xml:2: error: No resource identifier found for attribute 'widgetCategory' in package 'android'
Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [C:\Users\xxx\AppData\Local\Temp\brut_util_Jar_665076819065385106.tmp, p, --forced-package-id,127, --min-sdk-version, 7, --target-sdk-version, 21, --version-code, 450227, --version-name, 2.11.491, -F, C:\Users\xxx\AppData\Local\Temp\APKTOOL3245343448066818719.tmp, -0, arsc, -I, C:\Users\xxx\apktool\framework\1.apk, -S, C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res, -M,C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\AndroidManifest.xml]
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:437)
at brut.androlib.Androlib.buildResources(Androlib.java:374)
at brut.androlib.Androlib.build(Androlib.java:277)
at brut.androlib.Androlib.build(Androlib.java:250)
at brut.apktool.Main.cmdBuild(Main.java:225)
at brut.apktool.Main.main(Main.java:84)
Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [C:\Users\xxx\AppData\Local\Temp\brut_util_Jar_665076819065385106.tmp, p, --forced-package-id, 127, --min-sdk-version, 7, --target-sdk-version,21, --version-code, 450227, --version-name, 2.11.491, -F, C:\Users\xxx\AppData\Local\Temp\APKTOOL3245343448066818719.tmp, -0, arsc, -I, C:\Users\xxx\apktool\framework\1.apk, -S, C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res, -M, C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:488)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:423)
... 5 more
Caused by: brut.common.BrutException: could not exec command: [C:\Users\xxx\AppData\Local\Temp\brut_util_Jar_665076819065385106.tmp, p, --forced-package-id, 127, --min-sdk-version, 7, --target-sdk-version, 21, --version-code, 450227, --version-name, 2.11.491, -F, C:\Users\xxx\AppData\Local\Temp\APKTOOL3245343448066818719.tmp, -0, arsc, -I,C:\Users\xxx\apktool\framework\1.apk, -S, C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\res, -M, C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:89)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:482)
... 6 more
I: Signing APK
java.io.FileNotFoundException: C:\Users\xxx\WhatsAppKeyExtract\WhatsApp\dist\WhatsApp.apk (Das System kann den angegebenen Pfad nicht finden)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at com.android.signapk.SignApk.main(SignApk.java:320)
WhatsApp\smali\com - Das Verzeichnis ist nicht leer.
I: Done!

Would it be possible for the OP to atleast mention a version number. Just writing latest is vague. Being specific would be very kind.
Sent from my D5503 using XDA Free mobile app

pathaniya said:
Would it be possible for the OP to atleast mention a version number. Just writing latest is vague. Being specific would be very kind.
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
Tried on Z1 compact Kitkat 14.4.A.0.157 and whatsapp 2.11.481, also the Version 2.11.514 (latest) patched it didn't work. Mine is not rooted.
Thanks.

Hello everyone. first of all apologize for my English, I speak very little English ^^'. I'm a new user in XDA developers.
I used the patch and it has worked perfectly.
I have also installed and working without error. Thanks for your post ^^
I have android 4.2.1 Jelly bean and I'm root.

Thanks
Hey, I just came across an interesting issue when trying to install the patched apk - when verifying my number whatsapp gave me an error message saying that the version of whatsapp I was trying to install had been modified. Is there a work-around for this?
So annoying, why do they make it so hard for us to read our whatsapp messages on our PCs?!

Same as iceiceicex here.
Moreover, when I installed the older version, should I need to initialize/activate/register it first?
If I don't initialize/activate/register it first, the key extract replied that something like the path not found....
If I try to initialize/activate/register it first, it requires me to update to the latest version first....
As a result, I can't get the key in any ways....

install apk from pc to phone
Hi,
How could I install the patched apk to the phone via pc?
what kind of program should I use?
thank you

Hunkit said:
When trying to patch the newest Whatsapp-Version (2.11.491), I got the following errors. 2.11.481 worked.
Click to expand...
Click to collapse
Most likely as needed the latest version of apktool. I have updated the zip file.
pathaniya said:
Would it be possible for the OP to atleast mention a version number. Just writing latest is vague. Being specific would be very kind.
Click to expand...
Click to collapse
The patch is a wrapper for apktool so is therefore independent of any WhatsApp version numbers (the version is irrelevant). If it breaks then you will need to replace apktool.jar with the latest version. I have just updated the zip file in the first post.

Patch Whatsapp
Hello guys,
I’m tryin’ to patch the latest Whatsapp version (2.12.30) using WhatsAppADBPatch.zip (which was updated a few hours ago by TripCode).
However an error is displayed during the patching process:
Building resources... :\Users\alex\Downloads\WhatsAppADBPatch\WhatsApp\res\layout-v16\activity_corr tpt_installation.xml:7: error: No resource identifier found for attribute 'fontF mily' in package
I should mention that I have installed the latest Java version and tried this procedure on 2 different PCs (with W7 & W8).
Is there someone who has successfully patched this Whatsapp version?
If the answer is no then I will be very grateful if anyone of you can attach a patched Whatsapp version higher than 2.11.481 (this version will be outdated in a few days).
Thank you in advance!

Thanks for the useful pos
TripCode said:
UPDATE:
This app is now obsolete as there is now a workaround to re-enable ADB using WhatsApp Key/DB Extractor.
SUMMARY:
The purpose of this script is to patch new versions of WhatsApp so the ADB backup method will continue to function.
This will allow apps such as Helium or Crypt Key File Extractors to continue backing up WhatsApp data over the ADB.
PREREQUISITES:
O/S: Windows Vista, Windows 7 or Windows 8/8.1
Java - If not installed: Download Java
Old WhatsApp MUST be removed from your device
INSTRUCTIONS:
Extract WhatsAppADBPatch.zip maintaining the directory structure.
Download latest WhatsApp.apk from: https://www.whatsapp.com/android/
Copy WhatsApp.apk into the same directory as ADBPatch.bat.
Drag WhatsApp.apk onto ADBPatch.bat.
Install the created WhatsApp_Patched.apk on your android device.
AUTHOR: TripCode
THANKS: Brut.all / iBotPeaches (Apktool) and Lionello Lunesu for FART (Find And Replace Text)
Click to expand...
Click to collapse
thanxx a lot brofor this help

Apktool.jar common errors and solutions

As I'm no longer modding, this thread will not be updated anymore. Please refer to apktool issues https://github.com/iBotPeaches/Apktool/issues?q=is:issue++ and discussions https://github.com/iBotPeaches/Apktool/discussions for latest infomation
Since many got apktool.jar errors and don't know how to search or solve themself, I decided to explain and provide solutions here with links to Github. I have a friend who sometime can help me with this.
I will do my best to get much info. Feel free to post your thoughts
Know your error:
There’s a wide range of error messages you may encounter when decompiling and compiling your app. Depending on the kind of error you encounter, apktool.jar will always display the error message. Spotting error messages is easy
For example this log:
Code:
I: Using Apktool 2.4.1
I: Smaling smali folder into classes.dex...
I: Smaling smali_classes2 folder into classes2.dex...
I: Building resources...
W: D:\xxx\AndroidManifest.xml:15: Tag <uses-permission> attribute name has invalid character ' '.
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\evildog1\AppData\Local\Temp\brut_util_Jar_2200487015856364895.tmp, p, --forced-package-id, 127, --min-sdk-version, 19, --target-sdk-version, 28, --version-code, 19227, --version-name, 4.1.1, --no-version-vectors, -F, C:\Users\evildog1\AppData\Local\Temp\APKTOOL3877124333918122178.tmp, -e, C:\Users\evildog1\AppData\Local\Temp\APKTOOL2736431752124554942.tmp, -0, arsc, -I, C:\Users\evildog1\AppData\Local\apktool\framework\1.apk, -S, D:\xxx\res, -M, D:\xxx\AndroidManifest.xml]
If you think could not exec is your error, it's actually not, the real error is actually a 'warning'
Code:
W: D:\APK Easy Tool\1-Decompiled APKs\xxx\AndroidManifest.xml:15: Tag <uses-permission> attribute name has invalid character ' '
The good thing it tells you which line it occured AndroidManifest.xml:15:. it's line 15 in AndroidManifest.xml
This was caused by a space in a permission tag. Removing it will fix the compiling error
{
"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"
}
It's not always a simple fix. This always depending
Check the APK file:
Sometimes APK is obfuscated in many ways.
Open the APK using 7-zip and WinRar and see if the first classes.dex is smaller than 500 KB or way bigger than 10 MB. If so, it a sign it's encrypted. Decompiling and compiling the big dex file will result in a smaller size and it will fail to decrypt due to missing encrypted block
Decompile and check if smali files and codes are obfuscated. This is an example of Netflix app that is obfuscated
Don't ask me how to break protected APK, I'm not a reverser so I can't help you with it.
Troubleshooting:
Sometime those troubleshooting tricks helps fixing errors. Please try one or more of the following below
- If you are using any 3rd party GUI tools, please try the actual apktool.jar with CMD first
- Use latest version of apktool.jar: https://ibotpeaches.github.io/Apktool/ and test
- If you are using latest version, try use older version of apktool.jar. Sometimes it can mitigate the issue
- Clear framework apktool empty-framework-dir --force and decompile the APK again.
- Decompile APK with --only-main-classes (Only disasemble dex classes in root (classes[0-9].dex). Prevents disasemble dex from assets folder) (apktool 2.4.1 and up only)
- Decompile APK with --no-res if you are only editing Java (smali) (--no-res will prevent the decompile of resources. This keeps the resources.arsc intact without any decode.)
- Decompile APK with --no-src if you are only editing the resources (xml) (--no-src will prevent the disassembly of the dex file(s). This keeps the apk dex file(s) and simply moves it during build.)
- Compile with --use-aapt2 (Use the aapt2 binary instead of appt)

Errors list:
Tip: Press CTRL + F and find the words
If there is no error you are looking for, search it on following Github issue pages
Apktool: https://github.com/iBotPeaches/Apktool/issues
Baksmali/smali: https://github.com/JesusFreke/smali/issues
Deompile errors:
* Exception in thread "main" java.lang.NullPointerException (XML related)
This is an issue with apktool 2.4.1. Downgrade to 2.4.0 or below (2.3.4 is better)
* Exception in thread "main" org.jf.dexlib2.dexbacked.DexBackedDexFile$NotADexFile: Not a valid dex magic value: (xx xx xx xx xx xx xx xx)
Rare issue, it usally caused if it tries to decompile encrypted dex from assets folder
Decompile APK with --only-main-classes
* Exception in thread "main" brut.androlib.AndrolibException: brut.directory.DirectoryException: Error copying file: res
This is a trick to prevent decompiling on Windows. Open the APK file using 7zip or Winrar and delete the unnamed file from res folder
Or use Mac/Linux until then
See: https://github.com/iBotPeaches/Apktool/issues/1460
* Invalid debug offset
These are legitimate warnings about inconsistencies in the dex file. The invalid debug offset is otherwise ignored and the classes are successfully disassembled.
Compile errors:
* brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = -1073741515)
This was an issue with Java 8 32-bit on Apktool 2.4.0. Install 64-bit of Java or switch to other version
See: https://github.com/iBotPeaches/Apktool/issues/2141
* Cant find 9patch chunk in file: (...). Renaming it to *.png.
APK is Obfuscated
See: https://forum.xda-developers.com/showpost.php?p=81088145&postcount=619
* Cannot run program "aapt": CreateProcess error=2, The system cannot find the file specified
Not a bug. This means the default application that is copied to tmp and executed, could not be done. Therefore it relied on the aapt binary being accessible in the $PATH variable.
* Class (...) has already been interned
Decompile APK with --only-main-classes (apktool 2.4.1 and up only)
* Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
apktool.yml does not exist, because APK did not decompiled completely. Decompile again
* Float types not allowed
Remove the decimal from version number maybe?
Reported issue: https://forum.xda-developers.com/showpost.php?p=82840671&postcount=699
* Invalid resource directory name
Currently unknown. Try clear framework if you don't work with system apps
* Invalid file name: must contain only (...). Ignoring...
See: https://github.com/iBotPeaches/Apktool/issues/2282
* JAXP 1.5 Support is required to validate XML
Update apktool.jar to the latest version
* No resource identifier found for attribute 'isSplitRequired' in package 'android'
Split APK is not supported yet. See https://github.com/iBotPeaches/Apktool/issues/2218
If you are following some tutorials how to merge split apks into one, then remove the attribute android:isSplitRequired="true" from AndroidManifest.xml, save and compile again
* No resource identifier found for attribute (...) in package (...)
There are many reasons why. Please refer to these issues for more infomation: https://github.com/iBotPeaches/Apktool/issues?q=No+resource+identifier+found+for+attribute+
Try clear framework if you don't work with system apps
Sometimes, removing the attribute will fix the error and the app would run fine without it. Always test if the app is working fine or not
* No resource found that matches the given name
There are many reasons why. This is not always easy to fix
See issues
https://github.com/iBotPeaches/Apktool/issues/2365
https://github.com/iBotPeaches/Apktool/issues/2362
https://github.com/iBotPeaches/Apktool/issues/2339
https://github.com/iBotPeaches/Apktool/issues/2422
Try clear framework if you don't work with system apps
If you are working with system apps, you may need framework installed.
* Tag (...) missing required attribute name.
Not an easy fix, but you can try --use-aapt2 or don't decode resources (-r, --no-res) if you don't need
https://github.com/iBotPeaches/Apktool/issues/1880
Tag <uses-permission> attribute name has invalid character ' '
This was caused by a space in an attribute name. Removing it will fix the compiling error
Example, change:
Code:
<uses-permission android:name="com.google.android.finsky.permission.CHECK_LICENSE "/>
to
Code:
<uses-permission android:name="com.google.android.finsky.permission.CHECK_LICENSE"/>
* Unsupported res type name for bags
See: https://github.com/iBotPeaches/Apktool/issues/1719
* Unsigned short value out of range: 65536
You have too many methods. The method index can't fit into an unsigned 16-bit value each dex
Simply move your codes to smali_classes(X) or create new one. For example if smali_classes2 is the latest, move code to smali_classes3
Full error log:
Code:
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method Lcom/mintegral/msdk/thrid/okhttp/internal/publicsuffix/PublicSuffixDatabase;->findMatchingRule([Ljava/lang/String;)[Ljava/lang/String;
at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1046)
at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:345)
at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:300)
at org.jf.smali.Smali.assemble(Smali.java:131)
at org.jf.smali.AssembleCommand.run(AssembleCommand.java:96)
at org.jf.smali.Main.main(Main.java:100)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x52
at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1319)
at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1042)
... 5 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65536
at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1279)
... 6 more
* warning: found plain 'id' attribute; did you mean the new 'android:id' name?
See: https://github.com/iBotPeaches/Apktool/issues/2188
* warning: string (...) has no default translation.
Those are warnings, they are fine.
* WARNING: Could not write to (C:\Users\(username)\AppData\Local\apktool\framework), using C:\Users\(username)\AppData\Local\Temp\ instead...
Use the --frame-path [folder] parameter and describing the folder you want the framework resources to reside.
This warning can be ignored if you don't use framework
Others:
* 'java' is not recognized as an internal or external command
Install/Re-install latest version of Java 8 https://java.com/en/download/ or set the enviorment path manually
* APKTOOL_DUMMY
If you get APKTOOL_DUMMY that's generally because apktool can't decode some of the information in the original APK and creates a 'dummy' value instead. Because there's no things called APKTOOL_DUMMY in public.xml, the APK can't be recompiled. It's likely because you try to compile splitted APK with some missing infomation
* Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
Increase the java heap size like:
java -Xmx4096m -jar apktool.jar
java -Xmx4g -jar apktool.jar
If your system is Windows and is 64-bit, please uninstall 32-bit version and install 64-bit version (Windows Offline (64-bit)) https://java.com/en/download/manual.jsp
* Unsupported major.minor version (...)
Upgrade java to the latest version https://java.com/en/download/

ppst reserved 2

Updated. If you found more errors, please let me know

i have res relative problem, can anyone solve this

evildog1 said:
Updated. If you found more errors, please let me know
Click to expand...
Click to collapse
why I get this type of error

lokesh.Dewangan said:
why I get this type of error
Click to expand...
Click to collapse
Try
Code:
--use-aapt2

i get this error when decompile classes.dex :
Lcom/ano/gshell/AnoApplication;-><clinit>()V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;-><init>()V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->dec(Ljava/lang/String;)Ljava/lang/String;: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->dec(Ljava/lang/String;)Ljava/lang/String;: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->attachBaseContext(Landroid/content/Context;)V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->attachBaseContext(Landroid/content/Context;)V: Invalid debug offset
and then after recompile the app and install the app works then exit in lobby
but when i use --no-src the app work without crash but i cant edit smali like that.
this is the app link try decompile and recompile dex file.
Download

I have a little problem described here, would you look at it?
Thx

Hello, when I try to compile I get an error, could you please help me.
Thank you
Code:
Checking for update...
Compiling APK file... (Press ESC to cancel)
Executing command: java.exe -jar "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\Apktool\apktool_2.5.0.jar" b -d -f --use-aapt2 -o "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\2-Recompiled APKs\Teba_19.3.apk" "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3"
I: Using Apktool 2.5.0
I: Smaling smali folder into classes.dex...
I: Building resources...
I: Using aapt2 - setting 'debuggable' attribute to 'true' in AndroidManifest.xml
W: C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\res: error: failed to open directory: El sistema no puede encontrar el archivo especificado. (2).
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\JOSAND~1\AppData\Local\Temp\brut_util_Jar_131902690237150689966905402769991619447.tmp, compile, --dir, C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\res, --legacy, -o, C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\build\resources.zip]
Compile failed. Please read the log

When you write:
"Sometimes, removing the attribute will fix the error and the app would run fine without it. Always test if the app is working fine or not"
where i can do it, removing the attribute ?
My error is:
W: C:\Users\Marco\Documents\APK Easy Tool\1-Decompiled APKs\XRecorder_v2.1.1.1__Arm7_Pro__UserUpload.Net\res\layout\a0.xml:2: error: No resource identifier found for attribute 'paddingBottomNoButtons' in package 'videoeditor.videorecorder.screenrecorder'
etc...
Thank
Hispa

Sorry for very late reply guys
tahooo said:
i get this error when decompile classes.dex :
Lcom/ano/gshell/AnoApplication;-><clinit>()V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;-><init>()V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->dec(Ljava/lang/String;)Ljava/lang/String;: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->dec(Ljava/lang/String;)Ljava/lang/String;: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->attachBaseContext(Landroid/content/Context;)V: Invalid debug offset
Lcom/ano/gshell/AnoApplication;->attachBaseContext(Landroid/content/Context;)V: Invalid debug offset
and then after recompile the app and install the app works then exit in lobby
but when i use --no-src the app work without crash but i cant edit smali like that.
this is the app link try decompile and recompile dex file.
Download
Click to expand...
Click to collapse
Sounds like the app has a protection against tampering. I cannot help with that
gidano said:
I have a little problem described here, would you look at it?
Thx
Click to expand...
Click to collapse
I believe it has been fixed https://github.com/iBotPeaches/Apktool/pull/2650
Try using latest commit of apktool.jar (Requires Github account to download) https://github.com/iBotPeaches/Apktool/actions/runs/1712896706
Jaloga said:
Hello, when I try to compile I get an error, could you please help me.
Thank you
Code:
Checking for update...
Compiling APK file... (Press ESC to cancel)
Executing command: java.exe -jar "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\Apktool\apktool_2.5.0.jar" b -d -f --use-aapt2 -o "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\2-Recompiled APKs\Teba_19.3.apk" "C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3"
I: Using Apktool 2.5.0
I: Smaling smali folder into classes.dex...
I: Building resources...
I: Using aapt2 - setting 'debuggable' attribute to 'true' in AndroidManifest.xml
W: C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\res: error: failed to open directory: El sistema no puede encontrar el archivo especificado. (2).
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\JOSAND~1\AppData\Local\Temp\brut_util_Jar_131902690237150689966905402769991619447.tmp, compile, --dir, C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\res, --legacy, -o, C:\Users\José Andrés\Desktop\PÒRTABLE EASY\1-Decompiled APKs\Teba_19.3\build\resources.zip]
Compile failed. Please read the log
Click to expand...
Click to collapse
Try enable aapt2
hispanico957 said:
When you write:
"Sometimes, removing the attribute will fix the error and the app would run fine without it. Always test if the app is working fine or not"
where i can do it, removing the attribute ?
My error is:
W: C:\Users\Marco\Documents\APK Easy Tool\1-Decompiled APKs\XRecorder_v2.1.1.1__Arm7_Pro__UserUpload.Net\res\layout\a0.xml:2: error: No resource identifier found for attribute 'paddingBottomNoButtons' in package 'videoeditor.videorecorder.screenrecorder'
etc...
Thank
Hispa
Click to expand...
Click to collapse
By editing the xml if you know how. I won't cover it here
Otherwise report issue to https://github.com/iBotPeaches/Apktool/issues

How to prevent apktool from merging res folders?
Example:
color
color-v11
get merged into
color

gcrutchr said:
How to prevent apktool from merging res folders?
Example:
color
color-v11
get merged into
color
Click to expand...
Click to collapse
Sorry, didn't saw this post. I think this is a feature. You should contact iBotPeaches

evildog1 said:
Sorry, didn't saw this post. I think this is a feature. You should contact iBotPeaches
Click to expand...
Click to collapse
It can't be a feature. SystemUI.apk won't work without res/**.xml-v??

When I change the Minimum SDK Version using ApkTool. The apk it's Crashing.

Just a heads-up.
If you like modifying Android core files (like framework.jar) on Android 10 or greater (API 29+) using apktool 2.6.1 it's not going to work so nicely even if it doesn't bomb on an error.
Code:
Error occurred while disassembling class Landroid.util.proto.HapiProto; - skipping class
java.lang.ArrayIndexOutOfBoundsException: 6
at org.jf.dexlib2.HiddenApiRestriction.getAllFlags(HiddenApiRestriction.java:108)
It will make a mish-mash of the new hidden API modifiers (whitelist, greylist, greylist-max-o...)
@iBotPeaches has this already in sight and is trying to resolve it.
https://github.com/iBotPeaches/Apktool/issues/2918
On a bit of a tangent, in the interim I tried the "nuclear option".
I was working on a framework.jar and couldn't "round-trip" it, so I edited out all the hidden API modifiers.
It builds fine, but the logcat was a train wreck.
Anybody know why?
Edit: I gave up on nuking all hidden API modifiers.
apktool d works fine so I can disassemble at least, but I don't think there are any options to show the file addresses of the instructions.
So I wrote a work-in-progress to disassemble with file addresses:
Code:
C:\>dexdump classes.dex /cKeyboardEntryMap /mgenerateMap
KeyboardEntryMap
002eebec generateMap
002eebfc const-string/jumbo
002eec02 invoke-static
002eec08 move-result-object
...
002eec62 invoke-interface
002eec68 goto
002eec6a return-void
Then I just need some judicious hex editing to nops or return-void.

Exception in thread "main" java.lang.ClassCastException: class brut.androlib.res.data.value.ResStringValue cannot be cast to class brut.androlib.res.data.value.ResIntValue (brut.
androlib.res.data.value.ResStringValue and brut.androlib.res.data.value.ResIntValue are in unnamed module of loader 'app')
Anyone know anything about this?