Problem booting into TWRP recovery when rooting SAMSUNG Galaxy XCover 3 (SM-G389F) I am trying to root SAMSUNG Galaxy XCover 3 (SM-G389F) with Android 6.0.1. I successfully flash the latest TWRP (twrp-3.0.2-0-xcover3ltexx.img.tar official site) with Odin 3.12. 

In Odin I intentionally disabled Auto Reboot, so that I try to boot into TWRP recovery in the first phone boot by holding down (Home + Volume UP + Power key). Instead of booting into recovery the phone gets stuck on SAMSUNG Galaxy screen as shown in video link. After normal reboot my phone boots up as normal but this action puts back stock recovery.

To solve the problem I tried all available TWRP's, tried to factory reseat and clear phone cash several times before flashing recovery image, tried to use various Odin versions (3.07, 3.10, 3.12).

What else can I try? 

Thanks for suggestions.
This is usually an issue with your root method NORMALLY means it is using an older bootloader than the minimum allowed (through OTA updates the minimum allowed bootloader version can change).  When the phone goes to boot using the new loader in to recovery it is hanging.  Once you restart the changes are reversed because the device is not fully rooted and the newly installed TWRP is being overwritten by the backup of the OEM recovery because it can tell there is some issue with the recoery (whether the install signature fails, the method they use to get root is patched, etc.).  I would look around for an updated root method and be sure you follow it step by step.

This appears to be the newest set of instructions for your device:
http://www.galaxyrom.com/2016/04/update-galaxy-xcover3-sm-g389f-g389fxxu1apc7-android-6-0-1.html

I would also if you can do a factory reset, and reinstall or install if it is not already to the current OEM ROM version mentioned on that page (linked there).  This way you are sure you are rooting exactly what is expected by the rooting process.

So Update ROM if needed and then further down the page is root directions.  Note they say to make sure auto reboot is checked as part of the instructions so this may be a requirement (a script or other software may be expecting it to do something).