Archive. This is an archive of the Apple Support Community. Discussions are being restored and soon you will be able to read and post here again.

MacBook Air M2 2022 won't turn on after crashing during backup


I was doing a TM backup with the Mac plugged in.

All of a sudden it crashed, screen went black and the MagSafe adapter's green light went off.


I checked that electricity was on

I held the power key for 10 sec, then waited 5 and hit power key with no luck


This was plugged in all day.


Appreciate any help

Thanks

3 replies

MacBook Air M2 (2022) – Won't Turn On After Crashing During a Time Machine Backup


Since your MacBook Air suddenly shut down during a Time Machine backup, the screen went black, and the MagSafe indicator went off at the same time, I would investigate the power and charging system first.


You have already confirmed that the electrical supply is working and attempted a 10-second power-button reset, so there is no need to repeat those checks unnecessarily.


Please try the following steps in order:


1. Disconnect all accessories


  • Disconnect the MagSafe charger and all peripherals, including the Time Machine backup drive, USB hubs and external devices.


  • Leave everything disconnected for approximately 60 seconds.


  • Reconnect MagSafe and check whether its indicator illuminates.


2. Check the MagSafe connection


  • Inspect the MagSafe connector and charging port for debris or damage.


  • Make sure the connector is seated properly.


  • Remember that amber indicates charging, green indicates a fully charged battery, and no light may indicate a charging or hardware problem.


  • If possible, test with another compatible Apple power adapter and MagSafe cable.


Apple's guide: https://support.apple.com/en-us/102372


3. Try charging through USB-C


Your M2 MacBook Air can also charge through either USB-C/Thunderbolt port.


  • Disconnect MagSafe.


  • Connect a compatible USB-C Power Delivery charger.


  • Leave it connected for 20–30 minutes.


  • Try starting the Mac normally.


This helps determine whether the problem is isolated to MagSafe or involves the Mac's internal power system.


4. Try another power-button startup


  • Disconnect unnecessary peripherals.


  • Press and hold the Touch ID/power button for 10 seconds.


  • Release it, wait a few seconds, then press and release it normally.


  • Watch for any signs of activity, including the Apple logo, screen illumination or trackpad feedback.


5. Attempt macOS Recovery


  • If the Mac shows signs of life:


  • Make sure it is shut down.


  • Press and continue holding the power button until 'Loading startup options' appears.


  • Select Options, then Continue.


If Recovery loads, open Disk Utility and check the internal startup disk.


Do not erase or reformat the drive.


Apple's instructions:


https://support.apple.com/en-us/102518


6. If the Mac remains completely unresponsive


If neither MagSafe nor USB-C charging produces any response, the problem could involve the battery, charging circuitry, logic board or firmware.


At this stage, Apple or an Apple Authorized Service Provider should inspect the Mac.


A firmware Revive using another Mac may also be necessary. A Revive attempts to repair firmware without erasing data, whereas a Restore erases the Mac. Always request a Revive first.


Apple's instructions:


https://support.apple.com/en-us/108900


Important: Since the crash occurred during a Time Machine backup, avoid erasing, restoring or reinstalling macOS until the internal data and backup status have been assessed. Preserving your existing data should be the priority.


A few questions to help narrow this down:


1 When you reconnect MagSafe, does the indicator remain completely dark, or does it briefly illuminate and then go off?


2 Does the Mac show absolutely no signs of life, including trackpad feedback or screen illumination?


3 Have you tried charging through USB-C, or only through MagSafe?


Your answers will help determine whether this is a charging-related problem, a power-management failure or a more serious hardware or firmware issue.


Out for repair

mrokloricred37 wrote:
Out for repair

Ouch