Supported platforms: Difference between revisions
Jump to navigation
Jump to search
m 1 revision imported |
No edit summary |
||
| Line 5: | Line 5: | ||
*Official supported | *Official supported | ||
**[[MTK LK | MTK little kernel based bootloader]] | **[[MTK LK | MTK little kernel based bootloader]] | ||
**[[U-boot | Das U-Boot]] | |||
*Work in progress ports | *Work in progress ports | ||
**[[qcom abl | Qualcomm Android Boot Loader efi app]] | **[[qcom abl | Qualcomm Android Boot Loader efi app]] | ||
==2nd stage bootloaders== | ==2nd stage bootloaders== | ||
*[[lk2nd | little kernel based bootloader for older Qualcomm SOCs]] | *Official supported | ||
**[[lk2nd | little kernel based bootloader for older Qualcomm SOCs]] | |||
*Work in progress ports | |||
**[[Renegade UEFI | uefi implementation for modern qcom socs mainly used to boot windows]] | |||
==Not a bootloaders== | ==Not a bootloaders== | ||
*[[no-bl-workaround | Workaround for devices that do not have opensource 2nd stag bootloadr, based on Linux and dynamic boot re flashing]] | *Frozen | ||
**[[no-bl-workaround | Workaround for devices that do not have opensource 2nd stag bootloadr, based on Linux and dynamic boot re flashing]] | |||
Latest revision as of 13:05, 26 January 2023
Android Boot Manager consists of 2 parts, android app with sh backend (platform independent) and a "Droidboot" that stands for 2nd stage or 1st stage bootloader, in case it is 2nd stage bootloader, it is flashed to boot partition instead of linux kernel. In case it is 1st stage bootloader it replaces a bootloader of phone (like aboot, abl or lk partition), this is of course a better way of doing things, but sadly most devices needs signed bootloader, so modifying it is impossible. ABM currently support such:
1st stage bootloaders
- Official supported
- Work in progress ports
2nd stage bootloaders
- Official supported
- Work in progress ports