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

help me plzzz..

Guys it'smy first time i m about to unlock bootloader of zuk z2 got boot ing on mail.but when i type adb device it doesn't show my device ... Plzz giv any driver link or solution

Have you enabled developer options and do you have Android debugging enabled there?
Sent from my Z2 Plus using Tapatalk

manojchs said:
Have you enabled developer options and do you have Android debugging enabled there?
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
yess boss absolutly. i hav enable it adb is not detetcting my zuk 2...plzz help my first step is not successfull

Are you seeing any adb prompt in your phone when you connect it to the pc? If not then the phone mat not be properly connected. If possible try using a different USB cable.
Sent from my Z2 Plus using Tapatalk

manojchs said:
Are you seeing any adb prompt in your phone when you connect it to the pc? If not then the phone mat not be properly connected. If possible try using a different USB cable.
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
Noi there is no promt on ..phone

Disconnect the phone from PC then go to developer options and choose revoke USB debugging permissions. Then connect the phone again and run the adb devices command. You should see a prompt in you phone to allow USB debugging. Select trust this computer and cos ok. ADB should work after that.
Sent from my Z2 Plus using Tapatalk

manojchs said:
Disconnect the phone from PC then go to developer options and choose revoke USB debugging permissions. Then connect the phone again and run the adb devices command. You should see a prompt in you phone to allow USB debugging. Select trust this computer and cos ok. ADB should work after that.
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
sir i got promt on phone then i adb rebooted to bootloader but after puting this command fastboot -i 0x2b4c flash unlock unlock_bootloader.img it is saying waiting for device

manojchs said:
Disconnect the phone from PC then go to developer options and choose revoke USB debugging permissions. Then connect the phone again and run the adb devices command. You should see a prompt in you phone to allow USB debugging. Select trust this computer and cos ok. ADB should work after that.
Sent from my Z2 Plus using Tapatalk
Click to expand...
Click to collapse
Sir now device is showing on adb i command adb devices or showed my device then cammnded reboot to bootloader then i comm to unlock bootloader given on thread but it say waiting for device

Is the phone still in fastboot mode?
Sent from my Z2 Plus using Tapatalk

adb will not work

I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?

When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.

dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work

canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?

Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC

canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use

Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?

canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up

Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl

canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.

Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing

USB debugging enabled?

Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues

canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices

Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked

canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep

canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked

I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.

Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.

USB debugging

Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance

Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?

RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.

edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....

Bootloader un-detected.

I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.

KH-Squisshy said:
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
Click to expand...
Click to collapse
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say

Make sure your USB port on the phone is clean using compressed air. Though if it works with ADB it should also work in bootloader

Riski3Run said:
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Click to expand...
Click to collapse
I was trying to just root it, but I found out what it was. someone sent me the drivers to update my device in manage devices.