Activation Lock on the iPhone 11, explained
The iPhone 11 runs A13 and ships from iOS 13, with updates available through iOS 18. Activation Lock behaviour is identical across all of them: the lock is registered to an Apple ID on Apple's activation servers and is re-checked every time the device is activated.
Nothing stored on the handset can bypass that check. A restore, a DFU restore or a fresh IPSW install all clear the operating system but leave Activation Lock in place — which is exactly why so many people discover that a restore did not help.
Why there is no software bypass for A13 devices
The checkm8 bootrom exploit affects A5 through A11 only. The iPhone 11's A13 chip fixed that class of vulnerability, so even the hardware-level jailbreak routes that exist for older iPhones are unavailable here.
Even if they were available, they would not help. Activation Lock is enforced by Apple's servers at activation time, not by a local flag. A tool that cannot change the server's answer cannot remove the lock, however deep its device access goes.
The owner route: recover the Apple ID first
The overwhelming majority of locked iPhone 11 devices are locked to an account the current holder can reach but has forgotten the password for. That is a password problem, not a bypass problem, and it has a fast fix.
Go to iforgot.apple.com and begin account recovery using the Apple ID email or phone number shown on the Activation Lock screen. Account recovery takes a few days by design, but it clears Activation Lock completely and costs nothing.
When the Apple ID is truly gone
If the account no longer exists, Apple's Activation Lock removal request is the correct path. You provide the device IMEI or serial number plus the original proof of purchase, and Apple validates it against the original sale record.
Repair shops should set expectations here: this is a documentation process, not a technical one. A device with no recoverable proof of purchase will not be unlocked, and a shop that promises otherwise is promising something it cannot deliver.
- 1Confirm the device is locked by an Activation Lock screen naming an Apple ID.
- 2Try to recover that Apple ID at iforgot.apple.com — Activation Lock clears the moment the owner signs in.
- 3If the Apple ID is unreachable, gather the original proof of purchase.
- 4Submit an Activation Lock removal request at apple.com/support (or at any Apple Store / Authorised Service Provider).
- 5Apple verifies the purchase, then clears the lock server-side — usually within a few days.
- 6Activate the iPhone again and complete setup with your own Apple ID.
Buying a used iPhone 11 — avoid the lock entirely
Before money changes hands, ask the seller to erase the device in front of you via Settings → General → Transfer or Reset iPhone → Erase All Content and Settings. A clean erase that reaches the Hello screen with no Activation Lock is the only reliable proof.
Then confirm with the IMEI on a service like Apple's own coverage checker, and keep the conversation in a channel that leaves a written record. That single step prevents the entire problem this guide solves.
Where FRPB fits — and where it does not
FRPB is an Android repair toolkit for Factory Reset Protection on Samsung, Xiaomi, Vivo, OPPO, Realme, Motorola, MediaTek and Qualcomm devices. It has no iOS capability whatsoever.
We deliberately do not sell an iPhone 11 unlock, because a legitimate one does not exist for a device that is not yours. If your workshop handles Android handsets alongside iPhones, FRPB covers the Android half honestly and accurately.
Safety, legality and when to stop
FRPB is intended strictly for authorised device owners and licensed repair professionals. You must own the device or hold explicit written permission from its owner. Using an FRP bypass tool on hardware you do not own may defeat an anti-theft control and can be illegal in your jurisdiction.
Stop and reassess if the device reports a bootloader state you did not expect, if the model or chipset FRPB detects does not match the handset in front of you, or if the operation halts mid-way. A mismatched firmware package is the single most common cause of a hard brick — abandoning an operation is always cheaper than recovering from one.