Root My Galaxy 0.3.54

SHA-256: 633b4b71d8dc7cfd33f4c537a70e4b0ea8d87a48070944f8c6d164f59073b029

Changes since v0.3.53.

What's changed

• #45 Fix soft reboot by pre-arming bootstrap root session

Full changelog

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

#45 — Fix soft reboot by pre-arming bootstrap root session

Problem

After a successful CZG3 root and KernelSU late-load, Soft reboot after root fails with:

su: connect daemon: Permission denied

The bootstrap helper is a client of /data/local/tmp/temp_su.sock; helper -c ... does not itself retain root. Reconnecting from the app after KernelSU late-load can therefore be denied even though root and the KernelSU control channel are already valid.

Fix

Keep the soft-reboot execution channel open across KernelSU activation:

1. stage the exact verified ksud as before;
2. before --late-load, open a second bootstrap-root helper request;
3. the root shell prints an arm marker and blocks on stdin;
4. run the existing --late-load and verify KernelSU normally;
5. manual install persists its install receipt/history; Auto Root persists its boot receipt;
6. the existing post-success soft-reboot call writes go to the already-open root session;
7. that UID-0 shell executes /data/local/tmp/ksud-s25u-kdp soft-reboot directly.

No post-KernelSU reconnect to the bootstrap daemon is required.

Scope

• app-only change;
• no payload/exploit changes;
• no observer or diagnostic instrumentation;
• no P0/FOPS/reclaim/timing changes;
• no ksud debug su or KernelSU allowlist dependency;
• supports standalone and Shizuku transports;
• armed session expires automatically if the late-load never reaches the trigger point.

This preserves the minimal pre-instrumentation CZG3 runtime that just succeeded on-device in 2 exploit attempts.