I am sorry if this topic is covered in other threads. I search around and could only find the developer thread and I am not yet allowed to post there.
--------------------------------------------------------------
I have a new Nexus 7 running Jelly Bean 4.2.1. I have activated developer mode and checked the "USB Debugging" box. Other than that, it is in the default configuration.
I want to root it, so I went to http://forum.xda-developers.com/showthread.php?t=1809195 and downloaded the Google Nexus Toolkit.
After identifying my device (Android 4.2.1 (Build JPP40D) for Wi-Fi Only 32GB), the first option was the install drivers. I did that. The 2nd step was to backup the device and I did that with no problems.
The 3rd step was to Unlock the Bootloader (requires Fastboot Mode). When I try to do this, it says that a Fastboot Device was not found.
I am at a loss here as to what to do?
I have some screencaps. I hope this helps.
Ideas?
http://forum.xda-developers.com/showthread.php?t=1741395
simms22 said:
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
TY, this says I need to be able to use "adb and fastboot". That is the problem. I do NOT know anything about fastboot. I turn off my nexus and then hold the volume up and volume down buttons then turn it on. I get a screen that looks like the image I have attached.
However, I do not know what to do from here. I press the volume up and down keys to change "Start" other options, but Fastboot is not one of the options.
Ideas?
You don't have the right drivers installed. When you see the boot loader screen, you should see 'android fast boot interface' or similar in your device manager.
Sent from my Nexus 7 using xda app-developers app
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Keep clicking OK a few times, it might find it.
if not, then, press the volume down button until it says reboot bootloader or reboot recovery, sorry i can not remember 100% right now,
press ok a few times more, well keep pressing it and it will find it
adamz2013 said:
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Click to expand...
Click to collapse
You are replying to a post from December 16th. Doubtful that the OP is still waiting on an answer.
Nice pot shot at people that do try to help, though. Either that or an unmet entitlement issue. No one in here is entitled to an answer for anything. Anything you or others provide in response to an inquiry is a gift, plain and simple. The answers might even be completely wrong or crap; but they are still a gift.
If the OP is still waiting, then they should know that all the detail that they showed (screenshots) are immaterial as they were taken with the device booted into the OS (composite ADB + MTP/PTP showing in Device Manager) instead of the mode that was having communication difficulties - fastboot/bootloader mode.
Immaterial information does not imply that the wrong driver is installed for a different operating mode for which similar information was not provided.
Most of the trouble in these types of post are due to the fact that the posters have no clue how WINDOWS drivers are managed/installed/ etc. That has everything to do with WINDOWS and user skills, and almost nothing to do with the device on the other end of the cable.
Having said that, the principal reason there is confusion is due to the following set of circumstances:
- Casual Windows users are "accustomed to" doing a single install of a driver package when they buy a new device. Even when that device might have many logical endpoints across the USB bus. (Think of a multi-function printer - it might have an SD card slot on it, the printer, a scanner function, etc). When that multifunction behavior exists, usually the OEM provides a "driver installer" package which will actually install multiple drivers, depending on the plurality of USB endpoints in the device.
- Unfortunately, if you carefully inspect any of these three driver bundles:
- Google (SDK) USB Driver
- Asus Nexus 7 USB Driver
- XDA "Universal Naked Driver"
you will find that (as shipped) NONE OF THEM will work for all of the following modes of the Nexus 7:
- Fastboot mode
- ADB Mode, OS (Single or Composite)
- ADB Mode, Custom Recovery
- APX Mode
- PTP Mode*
- MTP Mode*
That's right. As shipped NONE OF THEM will handle all of these cases. The "as shipped" part is a reference to the fact that a trivial edit of the "android_winusb.inf" file for any of them will allow a single driver to handle all fastboot and ADB modes.*
* The MTP/PTP drivers are meant to be handled by MS Windows generic class drivers; in the case of Windows XP you might need to install a Windows Media package to get the MTP driver - I'm not sure that it is part of Vanilla XP SP3
So, anyhow - people get confused because they "install the driver" for one mode (usually ADB), and then are surprised when they boot the device into a different mode (fastboot or ADB running under custom recovery) and surprise, surprise - their PC says "unknown device".
My advice?
Install the Asus Nexus 7 Driver for everything but the Custom Recovery ADB mode, and then install the Universal Naked Driver for that.
Or, prior to installation fix up the android_winusb.inf file that comes with the Asus driver so that it also supports
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
Then a single driver will support everything but APX, MTP, and PTP. The latter two of which are provided by Mister$oftie, and the first of which is currently of unknown value to Nexus 7 rooters.
cheers
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
juicejuice said:
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
Click to expand...
Click to collapse
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
bftb0 said:
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
Click to expand...
Click to collapse
I am a Mac user, and I'm having problems with fastboot. My nexus is unlocked, and I'm trying to flash the lastest 5.1 factory image. I was rooted long ago, but really have no need for root, and lost it during one of the OTA's. I'm not a noob by any means, but none of my terminal commands are working, because fastboot has decided to disappear on me. Any suggestions would be appreciated.
I can't even get TWRP because I don't have root, and I can't get into fastboot.
Edit.....I'm an idiot....I figured it out. On top of it all, my USB cable sucks too so that didn't help any.
Related
I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?
xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium
Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.
I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.
I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?
One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0
Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method
No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills
AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!
Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!
I just bought a Nexus 4.
All I've done thus far -
Upgraded to 4.3.
Installed the drivers from the Android SDK kit, so in my device manager, all that shows is 'Android Composite ADB device' when the Nexus 4 is connected.
Yet, when I run fastboot devices in platform-tools, I'm getting nothing.
I've tried un-installing, then re-installing the drivers to no avail.
Any help?
It should be called "Google Nexus 4 Bootloader Interface".
The device probably didn't get the correct usb driver. Try going to Device Manager, Uninstall that ADB device and also select the checkbox "Delete the driver software for this device."
Then press the icon to "Scan for hardware changes". Reinstall the driver this time using Universal Naked Driver.
Just to make sure. Are in the bootloader on your phone when you are trying this?
As you can't use fastboot in android
To get there hold power and volume down
Your phone well reboot
Keep the buttons held and you will appear in the bootloader.
If you are trying this from within the bootloader then I'm very sorry for sounding patronising. That was not the intent
Sent from my Nexus 4 using xda app-developers app
As was previously mentioned, make sure that you are in the bootloader when running fastboot.
Now, when I updated to Android 4.3, my very old SDK kit had several programs that did not work anymore (Some of the commands didn't work, USB driver didn't work, etc.). So I installed the latest SDK, but later noticed that there was an update manager built right into the kit. It is located in the folder that has a name similar to the following: adt-bundle-windows-x86_64-20130717 (The name may look a little different), and the name of the program is "SDK Manager.exe". I ran it and several updates appeared, so I clicked on the Install button. The Windows driver is hidden under the "Extras" section and listed as "Google USB Driver". When you highlight that item it shows where it is located in Windows on the hard drive. The current version of this driver is "revision 8". After removing the old driver from the Device Manager in Windows, as I recall, I had to use the "search for the driver" mode, as pointing directly to the driver did not work for some reason. After installing it into Windows, it was listed as "Android Bootloader Interface", Version 8.0.0.0, dated 07-09-2013. These various updates solved all my 4.3 problems. What is really nice about the SDK is that you don't have to rely on drivers and programs posted on a forum somewhere that you have no idea whether they are up to date or not, and for that same reason and really understanding how things work and how to troubleshoot from the command line, is why I would never use a toolkit.
Alex240188 said:
Just to make sure. Are in the bootloader on your phone when you are trying this?
As you can't use fastboot in android
To get there hold power and volume down
Your phone well reboot
Keep the buttons held and you will appear in the bootloader.
If you are trying this from within the bootloader then I'm very sorry for sounding patronising. That was not the intent
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was it. Thank you very much. You will have to forgive me for my incompetence in advance. I am coming from dark side (iOS) after having finally seen the light.
Now, onto flashing LTE on my phone...
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!
Error messages
In device manager, a device named "APX" (within <computer>/Other Devices) with a yellow icon on the lower portion had the following inside its properties box:
-----
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
-----
blackthund3r's A500 Manager reports at the bottom, "A500 Detected in APX Mode. Please install the drivers!"
Circumstances
I am using a Windows 8.1 PC. I have an Acer A500 running an unknown ROM that is bricked. It boots to Acer logo, then continually loops the android text animation.
I am able to boot the device consistently in APX mode. (The trick is to unplug the power cord before starting, so one can see when the power button is lit, to time the release of the power and reset buttons properly. The tricky part is remembering to plug the power back in.)
Attempts so far
I am trying to start over with a clean (EUU?) ROM, but first, I need the CPUID to get the SBK.
After following blackthund3r's guide at http://acerhacks.com/ , I downloaded the A500 Manager executable. I also got "ICONIATABUSBDriverSetup.exe" from a source I do not recall, but I am fairly certain it was a link from forum.xda-developers.com .
I also followed the instructions at http://forum.xda-developers.com/showthread.php?p=48827675#post48827675 to get the folder full of "ini" files. I tried manually updating the driver from within Device Manager using files from this folder. This still did not work. :'-(
My plea
Can anyone help? Should I try a friend's Windows 7 computer? I don't want to install Ubuntu. If I must, will installing it inside VirtualBox work?
alexAG76 said:
My plea
Should I try a friend's Windows 7 computer?
Click to expand...
Click to collapse
Yes!!!
XP, vista or win7 all work fine.
Win8 or any 64bit systems have issues.
Sent from my GT-I9300 using Tapatalk
alexAG76 said:
Error messages
In device manager, a device named "APX" (within <computer>/Other Devices) with a yellow icon on the lower portion had the following inside its properties box:
-----
The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver.
Can anyone help? Should I try a friend's Windows 7 computer? I don't want to install Ubuntu. If I must, will installing it inside VirtualBox work?
Click to expand...
Click to collapse
To get windows to recognize the drivers properly, go into device manager and find the APX driver with yellow triangle. Update the driver for this but chose 'browse my computer for driver software". Direct it to crogram Files (x86)/Acer Inc. This should force it to find the correct driver. I am of course assuming you have the Acer driver installed.
I just bricked and unbricked this device a month ago. What an adventure. APX mode will lead you down the right road. Combined with the toolkits available, you can have it back up in a couple hours.
This link may help you out. http://forum.tegraowners.com/viewtopic.php?f=30&t=388
One thing is getting the uid. If you have an old nandroid off of the device it will be very helpful. There is a file in it that has a number in it that can convert to the UID. if you need more help let me know and I will dig through my history and find the resources I used.
dibb_nz said:
XP, vista or win7 all work fine.
Win8 or any 64bit systems have issues.
Click to expand...
Click to collapse
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
alexAG76 said:
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
Click to expand...
Click to collapse
Does safely remove hardware icon in the system tray show anything???
Sent from my GT-I9300 using Tapatalk
BCSC said:
To get windows to recognize the drivers properly, go into device manager and find the APX driver with yellow triangle. Update the driver for this but chose 'browse my computer for driver software". Direct it to crogram Files (x86)/Acer Inc. This should force it to find the correct driver. I am of course assuming you have the Acer driver installed.
I just bricked and unbricked this device a month ago. What an adventure. APX mode will lead you down the right road. Combined with the toolkits available, you can have it back up in a couple hours.
This link may help you out. (URL omitted due to newbie status.)
One thing is getting the uid. If you have an old nandroid off of the device it will be very helpful. There is a file in it that has a number in it that can convert to the UID. if you need more help let me know and I will dig through my history and find the resources I used.
Click to expand...
Click to collapse
Thanks. I'm about ready to throw in the towel, but I shall look at that URL.
I think my drivers are defective.
dibb_nz said:
Does safely remove hardware icon in the system tray show anything???
Click to expand...
Click to collapse
I will have to check. I've already purchased a replacement, but it would be nice to get this thing going again. Thanks for the responses.
alexAG76 said:
Using Vista/Win7, I kept hearing the "device connected" noise in APX mode. Device manager refreshed several times, but I could never find the non-functioning device icon in order to update the drivers.
Click to expand...
Click to collapse
Open up a couple branches in device manager and plug/unplug it. Do this until you find which branch it is in. Then apply the driver the way I mentioned above. At some stage you will come across the branch that changes. It should only take a couple minutes. Just watch and you will see a new item pop up. You are experiencing the same issues that haunted me and this method will work. Start at the bottom of the device manager list and work up. I'm confident it was towards the end. Hearing that connection sound means that it will be there.