summaryrefslogtreecommitdiffstats
path: root/crypto (unfollow)
Commit message (Collapse)AuthorFilesLines
2014-09-03Build block TWRP with RECOVERY_VARIANTMatt Mower4-5/+10
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
2014-02-26Check crypto footer before offering to decryptEthan Yonker4-2/+45
Verify that we have a valid footer with proper magic before setting things up for decryption to help prevent user confusion when dealing with data partitions that fail to mount. Also check to make sure that the block device for /data is present. Change-Id: Ie87818fe4505a8bf71df7d3934c114e7328ef3ca
2013-12-19crypto: Fix crypto dependencies for ICS/Samsung methodsOliverG964-7/+14
- 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-11Add getfooter tool for crypto debuggingDees Troy2-0/+234
Change-Id: I3b9e5f72f3c1c77e41a45d3c94a44f36cc5cbc3c
2013-11-10Update decrypt for 4.4Dees Troy39-477/+5748
Change-Id: I8d5d7b6a49890e4707d70de8b429563de0d2ad99
2013-08-23Fix AOSP decrypt when TouchWiz code is presentDees_Troy2-7/+11
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 Drake5-6/+11
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
2013-04-18Fix CFLAGS for Samsung decryptDees_Troy1-0/+12
2013-04-04Move all AOSP code out of recovery binaryDees_Troy2-0/+27
Improves license compatibility between GPL and Apache Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
2013-03-30Add partition list GUI elementDees_Troy2-2/+2
Add partition list GUI element and update backup, restore, mount, storage selection, and wipe sections of GUI and partition manager code to reflect the new GUI element. Update ORS engine to handle new backup and restore setup. Fix a bug with decrypt. Add 1080x1920 layout. Change-Id: Iaa2f44cb707167e66f935452f076ba00e68a2aa4
2013-01-10More Samsung sdcard crypto fixesDees_Troy2-19/+19
2013-01-09Improve remounting sdcard with ecryptfsDees_Troy1-9/+7
2013-01-08Add Samsung TouchWiz decryptiona39552697-658/+542
Change-Id: I418680e59372160dabfe3e2d5f0208229aa151ae
2012-11-19Workaround for crypto quirk on Nexus 10Dees_Troy1-1/+1
2012-09-21Fix special partition handlingDees_Troy1-27/+27
2012-09-05TWRP-ify AOSP codeDees_Troy11-0/+3418
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 19:37:45 +0100