0

LG V30+ US998U version Have struggled extensively to get AOSP running on my device. Would wipe data and reboot TWRP; flash DM-verity and no-encrypt also did not help prevent bootloop. But on to my main question(s):

In termux and ADB, ro.crypto.type and ro.crypto.state returned null arguments. Would assume, then, that device was not encrypted, yet the only thing that allowed my phone to boot was calling "adb shell setprop vold.decrypt trigger_restart_framework". Can someone explain to me why that worked? If my phone was truly decrypted?

|improve this question
  • Which android version? adb shell getprop ro.crypto.type should return either block or file and adb shell getprop ro.crypto.state should return encryptedor decrypted. I think pie added another type but I am unsure about that. Also this might help: android.stackexchange.com/questions/195713/… – Bo Lawson Jul 1 at 22:27
  • Android version - going from Oreo, stock, to Pie, AOSP. Phone is rooted but state returns decrypted; type produce no arugments (blank). ALWAYS use format data before installing, followed by a reboot of recovery. – Shahn Taylor Jul 2 at 23:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.