anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	recovery: Switch to clang	Tao Bao	2015-11-16	1	-0/+2
\| \| \| \| \| \| \|	And a few trival fixes to suppress warnings. Change-Id: Id28e3581aaca4bda59826afa80c0c1cdfb0442fc (cherry picked from commit 80e46e08de5f65702fa7f7cd3ef83f905d919bbc)
*	Separate uncrypt into two modes	Tao Bao	2015-05-28	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	uncrypt needs to be triggered to prepare the OTA package before rebooting into the recovery. Separate uncrypt into two modes. In mode 1, it uncrypts the OTA package, but will not reboot the device. In mode 2, it wipes the /misc partition and reboots. Needs matching changes in frameworks/base, system/core and external/sepolicy to work properly. Bug: 20012567 Bug: 20949086 Change-Id: I14d25cb62770dd405cb56824d05d649c3a94f315
*	uncrypt: Switch to C++	Tao Bao	2015-05-06	1	-1/+1
\| \| \| \| \| \| \|	Also apply some trivial changes like int -> bool and clean-ups. Change-Id: I5c6c42d34965305c394f4f2de78487bd1174992a (cherry picked from commit 381f455cac0905b023dde79625b06c27b6165dd0)
*	open misc device in write-only mode	Doug Zongker	2014-08-26	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	Opening the misc block device in read-write mode runs afoul of SELinux, which keeps the wipe code from working. Fix. Also change various things to log to logcat so we can see them happening, for future debugging. Bug: 16715412 Change-Id: Ia14066f0a371cd605fcb544547b58a41acca70b9
*	revert uncrypt back to dynamic linking, fix libs	Doug Zongker	2014-08-14	1	-6/+1
\| \| \| \| \|	Bug: 17029174, 17015157 Change-Id: I1d24f3402875dfb972daa6daef0f385baeff84e9
*	change uncrypt to static linking	Doug Zongker	2014-08-14	1	-0/+2
\| \| \| \| \|	Bug: 17015157 Change-Id: I3c4bdcf4f11d44b617bb731a48413e3707044d1c
*	program to store unencrypted files in an encrypted filesystem	Doug Zongker	2014-01-16	1	-0/+28
	uncrypt can read a file on an encrypted filesystem and rewrite it to the same blocks on the underlying (unencrypted) block device. This destroys the contents of the file as far as the encrypted filesystem is concerned, but allows the data to be read without the encryption key if you know which blocks of the raw device to access. uncrypt produces a "block map" file which lists the blocks that contain the file. For unencrypted filesystem, uncrypt will produce the block map without touching the data. Bug: 12188746 Change-Id: Ib7259b9e14dac8af406796b429d58378a00c7c63