# RocketLauncher RocketLauncher is an unresolved application or service name in the notebook's distribution sequence; it matters as a lead whose exact product identity must not be overfitted. ## Historical and Technical Context The four persistence classes are the page’s conceptual center. A tethered jailbreak requires a computer-assisted boot after every restart; a semi-tethered or semi-untethered system boots stock and must re-enable modifications; an untethered jailbreak persists through ordinary reboot. The author then shifts to **forensic observables**—logs, bundle names, and launcher artifacts—suggesting a desire to detect what installation path or modified environment was present rather than merely perform a jailbreak. ## Role in Scanned_20260730-1802 The primary identifying evidence appears on PDF page 21. A taxonomy page with a short heading, four persistence terms, and a lower log-artifact checklist. A rectangular patch at upper right looks like a removed sticky note. Within that page, RocketLauncher helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 21: "RocketLauncher" **Evidentiary status:** Visible evidence: explicit persistence taxonomy and artifact-hunting commands. Strong inference: troubleshooting or forensic verification. “iBootUp,” `pilot.mobile`, RocketLauncher, and “air Safari” require source recovery. The canonical name **RocketLauncher** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers. ## Relationships RocketLauncher is linked back to [[Scanned_20260730-1802|Scanned_20260730-1802]] as its primary notebook context. No additional page-level relationship has yet been confirmed. ## Cross-Notebook Significance This page’s concern with reboot persistence parallels page 28’s distinction between legacy and UEFI boot media and page 6’s separation of network daemons from key custody. ## Missed Signals and Open Leads Identify the platform and log source. Determine whether `pilot.mobile` is a bundle, process, MDM profile, or handwritten inversion. Recover the removed sticky note if separately scanned. ## Sources - [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF page 21. - `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`.