Root My Galaxy 0.3.69

SHA-256: e0d68c2f2e22a1f4a30c337165ea003c7500c0a0cfdd0d353d80cb08a2396b2b

Changes since v0.3.68.

What's changed

• #55 Share one exploit route policy between Manual and Auto Root

Full changelog

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

#55 — Share one exploit route policy between Manual and Auto Root

What

Replaces the firmware-specific ZZI4 route special case in the frontend with an ExploitRoutePolicy that travels with TargetProfile.

The optional routePolicy block is parsed from the support manifest and persisted by KnownGoodPayloadStore, so Manual Online, Manual Offline and Auto Root derive their environment from the same policy rather than maintaining separate firmware logic.

Behaviour

• CZG3: slideRoute: default, 24 supervisor attempts, boot-scoped P0 offset cache; existing behavior is preserved.
• ZZI4: slideRoute: auto, 24 supervisor attempts, boot-scoped P0 offset cache, shell transport preferred. The current payload itself prefers tracefs and logs the explicit physical-P0 fallback.
• ZZI4 Manual and Auto Root now log and use the same policy.

SLIDE_P0_OFFSET is only populated from an offset captured under the current boot token; it is never reused across boots.

The companion payload/feed changes are now merged in Root-My-Galaxy-Payloads-S938B: #36 publishes the tracefs+physical-alias/bounded-retry payload and #35 publishes the target route policy.

Compatibility

• A feed without routePolicy yields ExploitRoutePolicy.LEGACY.
• Invalid bounded numeric fields fall back individually instead of discarding valid policy fields.
• Cache reuse includes routePolicy, so a feed-only policy change rewrites an otherwise hash-identical known-good cache.
• Schema v3 remains additive/backward-compatible.

Validation

• :app:testDebugUnitTest
• :app:lintDebug
• :app:assembleRelease
• Review P1: route policy included in cache reuse identity
• Review P1: malformed fields degrade independently
• Hardware: ZZI4 Manual Online, then Auto Root after a full reboot, confirming both report route=auto and the payload reports data_mode=physical-alias on tracefs discovery

Hardware reliability is intentionally not claimed by this PR; it establishes one route-policy source of truth across the app.

Payload provenance

• Payload commit: 862f116909d90612b2d1740bb664d0f799e43ea9
• Root helper SHA-256: 788611baf566f0ca9008d28fa7d1b1edb4657efc56e4b5ac24b319ae12519dd4
• Root helper synchronized from feed: true