Database Develop

[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] Help with ADB

So basically i have been trying to get into download mode for the past few hours and none of the manual button pressing options have worked for me. I recently just upgraded to the official froyo update (KB1) through kies just to check it out and I now cannot get back to download mode so i can flash back stock 2.1. I have sdk installed and am attempting to use adb commands but cannot get it to work I go into command prompt with my phone plugged in (with usb debugging on) and do these steps:
1. Opened command prompt on PC
2. Type CD\ to start at C root directory
3. from there I typed in CD \sdk\tools\
4. I then type adb reboot download and my command prompt shoots back at me adb is not recognized as an internal or external command,operable program or batch file
Any help guys? This is really frustrating

newest releases of the sdk moved adb from /tools to /platform-tools
if you issue a 'dir' command while in the \tools folder you will see adb is not in there. move to the platform-tools folder

Just figure it out. Thanks so much!

[Q] ADB & Win7 x64 nightmare, tried everything

for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point

oceanisbleu said:
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
Click to expand...
Click to collapse
Double check your path...
"Now type cd\AndroidSDK\tools\"
My path is c:\android-sdk-windows\tools\

I've renamed the file to AndroidSDK & placed it directly in C:/ so for me it's C:/ AndroidSDK/tools/
doesn't work...
-I plug the phone in and it's recognized as "Android ADB Interface" in device manager
-I open easy tether on the phone then right click on the pc & click connect then it says connection established via Android ADB.....
-I open CMD
-I type cd\
-then cd\AndroidSDK\tools\
-then adb devices & this is where I want to break everything because I can never get past this part and all I see is 'adb' is not recognized as an internal or external command.......
I hate this phone lol & wish I had the money to get the evo so I can put this thing in the trash, I just want to setup firerat's and that's the main reason why I want to establish ADB, is there any way it can be done without ADB????
thanks for trying to help, I hope someone can still figure this out for me

If you downloaded the newest SDK, then the problem might be that you are looking for adb in the wrong directory. It is no longer located in \tools. It was moved to the \platform-tools directory
Sent from my HERO CDMA using xda premium

In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.

dastin1015 said:
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
I have just added this exact directory to the end of my PATH
;C:\AndroidSDK\platform-tools\
rebooted, opened cmd, typed adb devices and still I get ADB is not a recognized command.
I went to HTC's site & downloaded the latest hero sync software (new version just came out 2 days ago) when I plugged my phone in it re-installed the drivers, tried it again and nothing!!
I did notice that after the HTC Sync installation in device manager the phone is no longer Android ADB Device, now it says MY HTC, did Sync ruin my ADB drivers?

Ok. So were you at with this???
Shoot me a pm if you still need assistance.
Edit: From reading your post I think your not changing the directory first.
So open up the cmd window. And type cd\ "then hit enter"
Thenn type.
cd\AndroidSDK\platform-tools\
And hit enter.
Then type. "adb devices" without the quotes. And see if that will show your serial number.
If that yeilds no results then try
cd\android\SDK\tools\
And hit enter.
Then type "adb devices" without the quotes. And hit enter and see if that will return your serial number.
Locked & Loaded
" Shooter on Deck"

Thanks guys for all the help you have provided, I have finally figured it out using this guide;
http://forum.xda-developers.com/showthread.php?t=532719
slightly different than the first guide I followed, instead of editing the PATH a new Environment Variable was created also a slightly different CMD code to get to ADB;
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
I hope this helps anyone else who might have the same issue.

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

Stupid Idiot's Guide to getting rooted Moto X on 4.4 (for dummies)(also zombies)

Okay here is my guide for anyone daunted by the fragmented guides scattered all over the place and who doesn't want to piece stuff together. I was pretty apprehensive about attempting this so I figured other people are too, so hopefully this helps someone. It's really redundant so if your intelligence is easily insulted, avoid.
It worked for me on a device with att 4.4 OTA installed, and i THINK it should work for everything that has 4.2.2 and 4.4 firmware available on the firmware page.
What to download:
(many of these are here)
Android Development Tools (ADT) ;;; your carrier's firmware for 4.2.2 ;;; Motorola Device Manager (for drivers) ;;; Cydia Impactor ;;; puttytel (just puttytel.exe is all you need) ;;; RockMyMoto ;;; RSDLite ; MotoWPNoMo ;;; SlapMyMoto
Extras: root checker apk ;;; latest Xposed Framework
<wallOfText>
Code:
extract ADT, Impactor, MotoWPNoMo, RockMyMoto, SlapMyMoto, and the firmware
Install RSDLite. Puttytel should just be an exe already.
Open the adt directory and in the search bar type adb.exe
right click the file and open folder location.
this is a very important directory. it will be reffered to as the adb.exe directory/folder
copy all files from RockMyMoto extraction folder and put them in this directory
run moto device manager, follow instructions for it to get your drivers. you might have to connect the phone via usb.
open the extracted firmware and modify the xml file and remove the
disable any isolation mode on your router (IDk what this is but mine was turned off, if you can't get it to work and can't find your router setting you might be SOL.)
anytime the direction says "send" it means in the command line window
extract directory for ADT
search for adb.exe
open file location of adb.exe
copy location path
type win+r, cmd, enter
send "cd " then right click paste to paste the directory path
you are now executing commands from that directory
send " adb shell getprop dhcp.wlan0.ipaddress "
write down that ip address
factory reset phone
get to settings menu
enable usb debugging
connect to computer
send "adb devices"
look at phone, click always accept this connection or whatever it says...
send "adb devices"
if it shows some numbers and letters, you are good
send "adb reboot bootloader"
Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
open RSDLite
select the edited 4.2.2 xml file as file to flash.
click start to flash the 4.2.2 firmware
on your now jellybean phone open settings
enable usb debugging.
restart the phone. it took me a while to figure this out. it just wouldn't go on...
send "adb devices" to check if it is connected
send "adb push su /sdcard/"
send "adb push RockMyMoto.jar /sdcard/"
open cydia impactor exe
click drop down menu, select "# start telnetd as system on port 2222"
click start
check phone
follow prompts/click accept.
check cydia window on PC
wait for it to get through all the different messages until it is back at the initial screen.
This basically installs a temporary telnet receiver on your phone, whatever the hell that is...
now open up puttytel.exe
type your devices ip address and change port to 2222
click open
this brings up a command line screen but with green font.
wait for the $ sign, then send "dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto" on the green font screen
(in the green screen, you can paste by right clicking)
solve the equation LOL
open the cmd.exe window that you didn't have closed
send "adb reboot"
close cydia and puttytel
open cydia impactor and start the telnet session again on port 2222
check phone if the process seems to stick.
open another puttytel session
send "dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto"
wait for phone to reboot
close cydia and puttytel
open the cydia impactor and restart the session on port 2222
open the telnet session to your devices ip address and port 2222
send the exploit again.
your phone should have rooted 4.2.2 now!
in folder motowpnomo, open wpbegone.exe as admin
accept risks...
send monoies to [email protected] ; support people instead of corporations.
follow the instructions about flashing to reflash the xml file
enable usb debugging, cmd prompt at adb.exe directory, adb reboot bootloader, open rsdlite, select the modded xml file, start
wait for it to reboot
send "adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar"
open cydia impactor
open telnetd as system on port 2222
check phone and accept or deny until impactor stops waiting for completion
open puttytel
connect your phone to your router wifi, the ip address should be the same as earlier. if you want to check, send " adb shell getprop dhcp.wlan0.ipaddress "
put ip address and port 2222 again
click open
with the telnetd green command line screen send "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto"
close the green screen
on the cmd.exe screen send "adb reboot"
repeat the Impactor, telnet, "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto" again
reboot the device
go to settings, about phone, updates, take update if 4.4, if it only offers 4.4.2, you will have to ask someone what to do...
(I would imagine you can download 4.4 from the place you got your 4.2.2 firmware download then flash using RSDLite, but I never had to cross that bridge personally)
(the instructions were not very clear here. I was really winging it here but it worked for me)
On the PC, copy all files from SlapMyMoto extraction and place them in adb.exe folder, overwriting the old files.
in cmd.exe, send the following one at a time:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then wait a few minutes, toggle bluetooth, reboot the device.
</wallOfText>
You should now be rooted on 4.4!
I tried to write this as I was doing it but I may have accidentally omitted something.
Thanks to techsavvy2 ;;; beaups ;;; JCase ;;; CartlandSmith (and anyone else i didn't remember to thank), for helping the community to hack this thing! :highfive:

a10fjet said:
Okay here is my guide...........
Click to expand...
Click to collapse
Uhmm this has been covered many times.
Thanks for sharing
But I am closing this thread
THREAD CLOSED