自 2025 年 3 月 27 日起,我們建議您使用 android-latest-release
而非 aosp-main
建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
通用啟動載入程式 (GBL) 總覽
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
通用啟動載入器 (GBL) 是一種標準化且可更新的啟動載入器解決方案,旨在簡化 Android 啟動程序。GBL 會取代廠商專屬的引導程序,這類引導程序的環境高度分散,而 GBL 則是採用單一、持續維護的元件。這項異動可減少重複內容、提升安全性,並簡化 Android 生態系統中的更新作業。
GBL 包含下列元件:
- Android 核心啟動邏輯
- 邏輯,包括主要程式迴圈、啟動模式偵測和載入核心。
- Fastboot
- 用於裝置閃燈和偵錯的通訊協定和診斷工具。
- 供應商額外資訊
- 透過建立自己的通訊協定,擴充上述 GBL 元件。在 GBL 將這些通訊協定加入依附元件清單之前,會先與相關人員達成協議。供應商額外資訊為選用項目。
- UEFI 通訊協定處理常式
- 實作必要和建議的 UEFI 通訊協定,包括區塊 I/O、記憶體配置和隨機數產生。您可以在啟動韌體專案 (EDK2、UBoot、LK) 中找到參考實作項目。
- Android 專屬 UEFI 通訊協定定義
- 適用於 AVB、Fastboot、插槽選取、作業系統設定等的客製化 UEFI 通訊協定。實作項目可在 Android 晶片供應商韌體專案中找到。
自 Android 16 起,如果您出貨的裝置採用 ARM-64 晶片組,強烈建議您部署最新的 Google 簽署版 GBL,並將其整合至啟動鏈。
後續步驟
如要瞭解如何部署通用啟動載入器,請參閱「部署 gbl」。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],null,["# Generic Bootloader (GBL) overview\n\nThe *Generic Bootloader (GBL)* is a standardized, updatable bootloader solution\ndesigned to streamline the Android boot process. GBL replaces the highly\nfragmented landscape of vendor-specific bootloaders with a single, consistently\nmaintained component. This change reduces redundancy, improves security, and\nsimplifies updates across the Android ecosystem.\n\nGBL consists of the following components:\n\n*core Android boot logic*\n: The logic that includes the main program loop, boot mode detection, and\n loading the kernel.\n\n*Fastboot*\n: A communication protocol and diagnostic tool used for device flashing and\n debug.\n\n*Vendor extensions*\n: Extension of the aforementioned components of GBL by creating\n your own protocols. These protocols are agreed upon in advance before GBL adds\n them to their dependency list. Vendor extensions are optional.\n\n*UEFI protocol handlers*\n: Implementations for required and recommended UEFI protocols, including block\n I/O, memory allocation, and random number generation. Reference implementations\n are found in the boot firmware projects (EDK2, UBoot, LK).\n\n*Android Specific UEFI Protocol definitions*\n: Custom UEFI protocols for AVB, Fastboot, slot selection, OS configuration,\n and more. Implementations are found in Android Silicon Vendor firmware projects.\n\nBeginning with Android 16, if you ship a device based on ARM-64 chipset, we\nstrongly recommend that you deploy the latest Google-signed version of GBL and\nintegrate it into your boot chain.\n\nWhat's next?\n------------\n\nTo learn how to deploy the Generic Bootloader, refer to\n[Deploy gbl](/docs/core/architecture/bootloader/generic-bootloader/gbl-dev)."]]