I tried connecting it nexus 5 to my pc via USB. Although it shows as connected in my external devices and also shows up in My Computer, but when I try to open it and don't files to my phone, it just shows a plain, blank screen with the green placing had on top.
Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
On your PC, go to your device manager (You can find it in Control Panel, System) when the Phone is plugged in and set to MTP. Locate the phone, (it might come up as "Android Phone" if so open the tree a level. On my computer it says "Google Nexus ADB Interface" but it might be different on yours depending on how you've got things configured) right click on it and chose "properties" from the fly out menu.
Go to the Driver tab
Click Update Driver. . .
Click Browse my Computer for driver software
Click Let my pick from a list of devices on my computer
select USB Composite Device
Close the driver assistant
Your Nexus 5 should now appear as an MTP device on your computer.
I've had a similar problem for some months after over a year of normal operation but with a Nexus 4 Android (now Lollipop) phone and an Acer laptop running Windows 7. The Nexus would not show up in Windows Explorer in MTP mode, only PTP mode. That is ok for moving photos over to my laptop but not for making a backup of Android files, or data such as an exported Contacts list. On revisiting this problem and finding this page I did the following:
- Plug Nexus 4 into laptop (laptop acknowledges the connexion with its sound-effect)
- Go to Control Panel > Devices and Printers and click on Nexus
- Select Hardware, which shows Acer ADB Interface -- this seems to be what was wrong
- Go to Control Panel > Drivers, select Acer ADB Interface and delete it
- Unplug Nexus 4 and plug it in again, Windows goes off to find a driver for it
- Windows then installs a Nexus 4 driver, not the Acer ADB driver, and all is well.
Strangely, the Nexus driver has an earlier date and a lower version number than the Acer ADB driver had, suggesting it had somehow got upgraded. Perhaps I needed the Acer ADB driver for something, but I'll worry about that when I find out what.