Hi. I am trying to sideload the Android 6.0.1 update but am having some problems detecting the device in recovery mode.
I have previously unlocked my bootloader on the day i got my phone.
I have enabled USB Debugging and have installed android USB Driver 11.0.
On my Windows 8.1 Device Manager...
When I am in normal android = Android Composite ADB Interface is present.
When I reboot to Bootloader = Android Bootloader Interface was installed.
However, when I am in the stock recovery, Android Composite ADB Interface is not found. Neither is there any unknown devices in my Device Manager (yellow question mark) that might look like the ADB Interface.
As a result, when I am in Recovery Mode, "ADB Devices" command does not work.
Help? Thanks!
Same here!
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
I am having this same issue. I've installed HiSuite with the latest USB drivers and have the latest Android SDK Platform Tools updates. I have tried unplugging and plugging-in the device when it is in recovery to try and trigger something but nada. I've tried different USB ports too.
My behavior is exactly the same. The phone shows up in ADB devices under normal full boot and also in the bootloader. As soon as it goes to stock recovery it won't show up as a device in Windows anymore. Not as an even an unrecognized device.
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Minlock said:
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Click to expand...
Click to collapse
Thanks! I realised im actually on Windows 10 too...
However, your method doesnt seem to be working for me.
In Recovery mode, "Android ADB Interface" doesnt show up. Hence, I added a legacy hardware as you suggested, but it shows up that "This device cannot start. (Code 10)".
I also tried to update the hidden "Android Composite ADB Interface". While driver installation was okay, the phone is still not detected.
I tried replugging in the phone into a different USB port but it is still the same.
Strange... seems like only some people are encountering such issues? Wonder what is the difference. Thanks.
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
l0nEr said:
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
Click to expand...
Click to collapse
After doing all the previous steps, doing this step really did the trick.
Thanks!!!
makeitra1n said:
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
Click to expand...
Click to collapse
i'm here too
I had same problem and after searching days it solved by installing universal ADB Drivers from the link below:
Universal ADB Drivers
Related
Hello guys
I've got some serious issues with my DHD (and Vista). It all started up by trying to install HTC Sync on my computer. After a month of countless attempts i was unable to get it working as well as internet pass-through. But today when i attempted a root, i couldnt use any adb command because it kept giving me an "error: Device not found". When i tried "adb devices" it showed me "List of devices" but no serial number below. I tried to install USB drivers through Android SDK but with no succes and i even tried some HTC USB drivers. No chance. In device manager i can see "Android phone" and "Android ADB interface" with the exclamation mark. So does anybody know how to get those USB drivers working so i can downgrade an root my phone? thanks
you probly have it on.. but you do have usb debugging switched on?
htc sync drivers should have install no problem so maybe uninstall them and reinstall with admin permissions.
did you update sdk drivers by sdk manger?
this post could help
http://forum.xda-developers.com/showpost.php?p=10054771&postcount=271
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.
Did you install the correct drivers?
When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.
ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions
I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app
I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html
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.
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!
my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.
The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.
its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.