(347) 552-2258 [email protected]

820-02020 - PPBUS_AON low

HeyWatchOutDude

HeyWatchOutDude

Member
Hi,

after a CD3217 replacement the MacBook Pro M1 (A2338 / 820-02020) no longer boots into the OS and it shows the "restore" screen.

I have noticed that PPBUS_AON is 11.98V instead of 12.3V, any idea where I should start?

Note:
- Device restore via AC2 doesnt work ... Error 4014.
- PP5V_S2 = 5.2V
- PP3V8_AON = 3.8V

-- U8100 area:
- PPVDD_SOC_1 = 0.7V
- PPVDD_CPU_SRM_AWAKE = 0.9V
- PPVDD_EPCU_AWAKE = 0.8V
- PPVDD_PCPU_AWAKE = 0.5V
- PPVDD_GPU_AWAKE = 7.2mV
- PPVDD_DISP_S1 = 0.7V
- PPVDD_DCS_S1 = 0.7V
- PP1V4_LDO_PREREG =1.3V
- PP1V8_S2 = 1.8V
- PP1V2_S2 =1.2V
- PP3V3_S2_UPC = 3.3V

-- U7700 area:
- PP1V25_S2 = 1.25V
- PP0V88_S1 = 0.8V
- PP2V5_AWAKE_NAND = 2.5V
- PP5V_BSTLY_VOUT_SPMU = 5V

- USB-C output: 19.8V / 0.01A

Seems like there is no power rail missing ...

Before replacing the CD3217 everything worked fine except transfer speed on USBC0 which was limited to USB2.0 speed.
 
Last edited:
2informaticos

2informaticos

Administrator
Staff member
So you've replaced only one CD3217 chip?
Did you check first USB 2.0 lines in diode mode?
Put back original chip and see if machine boots at least.

You may have bad (new) chip, or incorrect replacement.
 
HeyWatchOutDude

HeyWatchOutDude

Member
I have replaced both CDs. (Took them from an A2337 donor board with correct order)

Any idea what else can cause the low PPBUS_AON?

Are the CDs paired to the logic board?

No, which lines should I check? (Hint needed)
 
Last edited:
2informaticos

2informaticos

Administrator
Staff member
You get 11.98V without battery connected?

USBCx_D2R/R2D are USB 3 lines.
USB_TOP/BOT correspond to USB 2.
 
2informaticos

2informaticos

Administrator
Staff member
If you only changed CD3217 chips, I don't see anything else to affect PPBUS_AON voltage.
If still bad with previous chips, then something more happended on the board.
 
HeyWatchOutDude

HeyWatchOutDude

Member
Yeah changed only CD3217 chips. (Also put back the original chips)

Is 11.98V normal on PPBUS_AON (without battery?)
 

Attachments

  • image.jpg
    image.jpg
    851.7 KB · Views: 2
2informaticos

2informaticos

Administrator
Staff member
Not normal, but machine works now?
Check if battery is charging.

BTW, did you check PPBUS_AON voltage at F5200?
I hope not at L5230.
 
HeyWatchOutDude

HeyWatchOutDude

Member
I’m able to see the “restore screen” on the Mac but it’s not possible to restore it via AC2 (DFU) - ends always with error message 4014.

Battery is charging, so I think the CDs are fine.

Yeah I have checked it on F5200.

I have also the restore logs from finder (macOS Sonoma).

[19:53:17.6214] sending file: /var/folders/gx/v8zrsyt9177d1s_9wbs8zmdw0000gn/T/1c999030a567bb23/RestoreRamDisk_096-17234-333.img4
[19:53:23.7793] unable to open device_map.txt: No such file or directory
[19:53:23.7801] found device map entry for 0x00008103 0x00000024 0x00000001. boardConfig=j293ap platform=t8103
[19:53:23.7802] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[19:53:23.7809] _AMRUSBDeviceSendDeviceRequestTO_block_invoke: AMRUSBDevice error (-536854449): {
[19:53:23.7809] "Error message" = "DeviceRequest failed: 0xe000404f (IOKit return code). DeviceRequest was index: 0, direction: 0, requestType: 2, recipient: 0, request: 0, value: 0, length: 21, noDataTO: 60000, completionTO: 60000";
[19:53:23.7809] }
[19:53:23.7810] command device request for 'getenv ramdisk-delay' failed: 2008
[19:53:25.3461] <Recovery Mode Device 0x1491ab1d0>: operation 6 progress -1

RAM failure? Should I replace the RAM (on M1 SoC with a new one?)

After that the error 4014 occurred.

[19:53:26.8609] Max file size is: 536870912
[19:53:26.8611] sending file: /var/folders/gx/v8zrsyt9177d1s_9wbs8zmdw0000gn/T/1c999030a567bb23/Firmware/all_flash/RestoreSEP_sep-firmware.j293.RELEASE.img4
[19:53:27.5734] <Recovery Mode Device 0x1491ab1d0>: operation 7 progress -1
[19:53:27.5749] Max file size is: 536870912
[19:53:27.5749] sending file: /var/folders/gx/v8zrsyt9177d1s_9wbs8zmdw0000gn/T/1c999030a567bb23/RestoreKernelCache_kernelcache.release.img4
[19:53:29.0710] <Recovery Mode Device 0x1491ab1d0>: operation 9 progress -1
[19:53:29.0720] <Recovery Mode Device 0x1491ab1d0>: Recovery mode succeeded
[19:53:29.0720] Finished Recovery Restore Phase: Successful
[19:53:30.6563] Recovery mode device disconnected
[19:53:30.6563] Device removed when in state Restoring, moving device to transition state
[19:53:30.6563] Changing state from 'Restoring' to 'Transitioning'
[19:53:30.6563] Creating timer to monitor transition
[19:53:30.6563] Creating a timer for 10 minutes
[19:53:32.1693] DFU mode device connected
[19:53:32.1693] Transitioning device returned, continuing restore.
[19:53:32.1694] Canceling timer
[19:53:32.1694] Changing state from 'Transitioning' to 'Restoring'
[19:53:32.1695] State Machine Dump, status:ERROR - [state:DFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:1 (current state)]
[19:53:32.1696] Unexpected device state 'DFU' expected 'RestoreOS' (Probably forced into DFU mode externally)
[19:53:32.1723] Restore completed, status: 4014
[19:53:32.1723] Elapsed time (in seconds): 37
[19:53:32.1723] Failure Description:
[19:53:32.1723] Depth:0 Code:4014 Error:Unexpected device state 'DFU' expected 'RestoreOS' (Probably forced into DFU mode externally
 

Attachments

  • IMG_9737.jpeg
    IMG_9737.jpeg
    721.7 KB · Views: 3
  • image.jpg
    image.jpg
    974.5 KB · Views: 2
Last edited:
2informaticos

2informaticos

Administrator
Staff member
Charge the battery a bit more, before trying DFU restore; keep it connected.
Also check all secondary power rails in diode mode and compare with good board.
M1 RAM can be a problem here...
 
HeyWatchOutDude

HeyWatchOutDude

Member
I have compared the AC2 restore logs with a working one ….

Working one:
[19:22:57.1704] Finished Recovery Restore Phase: Successful
[19:22:58.7522] Recovery mode device disconnected
[19:22:58.7522] Device removed when in state Restoring, moving device to transition state
[19:22:58.7522] Changing state from 'Restoring' to 'Transitioning'
[19:22:58.7522] Creating timer to monitor transition
[19:22:58.7522] Creating a timer for 10 minutes
[19:23:05.9815] RestoreOS mode device connected
[19:23:05.9815] Transitioning device returned, continuing restore.
[19:23:05.9815] Canceling timer
[19:23:05.9815] Changing state from 'Transitioning' to 'Debounce'
[19:23:05.9815] Creating timer to wait for USB debounce
[19:23:05.9816] Creating a timer for 2 seconds
[19:23:07.9859] Device still present after debounce timer, continuing restore
[19:23:07.9860] Changing state from 'Debounce' to 'Restoring'
[19:23:07.9860] requested restore behavior: Erase
[19:23:07.9860] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: searching for variant Erase (0 recovery)
[19:23:08.0930] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid, boardid, and secdomain only.
[19:23:08.0930] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: AMAuthInstallBundleCopyBuildIdentityForVariant: Found variant: Customer Erase Install (IPSW)
[19:23:08.1197] amai: AMAuthInstallBundleFDRSupported: FDR is supported for this device
[19:23:08.1198] no override trust object found
[19:23:08.1198] requested restore behavior: Erase
[19:23:08.1198] <Restore Device 0x15389b1e0>: operation 45 progress -1
[19:23:08.1200] requested restore behavior: Erase
[19:23:08.1200] requested variant: Erase
[19:23:08.1200] no override trust object found
[19:23:08.1200] requested restore behavior: Erase
[19:23:08.1200] requested restore behavior: Erase
[19:23:08.1200] amai: AMAuthInstallBundleFDRSupported: FDR is supported for this device
[19:23:08.1201] requested recovery OS variant: macOS Customer

Faulty one:
[19:06:24.7102] Finished Recovery Restore Phase: Successful
[19:06:26.2975] Recovery mode device disconnected
[19:06:26.2976] Device removed when in state Restoring, moving device to transition state
[19:06:26.2976] Changing state from 'Restoring' to 'Transitioning'
[19:06:26.2976] Creating timer to monitor transition
[19:06:26.2976] Creating a timer for 10 minutes
[19:06:27.8649] DFU mode device connected
[19:06:27.8649] Transitioning device returned, continuing restore.
[19:06:27.8650] Canceling timer
[19:06:27.8650] Changing state from 'Transitioning' to 'Restoring'
[19:06:27.8652] State Machine Dump, status:ERROR - [state:DFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:1 (current state)]
[19:06:27.8652] Unexpected device state 'DFU' expected 'RestoreOS' (Probably forced into DFU mode externally)
[19:06:27.8800] Restore completed, status: 4014
[19:06:27.8800] Elapsed time (in seconds): 40
[19:06:27.8800] Failure Description:
[19:06:27.8800] Depth:0 Code:4014 Error:Unexpected device state 'DFU' expected 'RestoreOS' (Probably forced into DFU mode externally)
[19:06:27.8656] Changing state from 'Restoring' to 'Error'
[19:06:27.8658] State is now set to error: Unexpected device state 'DFU' expected 'RestoreOS' (Probably forced into DFU mode externally)
[19:06:27.8659] Device isn't booted but USB is up.

Why does it get forced into DFU mode?

Note: Trackpad is clicking
 
2informaticos

2informaticos

Administrator
Staff member
Test starting in diagnostic mode; any error pops up?

Also try starting Internet Recovery, with its various flavours.
 
You must log in or register to reply here.
Top