Migration Assistant breaking MacBook Pro M1 T2 firmware (exclamation mark)

Hi all,

please share whether you've experienced similar obstacles as I think these are major issues and I'm not alone.

Sharing the problem, the possible cause and the resolution.

Having bought a brand new MBP 16 2021 M1 Pro based running on macOS Monterey, I’ve started migrating from my vintage Intel-based MacBook Pro on macOS Mojave.

I’ve chosen to go the Apple way with Migration Assistant hoping it will move the system and settings to save time.

I did try the Wi-Fi and Ethernet options several times - all of them stalled at a certain point. Restore from a Time Capsule connected via Ethernet failed as well.

—

Considering the amount of user reports noting the problem, it’s extremely strange the bug is not fixed yet…I’m absolutely not accepting any possibility of a broken Time Machine restore.

—

The only working (and fast) option for me turned out to be a fresh complete Time Machine backup to an external USB drive, then connecting the drive to the new MBP M1 for a Time Machine restore.

I have selected to migrate everything: Applications, User Profile, Other Files & Folders and System & Network.

FAILED AGAIN.

Turned out, you need to create your user profile on the new machine first, LOG IN and then Migration Assistant does its job successfully… OMG, what a mess…

Migration completed, the system has booted, everything looked fine. Made it reboot once again for a fresh start and… 

THE MACHINE HAS DIED. Exclamation mark. WEIRD. I was shocked. No tampering, no nothing, the migration process has killed the machine…

A little bit of googling uncovered the mystery: failed T2 chip firmware (migration of apps/data/settings kills firmware? Excuse me?!). Okay, turned out there’s an article on this:

Revive or restore a Mac with Apple silicon using Apple Configurator – Apple Support (UK)

The thing is, YOU NEED A SECOND MAC TO REVIVE OR RESTORE A MAC! Insane. 

Also, the second Mac must meet minimum system requirements for the macOS version capable of running the latest version of Apple Configurator…No, you can’t get an older Apple Configurator and give it a try on, let’s say, Mojave… Technically, this is understandable, BUT…

After several conversations with Apple Support in chat and over the phone, I was left with the only option: bring my brand new failed Mac to the Authorised Apple Service - which I did.

The Service told me that was A SOFTWARE PROBLEM, for which Apple is not responsible (again, the problem was a result of straightforward use of Apple Migration Assistant to migrate from one Apple device to another) and does not cover it with warranty and charged me, I guess, $35 or so plus 3 days wait time (TO FACTORY REFLASH THE DEVICE!).

Since it was a fresh system, the drive was not encrypted and I had to leave all my data in a service center unencrypted hoping the service guy will not want to dig through the data and retain it - and no, I don’t think this matter has something to do with trust. There must be a way to completely reset the soldered-on drive even in case of a system failure by the user (or in user presence). The Authorised Apple Service employees didn’t even suggest to mutually sign any kind of an NDA or data privacy guarantee…

Okay, I’ve got my restored M1 Mac back and faced the need to migrate again. Called Apple Support and after several diverts, a support specialist told me I need to DESELECT THE LAST OPTION “SYSTEM & NETWORK” to ensure the system will not be ruined again.

The migration was a SUCCESS this time, everything has migrated, all settings, networking (!), etc.

Conclusion&thoughts.

1. There’s clearly a major flaw in M1 system design that allows it to die completely from a software problem. Apple must have implemented a redundant/backup firmware image or a restoration path not requiring other devices (let alone a second Mac). This has nothing to do with security, it’s exactly the system design flaw.
2. Migration Assistant is an Apple tool and MUST provide bullet-proof experience, definitely not killing the system (and prevent migration of any potentially harmful leftovers from another architecture).
3. I wasn’t able to find any notes anywhere on the dangerous System & Network option, no warnings. I do suspect, Migration Assistant has migrated a certain application software related KEXT for Intel architecture that ruined everything.
4. The charge of $35 is absolutely weird (Apple has confirmed the charge was correct in this case). The issue must be covered by warranty since it’s a system design flaw which is unavoidable by the user under certain circumstances.
5. The M1 drive must be encrypted from the start, all data must migrate to the encrypted volume immediately to ensure data protection. If this is impossible - there must be a way to destroy data before leaving the system at a service center.

WBR)