Related
Hi,
I am new to Android. I have downloaded and installed every necessary component in order to start working with Android. The issue I am having is that in Command Prompt, anything I type in related to the Android SDK (for example: adb, or even just android) comes back with "Java was not found in your path". Now, I have changed all my PATH variables under "User" to the EXACT locations of where these folders are, but no dice. It keeps telling me to go and edit my PATH variables. Even running SDK Setup, gives me the same error, and tells me to add where Java was found (even though I have!).
I am starting to get really fed up with this, because Eclipse can't find the "jre" folder inside the Java JDK, either (that is, of course, until I copy the entire jre folder inside of the eclipse folder, or put eclipse inside of the JDK folder)...
I just know it shouldn't have to be this tedious to set everything up and I would really appreciate it if someone can help with this
I am running Java JDK 1.6.0_21 (x64), Eclipse Helios (3.6) IDE for Java EE Dev., Android SDK Revision 6, all on Windows 7 Ultimate x64.
Something to note: I have not encountered any problems with Eclipse Helios and the ADT plugin as stated on the Android Developers website. I can use Eclipse and the SDK to create and run the"Hello, Android!" application on the emulators without issues. I just want to be able to run everything from the command prompt, too. Now, if I can only get my phone to be recognized after I get this resolved.
I also need this for rooting and unlocking the phone.
Bazz44 said:
Hi,
I just know it shouldn't have to be this tedious to set everything up and I would really appreciate it if someone can help with this
I am running Java JDK 1.6.0_21 (x64), Eclipse Helios (3.6) IDE for Java EE Dev., Android SDK Revision 6, all on Windows 7 Ultimate x64.
Click to expand...
Click to collapse
In the SDK tools folder go to libs and edit find_java.bat.
Change all instances of %PROGRAMFILES% to %PROGRAMFILES(X86)% .
I had to do this for my SDK.
Your java will probably still resides in c:\program files (x86)\java or the likes.
To test if it works open DDMS.bat(May need to open twice).
I ran "ddms.bat" before changing the "find_java.bat", and it just came up that it could not find the path > checking if it is installed elsewhere. I did what you suggested (I found three instances of where I needed to add the (x86)), ran "ddms.bat", and got the same error. However, this time it also opened the Dalvik Debug Monitor. Eclipse still won't run without its own copy of the "jre" folder from the JDK at the same folder level as the "eclipse.exe"...
any luck with this? I'm also having same trouble in Win7x64
Gonna give in otherwise n reboot my ubuntu system see if thats any easier
i know i can't use OpenJDK or something so ill have to swap that but fingers crossed
=]
Solution
Install any JRE Java, Copy the java folder at program files/Java/jre6 Paste it inside MOTODEV´s folder program files/Motorola/MOTODEV Studio for Android 1.2/ and rename it to jre
Done
Edited the eclipse .ini works a treat now wi java x64...
time to whip out the olde java books from college an see if any of it comes back to me
Is it possible to install the android sdk platforms & extras offline manually, my only net atm is my desire tethered, unlimited data but I don't wanna push my luck
I'm not sure if it may be related or not but according to the android dev page, you should be using eclipse 3.5 because they have been having problems with 3.6
May or may not be related but worth a shot.
I'm not sure if it may be related or not but according to the android dev page, you should be using eclipse 3.5 because they have been having problems with 3.6
May or may not be related but worth a shot.
i need help http://forum.xda-developers.com/showthread.php?p=24028502#post24028502
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Make nu system path
Try making new system path named PATH (all caps). its an issue with Win7 64. Hope it helps. and yes Installing the Android sdk is a giant head****. I have it all put as fare as the link to abandroid put it doesn't make plug-in available in the plug-in list. I'm at a loss...
As i said, hope it works.
Having just had this issue myself on a new install of eclipse, the sdk and adt, here's what finally helped me: making sure the java\sdk1.6.x.x\bin directorywas in front of the windows\sys32 directory in the PATH statement of the environmental variables.
I did already add the JAVA_HOME and such, but the above was the step that finally allowed me to finish the setup.
Fix for Win7 64bit and Android SDK/Java install
MacDegger said:
Having just had this issue myself on a new install of eclipse, the sdk and adt, here's what finally helped me: making sure the java\sdk1.6.x.x\bin directorywas in front of the windows\sys32 directory in the PATH statement of the environmental variables.
I did already add the JAVA_HOME and such, but the above was the step that finally allowed me to finish the setup.
Click to expand...
Click to collapse
I had to finally use JAVA_HOME C:/PROGRAM FILES/JAVA/JDK1.7.0_05 That finally allowed me to instal the Android SDK
best answer
rowdyvc said:
I had to finally use JAVA_HOME C:/PROGRAM FILES/JAVA/JDK1.7.0_05 That finally allowed me to instal the Android SDK
Click to expand...
Click to collapse
Thank you you solve my prob man
Hey guys, Ive just purchased a new x64 windows7 computer and am having difficulty getting the SDK installed.. I had it on my xp 32bit just fine, but the installer for android sdk wont recognize that I have the Java SE JDK installed and is telling me to set an environment variable to point to it. I am not all that familiar with setting Environment variables, or the new OS, any help would be greatly appreciated thanks. Just looking to get adb running for GB and above for ODIN, not looking to develop.
To install Odin3 and flash roms you don't use adb.exe for any task.
But the answer to your trouble is your path.
I wish that i knew more about ADB, and the SDK...
I did manage to establish a working development environment last spring, but the system I use is only a 32 bit environment.
The time since my setup has been so long ago now, that I have forgotten the particulars of the build. But I did learn a great deal from the guides posted here:
http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Forgive my limited reply, as I desire to help you, but its quite clear that your knowledge of the android SDK exceeds that of mine.
And if you dont mind, I wish ask a question of you.
As you have used the 32 bit SDK successfully in the past, is it possible to copy and transfer all of the files needed to produce a working environment by simply loading said files from one PC to another ??
Or is the environment an individual set of parameters that must be created for use on each machine ??
I have never been successful in my search for an answer to that question.
Im sorry that its such an off topic request, but I truly wish to learn more in my old age....tbank you...g
rangercaptain said:
To install Odin3 and flash roms you don't use adb.exe for any task.
But the answer to your trouble is your path.
Click to expand...
Click to collapse
Thanks for the quick response, yea i gathered that much with the path , just dont know which field to put it in under environment variables or the proper format.. my question is how to properly set environment variables for the sdk to install.. Or just even a workaround for getting ADB up on windows 7.. Had no issues whatsoever on XP.. I Extracted the java.exe to the path the sdk software is looking, and still no luck (i like having ADB to push apks, root or recoveries n such when not looking to ODIN etc) I've tried several different tutorials and can't seem to get past the install of the sdk verifying i have the java se installed. ..
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
gregsarg said:
I wish that i knew more about ADB, and the SDK...
I did manage to establish a working development environment last spring, but the system I use is only a 32 bit environment.
The time since my setup has been so long ago now, that I have forgotten the particulars of the build. But I did learn a great deal from the guides posted here:
http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Forgive my limited reply, as I desire to help you, but its quite clear that your knowledge of the android SDK exceeds that of mine.
And if you dont mind, I wish ask a question of you.
As you have used the 32 bit SDK successfully in the past, is it possible to copy and transfer all of the files needed to produce a working environment by simply loading said files from one PC to another ??
Or is the environment an individual set of parameters that must be created for use on each machine ??
I have never been successful in my search for an answer to that question.
Im sorry that its such an off topic request, but I truly wish to learn more in my old age....tbank you...g
Click to expand...
Click to collapse
My apologies if i sounded sassy in my response, i didn't mean to offend and am very thankful for all that u contribute here on xda and ur response. As for your question, i believe IMO due to the heavy reliance on drivers for the SDK to run for "X" device(s) development is being implemented on, it would more than likely need to be created specific to each machine during the install of each runtime ..but would imagine certain elements could be transferred or copied across. . But again just my guess, for i have not tried. I am new to win 7 and a NEWB to XDA. .. You sir are the mentor in this happenstance. Thanks again for the link and advice.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Make sure you installed 64bit java. I had the same problem and it turned out I kept installing the 32bit java. Their downloads can be very confusing.
Right click on "computer" on the start menu or in Windows explorer. Then go to properties.
On the left you will see an option that says "advanced system settings"click on that.
In the new window there will be 5 tabs up top, go to the "advanced" tab which is in the middle.
Once there, at the bottom is a button that says "environmental variables"
Click on that and there will be a new window broken into 2 sections: user variables, and system variables.
Go down to system variables till you see one named "path" select it and choose edit.
Now, you should have the java jre installed.
I have a 64 bit environment with 32 bit java,.That's fine.
The path that is installed to, and what you want to enter into your variable is:
;C\program files (x86)\java\jre7\bin
Close that out.
Now open a command prompt and simply type java, if you get a long list of details that tell you the commands you can use, congratulations java is now in your path.
If it says "java is an unknown command" you have messed up somewhere.
Ok, now that you have adb installed, go to the platform-tools folder.
Copy:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
And paste those into your main Windows folder.
Now, you can enter adb command from any directory, you do not have to cd to the platform-tools folder first.
Excellent ....
Many thanks !!.....g
studacris said:
Right click on "computer" on the start menu or in Windows explorer. Then go to properties.
On the left you will see an option that says "advanced system settings"click on that.
In the new window there will be 5 tabs up top, go to the "advanced" tab which is in the middle.
Once there, at the bottom is a button that says "environmental variables"
Click on that and there will be a new window broken into 2 sections: user variables, and system variables.
Go down to system variables till you see one named "path" select it and choose edit.
Now, you should have the java jre installed.
I have a 64 bit environment with 32 bit java,.That's fine.
The path that is installed to, and what you want to enter into your variable is:
;C\program files (x86)\java\jre7\bin
Close that out.
Now open a command prompt and simply type java, if you get a long list of details that tell you the commands you can use, congratulations java is now in your path.
If it says "java is an unknown command" you have messed up somewhere.
Ok, now that you have adb installed, go to the platform-tools folder.
Copy:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
And paste those into your main Windows folder.
Now, you can enter adb command from any directory, you do not have to cd to the platform-tools folder first.
Click to expand...
Click to collapse
Thank you very much sir for the indepth instructions. . Between your directions and gregsarg's link i was able to get adb up by using the 32bit ver download instead of the 64bit even though my machine is 64bit... Guess there is at least a little functional backwards compatibility left in win 7 afterall. ..:thumbup::thumbup:
Please re-edit your title so you have [solved]Original Question so others having the same issue can enjoy the given solution. Thank you.
Hello,
I can't get Android SDK manager to run on Windows 8 x64. Every time I run the executable a command prompt window flashes briefly and then nothing happens. I have tried installing both 32 and 64 bit version of JDK 1.6 and running SDK manager with admin permissions and in compatibility mode.
Any help would be appreciated
kevdliu said:
Hello,
I can't get Android SDK manager to run on Windows 8 x64. Every time I run the executable a command prompt window flashes briefly and then nothing happens. I have tried installing both 32 and 64 bit version of JDK 1.6 and running SDK manager with admin permissions and in compatibility mode.
Any help would be appreciated
Click to expand...
Click to collapse
It runs fine for me on Windows 8 Pro x64. The command propt window does flash, but the manager comes up soon after. I have JDK 1.7 though.
Theonew said:
It runs fine for me on Windows 8 Pro x64. The command propt window does flash, but the manager comes up soon after. I have JDK 1.7 though.
Click to expand...
Click to collapse
Thanks so much for the info I tried again with JDK 1.7 and it works now
kevdliu said:
Hello,
I can't get Android SDK manager to run on Windows 8 x64. Every time I run the executable a command prompt window flashes briefly and then nothing happens. I have tried installing both 32 and 64 bit version of JDK 1.6 and running SDK manager with admin permissions and in compatibility mode.
Any help would be appreciated
Click to expand...
Click to collapse
The same was in Windows7 64-bit for some SDK version (dont remember version number).
It was solved by switching off some windows security checking. May be this is not best solution, but works.
Got a fix
I was having this problem too. It's caused by the PATH variables to java.exe being set incorrectly. You can modify the environment to have java_exe pointing to wherever it is C:\Windows\System32\java.exe for me or modify android.bat in tools to change set java_exe= call lib\find_java.bat if not defined java_exe goto :EOF
to this: set java_exe="D:\Program Files\Java\jdk1.7.0_07\bin\java.exe" where the path is the path to your java exe
you can then run android.bat and it works. The reason (re)installing java works is because it adds the path variables for you. They must have gotten changed/moved when I upgraded to windows 8
I'm having the same issue. Installed JDK 1.7 but still the same issue.
I have a fresh Install of W8 and am just now trying to install JDK and SDK.
.
I also cannot launch SDK Manager
o0rebelious0o said:
I was having this problem too. It's caused by the PATH variables to java.exe being set incorrectly. You can modify the environment to have java_exe pointing to wherever it is C:\Windows\System32\java.exe for me or modify android.bat in tools to change set java_exe= call lib\find_java.bat if not defined java_exe goto :EOF
to this: set java_exe="D:\Program Files\Java\jdk1.7.0_07\bin\java.exe" where the path is the path to your java exe
you can then run android.bat and it works. The reason (re)installing java works is because it adds the path variables for you. They must have gotten changed/moved when I upgraded to windows 8
Click to expand...
Click to collapse
I am having the identical problem. I try to launch SDK Manager and get a quick cmd flash and then nothing. I am on Win8 Pro with jdk 1.7.0_21.
I added c:\Windows\System32\java.exe to the path (correct on my system) but no obvious change in result. Then edited set java_exe in android.bat to "C:\Program Files\Java\jdk1.7.0_21\bin\java.exe" and ran the batch file, and still I just get a quick flash of the command window. My java sdk was just installed today prior to setting up the ADT Bundle for Windows. Eclipse loads with ADT, but the SDK Manager is still a no go. Thanks in advance for any ideas.
Solved my Windows 8 problem
Hi,
I have been having similar problems with Android SDK manager not starting in Windows 8. Tried altering Java paths and messing with Android.bat etc. etc. but am now convinced the problem is with the UAC of Windows 8. Why?
1) Originally installed Eclipse in a sub dir of Program Files and found that I could not edit any sub dir there (like Android.bat) because of User Access Controls (UAC)... got me thinking...
2) So re-installed Eclipse in a sub dir under my user, and bingo... SDK manager works fine now.
It is possible to disable all UAC in Win 8 Pro using secpol.msc, but I don't have Pro version and it's not in bog standard version... However, you can still edit the registry to give all apps admin privileges but seems a bit drastic to have to do this...
http://developer.android.com/sdk/installing/bundle.html
Install the SDK and Eclipse IDE
1.Unpack the ZIP file (named adt-bundle-<os_platform>.zip) and save it to an appropriate location, such as a "Development" directory in your home directory.
try c:\Development\
aleks3008 said:
http://developer.android.com/sdk/installing/bundle.html
Install the SDK and Eclipse IDE
1.Unpack the ZIP file (named adt-bundle-<os_platform>.zip) and save it to an appropriate location, such as a "Development" directory in your home directory.
try c:\Development\
Click to expand...
Click to collapse
This is what worked for me. Thanks!!!
I originally had it in User\Documents\
same problem
I am having same problem like you buddy.help would be much appreciated.
Same here
Yeah I've reinstalled everything as described here, and I am still unable to get it to launch. Just getting the brief flash of a CMD prompt.
Finally solved it!
I had the exact same problem. I have gone crazy trying to fix this for past 1 day. Finally solved it using this guide: http://www.dominantwire.com/2015/03/android-sdk-not-opening.html.
Had to do some tweaks in the android.bat file and re-specify the environment variable paths. The solution is pretty universal. Should work for you guys as well.
Noob question
Recently I have been working on an app for work. Things are going well, no issues. Using eclipse ide with android adt, etc. My question is, can i execute adb commands from anywhere inside eclipse. In the past, i have always done it from the command line. But in reading from the android developer site, and in talking to a friend Java developer (not android), you should be able to execute the command from somewhere inside eclipse. The problem is i cant find where? I cant type anything in the console window. There is nothing in debug or ddms. Thoughts?
Sorry for the noob question, but we all start somewhere.
Thanks.
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.