[Samsung Galaxy Tab E  ROMs, Kernels, Recoveries, &] pstglia:
Thanks a lot. By checking logcat now we can see it's on a loop trying to connect to installd:

07-31 08:45:45.947 494 494 I InstallerConnection: connecting...
07-31 08:45:45.950 494 494 I InstallerConnection: disconnecting...
07-31 08:45:45.950 494 494 E InstallerConnection: connection failed
07-31 08:45:45.951 494 494 W InstallerConnection: installd not ready
...
07-31 08:47:10.097 494 494 I InstallerConnection: connecting...
07-31 08:47:10.098 494 494 I InstallerConnection: disconnecting...
07-31 08:47:10.098 494 494 E InstallerConnection: connection failed
07-31 08:47:10.098 494 494 W InstallerConnection: installd not ready

I suspect the cause installd is not firing up is due missing efs partition. Dmesg shows it wasn't able to mount it:

[ 2.984436] [1: init: 139] [c1] EXT4-fs (mmcblk0p17): Ignoring removed nomblk_io_submit option
[ 2.984710] [1: init: 139] [c1] EXT4-fs (mmcblk0p17): bad geometry: block count 179200 exceeds size of device (5120 blocks)
[ 2.984802] [1: init: 139] [c1] fs_mgr: check_fs(): mount(/dev/block/platform/sprd-sdhci.3/by-name/efs,/efs,ext4)=-1: Invalid argument
[ 2.984863] [1: init: 139] [c1] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/sprd-sdhci.3/by-name/efs
[ 3.013702] [1: init: 139] [c1] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 3.013763] [1: init: 139] [c1] e2fsck: Error reading block 164358 (Invalid argument). Ignore error? yes
[ 3.013793] [1: init: 139] [c1] e2fsck:
[ 3.013854] [1: init: 139] [c1] e2fsck: Force rewrite? yes
3.013885] [1: init: 139] [c1] e2fsck:
[ 3.013916] [1: init: 139] [c1] e2fsck: Superblock has an invalid journal (inode 8).
[ 3.013946] [1: init: 139] [c1] e2fsck: Clear? yes
[ 3.013977] [1: init: 139] [c1] e2fsck:
[ 3.014007] [1: init: 139] [c1] e2fsck: *** ext3 journal has been deleted - filesystem is now ext2 only ***
[ 3.014038] [1: init: 139] [c1] e2fsck:
[ 3.014068] [1: init: 139] [c1] e2fsck: Superblock has_journal flag is clear, but a journal inode is present.
[ 3.014099] [1: init: 139] [c1] e2fsck: Clear? yes
[ 3.014129] [1: init: 139] [c1] e2fsck:
[ 3.014160] [1: init: 139] [c1] e2fsck: The filesystem size (according to the superblock) is 179200 blocks
[ 3.014221] [1: init: 139] [c1] e2fsck: The physical size of the device is 5120 blocks
[ 3.014251] [1: init: 139] [c1] e2fsck: Either the superblock or the partition table is likely to be corrupt!
[ 3.014282] [1: init: 139] [c1] e2fsck: Abort? yes
[ 3.014312] [1: init: 139] [c1] e2fsck:
[ 3.014343] [1: init: 139] [c1] e2fsck: Error writing block 164358 (Invalid argument). Ignore error? yes
[ 3.014373] [1: init: 139] [c1] e2fsck:
[ 3.014404] [1: init: 139] [c1] e2fsck:
[ 3.014434] [1: init: 139] [c1] e2fsck: /dev/block/platform/sprd-sdhci.3/by-name/efs: ***** FILE SYSTEM WAS MODIFIED *****
[ 3.014495] [1: init: 139] [c1] e2fsck: e2fsck terminated by exit(9)
[ 3.015502] [1: init: 139] [c1] EXT4-fs (mmcblk0p17): bad geometry: block count 179200 exceeds size of device (5120 blocks)
[ 3.015624] [1: init: 139] [c1] fs_mgr: __mount(source=/dev/block/platform/sprd-sdhci.3/by-name/efs,target=/efs,type=ext4)=-1
[ 3.016235] [1: init: 139] [c1] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/sprd-sdhci.3/by-name/efs at /efs options: noauto_da_alloc,discard,journal_async_commit,errors=panic error: Invalid argument

The device I tested, this partition was mounted and checked as ext4 without problems

Just to confirm: Have you enabled any encryption on your device / partitions?

## WARNING - THIS MAY BRICK YOUR DEVICE PERMANENTLY - BE SURE YOU UNDERSTAND THIS BEFORE PROCEED ##

u can try to format your efs partition AT YOUR OWN RISK (see [1] as reference ).

- Confirm if your device is "mmcblk0p17"

ls -l /dev/block/platform/sprd-sdhci.3/by-name/efs

- Boot twrp, connect through adb and format it as ext4:

mke2fs /dev/block/platform/sprd-sdhci.3/by-name/efs
mount -w -t ext4 /dev/block/platform/sprd-sdhci.3/by-name/efs

- Finally, reboot your device and wait until 5 minutes if Lineage will fire up. Meantime, you can connect adb and check logcat/dmesg (you can add the verbosity cmds I passed last post)

Remember:

Just try this if you are aware of the risk

. You may lose your device. Not kidding

[1] - https://xdaforums.com/galaxy-j7/how-to/fix-samsung-e-failed-to-mount-efs-t3870637