Related
I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU CAUSE!
So you are stumbling around XDA and you really want some kind of app or something, but you think you cant because you have a Mac, well I am here to tell you wrong.
The biggest and most used mistake for mac users when trying to use ADB is this:
HTML:
Inas-iMac:~ Hans$ /AndroidSDk/tools
-bash: /AndroidSDk/tools: is a directory
Inas-iMac:~ Hans$
Well this is how you do it!
Watch this!
http://www.youtube.com/watch?v=GLAMG4xU_lE
To make your phone go into debug mode go to settings/applications/development and check debug
DO NOT MOUNT PHONE! Just let it be
I did not go to deep into the process because this is made for complete beginners!
Why not follow the official SDK install instructions and add the path to bash_profile..
developer.android.com/sdk/installing.html#Installing
In my opinion that's not too hard for a newbie.. (i managed to do that) And after doing that you don't need to change directories with cd command, you can just type adb whatevercommand from your home dir which is the default location when you open the terminal.
Drag and drop is a little a fail.... one can add "alias" (linux can do it, probably mac too)
Little How-to:
Code:
$ nano ./bashrc
add and adapt the following line to bashrc:
Code:
alias adb="/home/carbonyle/android-sdk-linux_86/tools/adb"
now you just have to type "adb" from a terminal emulator to run it, eg:
Code:
$ adb shell
# reboot recovery
or
Code:
adb install ./Download/myFavortiteApp.apk
and so on...
ps: we don't need to "adb remount" at worst we can just "adb kill-server" then "adb start-server" if the device is not accessible
I have the Android ADK installed and I have adb. I don't seem to have the privledges to use it though. If I try and use it normally I get
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
I can only get it to work if I start adb as the admin. Then I can use it as a normal user.
Also, I don't seem to have fastboot. Where do I get it?
On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.
beartard said:
On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.
Click to expand...
Click to collapse
Ok I guess it's just easier to start it as root. Fastboot on the other hand wont work. After I use the command
Code:
adb reboot bootloader
my phone reboots into recovery and has FASTBOOT USB on the screen. When I type
Code:
fastboot devices
it just goes to the command line again and doesn't show anything. When I try and type $ fastboot reboot I get
Code:
< waiting for device >
Any ideas why it's not working?
I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.
beartard said:
I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.
Click to expand...
Click to collapse
Ok, now I feel really dumb. I guess I didn't run fastboot as root before. I could have sworen I did. Well now it seems to all be working, as long as I am root. I wish I could do it with out having to be root.
Thanks beartard
No problem. In case you're interested in how to do it The Right Way™ here's a post I found on the Google support forums for Android. The author had a Motorola CLIQ. The vendor id for the Slide is 0bb4.
I found this info to be helpful, although there was not much explanation behind it, and in the end things still did not work for me. after a number of hours of debugging (which was kind of fun!) i finally got things working, and wanted to document it here in case others have the same issues. also documented is *how to debug* your stuff, which may be as valuable as the fix!
disclaimer:
i still dont really understand udev very well, so if someone who does can clarify my observations, that would be cool.
my environment:
ubuntu 10.04, device is a motorola cliq.
adb version 1.0.26
eclipse version 3.5.2 (galileo)
the problem:
persistent issues with adb devices returning:
List of devices attached
???????????? no permissions
rat holes i went down:
a) first, be sure that when you write your android-specific rules in /etc/udev/rules.d that you ensure that you name the file with a name that ends in .rules, or else the udev daemon wont read it.
b) Ubuntu 10.04 uses a new version of udev, so some of the documentation you find on the web is out of date.
c) The phone looks like a disk drive to the OS, which caused me some wierdness. more later.
some basics:
a) the udev infrastructure is what the OS uses to dynamically map, present, and control USB devices. you will need to tell udev what to do with your android phone when the phone is in application debug mode (that is why you need the /etc/udev/rules.d/50-android.rules file.
b) the adb (android debug bridge) is the daemon (using network sockets) that allows the IDE to talk to the device. when you run commands like 'adb devices' the command looks for a running daemon, and if one is not running it starts one and then communicates with it.
c) the "no permissions" error message indicates that the adb daemon cannot get the right permissions to access the device as the user that it is running as. normally the IDE starts the daemon as the user you are logged in as. unless the phone device appears in the udev infrastructure with the correct permissions to be accessed as the user you are logged in as, it wont work.
steps:
1) plug your phone into the usb bus on your system. does not need to be in application debug mode yet...
2) verify that you can see the phone by using 'lsusb', e.g.:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 044: ID 22b8:2d66 Motorola PCS
Bus 002 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 002 Device 003: ID 10d5:0001 Uni Class Technology Co., Ltd
...
the line "ID 22b8:2d66 Motorola PCS" is my phone. the rest is other stuff on the usb busses. ignore it.
3) the 4 digit value 22b8 is the Vendor ID of my phone. yours may be different. whatever it is, this is the value you need to use in your udev rule.
4) the Bus number and Device number are useful. you can see what permissions your device is getting at any time by doing
$ ls -l /dev/bus/usb/<busnumber> where <busnumber> is the Bus number above (002 in this case).
the permissions of the device will be the permissions of the file numbered with the Device number above. in my case it was device 044, so the full file path is /dev/bus/usb/002/044
! note - this device number will change when you plug/unplug or enable/disable debug on your device.
5) you can now get *alot* of info on this device now by using 'udevadm info', but you need to use the bus and device info above (remember yours may be different and change). you can use either udev info command --query=all or --attribute-walk, e.g.:
$ udevadm info --query=all --name=/dev/bus/usb/002/044
or
$ udevadm info --attribute-walk --name=/dev/bus/usb/002/044
note that the attribute-walk walks up the bus. the first entry printed should be the lowest device on the chain, which is your phone. in my case some of the lines looked like:
looking at device '/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2.4':
KERNEL=="2-2.4"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{configuration}=="Motorola Config 42"
...
ATTR{idVendor}=="22b8"
...
ATTR{busnum}=="2"
ATTR{devnum}=="44"
ATTR{version}==" 2.00"
ATTR{maxchild}=="0"
ATTR{quirks}=="0x0"
ATTR{authorized}=="1"
ATTR{manufacturer}=="Motorola "
ATTR{product}=="MB200"
ATTR{serial}=="<serialnumber>"
...
where the <serialnumber> is the serial number of my phone, which will show up in the adb devices list when this all works. recognize the items that you will need for the .rules file are there.
6) now, lets write the .rules file. you have two choices. either get the permissions of the phone as it shows up changed to 0666 (rw for all users, including the world) or change the ownership to be your user. i prefer the latter. seems cleaner to me, so i will use this approach for the rest of the info.
7) find out who you are. use the id command, e.g.:
$ id
uid=1000(<your username>) gid=1000(<your group name>) groups=...
where the uid and gid for you are indicated. for now lets use both as 'juser' for the example.
8) now lets create the .rules file. the number at the beginning of the file name is the order that it will be loaded by the udev infrastructure. it may be important. all the examples showed a number of 50, but there are a bunch of things being loaded in /lib/udev/rules.d/ as well. i prefer to make my file name 99-android.rules to force it to load very late in the process. this keeps other later things from clobbering my permissions as they load.
for example, if you use the ATTR{idVendor} attribute in .rules as oppose to SYSFS{idVendor}, then when other later rules load they could over write the permissions you set in your .rules file.
9) you have to use root or sudo to create the file in /etc/udev/rules.d. create /etc/udev/rules.d/99-android.rules and put in a line like:
SUBSYSTEM=="usb", SYSFS{idVendor}=="<Vendor ID>", OWNER="<your username>" GROUP="<your group name>"
and save it.
the SYSFS{idVendor} value needs to match your device id, and the OWNER and GROUP are from step 7 above.
for this example lets use
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", OWNER="juser" GROUP="juser"
if you just want to set the permissions use:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
10) now, when you connect the device (try the application debug mode) you should be able to see that the device appears with the correct user permissions. e.g.(using this example's bus, device, and uid/gid values):
$ ls -l /dev/bus/usb/002
crw-rw-r-- 1 root root 189, 128 2010-10-09 20:02 001
...
crw-rw-r-- 1 root root 189, 131 2010-10-09 20:02 004
crw-rw-r-- 1 juser juser 189, 173 2010-10-10 11:29 044
this is very good, 'cause now adb running as you will be able to read and write the device.
11) if you did not get here, then you have udev issues. dont bother beating on adb, the problem is in udev. your best bet is to go into /etc/udev and edit udev.conf, to change the line
udev_log="err" to udev_log="debug" to see what is going on. then you can follow what udev is doing by opening a terminal window and following /var/log/syslog with:
# tail -f /var/log/syslog
you may need to restart udev, which you can do by doing:
$ sudo /etc/init.d/udev restart
from another terminal window.
this output is very verbose, but you should look to see that your .rules file is being loaded. if not, then that is the issue to fix.
12) if all is ok, and the device has the right permissions, when you put it into application debug mode you should be able to simply start the adb server with:
$ adb devices
and see your device by serial number
List of devices attached
<serialnumber> device
13) if you have problems with adb, here are a few things to check.
a) make sure you see that adb is running, and owned by you by looking for it with ps, e.g.:
$ ps aux |grep adb
you should see a line like:
juser <pid> 0.0 0.1 28160 728 pts/4 Sl 10:18 0:01 adb fork-server server
where juser should be your user id, and <pid> is the process ID.
b) if adb is running as root, you may need to use 'sudo killall adb' to kill it off and then as your user run 'adb devices', which should start the server as you.
c) if you still have problems you can run strace on the server and it's child processes with:
$ strace -f ./tools/adb server
note that the output is very verbose, but look thru there for some kind of permissions problem. lots of 'file not founds' are ok, but as the daemon starts and tries to bind to the device, you may find a permission problem.
hope this helps. sorry to be long winded.
jerichod.
Click to expand...
Click to collapse
For those of you with Mac OSX or Linux, you can root it using this method:
Step 1. Go to Settings->More->Device and make sure “Allow Installation of Applications” is checked “ON”.
Step 2. Connect your Kindle Fire to your computer via micro-USB cable. And hit “Disconnect” to turn off the USB disk drive mode.
Step 3. Download KindleFireRootMacLinux.zip and unzip to the root directory of your hard disk such as c:\KindleFireRoot.
Download KindleFireRootMacLinux.zip
Step 4. Open up a terminal.
Step 5. Browse to the KindleFireRootMacLinux directory by typing:
cd Downloads/KindleFireRootLinux
Step 6. Type:
mkdir ~/.android
cp adb_usb.ini ~/.android/.
*Note – You might have to add “sudo” for Ubuntu
Step 7. Type:
For Mac:
./adb-mac kill-server
./adb-mac devices
For Linux:
./adb-linux kill-server
./adb-linux devices
If you get a bunch of numbers and letters, that means you are good to go.
Step 8. Type:
For Mac:
sh runmemac.sh
For Linux:
sh runmelinux.sh
Step 9. Your Kindle Fire should do its rooting and reboot.
You can verify you have SuperUser app by going to Settings->More->Applications->All Applications.
Yay!
I do not have anything show up when I do the devices command. I am running a mac.
soundslikemitch said:
I do not have anything show up when I do the devices command. I am running a mac.
Click to expand...
Click to collapse
What do you get?
Did you do this step?
cp adb_usb.ini ~.android/.
soundslikemitch
I had this issue as well and zedomax is correct, you have to make sure that this file resides in your own $HOME/.android folder. While cp adb_usb.ini ~.android/. works you may want to try 'cp adb_usb.ini $HOME/.android` as well. I also had the issue where my fire wasn't being shown while executing ./adb devices which required me to reboot and then it seemed to start getting picked up without issue.
Hope this helps and thanks zedomax for the tutorial
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
SifJar said:
There's a problem with the original instructions: adb needs to be restarted after editing adb_usb.ini. You need to run
./adb-mac kill-server
or
./adb-linux kill-server
to make it work without rebooting your computer.
Click to expand...
Click to collapse
thanks forgot to put that in the instructions, fixed!
Moving it to my home folder in .android worked!
But apparently this broke the video store.
No-go for me. Tried all above instructions and nothing shows up in devices. The thing that had me thrown off a bit is the instructions don't exactly match.
I want to follow exactly so is step 6 necessary since the zip file already has the android directory with the file already in it?
soundslikemitch said:
Moving it to my home folder in .android worked!
But apparently this broke the video store.
Click to expand...
Click to collapse
I figured out how to fix the video store. Amazon seems to be looking for the existence of the file /system/bin/su so just rename it if you want to watch videos.
i.e.
Code:
mv /system/bin/su /system/bin/su2
reboot
I am still able to type "su2" and get root and I am able to play videos.
Another solution is installed voodoo OTA rootkeeper (free) from the market place. Once installed you can temporarily remove root, then restart the amazon video service and voila. Once the service is started you can re-enable root for the duration that the service is active (not rebooted) you will have root and amazon video.
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
None of these instructions have worked for me, I have spent countless hours trying to do this via Windows (the windows tutorial) and on mac. My device never shows up and it does not root. I have tried restarting my fire, unplugging and plugging back in, etc. I am running Lion 10.7.1. Please help, if possible, pm me so we can chat via Google Chat or something.
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
The OSX instructions did not work for me either. I ended up busting out my Windows Laptop and followed the guide and programs from rootkindlefire.com
masterc1111 said:
Also had the same problem (with Lion 1.7.2 ): Waiting for device...
I used this commands to get it working: (first you have to follow instructions from zedomax step 1-5)
cd downloads/
cd KindleFireRootMacLinux/
mkdir ~/.android
cp adb_usb.ini ~/.android
./adb-mac kill-server
./adb-mac devices
after device is shows up enter:
sh runmemac.sh
After this the KF will reboot and get rooted!
Click to expand...
Click to collapse
Doesnt work, it still does not show up under devices and the command runemac.sh just says it is waiting for the device.
I don't know why this may work, but try adding a trailing slash to the cp command; cp adb_usb.ini ~/.android/
Also, this works great under (Sabayon) Linux. Very great little script you have here. Only way it could be easier would be if it did the copying and all that on its own.
The problem I had was that the terminal kept saying "waiting for device." I originally downloaded the "KindleFireRootMacLinux" folder to my desktop. I substituted "desktop" for "download" in the prompts. I tried to root it at least 10 times with no success. The terminal never recognized my kindle. Then I moved the "KindleFireRootMacLinux" folder to the "Downloads" folder and it worked the first time. I'm assuming that some of the code is looking in the downloads folder. Try to move it there and see if that works.
bsoplinger said:
you have "mkdir ~.android"
The more common syntax, and what worked for me as your syntax didn't, is:
mkdir ~/.android
This is under Mac OS X 10.6.8
Click to expand...
Click to collapse
Dude! Thanks so much for pointing out the syntax issue. I tried to do this for nearly an hour... couldn't get it to see my device. But after adding the "/" as you so cleverly suggested, voila. Success!
Thanks a million!
root ran ok
should su show up in apps? Nevermind found it
I searched for the voodoo file and it doesn't show up in the app store. If its on the Android Market then I guess you'd have to download and install that first right?
EDIT: which is explained here - how to get market on fire
http://forum.xda-developers.com/showthread.php?t=1349902
my GT-N5100 got stock in loop boot after I install the driver of chainfire3d..
i tried to restore it factory default..erasing cache...but nothing seems to work...
I already resolved it using adb
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here: http://developer.android.com/tools/help/adb.html
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
NOTE:
if you encounter device not detected or something try this..
adb kill-server
adb start-server
>.<
Please read before installing anything.
Chain fire works for gingerbread. .. DOESN'T WORK with ice cream sandwich and jelly bean
Sent from my GT-N5100 using Tapatalk 2
actualy I didn,t download it from from google play...
that **** bastard site didn't include that warning...
sorry chainfire for not buying it from google play maybe thats my karma..haha..
but my gt-N5100 is fine now..I google for a solution and I found 1..
Edit: if chainfire manage to make it compatible with JB, I'll promise to pay for it next tym.. I wanted to play some THD...
Sent from my GT-N5100 using XDA Premium HD app
jhonuy03 said:
actualy I didn,t download it from from google play...
that **** bastard site didn't include that warning...
sorry chainfire for not buying it from google play maybe thats my karma..haha..
but my gt-N5100 is fine now..I google for a solution and I found 1..
Edit: if chainfire manage to make it compatible with JB, I'll promise to pay for it next tym.. I wanted to play some THD...
Sent from my GT-N5100 using XDA Premium HD app
Click to expand...
Click to collapse
Where did you read or see its compatible with JB
Sent from my Galaxy Nexus using XDA Premium HD app
Same issue stuck at boot logo
Could you please let me know how to solve this issue using adb
I am having same issue :crying:
Thanks in advancex
FIXED
ankitwase said:
Could you please let me know how to solve this issue using adb
I am having same issue :crying:
Thanks in advancex
Click to expand...
Click to collapse
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here: http://developer.android.com/tools/help/adb.html
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
Help
jhonuy03 said:
This is How I fixed mine..
I search several forum and and no one has the complete tutorial on how to use adb..
so I created my own step by step tutorial on how I did it just in case I need it again or someone needs it...
I hope this fixed yours as well..
Download ADB here:
1. extract the file you just download
2. put it in C: (so you can access it easily)
3. you can rename it (you can name it anything you want but we will use "Android-adb" in this tutorial)
4. open SDK Manager.exe
5. make sure that Android SDK tools, Android SDK Platform-tools, Android SDK Build-tools and Google USB Driver is installed
6. Boot your device to recovery mode (hold volume up + power) hold it until it is turned on
7. connect your device through usb to PC (it should automatically install your usb driver if not download samsung usb driver)
8. go to CMD
9.type cd c:\Android-adb\sdk\platform-tools
or
9.1 press windows + pause/break
9.2 click Advance tab
9.3 click Environment Variables
9.4 search "path" under System variable
9.5 click edit (there is a value for Variable value in default)
9.6 at the end of the default value add this ;C:\Android-adb\sdk\platform-tools
9.7 click ok
10.
type this
adb
adb shell
[email protected]:/ $ su
adb shell /system/lib/cf3d_uninstall.sh
11. your device will reboot...after that it should be fine...
Click to expand...
Click to collapse
I tried the above at last it is showing device not found
wew
ankitwase said:
I tried the above at last it is showing device not found
Click to expand...
Click to collapse
that's how exactly how I did it...
at least that what I remembered I did..
and it works for me..
is your device rooted?
Help
jhonuy03 said:
that's how exactly how I did it...
at least that what I remembered I did..
and it works for me..
is your device rooted?
Click to expand...
Click to collapse
Yes i think it is rooted
Do i need to do wipe data in recovery mode ?
I think so because I wipe my cache and reset to factory default before I used ADB...
Sent from my GT-N5100 using Tapatalk HD
just ignore step 9.1 to 9.7...
Sent from my GT-N5100 using Tapatalk HD
jhonuy03 said:
I think so because I wipe my cache and reset to factory default before I used ADB...
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Tried after wiping cache getting some problem "device not found"
Drivers are also installed correctly
r u sure u r in recovery mode and device is attach to usb?
Sent from my GT-N5100 using Tapatalk HD
Help
jhonuy03 said:
r u sure u r in recovery mode and device is attach to usb?
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Yes i m in recovery mode, and when i am typing adb devices it is showing a serial number, i checked and found if device is connected
and if i issue adb devices then it will show serial number if device is connected
did you install google usb driver in sdk manager?
Sent from my GT-N5100 using Tapatalk HD
adb
When you type adb this should be the output
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Windows\system32>
Help
jhonuy03 said:
did you install google usb driver in sdk manager?
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
Yes i have installed it
please see the attachment
oh wa8 i remembered something...
try to type in cmd
adb stop-server
adb start-server
Sent from my GT-N5100 using Tapatalk HD
Help
jhonuy03 said:
oh wa8 i remembered something...
try to type in cmd
adb stop-server
adb start-server
Sent from my GT-N5100 using Tapatalk HD
Click to expand...
Click to collapse
C:\Windows\system32>adb
'adb' is not recognized as an inte
operable program or batch file.
Firstly let me apologise If I've posted this thread in the incorrect place, I only joined XDA moments ago & I'm still struggling to navigate my way around.
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Sorry for my long-winded post! I just wanted you guys to know exactly where I'm at. I would really appreciate any helpful advice which could possibly correct this idiotic error of mine.
ADB Site load
Step by step guide:
ADB: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 - WINDOWS ONLY IF MAC PLEASE ASK
ROM:http://forum.xda-developers.com/showthread.php?t=2753450
push to sd card via adb
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check connectivity:
adb devices
(should return serial number)
4)push rom to sd card:
adb push romname.zip /sdcard/ (where romname is your actual zip file name)
5)you should then be able to simply wipe and flash the rom as you normally would.
*if you can find a nandroid for your particular build,you should be able to push that,with:
adb push nandroidname /sdcard/clockworkmod/backup/nandroidname/
(again,using cw. ill update if i can determine this to work for twrp)
be patient,the nandroid is a big file,so this will take some time.
2)install from adb sideload
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check for connectivity
adb devices
(should return serial number)
4)select "install from sideload" from the recovery menu
5)in cmd,enter:
adb sideload romname.zip (where romname is your actual rom's name)
you should see it installing on the phones screen
Hope it helps
Hi Jorandobnl, thanks for your reply.
I am using windows 7 & already have the android sdk bundle which I grabbed online when unlocking & attempting to root my device. It would of been great if I had the link you provided at the time as it was such a large download for the purpose of 4 files (fastboot, adb, adbwinapi & adbwinusbapi). Please let me know if I'm missing any other adb required files and I will download them.
So here's where im at...
I followed your instructions step 1 - 3 & my fastboot folder now contains root, fastboot, AdbWinApi.dll, AdbWinUsbApi.dll, adb & crDroid.zip
When typing 'C:\fastboot>adb devices' the cmd prompt returns with:
C:\fastboot>adb devices
List of devices attached
Even though the cmd prompt didn't list any adb devices I continued to the next step anyway & here's what was returned:
Code:
C:\fastboot>adb push crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip/sdcard/
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\fastboot>
'crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip' is the name of the ROM file which you kindly provided
When my handset is attached to my PC via USB I receive a different command prompt:
Code:
C:\fastboot>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\fastboot>
When I use the cmd code 'C:\fastboot>fastboot devices' It returns:
C:\fastboot>fastboot devices
HT244W103055 fastboot
I'm not sure whether this has any relevance but I would like to give you as much detail as possible.
To quickly summarise the steps which I took so you can check if I am doing anything wrong (which is more than likely)
Firstly I downloaded the ROM (crDroid) & placed it in my fastboot folder along with the adb files I already have. I connected my phone to my computer and started bootloader mode, then I clicked 'recovery' which loaded CWM. I proceeded to check for adb devices which unfortunately returned with nothing. I attempted 'step 4' regardless which returned the cmd code I copy and pasted for you above (for obvious reasons I could not complete step 5).
Your alternative method I have not tried yet because I neither know what nandroid nor sideload means (I must sound like im either 90, amish or stupid )
Any further help you could give me would be very much appreciated & hopefully I can find a way to fix this soon :fingers-crossed:
Once again I apologise on behalf of my technologically illiterate brain!
Update:
I checked out what sideload & nandroid are & attempted to fix my device through your 2nd method, sadly I bumped into more problems...
I located the correct nandroid build for my handset (which took way longer to find than I had hoped)
My computer still won't recognise any adb devices, I've downloaded at least 3 additional adb.exe files today to confirm that the one I downloaded with the android sdk bundle wasn't out dated. I've also killed all adb.exe processes via task manager & tried running it again in case one was interfering with the other... Still nothing
I then read in a separate thread that maybe the drivers were outdated? I couldn't check for driver updates using the traditional device manager route so I downloaded drivers online but still my PC wouldn't show any adb devices. Although I doubt out dated drivers are the problem as I updated them recently when I unlocked & attempted to root my HTC.
Again I ignored this and continued with your steps anyway, then I encountered my next problem. CWM doesn't seem to have a sideload feature... I understand its supposed to be located in the 'install zip from sdcard' section right? The options I have are as follows:
choose zip from sdcard
apply/sdcard/update.zip
toggle signature verification
toggle scripts asserts
I have checked every option on CWM & sideload is nowhere to be found! I am using CWM v5.8.1.8
Maybe the reason my PC can't find an adb device is because there is no removable disk showing when I plug in my phone using USB? When I use fastbootUSB my computer plays the normal sound to show it has recognised a device but nothing is showing in removable storage.
I've wasted my whole day trying to fix this problem. Surely there has to be a way...
have the same problem same rom.... hope answer will come out.
tried it too and nothing Works... have win 8.1