Bootloader driver issues on Windows 10?

[Waffle265]

I made this post to hopefully help me help you help us.

My Razer Phone is currently unable receive any commands while in fastboot mode/bootloader.

This seems to be a fairly common problem that I see some people are running into without having any concrete solution. I have tried numerous suggestions and then some. Therefore, I want to provide as much information and background to the problem to try and help anyone with more experience that is willing to get to the bottom of this.

So for some background, I successfully rooted my Razer Phone with help from both of these threads:
Rooting Android 9 December Update With Magisk (No TWRP)(Global)
and
[TWRP + MAGISK] FULLPROOF Guide for all Razers! Wifi Fix!

I primarily used the first thread listed to achieve root.

The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.

I am trying to revert to stock and relock my bootloader using Razer's guide HERE. When using the 'flash_all' script that the guide references, the script fails, because the phone cannot receive fastboot commands.

I followed Razer's installation guide PDF to install the adb/fastboot drivers.

I have also tried using ClockworkMod's Universal ADB Driver.
EDIT: I also tried using [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows

The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.

I'm pretty sure I have installed the adb drivers correctly. I can use adb commands while android is running. It's listed when using the "adb devices" command. It successfully restarts and enters the bootloader after typing "adb reboot bootloader", but after typing "fastboot device", it only outputs "< waiting for any device >" and waits. I have also tried using the command "fastboot -i 0x1532 devices" as suggested in a related thread, but this just returns "fastboot.exe: unknown option -- i" and fails.

I have also tried selecting "Android ADB Interface", as well as "Android Bootloader Interface" when installing the google usb driver. I even tried using the third option, no luck.

Now here's why I say that I'm pretty sure that I have the drivers installed correctly:

This is what is displayed in Device Manager when the phone is in fastboot mode and connected to my PC after installing the drivers.
It displays normal when android is running with or without USB debugging enabled.

I have tried this on a few Windows 10 PCs and get the same result. So, I wouldn't be able to tell if this is a Windows problem or if it is my phone:

This is what my bootloader shows. Besides the serial number I blocked out, notice how some data is missing? Could this be the problem?

I'm curious to know the method of root everyone else having this problem had used and whether their bootloader looks like this.

I understand the community for this phone isn't as active as it used to be.
So, thank you to anyone in advance for the help and your time.

 

[tys0n]

This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.

 

[Waffle265]

This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.

I forgot to mention that I had also tried this tool to install the drivers on a few different PCs. I did all of this (including other methods) after making sure to uninstall any drivers that were previously installed. The installation succeeds, but still has no effect on the phone being detected when it's in fastboot. Everything else, like file transfer and adb commands does.

Thank you for your time and for replying.

 

[nthnkirsch1]

I've had the same problems you've had Waffle. I tried everything I could read in the forms, what ended up fixing the driver issues for me was to use Linux. I owe it to Linux's superior driver support that fixed the issue for me.

 

[Waffle265]

Well, I finally got it to work. I decided to try the tool tys0n mentioned again, and it worked. Not sure what I did differently this time, but I am thankful that it is now connecting properly.

Sorry for piggybacking onto my own post but now, after using the razer file to factory reset and lock the bootloader, the screen says "Your device has loaded a different operating system." on boot and some apps still say that the phone is rooted. When accessing the bootloader it says that everything is locked and the OEM Unlocking switch is disabled in developer options. Not sure what I may have done wrong, since it's just running a script for the most part or if it's just stuck like this since I rooted the phone in general.