Database Info

[solved] Stuck at boot (even recovery), only fastboot works

I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.

xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779

When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)

xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!

Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.

I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.

cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything

Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.

[Q] Xperia XZs bricked - how to re-lock?

I got this Sony Xperia XZs (G8232, device: keyaki platform: tone) that came pre-installed with Android 8.0 and finally decided to build and install an AOSP image. After activating the OEM unlock under Developer Options I was able to execute the following commands:
Code:
$ fastboot -i 0x0fce oem unlock 0x....
$ fastboot flash boot out/target/product/keyaki/boot.img
$ fastboot flash recovery out/target/product/keyaki/recovery.img
$ fastboot flash system out/target/product/keyaki/system.img
$ fastboot flash userdata out/target/product/keyaki/userdata.img
Note: Sony recommends to use the platform tools version "26.0.2 or older" and that's the version I used.
All these commands came back fine but upon boot the device is stuck at the "Sony" screen early on. To make matters worse I'm unable to get it into fastboot mode to debug.
Holding Power and Volume-Up brings the dreaded "Your device has been unlocked and can't be trusted" screen and boots into the "Sony" screen after 5 seconds where it's stuck.
Holding Power and Volume-Down does nothing. Sometimes it will just boot into the "Sony" screen where it's stuck.
Holding Power and Volume-Up while an USB cable is connected to my computer appears to make an attempt to boot into fastboot mode as the LED is coming on blue but then goes out again. Running "fastboot devices" in a loop while it's doing that brings up nothing.
I connected the phone to a Windows PC and had both Emma and the Sony Xperia Companion installed. Emma appears to have found something on "USB 1" but can't do anything with it. The Xperia Companion is unable to find the device and proposed to run a recovery routine. And then this routine appears to have found the device but aborts early on with "Device has been unlocked" and refuses to continue:
Code:
Boot loader unlocked
Xperia Companion cannot update this device since the boot loader has been unlocked. Please go to
Developer World to get more information on how to restore the device to standard Sony software.
UEGetPhoneInfoRootedDevice
UE_2003
2.1.12.0 / Windows 10 32 bit / Win32 / US
But since I cannot use fastboot to re-lock the device I'm kinda stuck here. Pun intended :-\
Any ideas how to continue?
Update: Holding Power and Volume-Down does get me into the Android Recovery menu where I can Reboot/Reboot to bootloader/Apply update from ADB/..." and now fastboot is able to find the phone - but I'm unable to re-lock the bootloader:
Code:
$ fastboot flashing lock_bootloader
...
FAILED (remote: unknown command)
finished. total time: 0.020s
The same goes for "oem relock" or "oem lock" or "flashing lock_critical". And I think locking the boot loader will be necessary for the Xperia Phone Companion to eventually recover the device.

You are missing the vendor in the log.
I see you did not flash the vendor image.
Download the Vendor image for your version, extract it and flash the image inside.
fastboot flash oem <matching vendor version>.img
https://developer.sony.com/develop/open-devices/downloads/software-binaries
Else try this way to get the stock:
Hold (power and volume +) till it vibrates 3 times.
Install Flashtool.
Download some stock FTF using Xperifirm or any other download links.
Make Flashtool ready to flash the phone now it prompts to connect.
Now holding the vol - button, plug it in; Flashtool starts flashing and its done.
Hope it helps.

@jeoleo7 yes, you're right. In fact, I was trying to get rid of the Sony bloat that came preinstalled and skipped the vendor binaries in attempt to omit those. As I now re-gained control via fastboot I was able to:
Code:
fastboot flash oem ~/SW_binaries_for_Xperia_Android_8.1.6.4_r1_v15_tone.img
...and with that the device now boot. But all is very unstable and the Settings app is crashing as soon as I try to open the (already enabled) developer options. I'll try to get Flashtool working here (doesn't seem to work under Linux and I only have a 32-bit Windows installation at hand, but Flashtool for Windows is 64 bit only) and will report back. Thanks!

cb0gus said:
@jeoleo7 yes, you're right. In fact, I was trying to get rid of the Sony bloat that came preinstalled and skipped the vendor binaries in attempt to omit those. As I now re-gained control via fastboot I was able to:
Code:
fastboot flash oem ~/SW_binaries_for_Xperia_Android_8.1.6.4_r1_v15_tone.img
...and with that the device now boot. But all is very unstable and the Settings app is crashing as soon as I try to open the (already enabled) developer options. I'll try to get Flashtool working here (doesn't seem to work under Linux and I only have a 32-bit Windows installation at hand, but Flashtool for Windows is 64 bit only) and will report back. Thanks!
Click to expand...
Click to collapse
You may try an older version of Flashtool that supports 32bit!!

Thanks, @jeoleo7. Yes, I did that and installed v0.9.18.6 but then I could not get the phone into Flashmode. While Fastboot, for Flashmode it instructs me to
Unplug the device
Power off the device
Press the back button (I assume the Volume-down button is meant by this)
Plug the USB cable
....and I did all this but the prompt just sits there and it's not doing anything. In the console log window I see this:
Code:
09/041/2018 15:41:37 - ERROR - root : this bundle is not valid
09/041/2018 15:41:37 - INFO - Selected Bundle for Sony Xperia XZs (G8232). FW release : 41.3.A.2.171. Customization : Customized US
09/041/2018 15:41:37 - INFO - Preparing files for flashing
...maybe the newer version of Flashtool helps, but then I'd need a 64-bit Windows installation first.
Anyway, disregarding all this - all I really want is to re-lock the bootloader so that this Sony Xperia Companion tool can magically fix the phone again. Is there really no way to re-lock the bootloader with some simple fastboot command?
Code:
$ ~/Downloads/platform-tools_r26/fastboot -h | grep lock
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
flashing lock_critical Prevents flashing bootloader-related
flashing unlock_critical Enables flashing bootloader-related
flashing get_unlock_ability Queries bootloader to see if the device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
$ ~/Downloads/platform-tools_r26/fastboot devices
BXNNN123 fastboot
$ ~/Downloads/platform-tools_r26/fastboot flashing lock
...
FAILED (remote: unknown command)
finished. total time: 0.011s
And for platform-tools_r26.0.2:
Code:
$ ~/Downloads/platform-tools_r28/fastboot -h | grep lock
locking/unlocking:
flashing lock|unlock Lock/unlock partitions for flashing
flashing lock_critical|unlock_critical Lock/unlock 'critical' bootloader partitions.
flashing get_unlock_ability Check whether unlocking is allowed (1) or not(0).
$ ~/Downloads/platform-tools_r28/fastboot flashing get_unlock_ability
FAILED (remote: 'unknown command')
Finished. Total time: 0.013s
The "remote: unknown command" is returned for every other lock command too, no matter which version is used.
Halp!

Most important is you have custom ROM installed and you cannot lock the bootloader.
Get to stock first.
Start with the flashing thing.
1. Install Fastboot drivers:
To install the fastboot drivers you need to disable the drivers checking at startup.
You can do it by "Change advanced startup option > Advanced startup".
An executable file is located C: \Flashtool\drivers
2. Disable Antivirus program.
3. Flash the stock ftf
4. Lock the bootloader
I believe this will solve the issue.
Cheers

Yeah, fastboot is working, but flashmode (whatever that is) was not and the prompt never went away:
View attachment 4593835
Anyway, after installing a usable recovery on the phone I was able to install OmniROM on the phone and finally have a working device again. So, even though the device is still unlocked, it's not a brick any more.

fastboot cannot recognize device but adb can

usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.

Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk

Yes tried from bootloader as well

fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).

redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?

fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.

redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac

What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me

Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.

mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.

billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.

Issue fixed by billyt1's comment above. case closed.

billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.

Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.

I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t

puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.

billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!

I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.

Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day

Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com

Question Fastboot drivers not working

searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated

cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.

cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post

ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...

cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..

cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?

OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9

cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?

mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol

cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.

One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.

tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue

Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers

2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..

I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.

Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol

I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!

Can't unlock bootloader Moto C XT1756

Hey! I need help, please. I'm trying to unlock bootloader of the Moto C XT1756, it has a MT6735. So, I tried in Windows and in Linux (linux with 2 pc). And the problem is next.
I installed ADB and Fastboot (I tried minimal, 15 seconds, platfoorm tools, all). So, ADB detects the device, I can use any adb command like the "adb reboot bootloader". It reboot in fastboot mode and if I use "fastboot devices" it is detected. But when i'm trying to use "fastboot oem get_unlock_data" it says me "failed, unknown command." It happen also with any oem command. I don't know how to proceed. If someone can help me, i'll be grateful. Thanks for read

Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.

Oh. So, I'll test your ADB-FASTBOOT installer, really thanks!

Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.

jwoegerbauer said:
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Click to expand...
Click to collapse
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.

I see you didn't get it.
Manufacturers implement ADB and/or Fastboot with version what corresponds to their ideas.
Hence in your case some ADB and/or Fastboot commands may work or not.

Oh. So, this phone can't be unlocked?

Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"

jwoegerbauer said:
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
Click to expand...
Click to collapse
I didn't get the second sentence. "Use Motorola's "Android USB Driver". Btw, I used "mfastboot.exe devices" and it recognizes my phone, then "mfastboot.exe oem get_unlock_data" and it keeps saying "failed: unknown command."

Update: I tried three different wires. Three different PC (Including Linux-PC) and the error is the same. I can't understand it. It have an option "Unlock OEM" in Developer Settings (so, I think that the manufacturer allows unlock) I can't do nothing.