[Q] ADB will not connect to new nexus 7 - Nexus 7 Q&A, Help & Troubleshooting

I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.

theaftermath said:
I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.
Click to expand...
Click to collapse
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.

A possible solution.
aircooledbusses said:
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.
Click to expand...
Click to collapse
I forgot I made this thread. I have since since solved the issue and have both mtp and adb at the same time with this particular nexus 7.
First of all installing new drivers on my windows 7 installation was causing a problem. So I backed up and reinstalled. However, while that solved other problems it did not solve my issues with the Nexus.
After a lot of fiddling I finally got it to work by using the official google usb driver. http://developer.android.com/sdk/win-usb.html
Now here's the thing. I discovered that windows treated each combination of adb+mtp or adb+ptp, adb alone, mtp alone, and ptp as a seperate device. So while they all might use the same driver windows considered them different devices.
So basically what I did was install google's driver whenever a combination of usb modes did not work correctly. So in adb+mtp (which is what I really want to be able to use) I went to device manager found my nexus 7 under android devices or whatever it is called and installed the the official google driver. It proceeded to tell me there was an error but then it proceeded to work perfectly. The error may have been just my computer acting up because of all the drivers I'd been installing/uninstalling trying to get this to work.
Also, when you go into device manager and try to install the usb driver you typically right click on the device, select update driver and then click search computer, browse to the folder containing the driver and install. Sometimes that would fail for me, windows would say I already had an updated driver. Thankfully I did find a workaround that forces windows to install the driver you want to install no matter what.
When you get to the part where you browse your computer for the driver click let me pick from a list of device drivers on my computer. Then there should be a button that says I have the disk. Click on that browse to the folder with drivers, say yes to any warnings and continue.
If the I have a disk button does not appear and instead a list of possible manufacturers or devices shows up just click on one of the entries. Then the I have the disk button should appear.
The danger with forcing windows to install the driver you want is that you can install any driver for anything and possibly damage something.
Hope this helps!

Related

Can't Get Debugging To Work On Nexus 7

I'm trying to run my app while debugging on my Nexus 7, but it always loads in the AVDs instead of on the tablet.
Here's my checklist of things I've done:
Went into the settings on the Nexus 7 and enabled USB Debugging.
Installed the official ASUS Nexus 7 drivers. When I connect it to my PC, Windows 7 64 bit pops up and says the Nexus 7 is connected and the drivers loaded successfully.
Connected it to my PC (Windows 7 64 bit) and it pops up and saying the Nexus 7 is connected and the drivers loaded successfully.
However Eclipse doesn't detect it at all. The app loads the AVD instead of it. And if I go to Run As->Run Configurations->Target, it's not listed. If I select Launch on all Compatible Devices/AVDs and choose Active Devices and then try to run, I get the error "No active compatible AVD's or devices found. Relaunch this configuration after connecting a device or starting an AVD".
The app is set to be compatible with Android 4.1.
Suggestions?
The only way I've ever gotten it to work is switching the 7 from a media device to a camera.
NJGSII said:
The only way I've ever gotten it to work is switching the 7 from a media device to a camera.
Click to expand...
Click to collapse
Strange. Unfortunately it still doesn't work for me. Same symptoms. Thanks though! Any other ideas?
I found I had to fiddle with the drivers a bit to get the proper adb connection. Check Device Manager and make sure it shows up under Android Phone->Android ADB Interface. If you see anything else you'll need to uninstall the offending driver and reinstall.
charlesky said:
I found I had to fiddle with the drivers a bit to get the proper adb connection. Check Device Manager and make sure it shows up under Android Phone->Android ADB Interface. If you see anything else you'll need to uninstall the offending driver and reinstall.
Click to expand...
Click to collapse
Ehhh...Crap. You're right. Device Manager shows Other Devices -> Nexus with a caution sign on it. Weird cause when I plug it in it'll ask me if I want to transfer photos and it'll mount it as a drive and everything....grrrrrr. This might be annoying.
I'm trying to remember exactly what I did to get the right driver to install. I think you need to uninstall the all drivers being used and then make sure that USB debugging is turned on in the Nexus before plugging it back in. I used the Wugfresh toolkit which includes tools to check what drivers are lurking around in your system.
Finally got it. Turned out, the driver files were no good. I got them from a link to Asus's site from another thread. I googled their site for different driver files and found the correct ones:
http://www.asus.com/Tablet/Nexus/Nexus_7/#download
It should be a zip file with USB in the title.
Thanks for the help!
MSmithXDA said:
Finally got it. Turned out, the driver files were no good. I got them from a link to Asus's site from another thread. I googled their site for different driver files and found the correct ones:
It should be a zip file with USB in the title.
Thanks for the help!
Click to expand...
Click to collapse
I can confirm this, I switched it from MTP to PTP and installed the driver, and everything is working now. It's showing up in the ADB list.
Cant Get Drivers & Root Wont Work. PLEASE HELP
hey ive tried to root my devices for years and keep coming across the stupidest roadblock. i cant get the right drivers ever. it never finds them and i download them directly from the manufacter and it still wont work. i couldnt root my galaxy nexus because of this and now i cant root my nexus 7 because of this please help and let me know how to do this properly. i cant find any videos and know of no one who is having this issue except for my friend which also couldnt get the drivers for his galaxy nexus either....:crying:
_grayfox said:
hey ive tried to root my devices for years and keep coming across the stupidest roadblock. i cant get the right drivers ever. it never finds them and i download them directly from the manufacter and it still wont work. i couldnt root my galaxy nexus because of this and now i cant root my nexus 7 because of this please help and let me know how to do this properly. i cant find any videos and know of no one who is having this issue except for my friend which also couldnt get the drivers for his galaxy nexus either....:crying:
Click to expand...
Click to collapse
Download the asus drivers and extract the zip file. Plug in your Nexus 7. Go to Device Manager -> the device (might be listed as an android device) -> Update driver. Browse to the extracted folder.
On the Nexus 7, make sure USB debugging is enabled. And, when it connects, change it from being connected as a media device to instead being a camera device.
Thanks. I ended up being able to do it with the one click root program it helped me get the drivers super happy. Now my galaxy nexus and nexus 7 are rooted. Haven't had something rooted since my Samsung galaxy s fascinate
Sent from my Nexus 7 using xda app-developers app
Not working.. UGH!
MSmithXDA said:
Download the asus drivers and extract the zip file. Plug in your Nexus 7. Go to Device Manager -> the device (might be listed as an android device) -> Update driver. Browse to the extracted folder.
On the Nexus 7, make sure USB debugging is enabled. And, when it connects, change it from being connected as a media device to instead being a camera device.
Click to expand...
Click to collapse
Been at this fir 3 days. Installed, uninstalled drivers. Got ASUS drivers. Switched from Debugging on to off, then off to on. used Camera, used Media....The closest I come to seeing Nexus7 in Explorer or Computer is INTERNAL STORAGE/DCIM OR CAMERA.
I am unable to see any files, no matter what I do. So, now I must ask this: Must I be rooted to see android files? I doubt it, but I never used a Nexus before. Quite frankly, this tablet is awful for use with a PC. I need help-can u help me, pls.
MSmithXDA said:
Download the asus drivers and extract the zip file. Plug in your Nexus 7. Go to Device Manager -> the device (might be listed as an android device) -> Update driver. Browse to the extracted folder.
On the Nexus 7, make sure USB debugging is enabled. And, when it connects, change it from being connected as a media device to instead being a camera device.
Click to expand...
Click to collapse
Can I ask for your help guys? My Nexus 7 v1 is stuck on boot loop (either stuck on google screen or sometimes would proceed up to the nexus animation screen) and I've been trying to fix it with the Nexus Root Toolkit (NRT). I just have problem proceeding with the steps since the toolkit advices me to enable my device's USB DEBUGGING (open device , go to settings, then developer options etc) which I CANNOT POSSIBLY DO COS AGAIN, NEXUS IS JUST STUCKED ON BOOT LOOP.
Can you suggest OTHER ways I can enable USB Debugging in Nexus 7? I would greatly appreciate your help.

Nexus 4 ADB Connection

I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
akashi said:
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
heat361 said:
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
Click to expand...
Click to collapse
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
Click to expand...
Click to collapse
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
heat361 said:
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
Click to expand...
Click to collapse
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
Try pointing the path to the Google drivers in the android-sdk in device manager and not the naked drivers.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
This is what I did and waited for the PC to install the adb drivers.
I plugged the phone in and with the USB plugged in turned it off while holding the volume up and down keys. This made my nexus 4 go into download mode and the PC automatically installed the adb drivers. After I just unplugged and held the power button to restart the device hope this helped.
Sent from my Nexus 4 using xda premium
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
Thanks.
Click to expand...
Click to collapse
When you uninstalled what's there now, you did make sure to check the box that will remove the old drivers from your PC?
Just in case, HERE is another source for the drivers.
dinhume echoes
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
akashi said:
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
Click to expand...
Click to collapse
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
El Daddy said:
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks. I tried version 16.01 and still have this problem.
The problem is whenever I uninstall/install the ADB driver or disconnect/reconnect the USB, **ONLY** the "Nexus 4" appears on the Device Manager which I manually install the ADB drivers to. There is not a second "Nexus 4" on the Device Manager for the MTP or PTP.
On my laptop when I remove all drivers and reconnect the USB cable, I always see 2 "Nexus 4" listed on Device Manager. One for the ADB interface and the other for the MTP or PTP.
Please help!
Any ideas please?
Any Solution to ADB connection problems?
Hi was there any solution to this, as I seem to have the same issue.
I have tried different drivers and MTP & PPP modes as well as loading the PDAnet drivers and software.
Each time now I take care to remove all the drivers and also delete the drivers in all modes (Android running and Bootloader running)!
MTP & PPP load different copies of the drivers.
I can get either "Nexus 4" showing up in the device driver or "Google ADB Interface" or Android ADB interface" according to the driver loaded.
I can see the device when Android is running ie "ABD Devices" gives me the serial number and connected, then I can send an ADB command "adb Reboot-bootloader" the Nexus then reboots into the bootloader screen, the device driver changes to the bootloader driver (installs if not installed) however then I loose connection to the Nexus phone! "ADB Devices" returns none connected.:fingers-crossed:
I also tried unplugging and plugging back in the phone in bootloader mode but do not get adb to see the handset or it to react to commands.
I'm just about ready to try a toolkit to see if I can get past this roadblock!!!
Current computer is Win7-x64
This weekend I will try on a different computer.....Win8-X64
All comments appreciated
That's because you cant use adb when in boot loader. You use fastboot
Sent from my Nexus 4 using xda app-developers app
I have same problem on my work laptop DELL when my custom desktop machine works just fine with both Nexus 4 and 7. :/

[Q] Nexus 7 USB connectivity to Windows XP SP3

Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
o82239 said:
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Sent from my Nexus 7 using xda app-developers app
:-/
Is there any justice for me in this bad bad world of octa-core processors and Razer Edge!!! :'(
ansh360 said:
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
Click to expand...
Click to collapse
??? It worked and it doesn't work ???
What worked?
Try to delete the precompiled inf-file 'C:\WINDOWS\inf\wpdmtp.pnf', edit the 'C:\WINDOWS\inf\wpdmtp.inf' (see link in the post in the top...), open the XP device-manager, right-click in the yellow '!' and 'update driver'...
twics said:
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Click to expand...
Click to collapse
Do you have edit the 'C:\WINDOWS\inf\wpdmtp.inf'?
Sent from my Nexus 7 using xda app-developers app
I had a lot of problems myself getting Windows XP to work with my Nexus 7 as well... eventually I discovered that installing the latest version of Windows Media Player fixed the problem.
I wrote up a post on this issue on another forum (Sorry, XDA - this was before I discovered you guys), back in December of last year.
Anyway, here is my original post...
http://www.nexus7nexus10.com/forum/nexus-7-help/2600-cannot-connect-pc-2.html#post36608
(Actually, this whole thread is worth reading.)
The only nuisance factor is having to remember to re-enable USB debugging (Titanium Backup needs USB debugging enabled, and complains if itsn't) AFTER I've run some MTP Windows XP related file backups (USB debugging needs to be disabled, or MTP won't work)...
....or at least that is my experience.
Hope this is of some use.
Rgrds,
Ged.
Hello guys,
I have the same issue on windows XP with Nexus 7. I tried everything what was suggested and nothing is working.
I have Windows XP SP3 with WMP11 and MTP porting kit installed as well. the device is recognized and driver is instaled fine. But it's not visible on "my computer" in MTP mode. I tried to turn on usb debugging and still device is invisible in windows explorer, the same is when usb debugging is turoned off.
When device is in PTP mode it appears in "my computer" and i'm able to browse it and see all pictures and photos.
How can i browse my device in MTP mode and copy files there? Please reply if anybody knows what to do to fix this issue.
Thank you.
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Taowtp said:
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Click to expand...
Click to collapse
The above workaround was spot on, thanks

[Q] Adb sideload nexus 10 not recognized

My tablet is in developer mode, USB data bugging is clicked on. In storage, MTP is clicked on. Using the latest Android SDK along with the latest Google Win USB drivers (also different cables, different ports, uninstalled and reinstalled all drivers and software, turned on and off debug, debug authorization.. Just about everything I can think of.) Also, no, not rooted, fully stock. Been searching for a few days for this problem that occurs while trying to upgrade to Kit Kat 4.4 from JWR66Y 4.3 on my nexus 10.
Plug in my n10 normally and WIN7 will see it in the device manager as Android Device, Android Composite ADB Interface, Hardware Ids =
USB\VID_18D1&PID_4EE2&REV_0226&MI_01
USB\VID_18D1&PID_4EE2&MI_01
Boot the n10 into recovery and the adb sideload, the n10 shows everything correctly and waits for the adb sideload file. CONNECT THE USB cable and Win7 does not recognize the device. Tries to find a driver for 'other devices, nexus 10' but eventually returns with no driver found. Tried installing from specific directories (new google usb driver download), letting it search windows update evewn search my entire hd. It cannot locate a driver. Device manager shows an entirely different Hardware Id for 'other devices, Nexus 10' =
HARDWARE IDS (OTHER DEVICES, NEXUS 10)
USB\VID_18D1&PID_D001&REV_0226
USB\VID_18D1&PID_D001
I did a search with this information and found others had this ID/problem with their Nexus 7 during the Jelley Bean upgrade!
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
There is no Nexus 10 in this file, but the second line of 'google nexus (generic)' list the ID that I have when booting normally.
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
I assume that if I replace this number with the ID I see in adb sideload mode (USB\VID_18D1&PID_D001) I should be able to install the correct USB and ADB drivers as others did on their n7 (shown in that link)?
My problem is identical to tbe description on that link, but I am guessing at the fix for the n10. This sounds like the solution to me, but I am also worried if it could be a sign of a bigger broblem or might brick my nexus. So any help would be appreciated!
Thanks all!
Ed
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Duplicate deleted
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Wow, I hope someone finds this thread and it saves them the headaches and searches I have been through. Worked just like you said, installed this adb usb driver and it picked it right up. I wonder why google couldn't get the google driver to read their own nexus 10 tablet!
Now running Kitkat 4.4 with no data loss, thanks to you Kira!
Thank you!
Ed
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Thank you, been banging my head around to try and find a fix, worked like a charm for sideloading KitKat.
cheers
Oh my god, pushing this thread because I almost needed 6 hours to root my Nexus 10 with other ADB drivers but this one worked!

[Q] USB Issues with Windows 8.1

put in a new SSD and got Windows 8.1, did a fresh install on a new hard-drive, everything's been working great, My nexus 4 has worked with with ADB./Fastboot and I've been able to transfer files to and from it in MTP mode. Been like that for about 4 days until about 3 hours ago, I had Windows Explorer crash, had to run Task Manager, end the process, and then manually restart explorer.exe My device was plugged in when this happened, and afterwards, I noticed that I could no longer see my Nexus 4 under the Devices & Drives section of "This Computer" (My Computer had a better ring to it lol) First I tried rebooting both my laptop and my Nexus 4, then I tried uninstalled the drivers, rebooting, re-installing, and then rebooting again. Did that like 4 times now, each time re-downloading the drivers, and doing an MD5 hash to create a Checksum, and checking them each time. Also to no avail. ADB shows my device serial number when i enter : ADB Devices, but says it's unauthorized, so if I try anything like: ADB Reboot Bootloader, it says Device is not authorized.
So ! I don't understand wtf is going on. Was working fine before. The drivers are up to date, I just flashed the Official OTA image, and was on the leaked image prior to that. Then earlier this evening I switched to the newest version of the Nexus 5 Port, and everything was still working fine, hadn't made any changes in a couple hours before this happened. When I install the drivers, It acts like it worked. Instead of saying "NEXUS 4" under Other Devices in my Device Manager, it says Composite ADB Interface under Android Devices and MTP under Portable Devices. Sometimes tho the MTP entry will still show the Yellow Exclamation Point. But goes away. Don't know whats up with that either.
Also, it wont let me install drivers unless I am in MTP mode, which Usually you can install them regardless (tho I never tried in Camera mode, I am just assuming about that one) Usually I install drivers without MTP or Camera modes checked, but now if I try it, it says that Windows Cant find the Drivers, even tho I am obviously browsing for them myself and selecting them. And just now I tried updating instead of re-installing them, and it keeps saying that Windows has determined they are the most up to date.
So I am out of I ideas. I even updated windows media player cause that's what fixed my issue on Day 1 of running Windows 8.1 when it wouldn't recognize it at all. So I don't know. Sorry for the long post but I wanted to make sure I got everything in there so hopefully someone can narrow down what the issue is. Cause I've been at it for 3 hours, haven't slept yet, my Nexus 5 gets here today, and I need to get this fixed before I sell it to my buddy. Its brand new, only 15 days old.*
Any thoughts ?*
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
ADB Devices, but says it's unauthorized
Click to expand...
Click to collapse
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
eksasol said:
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
Click to expand...
Click to collapse
ok I am gonna try that now. And as far as the part about my phone being unauthorized. I already knew about the notification that pops up, i was waiting for it to happen. Never did tho. Maybe it will happen after I do the rest of what you said. thanks, i will post my results in a min
no matter what i do, i cant get MTP working. When i uninstall the ADB entry in Device Manager it gives me the check-box option for removing drivers as well, but not on MTP. And now it wont even give me the option to uninstall, update, or anything at all, even tho I uninstalled it already so it should at least give me the option to install drivers. Even tho it's showing up in Device Manager as a Portable device, if I look in Printers and Devices, it shows up as unspecified device. Disabled USB Debugging, and all that. it says its working but it wont show up in My Computer>Devices and Drives still. For some reason ever once in awhile it will pop up with the Yellow Exclamation Point tho, only for a brief second tho. other then that, its shows it like it's running correctly. Also, nothing pops up saying that windows is installing drivers when i plug it in. Which in Win 7, XP, etc, it always did. Does this not happen in Windows 8.1 ?
Also, under Driver Details, which is the only option it lets me click on MTP, it says the drivers are from 2006 lol
Update - Just reinstalled the drivers for ADB and enabled USB Debugging, and everything is still saying its working even tho its not. But when I take my phone out of MTP mode it shows up in device manager under "Other Devices" as Nexus4, with a Yellow Exclamation, and it gives me the option to update drivers, so i tried, but it says Windows Can't find my driver. This is very frustrating.
Had this problem aswell, which was caused by the N version of Windows 8 versions.
These versions dont have Windows Media Player istalled, which is needed for MTP to work.
So to fix your problem you need to download that latest Windows Media Player (WMP) from microsoft and install that.
I dont have the N version, I have WMP installed, i mentioend your fix in the OP. Had to update it, and it worked. It was working fine for the last few days, then it stopped working suddenly
double post, sorry. dont know why that happened.
Vouch. Since I use win8.1 (no n version) Mtp doesnt work. I tried all known drivers, disabled driver signature and so on. The only working combination for me is Usb Debugging + PTP. Then I use file manager to cut the files. Airdroid would be an alternative as well.
update - SOLVED * Kind of.....I say kind of cause I still don't know what caused it but apparently Flashing to the Nexus 5 Port fixed the issue lol. I am assuming something pertaining to the way USB connectivity is controlled by Android got corrupted, and a fresh install was in order. Whatever it was, it worked and i am back in business. thanks to all those who attempted to help.
Sent From My Nexus 4 via XDA Premium 4

Categories

Resources