Chosen Solution
Ever since changing the battery in my MacBook, I’ve been getting this error every time I close my lid and the computer goes to sleep. It doesn’t wake back up when I open the lid, I have to press the power button and boot it up. I’ve tried resetting the SMC to no avail. I get this error: Sleep Wake failure in EFI Failure code:: 0xffffffff 0x0000001f Please IGNORE the below stackshot
Date/Time: 2021-08-01 19:12:10 -0400
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 29
Data Source: Stackshots
Shared Cache: 0xc728000 867DFE32-D70B-31FB-9235-19DB52F41CA4
Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1
Time Awake Since Boot: 10s
Process: swd [283]
Architecture: x86_64
Footprint: 400 KB
Start time: 2021-08-01 19:12:10 -0400
End time: 2021-08-01 19:12:10 -0400
Num samples: 1 (1)
Thread 0x76e 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 1 (libdyld.dylib + 109769) [0x7fff73a61cc9] 1
1 ??? [0x109863454] 1
1 ??? [0x1098631dd] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135862) [0x7fff73bc32b6] 1
*1 ??? [0xffffff80002c3206] 1
*1 ??? [0xffffff8000983cd7] 1
*1 ??? [0xffffff800089c7f1] 1
*1 ??? [0xffffff80002e69e7] (running) 1
Binary Images:
0x7fff73a47000 - 0x7fff73a7dfff libdyld.dylib (750.7)
Sounds like the Hall sensor has failed. I would first make sure the HD SATA cable is plugged in fully. If that’s OK, I would just go-ahead and replace the cable as this cable is known to have problems! Your Hard Drive Cable Is A Ticking Time Bomb Make sure you don’t crease the cable as you also don’t want to damage it. Here’s the needed part: MacBook Pro 13" Unibody (Mid 2012) Hard Drive Cable and the guide to put it in MacBook Pro 13" Unibody Mid 2012 Hard Drive Cable Replacement
I’m very curious about how you arrived at this conclusion, e.g. that a “Sleep Wake failure in EFI” issue that began after replacing the battery is caused by a failing HD SATA cable. (I have a customer with exactly the same issue as described in the original post and am still searching for a solution.)
