[Codeblin]

Bump update frida to the latest PyPI runtime in an isolated venv, expand SSL unpinning for Frida 17, and stop nested progress bars from flickering during fix/ready.

Summary

Frida hook on a rooted x86_64 emulator was failing because update frida synced to the pinned runtime instead of PyPI latest, so the client stayed on 17.25.1 while a newer server was available. droidreaver update frida / use latest now install the latest runtime into ~\.droidreaver\venvs\frida-<ver> and set it active.

Also in this branch:

• Broader SSL pinning bypass (Java, OkHttp, NSC, WebView, TrustKit, native libssl) with Frida 17 export lookup (Process.getModuleByName().findExportByName).
• fix / ready no longer nest two Rich live spinners (the download vs “Fixing: push frida-server” flicker).
• ready only starts a 32-bit companion frida-server when the image actually has that ABI; skip a missing binary instead of nohup failing on frida-server-x86.
• CLI banner/console UX, faster adb-based app listing, attach-by-default hook with --spawn.
• Unit tests use com.codeblin.droidreavervault instead of third-party package names.

Testing

• python -m pytest
• droidreaver --help
• droidreaver status --offline

Device or Emulator Coverage

If this affects device flows, note what you tested:

• Setup: Android Studio AVD emulator-5554, ro.product.cpu.abilist=x86_64,arm64-v8a, Vault primaryCpuAbi=x86_64
• Rooted: yes (adb root)
• Command: droidreaver update frida then ready then hook / hook --spawn on com.codeblin.droidreavervault
• Result: attach worked after matching client/server to 17.25.2. Earlier Failed to attach: the connection is closed was a version mismatch, not ARM translation.

Supply Chain Impact

• No new downloads or network calls
• New/changed downloads are documented in THREAT_MODEL.md
• Checksums/signatures were added when upstream provides them

Existing PyPI frida and GitHub frida-server fetch paths are unchanged; update frida now targets latest instead of the pin. No new package sources.