iFixit - Answers With Device "MacBook Pro"

MacBook Pro 13" Function Keys 2017: No power, fans spin at full speed

Sun, 26 Jul 2026 19:25:30 -0700

I got a 2017 13” MacBook Pro online for parts. The fans gradually ramp up and spin at full speed when plugged in. The trackpad connector was ripped off of the board and there is no ssd. Water damage indicators are also red, but no visual marks or stains. I get no image on the display, caps lock key does not light up when I press it. When unplugged, the system immediately shuts down. Any help?

⟐ Commented July 26, 2026 at 19:25 MST

MacBook Pro 13" Two Thunderbolt Ports Late 2020: Camera does not work and the green light stay off

Sun, 26 Jul 2026 10:38:50 -0700

Hi everyone,

Essentially, my Macbook Pro M1 16GB 2020 (A2338) camera has stopped working. Not sure why. If I open Photo Booth, the screen is black but there is no message/warning. The camera light does NOT switch on either.

Tried the following:

Restarting
sudo killall VDCAssistant and AppleCameraAssitant but it says No matching processes.
Reset the laptop (factory reset using iTunes)
Took off the bottom cover to confirm the 4 ribbon cables were still connected from the screen

If I go to my system information, then go to my camera, it says "No video capture devices were found".

Everything else works perfectly fine so not sure why it would be the camera hardware itself.

⟐ Commented July 26, 2026 at 10:38 MST

MacBook Pro 13" Function Keys 2017: My backlight isn’t working after testing the screen on another MacBook

Sat, 25 Jul 2026 12:01:28 -0700

My display backlight was working perfectly just a day ago, but ever since I connected the display into another MacBook I was testing the backlight completely stopped functioning. I already swapped the small cable that connects the display board with the logic board and have also tried SMC/PRAM reset without luck. Connecting another display to the MacBook shows nothing either (this screen was untested however). Any help?

⟐ Answer accepted July 25, 2026 at 12:01 MST

MacBook Pro 16" 2021: Spacebar does not register clicks on the edges

Fri, 24 Jul 2026 06:01:20 -0700

After replacing all my keycaps I noticed that my spacebar does not register clicks properly on the edges. While this is not a major issue it is very bothersome. During replacement I noticed the key was bottoming out and not coming back up, after further inspection I noticed the clip that holds the stabilizers in was bent so I unbent it carefully with a flat screwdriver. I suspect the bent stabilizer clips are at fault, is there anything that can be done or does the entire keyboard have to be replaced?

⟐ Commented July 24, 2026 at 6:01 MST

MacBook Pro 16" 2021: Keyboard backlighting not working

Fri, 24 Jul 2026 04:04:42 -0700

Symptoms - White Keyboard backlighting doesn't work. Occurred after liquid entered left side of device when closed (side with MagSafe port). All ports work, key strokes work, CAPS LOCK LED WORKS, everything works other than white backlight.

Troubleshooting steps - I've basically done everything software wise, so I know it's hardware. Chat GPT seems to believe it's the backlight fuse that may have blown due to liquid entering.

Anyone have a hunch on what's happening? I know liquid is difficult, as I've actually worked at an Apple Store as a technician. This was a used purchase and I'd rather not spend a whole lot fixing it, but I'd like the backlight to work.

I do not have soldering equipment or a microscope, but I'm comfortable disassembling and stuff at home (I've replaced thousands of phone batteries and displays, and I build computers as a hobby). Thanks!

⟐ Commented July 24, 2026 at 4:04 MST

MacBook Pro 15" Retina Display Mid 2015: MacBook Pro Retina 15” Mid 2015 (A1398): Black screen after display re

Thu, 23 Jul 2026 13:03:48 -0700

Hello,

I’m looking for a board-level diagnosis for my MacBook Pro Retina 15” Mid 2015 (A1398).

Configuration

Intel Core i7
16 GB RAM
macOS Monterey 12.7.6

History

Before repair:

The original internal display was cracked but still displayed an image.
The Mac worked perfectly with an external HDMI monitor.

During repair:

A technician installed a display from a MacBook Pro 2013.
The replacement display never worked.
He reinstalled my original cracked display.
Since then, the internal display has been completely black.

Current behavior

If the internal display cable is disconnected:

Apple logo appears on the external HDMI monitor.
Startup Manager (Option key) works.
Internet Recovery works.
But when booting from Macintosh HD, Recovery, EFI Boot or a bootable USB, the Apple logo appears, then the screen goes completely black.

If the internal display cable is connected:

The internal display remains completely black.

The Mac appears to continue running:

keyboard backlight works,
volume keys work,
fans operate normally,
but there is no video output.

Already tried

NVRAM reset
SMC reset
Safe Mode
Internet Recovery
Bootable USB installer
OpenCore Legacy Patcher

Always the same result:
Apple logo → black screen.

Verbose mode also showed messages including:

device is not readable
failed to initialize volume keybag

Questions

Could installing a 2013 Retina display on a 2015 A1398 have damaged the LCD connector or another logic board component?
Which is the most likely cause?
- LCD connector
- LCD power/backlight circuit
- Display cable
- GPU
- SSD/APFS
- Logic board
What measurements or board-level tests would you perform before replacing parts?

Any advice would be greatly appreciated. Thank you.

⟐ Commented July 23, 2026 at 13:03 MST

MacBook Pro 13" Touch Bar 2019: Is this water damage? Related question: is this cable toast?

Wed, 22 Jul 2026 19:50:23 -0700

Is this water damage?

Also, is this cable bad?

Edit to add area after cleaning with IPA:

⟐ Commented July 22, 2026 at 19:50 MST

MacBook Pro 16" 2021: Horizontal screen glitches after water damage and repair

Wed, 22 Jul 2026 11:41:15 -0700

So long story short, I wiped my laptop (MBP M1 16") screen with a rag and then cleaned the keyboard in the same go. I used too much liquid apparently, as the keyboard then started producing multiple keypresses and shutdown after booting.

I brought it to a repair shop which then replaced the keyboard but after I took it home, the screen started to flicker weirdly and after 10-15 minutes, went black (not totally, had a weird glassy ghost effect). The next day, the screen did work but there are weird horizontal glitches (not black though) and an area which is kinda sepia in the screen. Using the screen eg. watching Youtube seems to aggravate it.

I took it back to the shop, unsatisfied with their lack of professionalism then went to a different shop and didn't get much out of it except that the screen needs replacing and it's gonna cost a lot (1257€).

So, does anyone have any clue what's wrong with the laptop? Or if there's some way to check what's really broken—nobody has really given me proper explanations. Running diagnostics returns ADP000 (no hardware issues). What !#^&@@ me off the most in this whole debacle was the 1st repair shop's sloppiness in diagnosing the damage before handing it back to me, causing this infuriating back-and-forth.

Here see the horizontal lines in the Finder icon.

⟐ Commented July 22, 2026 at 11:41 MST

MacBook Pro 15" Core 2 Duo Model A1211: How do I replace the CMOS battery?

Tue, 21 Jul 2026 18:32:08 -0700

My clock is not storing the correct time. I suspect it needs a CMOS battery. Where do I find this and how do I replace it?

⟐ Answered July 21, 2026 at 18:32 MST

MacBook Pro 13" Unibody Mid 2012: Fan Spin - No Boot - No Display

Tue, 21 Jul 2026 15:42:55 -0700

2012 A1278 Model on the bench.

It turns on, fan spins, but that is it nothing else happens.The sleep light is on.

I have tried, removing RAM, Swapping RAM, Without the KB connected, Without a display, different HDD / SSD, Different working HDD cable, Reset SMC, PRAM etc..... Board looks clean, no water damage evident. Owner siad it just wouldn't start anymore. It does charge the battery though.

⟐ Commented July 21, 2026 at 15:42 MST

MacBook Pro 13" Unibody Late 2011: No output on external display

Tue, 21 Jul 2026 05:08:57 -0700

Hello all, I have a Late 2011 Unibody MacBook Pro with the Intel Core i7 and 16 gigabytes of RAM. I want to connect another display externally so I can have a dual screen setup and/or use it for presentations, but I noticed that the Mini DisplayPort/Thunderbolt port doesn't seem to work correctly.

Things I have tried:
Tried multiple adapters
(two of the same Mini DisplayPort to HDMI adapters, and Mini DisplayPort to HDMI cable)
Tried macOS 10.13 High Sierra (I run the catalina patch along with the OpenCore Legacy EFI loader)
Tried macOS 11 Monterey
Tried macOS 14 Sonoma
Tried just removing the hard drive and have it display the blinking folder with question mark icon
Tried Windows 10
Tried the Display Menu application on all MacOS versions except Monterey (macOS 11)
SMC Reset
PRAM/NVRAM reset
Those two things when re-installing macOS 10.13 High Sierra.
Clean out the mini DisplayPort/Thunderbolt port, and dongles.

Observations:
macOS (all versions) detects and recognises the monitors, as in the screen flickers and recognises the brand and supported modes (within adapter limits)
Same goes to the pre-boot environment
Windows does not see the external display even after manual detection. Sometimes after reboot the integrated graphics in Windows is disabled due to a problem, re-enabling it brings back proper graphics but external monitor output is still not working or being detected.
All the adapters I've bought show the MacBook Air, not the MacBook Pro, although I've seen a review of someone using it on a 2012 Unibody MacBook Pro
A while back I had a different MacBook Pro model, still 2011 but the Early 2011 one, with the Core i5 instead of the Core i7. I was given a mini DisplayPort to VGA adapter and same symptoms, macOS and preboot environment sees it, but no display out. I was told by the person that gave the adapter to me that they use it on their 2015 MacBook Air just fine with no problems.

Is there like a common fault or difference with these Unibody MacBook Pros with how they handle that specific port and why it seems to be temperamental with cheap adapters? I haven't tried the adapters I've had since other than specific Lenovo ThinkPad laptops and MacBook Airs, I haven't had the opportunity to try them.

I want to try one of the more expensive adapters but I don't want to spend money on something that is not guaranteed to work.

Let me know if there's anything I could do.

⟐ Commented July 21, 2026 at 5:08 MST

MacBook Pro: Changed laptop battery but still says service recommended

Sun, 19 Jul 2026 15:47:55 -0700

coconutBattery and system information recognise the new battery (both say 3 cycles instead of previous 1888 cycles) but battery under system settings still says service recommended

⟐ Answer edited July 19, 2026 at 15:47 MST

MacBook Pro 15" Unibody Mid 2012: Can I replace internal DVD drive with a BLU-RAY drive?

Sun, 19 Jul 2026 12:47:09 -0700

Hi, I have a MacBook Pro 2012 15". Can I replace internal DVD drive with a BLU-RAY drive?

⟐ Commented July 19, 2026 at 12:47 MST

MacBook Pro 14" Late 2023 (M3 Pro and M3 Max): Screen having constant glitch of lines/ghost-images across the screen

Sun, 19 Jul 2026 02:09:24 -0700

I was using my Macbook and it suddenly happened. The screen definitely didn't get accidentally opened too far or too hard, but it looks a bit like something isn't plugged all the way, if that makes sense. Like the lines that form the display are disorganized and moving/flashing around. I'll include a couple pics but it's a bit hard to see. Look at the lower half of the image where you can see the folder icon leaving this weird "gradient" or "trail":

It seems subtle on the image, but in real life when its moving and flashing around it is pretty distracting...

⟐ Commented July 19, 2026 at 2:09 MST

MacBook Pro 13" Retina Display Late 2012: How can I test the display for this L2012 A1425 Retina

Sat, 18 Jul 2026 17:57:29 -0700

I have a late 2012 A1425 13" Retina here that has no sign of life. Before we start digging to why it didn't power up I would like to test the display. But without another late 2012 model at hand, is there a way to test the display, even if just to see if it had any defect such as lines, or whatever..... I only have Late 2013 models at hand & get a black screen zero.:(

MacBook Pro Retina

All Retina screen cables with hinges are compatible.

A1425 2012L 13" Retina could be tested with 13" or 15" 2013E Display. Unfortunately, 2013/13" Display has different Camera connector.
For testing 13 and 15 inch screens of the same generation are compatible
2012-E2013 are fully compatible
L2013-2014 are fully compatible
2015 is unique

I really need to know if this display is good before we attempt a repair as otherwise it is pointless to fix ...... @danj

⟐ Edited by author July 18, 2026 at 17:57 MST

MacBook Pro 14" 2021: Why does my MacBook hard crash after opening lid?

Sat, 18 Jul 2026 07:05:07 -0700

I have a M1 Macbook Pro 14" (2021) that I have been using for 4 years. For a long time, I simply used the OS it came out of the box with (macOS 12.1). It never gave any issues and I was too lazy to update it. One day I simply opened the lid of my macbook and tried to use Touch ID to open lock screen. After several attempts of trying to use Touch ID (it has a tendency to not work first time), I realized my mac froze and then a hard crash occurred (apple logo flashed).

I tried to force restart which led me to the black screen with exclamation mark. There was no trackpad haptic, power button was unresponsive, MagSafe LED did not work. Since I didn't have a secondary mac for a DFU restore, I simply kept my mac in isolation for a while and didn't touch it. 2 days later I plugged my mac in using Magsafe and the LED lit up.

After a full charge, I opened my macbook which showed how it restarted due to a problem. The logs said it was a kernel panic. After digging, i decided to update my OS to the latest version (macOS Tahoe 26.5.2). I thought it would fix every problem. However a few days later, the same thing happened. I opened the lid, spammed Touch ID for it to register, and then it simply hard crashed and I had to wait another 2 days for it to boot up again (same symptoms). This time there was no kernel log reports and my mac thinks absolutely nothing went wrong (I checked console and there was no crash logs or anything)

The only thing I found using the command
pmset -g log | grep -E "Failure|Sleep|Wake"

was:
2026-07-15 13:38:56 +0600 Assertions PID 1914(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30 id:0x0x10000856f [System: No Assertions]

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 "osservice426-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.

⟐ Commented July 18, 2026 at 7:05 MST

MacBook Pro 15" Touch Bar 2019: Battery exterior pierced upon removing stuck lid

Fri, 17 Jul 2026 19:56:10 -0700

Hello everyone,

Hope you all had a good week.

Just a quick one, do we think this is safe RE: Attached image. I asked AI but I wanted a fellow tech heads opinion. I'm also in a tight spot right now so cant exactly change it straight away.

Thank you in advance.

⟐ Answered July 17, 2026 at 19:56 MST

MacBook Pro 13" Retina Display Early 2015: Screen Polariser Issue (Solved)

Fri, 17 Jul 2026 08:37:56 -0700

The Anti-Glare or more than the AG has come away from the display in an odd way as pictured. If I use a flat edged plastic tool I can flatten it out and it sticks down for a short time only to return going completely across the screen. I initially thought it was a screen protector peeling away, so I tried lifting it away on the top corner but then under the material is just a white picture, so it must be the display itself. It feels like a plastic type of material. When the display is on you can barely notice it unless there is a black background. Would a heat gun do the job to shrink it or stick it back down permanently I don't think using a craft blade to slice it releasing the air underneath for the risk of leaving a permanent scratch as that it what seems to be forcing it to 'bubble'. The LCD is damaged for 1cm along the very bottom so it has o be used with the dock set to the edge. How to solve this one as it is still usable and would make a nice giveaway unit.?

As a footnote,Considering that in one of the pictures it shows that the coating can peel of, I could try removing it all, and replace with another as I have 2 other fully defective display assembly's that I could try to remove the part from. Trial & error maybe or a wild possibility? Now solved.

⟐ Edited by author July 17, 2026 at 8:37 MST

MacBook Pro 13" Retina Display Early 2015: Function of the rubber hinge screw covers

Thu, 16 Jul 2026 06:19:53 -0700

On A1502 & A1398 models we have this rubber cover that sticks onto both of the hinge screws. What purpose are they for as any connecting cables do not seem to touch them.

⟐ Answer accepted July 16, 2026 at 6:19 MST

MacBook Pro 13" Two Thunderbolt Ports Late 2020: Battery Dead, Hot Dongles, and Electrical Leakage from Case

Thu, 16 Jul 2026 06:10:25 -0700

Hi everyone, I have been facing this issue for about two years with my MACBOOK PRO M1 A2338

Symptoms:

Battery Dead: The laptop will not turn on unless connected directly to the power adapter. The battery is not charging.
Peripherals Overheating: USB dongles and other peripherals become extremely hot within a short time when plugged in.
Electric Shock/Leakage: I feel an electric shock (tingle) when touching the aluminum case, suggesting a grounding issue or internal short circuit.

My Question: Based on these symptoms, what components should I replace?

Is it just the battery?
Could it be the battery connector cable or the USB-C/Charging port flex cable?
Is the Logic Board (Motherboard) damaged and in need of replacement?

I am looking for suggestions on which specific parts to buy to fix this. Thank you!

⟐ Answer edited July 16, 2026 at 6:10 MST