when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
for the record nothing is wrong with my USB connection cable because, I'm able to connect my HTC ReZound via USB cable to my macbook, the CDROM and STORAGE auto mounts to my desktop so i know the connection is working, because I'm able to copy files, update music via winamp sync playlists, also my paid EasyTeather copy works, etc.
I updated & installed most recent Android SDK adt-bundle-mac-x86_64-20130917 and updated the device manager for my ver 4.0.3 and all tools, even tryed using a stand alone platform-osx-tools.zip that contains a adb and fastboot...\
I read up on this and found nothing tryed everything....
adb kill-server > adb start-server - does nothing
adding device in the adb_usb.ini didn't help either.
chmod a+r /etc/udev/rules.d/51-android.rules after creating file didn't help.
rebooted many times .
i've attached a terminal cmd window below to show.
USB debugging is enabled on the device, yes? Does the "USB debugging enabled" notification show up when you plug it into the computer?
MaxxPayne said:
when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
Click to expand...
Click to collapse
are you doing proper methods in command prompt for sdk's adb such as directing it to the folder its in...example did you type cd c:/androidsdk/platform_tools/ in command prompt for example
I used to have a mac ....but here
Download htc sync for mac
http://www.iskysoft.com/convert-mobile/sync-htc-to-mac.html
Download the sdk and all you need is a folder called platform tools
http://developer.android.com/sdk/index.html
Extract the platform tools folder Put it on your desktop
Open terminal type "cd" then hit space then drag and drop the platform tools folder into the terminal after that hit enter
Then you can run any command just make sure to put "./ " before the command without quotations so if you wanna flash a boot you would put
./fastboot flash boot boot.img and hit enter
Note that adb works perfectly well on my Mac without the HTC Sync drivers.
Related
So ive been trying to figure out how to push files onto my eris for like a week now and im not smart enough with computer to so it. Ive downloaded the mac ADB, and have a 2.2 emulator up and running. But when i plug my phone in i cant ever find it using terminal. Im pretty sure its just cause im using the wrong commands so if anyone knows them for a mac that would be awesome. Any info would help me, Thanks.
No emulator is involved. Find the adb executable, and cmd+c to copy it. Fire up terminal and cmd+v to paste it, then type a space, then "push" (without the quotes), then a space, then drag the file you want to copy onto the terminal window, then type the location on your phone you plan on pushing to (like /system/app/ for example). And that's it! But you should do an adb remount before pushing. Again, to do a remount, paste the adb file into terminal or drag it in, then type a space, then "remount" (without the quotes).
It's been a while since I did the initial install steps, but the main difference to the commands is having to use a dot and a slash before the command "./" to specify the command you want to run is in the directory you're working in. Other than that, the PC steps are the same.
For example, my files are in a sub-directory under my user profile: /Users/<user_name>/Phone/android-sdk-mac_86/tools/ which can also be typed as ~/<user_name>/Phone/android-sdk-mac_86/tools/
So, in Finder, I go to that directory and double click the android file. That starts terminal which also starts the Android app. I go back to Terminal, press Command+T to open a new tab in Terminal (just so I won't have a ton of windows open), change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/ then I run the adb command typed as ./adb
So, to re-cap step by step:
My adb files are located in ~/<user_name>/Phone/android-sdk-mac_86/tools/
Make sure your phone is connected in USB debugging mode
In Finder, go to the above directory and double click android
Switch back to Terminal, press Command+T to open a new tab and change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/
Type: ./adb remount
Type ./adb shell (or whatever adb commands you want to run)
Got a new computer and Im having trouble getting my ADb setup. When I try to run adb devices I get
adb is not recognized as an internal or external command, operable program or batch file.
I have adb setup on C, JDK is installed. Downloaded drives from htc sync, but did not install htc sync. Under Device Manager, the phone is listed as
-Android USB Devices
-My HTC. the monitor has a lilttle yellow triangle with an !. I tried to update the drives, but it says I have the most recent installed.
Any help would be greatly appreciated. Thanks.
Edit.....need to use the platform-tools folder, not tools.
+1
I have tried to run ADB on my Inc, Nook Color and now the TBolt.
I just cant get it to work.
It would be easy to just say I am a dope, but I have had a highly successful run with the Inc. I have flashed/installed/performed/restored every worthwhile mod available for the INC and Nook with no trouble. I just cant get ADB to run.
ive just helped someone with this.
they HTC Sync software has the ADB drivers
download
install
then cancel HTC sync instalation
http://forum.xda-developers.com/showthread.php?t=1000751
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
distortedloop said:
It sounds to me like your problem is that the adb executable is not in your path and you're not trying to run it from within the directory it is installed in, as indicated by your saying "adb is not recognized as an internal or external command, operable program or batch file".
In your terminal window, try using the cd command to switch to whatever folder the adb.exe file is in, and then try running the command. You don't even need the phone hooked up to test at first...just type adb devices or something to see if the app runs or not. On my Mac, if I just type adb at the command line, adb responds with a list of all available commands.
Do a dir command (Win) or ls (Mac/Linux) to confirm the file is in the same directory you are.
Click to expand...
Click to collapse
Yea, the error is the one you get when you use a windows command thats not in the path. So do this, or add it to your path environment variable
Thanks to all who answered. That is why this community is the best. The older version of adb just had tools folder, while the new version has platform tools that needs to be used. Again thanks.
sent from my commando style T-Bolt.
I'm on win 7 32 bit.
I have HTC sync installed, adb installed, added system variables and cannot get adb to recongize my device in command prompt.
http://www.youtube.com/watch?v=A1SOSXwkc_8
I'm trying to update my phone and it won't boot into download mode :X so I'm trying to do it with adb my problem is I can't get adb commands to work because I don't know what the path should be in the variables :C my location for adb is "C:\Program Files (x86)\Android\android-sdk\platform-tools.adb.exe" thats so much in advace!!
Dunphy said:
I'm trying to update my phone and it won't boot into download mode :X so I'm trying to do it with adb my problem is I can't get adb commands to work because I don't know what the path should be in the variables :C my location for adb is "C:\Program Files (x86)\Android\android-sdk\platform-tools.adb.exe" thats so much in advace!!
Click to expand...
Click to collapse
In order for adb to work you need to set the path to where adb.exe is. The code is
chdir C:/Program Files (x86)/Android/android-sdk/platform-tools
adb shell
that will enable you to use adb
Sent from my Optimus Me using xda premium
for adb to work u just needed to be booted up normally with usb debugging selected.
locate to the folder where adb.exe resides. SHIFT + right click on that folder and choose "open command window here"
cmd terminal will open up wid C:/Program Files (x86)/Android/android-sdk/platform-tools
nw run "adb devices"
if ur device is detected with serial no then are good to use adb....
Sent from my Nexus One using Tapatalk
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Thanks. Very useful! :good:
for me and the HTC One X it wont work.....
-Happy Feet- said:
for me and the HTC One X it wont work.....
Click to expand...
Click to collapse
Did work previously?
maybe restart the adbd on the phone.
Can you test in Recovery, Cwm has an extra button for restarting.
Maybe Stock too.
Illidan Pornrage said:
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Click to expand...
Click to collapse
Fraid it didn't work. End up with various errors and randomly appearing devices. Plus, the original error reappears eventually. Please help!
If you give me some Info around the issue, like what you intended to do and if it worked previously, I could help you.
FIX adb offline problem
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window
------------------------------------
After that you every thing will be OK
this solved my problem
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
ciano865 said:
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
Click to expand...
Click to collapse
as far as I know adb doesn't work in bootloader mode.
MadMan29729 said:
as far as I know adb doesn't work in bootloader mode.
Click to expand...
Click to collapse
How can I push file to phone it doesn't boot ?
I think thats intentional, bootloader mode is the mode corresponding to fastboot for directly flashing, deleting, formatting, stuff like that in the most basic environment. Try recovery or normal boot for adb, which is for debugging, shell access, backup, filetransfer and so on.
(More info for more specifics)
Thanks, my mistake not using recovery
from Nexus 4 with Tapatalk
took me a bit to get into the thing myself after > 4.2 update
i'm on ubuntu
i had to use the terminal command
Code:
android update sdk --no-ui
a couple of times to get the thing actually updated. using just
Code:
android update sdk
wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.
then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),
it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and
Code:
sudo rm adb
then navigate over the folder whereeveryouputyoursdk/platform-tools/ and
Code:
sudo cp adb /usr/bin
that should be the new version of adb into /usr/bin. remember, do all that after running the
Code:
android update sdk --no-ui
a few times
peace
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
ah great i thought there was an issue with my adb and you wrote the solution
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
Thanx man you saved me !!!
Sent from my Micromax A57 using xda app-developers app
Thanks
I still had this problem on OSx and Ubuntu in cli.
what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)
killall adb
then turn off USB debugging on device.
start new adb (doesn't work nothing to connect to)
then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"
test adb devices and should show 'device' instead of 'offline'
or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.
yay!
svs57 said:
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
Click to expand...
Click to collapse
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.
I am trying to fastboot flash a dtb battery.zip. I am brand new to linux. Only been using it about a week. I did manage to get adb installed from the software manager. I have the battery.zip saved in Downloads. I have USB debugging enabled. However, I never get a prompt to allow the computer. When I run adb devices though there is a device listed. I must have did a thousand google searching trying everything I find and I cannot get this file on my tablet Can someone please help me out?
0
Seppppx said:
Did you follow these Linux ADB guides? How to Install ADB on Linux
1. Download the ADB ZIP file for Linux
2. Extract the ZIP to an easily-accessible location (like the Desktop for example).
3. Open a Terminal window.
4. Enter the following command: cd /path/to/extracted/folder/
5. This will change the directory to where you extracted the ADB files.
6. So for example:cd /Users/Doug/Desktop/platform-tools/
7. Connect your device to your Linux machine with your USB cable. Change the connection mode to “file transfer (MTP)” mode. This is not always necessary for every device, but it’s recommended so you don’t run into any issues.
8. Once the Terminal is in the same folder your ADB tools are in, you can execute the following command to launch the ADB daemon: adb devices
9. Back on your smartphone or tablet device, you’ll see a prompt asking you to allow USB debugging. Go ahead and grant it.install adb
10. Finally, re-enter the command from step #8. If everything was successful, you should now see your device’s serial number in the Terminal window output. Congrats! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
Source https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Yes I have all that taken care of. The device is recognized. However, I never got a prompt to accept the computer connection. I'm wondering if you get one when your using Linux? Anyways, adb devices shows one device and serial number. I then enter adb fastboot reboot fastboot. Once rebooted I tried fastboot flash battery.zip. This did not work. I must have the wrong command or something but I cannot find directions from where I left off above.
Found instruction but their not working. The proper command was abd reboot bootloader. Once there when I run adb devices I get nothing. Why does it show a device in android but not in the bootloader? I also tried just running the command fastboot flash battery.zip I got the fallowing bash: fastboot: command not found. Also, tried unzipping the battery folder first and flashing battery.dtb. Still no go. It is because it is not being found in fastboot. I have no clue why.
I figured it out.
In software manager install.
android-tools-adb
android-tools-fastboot
Download unzip it in your downloads folder.
Download your battery dtb file unzip and pit it in the platform-tools folder.
Enable USB debugging on your phone or tablet.
In terminal type sudo cd /home/rocky/Downloads/platform-tools
Type sudo adb devices. You should see a device number.
Type sudo adb fastboot reboot bootloader
Type sudo fastboot devices
Type sudo fastboot flash dtb xxxxx.zip. xxxxx.zup is the name of your batty dtb file.
You should see your file being transferred.
Once complete type exit and reboot phone or tablet.