Related
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
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
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.
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
thatguy97 said:
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There should be a prompt on your phone when you connect to a computer. If it doesn't show up, then try using the "Revoke usb authorisations" option and try again.
Accidental thanks. Enjoy.
thatguy97 said:
Title says it all... I'm trying to unlock my Nexus 5 boot loader, but I can't get USB debugging to work. Any ideas? I've tried two different computers
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Had the same issue. Solved it by enabling PTP in Settings - Storage - (menu button in the upper right) - USB-Connection.
After enabling PTP the Popup with RSA key appeared.
Hope I could help.
djcreature said:
Had the same issue. Solved it by enabling PTP in Settings - Storage - (menu button in the upper right) - USB-Connection.
After enabling PTP the Popup with RSA key appeared.
Hope I could help.
Click to expand...
Click to collapse
I did sort of the same. I disabled MTP and didn't enable MTP and that worked. You might need to do a fresh install of the drivers.
You won't get the pop-up by just plugging it in and toggling USB Debug, etc. You need to open up a program that uses ADB (Like WugFresh) or a command prompt in the adb/fastboot folder and typing -> adb devices (or fastboot devices if in fastboot mode). I just revoked computer permissions and tried ticking and unticking everything, and I couldn't get the auth pop-up. As soon as I started WugFresh, the pop-up appeared on the phone to authorize.
Still no popup
I tried everything in this topic and I still don't get popup RSA key.. working with nexus5 4.4.2 and windows8 and WugFresh toolkit
Any idea?
gcej said:
I tried everything in this topic and I still don't get popup RSA key.. working with nexus5 4.4.2 and windows8 and WugFresh toolkit
Any idea?
Click to expand...
Click to collapse
First of all, don't use toolkits... Please.
Make sure you have installed the correct drivers... Download Android sdk and make sure you have downloaded the usb_driver...
Go to developer options and revoke permissions, enable adb debugging... Now again connect your n5 to the PC and the a message should popup...
I had this problem because I was using an old version of adb
Sent from my Nexus 5 using Tapatalk
Try using different drivers
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
Use the third option in the driver installation window. Forgot what it was called but that was the only one that worked for me
Sent from my Nexus 5 using xda app-developers app
Universal Naked Drivers for Windows 8(8.1) - had the same issue myself. Was the only drivers I could get working on a Lenovo machine.
Help!!
I have tried everything with this, I reinstalled the usb google drivers countless times. I have redownloaded the SDK and have gotten no where, I even changed the connection to PTP. Someone please help!:crying:
Pure_Android said:
I have tried everything with this, I reinstalled the usb google drivers countless times. I have redownloaded the SDK and have gotten no where, I even changed the connection to PTP. Someone please help!:crying:
Click to expand...
Click to collapse
Do you get the yellow exclamation mark in device manager on the port not working? I had a device where no matter what I couldn't get the pc to recognize it. What worked for me was to go to update drivers, then right below the area where you can browes for drivers is an area where you can choose drivers from a list on your computer. Go there and look for the android adb interface driver
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Do you get the yellow exclamation mark in device manager on the port not working? I had a device where no matter what I couldn't get the pc to recognize it. What worked for me was to go to update drivers, then right below the area where you can browes for drivers is an area where you can choose drivers from a list on your computer. Go there and look for the android adb interface driver
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, It shows as
Android Device > Android Composite ADB Interface.
Pure_Android said:
No, It shows as
Android Device > Android Composite ADB Interface.
Click to expand...
Click to collapse
Your drivers are set up correctly then. Have you authorized adb debugging in developer options?
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Your drivers are set up correctly then. Have you authorized adb debugging in developer options?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I have USB Debugging enabled, I have unknown sources enabled, I even tried revoking the permissions to try and get the RSA certification but no luck
Pure_Android said:
Yes, I have USB Debugging enabled, I have unknown sources enabled, I even tried revoking the permissions to try and get the RSA certification but no luck
Click to expand...
Click to collapse
Can you access the files on your phone from the pc? Are you on a custom Rom that may default to accepting the rsa?
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
Can you access the files on your phone from the pc? Are you on a custom Rom that may default to accepting the rsa?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I can access files, and no I am on stock, I'm attemting to root but this is whats blocking me from doing so
Pure_Android said:
Yes, I can access files, and no I am on stock, I'm attemting to root but this is whats blocking me from doing so
Click to expand...
Click to collapse
If you can copy files to the phone from the pc, just copy the super su zip to your phone. Then flash it in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Help!
jd1639 said:
If you can copy files to the phone from the pc, just copy the super su zip to your phone. Then flash it in a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The problem is, I have no root access, therefore it is till normal android. I need adb to root
Pure_Android said:
The problem is, I have no root access, therefore it is till normal android. I need adb to root
Click to expand...
Click to collapse
You don't need adb to root. Can you copy files to your phone? If so, copy supers.zip to /sdcard/download. Then get a twrp.img file and you'll flash that in fastboot.
See this http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5 using XDA Free mobile app
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse
Delete the device in device manager and then let it find it again.
Sent from my Nexus 5 using XDA Free mobile app
Thanks
If you mean to uninstall it, then I did it couple of times, and now again when the device was disconnected. Then I reconnected the device to the USB port, and scanned the deice manager for changes.
I got the same result - see attachement.
Delete then reboot both devices. Connect phone again. If same, delete device and reboot phone whilst still connected
If that fails, delete and use "universal naked driver"
Sent from my Nexus 5 using Tapatalk
dushkin said:
If you mean to uninstall it, then I did it couple of times, and now again when the device was disconnected. Then I reconnected the device to the USB port, and scanned the deice manager for changes.
I got the same result - see attachement.
Click to expand...
Click to collapse
Never seen that before. Your drivers obviously aren't set up right. Google 15 second adb drivers xda and use that to install the drivers. It'll also set up adb/fastboot which you may or may not need. It gives you the option
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Never seen that before. Your drivers obviously aren't set up right. Google 15 second adb drivers xda and use that to install the drivers. It'll also set up adb/fastboot which you may or may not need. It gives you the option
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No need google.. Section 1b of the resources thread in my signature
Sent from my Nexus 5 using Tapatalk
Are you trying to use ADB mode? If so, and it's not recognizing the device, try using ADB Driver Installer. It worked for me.
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse
I had a similar issue. In order to get my Windows 7 laptop to recognize my N5, I first turned off USB Degugging then connected my N5 to the laptop. Then it showed up.
Sent from my SPH-L720
optimummind said:
I had a similar issue. In order to get my Windows 7 laptop to recognize my N5, I first turned off USB Degugging then connected my N5 to the laptop. Then it showed up.
Sent from my SPH-L720
Click to expand...
Click to collapse
It's supposed to work fine even with it on, at least it did when I had it on. Tested on Win 7, 8, 8.1 and 8.1U1 lol. I never had any issues with USB ever.
Or use Linux, it'll work right away..
It's not set to Camera (PTP) instead of Media Device (MTP) ?
Case Status
Guys.
Thank you all for your kind help.
I tried at least most of your advises - but there were no joy...
I think that the best I should do now is somehow clean up my system from old drivers and related installations.
So, taking aside the option of reinstalling windows, can you share with me some procedures that will enable me to get rid of all old drivers and files and to reach a state of a clean system, so I can then start reinstalling the drivers again?
Thanks a lot!
Well... here is the solution!!!!
https://www.topnotchtablets.com/FixUSBproblems
dushkin said:
Guys.
Thank you all for your kind help.
I tried at least most of your advises - but there were no joy...
I think that the best I should do now is somehow clean up my system from old drivers and related installations.
So, taking aside the option of reinstalling windows, can you share with me some procedures that will enable me to get rid of all old drivers and files and to reach a state of a clean system, so I can then start reinstalling the drivers again?
Thanks a lot!
Click to expand...
Click to collapse
I have similar problems, and as many times as ive tried to uninstall and reinstall i cannot access it from my 1 laptop. However, another laptop connects fine to it- even though i used the same drivers on both laptops. thats the only way i was able to get it to work for me.
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse