[OnePlus 3 & 3T Cross Device Development] bendodge:
Am I totally hosed?

I'm really late to the party here.

Before:

twrp 3.2.3-1

fw 5.0.8

los 2016-06-14

encrypted data; unlocked bl

Flashed:

twrp 3.3.1-0

fw 9.0.3

los 2016-06-21

corrupted data; unlocked bl

I blindly updated. My own fault, to be sure, for not taking a backup. However, I did read the changelogs and even some of the code diffs in Gerrit before flashing everything. Unfortunately, the site I downloaded the OOS build from didn't mention the decryption issue. It's a testament to how well-done everything has been that I've been updating OTA for months with no issues.

I don't mean to be a whiner, but perhaps something of this magnitude could be noted in changelogs/Gerrit, specifically here. I always read the changelogs before updating, but I didn't know this forum thread existed, and it's not easy to wade through. I also don't follow OnePlus or Android news (where I might have found the corruption issue) because I have a life and no intention of buying a new phone anytime soon.

I tried going back to 5.0.8 and 2019-06-14. Decryption in recovery seems successful, but the filesystem won't mount. dmesg says, in part:

[ 5250.071919] synaptics,s3320: all finger up
[ 5254.150907] selinux: avc: denied { set } for property=ro.crypto.state pid=421 uid=0 gid=0 scontext=u:r:recovery:s0 tcontext=u:object_r:vold_prop:s0 tclass=property_service permissive=1
[ 5254.150907]
[ 5254.151037] init: processing action (ro.crypto.state=encrypted) from (/init.recovery.qcom.rc:117)
[ 5254.151077] init: starting service 'sbinqseecomd'...
[ 5254.171413] audit: type=1400 audit(1561217567.139:152): avc: denied { setattr } for pid=540 comm="qseecomd" name="sg2" dev="tmpfs" ino=1764 scontext=u:r:recovery:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
[ 5254.172723] audit: type=1400 audit(1561217567.142:153): avc: denied { read } for pid=540 comm="qseecomd" name="ion" dev="tmpfs" ino=15188 scontext=u:r:recovery:s0 tcontext=u:object_r:ion_device:s0 tclass=chr_file permissive=1
[ 5254.172741] audit: type=1400 audit(1561217567.142:154): avc: denied { open } for pid=540 comm="qseecomd" path="/dev/ion" dev="tmpfs" ino=15188 scontext=u:r:recovery:s0 tcontext=u:object_r:ion_device:s0 tclass=chr_file permissive=1
[ 5254.172791] audit: type=1400 audit(1561217567.142:155): avc: denied { ioctl } for pid=540 comm="qseecomd" path="/dev/ion" dev="tmpfs" ino=15188 ioctlcmd=4900 scontext=u:r:recovery:s0 tcontext=u:object_r:ion_device:s0 tclass=chr_file permissive=1
[ 5254.173459] scm_call failed: func id 0x72000206, ret: -1, syscall returns: 0x0, 0x0, 0x0
[ 5254.174048] scm_call failed: func id 0x72000206, ret: -1, syscall returns: 0x0, 0x0, 0x0
[ 5254.174959] scm_call failed: func id 0x72000206, ret: -1, syscall returns: 0x0, 0x0, 0x0
[ 5254.177123] scm_call failed: func id 0x72000206, ret: -1, syscall returns: 0x0, 0x0, 0x0
[ 5254.178475] selinux: avc: denied { set } for property=vendor.sys.listeners.registered pid=540 uid=1000 gid=1000 scontext=u:r:recovery:s0 tcontext=u:object_r:vendor_default_prop:s0 tclass=property_service permissive=1
[ 5254.178475]
[ 5255.450538] FG: fg_vbatt_low_handler: vbatt-low triggered
[ 5255.995722] QSEECOM: __qseecom_process_incomplete_cmd: fail:resp res= -65,app_id = 0,lstr = 12288
[ 5255.995736] get_ice_device_from_storage_type: found ice device ffffffc16f10d000
[ 5256.080118] get_ice_device_from_storage_type: found ice device ffffffc16f10d000
[ 5256.080561] QSEECOM: qseecom_create_key: Set the key successfully
[ 5256.080710] audit: type=1400 audit(1561217569.049:156): avc: denied { read write } for pid=545 comm="recovery" name="device-mapper" dev="tmpfs" ino=15201 scontext=u:r:recovery:s0 tcontext=u:object_r:dm_device:s0 tclass=chr_file permissive=1
[ 5256.080729] audit: type=1400 audit(1561217569.049:157): avc: denied { open } for pid=545 comm="recovery" path="/dev/device-mapper" dev="tmpfs" ino=15201 scontext=u:r:recovery:s0 tcontext=u:object_r:dm_device:s0 tclass=chr_file permissive=1
[ 5256.080754] audit: type=1400 audit(1561217569.049:158): avc: denied { ioctl } for pid=545 comm="recovery" path="/dev/device-mapper" dev="tmpfs" ino=15201 ioctlcmd=fd03 scontext=u:r:recovery:s0 tcontext=u:object_r:dm_device:s0 tclass=chr_file permissive=1
[ 5256.083784] device-mapper: req-crypt: req_crypt_ctr: Mapping block_device /dev/block/sda15 to dm-req-crypt ok!
[ 5256.083784]
[ 5256.084239] device-mapper: table: 253:0: adding target device sda15 caused an alignment inconsistency: physical_block_size=16384, logical_block_size=4096, alignment_offset=0, start=0
[ 5256.084251] device-mapper: table: 253:0: adding target device sda15 caused an alignment inconsistency: physical_block_size=16384, logical_block_size=4096, alignment_offset=0, start=0
[ 5256.915781] FG: fg_vbatt_low_handler: vbatt-low triggered
[ 5257.154417] audit: type=1400 audit(1561217570.122:159): avc: denied { read } for pid=421 comm="recovery" name="dm-0" dev="sysfs" ino=43101 scontext=u:r:recovery:s0 tcontext=u:object_r:sysfs_dm:s0 tclass=dir permissive=1
[ 5257.154530] audit: type=1400 audit(1561217570.122:160): avc: denied { open } for pid=421 comm="recovery" path="/sys/devices/virtual/block/dm-0" dev="sysfs" ino=43101 scontext=u:r:recovery:s0 tcontext=u:object_r:sysfs_dm:s0 tclass=dir permissive=1
[ 5257.154739] audit: type=1400 audit(1561217570.122:161): avc: denied { search } for pid=421 comm="recovery" name="dm-0" dev="sysfs" ino=43101 scontext=u:r:recovery:s0 tcontext=u:object_r:sysfs_dm:s0 tclass=dir permissive=1
[ 5257.180800] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.181519] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.194142] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.194487] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.205652] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts:
[ 5257.205846] SELinux: initialized (dev sda2, type ext4), uses xattr
[ 5257.214518] EXT4-fs (sde20): mounted filesystem without journal. Opts:
[ 5257.214540] SELinux: initialized (dev sde20, type ext4), uses xattr
[ 5257.221886] EXT4-fs (sde20): mounted filesystem without journal. Opts:
[ 5257.221910] SELinux: initialized (dev sde20, type ext4), uses xattr
[ 5257.231575] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.231854] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.240682] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem
[ 5257.240922] EXT4-fs (dm-0): VFS: Can't find ext4 filesystem

Has anyone ever successfully recovered from this situation? If yes, I'm happy to slog away and post findings. But if the consensus is that I'm truly hosed, I'll start over with a clean install, having lost a few photos and texts but gained a little caution.