After I flash the latest CM9 or CM10 builds, ADB no longer finds my phone.
I've checked my drivers and re-installed them numerous times and that doesn't help.
In CM9 I can mount my phone just fine, and I can explore the files with ease.
I have tried other Sense based ROMs and ADB will find my phone just fine. (The last one I tried was CleanROM4.5 and ADB found it right away)
I've tried the CM9 alpha4 build and ADB works perfectly.
ADB even works in recovery work.
I'm wondering who has it working and who doesn't.
Also, if you have it working, could I pick apart your brain to see what I'm doing differently?
Just try typing 'adb devices' and see if your phone shows up.
Finally solved this issue.
Here's how I did it in Windows 7 Profession 64bit. FYI, I have HTC Sync installed.
Plug your phone in to your pc.
Open up device manager (Right click computer -> Manage -> Device Manager)
Find your phone in the list.
Mine was initially under 'Other Devices' labeled as 'One'
Right click -> Update Driver Software...
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Make sure to uncheck 'Show compatible hardware'
Select 'Android Phone' then 'Next'
Select 'Google, Inc' on the left pane and 'Android ADB Interface' on the right pane. Hit Next
Hit 'OK' if there was a warning.
To test if ADB is working, launch a CMD prompt and type 'adb devices'
You should now see you phone in the list!!
p.s. mounting your sdcard should also work.
Thanks to h8rift and cortez.i for helping me out!
Click to expand...
Click to collapse
I'm in the same boat with ya. I've been trying to figure this out on my phone but have come across no solution. Nobody seems to like using adb here but I find it quite useful.. anyway I found that just using adb over WiFi is sufficing for now. Hope it gets fixed tho.
Sent from my HTC One XL using xda premium
xaey said:
I'm in the same boat with ya. I've been trying to figure this out on my phone but have come across no solution. Nobody seems to like using adb here but I find it quite useful.. anyway I found that just using adb over WiFi is sufficing for now. Hope it gets fixed tho.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That's good to know it works over WiFi. I haven't tried that myself, mainly because I don't know how.
Is it easy to set up WiFi ADB?
I need it for App development so it would be nice to get some form of it working
(At least I'm not the only one having issues)
[email protected] said:
That's good to know it works over WiFi. I haven't tried that myself, mainly because I don't know how.
Is it easy to set up WiFi ADB?
I need it for App development so it would be nice to get some form of it working
(At least I'm not the only one having issues)
Click to expand...
Click to collapse
Yup really easy. Just select the option right under enabling adb in the settings app that enables adb over WiFi. Then in the cmd prompt type "adb connect x.x.x.x:5555" where x.x.x.x is the ip address it gives you in the settings. Then you should be connected. To double check just check adb devices and it should show up.
Sent from my HTC One XL using xda premium
xaey said:
Yup really easy. Just select the option right under enabling adb in the settings app that enables adb over WiFi. Then in the cmd prompt type "adb connect x.x.x.x:5555" where x.x.x.x is the ip address it gives you in the settings. Then you should be connected. To double check just check adb devices and it should show up.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ah good deal! I'll try that when I get home.
Thanks!
Finally solved this issue.
Here's how I did it in Windows 7 Profession 64bit. FYI, I have HTC Sync installed.
Plug your phone in to your pc.
Open up device manager (Right click computer -> Manage -> Device Manager)
Find your phone in the list.
Mine was initially under 'Other Devices' labeled as 'One'
Right click -> Update Driver Software...
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Select 'Android Phone' then 'Next'
Select 'Google, Inc' on the left pane and 'Android ADB Interface' on the right pane. Hit Next
Hit 'OK' if there was a warning.
To test if ADB is working, launch a CMD prompt and type 'adb devices'
You should now see you phone in the list!!
p.s. mounting your sdcard should also work.
Thanks to h8rift and cortez.i for helping me out!
Mine comes up as HTC MTP Device and when I go into device manager and try to manually install it still fails. It doesn't come up as "One" and it won't let me choose "Google, Inc." As soon as I plug the device into the computer it starts to install the drivers and that's when it switches from "One" to "HTC MTP Device". Is there a way to make it so Windows 7 doesn't automatically try to install drivers for a device when you plug it in?
SkizzMcNizz said:
Mine comes up as HTC MTP Device and when I go into device manager and try to manually install it still fails. It doesn't come up as "One" and it won't let me choose "Google, Inc." As soon as I plug the device into the computer it starts to install the drivers and that's when it switches from "One" to "HTC MTP Device". Is there a way to make it so Windows 7 doesn't automatically try to install drivers for a device when you plug it in?
Click to expand...
Click to collapse
I had that show up once too, for this, in the 'Let me choose my own' try selecting '(Standard USB Host Controller) on the left pane and 'USB Composite Device' on the right pane.
Oh and p.s. Make sure to uncheck 'Show compatible hardware'
This worked perfectly! Thanks for this.
Sent from my One X using xda premium
i got adb working with that method above but my phone still doesn't mount the sd card without rebooting
thoughts?
bigballa said:
i got adb working with that method above but my phone still doesn't mount the sd card without rebooting
thoughts?
Click to expand...
Click to collapse
Hmm I have not heard of that issue before. That is interesting indeed. Did it used to work before on stock/other ROMs?
Well, I TRIED to follow the directions above, but I don't have the "Show compatible hardware" check box, and googling for the problem only turns up solutions to other devices that require the unchecking of that box...none, where the box IS the problem...
bikeracer4487 said:
Well, I TRIED to follow the directions above, but I don't have the "Show compatible hardware" check box, and googling for the problem only turns up solutions to other devices that require the unchecking of that box...none, where the box IS the problem...
Click to expand...
Click to collapse
What driver are you trying to update?
Is it the HTC MTP one? Or?
[email protected] said:
What driver are you trying to update?
Is it the HTC MTP one? Or?
Click to expand...
Click to collapse
It said HTC MTP at first, but I deleted the driver software for that so now it says "One".
Have you been able to resolve the issue? I'm unfortunately going on vacation and won't have internet for a week.
Sent from my One X using xda app-developers app
[email protected] said:
Have you been able to resolve the issue? I'm unfortunately going on vacation and won't have internet for a week.
Click to expand...
Click to collapse
Unfortunately, no. I've resorted to using the terminal emulator on the phone when I REALLY need the console, and I can still mount the USB storage just fine, so it's not ideal, but I've been making do.
Solved for LG OB
I browsed device manager on windows 7 , there i got missing drivers for "smbus controller"
I downloaded Intel chipset drivers and installed it. Missing smBus controller yellow icon gone. and now my device is listed in output of "adb devices" command
Related
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.
enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.
This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post
Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...
malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?
Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number
nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.
nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium
nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.
When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.
I haven't been able to do this either, anyone wanna help?
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?
Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks
what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me
openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
pmazz850 said:
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
Click to expand...
Click to collapse
If you are in fastboot it will not show up under adb... you need to install htc sync for the drivers then uninstall htc sync the program. Make sure you are using adb version 1.031 and that usb debugging is on.
pmazz850 said:
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
Click to expand...
Click to collapse
what driver did you use?
http://forum.xda-developers.com/showthread.php?t=2217396
123421342 said:
If you are in fastboot it will not show up under adb... you need to install htc sync for the drivers then uninstall htc sync the program. Make sure you are using adb version 1.031 and that usb debugging is on.
Click to expand...
Click to collapse
where do i find my adb version?
i just went in and updated android sdk to latest version.
i tried installing htc sync manager and uninstalling earlier. i assume sync manager is the same as htc sync??
Thanks.
pmazz850 said:
where do i find my adb version?
i just went in and updated android sdk to latest version.
i tried installing htc sync manager and uninstalling earlier. i assume sync manager is the same as htc sync??
Thanks.
Click to expand...
Click to collapse
Adb version in cmd prompt
Htc sync should have the drivers you can try Google to find a stand alone installer. Also switch usb ports.
Sent from my HTC6525LVW using Tapatalk
Karl said:
what driver did you use?
http://forum.xda-developers.com/showthread.php?t=2217396
Click to expand...
Click to collapse
thats the thread i got the driver from. bot i got the 4.1.... version. gonna try 4.2..
what about htc bmp drivers? are they supposed to be installed? I just seen that in my program list.
pmazz850 said:
thats the thread i got the driver from. bot i got the 4.1.... version. gonna try 4.2..
what about htc bmp drivers? are they supposed to be installed? I just seen that in my program list.
Click to expand...
Click to collapse
Having same issue with 4.2.. drivers...
pmazz850 said:
Having same issue with 4.2.. drivers...
Click to expand...
Click to collapse
so its still not showng in windows deviice manager?
and it still doesnt show in adb when you type ( adb devices)
you tried this right
Go to 'Device Manager', right click "Other Devices->HTC" and select 'Update Driver Software - HTC'
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Select 'Android USB Devices' & select 'Next'
Select 'Have Disk' and select the folder you unpacked the HTC Driver
Karl said:
so its still not showng in windows deviice manager?
and it still doesnt show in adb when you type ( adb devices)
you tried this right
Go to 'Device Manager', right click "Other Devices->HTC" and select 'Update Driver Software - HTC'
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Select 'Android USB Devices' & select 'Next'
Select 'Have Disk' and select the folder you unpacked the HTC Driver
Click to expand...
Click to collapse
My htc shows under portable devices. Under other devices it only says Broadcom USH. Also when i plug my phone into usb it says htc installed correctly, ready to use. but also "unknown device not installed "
I have never in all my years of rooting and roming had this issue and it's a pain in my ass!!
pmazz850 said:
My htc shows under portable devices. Under other devices it only says Broadcom USH. Also when i plug my phone into usb it says htc installed correctly, ready to use. but also "unknown device not installed "
Click to expand...
Click to collapse
go to unknown and add driver manually
Karl said:
go to unknown and add driver manually
Click to expand...
Click to collapse
Having trouble trying to update driver. When asked to direct to the driver, i cant find it. Its looking for an .inf file but the driver is in an exe file. Dont know where it supposidly installed to.
i used this to pull mine http://sourceforge.net/projects/drvback/
you can use the inf's or try to use the restore its your call
windows 7 64bit
If you're trying to S-OFF, the instructions state HTC Sync Manager isn't supposed to be installed. So if it still is, uninstall that (you can uninstall it separately from the HTC drivers). Also, make sure USB Debugging is enabled. Plus, when you connect the first time after enabling USB debugging make sure you hit the checkbox that says something like "always allow". I didn't, and it didn't prompt me on subsequent connections. I had to disable USB debugging and re-enable it to allow adb commands to communicate again.
good point i dont think that was tried go to debug and revoke authorizations
sfreemanoh said:
If you're trying to S-OFF, the instructions state HTC Sync Manager isn't supposed to be installed. So if it still is, uninstall that (you can uninstall it separately from the HTC drivers). Also, make sure USB Debugging is enabled. Plus, when you connect the first time after enabling USB debugging make sure you hit the checkbox that says something like "always allow". I didn't, and it didn't prompt me on subsequent connections. I had to disable USB debugging and re-enable it to allow adb commands to communicate again.
Click to expand...
Click to collapse
the only reason i installed htc sync was to get the drivers and after install i removed it. and debugging is checked. if i uncheck usb debugging and re-check, i don't get an option for a checkbox. just asks me to ok or cancel usb debugging.
Tried revoking authorizations....same deal....no device listed.
pmazz850 said:
the only reason i installed htc sync was to get the drivers and after install i removed it. and debugging is checked. if i uncheck usb debugging and re-check, i don't get an option for a checkbox. just asks me to ok or cancel usb debugging.
Tried revoking authorizations....same deal....no device listed.
Click to expand...
Click to collapse
did you try them drivers
Karl said:
did you try them drivers
Click to expand...
Click to collapse
Ya i click on htc in device manager, click update driver, and direct to the file and it says driver updated, but i'm not convinced its actually updating. still trying something now....gettin pissed now....picked up some malware along the way today that ****ed me up for a little while! I appreciate your help and will post back in a little while.
pmazz850 said:
Ya i click on htc in device manager, click update driver, and direct to the file and it says driver updated, but i'm not convinced its actually updating. still trying something now....gettin pissed now....picked up some malware along the way today that ****ed me up for a little while! I appreciate your help and will post back in a little while.
Click to expand...
Click to collapse
i meant the ones from my puter
Karl said:
i meant the ones from my puter
Click to expand...
Click to collapse
ya, thats what i used to update them.
Let me ask you something, when i click on my htc in device manager list, do i choose mot device or usb composite device? And which driver should i use to update it?
pmazz850 said:
ya, thats what i used to update them.
Let me ask you something, when i click on my htc in device manager list, do i choose mot device or usb composite device? And which driver should i use to update it?
Click to expand...
Click to collapse
usb, did you try to use all 3? or use the ones you dont see on your end