Network recovery fails, and boot settings blocking boot from external volume (Kobayashi Maru scenario)

Here's a fun one:


Booting from external USB device fails, because boot security settings won't allow it.


  • Can't change boot security settings because it requires admin password
  • No admin password, because corrupted volumes on internal drive have been erased
  • Network Recovery macOS reinstall fails with "PKDownloadError," even when connected via reliable ethernet connection


Running out of ideas. Suggestions?


Details: MacBook Pro 16" (Intel), macOS Ventura






MacBook Pro (2017 – 2020)

Posted on Mar 7, 2023 12:46 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 8, 2023 12:44 PM

Did you try to authenticate in Recovery Mode?


If you have access to another Mac running macOS 10.15+, then you can "Restore" the firmware which resets the T2 security chip as well as pushing a clean OS to the internal SSD.

Revive or restore an Intel-based Mac using Apple Configurator - Apple Support


Similar questions

4 replies

Mar 10, 2023 3:54 PM in response to Injunear

Update: Seems there is a bigger issue. The original problem I was trying to solve was strange volume error messages. Did a macOS reinstall, hoping that would go away. It didn't. Later, started to see occasional kernel panics.


Decided to erase the volume, and start over. That's how I ended up down the path of trying to reinstall, but painted myself into a corner with the T2 chip and disabled booting from an external drive. (Hint: enable booting from external media before you wipe the drive, or you'll be stuck). Then there was some mystery issue with the local network causing the Internet Restore loading of macOS to fail. Tried it on a different network, and made some progress.


Then I ran into "The operation couldn't be completed. Permission denied" when it was attempting to install macOS. The installer log showed:


Could not create mutable product at /Volumes/Macintosh HD/macOS Install Data (error 28).
- [OSISHelperProxy createMutableProductAtMountPoint: J_block_invoke_2: Error Domain-NSPOSIXErrorDomain Code-28 "No space left on device" etupd (641): 
- [OSISCreateMutable roductOperation startWithDelegate:]: Could not create mutable product at mount point: /Volumes/Macintosh HD etupd (641) : Operation queue failed with error: Error Domain-NSPOSIXErrorDomain Code 13 "Permission denied"
Stopped operation queue with Error Domain-NSPOSIXErrorDomain Code 13 "Permission denied"


To me, it was starting to look like an SSD issue.


Took it to the Genius Bar today, they did a diagnostic, but the SSD passed. They recommended a main logic board replacement, primarily due to the kernel panics. Covered under AppleCare+. We'll see what happens.


Thanks to all who replied.



Mar 10, 2023 7:15 PM in response to Injunear

FYI, most SSD failures I have encountered never show up as a problem with the diagnostics. It is very hard to support these 2018+ models as there is very little details or feedback when performing various procedures. Obviously no one designing these newer Macs are actually doing any day to day support of these Macs with troublesome unknown issues...these designs may look good on paper, but they are not good in the real world when something goes wrong. Usually involves shoveling out lots of money.


Please let us know how it all works out.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Network recovery fails, and boot settings blocking boot from external volume (Kobayashi Maru scenario)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.