Related
Hi guy,
I got this problem. When I plug my Kindle Fire into the laptop with the cable, of course I switched to USB debugging already, there is Android ADB Interface in my device management. However, when I start cmd and type adb devices --> there's no devices attached to my computers.
I re-plugged my Kindle Fire with the cable and click on turn on USB storage on the screen of KF, but it's still the same. There's no devices attached
I tried to re-run the install_drivers.bat (from KFU) but it has no results. It's still the same.
I think I have nothing wrong with the driver installation. It's kinda fine and I still can copy data in and out. However, I still tried to re-run the install_drivers in KFU and this is what I have (I rejected my Kindle Fire before re-running as your tutorial)
https://www.dropbox.com/s/sk84tqhtwba7jz7/KF_Noti.jpg
I tried to use some commands and this is the result
https://www.dropbox.com/s/u85xoupskedmaui/KF_cmd.jpg
I dunno what to do right now to install a new ROM when it's not connected. Previously, everything was fine.
What can I do now? I need to install a new custom ROM.
Also make sure your not using a 3.0 USB port they have fast boot communication issues but likely you need to uninstall you driver then plug your kindle in and let them reinstall
I tried to uninstall it and plug it to computer to reinstall it manually. However, when I plugged it to computer, it automatically receives the driver that I had just uninstalled.
I tried to make an overlapping driver, hence I continued to reinstall manually but it is said that it is working properly.
For your further information.
1. Whenever I plug in my Kindle Fire, this is the notification that I have. I think this is an error
https://www.dropbox.com/s/h0mhaiklthdfo01/KF_NoDisk.jpg
2. This is an overlook at my Kindle Fire driver on my computer when I plug it in and set up the debugging
https://www.dropbox.com/s/nym7n0ygo2sfqay/KF_General.jpg
The driver shown in your picture is the fastboot driver. Generally indicating your device in fastboot mode for kfu it needs to read android composite adb interface . So if your device is in normal bootmode then this driver is incorrect.
Yep! I have the same thought with you. I think there is a problem with my driver. But what am I supposed to do right now?
I did uninstall and re-install driver, both manually and automatically. ( Is there anything that I can try now?
P/S: I still can copy data between computer and Kindle Fire. So I don't know what the hell is going with my driver
Here is an excellent tutorial post #2 on drivers maybe it will be of some help to you http://forum.xda-developers.com/showthread.php?t=1552547
I did follow this tutorial, as the first step to start my Kindle Fire. I think I would try it again.
I would love to have your teamview. Thank you so much
I have a kindle fire which wasn't doesn't connect to the computer. I get an error message such as "USB device not recognized". I had rooted the kindle fire and I thought that this problem could have been because of the rom or some kind of kernal error so I installed the stock rom thinking that I will just re-root if however the connection problem still was still there. So now I have kindle fire which is not rooted so doesn't have google market and I want to root it however cannot find a way to get it connected. I have tried 3 different computers and many different cables however still no success. I have also tried reinstalling the drivers, turning off and on the kindle fire with the cable plugged in. Could the port on the kindle fire be broken even though it charges fine. Also, would a factory cable help because I don't want to order it if it doesn't work. What other options do I have? I live in UK and this kindle fire is the 1st gen which was only available in US so cannot send it to amazon for checking.
Your help will be appreciated :good:
Do you have TWRP installed? If so, try connecting it to the computer using the USB mount via TWRP...
I have 3 Kindle Fire tablets that I installed a JB ROM on for some friends, and one will not connect to the computer (except via TWRP). I never did figure out why, but I could copy a ROM and Gapps to it while in TWRP. I set them all up the same, and that one still doesn't connect.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
http://forum.xda-developers.com/showthread.php?t=2179748
No root therefore no twrp
larryf said:
Do you have TWRP installed? If so, try connecting it to the computer using the USB mount via TWRP...
I have 3 Kindle Fire tablets that I installed a JB ROM on for some friends, and one will not connect to the computer (except via TWRP). I never did figure out why, but I could copy a ROM and Gapps to it while in TWRP. I set them all up the same, and that one still doesn't connect.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
Click to expand...
Click to collapse
Sorry for the late reply but no i do not have twrp as went back to stock as I thought that root cause some problem. So now I'm stuck without root and therefore without play store and I cannot root
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
Thanks I will try this and get back to you
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
I tried following the guide however I cannot do the hardware ID bit because in device manager it doesn't show the hardware id. It just shows unknown device
shlokpatel said:
I tried following the guide however I cannot do the hardware ID bit because in device manager it doesn't show the hardware id. It just shows unknown device
Click to expand...
Click to collapse
Plug the device in and manually uninstall the unknown device that shows up in Device Manager. Then Find the directory where the 'android_winusb.inf' is stored (somewhere in your WINDOWS directory), delete it, and start over.
soupmagnet said:
Plug the device in and manually uninstall the unknown device that shows up in Device Manager. Then Find the directory where the 'android_winusb.inf' is stored (somewhere in your WINDOWS directory), delete it, and start over.
Click to expand...
Click to collapse
Tried but still not working
Could it be possible that the port on the kindle fire is broken as I have tried connecting in on many computers and in none it has worked. Also I dont know if this is relevant but when I connect the kindle fire to the computer, the device is connected screen doesn't come up, it just charges and thats it no other change
shlokpatel said:
Tried but still not working
Could it be possible that the port on the kindle fire is broken as I have tried connecting in on many computers and in none it has worked. Also I dont know if this is relevant but when I connect the kindle fire to the computer, the device is connected screen doesn't come up, it just charges and thats it no other change
Click to expand...
Click to collapse
If this is the stock OS, then I would say that is definitely a problem. You may have some system files missing for detecting USB devices plugged in as UMS. Are you able to access any flash drives?
soupmagnet said:
If this is the stock OS, then I would say that is definitely a problem. You may have some system files missing for detecting USB devices plugged in as UMS. Are you able to access any flash drives?
Click to expand...
Click to collapse
Yes, my computer detects my galaxy s2 and other flash drives perfectly. Is there any way of rooting the kindle fire without connecting it to the computer? Because all i want is to have the play store on my device
The new version of KFU seems to have a much more effective driver install. You should try looking into that.
soupmagnet said:
The new version of KFU seems to have a much more effective driver install. You should try looking into that.
Click to expand...
Click to collapse
Still doesn't work Any method of rooting without computer connection ?
EDIT:
Also tried the soupkit on Linuxmint and still no luck
Hi there,
I'm having the same problem with a kindle fire.
- Stuck at logo
- Driver is installed but device is not recognized, so does hardware id.
Hope some one have a solution
bangsnntk said:
Hi there,
I'm having the same problem with a kindle fire.
- Stuck at logo
- Driver is installed but device is not recognized, so does hardware id.
Hope some one have a solution
Click to expand...
Click to collapse
Windows version?
Listed as what in Device manager?
Sent from my XT894 using Tapatalk
I am having the same issue with my KF2. USB Comms disappeared in terms of the device being recognised by XP but strangely fastboot worked and I was able to load CM11 on the device after downloading it via wifi and installing TWRP via fastboot. Still no USB on CM11 but its briefly recognised for a split second when it first boots. Monting the volume via TWRP has not effect either.
Have tried a variety of cables and have tried connecting the Kindle to an XP netbook, downloading fresh drivers etc etc etc.
Any ideas out there?
Shotaway said:
I am having the same issue with my KF2. USB Comms disappeared in terms of the device being recognised by XP but strangely fastboot worked and I was able to load CM11 on the device after downloading it via wifi and installing TWRP via fastboot. Still no USB on CM11 but its briefly recognised for a split second when it first boots. Monting the volume via TWRP has not effect either.
Have tried a variety of cables and have tried connecting the Kindle to an XP netbook, downloading fresh drivers etc etc etc.
Any ideas out there?
Click to expand...
Click to collapse
I Think you would get better help in one of the Kindle Fire 2 / KF HD Q&A forums
Sent from my XT912 using Tapatalk
sd_shadow said:
Windows version?
Listed as what in Device manager?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Same problem.
Problem:
-stuck @ logo screen
-usb not recognize by computer (windows 7 OS)
I already tried using different sets of cable, reboot both kindle and pc, tried to insert on different usb ports, tried to install adb and adb drivers. still not recognize.
Please help, any suggestion is very much appreciated.
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've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
Dug my old 2013 wifi 7 out to use on a project. Running a stock ROM, not sure of the version, rooted and unlocked bootloader. I screwed up something installing a new ROM and ended up wiping the system and data partitions. I'm trying to get a ROM onto the device so I can flash it. I can boot into fastboot and TWRP 2.8.6.0. Of course with no system it showed up as an unknown device. While doing the driver uninstall/install dance trying to get the naked driver set to work the tablet just stopped showing as connected to my windows 10 pc. Not like "unknown device" etc, no devices connected at all. Nothing shows on usbdview either. Tried plugging into a windows 7 pc, same thing, even tried a ubuntu live cd boot, nothing. Tried toggling MPT in TWRP on all these attempts. I can't mount USB OTG from TWRP I think its too old of a version. The tablet will charge so I don't think the usb port died. I'm out of ideas. Any suggestions before throwing in the towel?
Get the stable ROM for Flo. Stick Ubuntu on a decent laptop. Get a USB cable that's good for data and look at this instruction: https://itsfoss.com/restore-android-factory-nexus-7-2013-linux/
You want to Root look at this one and follow exactly: https://itsfoss.com/root-nexus-7-2013-ubuntu-linux/