Enter your access key
One use per key. Your key is validated when you start.
Your details
Credentials are used once for the enrollment exchange and discarded after the request completes.
Working…
Contacting Google — this can take up to a minute.
- Validating access key
- Launching browser session
- Signing in to Google
- Exchanging OAuth tokens
- Registering device
- Pushing policy fetch
Something went wrong
You can safely try again.
About AutoEscape
Re-registers a managed Chromebook under your own account, clearing the organization's enrollment.
Requirements
- Your school Google account and password
- Device serial number — lock screen, press
Alt + V - A valid, unused access key
Get an access key
Access keys are distributed through the Discord server. Join, open a ticket, and request one.
Join DiscordHow it works
Your credentials drive Google's device enrollment sign-in flow directly. The resulting OAuth exchange registers the device and clears the previous organization's management record.
After running
Wait 5 minutes, then press ESC + REFRESH + POWER, then Ctrl + D, Enter, wait, Enter. Continue setup normally.
Privacy
End-to-end encrypted with the server's public key. Credentials are encrypted in your browser with AES-256-GCM, and the AES key is wrapped with the server's RSA-4096 public key before transmission. Only the server holds the private key. Nothing readable is sent over the wire.
Notes
- Works only if your organization permits enrollment
- Each access key is valid for one run
- Keys are issued through the Discord server