Apktool: Can't Recompile any android app. Exit code 132

[NarenderModi]

Information

1. **Apktool Version (`latest one 2.4.1)
2. **Operating System (Linux)
3. **APK From? (Any app from anywhere "Android app")

Stacktrace/Logcat

kali@localhost:/$ apktool b virus1
I: Using Apktool 2.4.1
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 132): [/tmp/brut_util_Jar_15924582530676693049.tmp, p, --forced-package-id, 127, --min-sdk-version, 16, --target-sdk-version, 22, --version-code, 1, --version-name, 1.0, --no-version-vectors, -F, /tmp/APKTOOL11389677012534912681.tmp, -e, /tmp/APKTOOL14404947888819616738.tmp, -0, arsc, -I, /home/kali/.local/share/apktool/framework/1.apk, -S, /virus1/res, -M, /virus1/AndroidManifest.xml]nclude stacktrace here
```

Steps to Reproduce

1. apktool

Frameworks

If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)

APK

If this APK can be freely shared, please upload/attach a link to it.

Questions to ask before submission

1. Have you tried apktool d, apktool b without changing anything?
2. If you are trying to install a modified apk, did you resign it?
3. Are you using the latest apktool version?

[NarenderModi]

[Yuliianto]

I got the same issue.
Please how can i fix this problem

[NarenderModi]

I got the same issue.
Please how can i fix this problem

[iBotPeaches]

Code 132 is either 32 bit incompatibilities or some missing image binary.

This is not a bug.

See - https://stackoverflow.com/questions/27715506/error-executing-aapt-return-code-132-problems

[NarenderModi]

I briefly describe you
I am using kali nethunter android
I also try to shift from kali nethunter to ubuntu and parrot OS. But getting same error in all platform

now this is becoming common problem for android users as i discussed with my friends..
They are getting same problem

Can you provide easy method or any video . So that we can solve this problem easily

[iBotPeaches]

They are getting same problem

I doubt it. You aren't using plain apktool in your Ubuntu screenshot and the Android (mobile) has no official supported version for Apktool.

[NarenderModi]

They are getting same problem

I doubt it. You aren't using plain apktool in your Ubuntu screenshot and the Android (mobile) has no official supported version for Apktool.

No , Android device supports apktool i have see many youtube video using apktool successfully

Please do check in your own android device (not emulator)

[whoiam1337]

Code 132 is either 32 bit incompatibilities or some missing image binary.

This is not a bug.

See - https://stackoverflow.com/questions/27715506/error-executing-aapt-return-code-132-problems

@iBotPeaches
I experienced the same thing, I can't recompile with exit code 132 on Kali Nethunter Android, but apktool run perfectly when recompile on Alpine Linux by using this aapt2.
this aapt2 compile with musl-libc, its possible to run this aapt2 on kali ?
sorry for my bad english

This aapt2

$ file /usr/bin/aapt2
/usr/bin/aapt2: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-aarch64.so.1, with debug_info, not stripped

[NarenderModi]

@whoiam1337
I tried this aapt2 but got the same error

[canxx99]

I have been dealing with this problem for a long time and I found a solution to this problem apktool. I have arranged to run on Android (nethunter vs.), you can use this jar file and forward it to those who have experienced this problem (fix exit code = 132)

[redacted]

@phhusson
@NarenderModi
@whoiam1337
@Yuliianto
@iBotPeaches

[iBotPeaches]

Hey @canxx99 , I'm going to remove your post. I shy away from sharing binaries due to security reasons. You are welcome to share source changes or even upstream them, but we won't share binaries due to the possible security implications.

[canxx99]

As a solution to this problem, I shared a jar file, but it was removed for security reasons.
I shared the file on my own page.

@NarenderModi
@whoiam1337
@Yuliianto

[Yuliianto]

So hos to solve this issue?

[giacomoferretti]

@Yuliianto you'll need to have ARM binaries for aapt and aapt2.

It seems that @canxx99 already compiled them and built the apktool.jar so you can download his version, at your own risk. That's the only difference between his version and the official version (we are talking about 2.4.0).

[Yuliianto]

@giacomoferretti it's still not got same problem

[canxx99]

@Yuliianto As stated verbally, this is not an error. Aapt does not work for arm64 architecture. You have to use the jar in my tank. I recompiled it and made it aapt arm64 compatible.
https://github.com/canxx99/apktool

[mertbeet]

i have the same problem. I am using apktool 2.5.0, what should I do? @iBotPeaches

[iBotPeaches]

@mertbeet - We don't officially support running Apktool on a device. Sorry.

[canxx99]

@mertbeet The jar I compiled for Android devices works, you can download it from my repository, but it only works with apktool 2.4.0. (but it is not an Official version, it is your responsibility to use the jar file)

[mertbeet]

@mertbeet The jar I compiled for Android devices works, you can download it from my repository, but it only works with apktool 2.4.0. (but it is not an Official version, it is your responsibility to use the jar file)

Thank you. I guess I need to use 2.5.0 for A11 apks, for best experience. Can you use your solution with the apktool developer?

[canxx99]

@mertbeet I tried it for you bro and it worked but I don't know if it works for all apk files, you can try. I tried it in an apk file for this and it worked. How can I send this to you