| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
On devices like the Galaxy Note 8.0, the touchscreen assumes portrait
mode while the recovery is in landscape mode. Allowing to swap x and y
dimension and flipping the x dimension makes the touchscreen usable on
these devices.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
|
| |
This would allow people who gain access to a pin-locked device
to remove the pin and gain access to media. This will still allow
wipes from Android to preserve media.
Change-Id: I73bc9d176297081a41c8d29fc77638d665442fe8
|
|
|
|
|
|
|
|
|
|
|
| |
* Do not require recovery binary to make toybox symlinks. It is not
necessary and provokes a circular dependency warning from make.
* Do not declare toybox symlinks and bu_recovery as additional
dependencies when in one-shot mode. This allows incremental
rebuilding of the recovery binary.
Change-Id: I5ba815ebd4ce5981f8be316ec5ab77272ff565cc
|
|
|
|
|
|
| |
* It's provided by fstools in CM
Change-Id: I62d3fc1c8f9056d3de6150c381680c2f1130fbbf
|
|
|
|
|
|
| |
Reduces recovery footprint by ~306kb.
Change-Id: Ibc2d791b6dbf7e125cd95f753d0b4e46fca1e827
|
|
|
|
|
|
| |
Reduces recovery footprint by ~256kb.
Change-Id: I544c14923859cee394485fac37b8c3822ec31b30
|
|
|
|
| |
Change-Id: Ib6ccf98ed68efacbb3b8c8238945da60b23a20d7
|
|
|
|
|
|
|
| |
This is needed for fugu (Nexus Player) as it has one button on the
bottom.
Change-Id: Ic9f1f546abd90ff9bb6f983bc57628bcb45d641c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Multiple fstab lines (supported in android) cause recovery to fail
to mount partitions if the fs type is not the same as the first
fstab entry. So when we attempt to find an fstab entry that matches
a path for an f2fs, ext4 or vfat type, check it against blkid's
determination of what filesystem type it is. If there is a discrepancy,
query fs_mgr for the next possible entry that matches that path until
either we find one that is good, or run out of fstab entries.
* Also attempt to autodetect the filesystem type for mounting from
update.zips.
Change-Id: Ib6f4535dd88ef714ae1ca6fb0ffae1c7dac0f7ce
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I86bfa73d4004a3b44b3047ee72205a8fa079ec20
|
|
|
|
|
|
|
|
|
|
| |
Provide a means to include device-specific recovery modules that need to
be built (i.e. not pre-built). A list of recovery modules can be
specified by a device with:
TARGET_RECOVERY_DEVICE_MODULES := rec_mod_one rec_mod_two
Change-Id: Ibd19a71318863461d472471a4f7cfddfb1b9ae0d
|
|
|
|
| |
Change-Id: I4ee87f3474aec0496c47bb561ddecc74e151cbbf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement two types of dialogs: info and error. Info dialogs are intended
to show that an operation is in progress and cannot be interrupted. Error
dialogs are intended to show that an error occurred. The user must respond
by dismissing the dialog with any input (a swipe or keypress).
Dialogs may be initiated internally within the UI code or externally via a
named local socket. Dialogs created via socket are presumed to be info
and may not be dismissed. When the client socket is closed, the dialog
automatically dismisses.
Initial implementation shows dialogs for adb backup and restore. Future
work will show dialogs for all errors and lengthy operations.
Change-Id: Icefea12ec0fd70fb487d54aa2eb1cae9dd451355
|
|
|
|
|
|
|
| |
* Conditionally compile support based on TARGET_HAVE_OEMLOCK.
* Use liboemunlock for device specific support.
Change-Id: I1cf1fef8e30075b0586bb86625b7df49723974cb
|
|
|
|
| |
Change-Id: I9e684868ce15aaaed3a40338dadc20b003b50ade
|
|
|
|
|
|
| |
A minimal vold client for recovery.
Change-Id: Id25d955dc1861a910e5f5fc27d9a19e245d66833
|
|
|
|
|
|
| |
* Also update for new pigz version
Change-Id: I93b2c9b659f911cb6fd0646e15dbb48781c254b8
|
|
|
|
|
|
|
|
|
|
| |
* Make sure we create any dirs before trying to put symlinks in them
* Create a new "fstools" target which aggregates all of our filesystem
tools into a single multi-call binary. This reduces the overall
recovery image size by a megabyte, and also removes GPL code from the
main recovery binary.
Change-Id: I5fc2a61d564915085071ccbbcb3136f45c640a60
|
|
|
|
| |
Change-Id: I938dc855742d4e1a5ba0b09fd74851b0d155f0a1
|
|
|
|
|
|
|
|
|
| |
* Secure ADB support
* Toybox applets
* mksh
* Various other tools
Change-Id: I80b0e2aa5eb7142eaa9f157709f4e029077d8dfa
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fork a logger process and send over the log lines through a pipe.
Prepend a timestamp to each line for debugging purpose. Timestamps are
relative to the start of the logger.
Example lines with the change in this CL:
[ 445.948393] Verifying update package...
[ 446.279139] I:comment is 1738 bytes; signature 1720 bytes from end
[ 449.463652] I:whole-file signature verified against RSA key 0
[ 449.463704] I:verify_file returned 0
Change-Id: I139d02ed8f2e944c1618c91d5cc43282efd50b99
|
|
|
|
|
|
|
|
|
| |
Every watch has a (mostly identical) copy of the wear_ui. Factor them
out into a single copy for easier maintenance. Device-specific settings
should be defined in recovery_ui.cpp that inherits WearRecoveryUI class.
Bug: 22451422
Change-Id: Id07efca37d1b1d330e6327506c7b73ccf6ae9241
|
|
|
|
|
| |
Change-Id: Id50c3e6febd0ab61f10a654b9b265cf21a2d1701
(cherry picked from commit 71dc365f25676cfb3f62dbb7163697a8c3c5243d)
|
|
|
|
|
|
| |
And a few trival fixes to suppress warnings.
Change-Id: I38734b5f4434643e85feab25f4807b46a45d8d65
|
|
|
|
|
|
|
|
| |
These are already getting libc++, so it isn't necessary. If any of the
other static libraries (such as adb) use new or delete from libc++,
there will be symbol collisions.
Change-Id: I55e43ec60006d3c2403122fa1174bde06f18e09f
|
|
|
|
| |
Change-Id: I6350618e1e04819d52f1049f9f2fb61c833a1b45
|
|
|
|
|
|
| |
* Fix compilation on yaffs targets
Change-Id: Icd571dce3ee8c232b13ae199df6e0a4feeb7fb68
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mobile Device Theft Protection prevents unauthorized modification
of the system image, ensuring existing of an Anti-Theft solution.
During FOTA, the baseline of the system image which is stored in
a dedicated DIP partition (Device Integrity Partition) is updated
with the baseline of the new received system image.
CRs-fixed: 777015
Change-Id: Ib2ff4bb16db5a08e69432ef3d6d7af26a447dea5
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it easier for us to deal with arbitrary information at the
top, and means that headers added by specific commands don't overwrite
the default ones.
Add the fingerprint back, but broken up so it fits even on sprout's
display.
Change-Id: Id71da79ab1aa455a611d72756a3100a97ceb4c1c
|
|
|
|
|
|
|
| |
Everyone's adding secret key combinations for this anyway, and it's
very useful when debugging.
Change-Id: Iad549452b872a7af963dd649f283ebcd3ea24234
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current abstract class was a nice idea but has led to a lot of
copy & paste in practice. Right now, no one we know of has any extra
menu items, so let's make the default menu available to everyone.
(If we assume that someone somewhere really does need custom
device-specific menu options, a better API would let them add to
our menu rather than replacing it.)
Change-Id: I59f6a92f3ecd830c2ce78ce9da19eaaf472c5dfa
|
|
|
|
|
|
|
|
| |
This eliminated the previous hack, that doesn't work reliably with the
"LOCAL_REQUIRED_MODULES := mkfs.f2fs".
Bug: 19666886
Change-Id: I1f0a2d41129f402c0165f3b86b6fda077291f282
|
|
|
|
|
|
|
|
| |
I think everything left now is here to stay (services.c might get
massaged in to libadbd if it gets refactored).
Bug: 17626262
Change-Id: I01faf8b277a601a40e3a0f4c3b8206c97f1d2ce6
|
|
|
|
|
|
|
| |
adb.h has diverged a bit, so that one will be more involved, but these
three are all trivial, unimportant changes.
Change-Id: Ief8474c1c2927d7e955adf04f887c76ab37077a6
|
|
|
|
|
| |
Bug: 17626262
Change-Id: If41031ba20a3a75fa510f155c654a482b47e409d
|
|\ |
|
| |
| |
| |
| |
| |
| | |
The cryptfs.h files is always included, but its path is only included when TARGET_USERIMAGES_USE_EXT4 is defined.
Change-Id: Iec6aa4601a56a1feac456a21a53a08557dc1d00d
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 17626262
Change-Id: I8ce7cff2b7789f39f35a4211d7120d072c05a863
|
|/
|
|
|
|
|
|
| |
This include path was needed because system/vold/cryptfs.h included an
OpenSSL header just to get the length of a SHA-256 hash. This has been
fixed in https://android-review.googlesource.com/#/c/124477/1.
Change-Id: I06a8ba0ee5b9efcc3260598f07d9819f065711de
|
|
|
|
|
|
|
|
|
| |
Make a fuse filesystem that sits on top of the selected package file
on the sdcard, so we can verify that the file contents don't change
while being read and avoid copying the file to /tmp (that is, RAM)
before verifying and installing it.
Change-Id: Ifd982aa68bfe469eda5f839042648654bf7386a1
|
|
|
|
|
|
|
|
|
| |
Split the adb-specific portions (fetching a block from the adb host
and closing the connections) out from the rest of the FUSE filesystem
code, so that we can reuse the fuse stuff for installing off sdcards
as well.
Change-Id: I0ba385fd35999c5f5cad27842bc82024a264dd14
|
|
|
|
|
|
| |
Instead of LOCAL_ADDITIONAL_DEPENDENCIES.
Bug: 15702524
Change-Id: Ic152ae60354bf09eccdb9a85dcd04f0f076a6422
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds F2FS support
- for wiping a device
- for the install "format" command.
Note: crypto data in "footer" with a default/negative length
is not supported, unlike with "ext4".
Change-Id: I8d141a0d4d14df9fe84d3b131484e9696fcd8870
Signed-off-by: JP Abgrall <jpa@google.com>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
cryptfs.h now includes sha header from libcrypto folder
Change-Id: Icd02c88971aedf96040c3bd9ca759e531546023b
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recovery now draws directly to the framebuffer by rolling its own
graphics code, rather than depending on libpixelflinger.
The recovery UI is modified slightly to eliminate operations that are
slow with the software implementation: when the text display / menu is
turned on, it now appears on a black background instead of a dimmed
version of the recovery icon.
There's probably substantial room for optimization of the graphics
operations.
Bug: 12131110
Change-Id: Iab6520e0a7aaec39e2ce39377c10aef82ae0c595
|
|
|
|
| |
Change-Id: I1541534ee6978ddf8d548433986679ce9507d508
|
|
|
|
|
|
|
|
| |
Older versions of android supported an ASLR system where binaries were
randomly twiddled at OTA install time. Remove support for this; we
now use the ASLR support in the linux kernel.
Change-Id: I8348eb0d6424692668dc1a00e2416fbef6c158a2
|