Skip to main content

M1 Pro Liquid Damage — PMU Control Lines & Corrupted Boot

M1 Pro Liquid Damage — PMU Control Lines & Corrupted Boot

Status: repaired successfully · Channel: LapFix · Published: 2025-08-12 · Runtime: 16:50 Model: MacBook Pro 14" M1 Pro (A2442) · Board: 820-02098 Source: YouTube Fault class: Liquid damage + corrupted boot image (requires DFU revive)

Summary

The board connected at 20 V but cycled every ~6 s between 0.08 A and 0.01 A. Corrosion on the underside bridging PMU enable signals and the SPI lines to the storage controller was pulling a rail-enable line low, interrupting an active write and leaving the OS unbootable. Cleaning and reflowing the control passives stabilised the rails; the SoC then booted only after a non-destructive DFU revive via Apple Configurator.

Timeline

Time Evidence Observation
02:10 [measured] Connects at 20.0 V, draws 0.08 A, drops to 0.01 A, cycles indefinitely every ~6 s.
05:30 [measured] Corrosion on the board underside across PMU enable signals and SPI lines to the storage controller.
08:20 [stated] Technician: liquid bridging the PMU enable line caused partial corruption in the Secure Enclave / NVRAM partition during a forced restart.
11:45 [measured] Ultrasonic cleaning + solder reflow on the oxidised PMU control passives; cycling stops; steady 20 V / 0.12 A in DFU.
14:30 [measured] Apple Configurator Revive Device succeeds; macOS boots to the UI.

Measurements

Time Measurement Value Context
02:10 Voltage / current 20.0 V / 0.01–0.08 A Cycling interval ~6 s
12:00 Voltage / current 20.0 V / 0.12 A steady Stable DFU state
15:10 Voltage / current 20.1 V / 1.65 A Operational, booted

Diagnostic reasoning

  • Observation — board cycles at 20 V with very low current (0.01–0.08 A).
  • Stated mechanism — corrosion pulled down a PMU rail-enable line, interrupting an active write cycle and leaving the OS unbootable.
  • Demonstration — cleaning and reflowing the passives stabilised the rails, but the SoC remained in DFU until a Configurator revive cleared the corrupted boot image. Hardware repair alone was not sufficient.

Repair procedure

  1. Clean localised liquid damage with flux and targeted ultrasonic solvent.
  2. Reflow corroded passives around the PMU peripheral lines.
  3. Connect the board in DFU mode to a host Mac via the designated DFU USB-C port.
  4. Run the non-destructive Revive in Apple Configurator.
  5. Reassemble and verify stability.

Claims audit

ID Claim Evidence Note
C1 Liquid-induced power drops during sleep/wake can corrupt Apple Silicon boot partitions, needing both hardware repair and a firmware revive. [inferred] Demonstrated on this unit; the specific partition implicated was not shown.
C2 The corruption affected the Secure Enclave / NVRAM partition. [unverified] Secure Enclave contents are not user-writable in this way — treat the "SE corruption" wording with caution; the observable fact is simply that a revive was required.
  • [[dfu-inductor]] — when a hardware rail dropout makes the revive itself fail.
  • [[m1-las-backlight]] — same board, different liquid-affected subsystem.

Provenance: condensed from the video's audio transcript (Google AI Studio); timestamps, refdes and values are as stated in the video and are not independently verified.