Apktool | A tool for reverse engineering Android apk files

My app"s permissions are not being requested on launch, the only way to allow it is by settings>apps>my_app>permissions>allow_permissions . Its possible to make the app request it just by modifying the manifest, the activity_main.xml, or some other file in the decompiled apk folder (using apktool) ?

I would like to add something to an app, so I added some lines to a smali file (decompiled the apk using apktools) and then repackaged and ran it on a real device. It shows

• 10121 10211 E AndroidRuntime: os.json.JSONObject a.b.a.a.a.i.m(android.context.Context, java.lang.String) Failed to verify: os.json.JSONObject a.b.a.a.a.i.m(android.context.Context, java.lang.String): [0x161] v0 has type Conflict but expected Reference: java.lang.AutoCloseable (declaration of 'a.b.a.a.a.i' in /data/app/xxxx/xxxxx/base.apk)

So what does the [0x161] refer to? Is it a line number? 0x161 = 353 in decimal. So I checked the smali code, but the function a.b.a.a.a.i.m has less than 353 lines in smali, so there is no line 353 and I can not locate the error.

Neither does this function have enough lines in java (I used jadx to decompiled the generated apk).

So in which type of file can I locate the problem in file's line 353? Should I transformed the apk into some other format to find a line 353 to troubleshoot the error? Thanks in advance.

I am trying to turn an apk into aab, decompile with apktool, and build with aapt2 and bundletool (all in command line, without gradle).

After decompile, aapt2 compile and link looks good, but when I execute build-bundle with bundletool, I got this error. What went wrong? And How can i fix it?

I hava an apk file.

When the apk is used v1 signature, it is ok when unzip an apk file. But when using v2, unzip fails.

How can i get the original dex file?

What i want to do is to modify the dex with ida, then rebuild to get a new apk.

I know i can use apktool to get smali files, then modify smali file and rebuild to a new apk. But i want do try modify dex file in hex mode(eg. using ultra edit).

enter image description here

I have an .apk file for an old version of an app but don't have the ability to rebuild the app from source using cordova. I'm trying to debug an error and would like to enable remote debugging. Is it possible to enable remote debugging of the webview without rebuilding the app?

I've tried unpacking the app using apktool, adding android:debuggable="true" to the AndroidManifest.xml and then repacking and resigning the .apk.

When I run the app I can see the device in the device list of chrome://inspect#devices but the webview is not appearing. Am I missing something?

4.1 dirthy, but this version was not official of apktool, and I was having some problems, so I upgraded to version 2.5.0 and official, however I want my apktool folder to be in /usr/share but if I move my apktool folder to /usr/share when I run apktool the result is this:

I'm trying to decompile an apk with the apk tools and I'm not getting it.

When I run apktool -d myapp.apk it displays this error to me:

I'm using Nethunter, and the architecture is Linux arm, and I would love to use the apktool tool, I'm studying and reading pentest books, but I can't practice if I don't apply what's there, the problem is that for me rebuild an apk using apktool b app it returns an error code 131, which according to the creator of apktool, is that aapt is not working for arm architecture, is there any way I can install aapt for arm?

Running into an issue around a native-Android Unity integration release into the Play Store. I extract it as a project out of Unity and migrate it as a Library in our native app.

When attempting to upload an .AAB into the Play Store, the following error occurs: