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
Hello,
My friend left me his Kindle Fire yesterday (it's vanilla, because he only watches movies with it), and I've tried rooting the device and complications happen and now my Kindle is stuck at logo. I'd really appreciate it if you can help me fix it. Here's what happened:
- I downloaded the KFU, and followed the instruction on rooting. After installing the drivers and run the utility, the driver shows as online and 4000, and I started rooting.
- The utility downloaded TWRP and FFF, and while installing FFF, the utility is stuck at <waiting for device> (at the same time, Windows gives me an error of Device not recognized). After I unplugged the device, kindle now is stuck at logo. I tried to reinstall the driver through the file in KFU to no avail.
- Open Device Manager, I saw the driver has yellow exclamation. Followed someone's guide on here, I uninstall the driver.
- After I plug the Kindle in again, Windows won't recognize the device and in Device Manager, it shows up as Unknown Device.
- I tried to reinstall the driver through KFU, it installs really fast (I think that means I haven't exactly uninstall the driver, idk), but then the device manager still doesn't recognize Kindle and it still shows Unknown Device.
- I switched to a different computer with KFU driver installed before, it still shows Unknown Device >.<
I tried changing the Bootmode through KFU to normal, but it stuck at <waiting for Device>
EDIT: I started with a different laptop, install a new, clean version of Kindle driver, and then connect the Kindle in again. It still shows Unknown Device.
Help please D:??????
If it says /unknown device/ in your divice manager then your drivers are not installed...Get your drivers installed first.Also try the UNBRICK utility it help me when i first started.
apple2107 said:
Hello,
My friend left me his Kindle Fire yesterday (it's vanilla, because he only watches movies with it), and I've tried rooting the device and complications happen and now my Kindle is stuck at logo. I'd really appreciate it if you can help me fix it. Here's what happened:
- I downloaded the KFU, and followed the instruction on rooting. After installing the drivers and run the utility, the driver shows as online and 4000, and I started rooting.
- The utility downloaded TWRP and FFF, and while installing FFF, the utility is stuck at <waiting for device> (at the same time, Windows gives me an error of Device not recognized). After I unplugged the device, kindle now is stuck at logo. I tried to reinstall the driver through the file in KFU to no avail.
- Open Device Manager, I saw the driver has yellow exclamation. Followed someone's guide on here, I uninstall the driver.
- After I plug the Kindle in again, Windows won't recognize the device and in Device Manager, it shows up as Unknown Device.
- I tried to reinstall the driver through KFU, it installs really fast (I think that means I haven't exactly uninstall the driver, idk), but then the device manager still doesn't recognize Kindle and it still shows Unknown Device.
- I switched to a different computer with KFU driver installed before, it still shows Unknown Device >.<
I tried changing the Bootmode through KFU to normal, but it stuck at <waiting for Device>
EDIT: I started with a different laptop, install a new, clean version of Kindle driver, and then connect the Kindle in again. It still shows Unknown Device.
Help please D:??????
Click to expand...
Click to collapse
Most of the time (if not all), when I see an "unknown device" error, it is a sign of a corrupt or failing bootloader. So far, there is only one way to fix a bad bootloader (Firekit), but it takes a little work on your part.
Before I get into that just yet, you need to know that on top of that potentially being the problem, you still have to deal with Windows driver issues. So my suggestion to you is, since you may very well have to install Linux or set up a Linux LiveUSB to fix your bootloader problem, you might as well install Soupkit to see if the bootloader is in a usable enough condition to issue fastboot commands. It's unlikely, but you'll at least be able to launch Firekit easily, and without the need to install anything else.
Same problem
I'm having the same issue with my manager's kindle fire (6.3.1). I attempted to root using the instructions provided here . My windows explorer crashed during the process and the kindle has been stuck on the kindle logo since.
I have tried restarting the process with his supplied driver and I can get the kindle to be recognized correctly in the device manager, but the process does not work.
I have also tried the kindle fire unbrick utility found here http://forum.xda-developers.com/showthread.php?t=1428428 to no avail (device not found).
I have also tried the kindle fire utility found here http://forum.xda-developers.com/showthread.php?t=1399889 also to no avail (ADB Status: Offline Boot Status: Unknown).
And last but not least, I have constructed a "factory cable" in an attempt to fix this. Unfortunately, it doesn't appear to be working either. Even with the factory cable inserted, the device never boots to anything but the kindle fire logo (Drivers installed, plug in, power off, power back on, kindle logo).
I would purchase a pre-made factory cable, but they all ship from China, I'm a cheapskate, and I'm pretty sure mine is configured correctly. Does anyone have any suggestions for trouble shooting this?
I've attached pics of my "factory cable" as well. If something looks amiss. Please let me know.
seems to be in fastboot mode - look here - especially post #3:
http://forum.xda-developers.com/showthread.php?t=1552547
kindle stuck
deletarus said:
I'm having the same issue with my manager's kindle fire (6.3.1). I attempted to root using the instructions provided here . My windows explorer crashed during the process and the kindle has been stuck on the kindle logo since.
I have tried restarting the process with his supplied driver and I can get the kindle to be recognized correctly in the device manager, but the process does not work.
I have also tried the kindle fire unbrick utility found here http://forum.xda-developers.com/showthread.php?t=1428428 to no avail (device not found).
I have also tried the kindle fire utility found here http://forum.xda-developers.com/showthread.php?t=1399889 also to no avail (ADB Status: Offline Boot Status: Unknown).
And last but not least, I have constructed a "factory cable" in an attempt to fix this. Unfortunately, it doesn't appear to be working either. Even with the factory cable inserted, the device never boots to anything but the kindle fire logo (Drivers installed, plug in, power off, power back on, kindle logo).
I would purchase a pre-made factory cable, but they all ship from China, I'm a cheapskate, and I'm pretty sure mine is configured correctly. Does anyone have any suggestions for trouble shooting this?
I've attached pics of my "factory cable" as well. If something looks amiss. Please let me know.
Click to expand...
Click to collapse
hey man, im having the same exact issue, did you ever end up getting it resolved
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.
I'm new to the Kindle Fire flashing scene, and trying to get Jelly Bean on to my stock Kindle Fire. I've spent several hours on it so far, and haven't been able to get past the first step of getting KFU to see my Kindle Fire, so I can root it or do anything else. To be clear, this is a 1st gen Kindle Fire, running 6.3.1. I've never rooted or flashed it before, and it boots and works perfectly.
The main problem I seem to be having is that Device Manager (on my Win7 PC) shows the device as 'Android ADB Device.' It seems the expected description should be 'Android Composite ADB Device' but I can't get it there. Most of the posts and pages I've seen related to having trouble getting KFU to see a Kindle Fire focus on the drivers not being installed at all, which I don't think is my problem. And I've uninstalled/re-installed them at least 1/2 a dozen times with no effect.
The documentation would seem to suggest that seeing 'Android ADB Device' in the Device Manager implies my device is in Fastboot mode. However, when I uninstall the drivers I see 'Kindle' not 'kindle' in my device manager which suggests normal mode according to the 'Windows Device Drivers and the Device Manager' tutorial. This seems consistent with the fact that my device behaves perfectly normally, so I don't think it's actually in FB mode. Further, the FB tool can't see it.
I've tried connecting to the device from the command line using both the ADB (adb devices) and Fastboot (fastboot -i 0x1949 getvar product) tools. Neither one seems capable of connecting to the device. I also tried connecting the device on a second PC and there too I got 'Android ADB Device', suggesting the problem is device side. I don't have a factory cable to force FB mode that way.
I suspect I'm missing something obvious, but can't figure out what. Can anyone help me out?
It`s probably something strange I`m pretty good at working it out contact me tomorrow via Pm I would be happy to look at it for you. Check your user/.android folder for adb_usb.ini see if it has 0x1949 in it.
Thanks, the adb_usb.ini has the 0x1949 line in it, so that's not the issue. My %userprofile% directory name has a space in it, which initially caused the install_drivers.bat that comes with KFU to have some issues (because it assumes it doesn't.) But everything is where it should be now. Look for my PM.
Re: [Q] Can't get Stock Kindle Fire to show "Android Composite ADB Interface"
I had to used the drivers in superoneclick 2.3.3.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This problem is solved he was running kfu from a temp directory.
Actually, I don't think the problem was the location of KFU. Thepooch gave me a new android_winusb.inf to use along with the KF drivers. The new .inf file had additional Kindle Fire entries for USB\VID_1949&PID_0004 and USB\VID_1949&PID_0007 which the original version I got with KFU did not include. If I pull up the Hardware IDs from the details tab of the device in Device Manager, it showed the PID_0007 version. So I suspect the fact that was missing from the inf file was the cause of my issues (and it's inclusion the solution.) I've attached the updated inf file (with added .txt extension) to this reply.
Beyond that, Thepooch did an amazing job helping me through the whole process. Really went above and beyond. Thanks!
Hi all,
I've got a Kindle Fire, which was rooted quite a while ago. More recently, I had the 5 second bootloop, so I took the kindle apart and charged the battery directly by cutting apart a micro usb cable. This worked and now the device powers on, but is stuck on the logo. I previously had all my drivers set up for kindle, and ADB was working properly, but now it shows up as an unknown device. I have tried reinstalling my entire Android SDK, with Amazon's repositroy added, and have uninstalled the drivers on the Kindle, so that only the Amazon ADB drivers remain. Still, I am unable to connect with ADB, and the device still shows up as "Unknown Device" and fails to be noticed by Windows7, or ADB.
Can anyone point me in the right direction please? Thanks!
P.S. I've tried the KFU.
lobwege said:
Hi all,
I've got a Kindle Fire, which was rooted quite a while ago. More recently, I had the 5 second bootloop, so I took the kindle apart and charged the battery directly by cutting apart a micro usb cable. This worked and now the device powers on, but is stuck on the logo. I previously had all my drivers set up for kindle, and ADB was working properly, but now it shows up as an unknown device. I have tried reinstalling my entire Android SDK, with Amazon's repositroy added, and have uninstalled the drivers on the Kindle, so that only the Amazon ADB drivers remain. Still, I am unable to connect with ADB, and the device still shows up as "Unknown Device" and fails to be noticed by Windows7, or ADB.
Can anyone point me in the right direction please? Thanks!
P.S. I've tried the KFU.
Click to expand...
Click to collapse
install drivers that are included with KFU
then
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
Sent from my XT907 using Tapatalk
+1 to above response. Tell windows to look for similar installed drivers and choose the ADB interface drivers.
Thank for the quick response. I tried what you told me, and I notcied that when I plugged the Kindle in, and listing of "Android phone" popped up in device manager. It then immediately disappeared. After a little dinking around with the cable, I found that the micro usb port on my Kindle in loose on the inside. It wasn't making a proper connection. So I'm charging it right now with the cable slightly angled in the device. Thank you for the help anyways!
Any ideas what I could do to fix the loose port? Solder?
soldering should fix it, several YouTube videos on it.
Sent from my XT907 using Tapatalk