Security Update 2019-001 (Mojave)

@damienbarrett: Hi, I am one of those "impatient" users who ... three weeks ago, gotten scared by the black screen, I turned off the MacBook Air (2018) while updating process was starting. After that the symptoms are exactly what have been reported in these posts (no login with pw, no possibility to mount from Terminal nor from Disk Utility, no TDM, for diskutil ap list comes the mythical Encrypted: ERROR -69808 just as for the xartutil -- list the Total session count: 0 etc.). So, if I understand you well @damienbarrett, based on what said by Enterprise, being bricked, NO WAY to fix the problem without wiping the machine. Is that right? I really hoped to find a solution which can somehow save all what I have on my HD (unfortunately no backup was made recently). Guys, really no way to recover my dates?

sudo softwareupdate --fetch-full-installer --full-installer-version 10.14.6

does that only work if your machine isnt updated or on a prior version?
im on 10.14.6 build 18g2022 (latest)

i get the following result is which leads me to believe that may be a possibility

C02YJ17VJHD4:~ ME$ sudo softwareupdate --fetch-full-installer --full-installer-version 10.14.6
softwareupdate: unrecognized option `--fetch-full-installer'
softwareupdate: unrecognized option `--full-installer-version'
usage: softwareupdate <cmd> [<args> ...]

** Manage Updates:
    -l | --list     List all appropriate update labels (options:  --no-scan, --product-types)
    -d | --download     Download Only
    -e | --cancel-download      Cancel a download
    -i | --install      Install
        <label> ...   specific updates
        -a | --all      All appropriate updates
        -R | --restart      Automatically restart (or shut down) if required to complete installation.
        -r | --recommended  Only recommended updates
    --background        Trigger a background scan and update operation
    --ignore <label> ...  Ignore specific updates
    --reset-ignored     Clear all ignored updates

** Other Tools:
    --dump-state        Log the internal state of the SU daemon to /var/log/install.log
    --evaluate-products Evaluate a list of product keys specified by the --products option 
    --history       Show the install history.  By default, only displays updates installed by softwareupdate.  
    --all           Include all processes in history (including App installs) 

** Options:
    --no-scan       Do not scan when listing or installing updates (use available updates previously scanned)
    --product-types <type>        Limit a scan to a particular product type only - ignoring all others
        Ex:  --product-types macOS  || --product-types macOS,Safari 
    --products      A comma-separated (no spaces) list of product keys to operate on. 
    --force         Force an operation to complete.  Use with --background to trigger a background scan regardless of "Automatically check" pref 

    --verbose       Enable verbose output
    --help          Print this help

@jcheLC The fetch options only work in Catalina.

@ddcdennisb is there something similar for Mojave that i can use to grab the installer vs appstore or saving the .app somewhere?
basically looking for a CLI version of pulling the latest version of Catalina or Mojave using terminal if possible.

thanks!

@jcheLC I swear by Greg Neagle's script.

Any clever folks here come up with a way yet to "slipstream" a la Windows of yore Security Update 2019-002 for macOS Mojave? I refuse to accept that the best practice is to tediously:

1. Upgrade / Clean install Mojave build 18G103 and watch the reboots.
2. Wait for the Mojave install to complete, go through "looky new OS steps before your logon completes!" windows.
3. Initiate the Security Update 2019-002 upgrade.
4. Depending on your hardware, watch your screen freeze for up to a minute, go black for a similar period of time, tell you it's going to be 39 minutes until it completes, then finish in 5 minutes, or 45 minutes depending on unknown variables...
5. Log on again after update completes - "ooh looky more new OS steps!" to check that the build iterated to 18G2022.