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...
Hi all,
Maybe some kind person can give me a hand with this:
I am trying to edit /etc/wifi/wpa_supplicant.conf (need this for some extra auth method in my university) on a HTC Desire (non HD) with 2.2 Froyo.
I rooted the phone using "revoked", and have Astro as file explorer and a shell terminal installed on the phone, and the Android SDK with abd.exe on Win764bit.
I tried editing the file directly with Astro (which does not seem to get root rights), no success.
'tried using adb, but I always end up having a no access. adb says the daemon is started successfully, but with "remount failed: operation not permitted".
Similar things happen with adb sysrw.
I googled some and a site mentioned a cat <some-file-name-i-forgot>
that should yield a 0, but yielded a 1.
Firewall on the Windows machine is off ofc. Bear with me, I'm new to Android.
anyone?
was rooting only partially done? any ideas?
hello, I have been trying to root my motorola backflip 1.5 for over a week now with no luck. I have been trying the rageagainstthecage-arm5.bin method and it seems to run fine but when I run su in the terminal emulator it gives me the following error:
bionic/linker/linker/.c:1581| ERROR: 7265 could noot load ´libbinder.so`
bionic/linker/linker/.c:1641| ERROR: failed to link su
bionic/linker/linker/.c:1741| ERROR: cannot link executable `su`
I am trying to root my phone so I ca update it to 2.3 but I can't complete the rooting process, can someone please help me!
try superoneclick
I tried superoneclick, same results!
god damn it....... search xda for rooting methids then if you keep getting su errors then you might not be able to root the phone
jose_am said:
hello, I have been trying to root my motorola backflip 1.5 for over a week now with no luck. I have been trying the rageagainstthecage-arm5.bin method and it seems to run fine but when I run su in the terminal emulator it gives me the following error:
bionic/linker/linker/.c:1581| ERROR: 7265 could noot load ´libbinder.so`
bionic/linker/linker/.c:1641| ERROR: failed to link su
bionic/linker/linker/.c:1741| ERROR: cannot link executable `su`
I am trying to root my phone so I ca update it to 2.3 but I can't complete the rooting process, can someone please help me!
Click to expand...
Click to collapse
Well bionic is the android version of the libc programming library and libbinder.so is a library of some kind, which it can not load, either because it is not there, or not where it is looking for it, or not accessible due to permissions or an incompatible library for your system.
No idea how to fix it though, but thought i would shed some insight.
Hello there well I'm using superoneclick and I found that its not putting the su exe in the right place it puts it in (/system/xbin/) and where it should go in /system/bin where all the commonds are.?
Are you sure that you're rooting it correctly?
Please make use of the instructions below .
Download Super One Click, make sure you have the Android debugger (SDK developer kit) running, expand the Super One Click zip file and click the SuperOneClick icon to run it. When SuperOneClick launches, you’ll see several large buttons at the top of the screen. Make sure your phone is connected to the computer via USB and that the debugger can “see” it (activity will start logging). Make sure your SD card is not mounted, and go ahead and click “Root” in SuperOneClick.
You’ll see the scrolling activity as SuperOneClick does it’s job, with “OK” appearing after each task. You may see warnings, but so long as it doesn’t “hang” on waiting for device, things should keep scrolling until it finally returns the “Success!” message. If you're stuck , go to your phone and enable usb debug and disable again . Until you get past it , that's how i got it to work for my phone.
At this point, check out the installed apps on your phone and you should see a “Superuser” icon that looks like a Droid skull and crossbones. If you see it, you’re rooted. If you don’t see it, reboot the Droid. In fact, I’d suggest rebooting even if you do see it, as I had some issues getting rooted apps to work until I actually rebooted my own device.
Hello, I´ve been testing Lightning Zap for my nitro HD with "LG-P930-V20c" rooted version with SManager and I get this error with some of them : ""reloc_library[1285]: XXXX cannot locate '__aeabi_llsl' , I have been having this same error on a Terminal Emulator with comands like whoami or even when trying "busybox ls" which I already have installed on my phone, I searched on this page but I couldnt find anything that may help me, I am a noob in android, does somebody knows how to work this out?, Thanks in advance for any answer.
Waiting for VM "MEmu_15" to power on...
MEmuManage.exe: error: The virtual machine 'MEmu_15' has terminated unexpectedly during startup with exit code 1 (0x1)
MEmuManage.exe: error: Details: code E_FAIL (0x80004005), component Machine, interface IMachine.
Starting up Memu console.exe and clicking play on any of my VM's MEmu_1 to MEmu_15 i get this error. i reinstalled the current version yesterday and it loaded perfectly. i really dont want to re import all my image files again, is there a way to fix this error?
Admin move this Topic if incorrectly placed idk where to post but i figured In the Assist section.
still no replies huh. well ive decided to uninstall MEmu's current version and im reverting back to the old one.
im tired of all this ****ty error bull****, no other emulators require additional options to be enabled and drivers are always getting blocked "unassigned driver" plus the error i mentioned above.
think i might just give up completely and come back when you give a **** (fix your bull**** errors)