Database Info

[RESOLVED] Charge root problem - adb drivers

Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.

droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Hi - Would really appreciate your help here. Thanks for the tip on turning debugging off to get to the phone so I could install the USB drivers. Problem now is that ADB just refuses to connect to it. It shows up asa disk drive in Devices, but when I do a kill-server then start-server then adb devices, it doesn't list any devices, and an adb shell just says device not found.
Do I need to reboot Windows, or the phone? Seems unlikely. I can open a window to the phone, but can't get access to install the Gingerbreak and su files I need to root it. Going crazy!
Thanks,
Eric

Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App

Black-Falcon said:
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!

Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App

ClarkSt said:
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Click to expand...
Click to collapse
Try downloading busybox from the market, or downloading titanium backup and hit the "problems" button when you open it and select get busy box

Black-Falcon said:
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Tried GingerBreak. No good. "permission denied".

Good idea - I got Busybox installed this way, but still no joy from Gingerbreak.

Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App

DroidXcon said:
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.

ClarkSt said:
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
Click to expand...
Click to collapse
Check the development thread for the Charge. There's a thread on how to rollback to ED1 with root using Odin.
Edit: Direct link: http://forum.xda-developers.com/showthread.php?t=1085190

droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Dude - THANK YOU!!!! I could not get those drivers to install!!!
Please - Stickie!!!

If you want the drivers and don't trust the sources posted anywhere (we're not trustworth ?) you can get them from the phone itself. They are located in the file /system/etc/autorun.iso and you can extract them from it.

[Q] MTP driver issue

Ok i just picked up my 32gb wifi only xoom. whenever i try to install the drivers it finds the files it needs but produces the following error, "A service installation section in this INF is invalid", WTF do i do tried uninstalling the drivers and anything i can think of ive rooted numerous phones before. is this a problem with the xoom itself and should i take it back?

josephparlangeli said:
Ok i just picked up my 32gb wifi only xoom. whenever i try to install the drivers it finds the files it needs but produces the following error, "A service installation section in this INF is invalid", WTF do i do tried uninstalling the drivers and anything i can think of ive rooted numerous phones before. is this a problem with the xoom itself and should i take it back?
Click to expand...
Click to collapse
check to make sure you have windows media 11 or higher on your computer. I had that issue. Running XP I had an issue but Win 7 it installed easily..
This is what I used
Motorola_End_User_Driver_Installation_5.1.0_32bit.msi
MotoHelper_2.0.49_Driver_5.0.0.exe
Windows Media 11
Also search around on google lots of people have had this issue and thats how I found my answer.. Also xoomforums.com is a good site for answers as well

OK so I installed wmp11 and it will recognize my xoom thanks for the tip. however now I cannot get ADB to work my device is there I have every sdk ever made down loaded and I have the moto USB driver mentioned installed but I can't get into a ADB to save my life.
Sent from my Xoom using XDA Premium App

Try un/check/ usb debuging, don't remember witch is correct...
Had this problem with adb...
Sent from my Xoom using XDA Premium App

makokoko said:
Try un/check/ usb debuging, don't remember witch is correct...
Had this problem with adb...
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
usb debugging needs to be checked in order for the adb to work.

Getting ADB access in Android 4.2.2

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.

Workaround for no USB Mass Storage in JB

I didn't know there was a workaround app to enable UMS. How come its not posted in here?
Sent from my XT897 using Tapatalk 4 Beta

How come you didn't post it in here?

http://forum.xda-developers.com/showthread.php?t=2175747
It works photon q. I've been using for my car radio which doesn't support mtp.
Sent from my XT897 using Tapatalk 4 Beta

jae18708 said:
http://forum.xda-developers.com/showthread.php?t=2175747
It works photon q. I've been using for my car radio which doesn't support mtp.
Sent from my XT897 using Tapatalk 4 Beta
Click to expand...
Click to collapse
...for me not tested on win7 .... i will test it tomorrow on xp

CornholioGSM said:
...for me not tested on win7 .... i will test it tomorrow on xp
Click to expand...
Click to collapse
It worked for me on Win7 x64 after some trying - what exactly doesn't work for you, Cornholio?

micx_pl said:
It worked for me on Win7 x64 after some trying - what exactly doesn't work for you, Cornholio?
Click to expand...
Click to collapse
i have in system / hardware error code 10 - device cannot be run

I used to use mass storage mode in Open Recovery.
Sent from my XT897 using Tapatalk 2

Connect your device to the computer in MTP mode, open the USB Mass Storage app and click On.
Thats how ive done it and it has worked fine in Windows 7, Ubuntu, OpenSuse and Fedora.
Sent from my XT897 using Tapatalk 4 Beta

jae18708 said:
Connect your device to the computer in MTP mode, open the USB Mass Storage app and click On.
Thats how ive done it and it has worked fine in Windows 7, Ubuntu, OpenSuse and Fedora.
Sent from my XT897 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This does not work for me, may be because i have an official JB
Win7 x64

i have tested it on XP and Mac and it works

For me it works on stock JB on win7 x64

MiklerGM said:
This does not work for me, may be because i have an official JB
Win7 x64
Click to expand...
Click to collapse
Is your phone rooted?
Sent from my XT897 using Tapatalk 4 Beta

jae18708 said:
Is your phone rooted?
Sent from my XT897 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, my phone is rooted.
I install SuperSU from market, and root start working
i tried to compare a '# mount' output and it is identical
But when i press 'mount' in app, mtp device disappears from my computer. And /mnt/sdcard in my phone still mounted to phone.
Afaik, /mnt/sdcard need to be umounted from phone and mounted to usb
Maybe there is something wrong with my phone cause my phone can't start a wifi tethering, Wifi hotspot works well, but no NAT rules in iptables
I think after unlocking bootloader applications can't execute something in command line

MiklerGM said:
Yes, my phone is rooted.
I install SuperSU from market, and root start working
i tried to compare a '# mount' output and it is identical
But when i press 'mount' in app, mtp device disappears from my computer. And /mnt/sdcard in my phone still mounted to phone.
Afaik, /mnt/sdcard need to be umounted from phone and mounted to usb
Maybe there is something wrong with my phone cause my phone can't start a wifi tethering, Wifi hotspot works well, but no NAT rules in iptables
I think after unlocking bootloader applications can't execute something in command line
Click to expand...
Click to collapse
I cannot keep it working reliably without AFT installed and ready to interfere. On a mac.

There's different between xp and win7. I was upgrade to jb via ota and my notebook (running on xp) didn't read device's mass storage. I decided to try on my bro notebook (running on win7) and you know what,, mass storage ****ing detected. And seperated where your internal and external

[Q] Fail to see my Nexus 5 on Win7

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