Database Info

ADB USB Driver

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 just need a little help

I currently have a mytouch 3g and am running a slide rom on it, problem is there is no keyboard, how do I manually install an apk file preferrably from the computers console such as swype or astro both of which apk files are currently on my sd card. Any help is much appreciated, I started using this forum in 2008 but have never once posted, sad really. ive been trying to install it via adb commands but I keep getting device not recognized errors, feel free to flame my noobishness

Once you have a file explorer you can just click on APKs to install them. If you don't have access to the market to get a file explorer you will have to install them using the ADB method. I found a forum post that gives some rough instructions, but it sounds like you don't have ADB set up correctly. Also I believe the path used with the adb install command is the location of the apk on the PC.
http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/
The following is a response to someone having a similar problem on another site:
http://www.androidkit.com/steps-to-install-and-uninstall-apk-file-on-android-g1-device
The message is coming because the drivers for the G1 Android device are not properly installed.
If you are running windows, Check so:
Right click on My Computer, and click Manage, then go to the device manager
If you see an “ADB Interface” category at/near the top, with “HTC Dream” under it, then you’re good to go.
Else, you need to install the drivers by pointing to the driver location to the usb_driver folder under the android sdk folder installed by you, while the device is connected, and the system prompts for it.
Click to expand...
Click to collapse

Portable ADB prompt

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.

ADB Help

Hi,
I have a Yarvik Tab250 and I want to modify the build.prop so i can install any app I'd like to. I've found the info i need to do here:
w w w.hembrow.eu/personal/yarviktab250.html
But I can't get ADB to list my device, my device is on, and debugging is turned on, and it can't list it under "adb devices". I know on linux you have to make a specific folder or something like that, do you have to do anything special in Windows? I only really have access to Windows, and limited linux knowledge.
As mentioned above, Also, if anyone can help with flashing a working play market on my tablet, i'd very much appreciate it!
Thanks!

You need to have the android SDK installed properly on Windows. The path stamemt must be correct for ADB to function properly.
Sent from my LG-P500 using XDA

Do you have the proper drivers for it installed
Sent from my HTC One X using Tapatalk 2

adb is an application that is part of android SDk and can be run from the command prompt in Windows. There is a windows application Android Commander that uses a gui to issue adb commands, it is very powerful program and I recomend it. you will be able to use it to pull the build.prop file edit it with a text.editor and push it back to the Phone. It can connect to the phone by wifi or with the usb cable. Of course android bebugging must be enabled on the phone. you can find it here. http://androidcommander.com/
I hope this helps.

ADB for dummies
http://forum.xda-developers.com/showthread.php?t=502010

[Q] ADB, RSA, Android 4.2.2, Android Commander

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!