Related
Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "ADB devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
shouldnt it be adb devices instead of dab ?
I wanna try this ABD but there no link?!!
Shouldn't this ABC post be somewhere else?
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
sheetmetalninja said:
you guys should quit cluttering this thread and help him figure this whole KFC thing out....
Click to expand...
Click to collapse
You're right.
But I also don't know anything about BAD or FASTBOOB or anything like that. I don't like reading. :[
yasinis said:
ok guys, here you go:
my phone doesn't make any ADB connections anymore with my mac.
points i already tested:
- reinstalled all the android dev tools
- flashed several rome on my sensation (tried: Beast rom, pyramid, arhd)
- reboot without fast boot
- usb debugging is active!
when i'm typing in terminal: "dab devices" --> i get no devices.
where is the problem?
i already used adb while s-off my device, but now it won't work anymore.
just remember, i'm using a MAC, so i haven't got a pc!
Click to expand...
Click to collapse
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Check the drivers, you may need to update them
Sent from my Desire HD using XDA App
taney said:
go into devmgmt.msc and see if your phone shows up under adb interfaces. if not, could be 1) bad usb cable, 2) bad usb port, 3) bad adb driver.
Click to expand...
Click to collapse
how 2 do that? i mean what do you mean with devmgmt.msc(device management...?)
1) usb cable is good, the original one. also tried different usb cables, it doesn't matter.
2) usb port is also ok, other devices running out of the box (f.e. dvd drive oder dslr)
3) adb driver already updated via "Android SDK and AVD Manager".
i installed Android SDK tools, SDK Platform tools, sdk platform (--> is there sth. missing?)
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Romanbb said:
Try disabling debugging on the phone, plug it in, reboot it, then enable debugging again
Click to expand...
Click to collapse
no sorry...won't work..
getting the same:
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
also tried without fastboot rebooting.
there are news guys:
just got an windows 7 personal computer for a couple of days.
installing the sdk and usb driver just worked fine.
why it doesn't work for mac?
already installed all new...
You may also check the cable you're using to connect the phone to your Mac. I was getting the same problem when trying to use the cable from my car charger - the phone was not even visible on the system list of USB devices. Using the cable that came with the phone did the trick.
(although if you used the same cable with Windows and it worked, my hint won't be of much help)
Do you got HTC sync installed on your PC?
TheStigx said:
Do you got HTC sync installed on your PC?
Click to expand...
Click to collapse
please remember - i'm using a MAC!
so finally i tested my device with several computers at the university.
i just found out, that the problem may been caused of my installed mac osx lion - but don't ask me why!
on the mac of my prof (also osx lion with latest updates) it worked out of the box...
--> so i'm gonna making backups now and will format my hard disk and reinstall lion again.
i'll give u feedback again ;-)
Have you closed the htc-sync application? solved the connection-error for me...
Maeffjus said:
Have you closed the htc-sync application? solved the connection-error for me...
Click to expand...
Click to collapse
again guys:
I'm using a MAC!
is there any official sync app for mac i don't know about??
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
yasinis said:
ok guys,
just reinstalled my system an got the problem away..
i don't know why this was so, but i'm happy to make it work now.
Click to expand...
Click to collapse
ok, just found out where the problem was caused. it was EasyTether!
this will help:
Code:
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!
MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?
MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?
MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder
Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.
Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)
Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.
Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).
Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!
Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk
drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?
spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.
File transfer and fastboot don't work on my Ubuntu either.
spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked
I have same problem with Windows 10 64Bit.
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
I have solved my problem. I have install Windows 10 new and now all working.
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.
Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.
James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day
Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem