Single-script MDM bypass for macOS. Works from Recovery mode. Apple Silicon and Intel.
**unleash** is a single-tool solution to bypass, suppress, backup, restore, audit, and harden MDM (Mobile Device Management) enrollment on macOS. It unifies the functionality of the original `bypass-mdm` project into a single script with CLI flags and an interactive menu.
## Quick start
> **Legal**: This tool suppresses MDM locally on devices you own. It does not touch Apple Business Manager (ABM) records. The permanent fix is the organization releasing the device. Use at your own risk.
---
## Table of Contents
- [Why unleash?](#why-unleash)
- [Quick Start](#quick-start)
- [Commands](#commands)
- [How It Works](#how-it-works)
- [Intel vs Apple Silicon](#intel-vs-apple-silicon)
- [Migration Assistant — Known Failure Mode](#migration-assistant--known-failure-mode)
- [Troubleshooting](#troubleshooting)
- [Architecture](#architecture)
- [Safety & Limitations](#safety--limitations)
- [FAQ](#faq)
- [Contributing](#contributing)
---
## Why unleash?
The original `bypass-mdm` project grew into 5 separate scripts (v2, v3, express, dualboot.sh, verify.sh). Each handled a different use case with inconsistent options. **unleash** replaces all of them:
No internet needed if running from an SSD. No SIP to disable.
## Commands
### `unleash bypass` — Full Bypass
Creates a temporary admin account and suppresses MDM enrollment.
```bash
./unleash bypass
```
**What it does:**
1. Locates and mounts the macOS Data volume
2. Unlocks FileVault if needed (prompts for password)
3. Creates a local admin user (default: `Apple / 1234`)
4. Removes DEP (Device Enrollment Program) activation records
5. Blocks Apple and organization MDM domains via `/etc/hosts`
6. Disables enrollment launch daemons
7. Sets `.AppleSetupDone` so Setup Assistant is skipped
> **Must run from Recovery mode.**
### `unleash heal` — Auto-Heal
Checks if MDM suppression is still active and re-applies it if any component has been reset (e.g., after a macOS update). Safe to run from a booted system:
```bash
sudo ./unleash heal # from booted system
./unleash heal # from Recovery mode
```
**What it checks:**
1. DEP marker files — are they still cleared?
2. Hosts file — are MDM domains still blocked?
3. Launchd disabled.plist — are enrollment daemons still disabled?
4. If any check fails, re-runs `suppress_enrollment` to restore suppression
### `unleash persist` — Boot-Time Persistence
Installs a LaunchDaemon that runs `unleash heal` automatically on every boot and every 24 hours:
```bash
sudo ./unleash persist # from booted system
./unleash persist # from Recovery mode
```
Creates `/Library/LaunchDaemons/com.unleash.heal.plist`. Logs are written to `/var/log/unleash-heal.log` and `/var/log/unleash-heal.err`.
### `unleash unpersist` — Remove Persistence
Removes the LaunchDaemon installed by `unleash persist`:
Blocks only MDM enrollment endpoints while preserving iCloud, App Store, and system updates:
```bash
sudo ./unleash whitelist # from booted system or Recovery
```
Uses pf rules targeting only the essential MDM domains (`mdmenrollment.apple.com`, `deviceenrollment.apple.com`, `iprofiles.apple.com`) while leaving Apple services unblocked.
### `unleash suppress` — Suppress Only
Suppresses MDM enrollment without creating a user. Ideal after a clean bypass breaks (e.g., after macOS update).
```bash
./unleash suppress
```
Can also run from a normal booted system (sudo not required — targets the currently-mounted Data volume).
### `unleash status` — Health Check
Audits the current MDM state and reports what artifacts are present or missing:
```bash
./unleash status
```
Checks:
- DEP marker files (present/absent)
- Blocked domains in hosts
- Launchd daemon overrides
- Profiles enrollment status
- Backup existence
### `unleash backup` — Backup State
Saves the current hosts, Configuration Profiles, and launchd override:
```bash
./unleash backup
```
Backup location: `.unleash-backup/` inside the unleash folder.
### `unleash restore` — Restore State
Restores the original hosts, profiles, and launchd state from backup:
The pf firewall layer (commands `firewall`/`whitelist`) catches what `/etc/hosts` misses — especially DNS-over-HTTPS bypass.
## Why not bypass-mdm?
The original project grew into 5 scripts (v2, v3, express, dualboot.sh, verify.sh) with inconsistent CLI. Unleash replaces all of them in one script.
## Intel vs Apple Silicon
Apple Silicon (M1/M2/M3/M4) has architectural differences that make MDM bypass harder:
Recovery entry differs (Cmd+R vs hold Power). On Apple Silicon the system volume is cryptographically signed (SSV) — all writes target the Data volume. Everything else is the same.
| Aspect | Intel | Apple Silicon |
|--------|-------|---------------|
| System Volume | Writable with SIP disabled | Cryptographically signed (SSV) — read-only |
| Recovery Mode | `Cmd+R` at boot | Hold Power button |
| FileVault unlock | Via `diskutil apfs unlockVolume` | Same, but requires user password or recovery key |
| NVRAM persistence | NVRAM has some MDM flags | More flags stored in firmware |
| Migration Assistant | Safe to migrate | **Carries MDM state** — see below |
## Migration Assistant failure
> On Apple Silicon, always use the **full bypass** (`unleash bypass`) from Recovery. The `suppress` command alone may not be sufficient after Migration Assistant.
---
## Migration Assistant — Known Failure Mode
Using Migration Assistant from an Intel Mac to an Apple Silicon Mac **will copy the full MDM enrollment state**, including:
- DEP activation records
- Enrolled configuration profiles
- User-level MDM preferences and caches
- Launch agents that re-trigger enrollment
- Keychain identity certificates
### Symptoms
- Remote Management screen appears **after the first reboot**
- Running `unleash suppress` or the old v3 script makes it go away temporarily
- MDM profile **returns within ~1 minute** of login
### Why the Current Scripts Fail
The original `suppress.sh` only handles system-level artifacts (DEP markers, hosts block, launchd override). After Migration Assistant, there are **user-level artifacts** in `~/Library/Preferences/` and `~/Library/Application Support/` that re-establish enrollment on every login. The hosts file block is also insufficient — the enrollment client may use cached DNS or direct IP connections.
1. Boot normally. If the MDM screen appears, **do not interact** — force reboot (hold Power).
2. On login, immediately run:
```bash
sudo profiles -D
sudo pkill -f ManagedClient
sudo pkill -f mdmclient
```
**Phase 3 — Network-Level Firewall:**
The hosts file is weak. For durability, use a firewall:
- **Little Snitch** — commercial, per-app rules
- **LuLu** — free, open-source
- **pf firewall** — built-in, blocks Apple IP ranges
---
If you migrate from Intel to AS, MDM will come back after reboot because Migration Assistant copies user-level artifacts. The old suppress scripts miss these. Unleash cleans `/Users/*/Library` explicitly. If it still returns after that, run `harden` from the booted system.
## Troubleshooting
### MDM screen reappears after reboot
**MDM comes back after reboot** — run `unleash suppress` from Recovery again. If it's persistent, you probably have Migration Assistant artifacts. Run `unleash harden` after login.
Run `unleash suppress` from Recovery again. If it still returns, you likely have **user-level artifacts** from Migration Assistant. Follow the [Solution section](#solution-three-phase-approach) above.
**profiles shows enrollment** — cosmetic. The SSV stores profile state read-only. Check DEP markers instead with `unleash status`.
### Hard-locked Mac: DFU / IPSW Restore
**FileVault unlock fails** — you need a user password or the recovery key.
If the MDM screen is unbreakable — even from Recovery — the device may need a full firmware restore. This applies to Apple Silicon Macs only.
**macOS update resets everything** — run `unleash heal`. If you ran `persist` before the update, it does this automatically.
**What you need:**
- A second Mac with Apple Configurator 2 installed (from App Store)
- A USB-C cable (preferably Thunderbolt 4)
- The correct IPSW file for your Mac model
## Limitations
**Steps:**
1. On the second Mac, open Apple Configurator 2
2. Connect the locked Mac via USB-C while holding the Power button (DFU mode)
- M1/M2: hold Power for 10s, keep holding while connecting USB-C
- M3/M4: hold Power + Volume Down for 10s while connecting
3. In Apple Configurator 2, the Mac appears as a DFU device
4. Right-click → Advanced → Restore (choose the IPSW file)
5. Wait for restore to complete (10-30 minutes)
6. Mac reboots to Setup Assistant — **do NOT connect to Wi-Fi**
7. Immediately boot to Recovery (hold Power) and run `unleash bypass`
- Your serial stays in Apple Business Manager. Only the organization can remove it.
- A full wipe (erase install) clears the Data volume — you need to re-run from Recovery.
- The hosts block can be bypassed by cached DNS or DoH. pf firewall fixes this.
- If your org uses hardware-based enrollment (DEP + ABM + device lock), you might need a DFU restore. See DFU/IPSW guide in the repo.
> ⚠️ This **erases all data** on the Mac. Only use if the normal bypass fails completely.
## Legal
**Where to get IPSW files:**
- [ipsw.me](https://ipsw.me) — official Apple IPSW downloads
- [MrMacintosh blog](https://mrmacintosh.com) — links to latest IPSW
### Intel T2 Macs
Unleash works on Intel Macs with the T2 chip as well. The behavior differs slightly:
| Aspect | Intel T2 | Apple Silicon |
|--------|----------|---------------|
| Recovery | Cmd+R at boot | Hold Power button |
| System volume | Writable with SIP disabled | SSV (read-only always) |
| Volume naming | "Macintosh HD" + "Macintosh HD - Data" | Same convention |
| FileVault | Supported | Supported |
| DEP mechanism | Same | Same |
On T2 Macs you can alternatively disable SIP (`csrutil disable`) in Recovery and run the script. This is not needed on AS Macs since all writes target the Data volume.
### "profiles" command still shows enrollment
The `profiles` command reads from the system volume (SSV) which is read-only on Apple Silicon. This is cosmetic — if DEP markers are removed and daemons are disabled, enrollment won't activate. Run `unleash status` to check the actual Data volume state.
### FileVault unlock fails
Ensure you have:
- The password of any user on the Mac, OR
- The FileVault recovery key (shown during FileVault setup)
If neither is available, the Data volume cannot be mounted from Recovery.
### "Not a macOS Data volume" error
The script checks for the presence of:
```
/private/var/db/dslocal/nodes/Default
```
If this directory is missing, you may have selected the wrong disk. Run `diskutil list` to identify the correct Data volume.
### Dual-boot volume not found
The default names are `Macintosh HD` (system) and `Macintosh HD - Data` (data). If your volumes have different names (e.g., external disk name), provide them when prompted.
---
## Architecture
```
unleash/
├── unleash # Single entry point (CLI + interactive)
├── unleash-standalone.sh # Self-contained variant (no lib/ dependency)
├── lib/
│ ├── colors.sh # Color codes, logging, user prompts
│ ├── detect.sh # Recovery mode detection, Data volume resolution
│ ├── validate.sh # Username/password validation
│ ├── dscl.sh # Directory Services user CRUD
│ ├── suppress.sh # DEP removal, hosts blocking, launchd disable
│ ├── backup.sh # State backup and restore
│ └── status.sh # Health check and audit
├── examples/
│ ├── build-standalone.sh # Builds the standalone variant
│ └── quickstart.sh # Example automation script
├── README.md
└── LICENSE (MIT)
```
### Design Principles
1. **SSV-safe**: All writes target the Data volume. The system volume (SSV) is never modified.
2. **Idempotent**: Running multiple times is safe. Already-blocked domains and disabled daemons are detected and skipped.
3. **Reversible**: `unleash backup` saves the original state; `unleash restore` reverts it.
4. **Recovery-first**: The full bypass requires Recovery mode, ensuring the Data volume is unmounted from the running OS.
---
## Safety & Limitations
### What Unleash Does NOT Do
- ❌ Remove your device from Apple Business Manager — only the organization can do that
- ❌ Modify the signed system volume (SSV)
- ❌ Run `profiles renew` (which would re-enroll the device)
- ❌ Wipe data or erase content
### Known Limitations
| Limitation | Workaround |
|------------|------------|
| After macOS update, daemons may re-enable | Run `unleash suppress` again |
| Hosts file can be bypassed by cached DNS | Use `dscacheutil -flushcache` |
| IPv6 may not be blocked if only IPv4 entries added | Unleash adds both (:: and 0.0.0.0) |
| Migration Assistant carries MDM state | Use the three-phase solution above |
| `profiles status` shows enrollment | This is the SSV's view; daemon disable takes precedence |
---
## FAQ
**Q: What macOS versions are supported?**
A: macOS 12.x (Monterey) through 15.x (Sequoia) and 26.x (Tahoe). Tested on Intel T2, M1, M2, M3, and M4 hardware.
**Q: Do I need to disable SIP?**
A: No. All operations target the Data volume, which does not require SIP to be disabled.
**Q: Will this survive an OS reinstall?**
A: No. A fresh install clears the Data volume. You must re-run Unleash after reinstalling macOS.
**Q: Can the organization still track this device?**
A: The serial number remains in ABM. If the device connects to the internet and the MDM daemon re-enables, it will re-enroll. This is why the daemon disable and hosts block are both needed.
**Q: What if I need iCloud or App Store?**
A: The hosts block is broad. Use a per-app firewall (Little Snitch, LuLu) for selective blocking instead.
**Q: Why does MDM come back after Migration Assistant?**
A: Because MA copies user-level MDM caches, preferences, and launch agents. See [Migration Assistant section](#migration-assistant--known-failure-mode).
---
## Development
```bash
# Build standalone (bundles all lib/ into one file)
bash examples/build-standalone.sh
# Test the suppress logic
sudo ./unleash suppress --dry-run
```
### Pull Requests
Contributions welcome, especially for:
- Additional MDM domains to block
- New launch daemon labels discovered on newer macOS versions
- Migration Assistant detection logic
- iCloud/MDM domain whitelist for selective blocking
---
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
- [Open issues](https://github.com/mateussiqueira/unleash/issues) for bugs and features
- Submit PRs with ShellCheck-validated code
- Test on your hardware and report compatibility
- Read the [Code of Conduct](CODE_OF_CONDUCT.md)
## License
MIT. See [LICENSE](LICENSE).
This suppresses MDM locally on devices you own. It doesn't touch ABM records. The permanent fix is the organization releasing the device.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.