Wipe M1 Macbook Pro

I've seen this as well, had some success with running:

Enter macOS recovery. If you have FileVault 2 enabled, click the Recovery Assistant menu and then select “Erase Mac”. If you don’t have FileVault 2 Enabled or have already erased the drive, click utilities from the top menu bar and then click Terminal. Enter in the command resetpassword This will bring you back to the Recovery Assistant menu. Click the Recovery Assistant menu bar item at the top and then select “Erase Mac”.

Deleting the volume entirely, rebooting, then creating the volume again.

Yeah had this issue yesterday too. Was able to do it by erasing the container.

Hi all,

Yes I understand.
But if you send the Wipe commando trough Jamf, you don't have the container and volume anymore.

So my problem is still there, I can't wipe the "SSD" in the screenshot to create a volume on.
Then I get the error message as you can see in the screenshot.

I have also tried the way by using the reset password command pchrichard, ends up in the same issue :(.

What macOS-version was running as you send the whipe-command?
Is Mobileconfigurator and the DFU mode to reinstall macOS an option for you?

Running 11.0.1 and having the same issue on 11.1
And yes, Apple Configurator is then the only way to "revive' the device.

I've also encountered this issue while testing new provisioning process in Big Sur and M1. Used Apple Configurator to reinstall the OS for testing. Some articles about it:
https://support.apple.com/guide/apple-configurator-2/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac
https://mrmacintosh.com/reinstalling-big-sur-on-apple-silicon-macs-with-11-0-20a2411-error/

Hi all, I found this guys site really helpful in dealing with a bricked M1 Macbook...
https://mrmacintosh.com/mac-transition-to-apple-silicon-everything-you-need-to-know-updated/

@Janssen Have you considered to run Jamf policy to erase and install OS on M1 instead of wiping through MDM command?
I'm using Self Service policy to wipe and reinstall Big Sur on M1 Macs.
Or you are just exploring how to recover when computer had to be wiped remotely?

@Strannik what does that Self Service Policy for Wipe and Reinstall look like for your M1s? I have a setup for startosinstall for our intel Macs for Big Sur but I just got my first m1 test unit and everything I am seeing isn't as elegant. Any info or links that might help? Thanks!

@gforsyth The M1 Big Sur "Wipe and Reinstall" policy is exactly like the Intel one. The policy puts Big Sur installer in /Applications and runs install command in a script. Only the script is different.
The command I tried in script looks like this:

/usr/bin/su -l Admin -c "echo <user_password> | /Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps  --user <name> --stdinpass"

This is not a good solution as you need to put admin password in clear text.
Another way is to save password into a hidden file, then run a command like this:

/Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps  --user <name> --stdinpass < /path/to/file.text

The user must have a Secure Token.

Use the DFU mode and Apple Configurator 2 via TB/USB cable then select Erase all contents
It only take 10 mins to wipe and full OS and recovery to install (revive will only restore recovery firmware)

M1 acts more like an iPhone now

I got a different message trying to wipe Mac mini M1.
"No users available for authorization"

Oh thanks jannsen! So i was fed up with a big sur mac and decided to remote wipe it. But then i boot up into recovery and go to try and install the OS, but there are no volumes to install to (the list is blank).

Using disk utility, i select "partition" and then click the large part of the pie circle. Set the volume to ASPF or whatever the osx file system is and then go forward with the partitioning. I was able to make a volume and now the installer works!

was previously trying to just erase it but it wouldn't let me with a disk in use error.

the wipe command doesn't really work right in jamf i think with bigsur as its not intuitive at all what you need to do. it also never asked me for the code i created so what was the point of that then? But at least the OS was able to recover from some kind of inbuilt recovery. But it did need to connect to the network at one point so maybes its downloading from the internet.. who knows.

As part of my testing of an M1 MacBook Pro I did a "remote" wipe with Jamf Pro (the M1 was on the desk next to me), and it was immediately bricked, no amount of pivoting or faking would get it back to life except for Configurator (tried everything above). Never presented the unlock code that I put into the wipe command.
This presents a security problem. Anyone can look up the Configurator procedure on the internet and restore a wiped M1. Very not good.

/usr/bin/su -l Admin -c "echo <user_password> | /Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps  --user <name> --stdinpass"

/Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps  --user <name> --stdinpass < /path/to/file.text

Could you please share the entire script for erase and install Big Sur on M1?

@user-aj  The entire script is just one line:

/usr/bin/su -l Admin -c "echo $4 | /Applications/Install\\ macOS\\ Big\\ Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps --user Admin --stdinpass"

Enter Admin account password as Parameter 4 in the policy scripts options

Admin user _must_ have Secure Token.

@PhilS  Have you tried setting Activation Lock on Apple Silicon Macs to prevent someone from wiping and reusing computer?

Our environment is different we have common account name but we using laps for admin password, So it won't work if we set the password in parameters. Any other way we can resolve it?

@user-aj Maybe you can package the script that will capture user name and password, install and run it locally in Terminal by Self Service policy as described by fernando_gonzal here