Database Info

adb commands not recognized

my adb commands in windows cmd are not recognized. I have done the following and am trying to install a custom boot animation
-Installed android SDK
-Installed Java SDK
-Have phone charging only while in debugging mode
-Added environment variable on windows 7 pc
First install of sdk yielded no recognition of adb commands, reinstalled and adb help command worked so downloaded the bootanimation i wanted, went back to command, ran adb command again - not recognized as valid command. So it seems the adb script commands just aren't sticking...arrggg
UPDATE : I have adb running commands now, but my device is not recognized [error: device not found] I have installed the google usb drivers and manually installed them on my computer but do not know if they are working correctly, there are three:
-Android ADB interface
-Android Bootloader interface
-Android composite ASD interface
FIXED : 1.Needed HTC Sense driver for adb inteface, found standalone driver 2. adb commands wouldn't run unless your in the adb directory - duh

[Q] adb devices not listing my device

I cant able to use the adb. It's not listing my mobile.
Even though, I've enabled my USB Debugging, It's not listing my device.
Last day it worked well.

Any idea guys? I'm still struggling with this problem.

That's problem in the driver and the custom ROM. I myself solved he problem.

Well

swordfish said:
Well
Click to expand...
Click to collapse
if device is not shown in adb then there will be some possibilties like
you haven't properly installed the driver or older version of drivers
or you haven't have all the binaries files to run adb command
or previous adb server was not killed
to prevent that
install updated drivers,check whether you have all binary files
and for killing adb server try these commands
adb kill-server
adb start-server
adb devices
hit thanks if helped

Pixel: no adb shell?

Brand new unboxed Pixel, only installed app "Helium" to restore a backup.
Here's where trouble starts: needs adb, but no matter what I do (OpenSuSE 42.1, udev rule for 0666 permissions) lsusb sees the device (when USB debugging is set to "charging" lsusb says Nexus 4., when I say PTP it lists as "Google Inc") but adb devices says: <empty list> and adb shell won't connect either.
Pointers appreciated.

Update to the newest version of ADB and dev tools from the Google website.
Sent from my Pixel using Tapatalk

yup, 1.0.36 fixed it.

ADB not recognizing Pixel on ubuntu 16.10

Pixel just updated to 7.1.2 build 47K, running adb devices is not showing any phone connected. I am able to view and transfer files through the file manager, but none of the adb commands will work. My other older androids will display fine. Any ideas?
I have usb debugging enabled and connection type set to file transfer. Tried 2 different usb ports on ubuntu 16.10. It's the google store version for what it's worth.
adb version: Android Debug Bridge version 1.0.32
lsusb: Bus 002 Device 012: ID 1xxx:4xxx Google Inc. Nexus 4 (debug)
Sorry if there is another post for this, I searched and did not find an answer to this on my own.

@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:

Geeks Empire said:
@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:
Click to expand...
Click to collapse
so turned out to be just a bad usb cable...
the one that came with the phone of course did not work

Android 10 ADB

Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.

ADB appears to be working just fine for me.

When using adb make sure you have debugging enabled and grant the popup on screen

adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.

Also need to make sure that the proper USB drivers on the computer are installed/updated.

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.

D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...

Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do

a second adb server was running.
TNX

Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865