Root My Galaxy 0.3.59
SHA-256: 2ec2ade6a7b0e5f5196158404ed1704c1903264bb24538f47e0908f3f85f63c1
Changes since v0.3.58.
What's changed
- #53 Treat verified Auto Root as success before ksud refresh
Full changelog
Detailed pull-request notes for all changes included in this release.
#53 — Treat verified Auto Root as success before ksud refresh
Fixes the real-device v0266 Auto Root run that acquired root successfully but was classified Failed at KernelSU staging with cp: /data/local/tmp/ksud-s25u-kdp: Text file busy.
The log proves the exploit completed with done=1 root=1 and uid -> 0; the failure happened only because v0266 auto-late-load had already made /data/local/tmp/ksud-s25u-kdp an executing daemon and AutoRootRunner then tried to truncate/overwrite that executable with cp.
Changes:
- if auto-late-load is already active, verify KernelSU first and make that the success boundary;
- persistent ksud refresh becomes best-effort maintenance after verification and can no longer convert a valid root into Failed;
- refresh uses copy-to-temp + chmod + atomic rename, avoiding ETXTBSY when replacing an executing ksud pathname;
- the historical client late-load fallback still requires successful staging, but uses the same atomic replacement;
- no exploit, payload, FOPS, timing, Auto Root scheduling, ADB/Shizuku or soft-reboot implementation changes.
This also allows the existing post-root path to actually run; in the reported run it never reached PostRootAutomation because staging threw first.
Payload provenance
- Payload commit:
7d18ae346d1798fccc3530be5abd3e9848f5ee69 - Root helper SHA-256:
0b4a12341225526a6e26daa9db2ba9615e7203b862a68b502fd4030c09a671c9 - Root helper synchronized from feed:
true