Start with antenna path
If Wi‑Fi and Bluetooth work only very near the AP/device, inspect coax, grounding springs, housing contacts, antenna feed and matching components before combo-IC work.
IPHONE WI‑FI / BLUETOOTH / NFC FORENSICS
Power the radio.
Power the radio.
Then prove the link.
Separate combo-IC power, reference clocks, PCIe/UART transport, RF front-end, coexistence, antenna paths and NFC/Secure Element before reballing a module or bypassing RF components.
CONNECTIVITY EVIDENCE CHAIN
POWER
CLOCK
BUS
RF
COEX
NFC
Greyed Wi‑Fi, weak range, AirDrop failure and Apple Pay faults belong to different branches. The correct repair follows the first stage that cannot be confirmed.
01 — CONNECTIVITY POWER & DATA HIGHWAY
Trace seven stages from supply to radio function
Select the domain first because Wi‑Fi, Bluetooth, NFC and antenna faults can share only part of the chain.
02 — SYMPTOM-TO-PROOF ENGINE
Greyed Wi‑Fi, weak range, AirDrop, NFC and standby drain
Each case keeps power, transport, RF and software/state branches open until confirmed.
SELECTED FAILURE
Observed evidence
Competing domains
Proof required
03 — RF / ANTENNA / COEXISTENCE
Weak range is not the same problem as a dead radio
Use range behavior, RSSI, antenna continuity, coax seating and coexistence symptoms to separate RF front-end from digital control faults.
Wi‑Fi activity disturbs Bluetooth
If Bluetooth audio stutters mainly during heavy 2.4 GHz Wi‑Fi traffic, check coexistence/control paths and shared RF behavior—not just the BT UART bus.
One band can fail independently
A phone can have normal 2.4 GHz service with weak or absent 5/6 GHz due to band-specific antenna/front-end/filter paths. Record band and RSSI rather than saying “Wi‑Fi weak.”
13.56 MHz loop is a separate RF path
Wallet UI working does not prove RF field generation. Check antenna loop continuity, controller power, SWP/security state and reader interaction separately.
04 — CONNECTIVITY REFERENCE DATABASE
Voltage + GR + resistance + protocol
Values are preserved as uploaded-source references and should be compared against exact-model known-good measurements.
| Subsystem | Rail / Signal | Source Voltage | Source GR | Resistance | Protocol / State | What abnormal supports |
|---|
05 — LIVE CONNECTIVITY-LINE EVALUATOR
One reading narrows the domain
A passing line reading does not prove high-speed PCIe, RF performance or Secure Element operation.
06 — SOURCE RULES CORRECTED
Do not jump from symptom to combo-IC rework
V2 removes several one-to-one conclusions from the uploaded V1.
Not automatically Wi‑Fi BGA
An open can be trace, filter, connector, pad or IC-side. Locate the discontinuity before reball or replacement.
No automatic RF bridge
Inspect coax, antenna contacts, housing grounds and matching network. Do not bridge RF filters without knowing the topology and failed element.
Not automatically NFC controller
Separate antenna loop, controller power, SWP/security state, replacement history and reader interaction.
Not automatically a leaky capacitor
Compare with module/state disconnected where possible and exact-model known-good before identifying a capacitor or combo IC.
Do not inject 3.3V by default
Confirm the rail, its normal maximum voltage and a genuine short/leak before any current-limited injection. Start below nominal and raise only as needed.
Not proof of RF or PCIe health
Static GR/voltage cannot prove active high-speed transport, RF output power, sensitivity or coexistence timing.
07 — CONNECTIVITY CASE DOSSIER
Record band, range, bus and security evidence
Preserve Wi‑Fi address state, Bluetooth behavior, RSSI/range, NFC response and electrical measurements.