anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add missing includes.	Elliott Hughes	2015-01-30	1	-0/+1
\| \| \| \|	Change-Id: I06ea08400efa511e627be37a4fd70fbdfadea2e6
*	Fix missing #includes in bootable/recovery.	Elliott Hughes	2014-12-29	1	-0/+1
\| \| \| \|	Change-Id: I58dfbac6ca1aa80d3659f53a8fad1bbbbdc9b941
*	create block map for all update packages on /data	Doug Zongker	2014-09-05	1	-12/+9
\| \| \| \| \| \| \| \|	Always create the block map for packages on /data; don't only look at the encryptable/encrypted flags. Bug: 17395453 Change-Id: Iaa7643a32898328277841e324305b9419a9e071c
*	open misc device in write-only mode	Doug Zongker	2014-08-26	1	-18/+26
\| \| \| \| \| \| \| \| \| \|	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
*	clear BCB in misc partition before rebooting	Doug Zongker	2014-08-19	1	-3/+43
\| \| \| \| \| \| \| \| \| \| \|	Something is leaving behind wipe commands in the BCB area of the /misc partition. We don't know what is doing that. It should always be safe to zero out that area from uncrypt, though (because if uncrypt is running then it's got the command we want in the recovery command file rather than the BCB). Bug: 16715412 Change-Id: Iad01124287f13b80ff71d6371db6371f43c43211
*	only do uncryption on packages in /data	Doug Zongker	2014-08-01	1	-1/+1
\| \| \| \| \| \| \|	If recovery is invoked with a package somewhere other than /data, leave it alone. Change-Id: Ief358b53df467ae24a65e30e7a631da59bf13683
*	recovery: 64 bit build issues	Mark Salyzyn	2014-03-19	1	-3/+3
\| \| \| \|	Change-Id: Ie88c49dea13cce5f4eb428e97f5a0956f2656a30
*	Fix a crash when going into recovery mode.	Maxim Siniavine	2014-02-14	1	-1/+6
\| \| \| \| \| \| \| \| \|	When going into recovery mode withoug recovery command file present, uncrypt crashes and the device gets stuck and eventually shuts down. Check that the command file is present before trying to read from it. Change-Id: If0192d597032be0067738e437188d92993ce56f7
*	program to store unencrypted files in an encrypted filesystem	Doug Zongker	2014-01-16	1	-0/+377
	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