Develop Bugs

[Q] Fastboot issues

Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?

BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.

I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.

Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium

No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.

rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.

BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.

Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.

BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.

efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:

BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.

Can't unlock bootloader, fastboot not detecting device

UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.

There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"

Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.

yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"

amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working

yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.

I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!

yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?

duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!

I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!

I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?

I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now

Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.

crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!

I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)

wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.

amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!

Adb recognizes devices during phone on state, but not in fastboot.

Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?

railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186

Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!

ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!

railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56

I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.

Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733

abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.

I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.

It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs

Mac doesn't see my pixel 2 xl

TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?

Desert.pro.riders said:
TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?
Click to expand...
Click to collapse
The first thing I would do is take a drink!! Wow! Seems you have quite the mess on your hands. Seriously though, you really can't do much until you get fastboot working. Question, when you unlocked the bootloader, did you run BOTH unlocking commands??? Also, is OEM unlocking and USB debugging still enabled from the developer options menu??
Do you have the latest SDK/platform-tools on your pc? Have you tried different USB cables and ports??
Here's a recovery thread you may want to look at to help you along and get you back up and running :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot
View attachment 4492382

Desert.pro.riders said:
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
Click to expand...
Click to collapse
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:

Yes! At least the phone os on the phone works fine
Yeah you're right about the macs. They are pretty cool because it works with removable devices without having to mess with drivers. But it sucks when something goes bad because there are really any device managers or drivers to mess with.
Blessing/curse.
I'm usually a pc dude too, but my ex took my PC ?
Well once I get home from school I'll get to trying to fix this once again

Badger50 said:
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
Click to expand...
Click to collapse
So the windows PC does detect that something gets plugged in But this the only thing that happens
This sucks
Edit:
I was able to get into stock recovery now. But I don't think you can do much from there.
Adb & fastboot continue to be unresponsive

..

Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server

I never had problems connecting my Pixel to mac, even to other hackintosh...
I have Android File transfer installed and no SDK platform tools.
Usually I just download the package from Google and place it somewhere. Than opening Terminal, going into that folder, which btw contains adb and fastboot...
For example: when typing the " ./ adb devices" for the first time, the message about not running / starting Daemon service pops up. This is normal.
I presume that you are using the "./" before every command in Terminal.... This is obligatory on Mac.

Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here

,,

Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
The way I do it is
1. Open terminal
2.write "cd "
3. Drag the platform tools folder from the desktop to the terminal window
4. Check adb devices , "./adb devices"
I will try to reinstall adb again your way, as I am out of options so anything helps, thanks

Desert.pro.riders said:
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here
Click to expand...
Click to collapse
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??

Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
Badger50 said:
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
Click to expand...
Click to collapse
This, stops before it goes into step 2

disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.

uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Still nothing I tried this a few times & did the path install too
IDK what else there is trouble try I'm pretty much open to anything

Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?

Desert.pro.riders said:
Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
Click to expand...
Click to collapse
You can adb side load from stock recovery as well.

uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Badger50 said:
You can adb side load from stock recovery as well.
Click to expand...
Click to collapse
If I'm on adb sideload mode & I type adb devices into the terminal, should the serial number show up in the terminal? Because it's not. I'll try messing with it a lil more once I get home from work

7T Android ADB Fastboot Driver Issue on Windows

Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.

raskulous said:
Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.
Click to expand...
Click to collapse
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.

Soapy! said:
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.
Click to expand...
Click to collapse
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.

raskulous said:
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.
Click to expand...
Click to collapse
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).

Soapy! said:
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).
Click to expand...
Click to collapse
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'

raskulous said:
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'
Click to expand...
Click to collapse
When you check the driver properties do they match what's in the attached image?

Soapy! said:
When you check the driver properties do they match what's in the attached image?
Click to expand...
Click to collapse
No, this is what I get after installing the "Composite ADB" driver from google.

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
Have you tried to uninstall AND delete all android/android usb drivers, then reinstall oneplus drivers? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing

[QUOTE = "bynarie, postagem: 83974147, membro: 5375894"]
Você tentou desinstalar E excluir todos os drivers USB do Android / Android e reinstalar os drivers oneplus? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing
[/ CITAR]
Tank You

raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
I had the same problem before, with fastboot not recognizing the device and only "waiting for device.." appear when I'm on bootloader mode on the phone. I got it working when I chose bootloader driver (Google USB drivers) on Windows Device manager (under the same screen like your screenshot). Put your phone on bootloader mode, open Device Manager (Windows), plug your phone and Android devices should appear. The Google drivers should come up (assuming you installed them) when you click on Update Driver, then choose bootloader. If successful, device should appear under fastboot devices command. Fastboot should then work.

for "fastboot waiting for devices" problem check solution here https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/

Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

CheshireShorty said:
Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Click to expand...
Click to collapse
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.

_sky.captain_ said:
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.
Click to expand...
Click to collapse
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.

Battled a bit with this one... Just to let others know. I had no change to get it work with Win11. Using Win10 everything worked fine. Luckily I had other PC with Win10 so I got everything working.

ej8989 said:
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.
Click to expand...
Click to collapse
Thanks! I wasn't able to install the Google drivers manually with the device manager but this worked for me.
Just click on "View All optional updates" after checking for updates, expand driver updates and choose the Google - Android Bootloader Interface. I wasn't aware of that option in Windows update.