I cannot get ADB to recognize my Note 7. I've installed the ADB & FastBoot 15-second install from the XDA forum, but when I plug my N7 into the PC it only recognizes it as a USB drive.
Dev options enabled,
USB Debugging enabled
USB configuration (MTP mode)
The only entries under Other in Device Manager are CDC and MTP, no Android Device. The phone is also listed under Portable Devices. No USB mode brings up "Android" in the list of devices under Other.
Does anyone have any suggestions?
Do you have proper Samsung usb drivers installed? Check your device manager, just asking sometimes phones can be finicky when trying to get the PC to recognize devices.
Thanks carelockh! That did the trick. I looked in Device Manager and found that only the Windows USB device driver was installed. I downloaded and installed the Samsung driver and was able to connect over ADB.
No problem, anytime glad I could help.
Related
I just turned my nexus 7 32GB on and connected it to the same cable as the 16GB I just returned. It doesn't show up on my computer at all in MTP mode. Only in PTP mode. Any ideas on what to try?
*EDIT*
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
*RESOLUTION*
I uninstalled the ADB driver while it was plugged in with MTP mode. I unplugged it and replugged it and now it works fine.
is usb debugging on?
i got drivers from asus site.
deleted all references to N7 and rebooted windows.
un checked debugging on N7.
went to storage and checked mtp.
connected to windows.
when windows wants to install new MTP device, pointed it to the usb_driver folder..
windows installed MTP device..
this all happened to me today.. i am brand new for this device and the N7 board.
i spose this is fine for me but i would still like to see MyComputer show as USB mass storage..
i feel like the MTP doesnt show everything , limiting my access / control..
i would like to know how to do this,
thanx
akusokuzan said:
is usb debugging on?
Click to expand...
Click to collapse
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
jptech said:
USB debugging is not on. Tried to install the asus drivers and got an error about there not being a driver for 64-bit in them, despite seeing the x64 drivers in the package.
Also, as MTP, my nexus 7 shows up as VID_18D1&PID_4E41&REV_9999
Again, that's with USB debugging disabled, it shows up only as an ADB device.
Click to expand...
Click to collapse
you didn't uninstall all references to adb first. even if you have to go back to a restore point. then start over for Windows to install as mtp
I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse
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.
Well I started having this wierd problem.
When i connect my nexus 4, in mtp mode, i dont get the yellow device logo at the device manager window.
All i get is adb installed.
as a result i cant transfer files from my pc...
Although i could install a custom rom via a toolkit, i cannot transfer files...
any help would be appreciated
thanx
You are in USB Debugging mode, which require a different driver than with it disable. You can try uninstalling the driver (check the box to also delete the driver file), then reinstall it using Universal Naked Driver (link below), or Google USB driver.
If that don't work, try disabling USB debugging.
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.