[Oukitel (All phone models)] sieger007:
-- adb shell on w7 does recognize device. In Fastboot mode `fastboot devices` will not recognize the phone. Are there separate fastboot drivers. I installed drivers from company website .

-- on a 2nd note. They use a tool called flash tool a CCP tool that does not fuss to much on checking files. These are the files in the offical ROM

2gb_TF919_OQ_S89_6833_R0_EEA_V2.8.3.1_S231121/TF919_OQ_S89_6833_R0_EEA_V2.8.3.1_S231121 # lr
total 4106408
-rwxrwxrwx 2 root root 392460 Nov 21 2023 preloader_tf919_oq_s89_6833_r0_eea.bin
-rwxrwxrwx 2 root root 4096 Nov 21 2023 vbmeta_vendor.img
-rwxrwxrwx 2 root root 4096 Nov 21 2023 vbmeta_system.img
-rwxrwxrwx 1 root root 4096 Nov 21 2023 vbmeta.img
-rwxrwxrwx 2 root root 14784 Nov 21 2023 spmfw-verified.img
-rwxrwxrwx 1 root root 11088 Nov 21 2023 spmfw.img
-rwxrwxrwx 2 root root 5776 Nov 21 2023 pi_img-verified.img
-rwxrwxrwx 1 root root 2080 Nov 21 2023 pi_img.img
-rwxrwxrwx 2 root root 64721280 Nov 21 2023 md1img-verified.img
-rwxrwxrwx 1 root root 64710144 Nov 21 2023 md1img.img
-rwxrwxrwx 2 root root 148064 Nov 21 2023 dpm-verified.img
-rwxrwxrwx 1 root root 136976 Nov 21 2023 dpm.img
-rwxrwxrwx 2 root root 661040 Nov 21 2023 sspm-verified.img
-rwxrwxrwx 1 root root 657344 Nov 21 2023 sspm.img
-rwxrwxrwx 2 root root 413232 Nov 21 2023 scp-verified.img
-rwxrwxrwx 1 root root 405840 Nov 21 2023 scp.img
-rwxrwxrwx 2 root root 444320 Nov 21 2023 mcupm-verified.img
-rwxrwxrwx 1 root root 440624 Nov 21 2023 mcupm.img
-rwxrwxrwx 2 root root 1170672 Nov 21 2023 lk-verified.img
-rwxrwxrwx 1 root root 1163280 Nov 21 2023 lk.img
-rwxrwxrwx 2 root root 2033072 Nov 21 2023 gz-verified.img
-rwxrwxrwx 1 root root 2029376 Nov 21 2023 gz.img
-rwxrwxrwx 1 root root 41943040 Nov 21 2023 boot.img
-rwxrwxrwx 2 root root 41943040 Nov 21 2023 boot-debug.img
-rwxrwxrwx 2 root root 977632 Nov 21 2023 tee-verified.img
-rwxrwxrwx 1 root root 970240 Nov 21 2023 tee.img
-rwxrwxrwx 2 root root 3054480 Nov 21 2023 logo-verified.bin
-rwxrwxrwx 1 root root 3050784 Nov 21 2023 logo.bin
-rwxrwxrwx 2 root root 64304 Nov 21 2023 dtbo-verified.img
-rwxrwxrwx 1 root root 8388608 Nov 21 2023 dtbo.img
-rwxrwxrwx 1 root root 2343188 Nov 21 2023 userdata.img
-rwxrwxrwx 1 root root 3962446632 Nov 21 2023 super.img
-rwxrwxrwx 2 root root 83929 Nov 21 2023 MT6833_Android_scatter.xml
-rwxrwxrwx 2 root root 50629 Nov 21 2023 MT6833_Android_scatter.txt
drwxrwxrwx 1 root root 4096 Nov 21 2023 DATABASE
drwxrwxrwx 1 root root 8192 Nov 21 2023 .

I wonder if its poss to open super.img and remove company firmware but instead put GSI ROM ? Concurrent with that you have to make changes in the layout info and tell that now super.img is xxx mb but use to be yyy mb . I think you do that in the scatter file ?

I used took a peep into this rabbit hole to see if its poss to do that

mount -o loop super.img /mnt/super
NTFS signature is missing.
Failed to mount '/dev/loop7': Invalid argument
The device '/dev/loop7' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
2gb_TF919_OQ_S89_6833_R0_EEA_V2.8.3.1_S231121/TF919_OQ_S89_6833_R0_EEA_V2.8.3.1_S231121 # xarchiver super.img

not much luck super.img does not mount ordinarily . Can someone help me on fastboot

3) how do I get these drivers working for Linux. Company provides w7 drivers