msm8996 8.0 Build Says Encryption Unsuccessful on Boot
Opened this issue · 3 comments
I followed the steps to build for OnePlus3T (msm8996 8.0) and made the factory images and ZIP file.
There was an issue with flashing the images, and an issue with flashing the ZIP, but I got around that.
I flashed the OTA zip onto my phone, it shows the Android boot animation and then says Encryption Unsuccessful.
I've tried to factory reset, wipe userdata, format userdata, erase everything, reflash, and more. Nothing works.
Thanks, Nate
@NateDev100 , there is one thing I confused that from where you got the OTA package, and which type of the package(incremental/full).
BTW, can you provide the boot up log(especially for the encryption failed part)?
Sorry for seeing your reply so late. I got the OTA zip by using make otapackage -j6, and it was a full package.
I will get the bootup log, which command do you want me to use for that? logcat? /proc/last_kmsg?
Edit: https://pastebin.com/S7ha0mPz there's a logcat on boot until the decryption unsuccessful message but it might have got cut off. This time I flashed the images directly, but didn't do userdata. I'll try to get a better one tomorrow.
@leonfish77101 - So I flashed every image except recovery as I wanted to keep TWRP, (so boot system and userdata) and then booted up the phone while capturing a logcat. Here it is: https://pastebin.com/9kDC8PmL
The last part in the log stopped there while my 3T was still doing the "android" text as boot animation, and even when it said encryption unsuccessful the log didn't progress further.
EDIT: So it looks like the problem is here:
01-12 16:07:40.314 483 705 D : HW based disk encryption is enabled 01-12 16:07:40.314 483 705 E : get_tmp_passwd: Passed argument is NULL 01-12 16:07:40.669 483 705 E : SUCESS::ioctl call to create encryption key for usage 3 success with ret = 0 01-12 16:07:40.702 483 705 D : HW based disk encryption is enabled 01-12 16:07:40.702 483 705 D : HW based disk encryption is enabled 01-12 16:07:40.702 483 705 I Cryptfs : target_type = req-crypt 01-12 16:07:40.702 483 705 I Cryptfs : real_blk_name = /dev/block/bootdevice/by-name/userdata, extra_params = fde_enabled ice 01-12 16:07:40.811 483 485 D vold : Disk at 254:1 changed 01-12 16:07:40.834 483 705 D Cryptfs : Password is default - restarting filesystem 01-12 16:07:40.862 483 705 D Cryptfs : unmounting /data succeeded 01-12 16:07:40.865 483 705 I vold : [libfs_mgr]Invalid ext4 magic:0x2,/dev/block/dm-1 01-12 16:07:40.880 483 705 I vold : [libfs_mgr]__mount(source=/dev/block/dm-1,target=/data,type=ext4)=-1 01-12 16:07:40.881 602 768 I tftp_server: pid=602 tid=768 tftp-server : INF :[tftp_server.c, 1315] WRQ stats : total-blocks = 1 : total-bytes = 5 : 5 timedout-pkts = 0, wrong-pkts = 0 01-12 16:07:40.881 602 768 I tftp_server: pid=602 tid=768 tftp-server : INF :[tftp_server.c, 1319] WRQ time stats : Total : [TX, RX] = [360, 546, 991950216] 01-12 16:07:40.881 602 768 I tftp_server: pid=602 tid=768 tftp-server : INF :[tftp_server.c, 1323] WRQ time stats : Tx [Min, Max] = [164, 196] 01-12 16:07:40.881 602 768 I tftp_server: pid=602 tid=768 tftp-server : INF :[tftp_server.c, 1327] WRQ time stats : Rx [Min, Max] = [546, 546] 01-12 16:07:40.889 483 705 I vold : [libfs_mgr]__mount(source=/dev/block/dm-1,target=/data,type=ext4)=-1 01-12 16:07:40.889 483 705 E vold : [libfs_mgr]Cannot mount filesystem on /dev/block/dm-1 at /data: Invalid argument
but I don't know how this would be fixed. Seems to be unable to mount /data after putting in the default encryption password and unmounting, but you probably know more than me!