Samsung Tab 4 7.0 / SM-T235: no boot to recovery with official V 3.6.2_9-0, and boot problems with V 3.6.0_9-0

[x ] I am running an official build of TWRP, downloaded from https://twrp.me/Devices/
[ ] I am running the latest version of TWRP
[ x] I have read the FAQ (https://twrp.me/FAQ/)
[ x] I have searched for my issue and it does not already exist

Device codename: Samsung Tab 4 7.0 / SM-T235 (degaslte) TWRP version: 3.5.2_9-0-degas

flashed twrp-3.6.2_9-0-degas.img from existing twrp 3.5.2_9-0-degas (which works fine). Reboot to recovery
flashed twrp-3.6.0_9-0-degas.img from existing twrp 3.5.2_9-0-degas (which works fine). Reboot to recovery
no apparent problem when running with twrp_3.5.2_9-0-degas

device is rebooted to newly flashed twrp version

(twrp 3.6.2) device stops booting at the SAMSUNG logo. In the upper left corner of the screen a red alert message tells me that "recovery is not SEANDROID enforcing". Boot process stops there and can only be forced to to shut down
(twrp 3.6.0) at boot while showing the SAMSUNG logo, the same red alert message is showing. Different from twrp 3.6.2, after a while the message turns from red to blue then another second later the device boots into TWRP. From there everything seems to be working as expected. Same behaviour repeats upon every boot to recovery
EDIT: Additional info, don't know whether this is related: I cannot connect my PC through ADB via USB while device is in TWRP (any working version). I can however access internal memory and SD card while device is in recovery mode. And ADB connect is fine when device is booted into system, and USB connect mode is either "file transfer" or "PTP" mode.

unknown

/tmp/recovery.log: (see below) dmesg: (see below)

(twrp 3.6.2): cannot not get into twrp therefor no recovery logs
(twrp 3.6.0): cannot access paste.omnirom.org. Instead attached recovery.log and dmesg.log here dmesg.log recovery.log

TeamWin / android_bootable_recovery