adb devices doesn't show anything. I have tried it with linux and windows (with Motorola drivers installed), it doesn't work. I can access the phone when I have enabled MTP, but it just won't show in adb. I have killed and started adb server so many times, it's frustrating.
The thing is, the first time (yesterday) it worked! I could reboot into fastboot with adb but then nothing worked anymore.
Any ideas?
Maybe silly question, but: is USB debugging activated on the phone? If yes, try to switch between MTP and Camera (PTP) under "USB computer connection" option. You should get the authorization prompt on your phone when everything is fine.
Yes, USB debugging is activated. I already tried both MTP, PTP, and neither, but I don't get any authorzation prompts. I revoked all previos prompts, but still nothing. Thanks for the suggestion though!
Are you on bootloader or recovery or normally on os
I tried all three.
Try playing with the USB cable - change it, change the USB slot on the PC that it's connected to, etc.
I only have one USB cable, but I already tried it on several USB slots.
It worked! I had to put sudo in front of my adb commands! Yay! :victory:
Related
I installed the Samsung USB drivers on my Win 7 64-bit laptop. I have ADB installed, and have used it for other devices, no problem. I can still use it to connect to my Color Nook.
I kill-server; start-server, and look for devices - nothing. But I can see the USB installer and those other few files on the phone, and I can see everything on the sdcard.
Any ideas? I'm going crazy here.
Do you have USB debugging on?
Sent from my SCH-I510 using XDA App
I had this problem as well.
First see if you have the "SAMSUNG usb driver" installed in control panel programs.
If not, take off usb debug and connect phone to computer. Then you should get a "install verizon software" option once you plug it in. Install software .. Then, enable "usb debuging" try it again, if that doesn't work .. remove verizon software, not usb drivers. This is basically what i did, and it started working
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
On Mac try sudo adb whatever
Always with sudo
Sent from my MB865 using xda app-developers app
xxDriveNxx said:
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
cogeary said:
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
Click to expand...
Click to collapse
I guess I'll have to give the factory wipe a shot tonight. I was really hoping it wouldn't come to that since I can't use Titanium Backup due to lack of root.
all i did was have my phone plugged in while i was installing the drivers. but i did have to download the ones from your post.
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
kousik said:
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
Click to expand...
Click to collapse
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Bob G said:
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Click to expand...
Click to collapse
FYI adb will not work in mass storage mode.adb needs the phone memory and other access which are not there when you connect your phone in mass storage where it acts merely as a card reader
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Just in case anyone else was on the fence about doing this: I had tried a million things (trying different computers, different USB cables, installing and uninstalling different drivers, editing driver inf files, editing adb_usb.ini, etc) for several days and nothing worked. I was skeptical about the factory reset helping, but now that I did it I can finally connect to my phone. Yay!
My setup used to work
Windows 7
CM11S
MTP work just fine. Can browse OPO /sdcard from windows 7
adb device work just fine. I can run all adb commands without problem: devices, shell, push, pull, etc
Now that I have upgraded to CM12S
MTP still work. I can browse OPO /sdcard from windows 7
adb device does not work.
adb devices report nothing. No error, just nothing. As if the phone is not plugged into the computer [see attached screenshot].
But I already installed usb driver, both google's latest and koush's universal adb driver, and tried ADB Interface and ADB Composite Interface
Currently, phone is setup as follow
Setting -> Storage -> USB Computer Connection : MTP
Setting -> Developer Option -> Android Debugging : on
With Android Debugging on, adb device won't show my phone serial when USB Computer Connection is MTP or PTP
When USB Computer Connection is set to charge only, Android Debugging is disabled
With Android Debugging off, I can browse the whole /sdcard when USB Computer Connection is set to MTP
With Android Debugging off, I can browse only DCIM and Pictures from /sdcard when USB Computer Connection is set to PTP
Back in CM11S
When USB Computer Connection is set to MTP, and Android Debugging off, I can browse the whole /sdcard from PC
When USB Computer Connection has NOTHING selected (no MTP, no PTP), and Android Debugging is on, I can use adb.exe on command line: devices, shell, push, pull, etc all work just fine
On CM12S, one of these options MUST be selected in USB Computer Connection: MTP, PTP, Charge Only. This is changed from CM11S
Does anyone have any success with adb.exe on command line on Windows 7 and CM12S (stock kernel)?
If yes, what is your phone setup for adb.exe to work, and which usb driver you installed on your winodws 7?
Thanks!
EDIT: fastboot work just fine
When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon
timmaaa said:
When you're on CM12S you can't have MTP enabled if you want to use adb. Disable MTP temporarily and adb should work.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks
animefans said:
timmaaa, this is what i could figure out
my only problem is: how do I disable MTP on CM12S?
On CM11S, I can
On CM12S, I must choose one of the options: MTP, PTP, Charge Only
If I am on MTP, and I press it again, the screen just grey out
and then I push back button to go back to main storage screen
and now I choose USB Computer Connection again, and MTP is still selected/enabled
Have you tried to do adb devices on windows on CM12S?
If you can, did you ever enable MTP or PTP?
Thanks
Click to expand...
Click to collapse
Instead of pressing MTP again, select PTP.
Transmitted via Bacon
timmaaa said:
Instead of pressing MTP again, select PTP.
Transmitted via Bacon
Click to expand...
Click to collapse
I will try to reconfirm, but I believe I tried that already
regardless of MTP or PTP, adb devices does not find my phone
EDIT: yup, regardless of MTP or PTP, when adb debug is on in developer tools, adb device does not show serial number, so can't connect to phone via adb shell
Same exact problem here, adb worked fine until I turned on MTP now I can't turn it back off and thus adb not working.
No matter what I select or disable I always end up with MTP back on and no ADB working. Someone else who just got their OPO yesterday having same issue and what caused me to mess with MTP setting breaking my ability to ADB :/
Also another new behavior to me is that I cannot access "USB Computer Connection" screen unless I am plugged into PC. When not connected to PC it just rescans internal storage and go's nowhere.
Quick dirty screencast showing how MTP can't be turned off (sorry rushed and kid in background)
https://drive.google.com/file/d/0Bwwwt8cZbp9rYXRGa0Y1dFBfY1k/view?usp=sharing
Good to hear, in a way...
Good is that it's not just me
Bad is that this problem exist
BTW, created this problem in jira
https://jira.cyanogenmod.org/browse/BACON-3358
Hopefully this is a bug in the setting app where USB Computer Connection option is not required. Right now options are required
PS: and yes, I notice the same thing where USB Computer Connection is not even available until you plugged it into PC
PPS: I wonder what is the behavior of USB Computer Connection under OxygenOS and Stock Android (ie Nexus 5/6/etc). Having this data point can narrow down if issue is cyanogenmod OS specific issue, or it's a general Lollipop AOSP issue
is this can be problem why I couldn't install custom recovery?? I try install TWRP, device have unlocked bootloader
if running adb devices on your PC can not see the phone (ie phone serial), then yes you can't install TWRP this way
However, I believe there are other ways to install custom recovery onto your phone without PC
Try TWRP Manager on play store
I used this to update my TWRP recently in order to update to CM12S without going through OTA
Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root
Solodude said:
Yeah I have the same issue as well and now i don't have Twerp or root . and i can confirm i never had the issue on my nexus 4 with stock LP and Dirty unicorns so it looks like a CM bug to me my phone feels incomplete without root
Click to expand...
Click to collapse
Thank you for the data Solodude!
Quick update on my current situation on this issue
http://forum.xda-developers.com/showpost.php?p=61975450&postcount=4
Can someone explain me how to get ADB working on my SGS8? I've tried everything: installing drivers, Java, Android SDK, 15 sec adb driver, universal ADB driver, minimal adb. I can't figure out how to do that.
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
jaannnis said:
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
Click to expand...
Click to collapse
Thanks, will try that
i was having one hell of a time as well. I tried everything on my laptop to no success. So i actually gave up. Than i thought well maybe its my laptop. So i ended up trying another one i had in the house and viola it worked like a charm. It seems like certain pc are just unable to connect to the samsung s8 via adb mode. Which is totally weird because I had been using adb mode on my pixel xl with no issues what-so-ever. So try a different pc if you can, it worked for me flawlessly.
Might be the USB port.
I had a similar problem connecting my Lenovo laptop to a Kindle Fire. I used a different USB port and everything worked.
9 bin
Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs