Database Users

[Q] adb Issue

hello
ummm .... seemed to be new at using adb tool ...so i am practice on my nook .... anyway ....i enable usb debugging in nook color tools .... then execute this command:
C:\Documents and Settings\XXXXXXX>cd c:\
C:\>cd Android
C:\Android>cd android-sdk
C:\Android\android-sdk>cd platform-tools
C:\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android\android-sdk\platform-tools>adb connect usb
unable to connect to usb:5555
C:\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
any suggestion
best regards

Hi:
Code:
adb connect usb
Tries to connect to a host named "usb" over TCP (WiFi) port 5555.
Code:
adb usb
Starts the adb server in USB mode.
Note: You can connect to one device over USB at the same time that you are connected to another over TCP (WiFi).
I do that all the time.
You just have to specify which device you want to talk to when using push/pull/shell.
Code:
adb -s nook:5555 shell
My adbsync also works with multiple devices, but that's a separate issue.

Renate NST said:
Hi:
Code:
adb connect usb
Tries to connect to a host named "usb" over TCP (WiFi) port 5555.
Code:
adb usb
Starts the adb server in USB mode.
Note: You can connect to one device over USB at the same time that you are connected to another over TCP (WiFi).
I do that all the time.
You just have to specify which device you want to talk to when using push/pull/shell.
Code:
adb -s nook:5555 shell
My adbsync also works with multiple devices, but that's a separate issue.
Click to expand...
Click to collapse
thx renate so much ....... how about if i hve a dead device or an android device that i didint enable usb debugging mode but my computer can identify it via usb ...... ????
thx
Sent from my NOOK using xda app-developers app

Nexus 4 not being recognized by adb (Ubuntu 12.10)

Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!

Is adb enabled on your phone ?
Did you restart udev or rebooted ?
btw, saw this and work allot better than standard 12.10 mtp
http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html
lvandam said:
Hi all,
I am trying to connect my Nexus 4 device to my computer via USB. I am currently running Ubuntu 12.10 with the latest Android SDK installed.
The problem is that I can't seem to properly connect the Nexus 4 so that I can see the device in the devices list of adb (using ./adb devices).
An entry to the USB rules list has already been added, which is this one:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666"
The file is named "99-nexus4.rules" and properly chmodded.
The output of lsusb is:
Code:
Bus 002 Device 012: ID 18d1:4ee5 Google Inc.
I have already tried to restart the adb server several times, but with no success. Starting the server as root didn't help either. I choose to mount the phone as MTP device on the phone itself.
Currently I am lost about what the problem is in this case. I would love to hear some feedback from you guys.
Thanks in advance!
Click to expand...
Click to collapse

nardusg said:
Did you restart udev or rebooted ?
Click to expand...
Click to collapse
Yes, every time after I changed something in the rules list I restarted udev and rebooted as well.

Do you have java installed properly? Here is the post I used to get adb working on Ubuntu 12.10 (its post #62 the OP was for Ubuntu11). It didn't work till I set the proper permissions as stated in the post under editing the udev rules (line in post where it shows sudo gedit /etc/udev/rules.d/99-android.rules). I did a 64-bit install and it worked perfectly. Basically what you are doing is manually entering the Nexus 4 into the list of devices as its not there by default.
http://forum.xda-developers.com/showthread.php?p=19446284

That solution worked for me! Many thanks.

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS ---> Edit: Thanks to Annoyingduck, we have the technique for the Verizon variant in post #5. If you are a VZW user, start with step #8 below and then replace steps 14 and 15 with annoyingducks instructions!
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.

thanks.
this will definitely help those who want to try purpledrake root

I get lost at step 9 lol.

ailima said:
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
--> NOTE: Verizon users need to connect to ADB a little differently. <-- You'll have to find different instructions.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.
Click to expand...
Click to collapse
Great and useful guide Bro !

For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...

Thank you!

If you have ARCH / Manjaro or any ARCH base just type
sudo pacman -S android-udev
Plug in phone and profit

Just as an FYI to Fedora and CentOS 64 bit users: If you get an error about libraries missing you need to add the 64 bit libraries.
Code:
yum clean all
Code:
yum update
Code:
yum install glibc.i686 zlib.i686 libstdc++.i686 ncurses-libs.i686
After that you should be good.

annoyingduck said:
For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...
Click to expand...
Click to collapse
This worked for me.

I thank this guide will help too
But, don't use his files to root only the orignal purpledrake files from xda !
http://www.androidrootz.com/2014/07/how-to-root-lg-g3.html

Awesome, thanks. Always try look for those vendor ID's and stopping my phones of trying to install some darn Windows applications.
Android is Linux, why does it need Windows to function?

Thank you!
If i may to add more links for what help others:
ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.3+ (and for win 8+)
http://forum.xda-developers.com/showthread.php?t=2588979
Fastboot problems on Windows 8+ x64 with USB 3.0
http://forum.xda-developers.com/showthread.php?t=2256359
How to install ADB and Fastboot on Windows for use with Android [Guide] 2 methods
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

Thanks!!! This really helped

Thank you
Very helpful

Thanks for the guide. Would it work on Mac OS X ?

Ths,it wroks pretty good.

Didn't work first time even though I took great care in implementing the command line steps (permissions, file name, file contents, location). Had to go back from the start to notice the PTP step! Howcome it needs to be in Picture Transfer mode? ...Not essential, as I have adb working now, but thought someone might know.
Many, many thanks! Incidentally, i'm only putting it in debugging mode to hunt down what's turning on my G3's Bluetooth by itself. I've never turned BT on nor have I paired it with anything for any reason. I've had the phone two weeks and I've turned bluetooth off a half-dozen times or so. It shows no correlation with Airplane Mode or the WiFi NFC switch or anything else - just happens while the phone is sitting unattended. If anyone has insight on that one, please share it w/me somehow.

Additional steps
If after the steps above device is not detected by sudo ./adb devices, turn off development options: click all apps button->click Settings->click General->Developer options->turn it off, change phone connection to "charging", then change connection to "Send Images (PTP)", and turn back on Developer options, run sudo ./adb devices, and it should detect the phone

Thank you very much. Works for me - LG-F460K 4.4.2

Would this work on LG G4? Currently I have the "waiting for device" problem.

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.

ADB Unauthorized Error

I can't connect to ADB, at all... All i get is this message
List of devices attached
LGH918 ect. unauthorized
When i connect USB debugging, i never get the finger print prompt.... I have all the proper drivers installed, I installed ADB and Hotboot. I already cleared the contents in the .android folder.
Can someone please help. I don't know what else to do.

type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.

me2151 said:
type
Code:
adb kill-server
adb start-server
then it should ask the RSA fingerprint again.
Click to expand...
Click to collapse
Nothing unfortunately :/ the prompt never shows, no matter what i try.

Bump

Bump. Im in the same boat

Try
1) unplug v20
2) go into developer options then click Revoke USB debugging authorizations
3) plug v20 in, unlock v20 screen
4) type adb devices
5) authorize the popup you see on the phone
You should be good.