ADB device list doesn't show phone
I've recently installed adb and fastboot:
apt-get install android-tools-adb android-tools-fastboot
After the installation finished, I connected my device and ran the following command:
$ adb devices
List of devices attached
I've enabled debugging in the phone settings.
I think am doing it wrong-- I don't know. Please explain me the correct process.
Using Ubuntu 16.01. Device: Yu Yuphoria
Update edit:
After all the frustrating attempts It's still not detected in adb.
However in fastboot mode, adding the vendor id command for my device, fastboot -i 0x2a96 devices as found mentioned here works
fastboot -i 0x2a96 devices
returned
7dd91912 fastboot
Other commands in fastboot mode, as instructed in the same page mentioned above, works too when vendor id command option was added.
android adb
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
|
show 7 more comments
I've recently installed adb and fastboot:
apt-get install android-tools-adb android-tools-fastboot
After the installation finished, I connected my device and ran the following command:
$ adb devices
List of devices attached
I've enabled debugging in the phone settings.
I think am doing it wrong-- I don't know. Please explain me the correct process.
Using Ubuntu 16.01. Device: Yu Yuphoria
Update edit:
After all the frustrating attempts It's still not detected in adb.
However in fastboot mode, adding the vendor id command for my device, fastboot -i 0x2a96 devices as found mentioned here works
fastboot -i 0x2a96 devices
returned
7dd91912 fastboot
Other commands in fastboot mode, as instructed in the same page mentioned above, works too when vendor id command option was added.
android adb
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
1
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16
|
show 7 more comments
I've recently installed adb and fastboot:
apt-get install android-tools-adb android-tools-fastboot
After the installation finished, I connected my device and ran the following command:
$ adb devices
List of devices attached
I've enabled debugging in the phone settings.
I think am doing it wrong-- I don't know. Please explain me the correct process.
Using Ubuntu 16.01. Device: Yu Yuphoria
Update edit:
After all the frustrating attempts It's still not detected in adb.
However in fastboot mode, adding the vendor id command for my device, fastboot -i 0x2a96 devices as found mentioned here works
fastboot -i 0x2a96 devices
returned
7dd91912 fastboot
Other commands in fastboot mode, as instructed in the same page mentioned above, works too when vendor id command option was added.
android adb
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
I've recently installed adb and fastboot:
apt-get install android-tools-adb android-tools-fastboot
After the installation finished, I connected my device and ran the following command:
$ adb devices
List of devices attached
I've enabled debugging in the phone settings.
I think am doing it wrong-- I don't know. Please explain me the correct process.
Using Ubuntu 16.01. Device: Yu Yuphoria
Update edit:
After all the frustrating attempts It's still not detected in adb.
However in fastboot mode, adding the vendor id command for my device, fastboot -i 0x2a96 devices as found mentioned here works
fastboot -i 0x2a96 devices
returned
7dd91912 fastboot
Other commands in fastboot mode, as instructed in the same page mentioned above, works too when vendor id command option was added.
android adb
android adb
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
edited Dec 26 '16 at 12:53
naga - elixir - jar
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
asked Dec 22 '16 at 17:51
naga - elixir - jarnaga - elixir - jar
3081312
3081312
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
1
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16
|
show 7 more comments
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
1
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
1
1
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16
|
show 7 more comments
4 Answers
4
active
oldest
votes
Finally got the device detected in adb under adb devices command by restarting adb server with root privilege as mentioned here in the Troubleshooting adb section.
sudo adb kill-server
sudo adb start-server
After this adb devices returned
7dd91912 unauthorized
with a prompt on device for RSA authorize. After authorizing
adb devices now returns
72291912 device
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
add a comment |
Make sure you have a good USB cable and are plugged into a good port. This was always the problem I experience when using ADB and fastboot. Also make sure you update and have the latest ADB drivers.
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
add a comment |
You installed the adb program correctly. The Android Debugging isn't activated by default. The activation option is hidden. You'll have to reveal it with these steps:
Goto Settings -> About phone -> (scroll to) Build number ->
(Tap on it about 7 times) -> (You should get a notice
You have enabled the development settings)
Now you will have a new menu item in settings called Developer options.
Go into this option and turn on the USB debugging option.
Now when you plug in the USB cable to the computer, you'll get the prompt to Authorize the connected computer.
After the debugging is turned on you may have to restart the server. You can do that with these commands:
$ adb kill-server
$ adb start-server
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with thekill-serverandstart-serveradded to my answer.
– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
|
show 10 more comments
To set up device detection on Ubuntu Linux:
Using sudo, create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
If you do not know your vendor ID, you can get this from lsusb, it is the string after ID.
Once you have created/updated the file, execute:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f863587%2fadb-device-list-doesnt-show-phone%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Finally got the device detected in adb under adb devices command by restarting adb server with root privilege as mentioned here in the Troubleshooting adb section.
sudo adb kill-server
sudo adb start-server
After this adb devices returned
7dd91912 unauthorized
with a prompt on device for RSA authorize. After authorizing
adb devices now returns
72291912 device
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
add a comment |
Finally got the device detected in adb under adb devices command by restarting adb server with root privilege as mentioned here in the Troubleshooting adb section.
sudo adb kill-server
sudo adb start-server
After this adb devices returned
7dd91912 unauthorized
with a prompt on device for RSA authorize. After authorizing
adb devices now returns
72291912 device
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
add a comment |
Finally got the device detected in adb under adb devices command by restarting adb server with root privilege as mentioned here in the Troubleshooting adb section.
sudo adb kill-server
sudo adb start-server
After this adb devices returned
7dd91912 unauthorized
with a prompt on device for RSA authorize. After authorizing
adb devices now returns
72291912 device
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
Finally got the device detected in adb under adb devices command by restarting adb server with root privilege as mentioned here in the Troubleshooting adb section.
sudo adb kill-server
sudo adb start-server
After this adb devices returned
7dd91912 unauthorized
with a prompt on device for RSA authorize. After authorizing
adb devices now returns
72291912 device
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
edited 6 mins ago
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
answered Dec 23 '16 at 10:45
naga - elixir - jarnaga - elixir - jar
3081312
3081312
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
add a comment |
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
also carefully check that debugging via USB is on
– im_infamous
Jan 8 '18 at 13:07
1
1
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
When these steps are not enough, check out this more complete answer.
– Skippy le Grand Gourou
Jul 23 '18 at 16:14
add a comment |
Make sure you have a good USB cable and are plugged into a good port. This was always the problem I experience when using ADB and fastboot. Also make sure you update and have the latest ADB drivers.
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
add a comment |
Make sure you have a good USB cable and are plugged into a good port. This was always the problem I experience when using ADB and fastboot. Also make sure you update and have the latest ADB drivers.
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
add a comment |
Make sure you have a good USB cable and are plugged into a good port. This was always the problem I experience when using ADB and fastboot. Also make sure you update and have the latest ADB drivers.
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
Make sure you have a good USB cable and are plugged into a good port. This was always the problem I experience when using ADB and fastboot. Also make sure you update and have the latest ADB drivers.
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
answered Dec 22 '16 at 18:29
MwebbsMwebbs
413
413
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
add a comment |
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
1
1
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
ADB drivers? Aren't those only for Windows?
– wjandrea
Dec 22 '16 at 21:11
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
Agreed, after an entire day spent getting frustrated with my computer and phone, it turned out that the cable was the reason they weren't talking.
– David Thefan
Dec 22 '16 at 21:56
add a comment |
You installed the adb program correctly. The Android Debugging isn't activated by default. The activation option is hidden. You'll have to reveal it with these steps:
Goto Settings -> About phone -> (scroll to) Build number ->
(Tap on it about 7 times) -> (You should get a notice
You have enabled the development settings)
Now you will have a new menu item in settings called Developer options.
Go into this option and turn on the USB debugging option.
Now when you plug in the USB cable to the computer, you'll get the prompt to Authorize the connected computer.
After the debugging is turned on you may have to restart the server. You can do that with these commands:
$ adb kill-server
$ adb start-server
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with thekill-serverandstart-serveradded to my answer.
– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
|
show 10 more comments
You installed the adb program correctly. The Android Debugging isn't activated by default. The activation option is hidden. You'll have to reveal it with these steps:
Goto Settings -> About phone -> (scroll to) Build number ->
(Tap on it about 7 times) -> (You should get a notice
You have enabled the development settings)
Now you will have a new menu item in settings called Developer options.
Go into this option and turn on the USB debugging option.
Now when you plug in the USB cable to the computer, you'll get the prompt to Authorize the connected computer.
After the debugging is turned on you may have to restart the server. You can do that with these commands:
$ adb kill-server
$ adb start-server
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with thekill-serverandstart-serveradded to my answer.
– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
|
show 10 more comments
You installed the adb program correctly. The Android Debugging isn't activated by default. The activation option is hidden. You'll have to reveal it with these steps:
Goto Settings -> About phone -> (scroll to) Build number ->
(Tap on it about 7 times) -> (You should get a notice
You have enabled the development settings)
Now you will have a new menu item in settings called Developer options.
Go into this option and turn on the USB debugging option.
Now when you plug in the USB cable to the computer, you'll get the prompt to Authorize the connected computer.
After the debugging is turned on you may have to restart the server. You can do that with these commands:
$ adb kill-server
$ adb start-server
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
You installed the adb program correctly. The Android Debugging isn't activated by default. The activation option is hidden. You'll have to reveal it with these steps:
Goto Settings -> About phone -> (scroll to) Build number ->
(Tap on it about 7 times) -> (You should get a notice
You have enabled the development settings)
Now you will have a new menu item in settings called Developer options.
Go into this option and turn on the USB debugging option.
Now when you plug in the USB cable to the computer, you'll get the prompt to Authorize the connected computer.
After the debugging is turned on you may have to restart the server. You can do that with these commands:
$ adb kill-server
$ adb start-server
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
edited Dec 22 '16 at 18:29
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
answered Dec 22 '16 at 18:09
L. D. JamesL. D. James
18.8k43889
18.8k43889
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with thekill-serverandstart-serveradded to my answer.
– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
|
show 10 more comments
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with thekill-serverandstart-serveradded to my answer.
– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
I've already turned on the 'USB debugging' option - but not getting any prompt on connecting to the computer
– naga - elixir - jar
Dec 22 '16 at 18:11
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
Also need to add udev rules for your device
– Kyle H
Dec 22 '16 at 18:28
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
can you please explain how to add the udev rules
– naga - elixir - jar
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with the
kill-server and start-server added to my answer.– L. D. James
Dec 22 '16 at 18:31
@red_speck When you connect your device, do you get a usb file browser of the content, or the option to view the content? Also, try starting restarting the adb server with the
kill-server and start-server added to my answer.– L. D. James
Dec 22 '16 at 18:31
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
I don't get this clearly "do you get a usb file browser of the content, or the option to view the content?" but if I guess what you mean, I think it's the usb file browser (I can browse through the files of the phone - I've used all three available options to connect USB for my device - MTP, PTP and charge only). I've tried restarting the adb with your said commands.
– naga - elixir - jar
Dec 22 '16 at 18:37
|
show 10 more comments
To set up device detection on Ubuntu Linux:
Using sudo, create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
If you do not know your vendor ID, you can get this from lsusb, it is the string after ID.
Once you have created/updated the file, execute:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
add a comment |
To set up device detection on Ubuntu Linux:
Using sudo, create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
If you do not know your vendor ID, you can get this from lsusb, it is the string after ID.
Once you have created/updated the file, execute:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
add a comment |
To set up device detection on Ubuntu Linux:
Using sudo, create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
If you do not know your vendor ID, you can get this from lsusb, it is the string after ID.
Once you have created/updated the file, execute:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
To set up device detection on Ubuntu Linux:
Using sudo, create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
If you do not know your vendor ID, you can get this from lsusb, it is the string after ID.
Once you have created/updated the file, execute:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
answered Dec 22 '16 at 19:46
Organic MarbleOrganic Marble
11.5k63459
11.5k63459
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
add a comment |
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
1
1
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
I did all this, (vendor id for my device 2a96) and also created adb_usb.ini file in .android from this post
– naga - elixir - jar
Dec 23 '16 at 8:49
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f863587%2fadb-device-list-doesnt-show-phone%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you already authorized the computer's RSA key?
– wjandrea
Dec 22 '16 at 17:53
Am a total newbee - can you please explain? Thanks.
– naga - elixir - jar
Dec 22 '16 at 17:54
When you enable USB debugging in the phone, then attach it via USB, you should get a prompt asking if you want to allow the PC to debug the phone, and it will show you the PC's RSA key to identify it.
– wjandrea
Dec 22 '16 at 17:56
I didn't get any such prompt when I attached my phone to the computer.
– naga - elixir - jar
Dec 22 '16 at 17:58
1
@Teekin see if this helps stackoverflow.com/questions/10086464/…
– naga - elixir - jar
Nov 20 '18 at 9:16