Rooting a Cubot King Kong 3 - a few general questions - Android Q&A, Help & Troubleshooting

Hello,
I'm interested in rooting a Cubot King Kong 3 phone (MT 6763 phone), which features Oreo 8.1, and I hope that I am currently posting in the correct forum category.
For my general understanding, I have a few questions and I really that somebody is so kind to help me shed some light on the following:
1. Is it possible to root any random phone just by unlocking the bootloader with ADB, flashing TWRP and then installing SuperSU in the recovery?
Is this the general approach I can use also on the Cubot King Kong 3? Or do I need a TWRP which is modified / customized for this phone? I would like to clarify this, before I do something and brick the phone.
2. What are some safety measures to take, before trying to root, so that I can reinstate the phone to the original state, if something goes wrong?
3. Do I have to disable any kind of data partition encryption so that I can root the phone? Or can I still root the phone without doing this?
4. What is a scatter file and for what is it used? I've read a lot of guides and it seems to be used only with SPFlash. Does this mean, that I do not need this, if root by going the ADB+TWRP+SuperSU route?
5. If after unlocking the bootloader with fastboot, I am getting the message "Orange State Your devices has been unlocked and can't be trusted. " at boot, then what went wrong and can this be fixed?
6. If after flashing the stock ROM, which Cubot provides on their forum, I get a red text "Not Verify" in the upper right corner of the screen every time the phone is on, then what went wrong and can this be fixed?
I am really thankful for your advice, you can't imagine!

---

what i did without sucess
Hey, i'm waiting exactly for the same things! I tested some TWPR, but no one worked at all. I cannot found any Magisk binaries who's look works with kingkong 3.
At the end, i was deseperated, so i try some kingoapp and other oneclick root apps, but without success.
I hope one day, someone with knowlegde and talent will helping us ?

---

As long as OEM/Carrier allows it, phone's Android can get rooted: that's true for all brands/models.
If you flash TWRP Recovery then phone's Stock Recovery gets removed. You have to re-flash phone's Stock ROM to bring it back.
SuperSU doesn't root phone's Android, it's a superuser (AKA root) management tool that allows you to manage which of all of the apps you contain installed gets granted root permission.
A phone's Android is got rooted if su binary ( what is a Linux tool, ~ 100KB ) is present on it's /system partion or any other partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To reiterate:
The typical way to achieve root access on an Android device is to first unlock the boot-loader, which disables verification of the /boot partition. Once the boot-loader is unlocked, the user can introduce a su binary to the system and also a superuser management app to control which processes have access to root. Unlocking the boot-loader is intentionally disabling one of the key security features on the device, which is why the user has to explicitly allow it to happen by typically enabling a toggle in Android's Developer Options and then issuing an unlock command to the boot-loader. With MediaTek-su, a script especially present for devices based on Meditek chipset, however, the user does not have to unlock the bootloader to get root access. Instead, all they have to do is copy a script to their device and execute it in shell.
Note that the user isn’t the only one that can do this, though. Any app on your phone can copy the MediaTek-su script to their private directory and then execute it to gain root access in shell.
Look also inside here