Database Users

Device not listed in fastboot

My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?

cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
You try install mi pc suite

cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
had experienced this before. Do you use Windows 10 ?

Install MiPc suit
N u r done!

kpratama24 said:
had experienced this before. Do you use Windows 10 ?
Click to expand...
Click to collapse
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works

cypherx1998 said:
Yes..i do use windows 10....the solution that worked for me this time is to delete every driver of my phone present in my pc and connecting it....by every driver i mean each and every one(inclusive of adb and fastboot and also usb drivers)...so pc installs a driver by itself and surprisingly it works
Click to expand...
Click to collapse
Good to hear that.

cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
Download Adb and fastboot.rar from google.
Extract it to desktop.
Then install Miflash , downloaded from google.
And for fastboot watch video from youtube.
If you are again unable to found or for any type of help.
I'll provide you the files with the video.

cypherx1998 said:
My device is not listed in fastboot devices. However it can be seen in adb mode. I have tried doing:-
1)entering in fasboot manually as well as via "adb reboot bootloader" command.
2)Updating drivers or installing them manually(tried several of them, but none works)
List of drivers that i have tried
1.Universal adb driver by koushik dutta
2.Samsung adb driver
3.Google sdk drivers
4. Installing some random unsigned driver(Last method done)
Please help me i want to revert back to miui by flashing it clean via Flash tool but device isnt detected what to do?
Click to expand...
Click to collapse
download MI Pc suit http://pcsuite.mi.com/
and you won't be needing drivers. and your device would be listed.

Windows 10 laptop can't detect softbricked Nexus 4, TWRP, no OS

I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?

The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.

I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.

first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/

For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.

i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!

elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?

If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.

You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.

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' ".

Can't flash factory image : waiting for device

Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.

basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.

Also, if you have USB 2 ports, try one of those. I couldn't get anything to flash when I had it plugged in one of my USB 3 ports.

Could be cable issue, USB port issue, driver issue or you can try updating your adb setup etc... I used the Minimal ADB and Fastboot. Mine was out of date and wouldn't recognize device in fastboot after the Oreo sideload.
Works perfectly with the Essential official drivers in Win8.1Pro now.

The cable is brand new by anker, and works perfectly. Drivers and adb are updated.

mrcooter said:
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Click to expand...
Click to collapse
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?

basongwe said:
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
Click to expand...
Click to collapse
Something that was odd that may help (assumed it was just my environment setup). I had adb installed to C:\adb and only way fastboot will work consistently for me is to run commands from that directory. Could be unrelated but thought I would mention it.

basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Try copying fastboot to the folder that has the flash all.bat

What operating system?

Where did you get your driver's?
Reason I ask is at first I had driver's auto install from a Samsung device that I used previously. Caused an issue where it wouldn't start the fastboot process and device got stuck at first step.

Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds

vergilbt said:
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
This also did the trick for me

You're welcome...

Edit : I have it(drivers from essential website)

Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.

723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
That did the trick.

723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update

un1ocked said:
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
Click to expand...
Click to collapse
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".

kt-Froggy said:
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
Click to expand...
Click to collapse
fastboot version 28.0.3-5475833
Installed as C:\Program Files (x86)\Essential\ADB\fastboot.exe
EDIT:
problem solved by switching to an old PC with a pure usb 2.0 port

un1ocked said:
problem solved by switching to an old PC with a pure usb 2.0 port
Click to expand...
Click to collapse
Ahh... Yeah, that's often the issue. Still doesn't make a lot of sense to me, because your error msg was "unsupported option". Well, good that it worked for you.

Fastboot not working

So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.

Try different usb cable or usb 2.0 port

I had similar issue, fastboot was detected but haven't been able to do any command. So when the phone was powered on with selected usb to transfer files, in device manager the phone was listed as "Android phone - Android Composite ADB Interface", I updated the driver to "ADB Interface", rebooted in bootloader and was able to communicate through fastboot.

bpodnar said:
Try different usb cable or usb 2.0 port
Click to expand...
Click to collapse
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault

alkesh95 said:
So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.
Click to expand...
Click to collapse
I hope drivers are up to date.

alkesh95 said:
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault
Click to expand...
Click to collapse
Did u tested this? Reboot to fastboot mod and connect mobile to pc. then right click my computer then device manager. Then check for A1 port. Update /install driver Automatically from internet. May be it will help , may be not.

ADB drivers are different than fastboot. If you can detect with ADB and not fastboot, I would suspect you have a driver problem. Boot into fastboot, then check device manager for your device. It might not have any drivers installed and be an unrecognized device, or it could have incorrect drivers installed. My device needed fastboot drivers, I had the same problem as you.

Thanks all of you. Fastboot driver was the issue.

alkesh95 said:
Thanks all of you. Fastboot driver was the issue.
Click to expand...
Click to collapse
I have the same problem, can you send me the fastboot driver please?

vu2pmc said:
I have the same problem, can you send me the fastboot driver please?
Click to expand...
Click to collapse
Follow the step. Windows will download correct driver automatically