View text source at Wikipedia
Developer(s) | Apple Inc. |
---|---|
Initial release | June 29, 2007 |
Stable release | iBoot-11881.40.163~61 (RELEASE)
|
Preview release | iBoot-11881.80.44~18 (RELEASE)
|
Operating system | Darwin, macOS,[1] iPadOS and iOS[2] |
Platform | x86, ARM |
Type | Boot loader |
License | Proprietary software |
iBoot is the stage 2 bootloader for iPhones, iPads, Apple silicon-based Macs, and the T2 chip in Intel-based Macs with such a chip.[3] [4] Compared with its predecessor, iBoot improves authentication performed in the boot chain.[2]
For Intel-based Macs with a T2 chip, the boot process starts by running code on the T2 chip from the boot ROM. That code has two primary responsibilities: to initialize system hardware (POST) and to load and run iBoot on the T2 chip. iBoot loads the bridgeOS operating system onto the T2 chip and starts it; bridgeOS loads the UEFI firmware into memory on the T2 chip, and starts the main Intel processor, which runs the UEFI firmware from the memory image on the T2 chip. The UEFI firmware loads boot.efi, which loads and starts the macOS kernel.[4]
For iPhones, iPads and Apple silicon-based Macs, the boot process starts by running the device's boot ROM. On iPhones and iPads with A9 or earlier A-series processors, the boot ROM loads the Low-Level Bootloader (LLB), which is the stage 1 bootloader and loads iBoot; on Macs and devices with A10 or later processors, the boot ROM loads iBoot. If all goes well, iBoot will then proceed to load the iOS, iPadOS or macOS kernel as well as the rest of the operating system.[5][6][7] If iBoot fails to load or fails to verify iOS, iPadOS or macOS, the bootloader jumps to DFU (Device Firmware Update)[8] mode; otherwise it loads the remaining kernel modules.[2][9]
Once the kernel and all drivers necessary for booting are loaded, the boot loader starts the kernel’s initialization procedure. At this point, enough drivers are loaded for the kernel to find the root device.[10]
Since Apple A7, the LLB and iBoot are stored on NAND flash of iPhone or iPad;[11] since Apple M1, the LLB is stored on the internal SSD of Apple silicon Mac.[12]
In iBoot, the build style varies on the version being used. Apple, Inc often uses "DEVELOPMENT" builds of iBoot, having features that are not available to "RELEASE" versions of it. This could apply to "DEBUG" or "SECRET" builds of it, but is not yet known.
RELEASE - A release version
DEVELOPMENT - A build that is used on developmental hardware, allows access to some developmental tools, such as the 'diags' command.
DEBUG - A build used for debugging iOS and other lower-level components
iBoot features a command prompt when in recovery, DFU, or restore mode (it is also in "DEBUG" builds of iBoot, but was never seen in future builds). Command availability depends on the type of iBoot being used, especially the build style (can be RELEASE, DEVELOPMENT, DEBUG, SECRET, etc).[citation needed]
When using iBoot's command prompt, the included commands are used to manage the behaviour, such as its boot arguments (internally called the "boot-args" in the NVRAM), or if the startup command (fsboot) should be used when iBoot is automatically loaded (known as auto-boot).[13][14]
Apple has modified the C compiler toolchain that is used to build iBoot in order to advance memory safety since iOS 14. This advancement is designed to mitigate entire classes of common memory corruption vulnerabilities such as buffer overflows, heap exploitations, type confusion vulnerabilities, and use-after-free attacks. These modifications can potentially prevent attackers from successfully escalating their privileges to run malicious code, such as an attack involving arbitrary code execution.[15]
In 2018, a portion of iBoot source code for iOS 9 was leaked on GitHub for various iPhone, iPad, iPod touch, and Apple Watch models,[16] Apple then issued a copyright takedown request (DMCA) to GitHub to remove the repository. It was believed an Apple employee was responsible for the leak. However, this was not confirmed by Apple. It is known that a user by the name of "ZioShiba" was responsible for the publication of the iBoot source code.
The earliest known version of iBoot was iBoot-87.1, seen on very early prototypes during the iPhone's production in 2006-2007.[17] It had the same features as the first known version of iBoot (iBoot-99), except it not having features before the final release. This version of iBoot could be considered the "first early beta" of iBoot. Following the release of the iPhone 2G and iPhone OS 1, the first release iBoot version was iBoot-159.