• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

USB not working

When I connect my phone to my lap or PC using the provided wire it's not getting connected instead it's just charging..... I can't open my phone in my lap neither transfer files need help please......:confused::mad:
 
Try a different USB port/cable - and also check if you have the appropriate drivers installed - see more here
 
When I connect my phone to my lap or PC using the provided wire it's not getting connected instead it's just charging..... I can't open my phone in my lap neither transfer files need help please......:confused::mad:

I assume you are not talking about ADB drivers (see the link in the answer above this one for that) but rather using an MTP connection to view your internal memory from Windows Explorer and transfer files.

What happens when you plug the phone in. Anything? Any dialog box pop up? Autorun box? If you go to device manager while the phone is plugged in, do you get an item with a yellow triangle?

If you get the device with a yellow triangle, try this (from another thread where I posted this but got no feedback if it worked ;) ):

Plug the Nexus 5 into your computer with USB. (I am going by my experience with Win 7). When you get the device with a yellow triangle, select it and do "update driver." Choose "browse my computer" then "Let Me Pick From A List Of Drivers On My computer." It should list a device with "composite" in the name (if it doesn't list MTP). Choose the composite device. It should install and widows should pop up the dialog box for it like you should get when you first connect the USB cable. For me, identified it as a portable device but labels it a Nexus 5. You should then be able to see the Nexus 5 listed in widows explorer and view the internal storage.

Note. This worked for me, but I've seen clear indications that people with different setups seem to have to do different kinds of things. You can also investigate connecting via wifi using apps like airdroid.
 
I assume you are not talking about ADB drivers (see the link in the answer above this one for that) but rather using an MTP connection to view your internal memory from Windows Explorer and transfer files.

The same drivers should work for the MTP connection too.
 
The same drivers should work for the MTP connection too.

No, actually, they are completely different in my experience. Getting ADB working is fairly easy, but they don''t allow Windows Explorer to view internal memory. Windows has to see the device as a portable player (which Windows 7 seems to call a "composite device"). If you installed ADB drivers and were able to use Windows Explorer to view internal memory and transfer files, I would suggest you already had MTP working before you installed the ADB drivers.

That said, it does sometimes seem that no two windows machines does this stuff the same... :rolleyes:
 
Hey I've had this problem too now if I remember correctly got to setting>storage and in the top right corner there should be a menu/options button or 3 vertical dots click on those and there you have it should work if not it's the cable/USB port
 
Hey I've had this problem too now if I remember correctly got to setting>storage and in the top right corner there should be a menu/options button or 3 vertical dots click on those and there you have it should work if not it's the cable/USB port

That simply determines whether the Nexus 5 is going to try to connect by either MTP or PTP. It does not determine whether your Windows Computer will accept the connection. ;)

However, yes, you do want the MTP box checked.
 
Hey I've had this problem too now if I remember correctly got to setting>storage and in the top right corner there should be a menu/options button or 3 vertical dots click on those and there you have it should work if not it's the cable/USB port
This :thumbup:

Make sure you have it setup to connect as a media device.

Try toggling it.
 
Disabled by default you have to manually set it and your welcome

Strange. Mine was enabled by default and toggling it off and back on had no effect either. I had to do the driver thing I described to get it to work with Windows 7.

However, as I warned, I've seen different setups requiring different solutions. This was back when I was unrooted on stock, before I began working with ROMs.
 
Back
Top Bottom