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

[Q] Editing file in /etc/wifi.., how?

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?

Need help using adb to root thunderbolt

Maybe Im an idiot but Im trying to follow http://forum.xda-developers.com/showthread.php?t=996616 to root my thunderbolt and have no idea what im doing with ADB.
I tried reading that ADB workshop but Im still lost. Adb wont seem to let me do anything. Even a simple command to list the connected devices results in a permission denied error. Is there a step by step instruction or video for rooting the thunderbolt that actually includes the EXACT commands needed to do this successfully rather than assuming that people are familiar with the various commands and quirks of ADB?
I've manually and one click rooted other phones before but the most complex it got was mounting my sd card in windows, copying over some files and then rebooting the phone into recovery mode.
Why is this phone's rooting process so over the top complex?

[Q] rooting inspire questions

Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!

Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!

He said the adb drivers won't connect

Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software

We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?

trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol

did u ever find out y adb wont connect im having d same problem

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..

Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer

Need help with samsung skyrocket root!!

So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.

is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.

shansmi said:
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
Click to expand...
Click to collapse
I have not changed anything since the first success of my Skyrocket root. It's weird that it would root the first Skyrocket but not the second one.

I used this one.
http://androidadvices.com/root-samsung-galaxy-s2-sky-rocket-4g-sgh-i727-tutorial/

Solution for "Files not found" and "permission" when trying to run ZergRush
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!

trying to root
ashque01 said:
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
Click to expand...
Click to collapse
I still get errors "system cannot find the path specified" and it doesn't work.
ashque01 you put "D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat"
I didn't get that to work until I switch the > to a \ the arrow instead of a backslash makes a difference, beg pardon but I don't know dos very well and I did use the arrow with no success, lol...
Once in the command prompt (you get there by typing exactly that "command prompt" in search bar, after clicking the start button in windows 7) Right click on command prompt to run as administrator.
I put D:\DooMLoRD_v3_ROOT-zergRush-busybox-su\runme.bat because that's where I used 7zip to extract it to, in the root of hard drive partition. It ran but with errors and announced done! press any key to continue.
I tried it again by creating a subfolder on the D: partition named android like you did, tried it again, same thing,
Still hoping to get a superuser icon so I can download my root explorer app from the market.

YAY!
I got root.
I told all of about it in that thread I started titled s#%rocket. I did admire what Entrophy remarked about it's hardware being disagreeable, but that was in the i777 thread. I had no business there (mod moved my thread, thank you) as my handset is i727.
I coulda swore that's what about phone said before I started but sure enough when you pull the battery it says i727 right there, can't argue with that, I was just being "elevator up, but door not open"
Beg pardon

androiduser1 said:
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
Click to expand...
Click to collapse
use 2.3 not 2.2
Sent from my SAMSUNG-SGH-I727 using xda premium