Not: Bilgisayarın tuşları çalışıyor sadece arada bu hatayı yaptığı için sürekli kullanmıyorum.

⟐ Answer accepted Nisan 17, 2024 at 4:41 GMT-7

⟐ Edited by author Mart 25, 2021 at 16:09 GMT-7

Merhabalar. Bugün çözüme baştan macOS Catalina yükleyerek ulaştım. Bilgisayar kapalıyken alt+cmd+r tuşlarına basıp bilgisayarı açtım ve Recovery moduna girdi. Diskleri sildim ve cihaz internet üzerinden Catalina yazılımını indirip kurdu. Bilgisayardaki yavaşlık, ısınma gibi problemlerin hepsi çözüldü.

⟐ Answer deleted Aralık 21, 2020 at 16:49 GMT-7

Bu ne demek???

Bu uyarıyı aldığımda herhangi bir USB takılı değil???

⟐ Answer deleted Eylül 19, 2018 at 13:55 GMT-7

Here’s the full history:

I spilled coffee on it. I took it to a shop and they told me they couldn’t fix it. After about a week I opened it up myself and left it open to dry for another week. Now, in about week three, I started putting it back together — and to my surprise it turned on.

So it’s partially alive, but I have a few related issues I’m trying to sort out:

When I first booted it during reassembly — before screwing the trackpad bracket down — the trackpad worked and I could move the cursor and check the battery percentage. After I screwed everything down and rebooted, the cursor stopped moving and hasn’t come back.

The battery connector is plugged in and locked with its metal locking arm, so that one seems fine. The connector giving me trouble is a small board-to-board (mezzanine) connector near the battery connector — I believe it’s the keyboard/trackpad flex. It has no ribbon and no latch; the two halves just press together. When I press it down it clicks and holds for a few seconds, then pops back undone. I have not used any glue.

On power: the machine shows one fixed battery percentage that never changes, and it shuts off immediately the moment I unplug the charger. It only runs while plugged in.

What I’ve tried so far:

• Reseating that board-to-board connector multiple times

• Confirmed the battery connector is seated and locked

• Verified I haven’t damaged the battery connector’s locking arm

What I’m trying to figure out:

1. Why that board-to-board connector won’t stay mated — alignment, a bent/cracked contact from the spill, tension from the bracket/screws pulling the flex, or corrosion damage?

2. Whether the “shuts off when unplugged / stuck percentage” means the battery is dead/failed, or something related to the spill.

3. Whether tightening the trackpad down is what’s unseating the connector, and how to get it to snap and hold.

Given the coffee spill, I’m also wondering if I should be looking for corrosion on these connectors or the board.

Details:

• Model: MacBook Air M1, A2337 (EMC 3598), Late 2020

• History: coffee spill → shop declined repair → dried open ~2 weeks → reassembling in week 3, powers on

• Battery connector: seated and locked

• Problem connector: keyboard/trackpad board-to-board (mezzanine) connector, won’t stay mated

I can post close-up photos of the connectors and board on request. Any guidance appreciated.

We thought the issue was a bad SMC, We replaced the SMC, Connected the charger, Brief fan spin, no chime or boot. No water damage, clean board Technician cannot find any shorts. The issue remains even with no KB connected. We have reset & programmed the SMC with SMC tools / Unable to reset PRAM etc...... Only with SHIFT+OPT+Power I got it to boot into the system, fan at normal speeds, power button does shut it down....But the system Prefs wont load and it is dead slow. I have used 2 new keyboards shells and 2 good TP cables yet still the same, and with a fresh Monterey installed drive. Diagnostics no issues found. The KB & TP are functioning fine (Except to power up). In recovery mode the terminal sudo nvram -c command is not found. Firmware password is off. @danj @oldturkey03 What can be our issue here?

System Firmware 489.0.0.0.0 correct for Monterey.

SMC Version 2.27f2

No Audio devices are detected with 2 I/O boards, which maybe our issue? Although it did chime once before.... Charges battery OK .....I eventually have successfully clean installed a copy of Monterey on the unit but everything is still the same.... At least I thought so but it has stuck on 12 minutes remaining for quite some time now, I will have a sleep and see if it finished when I wake up.... And as expected it is stuck at under a minute.....

⟐ Edited by author Temmuz 18, 2026 at 0:36 GMT-7

⟐ Answer accepted Temmuz 17, 2026 at 20:01 GMT-7

When I click restore, it gets on the 4th step and stalls, then I get a message saying:

“The System cannot be restored on this device.

Unexpected device state 'DFU' expected

"RestoreOS (Probably forced into DFU

mode externally)“.

I have used different USBC cables and keep getting the same message.

⟐ Commented Temmuz 17, 2026 at 19:31 GMT-7

As described in the title I can only charge my MacBook Air 2020 with an old (extremely slow) USB-A to C charger, I don't exactly know when the issue started because this MacBook was gifted to me not too long ago, but I think there were some smaller issues with charging prior to this one.

If anyone has any insight, it would be strongly appreciated!

⟐ Commented Temmuz 17, 2026 at 10:57 GMT-7

Debugger message: panic

Memory ID: 0x6

OS release type: Not set yet

OS version: Not set yet

macOS version: Not set

Kernel version: Darwin Kernel Version 25.4.0: Wed Mar 4 21:00:12 PST 2026; root:xnu-12377.101.14~1/RELEASE_ARM64_T8010

KernelCache UUID: D5918C78DE487948F02EC9C28C26C76E

Kernel UUID: 8988F27B-D524-3985-B6AC-E2F100747E6F

Boot session UUID: 8877C03C-24C3-4A04-B161-5BBB08005D29

iBoot version: iBoot-13822.101.1

iBoot Stage 2 version:

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x0

x86 System State: 0x3

x86 Power State: 0x6

x86 Shutdown Cause: 0x80

x86 Previous Power Transitions: 0x70707070706

PCIeUp link state: not available

macOS kernel slide: not available

Paniclog version: 15

Kernel slide: 0x0000000022364000

Kernel text base: 0xfffffff029368000

mach_absolute_time: 0x76e2b9f

Epoch Time: sec usec

Boot : 0x00000000 0x00000000

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x00000000 0x00000000

Zone info:

Zone map: 0xffffffdc024c0000 - 0xffffffe2024c0000

. VM : 0xffffffdc024c0000 - 0xffffffdce8b24000

. RO : 0xffffffdce8b24000 - 0xffffffdd357f8000

. GEN0 : 0xffffffdd357f8000 - 0xffffffde1be5c000

. GEN1 : 0xffffffde1be5c000 - 0xffffffdf024c0000

. GEN2 : 0xffffffdf024c0000 - 0xffffffdfe8b28000

. GEN3 : 0xffffffdfe8b28000 - 0xffffffe0cf190000

. DATA : 0xffffffe0cf190000 - 0xffffffe2024c0000

Metadata: 0xffffffe2024d0000 - 0xffffffe203cd0000

Bitmaps : 0xffffffe203cd0000 - 0xffffffe203dfc000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xffffffdf026338c0 0: 0x0000000000000000 0ro: 0x0000000000000000 }

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

CORE 1: PC=0xfffffff028608218, LR=0xfffffff028608210, FP=0xffffffedb7d5be10

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

Panicked task 0xffffffdd358b1f18: 0 pages, 165 threads: pid 0: kernel_task

Panicked thread: 0xffffffdf026338c0, backtrace: 0xffffffedb7ecf190, tid: 370

lr: 0xfffffff0295a2024 fp: 0xffffffedb7ecf200

lr: 0xfffffff0296f42ac fp: 0xffffffedb7ecf270

lr: 0xfffffff0296f2fe4 fp: 0xffffffedb7ecf360

lr: 0xfffffff02955d6b8 fp: 0xffffffedb7ecf370

lr: 0xfffffff0295a210c fp: 0xffffffedb7ecf850

lr: 0xfffffff029cff458 fp: 0xffffffedb7ecf870

lr: 0xfffffff02881ee30 fp: 0xffffffedb7ecf910

lr: 0xfffffff02881ef9c fp: 0xffffffedb7ecf930

lr: 0xfffffff02881e9b0 fp: 0xffffffedb7ecf980

lr: 0xfffffff028288bb4 fp: 0xffffffedb7ecf9a0

lr: 0xfffffff028288a10 fp: 0xffffffedb7ecf9d0

lr: 0xfffffff029c34714 fp: 0xffffffedb7ecfa30

lr: 0xfffffff028289cac fp: 0xffffffedb7ecfa90

lr: 0xfffffff02866ffc0 fp: 0xffffffedb7ecfb00

lr: 0xfffffff0287fdaa0 fp: 0xffffffedb7ecfb30

lr: 0xfffffff0287fbb28 fp: 0xffffffedb7ecfb60

lr: 0xfffffff0287fb9c8 fp: 0xffffffedb7ecfba0

lr: 0xfffffff028674f40 fp: 0xffffffedb7ecfc70

lr: 0xfffffff029c0466c fp: 0xffffffedb7ecfcf0

lr: 0xfffffff029c0412c fp: 0xffffffedb7ecfe00

lr: 0xfffffff029c03128 fp: 0xffffffedb7ecfe70

lr: 0xfffffff029c06f34 fp: 0xffffffedb7ecff20

lr: 0xfffffff0295686ec fp: 0x0000000000000000

⟐ Answer edited Temmuz 14, 2026 at 8:59 GMT-7

⟐ Answered Temmuz 13, 2026 at 21:02 GMT-7

⟐ Commented Temmuz 11, 2026 at 4:01 GMT-7

⟐ Commented Temmuz 07, 2026 at 7:11 GMT-7

Spanish: La MacBook prende y después se apaga y tarde horas en prender nuevamente

The MacBook turns on and then turns off and takes hours to turn on again

⟐ Answered Temmuz 02, 2026 at 10:51 GMT-7

I have a MacBook Air M1 2020 (A2337) with a keyboard issue. The 3, E, and D keys not work. These three keys are aligned vertically on the keyboard. I want to mention that this is how I purchased the macbook with this problem. I thought I could clean each key individually and solve the problem, but it seems my idea didn't work.

What I have already checked:

• The MacBook has never had any liquid damage.
• I removed the individual keycaps and inspected the mechanisms underneath.
• The rubber domes and key mechanisms look perfectly fine.
• There are no signs of corrosion or dirt.
• I opened the laptop and inspected the inside, which is also very clean.
• I disconnected and reconnected the keyboard flex cable, but the issue remains.
• All other keys on the keyboard work normally.

Since the affected keys are in the same vertical line (3, E, D), I am wondering if this could be a keyboard matrix issue or a failed row/column circuit.

Has anyone experienced the same problem on an A2337 MacBook Air M1? Is there any repair possible without replacing the entire keyboard or top case?

Any advice or schematics would be greatly appreciated.

Thank you!

⟐ Commented Temmuz 01, 2026 at 15:11 GMT-7

⟐ Commented Haziran 30, 2026 at 15:12 GMT-7

⟐ Answer edited Haziran 30, 2026 at 14:30 GMT-7

My Macbook Air has been displaying intense display glitching. The screen becomes covered with distorted coloured lines when I position it at most angles, however, at some very specific angles the glitching resolves entirely.

I've done some digging and discovered that I'll likely have to either replace the display flex cable or the screen assembly.

I'm inclined to think that the issue lies in the display cable, as the screen itself works flawlessly at specific angles, as I've mentioned. Dually, an A2337 display cable is much cheaper and easier to source than a new display assembly.

However, I'd really appreciate some professional advice.
Ask me any questions which may clarify things for you!

⟐ Commented Haziran 29, 2026 at 23:45 GMT-7