Nexus 5 Win8 MTP mode can not find the solution of the disk

Hmm, finally still want Nexus 5, @sofish his brother opened the new Android store. Yesterday afternoon, I decided to get it at noon today: Nexus 5 32G US version, Huo Huo

Then, after more than a year, Note2 was LP “ confiscated & rdquo; … … (even and just bought Like the new machine, how much I care for my equipment.)

Then I came across the RT problem: In the UnLock and Root process, I connected the computer
in PTP mode to be ADB. Identified, "My Computer
" also recognizes the Nexus 5 camera. Switching to MTP mode will not find the media disk, so I can't copy my data to the phone. Although WIFI can also copy, but slow, a few G will take a long time ……

put G Search, tried several methods, and later found a solution under XP system can also be used under Win8, record as follows, the same problem of oil can be solved according to the test:

0. Status: USB connection Win8, MTP mode does not recognize the disk, PTP mode can recognize Nexus 51. After connection, Win8's "Device Manager" recognizes Samsung Android Phone > Google Nexus ADB Interface (How can it be Samsung Android Phone? Because I I have already received Note 2, but not the MTP device 2. Right click on the "Google Nexus ADB Interface" > Properties > details, you will see something like: USB\\VID_XXXX&PID_OOOO, note XXXX and OOOO3. Open C:\\windows\\inf\\wpdmtp.inf (if you don't find it, set the folder option to show hidden files, the basic Windows
operation does not elaborate) 4. (Win8 64) Such [Generic.NTamd64] is added below: note that the XXXX, OOOO corresponding to the above is replaced by %GenericMTP.DeviceDesc%=MTP, USB\\VID_XXXX&PID_YYYY and then saved and exited. 5. Go back to the device manager and right click on “ Google Nexus ADB Interface”, select “Update Drivers> Browse Computers to Find Driver Software(R) > Select > Select MTP> from the list of device drivers on your computer, and click Next to update. Br>

2014.3.14 23:56 Added: Just reconnected to Nexus 5, and could not be recognized as MTP, changed back to Samsung Android Phone > Google Nexus ADB Interface, after various toss, found Universal Adb Driver This driver causes the MTP device to be unrecognized. After uninstalling Universal Adb Driver and reconnecting to Nexus 5, it recognizes MTP and automatically installs the driver. It is also recognized as Android Device > Google Nexus ADB Interface in Device Manager, and it also shows “Convenient devices> Nexus 5” So in the end, "the culprit" should be caused by a driver conflict. The above method may be used temporarily.

Since playing Android mobile phone, for the first time, I have Google pro son … … this is not so much tossing, and various ROM resources are great (I thought that my Note2 is LTE version, each Variety of ROM)