Develop Bugs

[Q] Help! Usb driver doesn't recognize my galaxy nexus in fastboot mode

I try to unlock my My galaxy nexus bootloader but every time i connect my phone to pc in fastboot mode, it appears nothing. I had tried many google usb driver yet it didn't help. Can anyone suggest me solutions?
In fastboot mode it said:
Product name - tuna
variant - maguro
HW Version - 9
Bootloader version - PRIMEKK15
Baseband Version - SC04D0MLE3
Carrirer Info - None
Serial Number - 0146B0000E01701C
Signing - production
Lock State - Locked
There is number inside this device: SC-04D <Titan Silver>
It's currently running adroid 4.1.1
Build number: androidME_v1.2_GNexus-build_cdtdroid

Are you in windows, linux, or mac? I had a problem getting it to install the fastboot driver for my GalNex on my Asus G73 laptop in windows so it might be a similar problem. What I did was download and install the android sdk including the optional google driver, and then manually install it from the device manager. If you've installed drivers from different sources windows caches them and when you connect a new device it may use the old driver even if you've uninstalled it.
To install the driver manually make sure the phone is connected and in fastboot mode
then go to control panel -> system -> device manager
then select whatever the galaxy nexus is listed as. probably samsung phone or something along those lines.
right-click and select "update driver software
click "browse my computer for driver software" then "let me pick from a list of driver software on my computer" and finally click "Have disk..."
this will open a window for you to select the driver so hit browse, and in the explorer window go to the android-sdk folder where you installed the sdk and find the %android-sdk%\extras\google\usb_driver folder. then select the "android_winusb.inf" file. After clicking ok and ok it should list 3 drivers. I can't remember which one it is but I think one of them is a fastboot driver (If I remember correctly they're adb, composite-adb, and fastboot).
After it's installed open a command prompt and put in "fastboot devices". if there's a device id listen then it's working.
edit: the driver I refer to can be acquired here: http://developer.android.com/tools/extras/oem-usb.html
it says "The Galaxy Nexus driver, however, is distributed by Samsung (listed as model SCH-I515)." but that refers to the Verizon version.

it's working
Thank you I followed you instruction and it's amazingly working :victory:

This may help... it worked for me...
The reason the driver isn't being recognized by Windows, is that you need to edit the android_winusb.inf file. Let's now go through some simple steps to show you how to enable the Android Composite ADB Interface.
1. Download and Install Google USB Driver (yes, the generic Google USB driver, even though the Galaxy Nexus uses the Samsung USB driver in normal USB mode)
2. Next go to Device Manager and right click on Android 1.0 driver and click Properties
3. On the 'Property' drop down look for 'Hardware ids'; you should see two values like this:
USB\VID_18D1&PID_4E30&REV_0100
and
USB\VID_18D1&PID_4E30
Write down the USB\VID_18D1&PID_4E30 you will need to copy this to android_winusb.inf
4. Go to the USB driver folder and open android_winusb.inf with notepad and create a new line under 'Google Nexus (generic)' adding the above PID as follows:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E30
*Note: There are two sections where 'Google Nexus (generic)' is found; add this line under both the "Google.NTx86" section and the "Google.NTamd64" section if you are uncertain.
Now save the file to same location
5. Next, go to Device Manager (Computer Management) > Other devices > Android 1.0
Right click on Android 1.0 driver and click 'Update Driver'
Browse to the USB drivers folder and open android_winusb.inf (Use Browse my computer for driver software)
6. Windows will present you with a pop up saying "Windows can't verify the publisher of this driver software"; click > Install this driver software anyway
7. You should now see a message "Windows has successfully updated your driver software"; make sure the driver description looks like this > Android Composite ADB Interface; then click > close
8. Device Manager will now label the device driver > Samsung Android Phone > Android Composite ADB Interface

my galaxy nexus is'nt showing in pc...its charging...but cant connect in download and fastboot mode...even not showing in device manager...tried diiferet usb cables...plzzz help me...sorry for bad english

Thanks for instructions. It worked.

[Q] [BootLdr] Computer not seeing Phone.

I am new to android, HTC One VX being my first phone ((Got it like Last year as a gift iirc)).
Using Stock rom and my os is 8.1 pro x64
I am trying to unlock the bootloader.. I went to HTCdev, followed the directions for unlocking the bootlader.
1. Got the Android SDK and installed
2. Got the HTC SYnc Manager for the drivers.
3. Got Fastboot and moved it to where the ADB .dll file is.
I get my phone into bootloader after making sure USB Debugging is enabled, then I plug it into my computer. After a few moments, Windows pops up with USB Device is not recognized. I check Device Manager, it shows "My HTC" under unknown devices. I manually point the thing to where the W8 x64 driver is , and it says the driver is up to date. Bring up the Property info of the device, this is what is showing int he text box,
Code:
A request for USB BOS descriptor failed
Just to make sure, I navigate back to the ADB folder, bring up CMD there and type in
Code:
adb devices
. No device was listed despite my phone being connected to my computer. Tried it with 3 different cords, front and back of my computer. ((USB 3.0 ports.))
I put it in one of my USB 2.0 ports and the issue persists, the device status shows
Code:
A device which does not exist was specified
.
Is there anyway to fix this, its quiet annoying, Apparently doing clean reinstalls of everything isn't going to fix it for me.

OP3 not recognized on Win10

My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.

Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk

Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.

Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk

jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10

Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager

setup driver and try in twrp

A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.

Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.

jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.

peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.

http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.

i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .

You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs

update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.

I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3

jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580

unable to unlock bootloader

Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.

I always use something called 15 Second ADB Installer when setting up ADB and Fastboot on a new computer. It installs all the correct drivers as well, so maybe that would solve your issue. Also, be sure to check Device Manager in Windows and see whether there are any devices showing with yellow caution symbols besides them.
If you find your phone displaying like this; right-click and choose 'Update driver', then 'Browse my computer for driver software' and 'Let me pick from a list of available devices on my computer'. Find Google Inc. and choose the one which says 'Android ADB Interface'. You have to do this AFTER running the 15 Second ADB Installer otherwise it won't work.

Definitely driver related, remove and reinstall etc but don't give up haha sometimes its a PITA to install the correct drivers...

satya365 said:
Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.
Click to expand...
Click to collapse
Download MIFLASH TOOL, it installs all the drivers needed for Z2

Fastboot mode Troubleshooting [windows users]

Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.

Nice... Thanks for the guide... Many people needed it... Was about to make one myself...

Great. Many many thanks bro

kickyvivi said:
troubleshoot guide for updating the adb and fastboot drivers manually in a pc running any version of windows​
first, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
pre-requisites:
* pc running windows 7/8/10
* internet connection (just 20mb)
* working usb cable
steps:
(1) download the [official][tool][windows] adb, fastboot and drivers - 15 seconds adb installer v1.4.3 from xda
link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) install it with "y" confirmation for all 3 options and reboot the pc
(3) disable the internet connection of your pc
(4) reboot your phone to fastboot mode and plug it to your pc's usb 2.0 port (important)
(5) open device manager on pc and scan for hardware changes from the option if your device is not listed already
(6) if it shows 'asus android device' -> "asus android bootloader interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) now scan for hardware changes (magnifying glass icon)
(8) it will show 'android' with an ! Symbol
(screenshot 3)
(9) right click -> update driver -> browse my computer for driver software
(10) choose "let me pick from a list of available drivers on my computer"
(11) choose "android device" or "asus android device" or similar option and confirm it with yes or next option
(screenshot 4)
(12) a warning will pop up, press 'yes'
done
(13) go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )

Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
I am having same problem... Did you find any solution for it?

kickyvivi said:
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
Hello, I followed your mentioned steps but in my drivers its showing "Samsung Android Device" is that okay for my asus zenfone max pro m1 device? Or there is one portable device option, is that it?

Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!

kickyvivi said:
(12) A warning will pop up, press 'Yes'
Done
Click to expand...
Click to collapse
After I completed all the steps, my phone showed on screen "press any key to shutdown" and even in device manager it shows android ADB interface as hidden. Help please. Rebooting again to fastboot mode doesn't help because it shows the same screen "press any key to shutdown" on reconnecting with PC.

May Asus x01bd can't in to the mode fastboot..how to solved it?

Kajin660 said:
May Asus x01bd can't in to the mode fastboot..how to solved it?
Click to expand...
Click to collapse
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it

D0CT0RFATE said:
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
Click to expand...
Click to collapse
this same with me,, n i donk know how it is??
my phone asus x01bd

Nightmonkeyps said:
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
Click to expand...
Click to collapse
can u explaining me?? sorry i dont understand what u mean??

Kajin660 said:
can u explaining me?? sorry i dont understand what u mean??
Click to expand...
Click to collapse
Well you know how there's a BIOS in your PC which contains the basic commands required to run a computer. There is a setting called secure boot inside your BIOS. You need to turn it off and then install fastboot tools. To open the BIOS, repeatedly press F10 or F8 on your computer while it is opening. This is how it worked for me atleast

Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
this happen to me,, and i have solved this,,
step:
1. U must flash ur Phone via qfil,(*)
,than u will lost ur IMEI and SN will Change to 111111,, but dont worry thats can be back again
2. next step is u must recover ur IMEI and SN back (in tele group u wil found the step) after that U just flash stock firmware modified (via TWRP/ORFOX)n then ur phne willl back normally
Note : (*) in firmware for flash via qfil replace the recovery.img with twrp/orfox (rename To "recovery.img") this will bring u a twrp/orfox recovery after flash via qvil
i hope this can help..