how did you guys install the android sdk? - Android Software Development

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

Related

installing sdk complications

i have downloaded the android sdk for the saphire and am having trouble in the command prompt with the given command. the wiki says to put adb and it should run smoothly but this is not working for me.
I saved the .zip file in a new folder at C:\androidSDK and it is still not working.
Can anyone help me PLZ!?!

Can someone help me with booting debian ?

I am following this guide here, http://ubuntuforums.org/showthread.php?t=1413313 but when i type the command
"sh android-sdk-linux_86/tools/ddms"
it says it can't open the file. Any help would be great. Thanks
btw i am already unlocked and rooted so i just need to do steps 2 and 5
does the file exist?
ddms is part of the android sdk. i'm assuming you have installed the linux version of the sdk and know where the tools directory for the installation is?
i don't think you are even required to run this step anyway:
Code:
Now, for example, if you plug in the phone and run
$ sh android-sdk-linux_86/tools/ddms
[b]you will see the phone listed. (Note: this is not a step in the howto) [/b]
-verify the file exists at the location specified
-make sure it is executable to the current user (chmod +x)
or post the exact error message here
Yep the file is there and in the right place but when i type it it tells me "Can't open android-sdk-linux_86/tools/ddms"
Anyone...all i need is to get ubuntu to recognize my phone when i plug it in...
Hmm, seems a little odd. If you type the same command but replace the "sh" with "ls -l" what comes back? Plus, what user are you logged in as?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I got it working yesterday, not sure what i did but ubuntu recognizes my phone now.

[Q] assiatance with adb please any one

hi guys im getting anoyed with my pc and phone now ive followed so meany tutorial etc on how to install adb but still not getting any where so far i have done
1. downloaded sdk from code.google.com
2. extracted to c:/android-sdk-windows
3.installed htc wildfire drivers
4.created a path on enviromentable variuble
5.ive loaded the skd.exe
6. ran cmd and ran adb and adb devices but my pc will not reconise this command any adice please thanks
ps ive also tryed using qtaADB it connect to the phone but dnt show any thing frustrated now lol thanks daddyspud
First download adb for windows from " http://developer.android.com/sdk/ ".
then u will get a file named " android-sdk_r08-windows ".rename it as "Android SDK" after extracting.
download proper driver for your phone and install them .now move "Android SDK" to root of hard drive that is to c\Android SDK...
now update the adb using SDK manager that is inside Android SDK.all packeges even usb drivers.
connect the phone via usb and windows should recognize it as android phone .
now take "cmd".command prompt and type the following code .
cd\
cd Android SDK\tools\
adb devices
Now Adb is set if it shows your phone code ..
Sorry about my english .
I had a hardtime making my computer recognize my wildfire, I had to manipulate the driver to make it find it. just google it and you shall find .. if thats the problem ..
thanks worked a dream cheers buddie
They changed the location of the adb.exe file with the new SDK release using the example given would be :-
cd\
cd Android SDK\platform-tools\
easier in my opinion to add to path in windows
c:\android sdk\platform-tools\adb.exe
make sure u add java.exe to path aswell
Hope this helps
ok i got that and it worked, ie picked up my device, then what do i do?
magpie22 said:
ok i got that and it worked, ie picked up my device, then what do i do?
Click to expand...
Click to collapse
Well what do you want to do with adb?
run the sdk but i get errors when i start it "error 2" cant find file.
Failed to get the adb version.
Edit - Never mind i have sorted it.

adb no longer working

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

Uninstalling Touch

I have the original OnePlus One, I threw touch on it ages ago and have since tried revert back to android but cannot seem to figure out how.
I run windows 10, and the only script I found was for linux.
I can create a live CD and fumble through it if needed, but I was hoping someone had instructions to do this through windows 10
Thanks
cblock said:
I have the original OnePlus One, I threw touch on it ages ago and have since tried revert back to android but cannot seem to figure out how.
I run windows 10, and the only script I found was for linux.
I can create a live CD and fumble through it if needed, but I was hoping someone had instructions to do this through windows 10
Thanks
Click to expand...
Click to collapse
Try via the windows subsystem for linux setup. It should work like a nativley running linux install.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Try via the windows subsystem for linux setup. It should work like a nativley running linux install.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
it doesnt have full usb support *yet*
Download adb and fastboot, you can find them on the Chocolatey Package Manager for Windows for easy installation, or install them using the Android SDK, or by downloading the platform-tools package from Google's Developer Center. And then, reading the script you have, translate those commands over to Windows. So for instance
Code:
#!/bin/sh
adb reboot-bootloader
fastboot -w
fastboot flash system system.img
would still work under Windows, but you'd need to use command prompt, and you need to have your current working directory set to the path where you've got the ROM at (so CD to it, ALSO: if you are using ADB/fastboot binaries and opted not to install them using chocolately, you will need to make sure those binaries are ALSO in that path.)
You can also open the .sh file, and instead, remove any shell script directives (I wouldn't think that a flash-all script would have things like conditionals though), and then save it as a .cmd or .bat file in your ROM (or ROM & platform-tool) folder, then double click it. For instance, the above would become:
Code:
REM This is an example batch script
adb reboot-bootloader
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash somepart somepart.img
and so forth. I hope that helps.

Categories

Resources