I'm currently trying to sideload the Nougat OTA to my Nexus 5X, but after rebooting into recovery mode, ADB is no longer able to find my phone. I've tried changing the driver to the Composite ADB Interface driver, but the only options Windows gives me are MTP drivers. How can I fix this issue?
I have the same problem. Hopefully there's a fix.
Related
i have managed to sucessfully install a 2nd bootloader, TWRP Recovery, and CM10.1 onto my new KFHD with no apparent problems, following Hashcode's guide at http://forum.xda-developers.com/showthread.php?t=2128175.
I had already set up my system to support developing and debugging the KFHD, including the Amazon-specific Kindle Fire USB drivers; when plugged in, the device showed up in Device Manager as a "Kindle" with a "Composite ADB Interface", and `adb devices` detected the device.
After flashing the CM10.1 ROM I can no longer see my device as anything except an MPT USB Device, and `adb devices` says there are no devices attached.
I have tried both the Google USB drivers and the Kindle USB drivers and Windows claims that neither of them is correct for my hardware. When I check Device Manager, it says the attached device is VID_18D1, PID_6860, REV_0100, which doesn't match any of the device descriptors in either of the driver inf files.
Which driver am I supposed to be using now and how can I get it to install properly?
EDIT: I had forgotten to re-enable ADB Debugging on the tablet after flashing; now it is actually called an "Amazon Kindle Fire HD" and has a different device descriptor:
VID_18D1&PID_6861&REV_0261&MI_01
but still no love from ADB.
Thanks.
I'm having the same problem. No connection to ADB, and MTP only exists as a single file when activating the camera toggle. Frustrating to say the least, but not a deal-breaker.
Oh and a friend has the same problem. I know its not helpful, but atleast you're not the only one
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
No more Composite ADB driver after installing CM10.1
apd said:
That's really odd as adb works fine for me on Haschode's 10.1 Perhaps try reinstalling the drivers, The adb drivers are - click here
You may need to uninstall the old drivers before these work. Also, goes without saying that you need to enable USB debugging on the tablet!
Click to expand...
Click to collapse
I installed Hashcode CM10.1 for the first time tonight on an KFHD 8.9.
I have the same problem on both Windows and LINUX: loading CM10.1 on an HFHD8.9 tablet. (No ADB)
I use both every single day on both windows and LINUX so have lots and lots of experience.
In windows after installing 2nd boot /twrp and Hashcode zips (8.1.4.zip, or 8.4.1.zip) I have to use some old windows drivers for ADB and fastboot does not work at all. In LINUX, ABD and fastboot work for both Stock Kindle OS and all of Hashcodes Mod'd KindleOS.zips
If I load Hashcode's CM10.1, I have not ADB on Windows or LINUX ADB Devices shows 123456789ABCDE offline
Recovery shows devices = 123456789ABCDE Recovery
I can push files in Recovery but, not if the tablet boots into OS.
If I revert back to any one of the Hashcode KindleOS.zip images all is well at least in LINUX.
This issue is definately related to something driver wise in the CM10.1 OS.
Regards
I saw this same issue
I had this same issue after installing twrp and CM 10.1 as well. I was fortunate to have a second laptop that had not been used for this stuff before, and once i installed the adb drivers on that machine, had no issue connecting to the tablet from that machine. I still could not connect to it from the original machine. My guess would be to uninstall the ADB drivers from the machine you are using to connect, and reinstall. if that doesn't work, hopefully you have a spare machine, otherwise you might need to look at re-imaging you computer. I happen to keep a stock image file of my laptop in case of hard drive failure or other emergency, so it was about 20 minutes, and i was back up and running.
I have two Nexus 7 2013 one a 16gb and the other a 32gb. I have used Wug's toolkit to upgrade to android 5.0.2. Fro some reason I am now unable to see the 32gb either in adb or mtp. I reboot and get into fastboot and get adb to recognize the tablet. At a loss on what to do. Need some advice. Thanks
gadget069 said:
I have two Nexus 7 2013 one a 16gb and the other a 32gb. I have used Wug's toolkit to upgrade to android 5.0.2. Fro some reason I am now unable to see the 32gb either in adb or mtp. I reboot and get into fastboot and get adb to recognize the tablet. At a loss on what to do. Need some advice. Thanks
Click to expand...
Click to collapse
ADB and Fastboot are not the same. You cannot see the device in ADB while it is in Fastboot mode, and you can't see it with Fastboot when it's booted.
If you can put the device into fastboot by holding the power and volume down and then run "fastboot devices" on your PC, and see it, then fastboot works. With that, you should be able to flash factory images, etc.
If you can't see it in ADB, make sure the device is booted into Android (like I said, ADB won't work when it's off, save for the ADB OTA mode in recovery, to my knowledge), make sure USB debugging is ON in Developer Options (Settings > About > tap build number 7 times to enable), try clearing authorized machines under USB debugging, lastly, try different USB modes. When I was sideloading the 5.2 OTA on my girlfriend's Nexus 6 it wouldn't work in MTP but I switched to PTP and it worked (or maybe the reverse, I don't really remember...).
Those are my suggestions.. hope they help in some way.
Also, LET'S GO WILD.
fury683 said:
ADB and Fastboot are not the same. You cannot see the device in ADB while it is in Fastboot mode, and you can't see it with Fastboot when it's booted.
If you can put the device into fastboot by holding the power and volume down and then run "fastboot devices" on your PC, and see it, then fastboot works. With that, you should be able to flash factory images, etc.
If you can't see it in ADB, make sure the device is booted into Android (like I said, ADB won't work when it's off, save for the ADB OTA mode in recovery, to my knowledge), make sure USB debugging is ON in Developer Options (Settings > About > tap build number 7 times to enable), try clearing authorized machines under USB debugging, lastly, try different USB modes. When I was sideloading the 5.2 OTA on my girlfriend's Nexus 6 it wouldn't work in MTP but I switched to PTP and it worked (or maybe the reverse, I don't really remember...).
Those are my suggestions.. hope they help in some way.
Also, LET'S GO WILD.
Click to expand...
Click to collapse
ADB is enabled, switching back and forth from MTP to PTP does nothing. For whatever reason my pc will not see the tablet. I've uninstalled all the usb drivers I could find for the various devices I own and re-installed just the nexus drivers. Still no luck. I had to use my wifes XP pc to transfer stuff back on the tablet.
I use win7 64 bit
Adb drivers are properly installed ...
Using stock recovery.
When i connect and check adb devices ,my device is listed
And getting connected.
But when it goes to sideload mode then error pops
up showing drivers are not properly installed.
Cannot execute adb sideload command.
Where can we find the driver for 64 bit to cure this
Problem.....
Pls help
Google? Its not so hard to find 64bit adb drivers. Anyways why dont you install TWRP? Its way easier and the stock rwcovery might give that error.
CE 354 cannot be flashed via twrp.It shows error.
Thus I changed to stock to sideload it.
Even in Twrp sideload ,the same issue remains
I updated my OP3 to OxygenOS 4.1.3 two days ago and obviously lost my root and custom recovery.
After the update, I used the OnePlus 3/3T unified Toolkit because it worked just fine for the past year.
However, upon checking the status of the device, it detected 0 devices connected.
Using the command prompt also gave me the same answer; no devices.
I already have USB debugging allowed/OEM unlocked and developer options enabled, and bootloader is already unlocked, so I don't know what's the problem with this.
Try to reinstall the drivers trough the toolkit. If that ain't worked try to install manually the driver in device controll in windows and select the driver that you can install when download sdk.
For a weird reason my windows, sometimes, lost the driver for adb devices and then i can, just like you, not see my adb or fastboot devices.
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Replace adb by fastboot in fastboot mode
ex instead of
adb reboot
type
fastboot reboot
You've to use the fastboot command instead of adb. Please note that fastboot doesn't have all adb features, e.g. install, shell, etc
[email protected] said:
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
adb commands only work when phone is turned on and connected to pc using ADB.. it wont work n fastboot mode. In fastboot mode the command is fastboot.
example:
in adb-> adb devices
in fastboot-> fastboot devices