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.
Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
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
Heres the deal. I have a MAC with a newly installed hard drive. On my old hard drive I had everything setup with SDK and Adb but that was when I had an HTC Hero. My problem is this: When in terminal my damn computer keeps prompting me for a password but it doesnt allow me to type anything except control C which aborts the program. It never was like that with the old hard drive.
2. Ive dl SDK for MAC unzipped it and saved it to my desktop and my hard drive.
3. When I click on tools it says "adb_has_moved.txt"
4. It says the adb tool has moved to platform-tools/ and if you dont see this directory in your SDK, launch the SDK and AVD manager and install "android SDK Platform-tools and also update my path environment variable to include the platform-tools/ directory, so I can execute adb from any location. What the heck does this mean and how do I fix it. Also how do I know if SDK is installed correctly.
5. I DL some version of eclipse that was recommended from SDK but I dont know how to use that either.
6. I have tried all the root methods shown here in XDA except the on with the Dock since I dont have a dock.
7. Also ADB does not recognize my device and my debug is selected. I cannot get it to find my device.
8. One last question when some instructions say unzipped and move the root exploit to /data/tmp/ is that the file labeled under sdcard/data or is it the one inside the Android Folder listed as "data"
Please anyone help if possible.
let me try that
Stupid question but How do I launch SDK?
laraiza said:
Stupid question but How do I launch SDK?
Click to expand...
Click to collapse
Make sure your phone has USB Debugging Mode enabled. Otherwise, adb will not recognize your device.
Check this thread: http://forum.xda-developers.com/showthread.php?t=879701
However, you will have to modify for MAC.
In my opinion the easiest way to root the Photon is still using the dock method. Otherwise, try the One Click Root method (Torpedo) as mentioned above. Then you don't have to worry about issuing all the commands.
I got it done I got it done. What I did was borrow my daughters windows netbook and the one click method worked on the first try. Thanks to all who replied. I will definitely hit your thanks buttons.
Sent from my MB855 using XDA App
im sorry.. my tool was a one click i dint think i needed to give it instructions.. especially teh part of how to run it on your computer... just fyi.. when invoking sudo (to do things as admin/root) on your computer. you are asked to enter in your password.. as a privacy/security feature it will NOT display any characters.. ergo it looks blank...
as you arent teh first one to run into this issue ill add instructions for mac users ( i know anyone running linux can figure out how to run a bash script, and windows users have a bat file after installing 209387249087 drivers... but they still figure it out ;P)
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.
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.