M1 Macbook Air Bricked? - Firmware Revive

[seebul]

Hi guys,

I have a new M1 Air, I used migration assistant to transfer old data from MacBook. After 6 hours migration assistant still said '0 Files Transferred'. So I cancelled the transfer, the new MacBook Air screen when black & wouldn't respond, so I turned it off via the power button.

Guess what, it now shows the exclamation mark on boot. Holding the power button gives no other options (recovery etc). So I've been following this guide https://support.apple.com/en-gb/guide/apple-configurator-2/apdd5f3c75ad/mac to 'revive' the firmware on the mac using an older one.

However, I get 'error 53' every time on Apple Configurator 2, has anyone done this successfully yet? Apple Support are clueless, I'm still waiting on a call back about it. I've attached a screenshot of the error I'm getting below.

 

[Quackers]

That's really unfortunate for you.
Do you happen to know which version of Big Sur was in use?
It could be
11.0
11.0.1
11.1

Error 53 became an unintended problem on iPhones some time ago and it involved the secure enclave on the chip.
Apple apologised and issued a software update.
I'm wondering if your system was using Big Sur 11.0 because that had problems originally with recovery and ultimately could lead to needing to take it to an Apple store to be fixed.
Apple issued Big Sur 11.0.1 to stop that happening.

 

[Saturn007]

Call Apple support! That's what they are there for!

 

[Apple_Robert]

Call Apple support! That's what they are there for!

He did contact Apple support.

 

[Bea220]

Oh man... is that what a bricked machine looks like? I had this error message and thought I bricked mine while I was trying to wipe my info from it to return it. The Apple rep put me on hold and said it was okay to return as it was. He was going to walk me through the long process of restoring it and I was like... um, I'm returning this laptop can I just send it back like this? Got the all clear and off it went to FedEx.

EDIT: Good luck with yours, OP.

 

[Apple_Robert]

Oh man... is that what a bricked machine looks like? I had this error message and thought I bricked mine while I was trying to wipe my info from it to return it. The Apple rep put me on hold and said it was okay to return as it was. He was going to walk me through the long process of restoring it and I was like... um, I'm returning this laptop can I just send it back like this? Got the all clear and off it went to FedEx.

EDIT: Good luck with yours, OP.

How did you go about trying to restore your M1 to factory settings? It can't be done like you can with the older Macs.

 

[Bea220]

How did you go about trying to restore your M1 to factory settings? It can't be done like you can with the older Macs.

I'm not going to lie to you, Robert. I had NO idea what I was doing (I'm not so tech savvy) so I just found this article and went off of it... https://www.macrumors.com/how-to/reinstall-macos-m1-apple-silicon-macs/

Obviously I did it wrong or not in the right order. I erased my info and then painted myself into a corner. So yeah, next laptop I buy is not going back to Apple. LOL.

 

[Apple_Robert]

I'm not going to lie to you, Robert. I had NO idea what I was doing (I'm not so tech savvy) so I just found this article and went off of it... https://www.macrumors.com/how-to/reinstall-macos-m1-apple-silicon-macs/

Obviously I did it wrong or not in the right order. I erased my info and then painted myself into a corner. So yeah, next laptop I buy is not going back to Apple. LOL.

Do you remember if you enabled FileVault when you first set up the Mac?

A woman promising not to ever lie to me. I need to print that out and save it for posterity.

 

[Bea220]

Do you remember if you enabled FileVault when you first set up the Mac?

A woman promising not to ever lie to me. I need to print that out and save it for posterity.

Ha! No, I don't recall enabling FileVault.... Ugh but I got the laptop in mid Nov so I'm not 100% certain... though I'm almost sure I didn't. My age is showing more often these days and I've never had a particularly good memory to begin with. SIGH.

 

[Apple_Robert]

Ha! No, I don't recall enabling FileVault.... Ugh but I got the laptop in mid Nov so I'm not 100% certain... though I'm almost sure I didn't. My age is showing more often these days and I've never had a particularly good memory to begin with. SIGH.

Look at it this way... When you get your 14" M1, you will be just a little more prepared after this experience. Hopefully, if you do run into a possible problem with the M1, you will ask in the forum.

Don't start throwing out the age factor as a means to divert answering questions with specificity. I have seen that ploy used many times by the female gender. I don't recall is suddenly used as a means to escape my newly printed out " I won't lie to you, Robert."

 

[seebul]

That's really unfortunate for you.
Do you happen to know which version of Big Sur was in use?
It could be
11.0
11.0.1
11.1

Error 53 became an unintended problem on iPhones some time ago and it involved the secure enclave on the chip.
Apple apologised and issued a software update.
I'm wondering if your system was using Big Sur 11.0 because that had problems originally with recovery and ultimately could lead to needing to take it to an Apple store to be fixed.
Apple issued Big Sur 11.0.1 to stop that happening.

Thanks, for all the replies guys - I'm using Big Sur 11.1. From what I could find online the Error 53 was related to iPhone & iPads as you say. I assume the M1 Macs' now use very similar boot processes to iOS devices.

I eventually got through to a 'Senior' tech at Apple based in Portugal, he was really helpful & told me not to follow the Apple support guide to 'revive' the Firmware but instead 'Restore' the entire Mac using Apple Configurator.

For anyone else that runs into this problem. Go to > Actions > Restore in Apple Configurator. (Note the target Mac must be in DFU mode before you do this).

This solved the problem for me! Although I never managed to get migration assistant to work properly.

 

[Quackers]

Thanks, for all the replies guys - I'm using Big Sur 11.1. From what I could find online the Error 53 was related to iPhone & iPads as you say. I assume the M1 Macs' now use very similar boot processes to iOS devices.

I eventually got through to a 'Senior' tech at Apple based in Portugal, he was really helpful & told me not to follow the Apple support guide to 'revive' the Firmware but instead 'Restore' the entire Mac using Apple Configurator.

For anyone else that runs into this problem. Go to > Actions > Restore in Apple Configurator. (Note the target Mac must be in DFU mode before you do this).

This solved the problem for me! Although I never managed to get migration assistant to work properly.

Thanks for the update.
I think I'm right in saying that DFU mode was designed for phones originally but as you surmise, Macs are now big phones (software-wise) it seems
Presumably then that wipes all your data out (assuming you'd got far enough to have any).
By migration assistant, do you mean once the system has booted into Big Sur you go to Applications > Utilities > migration assistant?
Or are you talking about the Setup Assistant which is part of the new system set up?
Setup Assistant worked fine for me but I've never tried migration assistant.

Anyway, glad you've got it sorted.

 

[chrixtopher]

I had exact same thing happen - migration from older 2010 mbp to new m1 mini. Stalled during transfer of files. rebooted mac mini and now wont do anything but exclamation point and amber led

My 2010 mbp is too old to run Apple Configurator (cant upgrade - not supported ) .... so any ideas on how to fix this besides taking into an apple store? thanks

 

[Quackers]

I had exact same thing happen - migration from older 2010 mbp to new m1 mini. Stalled during transfer of files. rebooted mac mini and now wont do anything but exclamation point and amber led

My 2010 mbp is too old to run Apple Configurator (cant upgrade - not supported ) .... so any ideas on how to fix this besides taking into an apple store? thanks

Wow, another one.
Are you sure about Apple Configurator 2? Mine's a 2012 and can run it.
If you're right and you can't get another Mac I think the only way is to take it to Apple store.
I've not heard of any other way, sadly.

 

[chrixtopher]

you have to have 10.15.6 for configurator 2

I have 10.13 and can not upgrade as this is latest supported OS for my mid 2010 mbp ;(

 

[Quackers]

you have to have 10.15.6 for configurator 2

I have 10.13 and can not upgrade as this is latest supported OS for my mid 2010 mbp ;(

View attachment 1708355

Yes. Quite right. I'd seen that but forgot about it.
Can you get your hands on a newer Mac for a while?
Otherwise I think it needs to got to Apple

 

[chrixtopher]

Yes. Quite right. I'd seen that but forgot about it.
Can you get your hands on a newer Mac for a while?
Otherwise I think it needs to got to Apple

At this point - I am tempted to order another off amazon just so I can fix this myself and return the new one after using it just for configurator! That seems like the safest, quickest bet.

 

[Quackers]

At this point - I am tempted to order another off amazon just so I can fix this myself and return the new one after using it just for configurator! That seems like the safest, quickest bet.

Good idea! ???
Wouldn't that be a longish wait though?

 

[Mike Boreham]

You may have tried this but can't see it mentioned. I have twice got my M1 MBA into a state where it wouldn't boot from its internal drive, following failed attempts to install onto and boot from an external drive (since solved). In my case it went into a loop of Apple > progress bar > reboot > Apple > etc. Did this three times then said I needed to reinstall from Recovery which failed with an error message (can't recall now which it was). I then booted from an 11.1 USB installer I had created with createinstallmedia on my other Mac. This worked. I didn't erase before using it so all my stuff was there.
The second time something similar happened but this time when I got the message about needing to reinstall from Recovery, I just shut down, and when I rebooted it booted normally.
Maybe worth trying a bootable USB installer if you haven't already.

 

[chrixtopher]

You may have tried this but can't see it mentioned. I have twice got my M1 MBA into a state where it wouldn't boot from its internal drive, following failed attempts to install onto and boot from an external drive (since solved). In my case it went into a loop of Apple > progress bar > reboot > Apple > etc. Did this three times then said I needed to reinstall from Recovery which failed with an error message (can't recall now which it was). I then booted from an 11.1 USB installer I had created with createinstallmedia on my other Mac. This worked. I didn't erase before using it so all my stuff was there.
The second time something similar happened but this time when I got the message about needing to reinstall from Recovery, I just shut down, and when I rebooted it booted normally.
Maybe worth trying a bootable USB installer if you haven't already.

I have not tried that - but I cant even get to boot option. The firmware appears to be hosed.

 

[seebul]

Thanks for the update.
I think I'm right in saying that DFU mode was designed for phones originally but as you surmise, Macs are now big phones (software-wise) it seems
Presumably then that wipes all your data out (assuming you'd got far enough to have any).
By migration assistant, do you mean once the system has booted into Big Sur you go to Applications > Utilities > migration assistant?
Or are you talking about the Setup Assistant which is part of the new system set up?
Setup Assistant worked fine for me but I've never tried migration assistant.

Anyway, glad you've got it sorted.

Yep, pretty much feel like big phones . Yet to decide whether that's a good thing or not! Yes it would have also wiped any data on that device - although there wasn't any on there anyway.

I used it via the Setup Assistant & clicked 'Move from another Mac', it then instructed me to open migration assistant on the source Mac.

 

[Quackers]

Yep, pretty much feel like big phones . Yet to decide whether that's a good thing or not! Yes it would have also wiped any data on that device - although there wasn't any on there anyway.

I used it via the Setup Assistant & clicked 'Move from another Mac', it then instructed me to open migration assistant on the source Mac.

Ooh! I didn't get that, as such. It just loaded the options for transferral on mine.
Second time I did no transfers at all and made sure Big Sur was updated before I did anything else.
I just set it up manually to make sure nothing dodgy came across

 

[seebul]

I have not tried that - but I cant even get to boot option. The firmware appears to be hosed.

Sounds exactly like mine was. I think your only option is to use a newer Mac with Configurator 2 or take it to an Apple Store. Remember you need a cable to link them! I had to order a USB A > C in my case.

 

[chrixtopher]

thanks

cant you just use usb A to USB A or do you have to use the C on the new mini?

 

[Apple_Robert]

thanks

cant you just use usb A to USB A or do you have to use the C on the new mini?

I believe it has to be USB-C.