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...
hello. ive been reading on different forums on the best way to sideload apps on captivate on mac. ive read about sideload wonder machine but seems ppl have problems... seems ppl r being more successful on pc.... if i were to run parallels then win 7 and try to use sideload wonder machine on pc will it work? im still reading on how to use commands, and terminals and cmd lines and all that . im new to android but familiar with winmo phones and jailbreaking iphones. so if anyone can help me or point me to the right direction, it is greatly appreciated! on a side note, i use parallel's and ran win 7 and dl droid explorer to try and delete some at&t bloatware but no go. when i try to delete it nothing happens... so i dont know what to do! lol. im rooted and all. i wanna have sideload next! thanks again guys!
1. Install Android SDK for Mac
2. Using Terminal CD to android-SDK/Tools directory
3. place your apk file in the tools directory
4. In terminal type: adb install file.apk <where file.apk is what you want to install>
This is the manual way on windows and this is what sideload wonder does for you. If you want to learn - this is the best way to start. ADB is easy, and it opens up the gateway for everything else.
YOu can probably find a more detailed tutorial on using ADB commands in Mac.
ADB is what lets you copy system files off the phone, change permissions, get access to the systems.db where you can allow sideload from phone, etc.
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.
hey just wondering about adb i need to download and adb and i am assuming some sort of device drivers i was wondering if anyone has a link for this or what versions i need and how i get adb to work before when i rooted phone i just imputed everything in the terminal emulator?
Check out guide, getting adb setup in Asus dev section. It's pretty good.
http://forum.xda-developers.com/showthread.php?t=1124217
Closing as a simple search would give you answers to these questions.
I am working on an awesome thread posted here http://forum.xda-developers.com/showthread.php?t=1886460
I have a query but can't ask at this thread as I am new to this forum so still not permitted.
The above mentioned link shows a method on "how to get root access to devices with a loophole present in Android".
I am working on Virtual Devices(Genymotion Emulators-Android 4.3) . The problem is that emulators, by default gives root access to us.
I noticed this thing when I executed 'adb shell' and I got root access. After small research, its true that emulators provide root access.
Can anyone please help me to get normal access to emulators ?
I want a shell as we get when we are working with adb and USB connected physical devices.
Any help will be highly appreciated.
Config*
Ubuntu 13.10, 32-bit.
Ecllipse 4.2 with ADT bundle.
Genymotion Emulators.