Feed me oil full apk apk#
With this keystore and its password, I tried to generate my app apk in 'release' mode, then. Next, the default keystore of Android Studio is located on. In my case, I found that the password is 'android'. But since everything is proguarded, I'm not sure that you can ever re-compile this half-baked Java code to a working apk. which contains your keystore passwords, for example in Linux: strings taskArtifacts.bin grep storePassword -A1. In my opinion, decompiling with dex2jar and JD-GUI is only helpful to get a better understanding what the classes are doing, just for reading purposes. After I decompiled with apktool I exchanged a full byte code file without logging by a full byte code file with logging, re-compiled and signed it and I was able to install it on my device.Īfterwards I was able to see the logs in Android Studio as I connected the app to it. In my test, the original release apk had no logging. signs the app the the debug key (the password is android) Jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore ~/.android/debug.keystore modified.apk androiddebugkey generates a folder with smali bytecode files. But nobody explained, that you have to sign the app again.
The way I was able to modify a (my) well-protected apk (Proguard, security check which checks for "hacking tools", security check, which checks if the app is repackaged with debug mode.) is via apktool as already mentioned by other ones here. This maybe works for non-protected apks (no Proguard), but nowadays nobody deploys an unprotected apk. The answers are already kind of outdated or not complete.
0 kommentar(er)
