Android Boot Manager - User contributions [en-us]

Droidboot API

2024-03-10T16:10:58Z

Luka177:

ABM version 0.3 introduced a universal api to have single gui, lvgl, config parser etc. across all devices. That is achieved by having a separated droidboot_gui, bootloader, and HAL (hardware abstraction layer) that implements common functionality needed to use ABM. Here is the list of function you should implement to get ABM running on your bootloader.
==Display==
===droidboot_internal_get_display_height===
int droidboot_internal_get_display_height()
Should return display height in pixels

===droidboot_internal_get_display_width===
int droidboot_internal_get_display_width()
Should return display width in pixels

===droidboot_internal_get_disp_buffer_height===
int droidboot_internal_get_disp_buffer_height()
Should return int that represents number of horizontal lines in lvgl image buffer, usually is same as droidboot_internal_get_display_height.

===droidboot_internal_use_double_buffering===
bool droidboot_internal_use_double_buffering()
Should return true if you want to have double image buffer for lvgl, if you have planty of free RAM should be just hardcoded return true; It do make display refrash faster in some cases.

===droidboot_internal_fb_flush===
void droidboot_fb_flush(lv_disp_drv_t * disp_drv, const lv_area_t * area, lv_color_t * color_p)
Should draw color_p buffer on screen, coordinates are stored in area->x1, area->y1, area->x2, area->y2 after doing so should call lv_disp_flush_ready(disp_drv);
Example implementations:
If you have adress of fb in memory:
lv_coord_t w = (act_x2 - act_x1 + 1);
long int location = 0;
long int byte_location = 0;
unsigned char bit_location = 0;
int32_t y;
for(y = act_y1; y <= act_y2; y++) {
location = (act_x1 + 0) + (y + 0) * upriv->line_length / 4;
memcpy(&fbp32[location], (uint32_t *)color_p, (act_x2 - act_x1 + 1) * 4);
color_p += w;
}
lv_disp_flush_ready(disp_drv);

Where fbp32 is pointer to framebuffer.
If you have function to change pixel color:
time_t t;
int32_t x, y;
for(y = area->y1; y <= area->y2; y++) {
for(x = area->x1; x <= area->x2; x++) {
fbcon_draw_pixel(x, y, 0xff << 24 | color_p->ch.red << 16 | color_p->ch.green << 8 | color_p->ch.blue ); /* Put a pixel to the display.*/
color_p++;
}
}
// Update display
fbcon_flush();
// Inform the graphics library that we are ready with the flushing
lv_disp_flush_ready(disp_drv);
Where fbcon_draw_pixel is function to update single pixel and fbcon_flush is function to flush whole display.

==Storage==
===droidboot_internal_sd_read_block===
ssize_t droidboot_internal_sd_read_block(void *buf, uint32_t block, uint count)
Is a function to read block(s) from storage device, it takes pointer to buffer (buf) where you should put reading result, "block" is a number of first block to read and count is amount of blocks to read. Buffer is pre-allocated. Should return amount of block that were read from storage device (if everything is successful should be same as count).
===droidboot_internal_sd_write_block===
ssize_t droidboot_internal_sd_write_block(const void *buf, uint32_t block, uint count)
Is a function to write block(s) to storage device, it takes pointer to buffer (buf) where new block content is stored, "block" is a number of first block to write and count is amount of blocks to write.Should return amount of block that were written to storage device (if everything is successful should be same as count).
===droidboot_internal_sd_blklen===
uint32_t droidboot_internal_sd_blklen()
Shoul return block size (usually is 512 or 4096) it is good idea not to hardcode it but rather get dynamically.
===droidboot_internal_sd_blkcnt===
uint64_t droidboot_internal_sd_blkcnt()
Should return amount of blocks on storage device.
===droidboot_internal_sd_exists===
bool droidboot_internal_sd_exists()
Should return true if storage device do exist.

A word about android, dynamic and stuff

2023-09-23T21:02:43Z

Luka177:

This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt.

== Handling super ==
Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as:

* system
* vendor

Likely to contain:

* product
* system_ext

Can contain:

* odm

Those partition might or might not be in 2 sets A and B. Right some devices are very modern but still A only.

The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like ```soc/8804000.sdhci``` to ```androidboot.boot_device``` but you should leave old one as first and separate wit ,

A word about android, dynamic and stuff

2023-09-23T21:01:47Z

Luka177:

A word about android, dynamic and stuff

2023-09-23T21:00:02Z

Luka177:

A word about android, dynamic and stuff

2023-09-23T20:59:29Z

Luka177: Created page with "This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt. == Handling super == Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as: * system * vendor Likely to contain: * pr..."

This page contains a bit of info about android dualboot handling for platform and app developers. Usually not too relevant for porters. All info here is up to date as of September 2023. Take all info found here with grain of salt.

== Handling super ==
Obviously a first question when it comes to dualbooting on modern android phones, is what to do with so called super partition, that in fact should contain such parturition as:

* system
* vendor

Likely to contain:

* product
* system_ext

Can contain:

* odm

Those partition might or might not be in 2 sets A and B. Right some devices are very modern but still A only.

The ABM team decided to create a separate super partition for each android based os installed, a big suprise they are named: super1, super2, ..., superX

As partitions are located on sd card and android wants to mount them from /dev/block/by-name, we should somehow get them there with minimum to no binary patching. Apparently its easy as adding path to sd device, like soc/8804000.sdhci to androidboot.boot_device but you should leave old one as first and separate wit ,

Random facts

2023-09-23T20:47:20Z

Luka177:

[[Droidboot_API|Droidboot API description]] (WIP)

[[A word about android, dynamic and stuff]] (even more WIP)

Random facts

2023-09-23T20:47:09Z

Luka177:

'''Random facts'''
[[Droidboot_API|Droidboot API description]] (WIP)

[[A word about android, dynamic and stuff]] (even more WIP)

Random facts

2023-09-23T20:46:55Z

Luka177: Created page with "'''Random facts''' Droidboot API description (WIP) A word about android, dynamic and stuff (even more WIP)"

'''Random facts'''
[[Droidboot_API|Droidboot API description]] (WIP)
[[A word about android, dynamic and stuff]] (even more WIP)

Android Boot Manager:Main Page

2023-09-23T20:43:58Z

Luka177:

'''Welcome to the Android Boot Manager wiki!'''

<div style="margin-top: 40px; width: 350px; padding-left: 15px">

{{mainpage-button|smartphone|Devices}}
{{mainpage-button|emblem-shared|:Category:Community|Community}}
{{mainpage-button|dialog-question|FAQ}}
{{mainpage-button|application-menu|Supported_platforms|Platforms supported by ABM}}
{{mainpage-button|random_facts|Random facts}}


{{mainpage-button|document-save|Installation_Tutorial|Installation}}
{{mainpage-button|application-menu|Porting_to_a_new_device|Porting}}


{{mainpage-button|emote-love|Contributing}}
{{mainpage-button|folder-documents|:Category:Technical Reference|Technical Reference}}
{{mainpage-button|emblem-important|Troubleshooting}}

</div>

=== Features ===
* Easily flash the bootloader
* Bootmenu at start time
* Partition your SD card
* Multiboot
* Install Android, Ubuntu Touch, Sailfish OS
* Use functions for power users
* Autoboot specific system after an Timeout

=== Use Cases ===
Dualbooting is useful...

* ...to try out an alternative operating system (without overwriting the existing installation)
* ...boot from a secure external storage (SD card) for special security like
** ensuring an untampered operating system
** prevent persistent viruses and tracking software

Lk2nd

2023-01-26T11:12:22Z

Luka177:

==Overview==
Before Snapdragon 82X Qualcomm did use lk based open source bootloader, while modern device don't use it anymore, ABM do still [https://github.com/Android-Boot-Manager/droidboot_device_qcom_lk2nd support it]

Lk2nd

2023-01-26T11:12:10Z

Luka177: Created page with "==Overview== Befor Snapdragon 82X Qualcomm did use lk based open source bootloader, while modern device don't use it anymore, ABM do still [https://github.com/Android-Boot-Manager/droidboot_device_qcom_lk2nd support it]"

==Overview==
Befor Snapdragon 82X Qualcomm did use lk based open source bootloader, while modern device don't use it anymore, ABM do still [https://github.com/Android-Boot-Manager/droidboot_device_qcom_lk2nd support it]

U-boot

2023-01-26T11:09:58Z

Luka177: Created page with "==Overview== [https://en.wikipedia.org/wiki/Das_U-Boot Das U-Boot] (subtitled "the Universal Boot Loader" and often shortened to U-Boot; see History for more about the name) is an open-source, primary boot loader used in embedded devices to package the instructions to boot the device's operating system kernel. It is available for a number of computer architectures, including 68k, ARM, Blackfin, MicroBlaze, MIPS, Nios, SuperH, PPC, RISC-V and x86. ==ABM== Currently there..."

==Overview==
[https://en.wikipedia.org/wiki/Das_U-Boot Das U-Boot] (subtitled "the Universal Boot Loader" and often shortened to U-Boot; see History for more about the name) is an open-source, primary boot loader used in embedded devices to package the instructions to boot the device's operating system kernel. It is available for a number of computer architectures, including 68k, ARM, Blackfin, MicroBlaze, MIPS, Nios, SuperH, PPC, RISC-V and x86.
==ABM==
Currently there is [https://github.com/Android-Boot-Manager/droidboot_platforms/tree/main/u-boot Work-In-Progress u-boot support] in droidboot platforms.

==Issues==
*Currently only one storage device is supported
*Only keyboard input is supported
*There are no gui menus for u-boot setup, only basic ABM boot menu

Supported platforms

2023-01-26T11:05:45Z

Luka177:

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
**[[MTK LK | MTK little kernel based bootloader]]
**[[U-boot | Das U-Boot]]
*Work in progress ports
**[[qcom abl | Qualcomm Android Boot Loader efi app]]

==2nd stage bootloaders==
*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==
*Frozen
**[[no-bl-workaround | Workaround for devices that do not have opensource 2nd stag bootloadr, based on Linux and dynamic boot re flashing]]

Droidboot API

2023-01-26T10:58:21Z

Luka177:

ABM version 0.3 introduced a universal api to have single gui, lvgl, config parser etc. across all devices. That is achieved by having a separated droidboot_gui, bootloader, and HAL (hardware abstraction layer) that implements common functionality needed to use ABM. Here is the list of function you should implement to get ABM running on your bootloader.
==Display==
===droidboot_internal_get_display_height===
int droidboot_internal_get_display_height()
Should return display height in pixels

===droidboot_internal_get_display_width===
int droidboot_internal_get_display_width()
Should return display width in pixels

===droidboot_internal_get_disp_buffer_height===
int droidboot_internal_get_disp_buffer_height()
Should return int that represents number of horizontal lines in lvgl image buffer, usually is same as droidboot_internal_get_display_height.

===droidboot_internal_use_double_buffering===
bool droidboot_internal_use_double_buffering()
Should return true if you want to have double image buffer for lvgl, if you have planty of free RAM should be just hardcoded return true; It do make display refrash faster in some cases.

===droidboot_internal_fb_flush===
void droidboot_fb_flush(lv_disp_drv_t * disp_drv, const lv_area_t * area, lv_color_t * color_p)
Should draw color_p buffer on screen, coordinates are stored in area->x1, area->y1, area->x2, area->y2 after doing so should call lv_disp_flush_ready(disp_drv);
Example implementations:
If you have adress of fb in memory:
lv_coord_t w = (act_x2 - act_x1 + 1);
long int location = 0;
long int byte_location = 0;
unsigned char bit_location = 0;
int32_t y;
for(y = act_y1; y <= act_y2; y++) {
location = (act_x1 + 0) + (y + 0) * upriv->line_length / 4;
memcpy(&fbp32[location], (uint32_t *)color_p, (act_x2 - act_x1 + 1) * 4);
color_p += w;
}
lv_disp_flush_ready(disp_drv);

Where fbp32 is pointer to framebuffer.
If you have function to change pixel color:
time_t t;
int32_t x, y;
for(y = area->y1; y <= area->y2; y++) {
for(x = area->x1; x <= area->x2; x++) {
fbcon_draw_pixel(x, y, 0xff << 24 | color_p->ch.red << 16 | color_p->ch.green << 8 | color_p->ch.blue ); /* Put a pixel to the display.*/
color_p++;
}
}
// Update display
fbcon_flush();
// Inform the graphics library that we are ready with the flushing
lv_disp_flush_ready(disp_drv);
Where fbcon_draw_pixel is function to update single pixel and fbcon_flush is function to flush whole display.

==Storage==
===dridboot_internal_sd_read_block===
ssize_t dridboot_internal_sd_read_block(void *buf, uint32_t block, uint count)
Is a function to read block(s) from storage device, it takes pointer to buffer (buf) where you should put reading result, "block" is a number of first block to read and count is amount of blocks to read. Buffer is pre-allocated. Should return amount of block that were read from storage device (if everything is successful should be same as count).
===dridboot_internal_sd_write_block===
ssize_t dridboot_internal_sd_write_block(const void *buf, uint32_t block, uint count)
Is a function to write block(s) to storage device, it takes pointer to buffer (buf) where new block content is stored, "block" is a number of first block to write and count is amount of blocks to write.Should return amount of block that were written to storage device (if everything is successful should be same as count).
===droidboot_internal_sd_blklen===
uint32_t droidboot_internal_sd_blklen()
Shoul return block size (usually is 512 or 4096) it is good idea not to hardcode it but rather get dynamically.
===droidboot_internal_sd_blkcnt===
uint64_t droidboot_internal_sd_blkcnt()
Should return amount of blocks on storage device.
===droidboot_internal_sd_exists===
bool droidboot_internal_sd_exists()
Should return true if storage device do exist.

Droidboot API

2023-01-26T10:11:30Z

Luka177:

Droidboot API

2023-01-25T21:41:01Z

Luka177:

Droidboot API

2023-01-25T21:25:49Z

Luka177: Created page with "ABM version 0.3 introduced a universal api to have single gui, lvgl, config parser etc. across all devices. That is achieved by having a separated droidboot_gui, bootloader, and HAL (hardware abstraction layer) that implements common functionality needed to use ABM. Here is the list of function you should implement to get ABM running on your bootloader. ==Display related== ==droidboot_internal_get_display_height== {{{int droidboot_internal_get_display_height()}}} Should..."

Template:Devices

2022-10-20T17:15:10Z

Luka177:

<noinclude>
{{#template_params:Codename|Manufacturer|Name|Chipset|StatusBootloader|StatusDisplay|StatusUSB|StatusTouchscreen}}
{{#cargo_declare:_table=Devices|Codename=String|Manufacturer=String|Name=String|Chipset=String|StatusBootloader=String|StatusDisplay=String|StatusUSB=String|StatusTouchscreen=String}}
</noinclude><includeonly>{{#cargo_store:_table=Devices}}
{{#template_display:_format=standard}}
[[Category:Devices]]
</includeonly>

Template:Devices

2022-10-20T17:12:59Z

Luka177:

<noinclude>
{{#template_params:Codename|Manufacturer|Chipset|StatusBootloader|StatusDisplay|StatusUSB|StatusTouchscreen}}
{{#cargo_declare:_table=Devices|Codename=String|Manufacturer=String|Chipset=String|StatusBootloader=String|StatusDisplay=String|StatusUSB=String|StatusTouchscreen=String}}
</noinclude><includeonly>{{#cargo_store:_table=Devices}}
{{#template_display:_format=standard}}
[[Category:Devices]]
</includeonly>

Form:Devices

2022-10-20T17:09:12Z

Luka177:

<noinclude>
This is the "Devices" form.
To create a page with this form, enter the page name below;
if a page with that name already exists, you will be sent to a form to edit that page.

{{#forminput:form=Devices|autocomplete on category=Devices}}

</noinclude><includeonly>
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|Devices}}}
{| class="formtable"
! Codename:
| {{{field|Codename}}}
|-
! Chipset:
| {{{field|Chipset}}}
|-
! StatusBootloader:
| {{{field|StatusBootloader}}}
|-
! StatusDisplay:
| {{{field|StatusDisplay}}}
|-
! StatusUSB:
| {{{field|StatusUSB}}}
|-
! StatusTouchscreen:
| {{{field|StatusTouchscreen}}}
|}
{{{end template}}}

'''Free text:'''

{{{standard input|free text|rows=10}}}
</includeonly>

Category:Devices

2022-10-20T17:09:01Z

Luka177:

Template:Devices

2022-10-20T17:09:00Z

Luka177:

<noinclude>
{{#template_params:Codename|Chipset|StatusBootloader|StatusDisplay|StatusUSB|StatusTouchscreen}}
{{#cargo_declare:_table=Devices|Codename=String|Chipset=String|StatusBootloader=String|StatusDisplay=String|StatusUSB=String|StatusTouchscreen=String}}
</noinclude><includeonly>{{#cargo_store:_table=Devices}}
{{#template_display:_format=standard}}
[[Category:Devices]]
</includeonly>

Volla Phone (volla-yggdrasil)

2022-10-20T16:52:04Z

Luka177: Created page with "{{Infobox device | manufacturer = Volla | name = Volla Phone | codename = volla-yggdrail | releaseyear = 2020 | chipset = Mediatek Helio P23 (MT6763V) | cpu = Octa-core 2.0 GHz Cortex-A53 | display = 2340 x 1080 pixels, 6.3-inch IPS LCD | storage = 64 GB | memory = 4 GB | architecture = aarch64 | status_bootloader = Y | status_display = Y | status_mainbuttons = Y | status_touchscreen = N | status_usb = P | status_extrabuttons = - }}"

{{Infobox device
| manufacturer = Volla
| name = Volla Phone
| codename = volla-yggdrail
| releaseyear = 2020
| chipset = Mediatek Helio P23 (MT6763V)
| cpu = Octa-core 2.0 GHz Cortex-A53
| display = 2340 x 1080 pixels, 6.3-inch IPS LCD
| storage = 64 GB
| memory = 4 GB
| architecture = aarch64
| status_bootloader = Y
| status_display = Y
| status_mainbuttons = Y
| status_touchscreen = N
| status_usb = P
| status_extrabuttons = -
}}

User:Luka177

2022-10-20T16:30:07Z

Luka177: Created page with "Hello, i have no idea why you are here, anyway I am Luka known as luka177 and cvbnm90i. I am main droidboot developer, and sometimes do app for fun."

Hello, i have no idea why you are here, anyway I am Luka known as luka177 and cvbnm90i. I am main droidboot developer, and sometimes do app for fun.