Hi.
It's not first time for me to root or flash rom or sth like that.
It's also not the first time for me to use the adb.exe or the android sdk.
Today, I installed the sdk and the java and everything I need. Everything works great until I tried to use the adb.exe.
When I click on adb.exe, it pop out for a second and then disappear. I can see a lot of commands within that second.
Then I try to use cmd and the commands are the following:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
These commands are obviously the command: [abd help]
Why the hack would they show out instead of running the normal adb.exe???
Also, any other adb command turns to the same things above( result of the [abd help] command)
Need help, can't use any adb functions..........................
What command are you typing? What guide are you following? This is all very vague!
Kangburra said:
What command are you typing? What guide are you following? This is all very vague!
Click to expand...
Click to collapse
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
NokiaBigS said:
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
Click to expand...
Click to collapse
What do you mean run adb.exe?
adb.exe doesn't run, its a service.
you should set it up your path on your computer to make life easier.
Open a command prompt (search for cmd in start menu) and type "set PATH=%PATH%;C:\sdk\whateverthepathis"
Then once that is set you can just type adb into command without the need for writing the whole path every time.
Like C:\sdk\platform-tools\adb.exe\adb devices becomes adb devices.
Sent from my GT-I9300 using xda premium
NokiaBigS said:
First, thanks for replying me.
I didn't really follow any guide as i know how it works...
I installed the driver >java pack>sdk and I just run C:\SDK\platform-tools\adb.exe
Click to expand...
Click to collapse
succeed code
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
nodstuff said:
adb.exe doesn't run, its a service.
you should set it up your path on your computer to make life easier.
Open a command prompt (search for cmd in start menu) and type "set PATH=%PATH%;C:\sdk\whateverthepathis"
Then once that is set you can just type adb into command without the need for writing the whole path every time.
Like C:\sdk\platform-tools\adb.exe\adb devices becomes adb devices.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
shoot....I don't know about that.....I thought exe is to run........
sorry about that.
So what if I got such result after using command: adb devices
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
Glad it is working for you.
NokiaBigS said:
shoot....I don't know about that.....I thought exe is to run........
sorry about that.
So what if I got such result after using command: adb devices
Code:
C:\SDK\platform-tools>adb devices
List of devices attached
TA53808AMN offline
TA53808AMN offline
Click to expand...
Click to collapse
Ya I thought you were going to the platform-tools folder and clicking adb.exe the icon.
Well try set up the path so you don't need to type all the long path to adb.exe whenever you want to use it.
When you set it up all you need to type in is adb devices. That's it.
Its up to you though.
Sent from my GT-I9300 using xda premium
solved issue
Related
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
antonio91282 said:
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
Click to expand...
Click to collapse
Did you put your phone in debug? Settings>Applications>Development
yes. and i been going over the directions repeatedly on theunlockr. im running xp 32 i believe
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
cd C:\Program Files\Droid Explorer\SDK\tools
Click to expand...
Click to collapse
- <type your ADB command here> e.g.
adb shell
Click to expand...
Click to collapse
^ yeah...
adb devices
Click to expand...
Click to collapse
should show your device...
To the OP, I don't know if this is the case for you but I changed my path on my Windows PC like the guides said to and that didnt completely work. (Maybe neede a restart). But in any case if you go to the command prompt, change directories to were you have adb and run your commands from there, it works like a charm.
For example if you unzip the the SDK in your download directory, open up the command line and type:
cd C:\Documents and Settings\<your user name>\Downloads\<whatever-you-named-the-unzipped-folder>\tools
ADB is in the tools directory you just went to. From here you can run the adb command without having to set up the system paths. This is a quick and dirty explanantion and might not even work for you. I was running this on Windows XP when I had this problem. Same thing had to be done on my Ubuntu Linux box b/c I'm to lazy to set up paths on that one, lol.
zephiK said:
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
- <type your ADB command here> e.g.
Click to expand...
Click to collapse
Oops, didnt see that you allready posted this. Yea do what zephiK says and it should work.
i have not been able to get adb to work no matter what i did (i am using xp) and i have been trying since i had the htc magic last year. here is how i recently got it working.
i downloaded the one-click root zip file and unzipped it. inside there is a adb.exe file. i clicked it and then then made sure my phone was in debugging mode and connected to my pc and used the command prompt to point to where adb is in my android sdk which for me is cd\androidsdk\tools
adb devices
i hit enter after tools and enter after devices and now it works. not sure why but it does. i couldnt get my magic, my nexus one or even the galaxy to work until i did this.
i got everything done. i think? only problem is im getting $ sign instead of # sign. any ideas?
i got adb working. thanks everyone.
A thread success story without any casualties. Almost makes me weep.
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
RPK925 said:
iam having trouble using ADB with windows XP. i have downloaded superoneclick program and opened the ADB folder inside. then i turned usb debugging on, then connected, then ran the ADB program, it starts with showing how to run commands, but only stays open for about 5 seconds, then closes, i cant read what the rest of it says because it closes to quickly. iam new to android and have never used adb before but i followed all the steps i think. what iam i doing wrong? thanks
Click to expand...
Click to collapse
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
raybond25 said:
you have to open a command prompt in the folder where adb.exe is stored. you don't need to run the program itself, just run commands necessary to do whatever hack you're trying to do. if you just put the apk files in the same folder as adb.exe then use "adb push" commands and such (whatever is detailed in the instructions)
to open a command prompt in the folder, i think you can just right click and select "Open command prompt here" (i know that's in win7, not too sure about xp)
also - this is the wrong section to post this. it should be in the Q&A section, not development.
Click to expand...
Click to collapse
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
RPK925 said:
thanks for your help. when i extracted adb from S.O.C. i gave me 5 files
ADB.exe
ADBmac
ADBlinux
ADBWinUsbapi.dll
ADBWinApi.dll
I right clicked on all of them and couldnt find anything about opening command prompt?
Click to expand...
Click to collapse
start, run and type cmd. this gives you a command prompt
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Big-A-Rob said:
Why are you using super one click on your atrix? Gingerbreak or gladroot is the preferred method for the atrix.
Sent from my Blue Steeled Atrix
Click to expand...
Click to collapse
Yes I know iam just trying to get the ADB files from.SOC. iam rooted on gingerbreak.
Sent from my MB860 using XDA App
scorneil said:
start, run and type cmd. this gives you a command prompt
Click to expand...
Click to collapse
Start the. Exe? Because it wont allow me to type any commands it just runs for about 2 seconds then closes.
Sent from my MB860 using XDA App
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
Hello all
So here I am in my first topic :laugh:
For Mac users can be tough to work with commands, which most of it has to be done in order to perform stuff in our Moto X.
Instead of having to mount virtual machines in order to have access to Windows' stuff. Or the Android SDK has to be installed, browse to specific folders to run commands from them, etc.
We can work directly in our precious Terminal! :victory:
So, I made a little script that will allow Mac users to work directly on Terminal, no matter which folder we are working on. I've included the following files:
adb
fastboot
mfastboot (Motorola's modified version of fastboot)
To Install
Run Terminal (/Applications/Utilities/Terminal.app)
Browse to the folder in which the script resides, i.e., if it’s in Desktop, then type in Terminal “cd Desktop/ADBInstall” (without quotes).
To run the script type “./install.sh” (without quotes).
You will see input on the screen.
That’s it
To Uninstall
You can safely remove the 3 files in one command, just run the uninstall.sh script by following step 1 and 2 from the Install section. Instead of following step 3, type the following in Terminal: “./unistall.sh” (without quotes).
Hope you like it
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
HeroOfTime said:
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
Click to expand...
Click to collapse
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
MoisesPerez said:
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
Click to expand...
Click to collapse
Thanks for looking into this for me. Yes, it did ask for my password. Here is what I get after running the installer:
Jareds-MBP:ADBinstall Jared$ ./install.sh
This will install ADB, Fastboot and mFastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/Jared/Desktop/ADBinstall
Copying ADB...
ADB copied to /usr/bin/adb
Copying Fastboot...
Fastboot copied to /usr/bin/fastboot
Copying mFastboot...
mFastboot copied to /usr/bin/mfastboot
You may now run Android Debug Bridge, Fastboot and mFastboot commands
Have a nice day
I'm attaching a screenshot of the output as well, but that is the output I get, which seems correct.
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
MoisesPerez said:
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
Click to expand...
Click to collapse
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
HeroOfTime said:
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
Click to expand...
Click to collapse
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
MoisesPerez said:
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
Click to expand...
Click to collapse
Well thanks a lot for your help. Still a great resource. I will keep playing around with things and maybe get it to work.
Thanks again!
Not a problem my friend. Good luck!
worked great for me on 10.9!
worked for me as well on Yosemite 10.10.1. thanks!
Glad it did! Regards.
Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
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.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
darkouz said:
Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
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.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
Click to expand...
Click to collapse
Normally on Windows the first time you turn on usb debugging it will pop up and ask you to accept the adb key. This is what is preventing you, I haven't had to resolve this in Linux, but essentially you need to go to C:\\Users\You\.android\ (in Windows, path will be different in Linux) and copy the file adbkey. Now you need to move it to data/misc/adb/
This will most likely require root or TWRP. Good luck, my friend.
Sent from my KYOCERA-C6745 using Tapatalk
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
darkouz said:
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
Click to expand...
Click to collapse
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
darkouz said:
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
Click to expand...
Click to collapse
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
i m doing : sh script.sh
i m gonna read that, thanks
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
darkouz said:
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
Click to expand...
Click to collapse
Glad you got it.
Sent from my KYOCERA-C6745 using Tapatalk
sudo rm -rf /home/(username)/.android
that worked with my kde neon machine