Database Develop

Problems with ADB install..

Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.

Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .

Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)

Glad I could help .

OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???

Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .

[HOW-TO] Setting up ADB - The Tutorial For WINDOWS USERS...

SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps

adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..

Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?

cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.

how do i install an apk file right to my phone using the "cmd"

jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk

n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything

Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.

[Q] Please help me use adb to root JI6 on a mac!!

I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!

Ok, so if you can see your phone through adb, then you are definitely on the right track. Unfortunately, I'm not really familiar with OS X anymore so I'm not quite sure how to do it. Just sit tight for now until someone who does use a Mac, or has more of a clue then I do can help you out.
But seriously, don't pull your hair out. It won't stay on your head forever ya know...

Edit: oops, just saw this is JI6 (Froyo) not JF6, so I can't help you, but here is a general overview:
from terminal inside Android sdk main directory:
tools/adb devices -> list all devices connected that ADB can see
tools/adb shell -> gets a normal user shell on your phone
tools/adb reboot recovery -> reboots into recovery mode, suitable for update.zip root method
--------------------------------
Place the root update.zip on internal sdcard.
from terminal inside Android sdk directory:
tools/adb reboot recovery
Select the update software option, and you will be done.

laxwillsch said:
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Click to expand...
Click to collapse
Start simple:
If you open a terminal on the mac, and go to your android SDK tools folder; what happens when you type ADB shell?
Or if you type any of the ADB push commands?
You need to give more detail around what you are seeing for us to help you.

Ok so if I am in terminal and i type in my /android-sdk-mac_x86/tools nothing happens and it just says /android-sdk-mac_x86/tools is a directory. But if I type the same but with /tools/abd it opens the abd command lines, like how to write code. Then when I try to "adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin"
it says "-bash: adb: command not found"
however when I type laxwillsch$ /android-sdk-mac_x86/tools/adb shell
it does give me the drop down $
but when I then try to write the next line of code "chmod 0755 rageagainstthecage-arm5.bin"
it says "chmod: rageagainstthecage-arm5.bin: No such file or directory"
I am stumped I am beginning to think i need to buy a pc as I am very interested in android development and want to learn more, but it seems all the tutorials are run assuming you are on a PC
EDIT** I have downloaded the android SDK started pack, and the 2.2 root pack and they are all in my /android-sdk-mac_x86/tools folder that is directly on my Macintosh HD for simplicity

Do you know how to change directories (cd command)?
The problem is that you are trying to work in one directory, but all your tools are in another.
So change directories to the tools directory:
cd /android-sdk-mac_x86/tools/
now run your adb commands - you may have to type ./adb to tell your mac to look in the current directory for the adb command (that is what ./ means "start here")
Also, try to understand what is happening so you can more easily troubleshoot: chmod is a command to change permissions, and you are running it on the phone. If you can't push the file to the phone, then you can change it's permisssions. I guess you never got rageagainstthecage on the phone, so there is no way to chmod it.
If you can't do this on a mac, a PC is not easier. I use both, and like both, but you need to learn basic commands first - they apply to the mac terminal and the windows cmd prompt.
Getting root means moving in and out of the phone - adb shell - puts you in a terminal on the phone. So you really need to understand cd (change directory); pwd (present working directory - shows you where you are); cp (copy); and know your current path - what the ./ does.
I hope this helps, not trying to sound condescending - maybe practice a linux terminal tutorial would help

Thanks so much, I am at school right now and cant test out all that but you are really helping me understand all this! I will post tonight and let you know how it goes. again thank you

ok so i dont have my usb cable with me but I was playing around with the commands that you suggested and ureka! i finally got to a point where it says "h70-33-65-19:tools laxwillsch$" thats a first! and when i type pwd it shows "/android-sdk-mac_x86/tools" so that means I am working out of the right directory right? and from here I enable usb debugging connect my phone then just copy and paste the codes from the thread correct?

yes, it sounds like you are on the right track. But take it nice and slow when you follow the steps. It is very important that the commands are entered exactly as you see them.
Also, one step tells you to wait for something to run and kick you out of ADB - wait just like it says - takes about 45 seconds but feels like forever.
If you are in the tools directory - just by typing "adb" no quotes will give you whole page of adb commands - if you get a "command not found", then you need to add the ./ and make it ./adb
Hope this helps and again, read the commands step by step a couple times first so you understand what is happening.
In a nutsell, you push the rage file;
change its permissions, run it;
get kicked out of ADB and then open a new ADB shell;
you are now root;
remount the system partition to give you write access when it reboots;
reboot;
push over some files;
change permissions on files you pushed;
reboot;
Some things to know - SU is a command for gaining root access; when you use SU your prompt changes (in adb shell) from $ to #
If you are succesful you should see the SuperUser app listed in your apps.

Done and Done just rooted successfully couldnt have done it without you! thanks so much

ADB Help

I thought I had this figured out and adb and fastboot was working after I reinstalled usb driver from web--but
I can not type adb devices and have phone seen. I did reinstall driver per web directions and Device Mgr says it is up to date.
Attch 3 pics
1. is my comp Device Mgr screen. The opened Android Phone is where I updated from and says up to date. The opened Portable Devices shows G:\. I thought it use to show the device by name.
View attachment 807632
2. Is blackrose installer seeming to work but didn't proceed any further on it
View attachment 807633
3. Is Command Window
View attachment 807635
Any ideas what I am doing wrong. When I open Command Window I cd/
then type adb devices. Also tried it with sdk path selected. Debugging is on.
Thanks
Ken

I've never worked on my Nexus from Windows. But is it because it is mounted as a drive? As in, you mounted the SD Card for access in Windows when you connected your Nexus?

Thanks
but i didn't mount anything. just plugged in. phone says usb connected and and select to copy files. so, i didn't mount. in command window, as mentioned, i just opened window and typed cd/ then typed adb devices
sorry if i misunderstood your comment
what about the adb server outdated comment in command window?

I just did a fresh adb install the other day and allowed SDK manager to update all drivers and tools. I installed the SDK zip to the root of my C:\Drive
Note: ADB moved from \tools to \platform-tools\
After plugging my phone in and turning on USB debugging, I type:
CD\
CD androidSDK\platform-tools\
ADB Devices
Then you should see a serial number for your phone.

i just got to that point while you were posting
too bad my blackrose and hypersense files are gone
however, i have no platform-tools in sdk. only platforms with android-2 thru android-8
and mine is platforms not platform per note
trying to install it too platforms and get path right. don't see how to install from SDK and AVD
i have nothing listed in avd manager

can't get sdk r15 to install with platforms-tools
can't fetch repository and can't get to screen where you can change https to http to allow fetching of repository

well after unsuccessfully trying to update sdk and not getting the repository I restored the android folder from full image bu I made with Acronis
still saw in tools that adb had been moved to platforms-tools, which I did not have
I found adb under the temp folder and re exe it and it moved back to tools and after adb start-server was able to get adb devices working
not sure how it got moved

Device Offline Error on HTC One

Okay, I am trying to run the firewater script in order to get S-OFF. But I have run into the "device offline" error when I try to connect my Mac to my HTC One. I understand from reading why I am getting the error, and that it is due to a new "feature" of Android 4.2.2+ which gives us secure usb debugging.
Here is the rub, though: When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’.
But that is not what is happening! Whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization. The trick, according to this thread [http://forum.xda-developers.com/member.php?u=4159439] would seem to be to remove the
adb key from the device, so as to trigger the confirmation window to allow USB debugging. But I can not find the location of this file on my HTC One, so I have no way to remove it.
Please tell me where this file is located if you know it. I have ES File Explorer installed on my rooted HTC One, Dev. Edition, running Android 4.4.2. but that path nets me an empty folder.
Thank you for any and all assistance that you provide.
SOLUTION FOUND! - See my reply below.

Okay, typed into terminal:
cd Android/HTCOneRoot
./adb-mac version (This command gives the version of ADB that the Mac is using.)
Android Debug Bridge version 1.0.29 (Terminal returns this answer; ADB needs to be at least version 10.3.1 to properly work and fix the "device offline" error.)
Here are the steps I then followed to fix problem:
1. I unplugged my HTC One from the computer.
2. Downloaded and installed Android Studio from the Android Developers’ site into my Applications folder
3 Updated my Platform Tools, as follows:
Control-clicked on the Android Studio Application and selected “Show Package Contents” from the pulldown menu.
Followed this path to the platform tools: Android Studio/sdk folder/platform-tools folder/adb & fastboot
Option copied both adb and fastboot from platform tools to my user directory ~/Android/HTCOneRoot.
Closed Android Studio
4. Restarted the computer.
5. Launched Terminal and typed cd Android/HTCOneRoot( my user directory where my adb and fastboot are stored)
6. Typed into my terminal the command, “./adb version”
Following this command prompt, Terminal responded with “Android Debug Bridge version 1.0..3.1. (Yes!!)
7. Typed into Terminal, ./adb devices
My device did not show up right away!
8. So, I unplugged my device. Shut down my Mac and restarted it.
9. Relaunched Terminal and typed cd Android/HTCOneRoot
10. Typed ./adb kill-server
11. Then typed, .adb start-server
Terminal responded with: daemon not running. starting it now on port 5037 *
daemon started successfully *
12. Plugged in device again, and the device dialog about RSA appeared. (Whew!)
13. Clicked “OK” on the dialogue box.
14. Now typed ./adb devices and my device's serial number shows up, followed by the word "device" (not "device offline")
14 All done! No more device offline errors.

Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3

RickCov said:
Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3
Click to expand...
Click to collapse
mini-sdk-1.0.31-windows.rar
download and extract to a folder of your choice, that's all.

let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.

I was having the exact issue described by OP and simply by getting the newest version of ADB and unchecking and rechecking debugging I got the authorization. Thanks all who offered suggested and posted links to files.

and this helped as well
metropical said:
let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Click to expand...
Click to collapse
http://goo.gl/WyyzhX