[OnePlus 7T Questions & Answers] GowCow:
Hi there!

I have a Oneplus 7T which is my daily driver, and I was disappointed in the stock OS, aka, OxygenOS.

And I wanted to have a little fun and use Pixel Experience OS, DerpFest OS or some sort, also note that I am a beginner in these things.

So day one, I successfully installed Pixel Experience OS on my Oneplus 7T - I connected the phone to my computer, installed Platform Tools and the computer and phone both picked each other up, I booted into bootloader (initially my computer couldn't pick up signal from the phone, so I installed the driver by first installing that 15 Second ADB Installer, and then installed the USB driver and link it to the phone from Device Manager and from there), unlocked the bootloader, and flashed the recovery image of PixelExp OS onto my phone, and sideloaded the actual PixelExp ROM onto my phone, and it went perfectly, my phone booted and it was in Pixel Experience ROM ‼ but then I wanted to check Derpfest version Android 14, so I installed that through the same steps I did above but then something ****ed up so I was nervous, so I looked on YouTube and Google on how I can revert back to stock OS and I did, through an application called "FastbootEnhance.exe" where I flashed payload.bin file (I tried using the MSM tool but it did not detect my device at all so I had to use this FastBootEnhance app) for Oneplus 7T. And then stock ROM came back, but I still wanted to see Derpfest and I tried installing it again with the same steps as above, and this time it worked. But I was disappointed with Derpfest, so I made up my mind and I was going to use Pixel Experience rom on this phone as a daily driver and not any other OSes, so I tried installing Pixel Experience from Derpfest, but then something ****ed up again, so I went to the "FastbootEnhance.exe" and clicked flash payload.bin, but this is when I accidentally clicked the power button file on Derpfest's FastbootD mode, which rebooted the device while Oneplus's stock rom was being flashed.

But, my phone did boot up to the stock OS fine. So now I was gonna try installing Pixel Experience on my Oneplus 7T right?

The problem is my phone can be detected by ADB on my computer while it's in stock rom, or by FASTBOOT on my computer while it's in bootloader, all commands work till there, I am able to flash images, and reboot, check "adb devices & fastboot devices" it works, but once I am in the recovery mode or the fastbootD mode, the phone decides to lose contact with my computer, it worked while I was in Derpfest's & PixelExp's ROM image, why isn't it working now? I tried "fastboot devices" and "adb devices" nothing works, I reinstalled ADB drivers, redownloaded Platform Tools, did everything as before but nothing works. But in my device manager, the phone is coming up as "Kedacom USB" as shown below

View attachment 6074444

So I thought, Kedacom is a driver that I should download, so I go to YouTube and I find this video where they have Kedacom drivers so I install them, and then link them to my phone through Device Manager:

View attachment 6074445

But still no response: I HAD ALSO UED ADB DEVICE DRIVERS, ADB COMPOSITE USB DRIVE, etc.

View attachment 6074447

I assure you that this worked before during Derpfest recovery image and PixelExp recovery image (and the phone was detected during bootloader and Oneplus stock rom), so why isn't it working now? The cable isn't the issue, the driver isn't the issue (I hope), I even tried it in another computer, still same issue.

I feel like when I accidentally clicked the reboot from Derpfest FastbootD while the payload.bin / Oneplus stock rom was flashing, something broke and now my phone isn't being identified by the computer while it's in recovery / fastbootD mode.

But now how can I fix this when I cannot contact my phone through CMD when it's in the recovery mode or fastbootd mode, I can flash all sort of endless recovery images, but I won't be able to do anything from them because my computer won't see it.

View attachment 6074450

Any fixes? Is it driver issue or my phone issue and how will I repair it?