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...
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.
Portable ADB Prompt
If you're on the road and you need an ADB prompt to interact with your phone, many people will be lost as to what to do. It's kind of hard to carry the Android SDK on a flash drive, and if you're doing that solely for an ADB prompt, then it's kind of useless.
Basically, I've packaged an ADB prompt into a portable package for debuggers, hackers, and others to carry on the road. It fits on a small USB drive, and can even sit on your phone's SD card slot, ready to use.
You don't need a working copy of the Android SDK to use it. I've tested this on several computers, with and without the SDK on them.
So far a Windows-only copy is working fully. I haven't started on a Linux repackage, and perobably won't do a Mac port (unless a Mac owner/user is willing to).
All you need to do is extract the package, run adbprompt.bat, and you're good to go!
I'm sure this is stable enough for everyday use. Although seeing as I haven't explored every single facet of ADB on this portable package, I can't be too sure. It's labeled as a BETA until I've confirmed its stability.
Download link is below.
This is pretty handy to have. I'd be willing to look into this for a mac. If I'm not mistaken, it should just be one file. I've been playing around with a 1-click-root for mac and come to find that only the adb file from the sdk is needed for the command prompt to work.
Sweet, feel free! It's be pretty cool if you could put it up in this thread to - y'know, as a central hub for portable ADB prompts.
If you want, you could do a port/repackage. Basically it's just caling the ADB executable, executing adb command, and looping back to ask for more input. Simple, really. Easier than cding to the directory with the exe and all that wankery.
The best thing to do by means of disribution would be to package it in a .dmg and make it call a script to to the input-execute-loop thing (I don't know much about Mac file extensions). If you understand Windows batch code, you could try interpret adbprompt.bat to work with the Mac's native shell code - which I think is .sh, correct me if I'm wrong.
So yeah, port it if you want, send it my way through a PM (upload it to mediafire or something), and I'll put it up - with appropriate credit of course
Kickface said:
Portable ADB Prompt
If you're on the road and you need an ADB prompt to interact with your phone, many people will be lost as to what to do. It's kind of hard to carry the Android SDK on a flash drive, and if you're doing that solely for an ADB prompt, then it's kind of useless.
Basically, I've packaged an ADB prompt into a portable package for debuggers, hackers, and others to carry on the road. It fits on a small USB drive, and can even sit on your phone's SD card slot, ready to use.
You don't need a working copy of the Android SDK to use it. I've tested this on several computers, with and without the SDK on them.
So far a Windows-only copy is working fully. I haven't started on a Linux repackage, and perobably won't do a Mac port (unless a Mac owner/user is willing to).
All you need to do is extract the package, run adbprompt.bat, and you're good to go!
I'm sure this is stable enough for everyday use. Although seeing as I haven't explored every single facet of ADB on this portable package, I can't be too sure. It's labeled as a BETA until I've confirmed its stability.
Download link is below.
Click to expand...
Click to collapse
With Your permissions i would like to upload this file and any updates of it to my dropbox to share on OXygenRom Forum
Regards
Yeah, sure! Feel free! Just make sure you credit Kickface of xda-developers forums for the package.
And although I don't own a Desire, I've joined up at the forums.
Good luck with the ROM!
Cool think for my flash-drive, but this version doesn't support the 'connect' command or?
i wanted to use it with the App 'adbWireless'.
Great. Exactly what i was looking for. I will try this and report back.
Sadly, I get an error saying "the system cannot find the file specified" with every command I try to run
I think a "portable" ADB is already in the SuperOneClick root solution. It has a folder called adb with the executable and a couple of .dll. It worked great on first try, so to anybody who this might not work, you can download SOC and extract the folder from there.
Thanks for your work though
Sweet. This is pretty much an essential tool for me.
You should add an if/goto label command before the 'cd src' so it only tries to cd once. This would prevent the 'The system cannot find the path specified.' message after every command
:newline
if exist AdbWinApi.dll goto jump
cd src
:jump
Thank you so much for this.
I moved your batch file in the "src" directory and modified line 12 to make it more "portable":
Code:
cd %~dp0
nice software but seems it is a bit out of date, my Note 4 with 5.1.1 doesnt get recognized.
Hi guys, I own an Xperia X8 running MiniCM RC1 Froyo. Let's say I have stock ROM with rooted phone. If I wanted to change the framework, I would use adb shell. Well...I have NO IDEA what adb shell is. Is this something like a command prompt? Do I access it from my phone? How do I use it?
Please explain.
Thanks in advance.
ADB (Android Debug Bridge) shell is a tool that comes with the Android SDK. It runs on your PC or Mac and connects to your Android phone over USB. You can find lots of documentation here: http://developer.android.com/guide/developing/tools/adb.html
ADB is also included with AppInventor, which runs on Linux as well as Windows/Mac.
So, if I wanted to change framework-res, what would I do?
I know this is going to sound "elitist", but the right answer is "you would read the ADB docs until you can answer that question yourself." Let's face it, the amount of damage you can do with ADB is substantial. Blindly entering commands is fundamentally unsafe -- if you don't understand the command, you won't catch yourself making mistakes. And if you do make mistakes, you won't have any idea what you did or how to recover.
There are some really good (and easy) guides here: http://forum.xda-developers.com/showthread.php?t=872128 ... post #3 has what you need to figure this out and you'll gain some knowledge that may come in handy down the road.
I posted this question over on Phandroids but this forum seems perhaps more appropriate. My Lenovo laptop running XP sees my phone just fine (Samsung Gravity Smart SGH-T589) and I'm able to transfer files to/from the phone. However, adb doesn't seem to be able to see it. A search about this problem turns up solution suggestions that mostly involve drivers, but my Samsung driver is up to date and clearly working (or else the phone wouldn't show up to Windows and I wouldn't be able to transfer files). My phone is rooted, which also makes it obvious that my laptop can talk to it just fine -- I used OneClick to root it last week using the same computer.
I'm using the DOS prompt (cmd) to run adb, and adb works fine. It simply doesn't see any devices. Here's an actual text transcript:
===============================
C:\Android\adt\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Android\adt\sdk\platform-tools>adb shell
error: device not found
C:\Android\adt\sdk\platform-tools>
===============================
Any ideas? I'm pretty new to this, so perhaps I'm missing something really simple. I hope so anyway!
--
Craig
Sunnyvale, California
Make sure that USB debuggin is enabled on your device. (This option should be changed only while device is disconnected from USB).
Also, try to restart adb server by killing it from the device manager.
Thanks for the suggestions. I had indeed already done both of those things. USB debug must be enabled to do file transfers, so I already knew it was definitely on. I still cycled it off/on anyway to make sure. And I did both kill-server and start-server commands as part of my checkout to assure myself that adb was in fact working correctly. I had Windows task manager up as well so I could watch adb disappear and reappear with those commands.
--
Craig
Sunnyvale, California
Hmmm... Try to reboot both your computer and device.
Have you tried to connect other devices to ADB? May be there is a problem with ADB installation?
Phone and laptop have both been rebooted many times. I also tried it with the phone in charge-only mode because that's what One Click Root required, but nothing changed. I also tried using all of the different USB ports on my laptop and tried two different USB cables, although that was silly because the phone is obviously talking to the laptop via USB. It shows up in file explorer, and I am able to transfer files using Windows drag and drop.
I'm afraid I have only one device, my recently rooted Samsung Gravity Smart phone, so I can't try it out on anything else.
I'm not sure how the adb installation could be at fault since the commands work as long as they don't involve the USB port. And I know that it MUST be possible to shell to the phone with what's already on this computer because One Click did it. I tried running the adb commands from the One Click Root > ADB directory just in case something about that particular install of adb was different, but I got exactly the same result.
It seems to me that I must be failing to do some setup step that an experienced Android developer might know about. I've never done anything like this before, so I wouldn't have even known about downloading the Android sdk if it weren't for forums like this! I sure appreciate the community of knowledgeable people here, who are clearly willing to help newbies like me.
If there are any software tools that anyone can suggest using to help me figure out what's going on, please let me know.
EDIT: Is there something that I need to load on my phone before adb will work? It occurs to me that OneClick might push something to the phone when it does the root, then delete it when the task is complete. I tried using QTadb, which is an adb GUI, and got the same result: no devices seen on the port even though Windows sees my phone and can talk to it via USB.
--
Craig
Sunnyvale, California