Hot answers tagged

5

Without the proguard mapping, this is not possible. That information is simply no longer contained in the dex file. The best you could do would be to manually rename the methods, etc. with your own names.


3

As I understand it, they didn't reverse engineer anything. They wrote an independent implementation based on reading the documentation of the APIs. Oracle's contention was that simply having the same method names in the APIs was a copyright violation, which is obviously silly.


2

Your best bet is to just start reading through the code and see everything it does. It almost certainly is checking signatures, just in a way that your search missed. That could be because it is using an API you didn't search for, or because the code is obfuscated, or because you messed up the search. Note that there are a lot of APIs that could be used to ...


2

I believe most versions of dalvik and art will reject the dex file and refuse to load it.


2

I think your approach is generally correct. You probably can't connect to the Bluetooth because your additional code throws an exception somewhere. The best idea would be to check it during dynamic analysis. You can do it using for example Android Studio and smalidea plugin. As far as I see you don't store the result of your ByteArrayToString function call. ...


2

Dex files have a maximum amount of methods which they can contain, specifically 64k methods. Jar files are just zip files containing class files. Knowing both of these, all you need to do is dex2jar (or whatever you're using to create the jar file from the dex file) each dex file individually. Then unzip each file to the same directory, enter the directory ...


1

The naming conventions for JNI functions are given by the Dalvik VM, a library couldn't change them and expect them to work, i.e. be callable from the Java part of the application. But, the Java_package_function convention is only needed for functions that Java wants to call, it it not neccesary for a C/C++ function calling another one. If you compile ...


1

I found solution myself. The thing is easy. It is one more Android Studio bug. I found that when IDA tries to connect to Dalvik debugger, I see following message in log: Ignoring second debugger -- accepting and dropping In not doubts no second debugger existed. Next, I found that this AVD doesn't work even with Android Studio and gives the same error. I ...


1

Setting the target app to debuggable in the android manifest and repackaging the apk has done the job. I didn't know that AVD automatically sets the APK to debuggable.


1

you can get system call stack with strace too. you just need to compile strace with libunwind. After that you just need to use -k to get system call stack for each system call.


1

JavaJournal, which was built on top of the pyspresso framework, was designed specifically for tracing method calls in Java.


Only top voted, non community-wiki answers of a minimum length are eligible