Skip to content
How to Fix Apple Error 3194: Target iOS build is no longer cryptographically signed by ApMappleCare Community ↗
Error 3194 iOS / iPadOS Firmware Unsigned / Deprecated

How to Fix Apple Error 3194: Target iOS build is no longer cryptographically signed by Ap

Reference ID: Error 3194 •

1. Overview & Failure Manifestation

Error 3194 manifests as a hard-block during the firmware verification handshake between the host Mac (running Finder on macOS 10.15+ or iTunes 12.12+ on Windows) and Apple’s Tatsu Signing Server (TSS) at gs.apple.com (IPv4: 17.253.144.10/24, IPv6: 2600:1f18:247b::/48). The exact alert dialog reads:

“The iPhone [DeviceName] could not be restored. This device isn’t eligible for the requested build.”

In Finder, the progress bar stalls at “Verifying iPhone Restore with Apple…” for 15–30 seconds before the modal appears. In iTunes, the error code 3194 is surfaced directly in the summary pane. Simultaneously, the device screen displays the Connect to Computer / Recovery Mode glyph (Lightning cable + Mac icon) with a static backlight at 0x3F PWM duty cycle (≈120 nits).

Console.app on the host Mac (filter: subsystem == "com.apple.MobileDevice") emits the following structured log sequence at FAULT level:

2024-11-15 14:32:17.412-0800 0x1a3d  Fault  0x0  com.apple.MobileDevice  [AMD] AMRestoreVerifyTSSResponse: TSS response status = 94 (kAMDRestoreErrorNotEligibleForBuild)
2024-11-15 14:32:17.413-0800 0x1a3d  Fault  0x0  com.apple.MobileDevice  [AMD] AMRestorePerformRecovery: Restore failed with error 3194: The requested build is not signed.
2024-11-15 14:32:17.414-0800 0x1a3d  Default 0x0  com.apple.MobileDevice  [USB] Device 0x1000004a5 (iPhone15,3) transitioned to kAMDDeviceStateRecoveryMode

The device's ap_nonce (generated by Secure Enclave P-384 ECDSA) was submitted to TSS via the TSSRequest plist (keys: ApNonce, ApECID, ApBoardID, ApChipID, ApSecurityDomain, UniqueBuildID). TSS responded with HTTP 200 but JSON payload {"status":94,"message":"This device isn't eligible for the requested build"}. The host aborts the AMRestore pipeline at AMRestoreVerifyTSSResponse (frame 12 in AMRestore.dylib), leaving the device in kDFUStateRecoveryMode (IBoot stage 2) with NAND GPT partition map intact but OS partition unmounted.

2. Silicon & Firmware Architecture Root Cause

At the silicon level, Error 3194 is a cryptographic policy enforcement failure orchestrated by the Secure Enclave Processor (SEP) firmware (sepOS) in concert with the Application Processor (AP) Boot ROM (iBoot). When the host initiates a restore, the following hardware/firmware sequence executes:

  1. DFU/Recovery Mode Entry: The PMIC (PMGR on A12–A17, PMU on A11 and earlier) asserts PMIC_RST_N low for 200 ms, forcing the AP into DFU_MODE (GPIO_12 pulled high on J85/J86 test points). The Boot ROM (address 0x180000000 on A14+) enumerates USB 2.0 HS (VID 0x05AC, PID 0x1227 for DFU, 0x1281 for Recovery).
  2. ApNonce Generation: The SEP (ARM Cortex-M33 on A14+, M3 on A12–A13) generates a 32-byte ApNonce via TRNG (True Random Number Generator, NIST SP 800-90B compliant) and signs it with the device-unique UID key (AES-256, fused at 0x2000_0000 in SEP keybag). This nonce is sent to the host over USB control endpoint 0 (EP0 IN, 64-byte max packet).
  3. TSS Handshake: The host wraps the ApNonce, ApECID (64-bit, fused at 0x2000_0100), ApBoardID (e.g., 0x000D for N71AP), ApChipID (e.g., 0x8015 for T8103), and UniqueBuildID (e.g., iPhone15,3_18.1_22B83) into a TSSRequest plist, POSTed to https://gs.apple.com/TSS/controller?action=2 over TLS 1.3 (AES-256-GCM, SNI=gs.apple.com).
  4. TSS Policy Evaluation: Apple's TSS cluster (running on Xeon Scalable, Linux 6.8, Java 21) evaluates the request against the Signing Window Matrix. Each iOS build has a StartTimestamp and EndTimestamp (Unix epoch, UTC). For iOS 18.1 (22B83), the window closed at 1731542400 (2024-11-14 00:00:00 UTC). The request timestamp 1731712337 exceeds EndTimestamp → status 94.
  5. APTicket Issuance Failure: Normally, TSS returns an APTicket (DER-encoded ASN.1, signed by Apple's TSS Root CA — SHA-384/ECDSA-P384). The AP verifies the ticket chain: Leaf → Intermediate → Root using certificates stored in Boot ROM (immutable). Without a valid ticket, iBoot refuses to decrypt the KernelCache (AES-256-XTS, key derived from GID + ApNonce) and mount the root filesystem.
  6. NAND Controller State: The NVMe controller (Apple custom, PCIe 3.0 x2 on A14+) holds the OS partition (APFS, container UUID F8B3...) in UNMOUNTED state. The Firmware partition (offset 0x40000000, size 0x800000) remains valid but unbootable without a signed iBSS/iBEC chain.

The root cause is strictly server-side policy: Apple has revoked the signing certificate for the requested BuildIdentity. No client-side action (cache clear, hosts file edit, time rollback) can bypass this because the ApNonce is single-use and the TSS response is cryptographically bound to Apple's root of trust.

3. Diagnostic Verification & Terminal Commands

Execute the following commands on the host Mac (macOS 14.0+ required for log predicate syntax). Each command isolates a specific subsystem.

3.1 Live TSS Handshake Capture

log stream --predicate 'subsystem == "com.apple.MobileDevice" and category == "AMRestore" and eventMessage contains "TSS"' --style syslog --color always

Output fields:

  • timestamp: Mach absolute time (ns since boot)
  • process: AMDRestore (PID varies)
  • eventMessage: Contains TSSRequest plist (XML) and TSSResponse JSON
  • status: Integer — 0 = success, 94 = not eligible, 96 = device not supported

3.2 USB Enumeration & Device State Verification

system_profiler SPUSBDataType -json | jq '.SPUSBDataType[] | select(.[]? | ._name? | contains("iPhone") or contains("iPad")) | .[] | {name: ._name, vendor_id: .vendor_id, product_id: .product_id, serial_num: .serial_num, speed: .speed, location_id: .location_id}'

Confirm product_id = 0x1281 (Recovery) or 0x1227 (DFU). speed must be 480 Mb/s (USB 2.0 HS). If 12 Mb/s (FS), the PHY (USB2PHY on AP) failed high-speed negotiation — check D+/D- termination resistors (45 Ω ±10%) on logic board.

3.3 ApNonce & ECID Extraction (Device-Side)

ideviceinfo -k UniqueDeviceID -k ApNonce -k BoardID -k ChipID -k SecurityDomain 2>/dev/null || echo "libimobiledevice not installed; brew install libimobiledevice"

Requires libimobiledevice 1.3.0+. Output example:

UniqueDeviceID: 00008020-00123456789ABCDE
ApNonce: 8f3a2b1c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a
BoardID: 13
ChipID: 32789
SecurityDomain: 1

3.4 TSS Request/Response Replay (Offline Analysis)

cd ~/Library/Logs/MobileDevice/AMDRestore
latest=$(ls -t *.log | head -1)
grep -A 20 'TSSRequest' "$latest" | head -30
grep -A 5 'TSSResponse' "$latest" | head -10

Look for <key>UniqueBuildID</key><string>iPhone15,3_18.1_22B83</string> and response "status":94.

3.5 Network-Level TSS Connectivity Test

curl -v --tlsv1.3 --ciphers TLS_AES_256_GCM_SHA384 \
  -H "Content-Type: text/xml" \
  -d '@/dev/stdin' \
  "https://gs.apple.com/TSS/controller?action=2" <<'EOF'




    ApNoncejzoLHHZeZ3qLmA0eL0tLXG1+j6o=
    ApECID123456789012345
    ApBoardID13
    ApChipID32789
    ApSecurityDomain1
    UniqueBuildIDiPhone15,3_18.1_22B83


EOF

Expect HTTP 200 with JSON {"status":94,...}. If HTTP 403/502, check /etc/hosts for gs.apple.com overrides (common in jailbreak tooling).

4. Step-by-Step Resolution Protocols

Phase 1: Rapid Software & Cache Reset (Zero Data Loss)

Objective: Eliminate host-side stale caches, expired cookies, and DNS poisoning that may cause spurious 3194 on currently-signed builds.

  1. Quit Finder/iTunes completely: killall -9 Finder; killall -9 "iTunes Helper" 2>/dev/null
  2. Flush MobileDevice cache: rm -rf ~/Library/Caches/com.apple.MobileDevice ~/Library/Logs/MobileDevice
  3. Reset DNS cache: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  4. Verify /etc/hosts has no entries for gs.apple.com, albert.apple.com, tss.apple.com: grep -i apple /etc/hosts → must return empty.
  5. Restart usbd: sudo launchctl kickstart -k system/com.apple.usbd
  6. Reconnect device, enter Recovery Mode manually (Vol Up, Vol Down, Hold Side until Recovery glyph).
  7. Attempt restore in Finder. If build is currently signed (check ipsw.me), this resolves 90% of false-positive 3194 cases.

Phase 2: Terminal / Subsystem Pipeline Flush (Command-line Remediation)

Objective: Force a clean AMRestore pipeline with explicit IPSW and verbose logging for forensic analysis.

  1. Download target IPSW (signed build only) via ipsw CLI: brew install ipsw; ipsw download --device iPhone15,3 --version latest --beta
  2. Verify IPSW signature: ipsw verify --device iPhone15,3 --ipsw ~/Downloads/iPhone15,3_18.1.
Still stuck on Error 3194?

Share your exact OS build and Finder/Console snippet in the OS Updates & Error Codes forum room.

Get Peer Triage →