500mA-like current is not unique
Check charger type, cable, host/PD state, battery SOC/temperature, software limits and negotiation evidence before USB-controller repair.
IPHONE CHARGING / USB / POWER DELIVERYDetect first.
Detect first.
Charge second.
Separate cable/port detection, USB handshake, VBUS power path, charger conversion, battery communication and thermal gating before replacing charging ICs.
CHARGING EVIDENCE CHAIN
PORT
DETECT
HANDSHAKE
POWER PATH
BMS
CHARGE
A charging icon proves detection, not necessarily battery current delivery.
01 — LIGHTNING VS USB-C
Two generations, different negotiation paths
The reference material keeps separate Lightning and USB‑C topologies. AIFlasher preserves that separation.
02 — CHARGING FAILURE PROFILER
Symptom → detection state → power state → proof
Current values are treated as observations. Each route requires confirmation of the failed stage.
SELECTED CASE
0.000A / no VBUS response
Observed evidence
Confirmation tests
Likely domain
03 — MASTER CHARGING DATABASE
Voltage + GR + resistance + signal state
Reference reference values are preserved as page references, not universal factory specifications.
| Generation | Rail / Signal | Voltage | GR / Diode | Resistance | Signal | What abnormal supports |
|---|
04 — LIVE CHARGING LINE EVALUATOR
One reading should narrow the branch, not name the IC
Use measured GR and live voltage together with the physical symptom and orientation/PD state.
05 — BENCH TRAPS CORRECTED
Do not turn one pattern into one component
AIFlasher keeps the reference material patterns but removes one-to-one conclusions.
Icon without battery gain has several branches
Measure input, system rail, battery current, BMS/thermal state and switching activity before charger-IC replacement.
Compare exact-model known-good
Orientation-specific failure supports a CC/port/mux branch, but diode values depend on board and measurement setup.
Read panic-full first
Use the exact missing-sensor string and model mapping before changing battery, dock or thermal components.