4 ms·
> How do I fix it? Image the partitions to a backup location. Zero the entire drive. Clear nvram. Reinstall macOS 15. See if it’s resolved.
by altairprime 2y ago
> How do I fix it?
Image the partitions to a backup location. Zero the entire drive. Clear nvram. Reinstall macOS 15. See if it’s resolved.
- mbirth 2y agoYou must have missed the part where it says that it's an M1 Mac. They don't have NVRAM you could clear. And zeroing the entire drive is also a bad idea as it also houses the "One True Recovery" - the only allowed pre-boot system. Once deleted, good luck getting your system working again. See: https://eclecticlight.co/2021/01/14/m1-macs-radically-change-boot-and-recovery/ https://eclecticlight.co/2021/01/14/m1-macs-radically-change...
- altairprime 2y ago> You must have missed the part where it says that it's an M1 Mac. That's certainly one possibility. > They don't have NVRAM you could clear. `nvram -p` still works fine on Apple Silicon — though I'm pretty sure it's only modifiable by the kernel these days — but, I haven't had a Mac that needed that wiped for years and years, so I missed that this is all the system image's problem on Apple Silicon now — thanks! > Once deleted, good luck getting your system working again. Per the 2021 post linked: > the only way to recover it is to restore the whole firmware and software image in DFU mode That's not "good luck" — that is, literally, the documented and expected next step, same as all the other Apple CPU devices, whether they're handheld or laptop or desktop: boot into DFU mode and factory reset it using another device. https://support.apple.com/en-us/108900 https://support.apple.com/en-us/108900 I know the author of the original post is aware of how to do that, and I recognize that they have chosen not to do so. I'm really glad that they explore all this stuff in depth; I don't have a development device to muck around with like they do!