Database Users

ZTE Axon 7 axon7tool failed to connect

Hi there!
I'm newby with android and unlocking the device. My device ZTE Axon 7 A2017G
I want a device running on Lineage os. So I try since 3 days to backup and flash the recovery with axon7tool.
I get always the error message: failed to connect.
I try to install the driver with zadig and now i see the Q...BULK device but still become this error...
I was on android 7.1 B01 and now have downgraded to android 6.0.1 (A2017GV1.0.0B10)
Still the same error.
I changed the computer, still this stupid error.
Can anybody help me, I'm frustrated...

I had this issue and solved it by showing all file extensions in windows. When you rename the recovery.img to recovery.bin you have to make sure that it's actually an BIN file and so you need to have show all file extensions on in the windows settings.

thanks for your answer.
I'm realy shure that I have activated this option, because of other development stuff
Even the first command in each tutorial is not working: "axon7tool -r gpt boot recovery"
When I disconnect my axon and then run the command again I become this error: "Device not connected/found, Failed to connect"
So this means, if I connect the device and I see only the error: "Failed to connect"
the axon7tool see my device but can't connect to them?
p.s. after the downgrad from android 7.1 to 6.0.1 I don't see any updates such as android 7 and I haven't a connection to mobile data (3G/4G). Very frustrated when I want to use whatsapp outdoor

Sorry. I don't know what your issue is then. I'm sure someone else here can help you.

Do you have then Qualcomm drivers installed? If not, try this: QUD.WIN.1.1 Installer-10039.2.zip
If it's still not detected, use the Zadig Tool found here

I had a similar issue. You have to grant admin rights when opening a command window.
Send from ZTE A2017G using Tapatalk

KwesiJnr said:
Do you have then Qualcomm drivers installed? If not, try this:
If it's still not detected, use the Zadig Tool found
Click to expand...
Click to collapse
thank you. What should I select in the wizard when he ask me for the following:
Please choose between WWAN(NDIS6.20) and ETHERNET(NDIS 5.1)
- WWAN-DHCIP is not used to get IPAddress
- ETHNER-DHCP is used to get IPAddress

First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.

KwesiJnr said:
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
Click to expand...
Click to collapse
oh wow! One step further.
The tool waits a second an then I see this error:
C:\Users\bearbeer\Downloads\adb>axon7tool -r boot
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
I dont understand the message.

bearbeer said:
oh wow! One step further.
The tool waits a second an then I see this error:
I dont understand the message.
Click to expand...
Click to collapse
Good, reboot your device into EDL mode once more and try again.

KwesiJnr said:
Good, reboot your device into EDL mode once more and try again.
Click to expand...
Click to collapse
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?

bearbeer said:
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
Click to expand...
Click to collapse
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.

KwesiJnr said:
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
Click to expand...
Click to collapse
thanks again. It works!
What's the next step to become lineageos running on my device? Download and install lineageos or do I need something else before?

If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.

KwesiJnr said:
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
Click to expand...
Click to collapse
Ok I have flashed the TWRP Recovery (not the latest because the latest boot not up) and unlocked the bootloader. What's the Nougat Bootstack and how do I install it?

Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.

KwesiJnr said:
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
Click to expand...
Click to collapse
What's the best way to upgrade the twrp?

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
0. Reboot to TWRP, then copy the desired Recovery Image file you want to upgrade to, (e.g. twrp-3.1.0.0-ailsa_ii.img) to your Internal Storage.
1. Tap Install Image from the lower right corner. Proceed to select the recovery image you just copied to your device.
2. You should now see a radio list. Select Recovery, then swipe to flash.
3. Reboot.
That is all.
Alternatively, you can flash the recovery upgrade file via fastboot, like you did the older version. Just make sure you flash the older version first, THEN the newer. Should work like a charm.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
metpolds said:
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
Click to expand...
Click to collapse
Lmao. I feel you, bro. Pretty convinced he's new to these forums as you guessed, and I'm sure he likely doesn't know about the 'Thanks' system. You know, benefit of the doubt and all.
Ultimately, I just wanted to help out. I know how frustrating it can be with these things so...

Thank you! Ok I'm now on "twrp-3.1.0-0-ailsa_ii.img" and it works.
Yes this is correct. I don't saw the "thanks" button...
I'm so happy that all of you help me. As a newby there are so many threads, tuts, ... an everywhere all goes right. But on my device nothing works at first try. Thank you a lot! :good: :laugh:

A2017g can't reboot to bootloader

So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?

ItsNewDroid said:
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
Click to expand...
Click to collapse
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though

Choose an username... said:
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Click to expand...
Click to collapse
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts

ItsNewDroid said:
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
Click to expand...
Click to collapse
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)

Choose an username... said:
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Click to expand...
Click to collapse
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly

ItsNewDroid said:
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
Click to expand...
Click to collapse
You rooted a lot of phones and don't have ADB lol
Search for 15 seconds adb installer

I already have it installed. It says unauthorized when I run adb devices

ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Unplug the phone, turn it off. Hold only the 2 volume buttons (DON'T TOUCH POWER) and insert the USB-C (plugged to the PC in the other end ofc) while holding the two volume buttons. then check device manager
This should get you to EDL
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Okay after you do that last thing you should get to EDL. Download Zadig, uninstall the Qualcomm QDLoader drivers and tick Delete driver software too. Then go to Zadig and install the driver. After that hold the 3 buttons (pwr, vol) until the led flashes or your PC makes a sound, wait 5 seconds, and you'll be able to run axon7tool.exe -r gpt boot recovery

In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found

ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
That's extremely weird...
Well I guess there's no harm trying to downgrade to marshmallow B03. Download that ancient ROM from raysteff's download center. I did the whole process there. Maybe you'll get fastboot too
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
Thinking about it it's not that weird, I think you're not getting the Zadig part. Did you install the driver through Zadig? How's the device reported aa when on EDL? If you installed the driver properly it should be listed as QUSB_BULK under USB something

Sure I'm not doing something right.
First I did not have Qualcomm drivers installed
I'm in edl with volume buttons and sub. open zadig and install wcid.
From here I did not get it. Hold all buttons vol÷power?

ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"

dnlilas said:
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
Click to expand...
Click to collapse
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one

ItsNewDroid said:
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
Click to expand...
Click to collapse
Please check periodically USB debugging option. I encountered similar problem as your, and before the popup that confirms USB debugging
for the phone, the option is set back to disabled. So maybe you have to check again this option, unplug and replug the phone, choose option MTP,
this should help to have the confirmation popup. Anyhow you must have to reach status "device" which means your phone is able to connect using ADB.
For A2017G B03, it is not necessary, B11 is OK for unlock, TWRP or root using the current guide.
However if you really need it (A2017G B03, B06, B09):
https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3

I suspect that my laptop is causing me trouble as also my g5 will not prompt me with authorization.
I'm gonna use a different laptop without any drivers installed. Can someone tell me all the drivers needed for the a2017g in chronological order so there won't be any conflicts?
In other tutorials they don't mention Qualcomm's driver but in othrrs they are needed.
This phone makes me so frustrated.
So please a step by step from new how to connect to adb on a total new pc. From there I hope I'll manage.
Thanks to all who replied. It's much appreciated.

Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!

the_cyberspace said:
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
Click to expand...
Click to collapse
The command "axon7tool -r gpt boot recovery" only backups your boot and recovery (-r = read, so of course only files *-backup.bin are created inside your PC directory, no change to the phone).
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?

dnlilas said:
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
Click to expand...
Click to collapse
Yes but get an error in adb: cannot read 'rom.zip'

the_cyberspace said:
Yes but get an error in adb: cannot read 'rom.zip'
Click to expand...
Click to collapse
Did you try installing the ROM zip from inside the stock recovery?

dnlilas said:
Did you try installing the ROM zip from inside the stock recovery?
Click to expand...
Click to collapse
I can choose "apply update from ADB" and "apply update from SD card". When i choose the option from SD card i get a error: "sorry, can`t sdcard upgrade" and when i`m flash the rom in adb: "cannot read 'rom.zip' ".

Cannot root or unlock Bootloader

Hi,
I just bought Mi A1.
Now, I wanted to install oreo.
So I was trying to root and install twrp.
Now I'm no expert, I just follow the provided steps and have been successful with past devices.
Note :
1) Developer enabled
2) oem unlocking enabled
3) usb debugging enabled
So I'm using this https://forum.xda-developers.com/mi...l-one-driversunlocktwrpfactory-t3695256/page2
But, there are two issues :
1) When I click on Reboot in fastboot/bootloader mode , it shows this in command prompt : http://prntscr.com/i2sn1o
and in the app, it automatically disconnects from the device http://prntscr.com/i2sncw
2) While this is happening and I leave my device, it automatically goes out from fastboot to power off charging mode.
I tried on another pc too, and followed the steps according to video, still no luck.
And I tried manual methods too, like https://www.youtube.com/watch?v=tRcYUMBgvaI
no luck there either.
Please help.

your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858

riccetto80 said:
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
Click to expand...
Click to collapse
I don't know if there is issue with driver. Because during installation there was no error.
Also, when I command "adb devices" it shows me a device as number.
So it is able to connect to the device then right?

You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.

_mysiak_ said:
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
Click to expand...
Click to collapse
Hmmmmm. Ok, I'll do that then. Thanks buddy. I'll try again and reply back asap.!!

need help

Hello guys, i m facing very serious issue with my device. My volume up button not working at all and when i take my phone to service centre they said they dont have cheap( i didnt know what they said) and they refuse to repair to my phone. Now problem is i m also custom rom lover and try many roms time to time but if i accidenlty mess with my phone and it get brick than how i can go into recovery mode at that situation ?? Please help me if any one know how to go into recovery mode pc using commands. Thank u

I do not understand clearly. Do you have now a working custom ROM? Or now you are on brick/bootloop?
If you have working system:
If ADB -like minimal ADB and fastboot- (and all windowsdriver) is installed on your PC. And USB debugging enabled. And you have a working TWRP.img on your computer for example to minimal ad and fastboot folder. Then.
Connect your phone to PC with USB
Open a command prompt or run "minimal ADB and fastboot" prompt on your PC.
Type on PC prompt: adb devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: adb reboot bootloader (+enter)
The your phone will reboot in fastboot mode.
If you have fastboot mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.
---------- Post added at 06:57 PM ---------- Previous post was at 06:31 PM ----------
My developer friend said: you need to go a private service, and ask him to full button replace. He think, it will be solve your problem.
I found a description http://en.miui.com/thread-84580-1-1.html
bit I am not sure, that is yours.
Maybe...
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.

Thanks for reply ....by the way i have already installed twrp recovery...and the method u said using command is work when my phone in bootloader mode ? Because i cant go into recovery mode at that situation because my volume up button not work

Yes.
Install to your PC minimal adb and fastboot.
https://www.mediafire.com/file/rz87kfzmljiwne4/minimal_adb_fastboot_v1.4.2.exe/file
As I said, if you have fastboot (bootloader) [little green droid with fastboot word] mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.

Volume strip available online

Thank u so much

Please note - this is a general section post. Not android development section post.

[HELP] Attempting to use ADB. fastboot.exe stuck on <waiting for devices>.

Title. I had already gone and installed the Samsung ADB Drivers from the official site listed on the Android Developer Guide.
I then had done the usual process of enabling developer mode on an Android Device (go to about phone, tap on build number 7 times, agree to be developer).
Afterwords I went ahead and enabled USB Debugging for the device and plugged it into my phone. I went ahead and opened CMD and used CD to navigate to the desktop on Windows 10 where I downloaded the latest version of ADB. But when I ran "fastboot.exe adb devices" it is stuck on <waiting for any device> and that there is no change or prompts on my S8 Active. Any advice?
SM-G892A
Android 8.0.0
Android Security Patch Level October 1, 2018

One thing I should probably point out is that I had tested out all 3 of my USB ports on my T420 Thinkpad (all 3 of which are USB 2.0). It is able to give me the MTP Prompt on my phone and that I was able to browse my phone's files VIA Windows Explorer.

digitalcatcher said:
One thing I should probably point out is that I had tested out all 3 of my USB ports on my T420 Thinkpad (all 3 of which are USB 2.0). It is able to give me the MTP Prompt on my phone and that I was able to browse my phone's files VIA Windows Explorer.
Click to expand...
Click to collapse
Update: I decided to instead try to install using adb from a Live Linux Mint USB. I followed the to install adb via Terminal, connected the S8 Active, abd.. it worked! I got the required promt to use Developer Permissions and I was able to do what I needed to do with adb. For now, the problem seems to rest with my current Windows install.

The US s8s don't have fastboot
---------- Post added at 01:48 PM ---------- Previous post was at 01:46 PM ----------
digitalcatcher said:
Update: I decided to instead try to install using adb from a Live Linux Mint USB. I followed the to install adb via Terminal, connected the S8 Active, abd.. it worked! I got the required promt to use Developer Permissions and I was able to do what I needed to do with adb. For now, the problem seems to rest with my current Windows install.
Click to expand...
Click to collapse
Don't know what your trying to do but if it's fastboot it's not gonna work. We have locked boot loaders and no fastboot

TheMadScientist said:
The US s8s don't have fastboot
---------- Post added at 01:48 PM ---------- Previous post was at 01:46 PM ----------
Don't know what your trying to do but if it's fastboot it's not gonna work. We have locked boot loaders and no fastboot
Click to expand...
Click to collapse
Sorry, I should have specified that I was trying to run adb and not fastboot. The "fastboot" I was referencing was part of the syntax in Windows needed to run adb commands in Command Prompt such as:
"fastboot.exe adb devices"
(Its probably wrong, it's been awhile since I tinkered with adb)