Database Info

[Q] compile SystemUi.apk

when im compiling systemui from virtuous Inquisition 4.0.1 im geting errors:
Code:
c:\apktool>Java -jar apktool.jar b systemui
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: c:\apktool\systemui\res/drawable-sw600dp-hdpi
invalid resource directory name: c:\apktool\systemui\res/layout-sw600dp
invalid resource directory name: c:\apktool\systemui\res/values-sw600dp
invalid resource directory name: c:\apktool\systemui\res/values-sw600dp-port
invalid resource directory name: c:\apktool\systemui\res/values-sw720dp
invalid resource directory name: c:\apktool\systemui\res/values-sw720dp-port
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\knyku\AppData\Local\Temp\A
PKTOOL1129380418371610026.tmp, -I, C:\Users\knyku\apktool\framework\1.apk, -S, c
:\apktool\systemui\res, -M, c:\apktool\systemui\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java: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, C:\U
sers\knyku\AppData\Local\Temp\APKTOOL1129380418371610026.tmp, -I, C:\Users\knyku
\apktool\framework\1.apk, -S, c:\apktool\systemui\res, -M, c:\apktool\systemui\A
ndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
c:\apktool>
framework and resources installed, any ideas ?

Yes, build on linux. I've never had luck with apktool on windows...
Also, has apktool been updated yet to support ICS apk's? I haven't used it in a little while, but it was unsupported last time I tried...

have read somewhere that it supports now, but not working. anyway, if its not working so how devs theming their roms ?!
edit:
updated builtin framework to SDK API14
Click to expand...
Click to collapse
so not supporting. but rly, how devs doin' it ?

I'm looking at the changelog right now:
code.google.com/p/android-apktool/wiki/Changelog said:
1.4.3¶2011.12.08
•updated builtin framework to SDK API14
•fixed some "Multiple substitutions (...)" errors ( Issue 254 )
1.4.2¶2011.12.02
•added support for API14 (Android 4.0) resources
•updated smali to v1.3.0
•added --quiet option
•fixed decoding error when string ends with '%' ( Issue 169 )
•fixed decoding error when <plurals> contains a reference ( Issue 234 )
•fixed a broken res when decoding <array> with positional substitutions ( Issue 222 )
Click to expand...
Click to collapse
It looks like 4.0 should be supported in v1.4.2 and up. Verify that you're running the correct version, and if that doesn't work then I still defer to my original recommendation of running on a linux system. One thing I'm noticing from your posted error is that the file system for the missing resource is using a forward slash after the res directory. Possibly an error in the windows version of apktool.
If you want to upload your changes to a git repo I can update my apktool and play with it...

As far as I know sense 3.6 is now SDK 15 and I can see that sense 4.0 is SDK 18/19 so it would be interesting to see if somebody could download apktool from git, add the framework into it and compile. That should solve the issues.
I was able to download the apktool from GIT but dont know what to do to add the framework in.

solved.
just need to copy updated aapt.exe from platform-tools @ sdk to apktool folder.
to install type apktool if framework-res.apk and done

kamik_f said:
solved.
just need to copy updated aapt.exe from platform-tools @ sdk to apktool folder.
to install type apktool if framework-res.apk and done
Click to expand...
Click to collapse
That works for me as well. I dropped it into my /usr/local/bin directory after updating my apktool in order to resolve the errors...
I'm glad you posted this today. I've been putting off updating my apktool. This not only motivated me to update, but also got it working in a timely manner...
dziekuje

GhostXSeries said:
As far as I know sense 3.6 is now SDK 15 and I can see that sense 4.0 is SDK 18/19 so it would be interesting to see if somebody could download apktool from git, add the framework into it and compile. That should solve the issues.
I was able to download the apktool from GIT but dont know what to do to add the framework in.
Click to expand...
Click to collapse
The 3.32 based apktool works fine for me on sense 4. Just need to install the new framework and then no errors
Sent from my Sensation using xda premium

[Q] please Help in recompiling with autoapk

when i try to decompile an apk and even with out editing any thing when i just recompile i get this log
[*] D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12
recompiling D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12...
I: Smaling...
I: Building resources...
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 5, --target-sdk-version, 8, -F, D:\Users\Rayman\AppData\Local\Temp\APKTOOL7498851666322294987.tmp, -I, D:\Users\Rayman\apktool\framework\1.apk, -S, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res, -M, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:255)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:324)
at brut.androlib.Androlib.buildResources(Androlib.java:269)
at brut.androlib.Androlib.build(Androlib.java:192)
at brut.androlib.Androlib.build(Androlib.java:174)
at brut.apktool.Main.cmdBuild(Main.java:188)
at brut.apktool.Main.main(Main.java:70)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 5, --target-sdk-version, 8, -F, D:\Users\Rayman\AppData\Local\Temp\APKTOOL7498851666322294987.tmp, -I, D:\Users\Rayman\apktool\framework\1.apk, -S, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res, -M, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:253)
... 6 more
Unable to open '_INPUT_APK\1.12\dist\1.12.apk' as zip archive
The system cannot find the drive specified.
and i cant install the recompiled apk
please help

mad.boss said:
when i try to decompile an apk and even with out editing any thing when i just recompile i get this log
[*] D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12
recompiling D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12...
I: Smaling...
I: Building resources...
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 5, --target-sdk-version, 8, -F, D:\Users\Rayman\AppData\Local\Temp\APKTOOL7498851666322294987.tmp, -I, D:\Users\Rayman\apktool\framework\1.apk, -S, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res, -M, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:255)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:324)
at brut.androlib.Androlib.buildResources(Androlib.java:269)
at brut.androlib.Androlib.build(Androlib.java:192)
at brut.androlib.Androlib.build(Androlib.java:174)
at brut.apktool.Main.cmdBuild(Main.java:188)
at brut.apktool.Main.main(Main.java:70)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 5, --target-sdk-version, 8, -F, D:\Users\Rayman\AppData\Local\Temp\APKTOOL7498851666322294987.tmp, -I, D:\Users\Rayman\apktool\framework\1.apk, -S, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res, -M, D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:253)
... 6 more
Unable to open '_INPUT_APK\1.12\dist\1.12.apk' as zip archive
The system cannot find the drive specified.
and i cant install the recompiled apk
please help
Click to expand...
Click to collapse
Your error is right here. I would make sure that these are there and not spelled differently.
\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.

zelendel said:
Your error is right here. I would make sure that these are there and not spelled differently.
\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
Click to expand...
Click to collapse
yes these r the errors, this is the log file nothing wrong
how to avoid them?
i just decompiled and recompiled with out even any editing why i'm getting error recompiling? is there any way to avoid these errors?

zelendel said:
Your error is right here. I would make sure that these are there and not spelled differently.
\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
Click to expand...
Click to collapse
even with these errors i find a compiled apk in the output folder but it cant be installed in my phone neither signed or unsigned

zelendel said:
Your error is right here. I would make sure that these are there and not spelled differently.
\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Widget.ProgressBar.Horizontal'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:8: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
D:\Users\Rayman\Downloads\Compressed\xdaAutoAPKTool_V3.0.2\xdaAutoAPKTool_V3.0.2\_INPUT_APK\1.12\res\values\styles.xml:12: error: Error retrieving parent for item: No resource found that matches the given name '@*android:style/Theme.Dialog'.
Click to expand...
Click to collapse
and i attached the file the contain the errors

mad.boss said:
and i attached the file the contain the errors
Click to expand...
Click to collapse
any one can help me pleaase

Cometo think of it did you install the proper framework files before decompiling and recompiling the apk?

zelendel said:
Cometo think of it did you install the proper framework files before decompiling and recompiling the apk?
Click to expand...
Click to collapse
where to put framework files? and where to find the proper framework plzzzzz?

mad.boss said:
where to put framework files? and where to find the proper framework plzzzzz?
Click to expand...
Click to collapse
You find the framework in the rom your running. Installing the frameworks is apk editing 101. I would do some research on it as it differs depending on the device and the rom your running.

zelendel said:
You find the framework in the rom your running. Installing the frameworks is apk editing 101. I would do some research on it as it differs depending on the device and the rom your running.
Click to expand...
Click to collapse
its a non-system app.
still need framework even if its a non-system app???

mad.boss said:
its a non-system app.
still need framework even if its a non-system app???
Click to expand...
Click to collapse
Yes

[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?

[05.23.14][TOOL] APK Tools v3.50 [Windows][GUI]

APK Tools --
"A complete fresh tool developed from scratch; inspired by existing tools available out there."
INFO: Pushed to GitHub​
SCREENSHOTS​
Requirements:
Java JDK/JRE
Android SDK
BRAIN! ^_^
Features:
Faster and easier APK handling (GUI Version) -- supports drag and drop file; access files anywhere
All-in-one (ADB Push/Pull, Extract, Optimize, Zip, Sign, Zipalign, Install, Decompile, Compile...)
Based on latest available tools
Great user interaction; less prone to errors (More information and warning during operation)
Works everytime and anywhere (No problem with paths and filename containing spaces or weird characters)
Log activities with time stamp and use date as log filename
Install and use of framework with custom tags
Generate and sign APKs with own private key (Android market supported)
Switch between apktool versions (2.0.0b9 & 1.5.2)
Many more . . . Check for yourself! ;D
To Do:
Log activities with time and date headers - Done
Install framework with custom tags - Done
Generate own private key with android market support - Done
Sign APKs with the generated private key - Done
GUI version with drop file support - Done
Switch between APKTOOL versions - Done
Post a feature request or suggestion here.​
Instructions:
Extract "APK Tool v#.##.zip"
Execute "APK Tools.exe"
Necessary files and folders are installed automatically every launch if not found.
Place APKs to be modded inside "APK Files" folder.
All extracted or decompiled APKs are found in "Projects" folder.
Generated private keys are located in "OUTPUT" folder.
Zipped, signed, zipaligned and/or compiled projects are found in "OUTPUT" folder.
Zipped/Compiled with Original Signature => system-%Project%
Zipped/Compiled with No Signature => unsigned-%Project%
Signed with Generated Private Keys => gpsigned-%Project%
Signed with Android Market => amsigned-%Project%
Signed with Test Keys => signed-%Project%
Click to expand...
Click to collapse
* Testers would be much appreciated to keep the tool stable.
** If possible, post full info regarding bugs encountered here.
*** Let's try to fix issues / errors ASAP. THANKS!!!
DOWNLOADS:
Direct (XDA)
Mirror v1.00 (MediaFire)
Mirror v1.50 (MediaFire)
Mirror v2.00 (MediaFire)
Mirror v3.00 (MediaFire)
Mirror v3.50 (MediaFire)
Rate and post a review here.​
CREDITS:
Google for Overall HELP and Android Tools
Brut.all / iBotPeaches for apktool
jesusfreke for smali/backsmali
deanlee3 for roptipng
Igor Pavlov for 7zip
Yorzua for signapk
XDA:DevDB Information
APK Tools (GUI Version), Tool/Utility for all devices (see above for details)
Contributors
kermage
Source Code: https://github.com/kermage/APK-Tools
Version Information
Status: Stable
Current Stable Version: 3.50
Stable Release Date: 2014-05-23
Created 2014-05-22
Last Updated 2015-08-01

Changelogs
v3.50 ( 05/23/14 )
GUI fixes and adjustments
Fixed ADB push and pull locations
Fixed Compile option not signing original signature
Added option to copy over original files after compile
Added ADB install option
{
"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"
}
v3.00 ( 05/21/14 )
GUI version (faster and easier handling) -- supports drag and drop file
Access files anywhere (not limited to APK Files folder)
Switch between apktool versions (2.0.0b9 & 1.5.2)
Improved error detection and logging capability
Multiple tweaks and rework to codes
v2.00 ( 05/07/14 )
Generate own private key with android market support
Sign APKs with the generated private key
More tweaks and fixes to code
Improved launcher script
v1.50 ( 05/03/14 )
Log activities with time stamp and use date as log filename
Install and use of framework with custom tags
Minor tweaks and fixes to code
v1.00 ( 04/27/14 )
Initial release

Reserved

Took me a few to find the add project (button) lol, but this works like a champ...great work, thank you sir.

Can't Recompile
Any idea on this ???? :crying: I can compile app from other rom. not mine. any help ?
Logs:
**Decompile Successfull
I: Using Apktool 2.0.0-Beta9 on Settings.apk
I: Loading resource table...
W: Skipping "android" package group
I: Loading resource table...
W: Skipping "android" package group
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: E:\Android Company\Work Files\APK Tools v3.50\tools\Frameworks\2.0.0b9\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...
**Compile error
Preparing Projects\Settings.apk . . .
I: Using Apktool 2.0.0-Beta9 on Settings.apk
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:69: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/PreferencePanel'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:77: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/PreferenceHeaderList'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:88: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/PreferenceFragmentList'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:189: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/TextAppearance.Holo.Widget.Switch'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:205: error: Error: No resource found that matches the given name: attr 'androidreferencePanelStyle'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:215: error: Error: No resource found that matches the given name: attr 'androidreferencePanelStyle'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:222: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/Theme.Holo.Dialog.Alert'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:229: error: Error retrieving parent for item: No resource found that matches the given name '@android:style/Theme.Holo.Light.Dialog.Alert'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:241: error: Error: No resource found that matches the given name: attr 'androidreferenceFragmentListStyle'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:242: error: Error: No resource found that matches the given name: attr 'androidreferenceFragmentPaddingSide'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:239: error: Error: No resource found that matches the given name: attr 'androidreferenceHeaderPanelStyle'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:240: error: Error: No resource found that matches the given name: attr 'androidreferenceListStyle'.
E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res\values\styles.xml:238: error: Error: No resource found that matches the given name: attr 'androidreferencePanelStyle'.
Exception in thread "main" brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [C:\DOCUME~1\user\LOCALS~1\Temp\brut_util_Jar_3068233787267709001.tmp, p, --forced-package-id, 127, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2, -F, C:\DOCUME~1\user\LOCALS~1\Temp\APKTOOL4280259419212628272.tmp, -0, arsc, -I, E:\Android Company\Work Files\APK Tools v3.50\tools\Frameworks\2.0.0b9\1.apk, -S, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res, -M, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\AndroidManifest.xml]
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:435)
at brut.androlib.Androlib.buildResources(Androlib.java:363)
at brut.androlib.Androlib.build(Androlib.java:286)
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: [C:\DOCUME~1\user\LOCALS~1\Temp\brut_util_Jar_3068233787267709001.tmp, p, --forced-package-id, 127, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2, -F, C:\DOCUME~1\user\LOCALS~1\Temp\APKTOOL4280259419212628272.tmp, -0, arsc, -I, E:\Android Company\Work Files\APK Tools v3.50\tools\Frameworks\2.0.0b9\1.apk, -S, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res, -M, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:470)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:416)
... 5 more
Caused by: brut.common.BrutException: could not exec command: [C:\DOCUME~1\user\LOCALS~1\Temp\brut_util_Jar_3068233787267709001.tmp, p, --forced-package-id, 127, --min-sdk-version, 19, --target-sdk-version, 19, --version-code, 19, --version-name, 4.4.2, -F, C:\DOCUME~1\user\LOCALS~1\Temp\APKTOOL4280259419212628272.tmp, -0, arsc, -I, E:\Android Company\Work Files\APK Tools v3.50\tools\Frameworks\2.0.0b9\1.apk, -S, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\res, -M, E:\Android Company\Work Files\APK Tools v3.50\Projects\Settings.apk\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:89)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:464)
... 6 more

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?