smali | dex format used by dalvik , Android 's Java VM implementation

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 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 found an app that detects Location spoofing and returns a warning screen. [1]: https://i.stack.imgur.com/qbhuU.jpg Then I tried to reverse engineer the app and remove the function isFromMockProvider()which checks whether the Location data is from a Mock location provider or not. I found these lines of code from a smali file

Here is the TestClass and MainActivity.

In order to always show the Toast, I changed TestClass constructor using smali patching to following:

but after compiling and signing, the new patched apk could not be installed.

where is the problem??

Here is the patching code:

I’m using mt manager to edit Smali in dex.

I found that there are many move-object in some classes. Most of them are unnecessary.

Does it impact performance?

I'm trying to debug a thrid party app like shown here Android Reverse Engineering: Debugging Smali in Smalidea . The problem is that the Android Device Monitor / DDMS is not showing any threads and the "Update threads" button is disabled.

Does anyone has an idea why that is the case?

I tried different physical devices and emulators (I'm using Win10) and even used the new profiler from Android Studio (also just showing "no processes to debug"). USB debugging is enabled and I can access all devices via adb from command line.

I have several dex files that needs to be statically analyzed by mobsf after unpacking the apk file because core code are inaccessible prior to unpacking.

What I've tried: Adding Line 3 and changing line 4 from glob_pattern = app_dir + *.dex' to glob_pattern = ddex_dir

I'm currently doing project that needs .smali file from android app. In order to get .smali file i have to decompile android app. Thus, someone recommends me to use apktool. Unfortunately, apktool only can decompile an android app at one time. I need to decompile a lot of apps ( more than 4000). it will waste my time if I decompile it one by one. So, is there a way to decompile multiple android apk at the same time? or If you can recommend me tools that will help me get .smali files from multiple app faster? Thank you.

I am using APK Easy Tool to Decompile games and apps in android but it generates .smali files which are difficult for me to understand. I do not have much knowledge about .smili code.

Is there any other way to decompile and edit such android games and apps using .java / kotline / c# etc code same as build before? Please help get ride of .smali code.