Having searched here and elsewhere for answers to my problems, I\'m still unable to fix this.
I\'ve installed Eclipse, ADT Plugin, and the Android SDK. My problem is
Open cmd,
go to android sdk folder,
in tools/lib/, edit find_java.bat,
you will see the lines like below, add black line to your file and save.
rem Check we have a valid Java.exe in the path. The return code will
rem be 0 if the command worked or 1 if the exec failed (program not
found). for /f %%a in ('%~dps0\find_java.exe -t') do set java_exe=%%a
this
set java_exe="C:\Program Files\Java\jdk1.7.0_11\bin\java.exe"
if not defined java_exe goto :CheckFailed
:SearchJavaW
rem Check if we can find a javaw.exe at the same location
than java.exe. rem If that doesn't work, just fall back on the
java.exe we just found. for /f %%a in ('%~dps0\find_java.exe -t -w')
do set javaw_exe=%%a if not exist %javaw_exe% set javaw_exe=%java_exe%
set javaw_exe="C:\Program Files\Java\jdk1.7.0_11\bin\java.exe"
i hope it helps
check the md5 checksum for eclipse and android SDK.It might be an md5 check sum problem.
for calculating the md5 checksum of files u downloaded you can go to http://www.guidingtech.com/9800/what-is-md5-checksum-how-to-verify-it/
for correct md5 checksum :- 1. for eclipse go to link their official download site click on downloaded package that u downloaded then go to check sum just match it with ur eclipse downloaded file. 2.for android sdk go to http://developer.android.com/sdk/index.html and click on download for other platformsand match the md5 checksum (f09aa4557bd1dc2703fde95dcdd6b92e).
i my case i downloaded all that stuff four times. with regards
ajay
When extracting the adt-bundle-windows-x86_64-20131030.zip
, three files were broken:
("sdk/tools/lib/httpcore-4.1.jar","sdk/tools/lib/find_java.exe","sdk/tools/lib/sdk-common.jar")
I don't know why but you can replace these files using old versions of android SDK e.g. android-sdktools_installer_r20.0.1-windows.exe
. It worked for me.
I found another solution, assuming you have Android Studio installed on your system:
After much searching.......and installing...re-intalling.....and changing the path of the android.bat as the answers above mentioned.....the final solution was: running Eclipse or the bat file or Android studio as administrator in windows 8 for the manager to open up!
Found out what the cause of this problem was in my case: In the registry, there was a setting to have the CMD using UTF-8 (chcp=65001).
If I double click C:\Programmer\Android\SDK Manager.exe
, I get the described symptoms.
If double click C:\Programmer\Android\sdk\tools\lib\SDK Manager.exe
there is a hint:
A pop-up stating: Failed to execute tools\android.bat
Starting a CMD window in C:\Programmer\Android\sdk\tools
and running android.bat
, gave no output, even if editing the file and reming out the initial @echo off
. Running the command chcp
returned 65001.
So changing the codepage with chcp 850 and then running android.bat again, I got output, ending with the line: call lib\find_java.bat
. This turned out to be the same problem. Each time a new CMD was spawned, the codepage changed to 65001
Fixed the problem by editing the following registry entry, deleting the value, and everything worked:
HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->Command Processor->AutoRun: @chcp 65001>nul
Having an empty value here, make the CMD using codepage 850, and the bat files begin to work again.
I am not quite sure what has made this change in the first place, but now I know the cure.