MacBook Air A2337 Not turning on, 0.00-0.05a current draw at 5V repair

Problem description
Facing an issue with the MacBook Pro A2337 displaying 5V and a very low current draw of 0.00 to 0.05A on the USB-C meter.

Symptoms

 * MacBook Pro A2337 stuck on 5V with a current draw of 0.00 to 0.05A on the USB-C meter.
 * Not turning on, all voltages missing.

Check for DFU or Recovery Mode

 * Connect the MacBook Pro A2337 to another Mac or MacBook via the master port (top left side USB-C port, closest to the display).
 * Use Apple Configurator 2 to verify whether the device is in DFU or recovery mode.
 * If the device is in DFU mode, proceed to "Device stuck in DFU mode due to corrupt firmware" in the repair steps below.

Check voltage on PPBUS_AON

 * Measure voltage on PPBUS_AON by placing your multimeter in DC mode, black probe on ground, and red probe on PPBUS_AON. A suitable measuring point on the 820-02016 logic board is C5960 (Figure 1). Normal voltage should be around 12.60-13.1V.
 * If the voltage is approximately 12.28-12.35V, it may indicate a communication issue between the SOC and PMICs, or corrupt firmware.
 * If the voltage is 0V, proceed to the repair steps for shorted or absent PPBUS_AON voltage.

Check PP3v8_AON_VDDMAIN voltage

 * PP3v8_AON voltage may vary depending on the device's sleep state.
 * To check voltage on PP3v8_AON, set your multimeter to DC mode, black probe on ground, and red probe on PP3v8_AON_VDDMAIN. Measuring points include C5887 or C5889 (Figure 2). Normal voltage should be around 3.8V.
 * If voltage is missing or low, proceed to the repair steps for PP3v8_AON_VDDMAIN low or missing.

Check CD3217 support voltages

 * Measure the following support voltages for CD3217 (Figure 4):

Note that voltage measurement should be performed WHILE the device is plugged in!
 * 1) - PP5v_S2: Normal voltage ≈ 5V measuring point: CC334 or CC335 (Figure 5).
 * 2) - PP3v3_S2_UPC: Normal voltage ≈ 3.3V measuring point: CF400 or CF500 (Figure 6).
 * 3) - PP1v25_S2: Normal voltage ≈ 1.25V measuring point: Pin 1 SWV011 (Figure 7).
 * If any of the S2 rails are missing, proceed to CD3217 support S2 rails low or missing repair steps below.
 * If all findings are negative, consider CD3217 or related circuit issues.

Device stuck in DFU mode due to corrupt firmware

 * Revive firmware via Apple Configurator 2.
 * Ensure the MacBook is running the latest macOS version for consistent results.
 * Follow the provided Apple support article for the procedure.
 * Once plugged in, open Apple Configurator 2. You should see a big square icon pop up that says "DFU" or rarely, "RECOVERY". Click the icon, Navigate to the top menu bar click "Actions" then "Advanced". Select Revive device. You will see a progress bar appear. This process can take over 30 minutes in some cases as Apple Configurator 2 now reinstalls the OS in addition to the M1's firmware. Data will still be retained with the revive option.
 * Be cautious that selecting "Restore" will wipe all user data.
 * Possible causes for a device to fail a DFU revive include various hardware issues listed above.

PPBUS_AON shorted, low or absent
How to find short circuits
 * If shorted
 * Inject around 1V with a 5A limit into PPBUS_AON using a DC power supply.
 * Perform thermal imaging of the board or apply isopropyl alcohol to locate the shorted component.
 * Replace the identified shorted component.
 * If not shorted
 * PPBUS_AON is created by the Intersil/Renesas ISL9240 (U5200) which is a buck or boost converter depending on its input voltage. If USB-C voltage is 5 V, the ISL9240 will boost the 5 V input to ≈12 V. If USB-C voltage is 20 V, the ISL9240 will buck (lower) the 20 V input to ≈12 V.
 * When PPBUS_AON is absent with no short to ground, we need to first make sure that PPDCIN_AON_GHGR_R is making it to the ISL9240 (U5200). C5201 or C5202 is a good place to measure from. Measure PPDCIN_AON_CHGR_R with your multimeter in voltage mode. You should get the same voltage that you are getting on the USB-C amp meter (5 V in this case, because that is what we are troubleshooting.) If you get 0v on PPDCIN_AON_CHGR_R, check R5220, however it must be noted that if you have 0v here, one of the CD3217s is probably bad. See "CD3217 Diagnostic Steps" above.
 * If you are getting 5V on PPDCIN_AON_CHGR, the ISL9240 is likely the cause of the problem, however we still need to check a few things before replacing the chip.
 * The ISL9240 relies on a series of current sensing resistors to measure the amount of power being used by its output rail, PPBUS_AON. If one of these resistors is blown, the chip will think that something on the output is pulling too much power, and it will disable itself as a protection measure.
 * To check the current sensing resistors, put your multimeter on resistance mode. Check each resistor listed below by placing your probes on each side of the resistors. The values should be within 5–10% of the reference listed below. Values slightly outside of the reference should be considered insignificant and ignored. If you find a resistor out of spec, replace the resistor AND the ISL9240, as the resistor likely blew as a result of the ISL9240 internally shorting. R5221, R5222, R5261, R5262 = 1.00 Ω
 * If the current sensing values are normal, replace the ISL9240.

PP3v8_AON_VDDMAIN low or missing

 * Check for a short to ground on PP3v8_AON_VDDMAIN (normal diode mode to ground reading ≈ 0.350).
 * If a short to ground is found, replace the shorted component.
 * Check the enable signal to U5700 (Figure 8), P3V8_PWR_EN, and address any issues with U5340 (Figure 9) or surrounding components.
 * P3V8_PWR_EN is sourced from CHGR_EN_MVR from the ISL9240 (U5200) and passes through a delay switch (U5340) where it is outputted as P3V8_PWR_EN.
 * If P3V8_PWR_EN is missing, check voltage on R5340 (CHGR_EN_MVR). If CHGR_EN_MVR is missing, replace U5200.
 * If CHGR_EN_MVR is present, but P3V8_PWR_EN is missing, potential faults could include U5340, or surrounding traces/resistors.
 * Ensure VIN (PPBUS_AON) is making it to U5700; Occasionally a via or trace can break resulting in a voltage not making it to some parts of the board. PPBUS_AON can be measured adjacent to U5700, on C5704 or C5804.
 * If the above findings are negative, replace U5700

CD3217 support S2 rails low or missing

 * Check for shorts to ground or enable issues on the affected S2 rails.
 * PP5v_S2 - Produced from UC300.
 * Check the enable signal for PP5v_S2, P5VS2_EN.
 * P5VS2_EN is produced by the PMU, U8100.
 * A missing enable signal can mean U8100 is bad, or there is a communication issue with U8100 and the SOC/other components. A firmware issue can also *likely* cause missing enable signals from PMICs on the M1 machines. As of 10/17/2022, this remains rare.
 * Check the VIN voltage to UC300, PPBUS_5VS2_VIN.
 * The VIN voltage listed above is sourced from PPBUS_AON and voltage measured on it should remain consistent with PPBUS_AON voltage. If voltage is low, possible causes could include a broken trace or RD550 blown or otherwise out of spec.
 * PP3v3_S2_UPC - LDO produced from U8100.
 * The incidence is unknown for PP3v3_S2_UPC missing without a short or voltage leakage to ground, however possible differential diagnoses can include corrupt firmware, where a DFU revive may resolve the issue or a failed PMIC (U8100), or an issue with the SOC. This section will be updated when more M1 powered boards present with similar issues. As of 10/17/2022, issues with PMIC voltages remain rare.
 * PP1v25_S2 - Produced from U7700, BUCK 13 LDO.
 * The incidence is unknown for PP1v25_S2 missing without a short or voltage leakage to ground, however possible differential diagnoses can include corrupt firmware, where a DFU revive may resolve the issue or a failed PMIC (U7700), or an issue with the SOC.

CD3217 Diagnostic Process

 * There is no definitive diagnostic test for a faulty CD3217 (Figure 4) other than replacing it.
 * You can determine which CD3217 is in use by measuring voltage on the input fuse that correlates with the chip. FF201 correlates with UF500 FF200 correlates with UF400.
 * Test 1: Measure PPDCIN_AON_CHGR_R on both ports to identify an internal MOSFET issue in one CD3217 (Figure 4).
 * Test 2: Measure the LDO outputs of both CD3217s to check if one is not outputting proper voltage; replace the corresponding CD3217 if found.
 * PP3v3_UPC0_LDO - Supplied from UF400 and powers the TBT ROM (UF260). Normal voltage = ~3.3v. Normal diode mode to ground reading = ~.500.
 * PP1v5_UPC0_LDO_CORE - Supplied from UF400 and powers internal CD3217 functions. Normal voltage = ~1.5v. Normal diode mode to ground reading = ~.510
 * PP3v3_UPC1_LDO - Supplied from UF500 and powers internal CD3217 functions. Normal voltage = ~3.3v. Normal diode mode to ground reading =~.500.
 * PP1v5_UPC1_LDO_CORE - Supplied from UF500 and powers internal CD3217 functions. Normal voltage = ~1.5v. Normal diode mode to ground reading = ~.510.
 * If you find that any of the LDO voltages are low, check for a short to ground on the correlating line. If no short to ground is found, replace the CD3217 that the line correlates with.