rename project to runaway

This commit is contained in:
2026-11-09 10:13:51 +08:00
parent 5857081832
commit c9feb8c05a
95 changed files with 1034 additions and 1034 deletions
+41 -41
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Troubleshooting — unleash
title: Troubleshooting — runaway
---
# Troubleshooting
@@ -16,7 +16,7 @@ Volume auto-detection failed.
**Fix:**
1. Run `diskutil list` to find your Data volume
2. Mount it: `diskutil mount /dev/diskXsY`
3. Re-run unleash
3. Re-run runaway
---
@@ -34,11 +34,11 @@ Volume auto-detection failed.
Various commands require root:
```
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Heal needs sudo: sudo ./unleash heal
[ERR] Hardening needs sudo: sudo ./unleash harden
[ERR] Audit needs sudo: sudo ./unleash audit
[ERR] Check needs sudo: sudo ./unleash check
[ERR] Firewall needs sudo: sudo ./runaway firewall
[ERR] Heal needs sudo: sudo ./runaway heal
[ERR] Hardening needs sudo: sudo ./runaway harden
[ERR] Audit needs sudo: sudo ./runaway audit
[ERR] Check needs sudo: sudo ./runaway check
```
**Fix:** Prepend `sudo` to the command.
@@ -51,18 +51,18 @@ The most common cause is **user-level artifacts** carried over by Migration Assi
**Fix from Recovery:**
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
**Fix from booted system:**
```bash
sudo ./unleash harden
sudo ./runaway harden
```
If it keeps returning:
```bash
sudo ./unleash persist # auto-heal on every boot
sudo ./unleash monitor # watch for re-enrollment
sudo ./runaway persist # auto-heal on every boot
sudo ./runaway monitor # watch for re-enrollment
```
---
@@ -73,7 +73,7 @@ System updates restore enrollment daemons automatically.
**Fix:**
```bash
sudo ./unleash heal
sudo ./runaway heal
```
If you ran `persist` before the update, this runs automatically on next boot.
@@ -85,19 +85,19 @@ If you ran `persist` before the update, this runs automatically on next boot.
This is **cosmetic**. macOS stores profile state on the read-only SSV (System Sealed Volume).
**Don't trust** `profiles status -v`.
**Trust** `unleash status -d` instead.
**Trust** `runaway status -d` instead.
---
### FileVault is enabled
Unleash detects FileVault and prompts for the recovery key or volume password.
Runaway detects FileVault and prompts for the recovery key or volume password.
**Fix:** If automatic unlock fails, unlock the volume manually in Disk Utility first:
1. Go to Disk Utility in Recovery
2. Select the Data volume
3. File → Unlock → Enter password
4. Re-run unleash
4. Re-run runaway
---
@@ -107,7 +107,7 @@ The basic `/etc/hosts` block includes `albert.apple.com` (iCloud activation) and
**Fix:** Use `whitelist` instead of the basic block:
```bash
sudo ./unleash whitelist
sudo ./runaway whitelist
```
Or manually remove these two lines from `/etc/hosts`:
@@ -133,14 +133,14 @@ Or manually remove these two lines from `/etc/hosts`:
### Monitor won't start
**Check:**
1. Is it already running? `sudo ./unleash monitor-status`
1. Is it already running? `sudo ./runaway monitor-status`
2. Permissions: needs root
3. Check logs: `/var/log/unleash-monitor.log`
3. Check logs: `/var/log/runaway-monitor.log`
**Fix:**
```bash
sudo ./unleash monitor-stop
sudo ./unleash monitor
sudo ./runaway monitor-stop
sudo ./runaway monitor
```
---
@@ -150,7 +150,7 @@ sudo ./unleash monitor
Recovery mode has no internet by default.
**Fix:**
1. Use a USB drive with unleash copied to it
1. Use a USB drive with runaway copied to it
2. Or connect to Wi-Fi in Recovery (top-right menu → Wi-Fi icon)
---
@@ -161,10 +161,10 @@ Recovery mode has no internet by default.
ERROR: Library not found: /path/to/lib/colors.sh
```
**Cause:** Running the source `unleash` script from outside the repo directory.
**Cause:** Running the source `runaway` script from outside the repo directory.
**Fix:**
- Use the standalone version (`unleash-standalone.sh`) instead
- Use the standalone version (`runaway-standalone.sh`) instead
- Or run from the repo root where the `lib/` directory exists
- Or install via Homebrew
@@ -176,8 +176,8 @@ pf might have existing rules that conflict.
**Fix:**
```bash
sudo ./unleash firewall-off # clear existing rules
sudo ./unleash firewall # re-apply
sudo ./runaway firewall-off # clear existing rules
sudo ./runaway firewall # re-apply
```
---
@@ -189,8 +189,8 @@ A full DFU/IPSW restore doesn't remove ABM assignment — the serial stays in Ap
**Strategy:**
1. After restore, **do not connect to Wi-Fi**
2. Boot to Recovery
3. Run `unleash bypass` before the device ever phones home
4. Run `unleash persist` and `unleash whitelist`
3. Run `runaway bypass` before the device ever phones home
4. Run `runaway persist` and `runaway whitelist`
5. Only then connect to the internet
The serial stays in ABM forever — but if the device never connects without protections, it won't re-enroll.
@@ -206,8 +206,8 @@ The serial stays in ABM forever — but if the device never connects without pro
**Fix:**
1. Make sure you have `gpg` installed
2. Import the signing key: `gpg --keyserver keys.openpgp.org --recv-key <KEY_ID>`
3. Try `sudo ./unleash update` again
4. Or download manually from [GitHub Releases](https://github.com/mateussiqueira/unleash/releases)
3. Try `sudo ./runaway update` again
4. Or download manually from [GitHub Releases](https://github.com/mateussiqueira/runaway/releases)
---
@@ -219,9 +219,9 @@ Error: ... homebrew-core ...
**Fix:** Make sure the tap is up to date:
```bash
brew untap mateussiqueira/unleash
brew tap mateussiqueira/unleash
brew install unleash
brew untap mateussiqueira/runaway
brew tap mateussiqueira/runaway
brew install runaway
```
---
@@ -234,7 +234,7 @@ All commands produce structured logs:
[INF] Data volume: /Volumes/Macintosh HD - Data
[ OK] Admin 'apple' created (UID 501)
[WRN] DEP activation record present
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Firewall needs sudo: sudo ./runaway firewall
[STP] Locating Data volume by APFS role...
[DBG] Checking pfctl availability
```
@@ -252,7 +252,7 @@ All commands produce structured logs:
Use `--verbose` for debug messages and `--log-file <path>` to save to a file:
```bash
sudo ./unleash heal --verbose --log-file /tmp/unleash.log
sudo ./runaway heal --verbose --log-file /tmp/runaway.log
```
---
@@ -263,22 +263,22 @@ Run these to gather information before seeking help:
```bash
# Quick health check
sudo ./unleash doctor
sudo ./runaway doctor
# Full system audit
sudo ./unleash audit
sudo ./runaway audit
# Generate report
sudo ./unleash report
sudo ./runaway report
# Dry-run a bypass
sudo ./unleash demo
sudo ./runaway demo
```
---
## Getting Help
- [GitHub Issues](https://github.com/mateussiqueira/unleash/issues)
- [Discussions](https://github.com/mateussiqueira/unleash/discussions)
- [Security Policy](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md)
- [GitHub Issues](https://github.com/mateussiqueira/runaway/issues)
- [Discussions](https://github.com/mateussiqueira/runaway/discussions)
- [Security Policy](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md)