anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	[MTE] Reset memtag message on factory reset.	Florian Mayer	2022-06-23	1	-0/+7
\| \| \| \| \| \|	Bug: 235255174 Test: https://gist.github.com/fmayer/8900b52636574ee079fa1943e5da918e Change-Id: If42faa0417f9717d66eaa4247a88de61985b21b0
*	Remove support for converting from FDE to FBE	Eric Biggers	2022-03-10	1	-31/+7
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Devices that launched with Android 10 or later require FBE (File Based Encryption) from the beginning, so there's no need to support converting to FBE after the fact anymore. This was only ever a developer option, so it probably wasn't used much. And in any case, it's not used anymore, as isConvertibleToFBE() is hard-coded to return false. Besides the fact that FBE has been required for several releases now, this functionality was only ever available on devices that use FDE (Full Disk Encryption), but FDE support has been removed from Android. Therefore, remove this unused code. Bug: 208476087 Change-Id: I1f56c8e05fb3fba09aab4bf5f8609b0f552b8999
*	Bring up the erase animation early for data wipe	Tianjie	2021-03-03	1	-3/+5
\| \| \| \| \| \| \| \| \| \| \|	Right now the "Erasing" animation displays after the merge step during the FDR process; and the merge can take 3-4 minutes. The users maybe confused about the blank screen and forcefully reboot the device. Bug: 181636823 Test: add sleep merge, check the animation displays correctly. Change-Id: Ib23b1ed3a84e95640271a429c51a3d3c142dc404
*	Force merges to complete before wiping data or metadata.	David Anderson	2019-11-11	1	-0/+7
\| \| \| \| \| \| \| \| \| \| \| \|	After an OTA is applied, a wipe in recovery may overwrite components of dynamic partitions living in userdata. If the OTA has not yet begun merging, we mark the current slot unbootable. If the OTA has begun merging, we wait for the merge to complete. This logic is encapsulated in libsnapshot. Bug: 139156011 Test: manual test Change-Id: Id6544a1b8583afcbba11559d46214ec2e68ffa40
*	otautil: Factor out the utils that're private to recovery.	Tao Bao	2019-10-02	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \|	A number of utility functions are intended for serving recovery's own use. Exposing them via libotautil (which is a static lib) would pass the dependencies onto libotautil's users (e.g. recovery image, updater, host simulator, device-specific recovery UI/updater extensions etc). This CL finds a new home for the utils that are private to recovery. Test: mmma bootable/recovery Change-Id: I575e97ad099b85fe1c1c8c7c9458a5a43d4e11e1
*	Move load & restore logs to logging.cpp	xunchang	2019-04-16	1	-71/+4
\| \| \| \| \| \| \| \| \| \|	We perform these steps to perserve the recovery logs when wiping /cache partition. Move them to logging.cpp to keep the actually EraseVolume function concise. Bug: 130166585 Test: unit tests pass, mount cache and check last log after cache Change-Id: Idc52833817a446f3a0148a3dd2112f911c9ef48d
*	Move wipe cache\|data to libinstall	xunchang	2019-04-15	1	-0/+190
	Therefore, libinstall becomes the sole owner to handle the request from minadbd service. The change also includes 1. move logging.cpp out of librecovery 2. drop the dependency on common.h 3. now it's more sensible to move the wipe_cache as part of install_package. move the wipe_cache to the end of the function. Bug: 130166585 Test: wipe data and cache from menu Change-Id: I6f356dccdb38015c50acf756bac246f87c30fc1f