Develop Bugs

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks

device not found

adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.

No ideas?
I can connect adb over WiFi, but ofcourse it says offline.

USB debugging ticked?
A

Adb doesn't work in the bootloader. Only fastboot commands

Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).

kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.

Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.

[Q] ADB not recognizing device

I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790

Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.

Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...

I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition

jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.

For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed

Phone not recognized in windows 7

I am already rooted and on xposed using a win8.1 laptop. Followed the root guide by Heisenberg (sdk and adb drivers etc), however, on my desktop running windows 7 64 bit, I am not above to get my phone to show up with MTP. The option PTP however has no problem.
ADB is recognized in windows, but fastboot and adb are not recognized when in bootloader mode
Switching over to Win8.1, I have no such problems. Tried searching for win 7 updates and drivers but not much luck there, still cant get device manager to show the nexus 5x.
I prefer using the win7 as it is my main desktop versus the win8.1 which is a laptop that I leave mainly in the office.

Bump for this, Windows 7 users help!

Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.

alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.

queerquirks said:
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.
Click to expand...
Click to collapse
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.

alvinhochun said:
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.
Click to expand...
Click to collapse
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.

queerquirks said:
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.
Click to expand...
Click to collapse
Have you tried "uninstalling" the device in device manager when in TWRP too?

alvinhochun said:
Have you tried "uninstalling" the device in device manager when in TWRP too?
Click to expand...
Click to collapse
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.

queerquirks said:
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.
Click to expand...
Click to collapse
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)

alvinhochun said:
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)
Click to expand...
Click to collapse
What I had was
Android>Google Nexus ADB Interface , this works fine for adb and fastboot
Instead of Portable>Android, I had Unknown Devices with a exclamation instead hence the uninstall and reinstall would not show it as Portable android, only as unknown device.
Solved:
Solution for me would be clicking the notifications in the bottom left. saw that a Nexus 5x was still attached as a hardware even though the storage was not shown under computer.
- Uninstall the unknown device, 5x is still shown as attached in notifications
- Right-click the "safely remove hardware.."> open devices and printers and double click 5x
- Choose Update device drivers and point the path to the universal usb drivers ( android sdk)
5x mtp storage is now showing under computer drives but adb does not work in android system, only recovery. Good enough for me
Thanks alot for your help and time!!

alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
Just what I needed to do thanked

Going mad just can't get fastboot to work?

I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks

xda163fm said:
I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
Click to expand...
Click to collapse
Think fast boot only works in bootloader mode see here for unlock instructions
http://https://wiki.cyanogenmod.org/w/Install_CM_for_crackling

If I am using windows what drivers should I install? Adb works but does fastboot need drivers also? I have tried fastboot both with phone in and out of the fastboot screen - I have to pull battery to get out of fastboot mode! Thanks

Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!

xda163fm said:
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
Click to expand...
Click to collapse
I can't get fastboot working either. Really annoying me.

I have got this sorted. I will post details in the morning. I used a live USB of Ubuntu 15.10.