# NVRAM ## Identification The list spans [[macOS Recovery|macOS Recovery]], boot caching and network boot, [[NVRAM|NVRAM]], System Integrity Protection (`csrutil`), disk and image administration (`diskutil`, `hdiutil`), identity (`dscl`), network configuration (`scutil`, `ipconfig`, `netstat`, `mDNSResponder`), security/keychain interfaces (`security`), and hardware profiling. Apple documents FileVault as full-volume encryption with recovery-key or account-based recovery paths ([Apple FileVault guide](https://support.apple.com/guide/mac-help/protect-data-on-your-mac-with-filevault-mh11785/mac)). ## Notebook evidence - [[Scanned_20260730-1719#PDF page 20 — macOS recovery and command-line tool inventory|PDF page 20: macOS recovery and command-line tool inventory]] — This is a rescue-shell vocabulary sheet: the commands most useful when the graphical system is unavailable or a disk, account, boot state, or network must be diagnosed from Recovery. - [[Scanned_20260730-1719#PDF page 21 — “Whatever it is” system and NVRAM variables|PDF page 21: “Whatever it is” system and NVRAM variables]] — “The Whatever it is system” is the most revealing phrase in the notebook. It suggests the author was not documenting one finished platform but assembling a trans-platform recovery environment from commands. NVRAM is important because it sits below the OS and can preserve boot, audio, ambient-light, and Bluetooth state even when the installed system changes. - [[Scanned_20260730-1719#PDF page 46 — UBU, MMTool, microcode, and AMI Aptio BIOS modding|PDF page 46: UBU, MMTool, microcode, and AMI Aptio BIOS modding]] — The author is researching repeatable module-level firmware maintenance: identify versions, extract components, replace option ROMs or microcode, and rebuild. This is a much more consequential form of “software update” than the Android app list on page 14. - [[Scanned_20260730-1719#PDF page 50 — AMI Aptio firmware modules and UEFITool|PDF page 50: AMI Aptio firmware modules and UEFITool]] — The author wants firmware that can understand more filesystems and emulate missing services before an OS loads. This is the architectural center of the Ozmosis section: move compatibility functions into UEFI modules so multiple boot paths can use them. - [[Scanned_20260730-1719#PDF page 56 — Apple startup modes and a mistaken SIP command|PDF page 56: Apple startup modes and a mistaken SIP command]] — The page is a boot-access cheat sheet, but it also illustrates a dangerous category error: Gatekeeper, SIP, single-user mode, and firmware startup modes are distinct controls. - [[Scanned_20260730-1719#PDF page 57 — Mac NVRAM/SMC resets, safe boot, startup manager, and diagnostics|PDF page 57: Mac NVRAM/SMC resets, safe boot, startup manager, and diagnostics]] — The page is an attempted fault-isolation ladder: reset persistent settings, reset hardware management, boot minimally, choose another disk, then test hardware. Some shortcuts have been merged incorrectly. - [[Scanned_20260730-1719#PDF page 71 — Mac lock-screen, hashes, startup keys, NVRAM, and virtualization|PDF page 71: Mac lock-screen, hashes, startup keys, NVRAM, and virtualization]] — The author is trying to relate firmware reset, boot access, password/account recovery, and a VirtualBox/Java workspace. The page is mnemonic, not a verified runbook. ## Relationships and overlays The source places this note in a shared evidence cluster with [[AMI Aptio|AMI Aptio]] · [[Btrfs|Btrfs]] · [[CPU microcode|CPU microcode]] · [[exFAT|exFAT]] · [[macOS Recovery|macOS Recovery]] · [[Scanned_20260730-1706|Scanned_20260730-1706]] · [[UEFI BIOS Updater|UEFI BIOS Updater]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Add command purpose, OS-version availability, required recovery mode, and read-only versus mutating risk. A bare command inventory is easy to misuse. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]