Hi, I have a 2012 Unibody MacBook Pro that I'm having a really weird issue with.

It wasn't used for around 6 months, but before that it was working perfectly fine. The battery was also working normally before I stopped using it.

Now, when I try to turn it on normally, it starts booting for about 1% and then suddenly turns off. But here's the weird part: if I hold down any key on the keyboard, it stays on and works like a normal laptop. As soon as I let go of the key, it immediately turns off.

The battery also isn't detected at all, and the battery indicator lights on the side don't work either.

I'm not really sure what's causing this. Could this be a battery or SMC issue, or could something on the logic board be causing it?

Is there anything I can test or try myself before taking it to a repair shop?

Also, diagnostics show reference code :PPT001, PFM001.

Thanks!

⟐ Commented August 27, 2026 at 21:01 MST

⟐ Answer edited August 27, 2026 at 15:57 MST

⟐ Commented August 27, 2026 at 13:43 MST

And also, The hinge is getting tight overtime. i kept opening it gently because the screen might crack. I still have 3 more years to graduate with this laptop.

⟐ Commented August 27, 2026 at 5:51 MST

I found some similar questions, but none specific enough to make sure they were the same problem, and none with detailed solutions.

A video of the symptoms before I explain with words:

My Macbook's screen sometimes starts fading out. First the pixels get wider, meaning the image seems pixelated. Then the colors start changing, until it gets inverted, then it fades to completely dark grey.

There's no correlation of when it does that and when it doesn't. Sometimes I am just working while everything is normal, and all of a sudden it starts. Sometimes it’s in the morning, I am just waking it from sleep, without even touching the screen, and it’s in that state.

If I then try to bend a little bit the upper left corner of the screen, it goes back to normal. Sometimes it’s enough to keep it working without my pressure. Sometimes as soon as I let go, it starts fading again, and I have to push the whole computer against something to exert that pressure while I work.

Sometimes the problem will remain for weeks and months, and at some point go away for weeks and months.

Sometimes I have to press very hard for the screen to come back to normal, sometimes a very gentle touch will suffice.

It’s mostly on the upper left corner that I have to bend. Sometimes it’s on the upper right corner, but rarely.

When I plug an external display, it works fine.

I tried opening up the Macbook and disconnecting the screen, vacuuming the cable, socket, and everything.

Sometimes after I put everything back together, the problem goes away for a few weeks. Sometimes it doesn’t change anything.

I also tried opening the case while the laptop is on, and moving a little bit the display cable, to see if it changes anything. It didn’t.

I noticed that some kind of shield on the motherboard’s socket is out of position. But it seems unlikely to me to cause the problem:

I also noticed a visual irregularity on the display cable’s outer wrapping, but I don’t know whether that’s damage or not:

I very recently noticed that the top part of my LCD is unglued from its shell. But I don’t know whether it was there before, and thus could be a cause, or whether it’s the consequence of my bending the top left corner of the screen so many times.

It seems to me the screen itself is fine.

So I feel like it could be either the socket on the motherboard, or the cable, or the socket on the LCD. Right?

Does anyone know whether there is a quick fix to this, or how to narrow down the cause?

My partner’s laptop is a 2010 macbook pro, so the same but one year younger. Do you know if I could plug her screen onto my laptop? If so I could rule out the motherboard socket, or conversely incriminate it.

Thanks a lot in advance for the help!

⟐ Commented August 26, 2026 at 19:05 MST

I have recently gotten my hands on a Mid 2015 15” MBP that was running slow, hoping I could get it fixed back up for personal use.

The previous owner had apparently swapped the old battery out with a new iFixit replacement one and then immediately sold the device as it has been running slow ever since. Using IntelPowerGadget on OSX or Task-Manager on Windows shows the CPU constantly being clocked down to 0.8ghz. This is definitely not thermal throttling as the chipset never exceeds 50C, there are also no faulty sensors when checking with HWMonitor.

The original battery had been discarded so I cannot check whether this issue is actually caused by the battery at all, however inspecting the battery visually and using CoconutBattery I can see that it is not an OEM battery since there is no battery serial number being displayed. Running the hardware diagnosis (holding the “D” key at startup) reveals that the battery might have problems but it says I should still be able to use the device without any noticable changes, showing the error code PPT004.

I then went ahead and bought this used original A1398 battery, thinking it was salvaged from another Macbook, however it ended up being some sort of refurbished third party battery causing the same issues again so I will have to return it anyway. The values shown on CoconutBattery are similar for both batteries (both less than 10 charge cycles, etc.) so I have just attached an image of the iFixit one below.

The machine itself is in mint condition, I have made sure to look for any water damage on the logic board but it seems perfectly clean, after all the device can be used flawlessly with the exception of it running at 1/4 the supposed speed.

I did come across similar threads however they were usually regarding older macbooks or were only having this issue intermittently when plugging in an external monitor, etc.

Others proposed just deleting the IOPlatformFamily.kext from OSX to get rid of the Intel Speedstepping feature, however this method is somewhat outdated and seems like a stupid idea anyway. A similar solution was being shared here, however that is again just circumventing the issue instead of fixing it, and even then Im not sure that would at all.

Essentially I just want to know two things:

1. Is this throttling behaviour really linked to a 3rd party battery instead of a logic board fault, and if so, why would anyone buy or manufacture such batteries if they make the device useless? If this is the case there should have been plenty of others with this exact issue, yet I have only found a few threads discussing a similar issue
2. With the iFixit as well as the other “genuine” battery not working as intended, where would I even begin looking for an actual OEM battery within Europe without having to get it replaced at an Apple store?

I never had any issues replacing the battery on a 2012 MBP, so Its fair to say this behaviour could just be another one of Apples shenanigans to get peoples devices fixed at Apple only and nowhere else, but I just couldnt find a definitive answer especially since I dont have the original battery to compare against.

I wouldn’t know where to ask otherwise, so any reply would be very appreciated!

Update:

I have tried using ThrottleStop on BootCamp Windows according to this thread, this does however also not work. Deleting the IOPlatformPluginFamily.kext as mentioned in the same thread is not an option since it does not even exist on my OS X Catalina installation.

Final Update (Found a solution):

So it turned out not to be a battery related issue . The person I bought the device from stated the issue appeared after swapping it for an iFixit replacement battery, but after buying yet another OEM battery the problem still persisted.

Instead, the issue was related to the CPU current sensing circuitry. I didnt manage to find accurate boardview and schematics for my specific model (820-00138) so I had to use this XinZhiZao (similar to ZXW tool) maintenance program which had the correct board layout to find the problem.

The issue was caused by the "SMC_CPU_IMON_ISENSE" line which is produced by the U7200 power management IC. This chip is responsible for measuring the CPU power usage among other things, and sends the signal through R5530 directly to the SMC. This line was permanently stuck at 1.8V which made the SMC read a high CPU power draw, so it throttled the CPU to 0.8ghz clock for safety reasons.

I ended up running a jumper (blue) from this line to ground, thus forcing the line to 0V.

This way the system now reads CPU current as 0W and I can finally use the machine with its intended performance. No lags, everything finally runs smoothly. It also no longer gets stuck in sleep mode after closing the lid.

Obviously this fix is only a workaround as I still dont know what was pulling the line to 1.8V, so I assume it was either the SMC or U7200 which shorted the line to a neighboring power line somewhere. I didnt want to risk ruining the SMC by reballing it so shorting the pad for C5530 to ground seemed easier to do. However this means there is a constant 1.8V short to ground so I might want to replace the jumper wire with a resistor to avoid losing much battery power being wasted into the short in the future.

In conclusion, the built-in Apple Diagnostics (Holding down Cmd + D on startup) did find an issue, however it was not related to the battery but rather the SMC or U7200. My assumption of having to use a OEM battery was wrong, as it also now works just fine with the replacement iFixit battery. I used HWmonitor on OSX to check the “CPU Package Total” readings, which were at 100 watts and above. After the fix it is reading -W, so the remaining battery time estimations might be inaccurate, but it technicallly isnt necessary.

Im not exactly sure how a simple battery swap could have caused this issue, but since I didnt find much information regarding Macbooks being throttled to 800mhz CPU performance, make sure to check all temperature and current readings using some sort of monitoring tool like mentioned above. A faulty temperature sensor might possibly cause a similar issue.

Hope this helps

⟐ Answered August 25, 2026 at 17:05 MST

Hi everyone,

I have a Late 2023 MacBook Pro 14" (M3 Pro), and I've noticed that the display lid is slightly misaligned to the right. When the laptop is closed and I run my fingers along the side edges, I can clearly feel that the top lid is slightly off-center compared to the bottom case.

I've seen other people reporting this exact same issue online, so I'm attaching a few more photos of misaligned screens for reference.

I would like to know: Is it possible to open the bottom case and adjust the hinge screws to realign the display perfectly?

Thanks in advance for the help!

⟐ Answer edited August 25, 2026 at 13:16 MST

⟐ Answered August 24, 2026 at 8:06 MST

⟐ Commented August 24, 2026 at 7:52 MST

So I want to disassemble the original Apple L connector and solder it to the unoriginal cable. I don’t mind cutting off the replacement L connector, as it is of no use for me, because when I use it with my Macbook pro 13” late 2011, the battery gets hot, and when I used it with my Macbook white mid 2009, the battery swelled and now when I use that MB 2009 with the unoriginal cable, with no battery, it won’t even turn on (it does turn on when used with fully original power adapter).

So… disassemble an original magsafe L connectror and solder it to another wire. How do I do that? In fact the problem is more about disassembling the L connector, because I do know how to solder things.

⟐ Commented August 22, 2026 at 15:22 MST

The issue:

1. With the new battery, the MagSafe light stays green. System Information sees the battery at 33% (2308mAh) but shows 0 Amperage and "Not Charging."

2. If I unplug the MagSafe, the laptop immediately shuts off.

3. I reinstalled the old (bulging) battery to test. It shows 100% (4322mAh) and "Fully Charged," but the laptop still shuts off immediately if the power cord is disconnected.

4. CRITICAL FINDING: The battery indicator button (on the left side) ONLY works when the MagSafe is plugged in. When plugged in, it shows 3 LEDs (consistent with 33%). When unplugged, the indicator button does nothing.

5. I have already:

- Reset the SMC and NVRAM/PRAM multiple times.

- Verified I am using an 85W MagSafe adapter.

- Reseated the battery connector and inspected the logic board pins.

- Ran Disk Utility First Aid.

Is it possible the original bulging battery blew a current-sensing resistor or a MOSFET on the logic board? What specific components should I test with a multimeter to diagnose why the battery rail is not being energized?

Here is an image (maybe) of the coconut app and the system report.

Here is an image of the system report with the bad battery

=== ===

⟐ Commented August 21, 2026 at 11:54 MST

This is my progress on removing the anti-glare coating after 2 hours. I tried Listerine, 90% alcohol, Peek Metal Polish, anti-bacterial wipes, bleach, and nail polish remover w/ acetone (before I read that someone else damaged the glass itself because of acetone). Luckily, my glass is still fine. Unfortunately, I haven't made much progress as you can see from the picture. I'm confused to why none of the solutions isn't working for me. Some said that Listerine alone worked well along with a microfiber cloth. I tried that but since it didn't work I moved on to try all the other solutions I mentioned. Is anyone else having this issue dispite of trying all kinds of solutions? And is there any other alternatives that would make it simple to remove w/o much time being spent?

⟐ Commented August 20, 2026 at 13:25 MST

I know that the CPU and GPU are soldered onto the logic board, so therefore, my question would be; is there any much more modern logic board that would in theory fit inside the chassis of a 17 inch A1229? I know that the connectors would be completely different, but would there be anything stopping you if you did find a logic board that fits in and you could swap out the connectors etc.

Clearly this doesn't make sense if you were just trying to get value out of an old machine thinking it would be cheaper, but is it even possible in theory for someone who had an abundance of time and money?

⟐ Answered August 19, 2026 at 16:42 MST

I’ve reinstalled the OS and restored from Time Machine, but the problem persists. Here’s a screenshot of the battery reading.

I really hope this can be fixed, as I’d hate to keep the Mac connected to a dock with this issue. Thanks in advance.

⟐ Commented August 19, 2026 at 4:22 MST

⟐ Commented August 18, 2026 at 7:56 MST

I have a mid-2012 13" MacBook pro (2.5 Ghz, the cheaper model).

So, my main focus is to change my Graphic Card (i have the Intel HD Graphic 4000) and my RAM (from 4 GB to 8 GB), however I found out i had to change my motherboard (logic board) to be able to change my graphic card.

Therefore would it be possible to get the motherboard of the other mid-2012 Macbook Pro 13" (2.9 Ghz), put it in my laptop and change the graphic Card to an NVIDIA ?

And the best question of all: would it be cheaper to buy a laptop just for Gaming ? Thats somethiin i dont want to do, having two laptops, thats too much.

And also because my mac works really well, he is just to shi**y to play games like Titanfall or BF4. I am stuck with Star wars and LoL right now. Feel my pain.

Just like Jon Snow, i know nothing. So please speak to me as if i was a toddler smashing a star shaped block into the circle shaped hole.

⟐ Commented August 17, 2026 at 23:04 MST

2026-07-15 13:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008591 [System: SRPrevSleep kCPU]

2026-07-15 13:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008591 [System: No Assertions]

2026-07-15 14:37:35 +0600 Assertions          PID 1967(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x1000085d7 [System: No Assertions]

2026-07-15 14:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000085f8 [System: SRPrevSleep kCPU]

2026-07-15 14:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000085f8 [System: No Assertions]

2026-07-15 15:37:26 +0600 Assertions          PID 1993(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x100008645 [System: No Assertions]

2026-07-15 15:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008668 [System: SRPrevSleep kCPU]

2026-07-15 15:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008668 [System: No Assertions]

2026-07-15 16:37:26 +0600 Assertions          PID 2020(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x1000086bf [System: No Assertions]

2026-07-15 16:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000086e0 [System: SRPrevSleep kCPU]

2026-07-15 16:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000086e0 [System: No Assertions]

2026-07-15 17:39:26 +0600 Assertions          PID 2074(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x10000872a [System: No Assertions]

2026-07-15 17:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008753 [System: SRPrevSleep kCPU]

2026-07-15 17:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008753 [System: No Assertions]

2026-07-15 18:38:20 +0600 Assertions          PID 2136(AddressBookSourceSync) Summary PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:24  id:0x0x10000879f [System: PrevIdle]

2026-07-15 18:38:26 +0600 Assertions          PID 2136(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x10000879f [System: No Assertions]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:00  id:0x0xd00008002 [System: PrevIdle SRPrevSleep kCPU]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008003 [System: PrevIdle SRPrevSleep kCPU]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008003 [System: PrevIdle SRPrevSleep kCPU]

Sleep/Wakes since boot at 2026-07-15 10:06:39 +0600 :0   Dark Wake Count in this sleep cycle:1

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created UserIsActive "com.apple.powerd.ws.initialize" 00:00:00  id:0x0x900008007 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

2026-07-15 18:28:42 +0600 Assertions          Summary- [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp] Using AC(Charge: 100)

2026-07-15 18:28:44 +0600 Assertions          PID 419(WindowServer) Created UserIsActive "com.apple.iohideventsystem.queue.tickle.nxevent service:IOHIDSystem pid:660 process:Dock" 00:00:00  id:0x0x900008038 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

2026-07-15 18:28:46 +0600 Assertions          PID 359(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:05  id:0x0xd00008002 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

What is wrong with my macbook? Is it a Touch ID issue or some other hardware/ software related problem?

Things to keep in mind:

1. I installed battery toolkit and used it in this month. I never had any issues with battery but decided to use it since my capacity was 85%. Cycle count is at 483. Condition is normal

2. I did not perform a full wipe when updating my OS from 12.1 to 26.5.2

3. After my macbook booted up, there were no other problems and it worked as intended.

4. Apple diagnostics says there is nothing wrong with any of my hardware (including Touch ID and Battery)

Update 1: Did a workaround by disabling lock screen entirely and removing touch ID as they were usually the causes of hard crash. After leaving my mac overnight with lid closed (not shutdown), it was simply dead right off the bat. I digged up some logs using the same command as before:

2026-07-18 10:11:47 +0600 com.apple.sleepservices.sessionTerminated SleepService: window has terminated.

2026-07-18 10:11:47 +0600 Sleep               Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using Batt (Charge:75%)

2026-07-18 10:11:50 +0600 Wake Requests       [*process=dasd request=SleepService deltaSecs=995 wakeAt=2026-07-18 10:28:25 info="com.apple.dasd:501:com.apple.chronod.nextScheduledTimelineRefresh"] [process=mDNSResponder request=Maintenance deltaSecs=7200 wakeAt=2026-07-18 12:11:50 info="upkeep wake"] [process=powerd request=TCPKATurnOff deltaSecs=312730 wakeAt=2026-07-22 01:04:00] [process=powerd request=CSPNEvaluation deltaSecs=3125 wakeAt=2026-07-18 11:03:55] [process=powerd request=UserWake deltaSecs=10775 wakeAt=2026-07-18 13:11:26 info="com.apple.alarm.user-invisible-com.apple.calaccessd.travelEngine.periodicRefreshTimer,617"]

2026-07-18 10:11:50 +0600 PM Client Acks      Delays to Sleep notifications: [com.apple.bluetooth.sleep is slow(1543 ms)] [mDNSResponder is slow(2877 ms)]

Sleep/Wakes since boot at 2026-07-17 20:45:23 +0600 :65   Dark Wake Count in this sleep cycle:4

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:00  id:0x0xd0000817c [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

Sleep/Wakes since boot at 2026-07-18 13:25:14 +0600 :0   Dark Wake Count in this sleep cycle:4

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Released PreventUserIdleSystemSleep "Powerd - Prevent sleep while display is on" 00:00:26  id:0x0x100008008 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 426(runningboardd) Summary PreventUserIdleSystemSleep "osservice<com.apple.itunescloudd(501)>426-739-303:com.apple.CFNetwork.StorageDB" 00:00:01  id:0x0x100008177 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Summary UserIsActive "com.apple.powerd.ws.initialize" 00:00:26  id:0x0x900008009 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 418(WindowServer) Summary UserIsActive "com.apple.iohideventsystem.queue.tickle serviceID:100000ab6 service:AppleMultitouchDevice product:Apple Internal Keyboard / Trackpad eventType:11" 00:00:02  id:0x0x900008033 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 556(mds_stores) Summary BackgroundTask "com.apple.metadata.mds_stores.power" 00:00:19  id:0x0xb00008105 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 374(mds) Summary BackgroundTask "com.apple.metadata.mds.power" 00:00:23  id:0x0xb0000803f [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask B5FB9788-3BCE-44C8-9D99-D492F0F20E72" 00:00:03  id:0x0xc00008172 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask A7F6768B-E0B3-4E2B-8783-17F66C8421B0" 00:00:02  id:0x0xc00008173 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask BBF3B16C-FA61-4E7F-8A82-B1CFD051E55D" 00:00:02  id:0x0xc00008175 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask A94CE808-2F83-4140-AE56-1C3AA62BB4A7" 00:00:01  id:0x0xc00008176 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask 0441BFAA-CDB2-4F65-8FC6-9DC89EBAF7A9" 00:00:01  id:0x0xc0000817b [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Summary InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:00  id:0x0xd0000817c [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Released SystemIsActive "NSURLSessionTask B5FB9788-3BCE-44C8-9D99-D492F0F20E72" 00:00:03  id:0x0xc00008172 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 418(WindowServer) TurnedOn UserIsActive "com.apple.iohideventsystem.queue.tickle serviceID:1000002e0 service:AppleM68Buttons product:(null) eventType:3" 00:00:00  id:0x0x900008033 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Created UserIsActive "com.apple.powermanagement.lidopen" 00:00:00  id:0x0x900008184 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:43 +0600 Assertions          PID 647(cloudd) Released SystemIsActive "NSURLSessionTask A7F6768B-E0B3-4E2B-8783-17F66C8421B0" 00:00:03  id:0x0xc00008173 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:43 +0600 Assertions          Summary- [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp] Using Batt(Charge: 69)

Somehow, my battery went from 75% in sleep state, hard crashed into a dead mode, and then suddenly became 69%

Update 2: Decided to shutdown mac and hopefully boot into diagnostics mode. Turns out mac simply restarted before i could even do anything and it said my mac restarted due to a problem. Logs are below:

panic(cpu 1 caller 0xfffffe003e8b4418): SEP Panic: :sars/sars: 0x100010858 0x000584bc 0x00050434 0x10000f880 0x100002388 0x10000be34 0x10000c568 0x10000d070 0x10000b014 0x100006180 0x00052870 0x10000ef0c 0x100005fe4 0x100008d20 0x100000d74 0x100000bc8 0x1000009f0 [hggghgolo]

Panic app vers: 3151.120.3

Panic app UUID: 68A9CDAF-552F-3BB1-B20A-76DA1F603737

Shared cache vers: 3151.120.3

Shared cache UUID: 3726CD1B-A290-308A-9AD8-69417B8D59B2

Root task tag: (root@cm8qz.p1l.plx.sd.apple.com)

Root task build time: Jun 1 2026 20:50:54

Root task vers: AppleSEPOS-3151.120.3

Root task UUID: ECFAE211-028E-35A0-B492-D6BB5A16CADF

Diagnostics: 584c0100e934093989bd7c6a86a7da3f703d52f2332e065d39caf3f38874b447f0b42bf2efeb644800000000000000000000000000000000000000000000000000000000a2953b28c10ac912c87cda8ad9b66eb1555b8ea7f3c9501033c7ca6ba6448acd9dd63ca700000000000000000000000000000000000000000000000000000000000005

SEPO/BOOT

SEPO/EXCP 0xa684/0xab04/0x0000000000000013 er/EXCP

SEPD/SEPD 0x4c63c/0x4cdb4/0x1817181718171817 er/SEPD

SEPD/TIME 0x4c63c/0x4cb10/0x1417181314171813 er/TIME

SEPD/XPRT 0x4c63c/0x4cdb4/0x1817181718171817 er/XPRT

SEPD/PMGR 0x4c63c/0x4cdb4/0x1817181718171817 er/PMGR

SEPD/TRNG 0x4c63c/0x4cb10/0x1314101314131413 er/TRNG

SEPD/KEY 0x4c63c/0x4cb10/0x1718171817181013 er/KEY

SEPD/MONI 0x4c63c/0x4cdb4/0x1516171810151617 er/MONI

SEPD/AKF 0x4c63c/0x4cb10/0x1406101314061013 er/AKF

SEPD/EP0D 0x4c63c/0x4cb10/0x1813141314131413 er/EP0D

SEPD/AESH 0x4c63c/0x4cdb4/0x1516171810151617 er/AESH

SEPD/shnd 0x4c63c/0x4cdb4/0x1817181718171817 er/shnd

SEPD/ep0 0x4c63c/0x4cb10/0x1413141314131413 er/ep0

AESS/DAES 0x4c63c/0x4cdb4/0x1817181718171817 er/DAES

AESS/AESS 0x4c63c/0x4cdb4/0x1516171810151617 er/AESS

AESS/PKA 0x4c63c/0x4cdb4/0x1516171810151617 er/PKA

AESS/AEST 0x4c63c/0x4cdb4/0x1516171810151617 er/AEST

dxio/dxio 0x4c63c/0x4d0fc/0x1410131410131410 r/----

enti/enti 0x4c63c/0x4cdb4/0x1817181718171817 er/enti

enti/vers 0x4c63c/0x4cdb4/0x0000000000131417 er/vers

skg /skg 0x4c63c/0x4cdb4/0x1817181718171817 er/skg

skg /skgs 0x4c63c/0x4cdb4/0x1817181718171817 er/skgs

skg /crow 0x4c63c/0x4cb10/0x0000000000000013 er/crow

skg /cro2 0x4c63c/0x4cb10/0x0000000000000013 er/cro2

sars/sars 0x4c63c/0x4c368/0x1112111211121112 ert/BOOT

ARTM/ARTM 0x4c63c/0x4cb10/0x0000000000000013 er/ARTM

xART/xART 0x4c63c/0x4c368/0x1314171817181718 ert/sars

hibe/hibe 0x4c63c/0x4cb10/0x0000000000131413 er/hibe

scrd/scrd 0x4c63c/0x4c368/0x1718171813141314 ec/xART

pass/pass 0x4c63c/0x4cb10/0x1013141013141013 er/pass

sks /sks 0x4c63c/0x4c368/0x1314131413141314 ert/xART

sks /sksa 0x4c63c/0x4cb10/0x0000000013141013 er/sksa

hdcp/hdcp 0x4c63c/0x4cb10/0x1413141314131413 er/hdcp

stac/stac 0x4c63c/0x4cdb4/0x1417181718171817 er/stac

sbio/sbio 0x4c63c/0x4cb10/0x1413141314131413 er/sbio

sbio/blcx 0x4c63c/0x4d2a0/0x0000000000000f11 wn/----

sbio/---- 0x4c63c/0x4d2a0/0x0000000000000f11 wn/----

sse /sse 0x4c63c/0x4cb10/0x1413141314131413 er/sse

boop/boop 0x4c63c/0x4cb10/0x1413141314131413 er/boop

skdl/skdl 0x4c63c/0x4cb10/0x1413141314131413 er/skdl

Firmware type: UNKNOWN SEPOS

SEP state: 8

PM state: 2

Boot state: 32

Mailbox status:

IDLE_STATUS: 0x00000028

INBOX0_CTRL: 0x00026601

OUTBOX0_CTRL: 0x00029901

Mailbox entries:

Unavailable

Mailbox queue pointers: 28/28 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 23/23 -1/-1 15/15 -1/-1 2/2 -1/-1 11/11 -1/-1 0/0 -1/-1 26/26 9/9 0/0 24/24 -1/-1 5/5 2/2 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1

TZ0 explicitly set 1 size 0x1c08000

TZ1 explicitly set 0 size 0x8000

Debugger message: panic

Memory ID: 0x1

OS release type: User

OS version: 25F84

Kernel version: Darwin Kernel Version 25.5.0: Tue Jun 9 22:18:58 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 32F4D28271521AC511D4722B289D8363

Kernel UUID: E977B940-FDD2-35CD-81B3-EC65AAB8BF5C

Boot session UUID: 7B3BB323-7201-44C9-B421-5D407834F08F

iBoot version: mBoot-18000.121.3

iBoot Stage 2 version: mBoot-18000.121.3

secure boot?: YES

roots installed: 0

Paniclog version: 15

Debug Header address: 0xfffffe001bfdd000

Debug Header entry count: 3

TXM load address: 0xfffffe002bf38000

TXM UUID: F0C1A57F-CE44-3DF4-9E86-0CFF02D7C00D

Debug Header kernelcache load address: 0xfffffe003bf38000

Debug Header kernelcache UUID: 32F4D282-7152-1AC5-11D4-722B289D8363

SPTM load address: 0xfffffe001bf38000

SPTM UUID: D249E718-9C0B-36F5-9F6B-24D58BED4606

KernelCache slide: 0x0000000034f34000

KernelCache base: 0xfffffe003bf38000

Kernel slide: 0x0000000034f3c000

Kernel text base: 0xfffffe003bf40000

Kernel text exec slide: 0x0000000039608000

Kernel text exec base: 0xfffffe004060c000

mach_absolute_time: 0x135ef1b987

Epoch Time: sec usec

Boot : 0x6a5b2a3d 0x0007708e

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x6a5b37c1 0x0009de5d

Zone info:

Zone map: 0xfffffe121a000000 - 0xfffffe381a000000

. VM : 0xfffffe121a000000 - 0xfffffe17e6000000

. RO : 0xfffffe17e6000000 - 0xfffffe1a80000000

. GEN0 : 0xfffffe1a80000000 - 0xfffffe204c000000

. GEN1 : 0xfffffe204c000000 - 0xfffffe2618000000

. GEN2 : 0xfffffe2618000000 - 0xfffffe2be4000000

. GEN3 : 0xfffffe2be4000000 - 0xfffffe31b0000000

. DATA : 0xfffffe31b0000000 - 0xfffffe381a000000

Metadata: 0xfffffe1008010000 - 0xfffffe1011810000

Bitmaps : 0xfffffe1011810000 - 0xfffffe1014520000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xfffffe2be6b2aba0 0: 0x0001000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f00bee0

CORE 1 is the one that panicked. Check the full backtrace for details.

CORE 2: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f0ebee0

CORE 3: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950ecebee0

CORE 4: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f5bbee0

CORE 5: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f56bee0

CORE 6: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950e91bee0

CORE 7: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950e9bbee0

CORE 8: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950ebbbee0

CORE 9: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950eafbee0

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xfffffe2517f8eb58: 0 pages, 595 threads: pid 0: kernel_task

Panicked thread: 0xfffffe2be6b2aba0, backtrace: 0xfffffe950edeb610, tid: 2176

lr: 0xfffffe004066457c fp: 0xfffffe950edeb6b0

lr: 0xfffffe00407e84ec fp: 0xfffffe950edeb720

lr: 0xfffffe00407e6464 fp: 0xfffffe950edeb7e0

lr: 0xfffffe0040611c40 fp: 0xfffffe950edeb7f0

lr: 0xfffffe0040664888 fp: 0xfffffe950edebd10

lr: 0xfffffe0040f68a78 fp: 0xfffffe950edebd30

lr: 0xfffffe003e8b4418 fp: 0xfffffe950edebd60

lr: 0xfffffe003e896af0 fp: 0xfffffe950edebd80

Note that I never even touched the Touch ID this time. I simply shut it down and before I even got the chance to do anything, it started right back up.

⟐ Answered August 16, 2026 at 6:36 MST

Anyway, I assembled everything according to the guide and everything works well, the battery is also great. However, I have just noticed, that even though the power button works, the touch id does not:

Whenever I log into the account after starting the mac, I enter the password, and after some time whenever it goes to sleep I cannot open it with touch id. Additionally, touch ID stopped working with saved passwords in Safari.

Also, whenever I try to add a new fingerprint, I get following error, right after I click add fingerprint and enter the password:

Failed

Unable to complete Touch ID enrollment.

So it does not even allow to put a finger on it. Anyone knows how I can solve this issue? Because power button works.

What I did so far:

• Tried to reset NVRAM and SMC
• Tried to add new fingerprint in Safe Mode
• Visually inspected if the ribbon for touch id and power button is damaged (it is not)
• Tried creating a new user and adding a fingerprint
• Tried running Apple Diagnostics (Control+D on startup) - no hardware failures.

Anyone encountered it and knows about any possible solutions I can try?

Finally found some time to disassemble it, I reconnected everything, as you can see in the images (even though low quality but hopefully good enough), the touch ID does not work and touch id enrolment fails :(

⟐ Answered August 16, 2026 at 4:28 MST

Current status/troubleshooting performed:

- Draws 20V and ~3.45A on USB-C (power delivery is negotiating normally).

- External monitor / peripherals show no output.

- Performed DFU mode revive and restore using Apple Configurator 2, but it did not resolve the issue.

- Internal connections and cables checked; no physical or liquid damage found.

Since standard DFU restore and basic troubleshooting haven't fixed a post-upgrade failure like this, what component level or firmware issue (such as T2 ROM corruption or specific power rails) could cause this behavior?

⟐ Commented August 15, 2026 at 21:01 MST