Hi, I have a problem in the connection between the fire and kindle mac.
I state, ADB I installed and working properly.
When I enable debug function, and I enter the command ./adb devices, the output gives me empty, ie not find the kindle. Yet he continues to appear on the desktop and connect as mass storage.
How can I do?
what rom do you have on the kf couse you are able to enable/disable usb debugging ?
may be you are able to find mac specific answers over the *FULL LIST*
maybe restart adb by "adb kill-server" and try again ...
b63 said:
what rom do you have on the kf couse you are able to enable/disable usb debugging ?
may be you are able to find mac specific answers over the *FULL LIST*
maybe restart adb by "adb kill-server" and try again ...
Click to expand...
Click to collapse
Is the stock rom: Current Version: 6.2.2_user_3205220
I received new Defy XT Dec. 17 from Republic Wireless and wanted to move as many apps as possible to SD card without rooting as discussed elsewhere.
However, after enabling USB debugging on the phone (Settings - Applications - Development) and connecting the phone to the computer with the USB cable here is the message when I type command "adb devices".
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
command "adb version" returns:
Android Debug Bridge version 1.0.31
Apparently my Defy is not recognized and of course no other adb commands work. I'm not using Windows. I'm using Linux, Ubuntu 12.10. I've used adb successfully on same computer with Acer Iconia A100 Tab. Attached file contains pertinent messages in syslog when usb cable from Defy is connected to computer. Any help with why this device not recognized by adb would be appreciated.
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
Code:
$ lsusb
Bus 002 Device 014: ID 19d2:0306 ZTE WCDMA Technologies MSM
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0306", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="0306",SYMLINK+="android_adb", GROUP="adbusers"
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
Code:
$ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
6f7f7da7 unauthorized
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
unrealpowerz said:
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem in Windows when using a custom rom. Enabling 'adb over network' solved it for me (the 'Allow USB debugging' window came up). even though it's seemingly unrelated
If that doesn't work try adb while phone is in TWRP (if you have it)
Hey fellow arch user here, (pacman ftw)
I had this same problem earlier with adb and fastboot. The solution is to run adb and fastboot commands as superuser. ie sudo fastboot ..... and sudo adb ......
Hi Everyone:
I am sorry if someone asked this question before, but I could not find an answer that works for me. I just got my phone today and I want to root it. I am planning to use my laptop running Linux FC21. I have used adb on this machine before and it has work flawlessly. Here is what I have done:
- became a developer on the phone
- enabled usb debugging
- enabled OEM unlocking
- connected the phone to my computer.
- I get a notification on the phone saying "USB debugging connected"- typed 'sudo adb devices'
- The list is empty.
I have tried stopping and starting the sever with no effect. I have tried multiple USB ports and cables (USB-A to USB-C). That did not help. I have looked at dmesg and it sees the phone.
Code:
[email protected] ~] dmesg | tail
[ 1650.391982] usb 1-3: Product: PH-1
[ 1650.391984] usb 1-3: Manufacturer: Essential Products
[ 1650.391985] usb 1-3: SerialNumber: PM1LHMA792600274
[ 2128.638511] usb 1-3: USB disconnect, device number 16
[ 2133.666971] usb 1-3: new high-speed USB device number 17 using xhci_hcd
[ 2133.835601] usb 1-3: New USB device found, idVendor=2e17, idProduct=c032
[ 2133.835614] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2133.835617] usb 1-3: Product: PH-1
[ 2133.835618] usb 1-3: Manufacturer: Essential Products
[ 2133.835620] usb 1-3: SerialNumber: PM1LHMA792600274
Finally I have downloaded 51-android.rules from the web and added the line:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0600", OWNER="hal"
This did not help either.
So, HELP!
Thanks
----
EDIT: I tried both my Galaxy Note4 and my Zenwatch3 and they both worked.
----
EDIT: The phone never shows the popup asking if I want to authorize my computer.
Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.
NaterTots said:
Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, this did not work for me.
Have you tried leading your commands with ./?
This is required on Mac: ./adb devices
Airwolf79 said:
Have you tried leading your commands with ./?
This is required on Mac: ./adb devices
Click to expand...
Click to collapse
No, that will not make a difference. The $path is set correctly on the machine. If what you suggested was an issue, I would get "adb: Command not found" when I tried to execute it.
Thanks for the suggestion!
Do you have lastest ADB?
Sent from my PH-1 using XDA Labs
avd said:
Do you have lastest ADB?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Well, I have been working this and I think that you identified the problem. I have the most up-to-date for my OS, but it is old and I can't get newer versions to work. I had to move on to Windows :crying:
The instructions I found suggested creating a user group and adding myself to it:
Code:
sudo groupadd androiddev
sudo usermod -aG androiddev your_login_name
Then grant the permissions to that group rather than directly to my user account:
Code:
sudo sh -c "echo 'SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="androiddev"' >> /etc/udev/rules.d/51-android.rules"
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.
bjs339 said:
The instructions I found suggested creating a user group and adding myself to it:
Then grant the permissions to that group rather than directly to my user account:
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.
Click to expand...
Click to collapse
When you run fastboot run it as super user.
Modify the flashall and prepend sudo in front of every line
Sent from my PH-1 using XDA Labs
Mine has never seen my device when running adb devices,however commands to give write permission still worked
Sent from my Essential Phone using XDA Labs
I am currently trying to gain access to a device based on the rk3128 and android.
There was an UART that allows me to access the serial console including su.
I successfully connected the device to my wifi. Currently I am struggling to enable ADB. It doesn't work via usb, even after typing "adb -d start-server"
using "adb -a start-server" doesn't work for me, as the server is only started on 127.0.0.1 (netstat).
Any idea how to get adb access over network?