Add support for API level 13 (Android 3.2) resources

[iBotPeaches]

Original issue 195 created by brian6azar on 2011-07-13T15:41:47.000Z:

What steps will reproduce the problem?

1. copy framework-res.apk from 3.2 WiFi Xoom to APKtool folder (with updated .jar)
2. CMD "apktool if framework-res.apk"
3. Error listed below

What is the expected output? What do you see instead?
I expected: "Framwork installed C:...".
Instead got: "
W: Config flags size > 32. Exceeding bytes: -2FFE0000.
W: Invalid config flags detected: dimen-v13-ERR0.
W: Config flags size > 32. Exceeding bytes: 00050000.
W: Invalid config flags detected: detected: dimen-v13-ERR1.
W: Config flags size > 32. Exceeding bytes: 0000D002.
W: Invalid config flags detected: detected: dimen-v13-ERR2.
W: Config flags size > 32. Exceeding bytes: 58020000.
W: Invalid config flags detected: layout-v13-ERR3.
W: Config flags size > 32. Exceeding bytes: 2FFE0000.
W: Invalid config flags detected: integer-v13-ERR4.
Framework installed to: C:...
"

What version of the product are you using? On what operating system?
WinXP with the most recent files as of 7/13/11

Please provide any additional information below.
I can provide screen shots of the errors, as well as the framework-res.apk taken from my Xoom if it's needed.

[iBotPeaches]

Comment #1 originally posted by Brut.alll on 2011-07-13T17:07:05.000Z:

Upload this framework-res.apk, please.

[iBotPeaches]

Comment #2 originally posted by brian6azar on 2011-07-13T17:30:30.000Z:

I also updated the SDK and tried using the new aapt, still same thing. This is from 3.1, would it be because they haven't released an SDK for 3.2 yet? Included is a SystemUI.apk from 3.2 also with many errors when trying to decompile.

Thanks for taking a look at this!

[iBotPeaches]

Comment #3 originally posted by Brut.alll on 2011-07-13T18:02:22.000Z:

There are some new qualifiers introduced in API Level 13. If you look into framework-res.apk you'll find layout-sw600dp and layout-w600dp dirs. Even if you decode them, you won't be able to build apk back, because we don't have aapt with support for new resources.

Actually apktool does what it should - it removes these resources, so you are able to build apk back and resulting apk should be nearly identical to original one.

We can't do much about this until Google release new SDK tools and docs. Just ignore these warnings.

[iBotPeaches]

Comment #4 originally posted by brian6azar on 2011-07-13T18:06:00.000Z:

Dang, I feared that would be the case. Not sure when they'll release 3.2. Were you able to decompile the SystemUI.apk after mounting the framework too? Or should I start a new issue for that? Because it doesn't even decompile, giving me many more errors.

Thanks for checking this out so quickly tho!

[iBotPeaches]

Comment #5 originally posted by brian6azar on 2011-07-16T14:56:20.000Z:

Hey Brut, I just downloaded the 3.2 SDK, copied the aapt.exe from platform-tools in to the apktool dir, and still get the same issues when trying to mount the framework. Are there any other files I need to bring in from the update?

[iBotPeaches]

Comment #6 originally posted by Brut.alll on 2011-07-16T15:29:15.000Z:

There are no sources yet, but I should be able to deal with this.

[iBotPeaches]

Comment #7 originally posted by oliver.pahl on 2011-07-28T07:28:47.000Z:

Hi,

i patched the latest trunk for support with v13. Tested it on a few 3.2 apps and it worked like a charm. I am attaching the patch.

[iBotPeaches]

Comment #8 originally posted by oliver.pahl on 2011-07-28T07:58:23.000Z:

Fixed apktool up for 3.2 (v13) Ressources. Attaching the binary and the according patch.

[iBotPeaches]

Comment #9 originally posted by oliver.pahl on 2011-07-28T12:02:45.000Z:

There are two versions of the download, one i posted earlier, which does not decode framework-res.apk correctly. This is fixed in the above upload (which I uploaded a few minutes later ;)). So, if your binary or patch do not work, please re-Download.

[iBotPeaches]

Comment #10 originally posted by brian6azar on 2011-07-28T15:39:12.000Z:

Dude, you are the man!! Thank you so much!!

[iBotPeaches]

Comment #11 originally posted by DanielWilliamson17 on 2011-08-04T11:34:29.000Z:

This 3.2 fix got me further, I.e further than the smali folder, however I recieve a values/ xml error and so all the other files and folders are there apart from the most important for me, values. I am using a 3.2 custom asus eee pad transformer rom.

[iBotPeaches]

Comment #12 originally posted by oliver.pahl on 2011-08-04T12:40:38.000Z:

Hi,

have you done 'apktool if /path/to/your/framework-res.apk'

If you didnt, thats the issue, if you did I would need further Error messages and the apk you try to disassemble to be able to help you.

[iBotPeaches]

Comment #13 originally posted by DanielWilliamson17 on 2011-08-04T15:13:20.000Z:

Thankyou, did not know about that feature. All working.

[iBotPeaches]

Comment #14 originally posted by DanielWilliamson17 on 2011-08-05T20:22:00.000Z:

Struggling with compiling now with android 3.2, not sure if this has been mentioned somewhere else but whatever I try the following appears:

I: Building resources...
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/layout-sw600dp
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/layout-w600dp-v13
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/values-h720dp-v13
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/values-sw600dp
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/values-w1280dp-v13
invalid resource directory name: C:\Users\Daniel\Desktop\Apk-tool\framework-res
res/values-w720dp-v13
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\Daniel\AppData\Local\Temp
APKTOOL930483141669058782.tmp, -x, -S, C:\Users\Daniel\Desktop\Apk-tool\framewor
k-res\res, -M, C:\Users\Daniel\Desktop\Apk-tool\framework-res\AndroidManifest.xm
l]
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:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\Daniel\AppData\Local\Temp\APKTOOL930483141669058782.tmp, -x, -S, C:\Users\D
aniel\Desktop\Apk-tool\framework-res\res, -M, C:\Users\Daniel\Desktop\Apk-tool\f
ramework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more

[iBotPeaches]

Comment #15 originally posted by oliver.pahl on 2011-08-05T21:37:33.000Z:

Seems like you forgot to update your Android SDK to API Version 13 -> So aapt is out of date and does not know how to pack the ressources.

[iBotPeaches]

Comment #16 originally posted by scar45 on 2011-08-06T04:36:20.000Z:

Hi Oliver, thanks for your great tool! I have been using it to build themes for the ASUS TF101, and with HC 3.2 recently released, I'm having a problem with bootloops after replacing 'framework-res.apk' and 'SystemUI.apk'.

I can decompile/build the APKs fine with that updated APKTool link you posted above, and I've also updated my Google SDK to v13 and replaced 'aapt.exe' from the SDK into the APKTool folder. Anyways, as I said, they appear to build fine, but when flashing them, I get a bootloop.

I have a logcat excerpt here: http://pastebin.com/1RnW3012, and the "E/----" lines do show an issue with missing/bad certs in AndroidManifest.xml.

Hoping you can lend some insight, as I never had a problem with HC 3.1 (and I've also re-installed the HC 3.2 framework-res.apk as a new tag).

Thanks in advance!

[iBotPeaches]

Comment #17 originally posted by oliver.pahl on 2011-08-06T06:05:46.000Z:

Seems that you have a signing issue. Apktool removes the certificates once you run it. The best way to preserve them is to take the following steps.

1. unpack your apk
2. Make your changes
3. Repack the apk
4. Open the original apk in winzip or similar (the one you pulled from device or update.zip)
5. Unzip the new apk (the one you created with apktool)
6. Delete all files except AndroidManifest.XML and the meta-inf folder in the winzip window
7. Pull all the files from your unpacked new apk and push them into winzip (except AndroidManifest.XML)
8. Enjoy your newly signed hybrid

This should work for all apks, but only if you do not change AndroidManifest.xml

[iBotPeaches]

Comment #18 originally posted by DanielWilliamson17 on 2011-08-06T07:17:03.000Z:

Okay, ill try that although I can't seem to be able to re-download the 13 ApI. Could someone please upload the aapt for level 13, it would be a great help.

Thanks

Dan

[iBotPeaches]

Comment #19 originally posted by scar45 on 2011-08-06T14:37:53.000Z:

Many thanks Oliver!

That was indeed the fix, although I did it the opposite way by taking the original META-INF + AndroidManifest.xml files, and popping them back into my modded APKs.

Thanks again for the swift reply! :)

[iBotPeaches]

Comment #20 originally posted by theguitardood on 2011-08-18T13:41:52.000Z:

I wanted to edit a few simple things on my xoom like text colors and such. This tool accomplished just that, but it has a nasty side effect. In order for some of the changes to take place, I had to swap out the resources.arsc file from the newly compiled apk, which caused things to start crashing and force closing all over the place. For example, I only edited the clock color on the lock screen in framework-res and it caused the "Settings" menus in many apps to force a close of the app.

I believe the problem lies here. I found this in drawables.xml in the values folder (which is used to create the .arsc file)

<item type="drawable" name="APKTOOL_DUMMY_04b5">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04b8">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04ba">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04bd">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04bf">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04c3">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04c6">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04c8">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04c9">false</item>
<item type="drawable" name="APKTOOL_DUMMY_04cb">false</item>

Any ideas?

[iBotPeaches]

Comment #21 originally posted by Brut.alll on 2011-11-05T01:36:00.000Z:

I have fixed this in a git.

Oliver, how did you now there is a -television qualifier - I don't see it in the docs?

[iBotPeaches]

Comment #22 originally posted by oliver.pahl on 2011-11-05T08:46:58.000Z:

Hi,

I looked up the API Diffs. The density for tv is here:
http://developer.android.com/reference/android/util/DisplayMetrics.html

Here the UI Mode:
http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_TELEVISION

[iBotPeaches]

Comment #23 originally posted by Brut.alll on 2011-11-05T17:15:11.000Z:

Thanks, seems they forgot to add it in the main article about qualifiers: http://developer.android.com/guide/topics/resources/providing-resources.html .

Ok, I have added it too.

[iBotPeaches]

Comment #24 originally posted by Brut.alll on 2011-11-05T17:58:29.000Z:

<empty>

[iBotPeaches]

Comment #25 originally posted by Brut.alll on 2011-11-05T21:07:03.000Z:

Issue 197 has been merged into this issue.

[iBotPeaches]

Comment #26 originally posted by Brut.alll on 2011-11-05T22:26:49.000Z:

Issue 215 has been merged into this issue.

[iBotPeaches]

Comment #27 originally posted by Brut.alll on 2011-11-05T23:00:19.000Z:

<empty>

[iBotPeaches]

Comment #28 originally posted by Brut.alll on 2011-11-05T23:03:46.000Z:

Issue 219 has been merged into this issue.

[iBotPeaches]

Comment #29 originally posted by Brut.alll on 2011-11-05T23:49:03.000Z:

Issue 230 has been merged into this issue.

[iBotPeaches]

Comment #30 originally posted by Brut.alll on 2011-11-28T23:36:15.000Z:

Issue 243 has been merged into this issue.

[iBotPeaches]

Comment #31 originally posted by support@networkltd.co.uk on 2012-03-14T10:41:31.000Z:

So this issue is not fixed
Tried http://dev-host.org/Agy with 1.4.2 and 1.4.3 and still getting:
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-hdpi-ERR0
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-hdpi-ERR1
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-hdpi-ERR2
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-hdpi-ERR3
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR4
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR5
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR6
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR7
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR8
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR9
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR10
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR11

[iBotPeaches]

Comment #32 originally posted by xxx on 2012-03-14T10:42:33.000Z:

So this issue is not fixed
Tried http://dev-host.org/Agy with 1.4.2 and 1.4.3 and still getting:
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-hdpi-ERR0
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-hdpi-ERR1
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-hdpi-ERR2
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-hdpi-ERR3
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR4
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR5
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR6
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR7
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR8
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR9
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR10
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR11

[iBotPeaches]

Comment #33 originally posted by xxx on 2012-03-14T10:42:56.000Z:

So this issue is not fixed
Tried http://dev-host.org/Agy with 1.4.2 and 1.4.3 but still getting:
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-hdpi-ERR0
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-hdpi-ERR1
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-hdpi-ERR2
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-hdpi-ERR3
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR4
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR5
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR6
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rCN-hdpi-ERR7
W: Config flags size > 36. Exceeding bytes: 0x1000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR8
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR9
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR10
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected: dimen-zh-rTW-hdpi-ERR11

[iBotPeaches]

Comment #34 originally posted by linuxlee.lb on 2012-04-06T21:50:27.000Z:

Same issue here, apktool V1.4.3, HTC One X, htc-resources.apk..
As the apkis to big I have uploaded it to my ftp here >> http://leedroid.ftp.rshost.eu/share/com.htc.resources.apk

error log

I: Loading resource table...
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-hdpi-ERR0
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-hdpi-ERR1
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-hdpi-ERR2
W: Config flags size > 36. Exceeding bytes: 0x6000000.
W: Invalid config flags detected. Dropping resources: dimen-hdpi-ERR3
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-xhdpi-ERR4
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-xhdpi-ERR5
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-xhdpi-ERR6
W: Config flags size > 36. Exceeding bytes: 0x6000000.
W: Invalid config flags detected. Dropping resources: dimen-xhdpi-ERR7
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-hdpi-ERR8
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-hdpi-ERR9
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-hdpi-ERR10
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-xhdpi-ERR11
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-xhdpi-ERR12
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-ja-xhdpi-ERR13
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-hdpi-ERR14
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-hdpi-ERR15
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-hdpi-ERR16
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-xhdpi-ERR17
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-xhdpi-ERR18
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-ko-xhdpi-ERR19
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-hdpi-ERR20
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-hdpi-ERR21
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-hdpi-ERR22
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-xhdpi-ERR23
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-xhdpi-ERR24
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rCN-xhdpi-ERR25
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-hdpi-ERR26
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-hdpi-ERR27
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-hdpi-ERR28
W: Config flags size > 36. Exceeding bytes: 0x2000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-xhdpi-ERR29
W: Config flags size > 36. Exceeding bytes: 0x4000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-xhdpi-ERR30
W: Config flags size > 36. Exceeding bytes: 0x5000000.
W: Invalid config flags detected. Dropping resources: dimen-zh-rTW-xhdpi-ERR31
Exception in thread "main" java.lang.NullPointerException
at brut.androlib.res.decoder.ARSCDecoder.addMissingResSpecs(ARSCDecoder.java:315)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:133)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:105)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:82)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:48)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibResources.java:315)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.java:50)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.java:43)
at brut.androlib.Androlib.getResTable(Androlib.java:44)
at brut.androlib.ApkDecoder.getResTable(ApkDecoder.java:148)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:98)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)

Is apktool still under active development?

[iBotPeaches]

Comment #35 originally posted by iBotPeaches on 2012-08-26T04:06:27.000Z:

I haven't seen brut.all in 8 months. I've taken over active dev.

http://connortumbleson.com/apktool-v1-4-5-a-tool-for-reverse-engineering-apk-files/