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...

Can't get adb to run

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

Unlock Xoom on a Mac running Parallels

Hey folks -
I am a proud new owner of a Xoom, and would love to unlock and root it! I have had a Droid X for a while now, and while it is rooted, rommed and the rest, I have not dealt with a bootloader before. All I had to do was use Z4root and go from there, simple. I used a friend's PC at school to learn how to SBF if needed, and that's as far as I've gotten with Android.
I could really use help with unlocking the Xoom. I am running Parallels on my Mac (Windows XP Home) and am unsure how to go about installing Android SDK. Motorola Drivers I think I am all set, I've run the program and it says I'm up to date. With Android SDK, however, I downloaded the zip and it says there are no files to extract. I run the installer program for Android SDK, and it says I need Java JDK. I download Java JDK, and yet Android SDK installer program still says I don't have it.
I would really appreciate where to go from here, and I apologize if this has been covered somewhere else, but I did look around for quite a while and I don't want to do anything prematurely and mess up a $600 device. Again, apologies for my nOObness.
Thanks!

Sorry to bring this thread back from the dead, but I did exactly what you are talking about doing. Boot into your virtual machine and install all the sdk, moto drivers, and fastboot.
When connecting your xoom, enable USB debugging and make sure the usb device (when plugged in) is attached to your parallels machine only, it should give you an option when booting it up.
Everything works as normal, Parallels really has no drawbacks, just follow the root instructions as if you were doing it on a native machine.

I actually ended up just doing everything on my Mac natively, but thanks for the info! I think I was more confused on actually installing the SDK properly than anything else.

[Q] adb doesn't recognize my phone

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

ADB Problems with Emulator

Okay. I have been trying to do other things with rooting other phones besides my HTC Rezound. I've rewritten a exploit so it will work on Mac. But this is a general problem. I deleted the Emulator and every single thing but the platform-tools on the windows side of my computer. So the only thing I have on my computer is the platform-tools folder (aka fastboot and adb) So I have tried what almost every forum has said. The adb kill-server. I restart it. Still there. I've tried to individually kill it still there. I've unplugged my device and ran adb still there. The Emulator is Port 5554 offline. I can't get it to come online, I have spent hours trying to kill it. This is one reason that stopped me from rooting on a windows because this stupid emulator won't go away and it never has. I've never ran eclipse on the windows side or to say that never anything but the adb and fastboot. Only the Mac side have I done other things. Please if anyone could help that would be nice. It'd save me time from having to take the .bat files and changing them to sh files and opening with text edit, editing the file to work with terminal, then sh run the file and it not work then back to the drawing board which after rewriting some stuff over and over is a miracle to see it finally execute the exploit. Thanks for any help. I would gratefully appreciate it. Thanks. This is the also what's from keeping me going s-off to. It's annoying and I would really love to fix the issue. I will take any advice. Just saying though the adb kill-server and a lot of other commands are not working and not doing the process. Please anyone who would like to help. Just put anything :$ Please and Thank you.

Bump
Sent from my Rezound using tapatalk. CyanogenMod 11. S-off.