🚀 A12 Bypass Setup & Operation Guide
📋 Initial Setup

Server Configuration:
bash

Get your computer's network IP address
ipconfig getifaddr en1

Start the server (replace 192.168.0.103 with your actual IP)
cd server/
php -S 192.168.0.103:8000 -t public
2. File Configuration:

Open downloads.28.png in a text editor

Find and replace all paths to badfile.plist with your server IP

Example: http://192.168.0.103:8000/badfile.plist

🔄 Activation Process (3 Stages)
🔄 Stage 1 - Initial Activation:

The generator program automatically sends downloads.28.sqlitedb

The device will reboot after this stage

Important: Periodically delete downloads.28.sqlitedb-shm and downloads.28.sqlitedb-val files in the downloads folder before reboot

🔄 Stage 2 - Metadata Transfer:

After first reboot, the server creates iTunesMetadata.plist

Manually copy this file to /var/mobile/Media/Books/ folder

Reboot iPhone - asset.epub will appear after this

🔄 Stage 3 - Data Population:

Server receives requests like: 192.168.0.105:52588 [200]: GET /firststp/8dc56bf27aa8b527/fixedfile

The asset.epub book gets populated with data from these requests

Do not stop the server until the process fully completes!

💡 Important Notes
GUID for Generation:

Get it manually from: https://hanakim3945.github.io/posts/download28_sbx_escape/

Critical Reminders:

✅ Server must run continuously until the final reboot

✅ Don't interrupt the process after launching activator.py

✅ Monitor server logs to track progress

✅ Keep the server active throughout all stages

# iOS Activation Tool Suite

A complete, end-to-end solution for iOS device activation management. This repository contains both the client-side automation logic and the server-side infrastructure required to handle device activation payloads.

## Architecture Overview

The suite is divided into two core components:

- **Client Automation (`client/`)**: A Python-based utility that interacts directly with connected iOS devices via USB. It handles lifecycle management (reboots), system log analysis, and filesystem operations (AFC).

- **Server Backend (`server/`)**: A PHP application that dynamically generates device-specific activation payloads. It serves as the central authority for handling device requests and delivering the necessary configuration databases.

## Repository Structure

```
.
├── client             # Python client application
│   ├── activator.py   # Main automation entry point
│   └── README.md      # Client-specific documentation
└── server             # PHP backend infrastructure
    ├── assets         # Device configuration storage
    ├── public         # Web root
    ├── SETUP.md       # Server deployment guide
    └── templates      # SQL templates for payload generation
```


## Prerequisites

### Client-Side (macOS/Linux)

- Python 3.6+

- `libimobiledevice` (via Homebrew on macOS)

- `pymobiledevice3` (via pip)

- `curl`

### Server-Side

- PHP 7.4 or newer

- SQLite3 extension enabled

- Write permissions for cache directories


### 1. Server Deployment

Deploy the contents of the `server` directory from the release package to your web host. Ensure the `public` folder is set as the document root.

See [server/SETUP.md](server/SETUP.md) for detailed configuration steps.

### 2. Client Configuration

Update the `activator.py` script to point to your deployed server URL before running.

### 3. Run the client tool
```
sudo python3 client/activator.py
```


NOTE: The OFFLINE version will NOT work, sorry i was sick a made a mistake.

## Disclaimer

This tool is provided for educational and research purposes only. The authors are not responsible for any misuse of this software or damage to devices. Ensure you have authorization before performing operations on any device.