Only functionality i can think of if it's 865. I just told you thak ask1 not the latest and when people root they format anyway, so it doesn't matter. The csc is also doesn't matter, can be jumped off to another csc and firmware if it's not 865.
I followed all the procedures of the OP, everything went well and then successfully flashed and all done. Finally after flashing and upon trying to restart into recovery, the Tab just gives me a continuing bootloop of the following message and completely refuses to go into recovery with the Volume up + Power Button combination (or any other mode actually). Also the Tab cannot be turned off because if I press Volume Down + Power, it auto starts again into the same error splash screen message. No idea what happened. What should I do?
The TWRP version doesn't matter as I did exactly the opposite of you and got stuck the same.. you flashed twrp-3.3.1-1-gts6lwifi.img.tar (official TWRP) instead of TWRP_T860_3.3.1-10P.tar and I flashed the P one.. same same. I could never get it to work again or even get back into recovery or download mode and had to take it to Samsung for an off-warranty paid repair. I keep insisting there is something very strange going on with some of these Tablets.. even of the guides are followed exactly step-by-step, this keeps happening to a few users. I am yet to find a fix and given up trying to get custom recovery or root flashed.Were you able to find a fix to the stuck Samsung logo and inability to power it off completely?
I have the exact same problem with my USA version Samsung Galaxy Tab S6 SM-T860
I followed these instructions exactly EXCEPT that I flashed twrp-3.3.1-1-gts6lwifi.img.tar (official TWRP) instead of TWRP_T860_3.3.1-10P.tar (as shown in the instructions).
Prior to flashing TWRP here is what my tab looked like
adb shell getprop
I thought to include this in case someone else has the same problem and I hope I can prevent someone from pulling their hair out.
When I first flashing and rooted the Tab S6 I noticed after a couple hours/restarts Magisk was not longer installed, only Magisk manager remained. All root access was removed.
After reflashing rooted ROM (failing due to vbmeta aka RMM was triggered) --> flashing stock ROM followed by resetting it by changing clock to bypass 7 day OEM lock --> flashing back to rooted ROM again
only for it to happen again. All in all wasted a good half of a day and was tempted to try again, this time trying TWRP method. I finally re-read the post and realized it stated
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)"
Lo and behold, after holding down Bixby+Volume Up during boot and releasing recovered installed Magisk.
How do you boot into system by holding down Bixby+Volume Up during boot?.. and by Bixby you mean the power button as the S6 does not have a dedicated Bixby button.
Usually (always) holding down Bixby+Volume Up during boot will get you into recovery. If you boot into system with this sequence, then how do you go into recovery?
I can't imagine the headache when android 10 comes along and I need to update