Running it before / during the decrypt cycle gives me a dmesg that's extremely similar to Android, but it still fails at the end. I found that /system/bin/qseecomd is supposed to be running during the decrypt cycle. Hopefully someone with more time and fewer devices to maintain can take it a bit further and figure out what is still missing. I/Cryptfs ( 204): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name/userdata, extra_params = fde_enabledĭ/Cryptfs ( 204): test_mount_encrypted_fs(): Master key savedĮ/VoldConnector( 656): NDC Command took too long (5946ms) I/Cryptfs ( 204): load_crypto_mapping_table: target_type = req-crypt Event-4Į/QSEECOMAPI: ( 204): SUCESS::ioctl call to create encryption key for usage 1 success with ret = 0 count 6ĭ/Ulp_jni ( 656): JNI:In update_settings:currentContextType 0, currentGpsSetting 0, currentAgpsSetting 1,currentNetworkProvSetting 0,currentWifiSetting 0,currentBatter圜harging 0,currentEnhLocationServicesSetting 0 currentPipUserSetting 0ĭ/Ulp_jni ( 656): JNI:system_update. I/Cryptfs ( 204): Signing safely-padded objectĭ/QSEECOMAPI: ( 204): QSEECom_dealloc_memoryĭ/QSEECOMAPI: ( 204): QSEECom_shutdown_app, app_id = 2ĭ/ ( 204): HW based disk encryption is enabledĭ/ ( 204): Success loading QSEECom_create_keyĭ/ ( 204): Success loading QSEECom_update_key_user_infoĭ/ ( 204): Success loading QSEECom_wipe_key I/Cryptfs ( 204): Using scrypt with keymaster for cryptfs KDFĭ/QSEECOMAPI: ( 204): QSEECom_get_handle sb_length = 0x2000ĭ/QSEECOMAPI: ( 204): App is already loaded QSEE and app id = 2
I repacked the boot image with some default.prop changes to enable full rooted debugging and got this log from a normal Android decrypt cycle:ĭ/Cryptfs ( 204): crypt_ftr->fs_size = 25920798 I'm not really sure where to take it from here. TWRP should report that it was decrypted successfully meaning that we've properly generated a decrypt key but for some reason the resulting dm-0 block device is not readable. adb shell ln -sf /system/vendor /vendor and wait about 30 seconds then decrypt using the Decrypt button in the lower right. Go to the mount page and mount system and firmware.
Build and boot TWRP using these repos and cherry pick the patch set. The process for using this at this point is somewhat manual. I created this patch set to add some hardware decrypt methods to TWRP's decryption here:
I pushed a couple of changes to my OnePlus One device files here: Unfortunately, the process for decrypting in hardware isn't all that well documented.
The CM 12 nightly for supports some kind of hardware encryption methods that aren't present in AOSP.
That’s it! it will install the files in C:Program Files/Minimal ADB and Fastboot folder). Just below the onscreen instructions & press next.
And Can be used as portable ADB and Fastboot tool. Supports both 32 Bit & 64 Bit OSĪDB and Fastboot with a simple to use installer. Total installation size is around 2 MB whereas Android SDK takes takes about 1.5-2GB after installation. Features of Minimal ADB and Fastboot Tool