I have a Nexus 7 that used to be able to be seen (and trnasfer files) on my Win 7 64-bit Ultimate pc. It is not visible in Explorer now- think it happened after upgrade to 4.2.2
I have tried various ways and means from this site and others but still unsuccessful. My pc kept wanting to install MTP USB drivers everytime I plug the N7 into it even when I have it set as PTP; and the drivers always failed.
I downloaded the Universal naked Drivers and tried to install it as well but problem is that my device only show up as MTP USB (under portable devices) instead of as N7; and under that the drivers is always the failed MTP USB drivers. I cannot browse to install Universal Drivers here cos the pc will not accept it.
Really running out of my wits. Any advises please?
Thanks.
I had initial problems connecting to my pc after installing all the drivers from a toolkit. After searching, I followed a tip and installed pdanet on my phone and pdanet for android on my pc. Now I connect exactly like my phone or other storage with full access to the user storage on the n7 from the pc. Win 7 pro 64bit.
Related
I'm having an issue connecting GT to windows 7 via adb. Device manager doesn't recognize the GT. I need a little help finding the drivers.
Thanx
install android sdk, run sdk manager, and choose Google. Usb driver package, Samsung drivers.
Roadk1ng said:
I'm having an issue connecting GT to windows 7 via adb. Device manager doesn't recognize the GT. I need a little help finding the drivers.
Thanx
Click to expand...
Click to collapse
I had initial difficulties connecting via ADB. Did not see my device.
I had the USB drivers installed for my Fascinate phone, so I could mount the TAB as normal, just not recognized by ADB. When I downloaded and tried to re-install the USB drivers, PC said already installed. So, I simply re-installed the new download over the old drivers, ADB immediately recognized the TAB device.
So, Fascinate USB drivers were close but not quite complete for my Tab device.
YMMV
Hi,
Trying to get my Nexus 7 connected to my laptop running Windows XP (32bit), SP3, to allow me to root it.
I've downloaded the Nexus Root Toolkit and I've tried installing all the different drivers from there (USB Debugging is OK), and even the Samsung drivers.
Every time, I get a error on the android ADB interface (can't install). I can't post a picture yet (need 10 posts on here), but I get the following in device manager:
Android Device
Nexus (!)
Other Devices
MTP (!)
Any ideas where I'm going wrong? I think I've read somewhere that XP is difficult to get communicating.
Cheers.
Oh, and it tries to install wdtCoinstaller01007 as standard for a driver.
Have also tried *01009
I have the same problem.
I guess the MTP while in debugging mode is not important
Last night I finally decided to use Wugs Nexus Root Toolkit to unlock the bootloader, root the device, flash CWM recovery and installed SlimBean ROM. It was somewhat of a pain to get adb to work at first, it had me uninstall drivers off my PC. Now when connecting my tablet to my PC, PC is not letting me view the internal SD card, nothing comes up. I've tried connecting it to another Windows 7 PC, same issue. Wondering if its something with the ROM, anyone else had this problem? What's the solution.
Uninstall USB ADB Driver
I had the same problem. What ended up working was re-connecting the tablets via USB to my Windows 7 machine. Open up Device Manager and find Nexus 7, right-click on it and select Uninstall (this removes the ADB drivers that were used to root, etc). Then disconnect the USB cable and reconnect it. Then it should automatically reinstall the USB drivers for MTP access. Hope that helps.
That's actually what I had to do to get Root Toolbox to work....or so it said.. I'm surprised though, if I hook it up to another PC why that PC wouldn't automatically try to install the driver.. If I have it with USB debugging off, it doesn't show in the display manager, if I enable USB debugging it does. Tried uninstall, disconnect, reconnect USB cable, same issue.
Check your USB Connection settings for MTP yet?
Thank you. Didn't know where that was at first. Went to settings:storage:menu icon:USB connection settings: checked MTP. now my PC is detecting the N7.
I have a nexus 7 2012 and i am trying to install 4.3. Of course since i have rooted it and have twrp on it i cant just ota update, so i tried plugging it up to my computer. Right now everytime i plug in the device and use it as a media device it works until i turn on developer mode and enable usb debugging. As soon as i turn on debugging the device disconnects at the bottom right showing my N7 (on windows 7), and whenever i look in my computer its not there also. The only way i can find it in this mode is in device manager in which it says "android phone". I figured maybe i have a driver problem, but if you look for drivers and try to install it says it already has them.
So does anybody know how to get it to work so i can reset it?
Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
Delete the current drivers than manually choose the n7 drivers you downloaded from xda.
Or use a free program called usbdeview for windows to seek out all drivers associated with a device to make sure you uninstalled them correctly. Also I highly recommend dual booting a Linux distro which is much less finicky than windows when using android
Best of puck
Sent from my Nexus 7 using Tapatalk 2[/Q
Can you inform me on how to delete the current drivers?
when i connect with usb debugging mode turned on it connects as nexus 7 with a description as Android Composite ADB Interface. Also it is not recognized under the my computer setting at all. In usb deview it also has a purple dot all the way to the left beside the name instead of a green dot.
When i connect to the pc without usb debugging on the computer recognizes it as nexus 7 \ media device and i can use it as storage back and forth and in usb deview it has a green dot beside the name
Click to expand...
Click to collapse
So i finally got around to setting up my laptop anew, and i ran into a little snag. I've installed the Motorola device manager 2.5.4.
My XT1562 is not correctly installed as such when connected... (yes, in PTP mode, adb enabled too)
The phone knows it is connected by USB and charges, it works fine on other PCs
Reinstalled Device Manager, nope
Trying different USB port didn't help
Tried different USB cable for the heck of it
Device Manager shows Android Device "Motorola ADB interface" and one unknown "MTP".
Device shows:
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
Using the auto update for drivers doesn't work. Manually Specifying the folder for the Motorola Device Manager doesn't work, i checked, there are no drivers lying around in there...
To manually specify the driver i would have to know exactly which device that thing is supposed to be. Hm actually let me check that on the other PC brb
EDIT:
Well, ive never even installed the motorola device manager on the pc (win7 x64) and it just works. Does have the ADB device as unknown in Device Manager.
If you are using Windows 10 or win 8.1 follow this guide to disable driver signature enforcement
https://www.youtube.com/watch?v=71YAIw7_-kg
For abd drivers
http://adbdriver.com/downloads/
Then reinstall Moto device manager
I've had them installed with signatures before (It was Win10 x64 before too) no problem. Did they mess that up? Thanks ill try it
EDIT
Didn't work. Rebooted with sigs off, reinstalled 2.5.4, no difference
EDIT2: There was no driver signature warning either
Riiight, after some tinkering (including a driver backup from w7 and restore to w10 solution) i figured out the actual problem. I've installed Windows 10 N, and the optional media pack is required for these drivers to work. Go figure.