github igorcv88/Root-My-Galaxy-Extended v0.3.57
Root My Galaxy 0.3.57

latest releases: v0.3.104, v0.3.103, v0.3.102...
one month ago

Root My Galaxy 0.3.57

SHA-256: 35d0aabe7ea0ea269b54b460c432e9e0b87ad2ab59a987d05c450802589c9814

Changes since v0.3.56.

What's changed

  • #49 Post-root Wireless ADB + Shizuku lifecycle without Tasker
  • #50 Fix first-run pairing permission and invalidate legacy offline cache
  • #51 Restore save all and selected History logs

Full changelog

Detailed pull-request notes for all changes included in this release.

#49 — Post-root Wireless ADB + Shizuku lifecycle without Tasker

Scope

Keeps root acquisition isolated, then automates the userspace work that previously required Tasker.

Critical root path

  • Auto Root remains offline + standalone through exploit execution and KernelSU verification.
  • Wireless ADB and Shizuku are never prerequisites for acquiring root.
  • A successful root/KernelSU result is checkpointed in History before post-root work begins.
  • Post-root failures never retroactively convert a verified root into failure.

Post-root automation

Ports the tested local Wireless ADB stack from the HyperRamzey fork:

  • persistent ADB key;
  • TLS/SPAKE2 pairing;
  • mDNS discovery of the dynamic Wireless Debugging port;
  • authenticated local connection to 127.0.0.1;
  • one-time root grant of WRITE_SECURE_SETTINGS, allowing later boots to set adb_wifi_enabled=1 without Tasker;
  • automatic Shizuku start.sh execution and Binder verification after root (enabled by default).

When Soft reboot after root is enabled, the old bootstrap-daemon handoff is replaced with the tested KernelSU userspace lifecycle:

post-fs-data → services → boot-completed → zygote restart

Shizuku is started before the zygote restart so its shell-owned server does not depend on reconnecting after userspace comes back.

Payload/helper coupling

  • v3 support manifests accept optional rootHelper metadata;
  • online/offline payload use verifies the APK-bundled libcve43499root.so against that metadata and fails closed on mismatch;
  • the release workflow resolves and pins the payload repository main commit, verifies the published helper size/SHA-256, embeds that exact helper in the APK, and records payload/helper provenance in release notes;
  • v0265 feeds without rootHelper remain accepted during the transition.

Dependency / rollout

Do not release this app before payload PR #29 is merged and Atualizar Payloads → Exploit has published the v0266 exploit/helper metadata on payload main.

Validation status

No full Gradle build/lint or integrated hardware validation was run in this conversation environment. Unit-test coverage was added for optional rootHelper manifest round-tripping. The branch contains a minimal three-step real-device validation plan intended to avoid unnecessary reboot/sweep testing.

#50 — Fix first-run pairing permission and invalidate legacy offline cache

Follow-up to merged PR #49 and the failed release validation.

Changes:

  • fail closed on pre-v0266 offline caches that do not contain rootHelper metadata; one successful Manual Online run is required to establish a helper-bound cache;
  • do not start the notification-only pairing FGS blindly from Auto Root/background execution;
  • on a successful manual root, launch a one-shot visible pairing setup activity that requests POST_NOTIFICATIONS before starting the RemoteInput pairing notification;
  • document the v0266 root path, Offline/Auto Root policy, local Wireless ADB/Shizuku lifecycle, soft reboot route and full source/provenance credits.

The earlier SupportManifestRootHelperTest failure was a local-JVM Android org.json stub issue, not a manifest parser failure. main already includes org.json:json for unit-test runtime so those tests exercise real JSON semantics.

No exploit/payload code is changed here.

#51 — Restore save all and selected History logs

Restores the History export functionality lost during the rollback without touching root runtime code.

  • keeps existing per-run plain .log export;
  • adds Save in the History header to export every completed run as a ZIP;
  • selection mode adds Save selected while retaining Select all / Clear / Delete;
  • ZIP contains one stable .log snapshot per run; active Running entries are excluded from bulk export;
  • adds only non-translatable UI labels to avoid reopening MissingTranslation lint failures;
  • updates README documentation.

No exploit, Auto Root, payload, KernelSU, ADB or post-root execution code is changed.

Other changes

Commits merged directly without an associated pull request:

  • 0e2419c Run manifest JSON tests against real JVM org.json

Payload provenance

  • Payload commit: f598ddb492cd1bba7480ac378b34679d8df67eb3
  • Root helper SHA-256: 0b4a12341225526a6e26daa9db2ba9615e7203b862a68b502fd4030c09a671c9
  • Root helper synchronized from feed: true

Don't miss a new Root-My-Galaxy-Extended release

NewReleases is sending notifications on new releases.