Mojave Safe Mode Not Accessible

When all three example Automator AppleScripts run, they assume or implement a boot sequence, that in turn constitutes a "remote" macOS instantiation, a new boot cycle. A special system cache on all bootable digital devices, stores and imlpments boot instructions.

Apple has a global system to protect. It would not surprise me to learn that macOS Safe Boot is a sacrosanct component of backend system security. With Safe mode boot being an un-scriptable process, intentionally obfuscated, to protect millions of Apple devices.

But where does Apple tell us that Safe mode boot cannot be scripted, because that process is obfuscated, for security reasons? No where. So I am just a mere mortal, wondering, if I can script a simple Safe mode boot, using that delightful Automator toy. Using perhaps script that triggers what dilabrain calls "remote access". Remote in a context that is relevant to this thread.

"there's a new way to do it: boot in recovery mode, and run the command csrutil enable --without kext"

getting warm, but not going to work

Try to set boot args...

There are millions of ways that we cannot do anything we want to do. Please stop trolling fails. If you know how to accomplish from the desktop, what we are trying to accomplish from the desktop (read HT201262, version at time of request for assistance in this thread) then please offer help. Otherwise, help is requested, writing a desktop command or script that will reboot macOS in Safe mode. There are App Store apps that will do this, but we are trying to do this with Terminal or Automator, using a command or Automator app.

Example AppleScript:

tell application "Terminal"

do script "sudo nvram SystemAudioVolume=%80"

end tell

Example AppleScript:

tell application "System Events"

restart

end tell

Example AppleScript:

tell application "System Events"

shut down

end tell

Safe mode boot?

Now dilabrain and ClassicII, you understand your parts left out, better now? I used a part of your reply to google into StackExchange, where the method of obfuscation by Apple seems to become apparent.

Trying to set boot args... opens a discussion where multiple boots are used to tunnel into settings where the following monstrous obfuscation is applied:

nvram boot-args="serverperfmode=1 ncl=262144"

YIKES! How could anyone ever work that out, without direct assistance from an Apple macOS engineer! So far as I know, there is no way with a mere mortal tiny AppleScript to tunnel into macOS with a secret multi-tunneling-boot command. This is just to demonstrate, Apple knows what the specific command is. It is not the M-T-B nightmare we seek, but something simple, like, "tell application "System Events" | shut down | end tell"

Anyone know the word or short phrase that works magic with Safe mode?

Further to Apple's words, or 'common (sic)' advice, shutdown -r now › after performing the hard reset (everyone calls this the 'hard' reset), immediately boot into safe mode and run diagnostics (here), SMC reset, etc..

Could be that our elusive Safe mode boot script is hidden under layers of other things, necessarily wiping out Apple reveal of the basic Safe Restart method. There must be thousands of ways that Mac techs are working Safe boot into who knows what.

And then there was T2... rendering my Mac Pro late-2013 (2018 build) a lost lamb. Help!