Related
the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.
Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.
I have the same problem... working on it now...
I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.
It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Thank you dagentooboy!
Can someone explain this for this not so savvy person?
chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.
Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.
yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.
Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..
check too make sure your Android isnt listed under usb mass storage devices in device manager.
Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.
my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this
Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...
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 have tried everything to get a one click solution to enable non-market apps. First and foremost I am on a MAC. No access to a windows machine. I have my phone rooted and have installed superuser status.
I am looking for a solution that will let me install (easily) non- market applications. There appears to be several solutions doing this on a windows machine. I have not been able to find a solution on a MAC. And instructions, help, videos anything is greatly appreciated.
Thanks
PS: not a total nube, but I have limited knowledge of the root directory and manipulation, but follow instructions well ........
What firmware are you on? Because if you are on the leaked 2.2 you should look on the leaked ji6 hacks forum page and it will give you the instructions that you can run in adb shell in the terminal application on a mac you just have to type ./adb (command) where windows users just have to type adb (command) you should make sure that you are comfortable on adb though because there are hardly any tutorials for adb on a mac around. I found that the hard way. Hope this helps, if you still can't figure it out post more info and I will do my best to help although I am still kinda a noob to android development.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thank for the help, I will look at thie ji6 hack and see if it works. I'll let you know. Right now I have spent 3 days trying to unlock this pile of dung. ATT should be shot for doing this people. We bought the phone let us put what we want on it. PERIOD
Have you tried ADB? If you can get ADB to work, you should have the skill to copy over the settings.db and use the SQLeditor for Firefox plugin. Or use SQLite on the phone.
Read up on how to enable sideloading - the same commands that work on windows work on a mac - or very similar. As long as you know how to copy files in terminal you should be set.
Hi, I have successfully installed Kali Linux on my LG G3 using Linux Deploy and VNC viewer. I am successfully able to use everything, but I am relatively new to Linux. Still, I was able to switch to root in the terminal. I also tried creating a new account, giving it root access, and then switching to it, which I was able to do, again only in the terminal. However, even if I had root access in the terminal (confirmed by "whoami"), it seemed that I did not have any other root privileges. For example, everything, including the desktop, was read only. I tried switching users using the gui and that did not work at all. I also tried to open the root folder under computer and I wasn't able to do that either. I have tried changing the preferences in linux deploy to log me in as username "root," but I think even then I am logged in as a user that is named root... not the actual root administrator. If anyone could offer some guidance with this situation that would be great. I have spent a lot of time searching google and more to find the solution to this problem, but I haven't had any success. Thanks in advance.
I'd also like to add that some normal commands were not accessible in the terminal even though it said that I had root privileges. Therefore, I could not get done what I would like to even if I were to do everything in the terminal .
jackfitz5 said:
Hi, I have successfully installed Kali Linux on my LG G3 using Linux Deploy and VNC viewer. I am successfully able to use everything, but I am relatively new to Linux. Still, I was able to switch to root in the terminal. I also tried creating a new account, giving it root access, and then switching to it, which I was able to do, again only in the terminal. However, even if I had root access in the terminal (confirmed by "whoami"), it seemed that I did not have any other root privileges. For example, everything, including the desktop, was read only. I tried switching users using the gui and that did not work at all. I also tried to open the root folder under computer and I wasn't able to do that either. I have tried changing the preferences in linux deploy to log me in as username "root," but I think even then I am logged in as a user that is named root... not the actual root administrator. If anyone could offer some guidance with this situation that would be great. I have spent a lot of time searching google and more to find the solution to this problem, but I haven't had any success. Thanks in advance.
Click to expand...
Click to collapse
There is not a specific XDA forum for Kali Linux.
You might find some help in Ubuntu Touch General
or [APP] Linux Deploy by AbuYahya
Which S3? SGH-I747 or I9300, I9305 ...
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.