Related
I am running ubuntu and im am trying to install the sdk, i searched on the internet and messed around with it for 2 hours last night and still could not figure it out, it is a tgz file, Any help would be great. Thanks
deleted
Im having the same problem except I have everything installed just need to figure out how to get my computer to recognize my phone
if i remember correctly,cd to the directory where you saved the sdk tarball, then as mentioned above extract it using tar zxvf
cd to the extracted directory and you should see /tools
cd into /tools and you should be able to load the sdk by typing ./android
if you add the /tools directory to your path in your .bashrc, you will be able to type android straight in the terminal to load up the sdk.
hope that helps
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
Alright i have the the sdk installed i just need abd commands to work now
Don't forget to add the tools directory to your PATH
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
Click to expand...
Click to collapse
Go into the directory and see if there is a file called adb in there...if it's not check the other folders like tools or something like that i'm at work so i don't know the exact name of the directories...
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This is a PC error message stating that the file adb.exe is no longer in the AndroidSDK directory. As zervic mentioned, check and see if the file adb.exe is in that directory.
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
duckredbeard said:
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
Click to expand...
Click to collapse
Just reinstall (or unzip if I remember right) the Android SDK into that directory
I started the "update all" in the "installed packages" window. If that doesn't fix it, I shall follow your advice.
Edit: The "update all" didn't fix it.
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
duckredbeard said:
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
Click to expand...
Click to collapse
Just so you know that may be a little unstable. It may be worth your while to check the "platform-tools" folder and see if adb is in there, i believe that's where it is by default and it also may be worth your while to run adb from that folder instead of where you jerry rigged it to run. But, on the other hand, it may work the way you have it. You never know. Just figured I'd throw that out there.
While rooting my Nook Color, I came across a recommendation for a free app in the market called adbWireless.
It's AWESOME! No need to use USB or worry about drivers, just install the app, push the big huge button and then type the adb command it shows you to connect to your device. Worked absolutely perfectly on my Nook... haven't tried it on my Aria, but next time I need to ADB something on it, you can bet I will!
did anyone check their tools directory?
ie: C:\android-sdk-windows\tools
LOL
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Has winxp, tmobile GT
I had this same exact problem, but I was just able to get it working. First, this website is helped a lot:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Also, make sure you download the Java SDK package from the link given on that website.
Second, when the website says to "Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool" open command prompt and enter this code:
cd (enter the path to where the android SDK was installed), for example:
cd C:\android\android-sdk-windows\platform-tools
Notice how I entered "platform-tools" instead of just "tools" because this is the folder where the adb file is download with the android SDK. After you do this, you should then be able to apply adb codes (make sure the screen on your tab is on because you will have to accept superuser prompts, therefore your tab needs to be rooted).
Every time you open command prompt, you will have to enter:
cd thentheplacewheretheandroidSDKisinstalled
as stated above before you are able to enter adb commands.
Hope this helps!
@caveman999 is giving good advice. Working in the command window is weird to those who did not use old pc-dos environment.
You have to be in the tools directory or you have to edit your PATH in windows so you can use adb from any prompt.
thnaks for both of you guys i installed the java jdk and also specified the path in environment variables but still error message!
I could only get adb to work error-free when I was in the same directory as adb.exe program. Just change directories cd..(enter) etc until you are in that directory.
tabing said:
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Click to expand...
Click to collapse
I had the same error, until I downloaded and placed the .adb files accordingly.
Source: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
"UPDATE: If it says adb not found or something similar, download the ADB files and extract them into the Tools folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back)."
download adb files from here: http://www.megaupload.com/?d=RTEY0Q97
The important thing is to put the files really under the "tools" folder.
When you check out above Source I am sure your problem will be solved
Thank you all problem solved
tabing said:
Thank you all problem solved
Click to expand...
Click to collapse
Glad to here it. Why not hit a few thanks buttons?!
I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.
Hey guys, I'm finally working up the courage to root. I installed adb on my Macbook but I can't find where the platform tools folder is at. I used the Android.zip file and ran the Adb-install-mac.sh script to install adb. The computer recognizes the phone via adb devices and I'm able to reboot into boot loader and get fastboot oem device-id (needed for us996 unlock). My obstacle now is getting the exploit files into the platform-tools folder so I can begin rooting it. Problem is.. I can't find where the Adb-install-mac.sh script installed adb folder. Ive searched the hard drive and nothing comes up.
EDIT
Forgot to add.. The documentation for the adb install states that adb and fastboot installs in usr/bin. Do I copy the exploit files/twrp/superSU into that directory? I don't see any folders in there.
I figured it out. Got it rooted. Not as scary as I thought it was going to be.