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
Related
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?
Hi guys,
I'm having problems unlocking bootloader.
The phone enter into fastboot mode but when I type "fastboot oem unlock-go" in the cmd of windows it doesn't recognize my device.
I have installed Minimal ADB and Fastboot and I have installed ADB Driver installer too but it doesn't recognize the device.
Can anybody help me with this please?
I need to unlock it because I want to root it.
Thanks
Have you tried unplugging and replugging when the phone goes into fastboot mode?
I just got my pro 3, did the OTA to the .19 software and unlocked and rooted just today and my girlfriend's very very fresh windows 10 install.
If that doesn't work just delete the adb driver, replug the device and windows should install the same drivers I used.
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
same problem.
fix for it -> use linux
setup vmware, install ubuntu
when everything is set up connect device in fastboot mode
open command line:
sudo apt-get update
sudo apt-get install adb
sudo apt-get install fastboot
now you can make adb and fastboot commands, don't forget the sudo before the command e.g.: sudo fastboot reboot
I made the mistake of wiping my entire device when going to do a clean flash so the only thing I could access was recovery. I had no issues with using adb to sort out my mess in Win 10. The last phone I had was an old HTC that I was using between getting my OP3 stolen and the OP5 release and for that I had HTC drivers installed.
Not sure if that is a solution that will help you, but just putting it out there.
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?
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
Windows 7...
Seems I can have either ADB drivers installed for when the phone is booted or when the phone is in fastboot mode, but not both. I have fastboot ADB drivers installed now as I need them the most; it's easy to reboot the phone into bootloader. Am I stuck with one or the other? If I install the ADB driver when the phone is booted I lose the fastboot drivers. TIA.
I don't think you lose the drivers... you just can't see the device using ADB when in fastboot mode and vice versa.
vanish0104 said:
I don't think you lose the drivers... you just can't see the device using ADB when in fastboot mode and vice versa.
Click to expand...
Click to collapse
It's more like I have to install from a different driver package for booted vs fastboot condition. Both work, I just have to redo the driver install depending on the state of the phone. Seems odd.
Hey, I've been having a lot of trouble getting fastboot to work properly. I can get adb commands to work with my phone on but fastboot commands in fastboot mode don't work at all. I've been at this for about an hour.
I sort of get what you mean when you're saying you need to install separate drivers each time you want to switch between having adb and fastboot work. How exactly did you install "fastboot" drivers and how would I go around doing that? Help would really be appreciated!