Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yeah, nice try, but that is broken on the M1 Mac, so whatever you do, don’t Erase your HD, or you will be using the Apple Configurator 2, just like I have to.

Simply not true. The process I provided erases the drive and does bare install without GarageBand, iMovie and the 3 office apps. Works great. I’ve also posted on Reddit and many successful there as well. @Lumpydog discovered the process and helped many as well.
 
  • Like
Reactions: Nightfury326
If you can, please do!
I was in extreme urgency to get a new computer (and I wanted to stay with apple), therefore I took an M1 Mac Mini with 16GB of ram, but if you're in the position to wait 7-8 months (tops) please do.
 
  • Like
Reactions: Nightfury326
Simply not true. The process I provided erases the drive and does bare install without GarageBand, iMovie and the 3 office apps. Works great. I’ve also posted on Reddit and many successful there as well. @Lumpydog discovered the process and helped many as well.
That’s all great and all, but that is not the standard process by which Macs have traditionally been restored... My M1 is already at the point where it needs to be recovered with Apple Configurator 2.

As for what I’m saying, You can even see the docs where Apple released a process to get it back up and running. Why Did Apple do this? Because you get an error message telling you there’s no user authorized to restore the Mac once you Erase the drive.

I did not try the reinstall option on the OS, but the erasing of the HDD and the restore simply does not work.
 
Last edited:
If your current system does everything well, I don't see any super major benefit to you updating right now unless you are constantly running out of battery power. Wait on a new 16-inch IMO.
 
That’s a lie, you can even see the docs where Apple released a process to get it back up and running. Why Did Apple do this? Because you get an error message telling you there’s no user authorized to restore the Mac once you Erase the drive.

I did not try the reinstall option on the OS, but the erasing of the HDD and the restore simply does not work.

What motivation would I have to lie? I’m an 11 year contributor of this site. (Look up what that means) I come here primarily to help others. And speculate on the future of Apple. I have 1,100 + messages as an example.

I’ve performed the operation. It works. You by admission “did not try.” You’ll find in these forums that experience goes a long way.

Also, Apple makes mistakes, the legacy process lead users down a path not suitable for the new drive partitioning schema for the SoC. Bad interface design, because the recovery option, also which can be done from iCloud, works and was there all along a bit hidden off the path. (Requires WiFi and you to know your iCloud Account user ID and password)

First time I tried it, was an experiment. My store is open in San Antonio, had it not worked, I would have returned it.
The second time, in a rage, I wanted to purge Apples bloated Xcode IDE from my system when I noticed the installed package now consumes 25 GB of disk space.
 
Yeah, nice try, but that is broken on the M1 Mac, so whatever you do, don’t Erase your HD, or you will be using the Apple Configurator 2, just like I have to.
What @Zazoh said is true and does work reinstalling Big Sur. 11.1 And it also does not install Garage Band etc. He didn't lie. If he had been wrong, that is a lot different than lying. Don't equate the two. Zaz is a good guy.
 
Last edited:
What @Zazoh said is true and does work reinstalling Big Sur. 11.1 And it also does not install Garage Band etc. He didn't lie. If he had been wrong, that is a lot different than lying. No equate the two. Zaz is a good guy.
Right but you’re okay with him saying that I’m not telling the truth right? I’ll give you a screenshot with the error and you can then tell me I’m lying.

The truth is Apple put something in place that doesn’t work, and those of us who support macs for a living followed the same steps we always have, only to be met by a process that not only didn’t work, it forced us to use a second Mac to recover it (I’ve yet to go through the Apple process to recover it).
 
What motivation would I have to lie? I’m an 11 year contributor of this site. (Look up what that means) I come here primarily to help others. And speculate on the future of Apple. I have 1,100 + messages as an example.

I’ve performed the operation. It works. You by admission “did not try.” You’ll find in these forums that experience goes a long way.

Also, Apple makes mistakes, the legacy process lead users down a path not suitable for the new drive partitioning schema for the SoC. Bad interface design, because the recovery option, also which can be done from iCloud, works and was there all along a bit hidden off the path. (Requires WiFi and you to know your iCloud Account user ID and password)

First time I tried it, was an experiment. My store is open in San Antonio, had it not worked, I would have returned it.
The second time, in a rage, I wanted to purge Apples bloated Xcode IDE from my system when I noticed the installed package now consumes 25 GB of disk space.
You act like I have a reason to lie! I do not, I’m speaking from experience. This is the process I actually have to do to recover it.


I did not try that approach, because my Mac is already in the state where recovery that way is not possible.
 
Right but you’re okay with him saying that I’m not telling the truth right? I’ll give you a screenshot with the error and you can then tell me I’m lying.

The truth is Apple put something in place that doesn’t work, and those of us who support macs for a living followed the same steps we always have, only to be met by a process that not only didn’t work, it forced us to use a second Mac to recover it (I’ve yet to go through the Apple process to recover it).
I haven't looked at every recent post in this thread.

Calling other people liars (regardless of who is doing it or started it) is not good, especially when one may be stating inaccurate information that one doesn't know to be inaccurate at the time. That is all I am going to say on that aspect of the posts.

With 11.0 - 11.01, Using the Configurator was one of the routes needed at the time, to do a reinstall of Big Sur. I got my M1 with 11.01 pre-installed and immediately updated to 11.1. I didn't have to use the previously mentioned route. I did reinstall Big Sur 11.1 without any problems, although I did have to rename my drive and reinstall some of the Apple stock apps I use. Since I have FileVault enabled, I had to go into Terminal and erase the drive and resetpassword twice. Those that don't have FileVault enabled don't have to go that route, as far as I am aware.
 
  • Like
Reactions: Zazoh
I would wait for the new 16", I personally love having a larger screen, don't care about the weight. My wife has a 13" on order, but I'm waiting for a 16".
 
You’ve basically answered you’re own question. The one you have runs fine, 13” is too small and 2 TB3 ports aren’t enough for you.

So, seems fairly obvious to me, I’d say wait. You know there’s going to be a 16” Apple Silicon MBP within the next year, two at the most. It’s not that long to wait really.
 
  • Like
Reactions: tonyr6
I would wait for the new 16", I personally love having a larger screen, don't care about the weight. My wife has a 13" on order, but I'm waiting for a 16".
I am also waiting for the Apple Silicon 16" MBP to replace my current 16" MBP. I hope that Apple also updates the display resolution too, but I don't believe that they will any time soon..
 
I haven't looked at every recent post in this thread.

Calling other people liars (regardless of who is doing it or started it) is not good, especially when one may be stating inaccurate information that one doesn't know to be inaccurate at the time. That is all I am going to say on that aspect of the posts.

With 11.0 - 11.01, Using the Configurator was one of the routes needed at the time, to do a reinstall of Big Sur. I got my M1 with 11.01 pre-installed and immediately updated to 11.1. I didn't have to use the previously mentioned route. I did reinstall Big Sur 11.1 without any problems, although I did have to rename my drive and reinstall some of the Apple stock apps I use. Since I have FileVault enabled, I had to go into Terminal and erase the drive and resetpassword twice. Those that don't have FileVault enabled don't have to go that route, as far as I am aware.
Yeah that’s a pain in the butt! Never had to do any of that with the Intel Macs, even with Big Sur.

I was polite and removed the lie remark.

At the same time I’m not lying, these are legitimate issues.
 
Last edited:
I’m going to hold on to my 16” for at least another year or two. The 16” performs just fine, and there’s not much of a reason to update yet. You might as well just let the M1 transition mature a little bit and then get the M2/M3 when that comes out in a 16” form factor. I’m planning on hopping over to Apple silicon within the next two generations of MBP, but I’m by no means in a hurry to leave the Intel line for the time being since it’s been performing just fine.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.