macOS 11.3 bricked my M1 Air

[xk991]

Updating to macOS 11.3 has bricked my M1 MacBook Air, it continually reboots and only gets as far as showing the Apple logo. Apple Configurator is unable to revive or restore, failing with "Failed to restore device in recovery mode, libusbrestore error:21 [com.apple.MobileDevice.MobileRestore – 0x15 (21)]". Has anyone else had this issue?

I had to revive the firmware before applying the 11.2 update as well. Firmware or hardware issue?

 

[Apple_Robert]

How many times did you try using the Configurator 2 app route to restore? If more than once, did it give the same error every time?

 

[xk991]

How many times did you try using the Configurator 2 app route to restore? If more than once, did it give the same error every time?

Yup same error every time, probably > 5-6 tries now.

Also should note that I can't get to the boot options screen either, it shows "Loading startup options..." and then reboots.

 

[Apple_Robert]

I think you got a corrupt software problem that is going to require sending it to Apple.

Edited to add: When you tried to get into recovery, did it ask you for your password? If so, I take it you have FileVault enabled?

Edited to add: Log into appleID.apple.com and see if your M1 is listed. If so, try deleting it and try the Configurator again.

I have run into the SSD not showing before and I am trying to remember how I got it to show again. I didn't have the boot loop problem you are experiencing. That enabled me to access Terminal and use the resetpassword command. I then rebooted, accessed disk utility in recovery, and deleted the Apple SSD with numbers in the name drive and that brought back the SSD showing in options again.

 

[xk991]

I think you got a corrupt software problem that is going to require sending it to Apple.

Edited to add: When you tried to get into recovery, did it ask you for your password? If so, I take it you have FileVault enabled?

Yes I do have FileVault enabled but it doesn't ask for my password, just reboots.

 

[Apple_Robert]

Yes I do have FileVault enabled but it doesn't ask for my password, just reboots.

So, you can't access Terminal or Disk Utility in Recovery? If you can't, I think you are going have to send your Mac to Apple. If you can access but don't see your drive listed, see my revived post you responded to.

 

[xk991]

So, you can't access Terminal or Disk Utility in Recovery? If you can't, I think you are going have to send your Mac to Apple. If you can access but don't see your drive listed, see my revived post you responded to.

Yeah can't get into recovery at all, shows "Loading startup options..." and then reboots.

Looks like a logic board replacement issue. Super inconvenient.

 

[Apple_Robert]

Yeah can't get into recovery at all, shows "Loading startup options..." and then reboots.

Looks like a logic board replacement issue. Super inconvenient.

I think, for whatever reason, you have a bad software problem that Apple will have to sort. I may be wrong but, it sounds like your old credentials are still being seen and Configurator was unable to clear it.

Before calling Apple, try removing the M1 from your devices on AppleID.apple.com and try Config one last time.

Sorry I couldn't be of any real help.

 

[JLH81]

Sounds like corrupt software to me. I would take it to Apple.

 

[MBAir2010]

cant you reinstall a time machine or use safe mode on these new M1 macbooks?
also Apple_Robert dedication and enthusiasm to these M1 MacBooks is outstanding, with expert advice!

 

[Apple_Robert]

cant you reinstall a time machine or use safe mode on these new M1 macbooks?
also Apple_Robert dedication and enthusiasm to these M1 MacBooks is outstanding, with expert advice!

With Big Sur, you have to install the OS before you use Migration Assistant to restore from a TM backup. In order to access safe mode on the M1 (with computer off, hold the power button until the system says loading options, Once you see your SSD, select the disk and then press the shift key. That will start safe mode), you have to be able to see your SSD listed under Options when you have done a cold boot holding down the power button etc.

 

[xk991]

I think, for whatever reason, you have a bad software problem that Apple will have to sort. I may be wrong but, it sounds like your old credentials are still being seen and Configurator was unable to clear it.

Before calling Apple, try removing the M1 from your devices on AppleID.apple.com and try Config one last time.

Sorry I couldn't be of any real help.

Thank you for helping! I tried Configurator after removing the device from my Apple account, but same result.

Spent hours on chat & phone with Apple, now waiting for an engineer to look into it and expecting a call back tomorrow.

 

[Pummers]

Thank you for helping! I tried Configurator after removing the device from my Apple account, but same result.

Spent hours on chat & phone with Apple, now waiting for an engineer to look into it and expecting a call back tomorrow.

Have you tried this?

Exclamation at startup on M1 Macbook Air - Apple Community

discussions.apple.com

1st comment on this page seems to corroborate a specific order of restoring is what is causing the error.

Restore macOS Firmware on an Apple Silicon M1 Mac + Boot to DFU Mode

Need to install macOS on an Apple Silicon Mac? I will show you how to boot into Boot to DFU Mode + Use Apple Configurator 2 to restore macOS!

mrmacintosh.com

 

[easycure1974]

Updating to macOS 11.3 has bricked my M1 MacBook Air, it continually reboots and only gets as far as showing the Apple logo. Apple Configurator is unable to revive or restore, failing with "Failed to restore device in recovery mode, libusbrestore error:21 [com.apple.MobileDevice.MobileRestore – 0x15 (21)]". Has anyone else had this issue?

I had to revive the firmware before applying the 11.2 update as well. Firmware or hardware issue?

View attachment 1768376

This might be a long shot by I got the same error trying to restore my M1 Pro. I used an Anker cable and not an Apple original connected to my iMac and the M1. It started restoring but when it thought it was going ok it always stopped with the same message as you got. Then I found my apple original cable and it worked at once. So if you are using a 3rd party cable it could be the culprit. And be sure to use the correct TB port on the M1, I don’t think it is working on both the ports

 

[xk991]

Have you tried this?

Exclamation at startup on M1 Macbook Air - Apple Community

discussions.apple.com

1st comment on this page seems to corroborate a specific order of restoring is what is causing the error.

Restore macOS Firmware on an Apple Silicon M1 Mac + Boot to DFU Mode

Need to install macOS on an Apple Silicon Mac? I will show you how to boot into Boot to DFU Mode + Use Apple Configurator 2 to restore macOS!

mrmacintosh.com

Thanks for the comment! This seems to be a different issue where the MacBook boots to an exclamation point saying it needs a firmware restore. Sounds like hitting the DFU key sequence then works but I'm getting a reboot loop not a warning.

 

[xk991]

This might be a long shot by I got the same error trying to restore my M1 Pro. I used an Anke cable and not an Apple original connected to my iMac and the M1. It started restoring but when it thought it was going ok it always stopped with the same message as you got. Then I found my apple original cable and it worked at once. So if you are using a 3rd party cable it could be the culprit. And be sure to use the correct TB port on the M1, I don’t think it is working on both the ports

Thanks! I had actually been using Apple's TB3 Pro cable but the same thing happens with a normal Apple USB-C cable too.

 

[Mike Boreham]

You could try booting from a USB installer. Use DU to completely erase the internal drive (normally a very bad thing to do, and forcing the use of Configurator) but in your case it might prepare the internal drive such that Configurator could work.

At this stage I don't think you have anything to lose by trying this.

EDIT you would have to create the USB installer on another Mac if you dont have one, but you can do this on an Intel Mac.

 

[Fishrrman]

OP:

Do you have a brick-n-mortar Apple Store anywhere near?
If so, why not just take it to them and let them have a look at it?

This is one of those issues where "it's still under warranty... let THEM fix it"...

 

[jdb8167]

You could try booting from a USB installer. Use DU to completely erase the internal drive (normally a very bad thing to do, and forcing the use of Configurator) but in your case it might prepare the internal drive such that Configurator could work.

At this stage I don't think you have anything to lose by trying this.

EDIT you would have to create the USB installer on another Mac if you dont have one, but you can do this on an Intel Mac.

There is also the second recovery partition. I think you reach it by a quick double press and hold. If the problem is that the first recovery partition is corrupted using the second might work.

 

[Mike Boreham]

There is also the second recovery partition. I think you reach it by a quick double press and hold. If the problem is that the first recovery partition is corrupted using the second might work.

Yes, my understanding is that this second recovery partition is what Apple call the "1 True Recovery" or 1TR according this article by Howard Oakley. M1 Macs cannot boot without this which is in the Recovery Container on the internal SSD.
Apple Configurator restores this in the event that the internal drive has been completely erased or corrupted. Since the OP has tried and failed with the Configurator my suggestion was to completely erase the internal again in the hope that it would enable the Configurator to work.
I haven't heard of the quick double press and hold option, is that documented anywhere?

 

[jdb8167]

Yes, my understanding is that this second recovery partition is what Apple call the "1 True Recovery" or 1TR according this article by Howard Oakley. M1 Macs cannot boot without this which is in the Recovery Container on the internal SSD.
Apple Configurator restores this in the event that the internal drive has been completely erased or corrupted. Since the OP has tried and failed with the Configurator my suggestion was to completely erase the internal again in the hope that it would enable the Configurator to work.
I haven't heard of the quick double press and hold option, is that documented anywhere?

I don’t know. Maybe it was mentioned by Oakley. I’m away from my computer right now but I’ll try it later.

The whole boot process on the M1 Macs is too complicated. I can’t keep track of it.

 

[jdb8167]

Yes, my understanding is that this second recovery partition is what Apple call the "1 True Recovery" or 1TR according this article by Howard Oakley. M1 Macs cannot boot without this which is in the Recovery Container on the internal SSD.
Apple Configurator restores this in the event that the internal drive has been completely erased or corrupted. Since the OP has tried and failed with the Configurator my suggestion was to completely erase the internal again in the hope that it would enable the Configurator to work.
I haven't heard of the quick double press and hold option, is that documented anywhere?

It is documented. On page 29 of this Apple security guide PDF.

 

[Apple_Robert]

I see my fellow M1 nerds have come with minds ready to help solve the problem. Kudos.

 

[Mike Boreham]

It is documented. On page 29 of this Apple security guide PDF.

Very interesting! Thanks. This is the relevant bit:

This doesn't seem to be at all well known. I don't understand why not. The way it is described does not sound like the same "1TR" that Howard Oakley mentioned.

 

[Mike Boreham]

Very interesting! Thanks. This is the relevant bit:

View attachment 1768697

This doesn't seem to be at all well known. I don't understand why not. The way it is described does not sound like the same "1TR" that Howard Oakley mentioned.

I just tried this and it worked! I know I was in Fallback Recovery, not regular Recovery, because when I tried to change Security Settings I got this: