iFixit - Active Questions With Device "Mac Laptop"

MacBook Pro 15" Retina Display Late 2013: I replaced the battery of my MacBook Pro, but the error 'Service recom

Fri, 17 Dec 2021 03:46:53 -0700

English

Hello. I am John Schindler.

I replaced the battery of my MacBook Pro today, but a 'service recommended' message appears.

In the Coconut Battery program, the battery life is 100% and there are no problems.

Is there any way to solve the symptom of this problem?

Korean

안녕하세요. 저는 존쉰들러입니다.

오늘 맥북프로 배터리를 자가교체를 했지만, '서비스 권장됨' 안내표시가 뜹니다.

코코넛 배터리 프로그램에서 배터리 수명이 100%이고 별 문제가 없어보입니다.

이 문제의 현상을 해결할 수 있는 방법이 있습니까?

image

MacBook Air 13" Retina Display 2020: MacBook Air 13" Dropped - No power / DFU restore failure

Tue, 18 Aug 2026 14:04:10 -0700

I'm troubleshooting a MacBook Air 2020 A2179, logic board 820-? that does not power on.

Symptoms:

Mac does absolutely nothing when pressing the power button.
Tried both USB-C ports.
Internal white LED stays solidly on when the charger is connected.
Battery has been tested both connected and disconnected.
The Mac can be put into DFU mode and is detected by Apple Configurator on another Mac.
Both Revive and Restore fail at step 4/4, around 50%, with:

gave up waiting for device transition from dfu state to dfu state

and/or:

Probably forced into DFU mode externally

This happens with both Revive and Restore.
Cable might be not good, I'm going to retry with an official Apple cable suited for a Revive/Restore purpose soon.
The Mac have been dropped, so physical motherboard damage is possible.

With the Mac powered off, charger connected, battery connected, I measured:

PPBUS_G3H = 12.63V
PP3V3_G3H = 3.30V
PP5V_G3S = 5.11V
PP1V8_G3S = 1.80V
PP0V9_SSD = 0.90V

PP1V8_SSD = 1.80v

PP3v3_S5 to ground = 780 ohms

F3000 & F3001 = 19.94V on each side of the components

C7050 & C7056 = 12.63V

Main rails appears to be good, so I'm wondering what could have gone wrong.

If anyone has an idea,

Best regards,

Another official Apple cable did not fix the problem

Could it be the SSD?

⟐ Edited by author 8월 18, 2026 at 14:04 GMT-7

Macbook Pro 14" 2023: Battery Charge limit not working after battery replacement?

Tue, 18 Aug 2026 13:53:07 -0700

I replaced my MacBook battery with what I believe was a replacement part from iFixit. A few days later, I noticed the battery always charges to 100%, even though I set an 80% limit in macOS. I tried several terminal commands to reset to default settings, but had no luck. Now I’m worried it might be a hardware problem. Is this a common issue?

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 8월 18, 2026 at 13:53 GMT-7

Macbook Air M2 2022: Do I need to replace a screen assembly?

Tue, 18 Aug 2026 08:34:33 -0700

Hi everyone,

I'm looking for some advice or insights regarding a frustrating issue with my MacBook Air M2. I suspect it might be related to the T-CON board, lid angle sensor (ALS), or a loose display cable, but I wanted to share the full story and my troubleshooting steps along with a video clip showing the exact behavior.

Here is the timeline of what happened:

1. The Incident

Day 1 (Right before leaving): Before I even left for class, I was using my MacBook normally, watching YouTube. Suddenly, the mouse cursor froze and wouldn't move.

When I shook the mouse back and forth—using the macOS feature that temporarily enlarges the cursor so you can find it—the cursor did enlarge, showing the system wasn't totally dead. However, when I stopped shaking, the cursor stayed stuck in place and wouldn't respond. Interestingly, if I dragged the frozen cursor down to the Dock, the Dock icons still popped up and reacted as expected, even though the pointer itself wouldn't navigate normally.

Day 1: I brought my MacBook to class. It was packed inside a protective laptop bag, and I placed it under the seat of my motorcycle.

When I arrived at class, I opened the lid, but the screen was completely blank. Because the room was extremely bright, I couldn't see the keyboard backlight or any faint glow from the display, so I assumed the battery had run out.

Since I didn't bring my own charger, I tried using a friend’s iPad charging cable. However, the cable was too thin and didn't provide enough wattage, so it didn't charge.

2. Initial Troubleshooting

When I got back to my room and plugged it in properly, nothing happened to the built-in display.

However, the keyboard backlight turned on, and the trackpad responded normally (haptic feedback worked), meaning the system was actually running.

Later, I tried connecting it to an external monitor via USB-C/HDMI, and it worked normally. While using the external display, I updated macOS. Suddenly, during or after the update, the built-in laptop screen came back to life and worked normally again.

3. The Lid Angle & Sleep Issue

After that, I noticed a strange pattern: if I open the lid past roughly 90 degrees, the screen goes black.

As shown in the attached video, I have to lower the angle down to about 45 degrees for the display to turn on properly.

Crucially, I must not let the laptop go to sleep. If it goes to sleep, it reverts right back to the black-screen state.

When the screen finally wakes up or recovers, a Kernel Panic report pops up.

4. Apple Store Visit

I made a Genius Bar booking at the Apple Store. The technician told me that the display assembly might need to be completely replaced, costing around 26,000 THB.

Given the high cost, I decided not to repair it through Apple right away and took it back home.

5. Current State & Workarounds

For the first 2–3 days after coming back, it worked fine (as long as I managed the lid angle).

But now, as seen in the video, if I test putting it to sleep (e.g., pressing the Touch ID power button once, then pressing ESC), the screen shuts off with an abnormal flickering flash, and it gets stuck in that broken loop.

Right now, the built-in display is completely black again. My current workaround to revive it is purely a game of chance: I have to completely drain the battery (sometimes by using the MacBook's ports to charge an iPhone) until the battery dies completely, hoping it resets the SMC/display state upon reboot.

Has anyone experienced a similar issue with their M2 MacBook Air? Is this definitely a hardware failure with the physical display cable/T-CON/lid angle sensor, or could it be software-related? Any advice or workaround suggestions would be greatly appreciated.

(Please check the attached video to see the lid angle behavior and the flickering screen issue.)

Thank you so much!

⟐ Commented 8월 18, 2026 at 8:34 GMT-7

MacBook Pro 13" Retina Display Early 2015: Screen flickering only on MacOS

Tue, 18 Aug 2026 07:56:12 -0700

Hi, I have a 2015 13 inch Retina MacBook Pro that has a display issue, when booted to macOS (I tried several macOS versions), the display just flickers continuously. Sometimes it's just flickering, other times the display would show corruptions, but:
- The display does not flicker in recovery mode, or in Safe Boot
- The display does not flicker in any other OS like Windows 10, Windows 11, and Ubuntu Linux
- The display stops flickering on macOS the moment I connect to an external display
- The flickering does not change/improve when adjusting the lid angle

In the other OS scenarios I just described or when I use macOS with an external display, the display works PERFECTLY. No flickering, no hanging, brightness control works, it's just in macOS proper it starts acting broken, even went as far as to use it daily on Windows 11 and yeah, the display works perfectly.

Things that I have tried:
- PRAM/NVRAM reset
- SMC reset
- Cleaning the connector on both the screen and motherboard
- Different power adapter
- Different macOS versions (tried El Capitan, Catalina, and Monterey)

Note: the device has no battery. It runs from adapter only.

⟐ Commented 8월 18, 2026 at 7:56 GMT-7

MacBook Air 13" Late 2020: Touch ID pairing - Self Service Repair

Tue, 18 Aug 2026 01:41:35 -0700

I am a little confused by the Self-Service Repairs from Apple, and what is and isn't possible.

When I attach a second hand screen (genuine Apple) it gives me the option to finish the repair and it calibrates accordingly.

When I try a second hand Touch ID (genuine Apple) it fails to recognise it as being a genuine part.

My questions are - is it possible to calibrate a Touch ID now through Apple's program? And if so, would I need to buy a new button through the Self-Service Repair from Apple?

⟐ Answered 8월 18, 2026 at 1:41 GMT-7

MacBook Pro 13" Unibody Mid 2012: Changing logic board to change graphic card

Mon, 17 Aug 2026 23:04:59 -0700

Hey guys !

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 8월 17, 2026 at 23:04 GMT-7

PowerBook 5300c: How do I turn it on?

Sun, 16 Aug 2026 11:14:48 -0700

This is my "old computer" ('96). I want to recycle it, after checking to see what is on it. I don't have the manual, nor do I see a "power on" button.

⟐ Commented 8월 16, 2026 at 11:14 GMT-7

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

Sun, 16 Aug 2026 06:36:32 -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.

⟐ Answered 8월 16, 2026 at 6:36 GMT-7

MacBook Pro 13" Two Thunderbolt Ports 2020: My touch bar is unresponsive about half the time

Sun, 16 Aug 2026 06:24:57 -0700

I've never had a good experience with the Touch Bar on my M1 2020 Pro, but lately the things I have to use it for (volume and display brightness settings) work around half the time when I touch them, making it extremely annoying to use.

Has anyone had any experience fixing or replacing this part?

MacBook Pro 16" 2019: Touch ID does not work after battery replacement

Sun, 16 Aug 2026 04:28:56 -0700

A few days ago I have replaced the battery in my Macbook following the guide on ifixit, which involved taking out the logic board.

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 8월 16, 2026 at 4:28 GMT-7

MacBook Pro 16" 2019: MacBook Pro A2141 black screen and unresponsive keyboard/trackpad after upgrade

Sat, 15 Aug 2026 21:01:49 -0700

My MacBook Pro 16" 2019 (Model A2141) experienced a black screen with backlight only, along with completely unresponsive internal keyboard and trackpad, immediately following a software/firmware upgrade. The device is lightly used with zero liquid damage.

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 8월 15, 2026 at 21:01 GMT-7

MacBook Air 13" Retina Display 2020: Caps Lock Key Came Off

Sat, 15 Aug 2026 18:34:21 -0700

My caps lock key came off, and I can't get it back on. Everytime I do, it stays stuck down and wont come back up. I'm wondering how to properly reinsert the metal bracket and keycap?

⟐ Commented 8월 15, 2026 at 18:34 GMT-7

Retina MacBook 2015: Leftover part from USB-C fixing - bracket?

Sat, 15 Aug 2026 11:38:26 -0700

Hi, I replaced the USB-C port successfully on Retina MacBook 2015.

Around step 25-30 I noticed a small part loose on the tray that looks like this:

Anybody know what part it is? Cannot find it anywhere in the guide.

The guide used was:

Retina MacBook 2015 USB-C Port Replacement

⟐ Commented 8월 15, 2026 at 11:38 GMT-7

MacBook Pro 15" Touch Bar 2017: Can I remove MDM after I already completed a fresh install?

Fri, 14 Aug 2026 18:33:05 -0700

A friend from work gave me a laptop from our old company that nobody was using and it was reformatted so it was a clean Mac. He gave it to me while we both worked there but have both left since. I've been using it for about 4 years and I decided to replace the logic board for a larger SSD.

Before replacing the old logic board, I erased the machine and attempted installing macOS on it to make sure my time machine backup worked correctly. But as I was reinstalling, the MDM for my company showed up. This brought up a some questions:

Is MDM tied to the logic board or will replacing it still lock me out?
Has MDM been enabled on my laptop the entire time I've used it and I just didn't know? I haven't heard from the company so do they just not care?
Will MDM be linked to my Time machine backup? If I restore from my time machine backup on the new logic board, will my old company be able to track it? Is a fresh install a better idea?
Is it possible to bypass MDM so I can reuse the old logic board?

I've tried booting off a flash drive to avoid connecting the the MDM servers in hopes of bypassing the need for an internet connection, but I get an error saying a critical update is needed in order for me to complete the install

I am also unable to restore my time machine backup for some reason. Any reason MDM would cause issues? I loaded the time machine backup but it keeps getting stuck at page with the Apple logo with the loading bar. All troubleshooting leads back to a fresh install which I can't get past because of MDM. Hopefully there is a workaround.

Would appreciate any insight/advice.

Thanks!

⟐ Commented 8월 14, 2026 at 18:33 GMT-7

MacBook Air 13" Early 2015: Can I upgrade the SSD in a 2014 or 2015 MacBook Air?

Fri, 14 Aug 2026 10:26:52 -0700

Hi,

I'm considering buying a brand new 2015 or 2014 13" MacBook Air. I would prefer to upgrade the SSD myself.

1. Will any standard "M.2" (form factor) SSD module fit the socket connector on this logic board?

2. Or, is the socket connector a totally proprietary connection on on these 2014/2015 MacBook Airs?

I'm planning on purchasing the following "M.2" SSD:

Samsung XP941 Series [Generation 2 PCIe "4 Lanes"] 512GB M.2 SSD.

http://www.newegg.com/Product/Product.as...

From iFixit's teardown of the 2015 MacBook Air it seems like it should be easy to simply pop out the factory "M.2" style SSD and swap in a new "M.2" style SSD module.

Please let me know if this is true.

Thanks!

⟐ Answer accepted 8월 14, 2026 at 10:26 GMT-7

MacBook Air 11" Mid 2012: Backlight Not Working...Should I replace Display or Fuse?

Fri, 14 Aug 2026 00:21:25 -0700

My brother has a Mid-2012 Macbook Air 11". He was recently on a flight and was trying to place his bag (which held the Macbook Air) into the cabin compartment. Unfortunately, he lost his grip and the bag feel onto the ground.

A couple of hours later when he went to turn the Macbook and that's where he first noticed the problem with the backlight. He says that when he first turned it on, the screen was very dim, but he was able to make out a dialog box on MacOS. Then he said it flickered and went completely dim.

When he gave it to me, the screen was completely dark. However, by shinning a light through the Apple logo, I was able to see the MacOS desktop and confirm it was the backlight that was not-functioning and not the LCD. I connected his laptop to an external monitor and was able to confirm that everything else was working fine.

At that point, my initial instinct was to just replace the display. I found a couple of eBay listings of Macbook Air displays that came with the full display housing. However, in the course of my research, I've read a lot of support threads identifying the Fuse on the mainboard of the Mac as the reason why backlights on the MBA might fail.

Here's a picture of the (what I think is the) fuse on the mainboard:

My Question: How do I know which is the right solution? How do I know if the Fuse is blown or not? Will buying the display off eBay solve the problem regardless? Or will I end up wasting money if it turns out to be a problem with the Fuse?

⟐ Answered 8월 14, 2026 at 0:21 GMT-7

MacBook Pro 13" Touch Bar 2019: Pull tab adhesive on battery

Wed, 12 Aug 2026 15:28:18 -0700

Hi,

Does anyone know what the battery pull-tab adhesives are inside macbook pro 2019 and where I could purchase one?

Long story short, (I naively thought) my only option was to open and check the battery of my 5 month old mbp that stopped turning on (as I moved country and couldn't avail of my warranty at home) and I was advised I would need to pay $700 to fix in the country I'm currently residing.

During this very short process of me testing the battery inside, the adhesiveness of the black tab over the battery got weaker and so no longer sticks. I know opening the mac 'voids warranty', but I now can get it back to my home country (after a lot of effort) to send back to the reseller I purchased it from- as I want to try avail of said warranty. The only problem is I'm worried about that little black tab and how it is no longer sticking, giving away the fact I opened the back up.

Does anyone know if this is a major cause for concern re warranty and if so, how can I fix it:(

Big regrets now obviously for opening it at all but it felt like no other option at the time. Hindsight..

(On image attached, mine was stuck to this black cover when I got it from the reseller, so only the tab part I need to replace)

Thanks
Steven

⟐ Commented 8월 12, 2026 at 15:28 GMT-7

MacBook Air 13" Early 2015: MacBook Air Power Problems

Wed, 12 Aug 2026 11:17:23 -0700

About Me - I am a relatively new, 19 year old Senior Technician at a store that repairs primarily apple products. I'm starting out as the senior tech here with almost no previous experience except my interest to go into computer science later this year when I start my college classes. To say in the very least, I'm still learning, so please be patient if it takes me a little time to catch on to all that you might try to help me with. I Love learning these things and thought this would be a good place to start because i look at the forums often for help, this is just my first post thus far. I'm always looking for more ways to learn and adapt my skills in this industry. I love my job and can't wait to learn more about the things I'm doing! Thank you very much for reading or helping me with diagnosing the Issue below. - Cole W.

Today's problem: Diagnostics I received a 2015 13" Macbook Air and the customers problem was that the computer randomly shut off while his daughter was watching a youtube video and then it would not power back on after being plugged in.

They attempted to fix it themselves just by those steps i.e. (unplugging it and discharging and then plugging it in again to see if it powers on.

So far I have tried unplugging the battery from the logic board and powering on to see if the battery was the problem at hand. It still didn't power on. So my only thought is the IO port is bad and that needs replacing, I came here to see if anyone thinks that would be my best next step or if any of you had any advice for me on this project.

A friend of mine who does board repairs/ micro soldering suggested it might be the smc chip has lost its touch.

⟐ Commented 8월 12, 2026 at 11:17 GMT-7

MacBook Pro 13" Unibody: Not charging iFixit battery, I plug it in, green led and nothing.

Mon, 10 Aug 2026 14:57:01 -0700

The SMC, PRAM, and NVRAM have been reset, I used it on battery until it drained to zero, and now it doesnt detect the battery at all. I plug it in, green LED, flashing front indicator, and nothing.

⟐ Answered 8월 10, 2026 at 14:57 GMT-7