| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Use board define BOARD_RECOVERY_BLDRMSG_OFFSET with a decimal integer
to define a custom offset where the bootloader message should be
read/written.
Edify commands get_stage and set_stage need to be aware of the
custom bootloader msg offset because they write the stage directly
to the BCB.
Change-Id: Id13a23dd41bb7d907b96d657b8e21eb839dfeaa9
|
|
|
|
|
|
|
|
|
|
|
| |
When set_bootloader_message_block() is called, it fopens /misc in write
binary mode, wiping all contents other than what is being written. The
bootloader msg structure is only 1024+32+32 bytes, so some manufacturers
store more than just a bootloader msg on /misc. fopen in read+append
mode so that only the bootloader msg is written and the rest of the
partition is left untouched.
Change-Id: I2d2fbdf067282744864a19d404ca7dc12f688a98
|
|
|
|
|
|
|
| |
LOGE has been changed to LOGI for "Cannot load volume /misc!"
since many devices do not define a /misc partition in fstab.
Change-Id: I53c440f820fd4614b0af79e9283baa8c48453373
|
|
|
|
|
|
|
| |
Instead of reading it's own fstab, have recovery invoke
fs_mgr to read the unified fstab.
Change-Id: I80c75d2c53b809ac60a4a69f0ef7ebfa707c39e9
|
|
Change-Id: I423a23581048d451d53eef46e5f5eac485b77555
|