I had the SDK installed and everything was peachy but then I did a clean install of my OS.
I have reinstalled the SDK, downloaded the java ADT program, installed it, updated it, pointed it to my SDK folder, etc...
I need to use adb through the emulator as I am locked out of my handset and trying to use it to uninstall an app. (Lock 2.0 was updated, starts by itself and just gets stuck in a random cycle that will never allow you to get to the home screen... as a matter of fact home doesn't even load.)
Back OT... when I click the emulator or adb I just get the black box that flashes a bunch of command line real quick. Nothing will actually launch or open.
If you guys have any step by steps, know what I am doing wrong, or know how to get this POS uninstalled from my phone another way, I would REALLY appreciate some help. Thanks.
Related
Alright, since my google search returned the whole 2 (two!) relevant results, and the search here around 10 irrelevant, I thought I'd drop this on the community, in hope for some help.
I've upgraded my 64bit OpenSuSE to 11.2 the other day, downloaded the Android SDK, set up the environment variables, and fired up the "android" script that is supposed to download and install a platform, so I could access my device through adb shell.
Here I ran into a problem: Half of the buttons I click in the SDK updater don't seem to work, it will not save the settings, it will not remember the URL I type in (had to use http), and when it reads the http repo, it will not download and install what I have cheked! What happens is, I click the button, it appears to stick down for a while, then pops back up as if I never clicked it, and nothing happens.
My first question is, has anybody tried this on SuSE 11.2? I have had no problems on 11.1, for instance.
Second, does this need any "special" Java configuration to work properly? I have tried both the openJava (now built-in into SuSE), and Sun Java latest (SDK and JRE). I don't think so, but asking just in case...
I'm pretty much stuck. If anyone has this working, or better yet, if anyone knows where I could download platforms outside of the updater, please be so kind and share. Thank you!
P.S. Oh, and the optional third question: Is there a way to trigger the download from console? That would probably help to figure out what goes wrong...
EDIT: Not Java problem, but updater problem. It does not show any of the SDKs, it shows only APIs, which can only be added if a valid SDK exists.
Can anyone confirm this?
It seems I need an external link to SDK 1.6 for Linux (for example). Can't anyone share?
Thanks!
Still stuck...
EDIT2: Solved it, my adb works again. But the updater app is crap I installed the APIs, then shut it down, rebooted, then ran it again. Also, for some reason the buttons wouldn't respond to clicks, but if I click and then push Enter key, it works. Took me a while to figure this one out.
Hey, I'm getting ready to install Android SKD on openSUSE 11.2 from scratch. Could you list your steps and/or suggestions based on how you got it working? Thanks.
How did it go?? Sry, just saw this...
Don't have time to do the steps.. actually, everything works just as the standard procedure suggests, with the exception of button clicks - as I said, each time I clicked a button, I had to press the Enter key (as if the click was just giving it focus, but not the actual command)
Feel free to PM me (or any other user), especially if the thread is a bit old, like this one.
MountainX said:
Hey, I'm getting ready to install Android SKD on openSUSE 11.2 from scratch. Could you list your steps and/or suggestions based on how you got it working? Thanks.
Click to expand...
Click to collapse
I'm new to android hacking and all this so bare with me.
I downloaded the Android SDK and installed everything I needed. I used ECLIPS3's master app to root my Droid Eris and installed the drivers for adb when I had my phone plugged in with usb debugging. So anyways, now I'm going to flash another rom which requires me to push an mms fix through adb. But whenever I go to tools and double click on adb, it just opens up a command prompt windows, flashes through a bunch of sentences/commands (it's too quick to see) and then closes. I thought maybe it was my antivirus so i disabled it but it's still doing it. Any ideas on how to fix this? Or am I just completely doing it wrong?
Edit: Never mind I figured it out.
I have had problem figuring this out to, but this video helped quite a bit.
http://www.youtube.com/watch?v=Z3SpI7m7mFI
and this to
http://cupcakehax0r.com/blog/?p=139
When i try and open sdkmanagerexe to install i get a brief cmd screen flash but program does not run to install. Im running windows xp. I have java 6 update 26 java 7 and java se development kit 7 installed. I have sdk on root of C:/ extracted it right to there. Do not have anything in environment variables yet. I had to uninstall sdk and reinstall and deleted out of variables. Do i need a driver to open to install. Usually i install driver after. I dont know. Im lost. Really would like to get my adb and fastboot working again. Any pros out there willing to help it would be greatly appreciated!!!!! Pm me if you want or i will check back. Thanks in advance!!!!!!! Oh and isnt it possible to get adb and fastboot working without installing sdk?
Sent from my HTC Sensation 4G
Are you full admin on the xp pc? Make sure you have full read/write access to the root drive. I take it you already know how to set the variable for the tools menu. If so, try and older version of the JDK something like version six. Sometimes newer means bugs. Let me know know how it goes.
Would it make a difference putting the variable in before opening sdkmanagerexe? Because last time i installed and it ran and i didnt put the variable in till after it was set up. If you could give a recap on how to do this again it would be great. Also i changed the name of the sdk on root of C:/ to AndroidSDK. Dont know if this is throwing things off. But even when i try opening it without renaming. It still does the same. I will try downloading and installing an older version tomorrow. Ill let you know how it goes. Thank you for the response!!!! Dying to get this fixed and working!!!!! Oh and yes im full admin
Sent from my HTC Sensation 4G
Xx12thANG3LxX said:
Would it make a difference putting the variable in before opening sdkmanagerexe? Because last time i installed and it ran and i didnt put the variable in till after it was set up. If you could give a recap on how to do this again it would be great. Also i changed the name of the sdk on root of C:/ to AndroidSDK. Dont know if this is throwing things off. But even when i try opening it without renaming. It still does the same. I will try downloading and installing an older version tomorrow. Ill let you know how it goes. Thank you for the response!!!! Dying to get this fixed and working!!!!! Oh and yes im full admin
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
Yes, you have to define and place the variable before starting the sdk executable. I would restart the pc after you do the variable then try running sdk manager again.
http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.
Did you find a solution? I am having the same problem.
I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......
I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488
Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.
Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
JohnCSElwell said:
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
Click to expand...
Click to collapse
Uninstall all other drivers and android sdk.
https://forum.xda-developers.com/showthread.php?t=2788632
Use this guide and all will be fine.