Hello Everyone,
----------------------------
Nexus 7 Driver Fail
----------------------------
I was Unable to install drivers on Windows XP (ADB and Fastboot Drivers do not load). Every step has failed and multiple drivers fail to install with Code 18 and 28. I’ve tried just about EVERY Tool Kit available out there and searched fourms, still no positive results. If anyone out there may have an answer please feel free to drop it in here, I greatly appreciate all your help. Thank you.
Here is a list of what I have done thus far:
- Rebooted the computer after uninstalling devices with USB Deview before
continuing on to the other steps
- Uninstalling and manually deleting driver from the registry
- Unplugging and repluging the device while watching
the device manager (The device shows up as other devices, Example: nexus and MTP)
- I tried disabling auto driver configuration by Simply pressing the "Disable Auto Driver Config" button and then
changing the settings accordingly
- Registry cleaning
- Removing and manually adding to windows driver folder
- Trying on different User accounts from Admin to guest
- Used Android SDK manual driver installation
- Unplugged the device and Launched USBDevice
- Used USBDeview to uninstall any;
- Android ADB Interface device's
- Samsung USB devices
- Google USB drivers
- ANYTHING else you see that resembles your Nexus.
- Looked for devices with Vendor ID's:"18d1"or"04e8"
I then right clicked these devices, and selected the option to” Uninstall Selected Devices"
-Downloaded The official Asus USB driver off of Asus actual support base
And it said the following: an error occurred during the installation of this device The Parameter is incorrect.
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
peterk-1 said:
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
Click to expand...
Click to collapse
I tried the same steps.
I even tried using Android SDK, Universal Naked driver
Still no luck
N7 running 4.2.1 stock
After many hours googling and searching here, I have finally successfully rooted my new Verizon Galaxy S4 (SGH-i545), and it had nothing to do with the root process itself, but it was the basic setup that was giving me fits.
Googling and searching has shown that this is actually a common enough problem with some Samsung devices, and there is a fix for it. Since I had to combine several different processes, I thought I would add a note here on how to get the device connected. I will leave the rooting and other discussions to the others. I am also going to give credit to arpruss, most of the steps here come from his work on the Epic. I have trimmed down to only what is necessary to get ADB working properly.
This assumes that you have already tried the various processes to install or update drivers, and that has not worked. Also assumes mid- to advanced user skills:
1. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
2. Set device in USB Debug mode (Settings | Applications | Development | USB debugging(x)).
3. Plug device into computer.
4. Run Device Manager
5. Look for SAMSUNG_Android. You shoud see it in the Other devices section.
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
For me turning off adb and reconnecting the cable fix the issue. Try it and report back.
Please ignore my spelling mistakes. English is not my native language.
Yes, but I now have both abd and mtp.
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
zzvelik said:
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
Click to expand...
Click to collapse
Dd you thank the post author?
Anderson2 said:
Dd you thank the post author?
Click to expand...
Click to collapse
I just did (Never really noticed that feature before)
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
I followed this advice, but didn't work for me. However, I then chose the 2nd option, "USB Composite Device", updated that and Voila! The "Unknown Device" with yellow warning still appeared, but I deleted that and all is good, thank you.
simple fix turn usb debbugging off
So your computer can install the driver for u
It worked!
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
Lots of thanks! It worked... I can now connect my rooted Nexus 7 under MTP mode!
zzvelik said:
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
Click to expand...
Click to collapse
I've been trying to fix this issue for way too many damn hours. Thank you so much for coming back to your own post and putting in the solution. This has been driving me CRAZY. Happy holidays
Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??
I ran into a very weird issue lately. My PC running Windows 10 (previous Windows 7) and having gone through more than 4 phones with me without cleaning out my system had a ton of old drivers for different phones attached to the computer. Whenever I'd plug my Pixel 2 into the computer ADB worked fine but for some reason when I go into recovery it wouldn't recognize my phone. I rummaged through hours worth of forums/reddit posts guides/youtube videos and everyone kept coming up with the obvious answers being; install the latest adb drivers or force install the google ones or you're entering recovery completely wrong. Being quite savvy in this I tried everything and have sideloaded in the past through recovery on this very phone so it was a real head scratcher what had happened. I went through device manager uninstalled and reinstalled pretty much every adb/mobile device driver associated with the phone. However through some oversight it just wasn't clicking with me when I was in device manager my ADB was listed as "LeMobile Android Device" and even when I uninstalled restarted my computer/phone used different USB cables and ports it never clicked that it shouldn't say LeMobile Android Device because obviously my phone is a Google Pixel 2. Again seeing that I have used this very computer and phone before in the past and have sideloaded OTAs I assumed my old setting would've stuck. But I guess the latest OTA or something on my computer reverted my ADB drivers to a LeMobile Android Device thus causing my ADB to NOT work in recovery anymore but still functioned fine inside Windows.
Through more digging I found a guide on reddit: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
Pretty much the top comment/solution is as follows:
A few steps to get rid of the LeMobile pesky driver.
1-Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2-Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3-Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4-Go to the device manager. Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver like the one in location "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
5-And You're done! Cool thing is that you will have to do it again if you connect a tablet or something new and Microsoft decides the LeMobile driver is better then Googles driver...
So yes in the future I may have to do this setup again because Microsoft is just dumb and doesn't let settings stick but I went through the list and force deleted all my old phones from Motorola and Samsung as well so when I installed the ADB drivers finally the Google one's stuck. Hopefully this will fix many other people's problems when they can ADB in windows but NOT in Recovery. My other option would be to format my computer and have a fresh install but ain't no one got time for that. There are other guides online to fully delete drivers but it is very time consuming so I'm going to skip that for now.