Ive tried reinstalling driver, changing from mtp, etc...
It just keeps giving me the exclamation mark on adb driver.
fastboot works fine though.
what to do next?
Related
Any Idea as to how to get adb working.....i got the bootloader unlocked with fastboot but no adb yet
adb works no problem.
says I am missing a couple drivers:
Android 1.0 & Nexus S drivers, wtf.
i installed drivers from sdk this morning. no issues. win7 32bit.
http://mycarbl0ws.com/google-usb_driver.rar
try this if it works
open a command window and type adb devices
i get nada
Duh
problem solved im an idiot.....after the boot loader unlocked it did the factory reset disabling debug mode DUH my bust. thanks for the help now on to try some hunches
I am trying to do a full reset in ADB which I have done a few times before. However, when I connect my nexus 4 in fastboot mode to my laptop and open command prompt it says 'device not found'. I have USB debugging enabled and the right drivers but it still won't let me do any adb commands. I am using the fastboot and adb files from the latest SDK but its not working. I have tried reinstalling drivers and rebooting my laptop but it still won't work. If it matters I am running android 4.3, on the latest PA 3.99.
Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also
apopberz said:
Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also
Click to expand...
Click to collapse
How do you clear RSA keys? I can't see it in developer options
I have attached a screenshot, as you can see, fastboot devices shows but no adb
Anyone??
Not sure if you know, but ADB commands are only allowed when android itself is running, thus the name "Android Debug Bridge".
If your fastboot is working, you should be in bootloader. How are you going to ADB in the bootloader?
Trying to flash recovery partition.. as per many guides or http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
adb sees the phone (adb devices)..
Reboots to fastboot..
But then fastboot devices reports nothing and fastboot flash recovery recovery.img just sits there <waiting for device>
Its like adb works.. but its not 'seeing' it in fastboot.
Phone is rooted.. I just need to get recovery partition changed to do backups and get a better ROM on there.
I faced the same problem and the solution was very simple. Make sure that you have downloaded the usb drivers corresponding to your PC's system type e.g., 32 bit or 64 bit. After downloading the correct version of the usb drivers make sure that you restart your PC. Hope this solves your problem.
Surely if I didnt have the right drivers already ADB wouldnt work ??
So am still getting exactly the same thing.. ADB works.. Fastboot doesnt..
Fastboot never seems to 'see' the device..
I have tried every set of USB drivers, lenovo drivers, minimal adb and fastboot drivers.. I can find..
What exact sets to making sure fastboot drivers are installed and correct ones.
So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.
Try different usb cable or usb 2.0 port
I had similar issue, fastboot was detected but haven't been able to do any command. So when the phone was powered on with selected usb to transfer files, in device manager the phone was listed as "Android phone - Android Composite ADB Interface", I updated the driver to "ADB Interface", rebooted in bootloader and was able to communicate through fastboot.
bpodnar said:
Try different usb cable or usb 2.0 port
Click to expand...
Click to collapse
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault
alkesh95 said:
So i decided to root my A1. But fastboot isn't working for me.
Tried with previous adb files.
Adb works properly.
But when device is rebooted into fastboot mode. Fastboot isn't and to talk to it.
Updated adb and fastboot (sdk tools and even in AIO tool)
Just adb works.
Reboot to fastboot and my device is not detected.
Disabled driver signature enforcement in windows 10
OEM unlocking allowed.
Usb debugging on.
Tried multiple times.
Nothing seems to work.
Maybe driver problem but since adb works i don't think that's the problem and i have installed it again from AIO Toolkit.
Click to expand...
Click to collapse
I hope drivers are up to date.
alkesh95 said:
I would if i could get my hands on one. But i can't not for few more weeks.
Adb is working fine. File transfer is working fine. Charging is working fine.
So I don't think cable is at fault
Click to expand...
Click to collapse
Did u tested this? Reboot to fastboot mod and connect mobile to pc. then right click my computer then device manager. Then check for A1 port. Update /install driver Automatically from internet. May be it will help , may be not.
ADB drivers are different than fastboot. If you can detect with ADB and not fastboot, I would suspect you have a driver problem. Boot into fastboot, then check device manager for your device. It might not have any drivers installed and be an unrecognized device, or it could have incorrect drivers installed. My device needed fastboot drivers, I had the same problem as you.
Thanks all of you. Fastboot driver was the issue.
alkesh95 said:
Thanks all of you. Fastboot driver was the issue.
Click to expand...
Click to collapse
I have the same problem, can you send me the fastboot driver please?
vu2pmc said:
I have the same problem, can you send me the fastboot driver please?
Click to expand...
Click to collapse
Follow the step. Windows will download correct driver automatically
I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?