summaryrefslogtreecommitdiffstats
path: root/crypto/fs_mgr (unfollow)
Commit message (Collapse)AuthorFilesLines
2014-09-03Build block TWRP with RECOVERY_VARIANTMatt Mower1-1/+3
Enable TWRP to reside alongside other recoveries with the naming convention: bootable/recovery(-flag). If TWRP resides at bootable/recovery and a device does not specify RECOVERY_VARIANT, then it will build like normal. If TWRP resides at bootable/recovery-twrp, then its makefiles will only be parsed if a device specifies 'RECOVERY_VARIANT := twrp'. This prevents TWRP specific makefile warnings/errors (notably, missing DEVICE_RESOLUTION) when another recovery is being built. Change-Id: I8f02fffcd79c309c7123b9428eedc69af02e126e
2013-12-19crypto: Fix crypto dependencies for ICS/Samsung methodsOliverG961-2/+2
- libmincrypt renamed to libmincrypttwrp that is an static library - libjpegtwrp does not exist - libfs_mgrtwrp is for JB decryption methods This fixes making full builds when TW_INCLUDE_CRYPTO_SAMSUNG := true and TW_INCLUDE_CRYPTO := true are set. Somehow typing make recoveryimage doesnt push the mentioned issue. Change-Id: I7cad5db4f51152a1a8209e619b188ca88d7c74d1
2013-11-10Update decrypt for 4.4Dees Troy7-143/+964
Change-Id: I8d5d7b6a49890e4707d70de8b429563de0d2ad99
2013-08-11Fix conflict with getline in 4.3 treeDees_Troy1-3/+3
Change-Id: I5accf8731829229d153a657c9290a7be83f87a03
2013-07-03Add additional build variable checks to Android.mk filesTrevor Drake1-1/+2
This was causing the mm command to fail when it was run from bootable/recovery and no crypto features had been specified in a device's configuration files Change-Id: Iddbeea5349bbf75cddb0250cd71821dfe3b7b9d8
2012-11-19Workaround for crypto quirk on Nexus 10Dees_Troy1-1/+1
2012-09-05TWRP-ify AOSP codeDees_Troy5-0/+860
Pull in most TWRP sources Stub out partition management code Make it compile -- probably will not boot Kind of a mess but have to start somewhere