A success line in the message column only means this environment path finished: the device ID is written into the main program, and the developer disk image and pairing certificate have been handled by the activator steps. Business content, login accounts, and each phone exit proxy sit outside these buttons.
The activator touches the environment path
The offline activator is a desktop client connected to the computer. It keeps pairing certificates, disk images, WiFi debugging, and the self-activation test in one window. Offline in the name means that after the environment is ready, the script can run on the phone by itself. The activator still needs the computer open while you operate it.
Its batch menu covers these jobs: write the device ID into the main program, generate and push the pairing file, push the developer disk image, scan the WiFi IP of devices that are already initialized, run the self-activation environment in one pass, then run the self-activation test. For a single phone you can also restart, view the pairing certificate, and copy the device ID or ECID.
The main-program BundleId is required. Separate several package names with English commas. Fill in the proxy-program BundleId when you want Start automation service. You can copy a package name from i4Tools: right-click the app and choose Copy identifier. That field decides which app receives the device ID. It does not decide whether the phone holds copy, images, or a signed-in session.
Disk image files live in bridgebin\config\DeveloperDiskImage, and the version has to match the phone system. The phone needs to be unlocked and to trust this computer. If pairing fails, check whether a lock-screen passcode is set and whether the trust dialog on the phone was dismissed.
Three things done elsewhere: content, accounts, proxies
| Item | Does the activator do it | Where it goes instead |
|---|---|---|
| Device ID, disk image, pairing | Yes | Message column and disk-image column |
| Photos, videos, publishing copy | No | Upload through mirroring, or prepare them inside the business app |
| Apple ID and app logins | No | Sign in on the phone, and record which account belongs to which device |
| Each exit proxy | No | Soft-router policy or the phone proxy, and record host and port in the ledger |
Content means the material you will publish or recognize. The activator has no Upload to Photos or Write copy action. On iOS 15 and later, if you later use the offline main program to send images, that is a mirroring or main-program feature, from v7.2.0 onward. Below iOS 15 this offline build cannot be used. From 7.0.0, single-app installs only the main program. Dual-app also installs the proxy IPA. Those installs happen before or outside activator initialization. The assets themselves are still transferred separately.
Accounts split into two layers. One is the developer identity that signs the IPA: an Apple individual developer account is 688 yuan a year, up to 100 devices, iOS 12 and later. That fee is Apple signing. The other layer is the Apple ID on the phone and the business app accounts. The activator signs in to neither. TrollStore covers iOS 15 through 16.6.1. After a restart the signature drops. When the main program will not open, the usage conditions written earlier have to be done again.
Proxies are easy to mix up with the self-activation test. When the test fails, the docs require WiFi debugging on, the pairing certificate pushed, and the phone on WiFi (cellular will not do). External VPN mode also requires LocalDevVpn already installed. A passing test means WiFi debugging, pairing, and LocalDevVpn are all in place. The node host, port, and account password are written in the soft-router policy, or in the phone proxy settings, and copied into the ledger: device ID, business account, proxy address, port, protocol. Refreshing devices in the activator does not bring those columns back.
For the batch that uses board-free USB HID, do not tap Start Automation in the activator on the same phone. That capability is available from EasyClick iOS USB 10.7.0 (2026-09-08). The phone needs iOS 17 or later, no Bluetooth board and no OTG board, and it is mutually exclusive with Start Automation.
About EasyClick: A mobile automation script development platform covering three phone ecosystems: Android without root, iOS without jailbreak, and HarmonyOS. It also offers Apple script writing, Apple cluster control, Android cluster control, remote cloud control, and AI phone cluster control. → Explore all products · iOS cluster control product site
Ready to build it for real?
Every approach in this article can be built with EasyClick capabilities on iEasyClick — full documentation, developer tools and automation products, free to try.