MacBook Pro A2289 Not turning on, 0.01A current draw at 5V repair and MacBook Pro A2289 Not turning on, drawing 0.03-0.06A at 20V repair: Difference between pages

From Repair Wiki
(Difference between pages)
No edit summary
 
No edit summary
 
Line 8: Line 8:
{{stub}}
{{stub}}
==Problem description==
==Problem description==
The most likely cause for a 820-01987 to be stuck on 5 V and low current draw (~0.00–0.02 A) on the USB-C current meter is a short to ground on PPBUS_G3H. However, if all ports are not reading the same, then it may be indicative of a CD3217 issue.[[File:Placeholder image.jpg|thumb|Example image (Figure 1) -- No image yet. Help expand this page by uploading it!]]
No Power, 20v and ~0.03-0.06A current draw on the 820-01987 logic board diagnosis and repair.
[[File:Placeholder image.jpg|thumb|Example image (Figure 1) -- No image yet. Help expand this page by uploading it!]]
==Symptoms==
==Symptoms==
*MacBook not turning on or charging
 
*All voltages are missing
*MacBook not turning on
*only drawing 0.01-0.02A at 5V from the USB-C current meter
*Pulling ~0.03-0.06A current at 20v from USB-C as measured by USBC meter


==Solution==
==Solution==
Line 23: Line 24:
* If the device is in DFU mode, proceed to "Device stuck in DFU mode due to corrupt firmware" in the repair steps below.
* 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_G3H ====
==== Check for a short to ground on PP3v3_S5 ====
 
If a short to ground is found, proceed to the "PP3v3_S5 short to ground" repair steps below.
* To accurately measure voltage on PPBUS_G3H, set your multimeter to DC voltage mode and place the black probe to ground and the red probe on PPBUS_G3H.
* For the 820-01987, the ideal measurement point is F7000.
** ~12.60–12.65 V = Normal
** ~12.28–12.35 V = T2 communication issue with the ISL9240. The likely cause for this is the device is stuck in DFU mode due to corrupt T2 firmware or a failed CD3217. Proceed to repair steps below for corrupt T2 firmware.
** ~0 V = Short to ground or absent voltage due to a creation problem. Proceed to repair steps below for shorted or absent PPBUS_G3H voltage.
 
==== Check PP3v3_G3H_RTC voltage ====


* Ensure your multimeter is in DC voltage mode. Place the black probe on ground and the red probe on PP3v3_G3H_RTC.
==== Check resistance to ground on PP2v5_NAND_SSD_0 ====
* It is recommended to measure PP3v3_G3H_RTC on a capacitor or resistor near one of the CD3217s to rule out a trace/via issue.
Normal values can be as high as >1MΩ or as low as 60Ω. In the case of SSD/NAND failure, resistance will usually be between 1-.
** C3200 is a good place to measure this line on the 820-01987 logic board.
** ~3.3 V (3.290–3.425 V) = Normal.
** ~0 V = Short to ground or absent voltage due to a creation problem. Proceed to repair steps below for shorted or absent PP3v3_G3H_RTC voltage.


==== Check PP3v3_G3H_PMU_VDDMAIN voltage ====
==== Inspect U9000 for corrosion. ====
The location of the chip on this board makes it prone to corrosion, either from liquid ingress or from condensation from dust collection.


* The PP3v3_G3H_RTC voltage powers the "brain" of the CD3217 USB-C controllers, enabling communication with the USB-C charger to allow for 20 V.
U9000 can be reballed if corroded which will likely resolve the issue if it is corroded.
* Ensure your multimeter is in DC voltage mode. Place the black probe on ground and the red probe on PP3v3_G3H_PMU_VDDMAIN.
* It is recommended to measure PP3v3_G3H__PMU_VDDMAIN on a capacitor near U7800 to rule out a trace/via issue.
** C7891/C7807 is a good place to measure this line on the 820-01987 logic board.
** ~3.3 V (3.290–3.425 V) = Normal.
** Values below the above spec should be considered abnormal. Proceed "PP3v3_G3H_PMU_VDDMAIN low or absent" in the repair steps below.


===Repair Steps===
===Repair Steps===
Line 60: Line 47:
** Select Revive device. You will see a progress bar appear. This process can take over 30 minutes in some cases.
** Select Revive device. You will see a progress bar appear. This process can take over 30 minutes in some cases.
** Be cautious that selecting "Restore" will wipe all user data.
** Be cautious that selecting "Restore" will wipe all user data.
* Possible causes for a device to fail a DFU revive include various hardware issues.
* Possible causes for a device to fail a DFU revive include various hardware issues:
** Short to ground on PP2v5_NAND_SSD_0).
** Absent U9000 voltages. (PP0v9_SSD_0, PPVCCQ_ANI_SSD0 (1.8v).
** Failed Trackpad (Will almost always show the Apple logo before failing the process.)
** Failed NAND.
** Failed T2 or T2 RAM.
** If no secondary causes are found, a DFU Restore may resolve the issue.


==== PPBUS_G3H Short to ground ====
==== '''PP3v3_S5 shorted to ground''' ====
[[How to find short circuits]]


* Inject around 1 V with a 5 amp limit into PPBUS_G3H with a DC power supply.
* Locate and replace the shorted component. [[How to find short circuits]]
** A larger tantalum capacitor or the main PPBUS fuse (F7000) is preferred to inject voltage to, as you will often need a lot of current to be pushed into the line to cause the shorted component to heat up.
** PP3v3_S5 is a tricky line to inject voltage to on this board, as most components are small 0201 parts.  
** It is not recommended to inject over 1 V as if one of the CPU VRMs is shorted, you will end up killing the CPU.
** Be sure to use a small gauge wire to inject voltage if you choose to inject voltage to a 0201 part. The best place to inject voltage to on this board is pin 5 of U4801.
** A good place to inject voltage to on the 820-01987 is F7000.
** 1v at 5 amps is an appropriate voltage to inject into the line. Remove the heatsink prior to injecting voltage as occasionally, the CPU will be the cause of the short to ground. With voltage being injected, perform thermal imaging of the board. If thermal imaging is not available, feel around the board to see where it is getting warm. Once the area is localized, add a small amount of isopropyl alcohol to the area to localize the shorted component.
** With voltage being injected, perform thermal imaging of the board.
** If thermal imaging is not available, feel around the board to see where it is getting warm. Once the area is localized, add a small amount of isopropyl alcohol to the area to localize the shorted component.
** Once the shorted component is localized, replace the shorted component.
** Once the shorted component is localized, replace the shorted component.
* ''Most commonly, you will find one of the capacitors near the speaker connectors to be shorted to ground. (Typically C6405, C6456 , C6555 or C6556.) If this is the case, remove the capacitor. It does not have to be replaced.''


==== PPBUS_G3H Absent or low with no short ====
==== U9000 visibly corroded or damaged ====
 
* If corroded, reball the IC. Replacement is usually not necessary.
* If physically damaged or burned, replace the IC. The IC is not programmed and can be taken from any board which utilizes the same part. (338S00410)


*
==== '''If no short is found on PP3v3_S5, and the device is not in DFU or recovery mode, and all other findings are negative, you can try forcing a firmware revive''' ====
* If PPBUS_G3H is absent, first check that PPDCIN_G3H is making it to the Intersil/Renesas ISL9240 (U7000).
** Measure PPDCIN_G3H with a multimeter in voltage mode at C7024, C7029, C7028, or C7026 on 820-01987.
** The voltage should match that of the USB-C amp meter (5 V).
** If 0V is read, check for a short, and if none is found, It is most likely a CD3217.
** If 5 V is read, check the current sensing resistors (listed below) as the ISL9240 may have shorted internally causing the current sensing resistors to blow.
*** Place the multimeter probes on each side of the resistors to measure the resistance, which should be within 5–10% of the reference.
*** If a resistor is found out of spec, replace it and the ISL9240, as the resistor likely blew due to an internal short.
*** Depending on the input voltage, the ISL9240 either buck or boosts the voltage to ~12 V; if USB-C voltage is 5 V, it boosts it
*** R7021, R7022, R7061, R7062 = 1.00 Ω
*** If the current sensing values are normal, replace the ISL9240 (U7000)


==== PP3v3_G3H_RTC low or absent ====
* Attempt to restore BridgeOs firmware via Apple Configurator 2 by placing the device into DFU mode.
** Solder a wire across SE032 (Omitted/No Stuff) to pull SOC_FORCE_DFU high. Wire should be across pins 3 and 4 or 1 and 2.
* STOP! Before you begin, is your Mac on the LATEST VERSION of MacOs? If not, update your system before proceeding. Forcing a MacBook into DFU mode, and attempting to restore BridgeOs firmware on a old version of MacOs may result in a bricked device. NOTE: Selecting restore will wipe all user data.
* Follow the instructions on this [https://support.apple.com/guide/apple-configurator-mac/revive-or-restore-an-intel-based-mac-apdebea5be51/mac Apple support article] on how to revive or restore T2/BridgeOs firmware, including on how to force a Intel based MacBook into DFU mode by using a key combination.


* On the 820-01987, the buck converter U6903 is responsible for lowering the voltage from PPBUS_G3H (approximately 12 V) to 3.3 V to generate PP3v3_G3H_RTC.
If the device fails the firmware revive or restore, the T2 chip or one of the NANDs is likely dead or is receiving unstable power from the PMIC (U7800) causing it to crash. If the device fails the firmware revive, you can try empirically replacing U7800. You must removal the large shield covering U7800 and the T2 chip prior, which is not easy. You must use low melt alloy to remove the shield. Be careful not to bridge surrounding components. Go slow and be patient.
* The most common reason for PP3v3_G3H_RTC to be missing or low, is a short to ground, usually on a capacitor around one of the CD3217s, or from a CD3217 itself.
** PP3v3_G3H_RTC may falsely read as short, measuring around 100 ohms. This should be considered a false positive. To confirm, remeasure the PP3v3_G3H_RTC after the board has been removed from power for a few minutes.
* If PP3v3_G3H_RTC is not shorted, confirm that the enable signal GHGR_EN_MVR is present, which is generated by the ISL9240 (U7000).
** The ISL9240 often fails in such a way that prevents GHGR_EN_MVR from being produced. If the enable signal is missing, replacing the ISL9240 (U7000) is recommended.
* PP3v3_G3H_RTC can also be pulled low by PP3v3_UPC_XB_LDO or PP3v3_UPC_XA_LDO, so if you have no measurable short to ground, and your enable/VIN is present, check both the above rails for a short or low resistance to ground.
** Low resistance to ground/short on the above LDO lines will usually be caused by a bad CD3217.
* Occasionally, U6903 may PPBUS_G3H to ground and may blow it's VIN current limiting resistor U6900. Be sure to check voltage on both sides of U6900 if you suspect your VIN may be missing to U6903.


'''If you found and resolved a short circuit, and still have low voltage on PP3v3_G3H_RTC, check voltage on both sides of R6934/35. These resistors can blow in response to a short circuit.'''
'''Replacing U7800 should be seen as a last ditch effort, as it only works in a small amount of cases, and does not have a definitive diagnostic test to determine if it is bad.'''

Revision as of 15:28, 29 October 2023

MacBook Pro A2289 Not turning on, drawing 0.03-0.06A at 20V repair
Device MacBook Pro A2289
Affects part(s) Motherboard
Needs equipment multimeter, soldering iron, soldering station
Difficulty ◉◉◉◌ Hard
Type Soldering


This article is a stub. You can help Repair Wiki grow by expanding it

Problem description

No Power, 20v and ~0.03-0.06A current draw on the 820-01987 logic board diagnosis and repair.

Example image (Figure 1) -- No image yet. Help expand this page by uploading it!

Symptoms

  • MacBook not turning on
  • Pulling ~0.03-0.06A current at 20v from USB-C as measured by USBC meter

Solution

Diagnostic Steps

Check for DFU or Recovery Mode

  • Connect the MacBook Pro A2289 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 for a short to ground on PP3v3_S5

If a short to ground is found, proceed to the "PP3v3_S5 short to ground" repair steps below.

Check resistance to ground on PP2v5_NAND_SSD_0

Normal values can be as high as >1MΩ or as low as 60Ω. In the case of SSD/NAND failure, resistance will usually be between 1-3Ω.

Inspect U9000 for corrosion.

The location of the chip on this board makes it prone to corrosion, either from liquid ingress or from condensation from dust collection.

U9000 can be reballed if corroded which will likely resolve the issue if it is corroded.

Repair Steps

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. Check for MacOS updates prior to reviving/restoring T2 firmware.
  • Follow the provided Apple support article for the procedure.
    • Plug the device you are working on to another Mac or MacBook via its master port. The master port on the A2289 is the bottom left side USB-C port (closest to the trackpad).
    • 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.
    • Be cautious that selecting "Restore" will wipe all user data.
  • Possible causes for a device to fail a DFU revive include various hardware issues:
    • Short to ground on PP2v5_NAND_SSD_0).
    • Absent U9000 voltages. (PP0v9_SSD_0, PPVCCQ_ANI_SSD0 (1.8v).
    • Failed Trackpad (Will almost always show the Apple logo before failing the process.)
    • Failed NAND.
    • Failed T2 or T2 RAM.
    • If no secondary causes are found, a DFU Restore may resolve the issue.

PP3v3_S5 shorted to ground

  • Locate and replace the shorted component. How to find short circuits
    • PP3v3_S5 is a tricky line to inject voltage to on this board, as most components are small 0201 parts.
    • Be sure to use a small gauge wire to inject voltage if you choose to inject voltage to a 0201 part. The best place to inject voltage to on this board is pin 5 of U4801.
    • 1v at 5 amps is an appropriate voltage to inject into the line. Remove the heatsink prior to injecting voltage as occasionally, the CPU will be the cause of the short to ground. With voltage being injected, perform thermal imaging of the board. If thermal imaging is not available, feel around the board to see where it is getting warm. Once the area is localized, add a small amount of isopropyl alcohol to the area to localize the shorted component.
    • Once the shorted component is localized, replace the shorted component.

U9000 visibly corroded or damaged

  • If corroded, reball the IC. Replacement is usually not necessary.
  • If physically damaged or burned, replace the IC. The IC is not programmed and can be taken from any board which utilizes the same part. (338S00410)

If no short is found on PP3v3_S5, and the device is not in DFU or recovery mode, and all other findings are negative, you can try forcing a firmware revive

  • Attempt to restore BridgeOs firmware via Apple Configurator 2 by placing the device into DFU mode.
    • Solder a wire across SE032 (Omitted/No Stuff) to pull SOC_FORCE_DFU high. Wire should be across pins 3 and 4 or 1 and 2.
  • STOP! Before you begin, is your Mac on the LATEST VERSION of MacOs? If not, update your system before proceeding. Forcing a MacBook into DFU mode, and attempting to restore BridgeOs firmware on a old version of MacOs may result in a bricked device. NOTE: Selecting restore will wipe all user data.
  • Follow the instructions on this Apple support article on how to revive or restore T2/BridgeOs firmware, including on how to force a Intel based MacBook into DFU mode by using a key combination.

If the device fails the firmware revive or restore, the T2 chip or one of the NANDs is likely dead or is receiving unstable power from the PMIC (U7800) causing it to crash. If the device fails the firmware revive, you can try empirically replacing U7800. You must removal the large shield covering U7800 and the T2 chip prior, which is not easy. You must use low melt alloy to remove the shield. Be careful not to bridge surrounding components. Go slow and be patient.

Replacing U7800 should be seen as a last ditch effort, as it only works in a small amount of cases, and does not have a definitive diagnostic test to determine if it is bad.