I have windows 10, and am attempting to root and flash a custom recovery and ROM onto my nexus 7. Everything functions as intended until i have to enter bootloader. windows 10 is not able to recognize the device drivers when plugged in while in bootloader mode. It simply says that the device is not recognized. I read that the issue is needing to edit the .INF with updated hardware ID's for the device and reinstall the drivers using that INF file. However, trying to do that yields no results because when i uninstall the driver i cant find the device plugged in anywhere to be able to update its drivers in the device manager, and simply trying to override the devices currently installed drivers via device manager also does nothing. I even tried installing the driver update while the device was in bootloader via device manager (the device is recognized in device manager but has a yellow exclamation point and says device descriptor failed) with no results. What am i doing wrong? can anyone help? I've never had an issue this frustrating while trying to root an android device. Is it a windows 10 issue? I need a complete (and simple to understand) step-by-step please.
No help?
Related
So I'm getting this issue where I can't locate the device via ADB. I've tried reinstalling drivers which doesn't work. The device regardless of if it's in debug mode or not fails to mount and instead, windows fails to even detect it branding it a "Unknown device". I've tried restoring to a previous nanddump (taken just after rooting) which has still failed to fix the issue.
Is there a fix or am I stuck with having to sideload every app I develop?
Edit: apologies for putting this in the wrong sub-forum
I had to go into device manager and force the unknown device to use the nexus 7 drivers from the android SDK folder manually, (after I have used the SDK manager to download them of course) I've had to do this on 2 windows 7 computers so far, so I would give that a go, if you need help I'll hunt a guide out for you.
dasmith91 said:
So I'm getting this issue where I can't locate the device via ADB. I've tried reinstalling drivers which doesn't work. The device regardless of if it's in debug mode or not fails to mount and instead, windows fails to even detect it branding it a "Unknown device". I've tried restoring to a previous nanddump (taken just after rooting) which has still failed to fix the issue.
Is there a fix or am I stuck with having to sideload every app I develop?
Edit: apologies for putting this in the wrong sub-forum
Click to expand...
Click to collapse
wugtoolkit has update the driver you search for try download that...
I got a nexus 7 2012 wifi 32gb today, updated to 4.3, and I have had nothing but problems trying to root the thing. I have been unable to unlock the bootloader, currently whenever I'm in bootloader mode windows 7 64 bit just shows it as an "unkown device" when I look at the properties it says "Windows has stopped this device because it has reported problems. (Code 43)" I have tried "update drivers" and had it look at C:\PROGRAM FILES (X86)\WUGFRESH DEVELOPMENT\DATA\DRIVERS but it just says the drivers are up to date for my unkown device. There was actually a point where in bootloader mode windows had device manager say bootloader something instead of unkown device however it says drivers were not installed and I think the error code was 10 or something, basically it was still useless and would not recognise my device and install drivers. I have tried on my laptop which has windows 8 64 bit but it is far worse there, the computer keeps giving malfunction usb message or something over and over again as if the device is constantly connecting and disconnecting. Despite this however MTP works fine and I have transferred a music album over as a test and it was fine and the device charges fine too. Would really appreciate help as I'm desperate at this point.
Uninstall whatever out of date drivers that came with the toolkit then install the latest Android Composite ADB Interface Driver 8.0.0.0.
You also need to install this in order to use ADB while in recovery.
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Short of going back in and deleting (not just uninstalling) every USB driver, might be easier to borrow another computer?
lightlink7 said:
No dice, still unable to install the drivers for the bootloader interface, I go to device manager and right click the android bootloader interface thing and click update driver software navigate it to the universal naked driver folder however it always just says the drivers for your device are up to date, which is bull**** because the drivers have not installed. I have tried right clicking then clicking uninstall then unplugging and replugging but it will now just give a message saying the device is not recognised and it shows up as an unknown device in device manager, 90% of the time it just shows up as an unknown device and it is impossible to install drivers for it, it just always says the drivers are up to date and uninstalling them and trying again will just yield the same results. I have the other drivers installed completely fine, it's the bootloader drivers which are impossible for me.
Click to expand...
Click to collapse
The Android Composite ADB Interface Driver 8.0.0.0 driver from SDK is for bootloader and when booted into ROM. Naked Driver 0.72 is only for when in recovery or else your computer would show "Nexus 7" under Unknown Devices in the Device Manager.
Hi guys,
this is my first post here, so please be tolerant.
I have a Nexus 4 that is rooted and bootloader unlocked. Today I made the mistake to start the OTA update for version 4.4 and after that it was not able to restart, only showing the "Google" sign.
So I wanted to use adb sideload, but the device is not able to connect to my computer. The problem is that it is classified as "unknown device" and therefore it cant communicate. I already tried to reinstall the SDK and PDAnet driver, but the problem is that the the device is still unknown.
I already tried it with different pc and also with uninstalling all drivers, still no success.
I also tried the factory reset from the recovery manager, but it had no effect.
For now I am able to start fastboot mode, but as I already said I have no chance to communicate with the device.
Hope you guys here have some more ideas.
Hi all,
After a long time, I decided to play with my Nexus 7 again. About a year ago, I bricked itsomehow (don't remember how exactly).
As a result, only the bootloader is installed. So no (custom) recovery and/or ROM. Today, I tried to flash the stock rom with the Nexus Root Toolkit but it didn't work.
My computer (Win 8.1) was not able to recognize my Nexus 7 in fastboot mode.
The device manager in windows labels my nexus as an unknown device of which the device descriptor request has failed.
I already tried to install many different driver packages (while removing the device from the device manager) but it did not work for me. Everytime, the tablet is seen as an unknown device.
I also tried to update the driver manually by right clicking on the unknown device in device manager and clicking update driver software and then manually selecting this http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2 driver but it does not recognize any driver.
So in short, my pc, which runs windows 8.1 is unable to see my Nexus 7 (which is bricked and has no rom nor custom recovery installed) when it is in fastboot mode. Therefore I am unable to install another rom.
Any thoughts on this problem? Thanks in advance.
I sent you a PM regarding this issue and a potential fix. If it works, i'll post the detailed info here later
Windows 10 automatically installed this update: Microsoft - WPD - 2/22/2016 12:00:00 AM - 5.2.5326.4762
Since then no mobile device I connect to my PC can be detected. I used a restore point and that got things working, but it auto updated again and this time a restore point did nothing, and after the restore all restore points magically disappeared.
What kind of USB driver can I install, or what do I need to do to get my PC detecting my phone again?
Update: After attempting to reinstall the Qualcomm USB drivers, which just came as loose files, it detected the phone improperly in the device manager and from there I manually chose "MTP USB Device" which I know is the default and that got the phone detected again. But now the phone is not detected in fastboot mode as an ADB device when I use the command ADB devices. I tried reinstalling the fastboot driver package but that doesn't do anything. How can I properly clear/install fastboot drivers to get this working again?