Database Users

N1 Windows Drivers problems

Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you

http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/Posted Yesterday, 10:17 PM
ATT N1's can run CyanogenMod without any real trouble. The commands and guides remain the same as the Tmo N1
THE ONLY CAVEAT IS: YOU CANNOT USE CM 5.0.5.1 or 5.0.5.2 as your initial install base, as these releases were bugged. Use 5.0.5 here
For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Setup ADB/FASTBOOT
Fastboot oem unlock
fastboot flash recovery recovery-ra-blah-blah.img
Reboot into recovery
NANDROID
WIPE!!!! (if you dont wipe you get boot loops)
Flash CM
Flash Google (optional)
Reboot
Fastboot flash radio radio.img (unnecessary on ATT n1's)

cheloman said:
Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
Try those drivers.

jerrycycle said:
...For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Click to expand...
Click to collapse
jerrycycle said:
fastboot flash recovery recovery-ra-blah-blah.img
Click to expand...
Click to collapse
Thank you by your post, it was very usefull and I could change my drivers, so I have access in debug mode to my n1. Even with this, Ive tried to apply the root with modaco´s files, using the original ERE27 pack, but, it just stucks in "copying...".
Maybe the problem is that I was instructed about I should execute the .bat, in bootloader moder (no in fastboot). I have the adb commands with fastboot mode, but, when I do: fastboot devices in bootloader mode, I dont have any device. Maybe the tutorial that I followed its wrong and should I execute directly in fastboot not in bootloader.
Anyway, Ive quoted your post, because when you say that isnt necessary, the instructions of recovery installation, says about its a "pre-requirement"
You can check it in /showthread.php?t=611829 As new user, i cant put the link to the thread of RA recovery, sorry
I dont want to mess with this, because the consequence of bad procedure.
Thank you by your help and patience.

you might want to make sure you're using the main USB ports, not those extension ones or those that are built into PC cases. I used to have the problem with "unrecognised device" because of that.

computer can't find phone in fastboot mode

Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon

Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net

Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.

What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).

kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.

Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!

Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.

i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you

mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.

glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?

also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on

http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode

mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App

which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?

mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.

Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers

noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?

deleted!!!!!!!!!!

I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.

Okay, so put it in fastboot mode and try to run a fastboot devices real quick.

Soft brick? (No ROM installed but can sort of boot into recovery)

howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7

Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!

demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.

fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones

I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?

You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed

I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.

Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand

[A2017G] Bootloader unlock stuck at < waiting for any device >

I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!

ileikpi said:
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
Click to expand...
Click to collapse
either you are not in bootloader mode on the phone or you need to fix your drivers.

This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.

I got stuck at that step as well, had to do a hard reboot, attempts at reinstalling the drivers only seemed to make it worse!

JP_93 said:
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
Click to expand...
Click to collapse
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!

ileikpi said:
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
Click to expand...
Click to collapse
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.

JP_93 said:
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
Click to expand...
Click to collapse
Zadig doesn't let me right click to uninstall drivers T-T. I tried reflashing twrp and redoing everything in the guide to make sure I didn't miss anything but I'm still stuck at < waiting for any device >. Unlocked bootloader seems so close yet so far... Thank you very much for your help thus far tho!

if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?

Bucci83 said:
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Click to expand...
Click to collapse
Yep it does.

lafester said:
either you are not in bootloader mode on the phone or you need to fix your drivers.
Click to expand...
Click to collapse
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...

ileikpi said:
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
Click to expand...
Click to collapse
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...

Bucci83 said:
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Click to expand...
Click to collapse
Ok I'll try that when I get home.
Sorry but may I ask if you remember what your phone was called in device manager when you rebooted it into bootloader? Was it "Android", some Qualcomm code (ie. QUSB_BULK), or ADB something? In @JP_93 and my cases, our phones were simply labelled as "Android" in device manager.

Unlocked using a different PC
Ok guys, I managed to unlock my phone using a friend's computer with no problems. The drivers in my own pc were definitely messed up and uninstalling and reinstalling them didn't work.
Thank you very much to everyone for your help and sorry if I blew this out of proportion!

Glad you got it to work!

Fastboot Not Recognized

I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.

phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?

phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them

phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!

Thank you all. I will try these suggestions later today and report back.

I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.

After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/

Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!

jullev said:
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Click to expand...
Click to collapse
Thank you! I can't believe I didn't think to check that.

it is solved for me oneplus 6t not recognized in fastboot
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck

hichemkanon said:
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
Click to expand...
Click to collapse
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Thank you.

phaino00 said:
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
Click to expand...
Click to collapse
Did this and still not able to recognize it in fastboot mode

sonice43 said:
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Click to expand...
Click to collapse
Rijul30 said:
Did this and still not able to recognize it in fastboot mode
Click to expand...
Click to collapse
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.

Really need help. I'm going in circles and wasting a lot of time:
I'm attempting to root a OP6T A6013. Its already been unlocked.
My device is recognized when powered up as an ADB device.
But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot?
I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot.
Any tips or direction?

Hey all , replying to share my solution to this exact problem I was having..
My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle.
So just a fyi, it could be something simple as switching USB ports or even another computer.
hopefully this helps if someone get's stuck at this point.

I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.

OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device.
Thanks a ton.
EDIT : Just to add .. this linux was in VM

OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
I agree. Linux is far better when flashing android phones

anonymoustl said:
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
Click to expand...
Click to collapse
This worked for my OnePlus 9 Pro running Windows 10. Happy modding!