apk-reverse

Run jadx to decompile Java code and apktool to unpack smali and resources, then inspect AndroidManifest.xml and the main package. The bundled decode script runs both tools in one pass and summarizes package name, Java files, smali dirs, and native libraries.

Hook okhttp3.CertificatePinner.check to return nothing and replace TrustManagerImpl.verifyChain to return the untrusted chain. The references include a universal bypass script covering OkHttp, Retrofit, WebView, and Flutter's libflutter.so.

Use jadx first to read high-level Java logic and search class and method names. Switch to apktool output when jadx decompilation is incomplete or obfuscated, or when you need to actually patch smali and rebuild the APK.

Yes. Edit smali or the manifest in the apktool output, then rebuild with apktool b, align with zipalign, and sign with apksigner using a debug keystore. The rebuild-sign-install script automates this chain and can adb install the result.

The XOR key was parsed incorrectly, usually because byte values were scraped from the whole class file instead of only the byte[] initializer, inflating the key length. Parse just the array initializer and sanity-check against a known string like UTF-8.

Switch when the Java layer is only a JNI wrapper, key logic disappears after System.loadLibrary, or signing and certificate validation live in native code. Use radare2 for quick triage and IDA for deep decompilation of the .so.