Repair Cases Index
Repair Cases Index — Apple Silicon (M1–M4)
Consolidated index of component-level repair cases on Apple Silicon MacBook logic
boards, drawn from published independent-repair videos. Cases are limited to
non-trivial failure modes — Power Delivery controller handshakes, battery
management buses, liquid-induced track and flex damage, solder-joint fatigue,
sensor lockouts, and sub-rail regulation faults. Simple "shorted MLCC on
PPBUS_AON" cases are deliberately out of scope.
How to read these pages
Every technical statement carries an evidence label:
| Label |
Meaning |
[measured] |
An instrument reading shown on camera (meter, oscilloscope, thermal). |
[stated] |
A claim made by the technician in narration, not independently shown. |
[inferred] |
Reasoning drawn from the observations, not directly demonstrated. |
[unverified] |
Asserted but not substantiated, or contradicted by known engineering practice. |
Provenance. These pages were condensed from the audio transcripts of the
source videos (extracted with Google AI Studio) and from on-screen meter
readings described in those transcripts. Timestamps, reference designators,
board numbers and measured values are reproduced as stated in the video and
have not been independently verified against schematics or a physical
board. Treat every refdes and rail name as a lead to confirm on the actual
board revision, not as a fact.
Cases by fault class
USB-C Power Delivery controllers (CD3217 / CD3218)
Battery management bus (SMBus / I2C)
Liquid damage and high-voltage flex
Display, sensors and power rails
Recurring thresholds seen across cases
Standing cautions
- Chip-off data recovery is not viable. NAND contents on M1–M4 are encrypted
with keys fused into the Secure Enclave inside the SoC; reading the NAND
elsewhere yields undecryptable ciphertext. Repairing the original board to a
bootable state is the only data-recovery path — a point every surveyed channel
agrees on.
- "Revive" preserves user data; "Restore" wipes keys. Revive failures are
frequently hardware power dropouts, not software corruption.