I have installed adb drivers. But when I enter the command "adb devices", my phone doesn't get detected. I have Xperia ZL and adb detects it and not my OnePlus One. Yes, I have enabled Android Debugging in developer options. Tried updating driver software too. It says "windows couldn't find driver software for your device". I use windows 7.
EDIT: Solved. Installed drivers from here
anagramgenius said:
I have installed adb drivers. But when I enter the command "adb devices", my phone doesn't get detected. I have Xperia ZL and adb detects it and not my OnePlus One. Yes, I have enabled Android Debugging in developer options. Tried updating driver software too. It says "windows couldn't find driver software for your device". I use windows 7.
Click to expand...
Click to collapse
This problem is solved here is the link.
http://forum.xda-developers.com/showthread.php?t=2782721
If I helped you. Please click thanks
Sent from my YU Yureka using XDA Free mobile app
Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
KodRoute said:
Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
Click to expand...
Click to collapse
Whats your device?
LS.xD said:
Whats your device?
Click to expand...
Click to collapse
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
KodRoute said:
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
Click to expand...
Click to collapse
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
LS.xD said:
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
Click to expand...
Click to collapse
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
May you press "thanks" for my posts if i helped you ?!
KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
Doh! I hate when that happens. It's always the little things.
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
has it previously been paired with your computer via ADB ?
3mel said:
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
nogods said:
yes - it shows up as a device with adb
Click to expand...
Click to collapse
hope this works for ya
Factory reset Android using ADB
I am trying to factory data reset my Oppo Neo 7 (Android 5.1) using ADB shell. Any way I can try and link to ADB shell?
android.stackexchange.com
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
try flashing the stock rom from adb/fastboot
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
blackhawk said:
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
Click to expand...
Click to collapse
the pixel 4a doesn't have an sd card
the ADB devices shows the phone's id with "unauthorized" next to it. All ADB commands return this:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
maoriboi said:
try flashing the stock rom from adb/fastboot
Click to expand...
Click to collapse
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
\
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
nogods said:
the pixel 4a doesn't have an sd card
Click to expand...
Click to collapse
Yes I know. Keep that in mind next time around as it makes life much easier.
All joking aside, sorry to hear about your issues.
AlexKarimov said:
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
Click to expand...
Click to collapse
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
nogods said:
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
AlexKarimov said:
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
Click to expand...
Click to collapse
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
nogods said:
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
Click to expand...
Click to collapse
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
nogods said:
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
Click to expand...
Click to collapse
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
O
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
yup - looks like it worked:
Erasing 'userdata' OKAY [ 15.171s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.158s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 15.797s
What nows "not automatically formating" mean?
nogods said:
O
yup - looks like it worked:
Click to expand...
Click to collapse
Awesome, thanks for the updates. I'm glad you got it going
nogods said:
What nows "not automatically formating" mean?
Click to expand...
Click to collapse
I'm not sure about this, I've never encountered that as far as I know. Did it say "can't determine partition type" after that?
I have LE2110. In Settings I've enabled "OEM Unlocking" and also "USB Debugging".
I also instsalled the proper USB drivers but think they are unecessary regardless.
I boot into Fastboot & connect to laptop withofficial USB cable.
From the folder where I installed Android SDK Platform Tools I open command prompt.
Type in fastboot oem unlock and it says 'waiting for devices'.
I've rebooted everything, tried a few times over several days but always same result.
Phone works perfect, no issues otherwise.
Any tips what to try next or possibly what I'm doing wrong?
Thank you
I have a global unlocked 9. I had to use this to unlock bl. Open your command window from this after it installs,make sure to add shortcut to desktop when installing. Then run unlock command. Worked for me back in April when I bought device.
"minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities" https://androidfilehost.com?fid=746010030569952951
For me, I installed every driver while being in testsigning on ("bcdedit /set testsigning on" in cmd as administrator then reboot) and then I rebooted, turned testsigning off, rebooted again then it worked.
100 percent driver issue. Just reinstall the correct drivers and you'll be good to go.
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
dotuletz said:
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
Click to expand...
Click to collapse
Plus you can reboot edl through adb.