I've flashed twrp on my s8 and all it did was fail in Odin. Just reboot and that was it
I've
attached screenshots to show commands, etc. This is just to show that you can still use your bootloader locked US Snapdragon with a custom recovery installed (i.e., booting & re-booting normally), it's just that secure boot won't let you access the custom recovery and puts up a scary-looking warning screen that gives the illusion of bricking.
Pic 1: scary-looking warning screen due to rebooting to custom recovery (combo button press to download mode, then press down to boot normally into Android OS)
Pic 2: TWRP download page for S8+ Snapdragon (must extract recovery.img from .tar)
Pic 3: dd commands in root Android terminal to flash downloaded TWRP (after zeroing recovery partition)
Pic 4: 26MAR2017 combo kernel info (tested TWRP with two different combo firmware versions)
Pic 5: 02NOV2017 combo kernel info
Pic 6: flashing with Prince Comsy Odin the latest combo recovery.tar to flash back to normal
Pic 7: Prince Comsy Odin latest combo recovery.tar successful flash
Note: In Pic 6 you will see 4 files from currently latest S8+ combo (archived by 7-Zip into .tar files with store compression level), and the entire ROM of currently latest stock T-Mobile firmware. Relatedly, the only partitions I have that are currently latest combo firmware are:
boot.img,
abl.elf,
devcfg.mbn and
recovery.img. The latest stock T-Mobile system.img.ext4 was pre-rooted by me, dd copied from an actual rooted system partition, then added by 7-Zip to a .tar archive with store compression level to be flashed via SamFail method. I'd been consistently updating system partition with latest stock T-Mobile system.img.ext4 + SuperSU system root zip with FlashFire--prior to the aforementioned dd copying, etc.. As such, the dd copying of the pre-rooted system partition was merely to facilitate making sure SamFail still worked with latest currently available S8+ combo + stock T-Mobile firmware.