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
Related
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
4nic8 said:
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
Click to expand...
Click to collapse
WORKS FOR EPIC 4G!!!!!
This worked for my BH2 but it may need some tweaking on the rules file to make it work, but I will double check it when I get home.
After downloading the SDK, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.
After this, I took the rules file (attached) and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:
su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules
Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!
Note: Attachment updated!
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I will tune the Rules file and test and let you know. Most of the time, when it doesn't work, its the rules file who has the problem.
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
megabiteg said:
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
Click to expand...
Click to collapse
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
4nic8 said:
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
Click to expand...
Click to collapse
mmmm..
I've tested this with several other friends that use Ubuntu 10.10 and it works fine for them. Are you following step by step on my OP?
Also are you on a desktop or laptop? Please note that while you have USB Debugging on the option to mount your SD card will not be prompted.
If your using a Desktop, please refrain of using front side USB ports. If you need additional help, let me know, I'll be glad to help you getting it working.
send me what the lsusb command dumps if you can, that can help me tweak the rules file for you.
Thanks! after some trial and error..the zip file in the first post worked for me!
FYI, you can just run this command instead of restarting your computer:
Code:
sudo udevadm control –reload-rules; sudo reload udev; adb kill-server; adb devices
Same problem
Hello, I have the same problem, adb don't detect my tablet. I do it from my laptop and this is the lsusb exit:
[email protected]:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 18d1:0001 Google Inc.
Bus 001 Device 002: ID 174f:a311 Syntek 1.3MPixel Web Cam - Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Click to expand...
Click to collapse
Is it possible that the integrated webcam generates the conflict? how can I disable it on Ubuntu 10.10?
Thanks
One thing I've noticed is that my phone will come right up (with debugging turned on) on certain usb ports but won't on others. Might be worth trying different USB ports just to see if it makes a difference.
Was this way on both my desktop and my netbook (both running Ubuntu 10.10).
Thanks flatspin, I have tried all my 4 usb ports without luck.
Solved, I forgot to put the tablet on adb mode at boot time.
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
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.
Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.
hohassan444 said:
Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.
Click to expand...
Click to collapse
Do you mind providing a link to the linux version so that i can test?
kirito9 said:
Do you mind providing a link to the linux version so that i can test?
Click to expand...
Click to collapse
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note: currently latest version on that page actually is SP Flash Tool v5.1520.00
Nofan Tasi said:
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note latest version on that page actually is SP Flash Tool v5.1520.00
Click to expand...
Click to collapse
Alright, thanks
I found a solution for S_BROM_CMD_JUMP_DA_FAIL (2035) here:
The “modemmanager” package integrated by default on your computer it is not compatible with the MTK Flash Tool for the Linux (14.04 and 14.10) latest versions, and must be uninstalled beforehand. This package is used as a protective USB modem device. Any user configuration file will remain after you uninstall and install the package. Though, we can reinstate our current configuration if necessary, after using the tool.
The following steps will be necessary for the latest versions of Ubuntu:
º Uninstall the designated package using the following commands:
♦sudo apt*-get remove modemmanager
♦sudo service udev restart
Udev restart the service without restarting the computer
Udev restart the service without restarting the computer
This may have the side effect of removing the kernel module “cdc_acm”. To check if so, run the following command:
♦lsmod | grep cdc_acm
Check kernel module
Check kernel module
º If it gives you an empty list in return, you must install the following module:
♦sudo modprobe cdc_acm
Click to expand...
Click to collapse
After this, the tool connected to my phone without errors.
I reinstalled modemmanager after flashing:
Code:
sudo apt-get install modemmanager
I slightly modified Sergio Riveros excellent! marvellous! perfect! tutorial and translated it into German for android-hilfe.de
I will post an English version here within the next couple of days...
I finally can put the ancient XP netbook back where it came from to (hopefully) never have to come out again.
The linux SP flash tool works just fine and, yes: cdc_acm module is needed as dmesg shows:
--
usb 1-5: new high-speed USB device number 6 using ehci-pci
usb 1-5: New USB device found, idVendor=0e8d, idProduct=2000
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: MT65xx Preloader
usb 1-5: Manufacturer: MediaTek
cdc_acm 1-5:1.1: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
--
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 ......