Not automatically Hydra/Kraken
Locate the open through connector, protection/filter/series components, trace and IC-side before replacing the controller.
IPHONE USB / LIGHTNING / TYPE‑C DATA FORENSICS
Detect the cable.
Detect the cable.
Then prove the transport path.
Separate connector seating, accessory/orientation detection, USB 2.0 data, SuperSpeed lanes, controller power, mux/retimer paths and host enumeration before replacing a dock assembly or USB controller.
USB DATA & ACCESSORY EVIDENCE CHAIN
PORT
DETECT
AUTH
USB2
USB3
HOST
Charging current and USB data are different subsystems. A phone can charge normally while D+/D−, CC, SuperSpeed or host-enumeration paths fail.
01 — USB DATA & ACCESSORY HIGHWAY
Trace seven stages from connector to host enumeration
Select the interface first because Lightning and USB‑C use different orientation, accessory and high-speed paths.
02 — SYMPTOM-TO-PROOF ENGINE
No computer, no data, one-sided Type‑C, accessory and restore dropouts
Each case keeps cable, connector, protection, mux/controller and host-side causes open until confirmed.
SELECTED FAILURE
Observed evidence
Competing domains
Proof required
03 — LIGHTNING VS USB‑C TRANSPORT
Different connector, different failure map
Do not mix Type‑C CC/PD failures with Lightning accessory-detect faults.
| Interface | Detection / Orientation | USB 2.0 Data | High-Speed Path | Accessory / Role State | Typical Isolation |
|---|---|---|---|---|---|
| Lightning | Accessory/orientation logic via Lightning controller path | D+/D− USB 2.0 | No USB3 on Lightning iPhones | Accessory identification / MFi-related path | Cable → port → ACC/data lines → controller power → host enum |
| USB‑C USB2 | CC1 / CC2 orientation + role detection | D+/D− | USB2 only on affected models | CC/PD role/attach state | Flip test → CC1/CC2 → D+/D− → controller / PHY |
| USB‑C SuperSpeed | CC1 / CC2 + lane orientation | D+/D− fallback | TX/RX differential SuperSpeed lanes | CC/PD + mux/retimer state | USB2 works? → flip test → SS lanes → mux/retimer → host |
| DFU / Recovery | Depends on underlying connector path | Critical for restore transport | May fall back depending on model/host | Host driver + cable + port stability matters | Known-good cable/host port first, then device transport path |
04 — USB / ACCESSORY REFERENCE DATABASE
Voltage + GR + resistance + protocol
Values are preserved as uploaded-source references; exact-model known-good measurements take priority.
| Interface | Rail / Signal | Source Voltage | Source GR | Resistance | Signal / Protocol | What abnormal supports |
|---|
05 — LIVE USB-LINE EVALUATOR
Combine static reading with actual host behavior
A passing line reading does not prove enumeration, eye quality, retimer behavior or long-duration restore stability.
06 — SOURCE RULES CORRECTED
Do not let one USB symptom force controller replacement
V2 deliberately removes several one-to-one conclusions from the uploaded V1.
Not automatically Tristar/ESD leakage
Compare exact-model known-good and isolate the connected load before identifying the leaky part.
Not automatically dock flex
Separate CC orientation detection from D+/D− and SuperSpeed lane/mux faults.
Not automatically controller
Known-good accessory/cable, connector contamination, accessory lines and controller power must be checked first.
Not automatically USB hardware
Host port, cable, restore stage, NAND/storage, power stability and USB transport can all produce restore interruption.
Does not prove high-speed integrity
USB2/USB3 eye quality, retimer/mux timing and intermittent connector faults can survive normal GR/voltage checks.
07 — USB DATA / ACCESSORY CASE DOSSIER
Record connector, orientation, host and transport evidence
Preserve cable/host tests, flip behavior, USB mode, GR/voltage and restore-stage observations.