[Xiaomi Mi 10T / 10T Pro Questions & Answers] Majin Dante:
So I did Try the method you suggested me, I've installed Lineage's Recovery using both the full path method and tried re-installing it while not doing so, in either cases, whenever I try to install a different ROM, I get the Following Error:

deamon not running. starting it now on port 5037 *

* daemon started successfully *

Well, Great. It started successfully. Now I try using adb shell:

* deamon not running. starting it now on port 5037 * What??? I thought it already started...

ADB server didn't ACK

* failed to start daemon *

error: cannot connect to daemon.

Well, Crap. So I open Task Manager and kill adb.exe. Then I run adb shell (without running adb start-server first). This time I get:

* deamon not running. starting it now on 5037

* deamon started successfully

** deamon still not running *

error: cannot connect to deamo

So, As a brief summary - here is what I have tried

Rebooting my

Rebooting my Phon

Executing adb shel

Executing adb start-server and then executing adb shel

Killing ADB and Executing adb shel

Killing ADB and Executing adb start-server and then executing adb shel

Reinstalling my phone's USB Driver

Checking port 5037, It is not in use by any other application, and only becomes used by adb.exe when I start the daemon

.sllllePC:n** *art the daemon.

Honestly, I found this to be pretty Silly since my device IS INDEED connected as again, I didn't install the Fastboot Drivers manually and I can transfer files just fine with the codename for my phone appearing, and thus they were already in the package the First time I've connected the stock USB charger to the Device.

so, maybe I was thinking that I was using an old Version of ADB drivers, and that the Fastboot Drivers were maybe updated but maybe I needed to download the SDK platform tools for ADB, since Android 11 and above Requires API 41, and the obsolete server client version was dated as 39, So android 10 and below.

so, I prompted both the devmgmt.msc Command and Device Manager, and indeed, My device is connected and my Drivers are up to date.

i was thinking that maybe since this is a Universal Charger for Qualcomm Devices, I needed to uninstall the stock USB drivers and use a Universal ADB Driver tool.

I disabled and uninstalled all the paths from the previous ADB platform tool and all ADB interface drivers using the USBdeview app on Windows.

I've created path for the new Universal driver, Again, the TCP Error is still there.

That's as far as ABD shell goes.

In CMD, I get the following Error:

adb server version (39) doesn't match this client (40); killing...

could not read ok from ADB Serve

* failed to start daemo

error: cannot connect to daemo

adb: error: failed to get feature set: protocol fault (couldn't read status): Connection reset by pee

* daemon not running; starting now at tcp:503

* daemon started successfull

- waiting for device

error: protocol fault (couldn't read status): Connection reset by peer

So I did the following things

I ran command which adbwhich gave me the location of the adb that the previous command was using, in my case output was:

which adb

/usr/bin/adb

Then i ran whereis adb command which gave me the location of adb's:

whereis adb

adb: /usr/bin/adb /home/arefin/Android/Sdk/platform-tools/adb

/usr/share/man/man1/adb.1.gz

I get rid of this problem by moving the adb from /usr/bin directory with mv command: (meaning this is of no use thus instead of deleting just put in desktop),

/usr/bin$ `sudo mv adb /home/arefin/Desktop/`

After this i executed this command adb kill-server then ran adb devices. I found everything is fine this time.

My Android development related path in in $HOME/.profile file is, as below:

export ANDROID_HOME=/home/arefin/Android/Sdk

export PATH=$PATH:$ANDROID_HOME/platform-tools

export PATH=$PATH:$ANDROID_HOME/tools

Still the Error was present.

so, Next up I thought that maybe I truly had obsolete versions of my ADB drivers and needed to manually update them from Xiaomi's website.

the conflicting ADB drivers were eliminated, so again, couldn't be.

I've downloaded them, the client Server error disappeared, the TCP 5037 error was back once again.

maybe there truly was something in the USB(5037) port interfering, I searched over the CMD prompt and nothing was found so far.

i've even trying to use another Borrowed USB charger from a Local store in my Zone, nothing at all, and all this was what I went through Yesterday, today I couldn't get my USB cable connected cause whenever I would connect it to the PC, it would automatically disconnect my mouse or they Keyboard.

Given this isn't the first USB cable this happens to me, I honestly just feel like I have a fail unit with a faul USB port. This phone is a lost cause, and I'll probably sell it whenever the new generation of Smartphone comes out.

Again dude, thanks for feeling worry, but I wasn't anxious or tired at all when I wrote this, my idea over this was, and yet still is over what I've originally wrote.

the main reason why I've even bothered Disabling the Thermals in the First place was beacuse of the very little hours of Screen time that I was getting when Frequencies were locked, phone was constantly heating up above 45 grades playing games like League of Legends and even at the lowest graphics I was getting lag spikes.

overclocking the DDR memory channels to 11 and above and setting the GPU clock to 940Mhz through the Konabess app(the maximum Adreno 650 can Ramp up to, everything above that it will give you fake frequencies) actually helped, Before I got stuck with Frequencies running below their full throttle capabilities I was using the ultimate Performance Module through Magisk by Matt Yang, which converts I/O Schedulers and IOP RAM Channels to work in a more similar way to HMP smartphones than EAS Smartphones, unlocking the full potential of the Prime and Performance Cores(in case you don't know, many games lag on Android beacuse EAS software limits performance to efficiency cores to increase efficiency, like in the GTA games), and that alongside Konabess helped me actually decreasing temps, on Wild Rift even at high temps I didn't go above 38 grades which is amazing levels of temperatures, although that probably has a lot to do with me focusing the Cache Bus to L0 GPU turbo from SVS on L1 which the manufacturer selects the GPU usually as stock.

that Helped me have -6-7 hours of gaming screen time, without that I can't go on a 2-3 hours sessions of gaming without the phone turning off.

On top of that, it is a known fact that Xiaomi phones require the device to be at full speed since Xiaomi Memory bottlenecks their RAM, these RAM Channels could hit 4 or 5 GBPS of speed but on Xiaomi phones it usually ramps up to 1 and a half.

on top of that, current GPU smartphones are just weak, a 7 year old GTX 1060 can do 170-160 FPS on 3D mark Wild Life extreme, a current 865 GPU can barely do 20FPS and the CPU performance Is just lackluster.

The 8G1 GPU is actually the only smartphone that currently seems to have had a huge GPU upgrade from 888, ramping up at around 60 to 75 FPS probs with overclock, which is 30 to 45ish FPS more than 888, and I used to have an old Rig with a 1060 some year ago before I overclocked my 7700k with no Cooler and destroyed my motherboard, so an 8 Gen 2 should right about just hit a similar spot to it, and I would be completely fine with Building up some money now and wait for the New generation to hit the fan.

the Exynos 2200's GPU is more powerful than all these, but again, it's built on ANGLE Project, Dolphin Developers even talked about it in their website, they've clearly implied that it was difficult for them at first to even make that GPU to turn on beacuse there were no available GL layers translating from Vulkan at first, so yeah....