Related
I've bricked my Kindle Fire into Bootloop. I installed busybox 1.19.3 and was attempting to install TWRP recovery with "Kindle Fire Utility" then it started to download the latest version of TWRP. While it was downloading my Kindle Fire rebooted itself (download has not finished yet) and was stuck at the "Kindle Fire" splash logo(no animation). What should I do?
My adb cant find my device at all.
I've added
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
and installed the adb driver currectly.
Note: Before it got bricked, root access turned off after installing busybox.
I've tried Hard Resetting, but turns off at 10sec and stays in bootloop after i press the power button.
I don't know what to do, plz help!!!
http://forum.xda-developers.com/showthread.php?t=1413096
More specifically...
http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5
OK that helped a lot and fixed it. now its stuck in recovery bootmode. KFU cant even detect it. its stuck with a yellow triangle with fire inside, and says "press power for recovery" on the bottom.
What should i do???????
use kfu anyway - change bootmode to normal (point 1 of my last post)
KFU cant find device
Sent from my X10i using XDA App
what's the error message if you try the KFU ?
looks like a driver problem we have to sort out
what's the status of your drivers in device manager ? (assume your on windows)
if windows what version/bit(32/64)/language ?
yes , im on windows, 32bit xp Traditional chinese
Sent from my X10i using XDA App
it stays in <waiting for device>
Sent from my X10i using XDA App
ok - you have a driver problem
do you have the newest KFU (.9.1) ?
download and run install_drivers.bat
Still didnt find my kindle...
how should i connect my kindle??
i turned it off my pressing on the power button for 10sec, ran KFU, went in to bootmode menu, connected my kindle and ran Normal(4000), and stays at <waiting for device> .
like i said - you have a driver problem
take the newest kfu and run "install_drivers.bat"
if that does not work we have to uninstall your faulty drivers first and
if it's really bad we have to install the drivers manually*
let' take one step after the other
* to uninstall old/faulty drivers:
disconnect kf and use:
http://support.microsoft.com/kb/315539/en-us
connect KF and select the last installed driver (which you installed by running "install_drivers.bat") manually (check the date/time on selection)
alternately you can try:
open a command prompt and cd to the tools folder (Kindle Fire Utility\tools)
do the following commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
depends on the current status/bootmode of your kf and drivers if it's working or not ...
or this:
http://forum.xda-developers.com/showpost.php?p=20756846&postcount=15
or if you can get into TWRP by pressing the power button at startup till it gets orange:
http://forum.xda-developers.com/showpost.php?p=20757041&postcount=16
the terminal is in the right upper corner
did you get it ?
adb wasn't recognizing any devices
kfu wasn't letting me change boot mode
I reinstalled ADB on kindle (it was listed under other devices again...not android)
now adb is installed but it says no devices listed
still stuck on yellow triangle with fire screen.
can someone help me or link me to a older thread that can help me?
I seriously just want to get my device functional again...i don't even care about loading a custom rom anymore (I think this has completely discouraged me from trying to load a custom rom on this thing ever again.)
there are a lot of reasons, try reading this:
http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5
and
http://forum.xda-developers.com/showpost.php?p=20761609&postcount=12
if you have still problems after doing this, ask further
btw. don' be encouraged - it's a common problem - once you've setup you drivers correctly (connect right in every bootmode) most problems are gone and you can do nearly everything you want with your KF
FIXED!!!
Thanks Guys!!!!
I just switched a computer and installed the driver(so i dont have to uninstall form first computer).
Then started KFU didnt cared if it said "cannot find device" and chose the bootmode, surely the Kindle Fire Rebooted, Started up, and Recovery working greatly. Thanks Guys!!!!!!!!
glad to help ...
please change the subject of the topic (edit first post) to [Solved]
First, sorry for my english.
I have a Kindle Fire OS 6.2.1. I dont know why my Kindle didn't work with ADB driver.
Only one time it work when I used Kindle Fire Utility 0.9.1, then I run option 2 then 3. After that, my Kindle reboot and stop at logo's screen, and adb didn't recognize my Kindle anymore.
I tried install/uninstall, downloaded new driver, install Android SDK,.... but don't luck.
All method to unbrick need adb work well.
Help me fix this issue, please. I live in Asia and can't return my Kindle for Amazon.
first - have you read and done the tricks from kfu ?
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
This helped me get out of a brick 4 times I hope it helps you-
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Just to be redundant this is not a 'brick'
Confirming the driver issue- gotta use diff drivers I restored my Win8 to the kfu .6 just to get adb working
Sent from my Amazon Kindle Fire
b63 said:
first - have you read and done the tricks from kfu ?
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
Click to expand...
Click to collapse
The 2nd option help me out to get my kindle fire recognized.
Thanks.
On mine I booted it up to the firefirefire logo and right before the screen flickered I'm not sure if yours does that) I ran a command on the an adb shell command then re ran Kindle fire utilitity's taro installed and it fixed it!
I spent two weeks with a similar problem, finally have everything working. My biggest problem was a USB to micro USB cable that worked fine for charging, but seldom worked for communication between the Fire and my PC. Try another cable.
If your PC beeps when you insert the USB cable, then the cable is probably OK.
Next likely problem is that you don't have ADB installed properly. You can check this by typing adb help at the CMD prompt. (START, RUN, CMD, adb help) If you get a lengthy response, then ADB is installed OK. If you get an error msg, then you need to fix that. Google "How to Install ADB"
If ADB is OK, and you still can't see your Kindle, you probably haven't updated your PATH Variable properly. "How to Install ADB" should include instruction for doing that, but you need to be sure you enter the actual path that your have to the SDK Platform_Tools folder on your PC, not the one described in the video.
Once I managed to get these three thing all working at the same time, things started to fall into place. To most of the people on this forum, these things are probably obvious, but to an old geezer like me every step is a painful learning process.
Good luck
I am stuck with this headache and have stressed my self for hours trying to fix this so now I turn to you guys for help.
My Situation:
I had kindle to 6.2.1 then I rooted it, installed CM7.
after using it for 7+ days there is an update of CM7 by another dev. which had sound in the CM7 so I tried to flash it.
I put it in the SD card and renamed it CM7.zip from Update.zip so I flashed on Custom Recovery to flash the Update.zip later finding out that I renamed it to CM7.zip so I was stuck at Customer recovery bootloop so I enter the command to flash stock recovery to boot as the CM7 required.
so after stock recovery flash on Kindle the Kindle got stuck on the "kindle fire logo"
I think it was stuck in Fastboot.
I tried with KFU and Kindle Fire Unbrick software but the thing is NONE of them detect my kindle
I have tried soo many ways to Get my kindle detected to unbrick it but still no luck
Any help would be greatly appreciated.
Thanks
BUMP!
Still need help with a bricked kindle
BUMP!
Any1?
Kindle Still Bricked and not working >.<
Have you tried Kindle Fire Utility 0.9 to install the latest drivers? After that install Kindle Fire Unbricking Utility 0.1 to unbrick. If that doesn't work, reply with a detailed explanation of what you're seeing and what you have already tried.
This post has links to both and a good alternative option: http://forum.xda-developers.com/showthread.php?p=21232193
Good luck.
Sent from my rough sketch of a Vibrant on a brick.
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
In my case, KFU also stated
status: offline
bootmode: unknown
adb root: No
but it still worked when I tried to change bootmode to 4000.
Also, are you sure your KF is charged enough to start? Try plugging it for a while, then recheck in windows.
b63 said:
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
Click to expand...
Click to collapse
I am running Windows 7 64bit on two of my laptops and windows 7 32 bit on my desktop.
the Kindle logo is not glimmering or flashing so it is in fastboot, I know that much.
I have tried the drivers that came with the KFU 0.9.2 (Newest, I believe)
and Yes the Kindle Fire is fully (if not mostly) charged as I had it on the charger for 6 hours last night.
and No I have not placed it or renamed to c:\kfu
I will let you know in a minute about the results
If it keeps saying Waiting for Device then it's not really in fastboot. I had a similar issue and got it solved through this thread:
http://forum.xda-developers.com/showthread.php?t=1430515
It was stuck in a boot loop and appeared like it was in fastboot, but it would hang up and not respond. You may need to install the fastboot package manually and force it into the right mode. Then you can load TWRP and put it all back together.
If ADB isn't working though, you will need to start by getting that to work. It sounds like a driver issue even though you said you worked on that. You should try the Ubuntu boot method and Firekit to install the fastboot package through ADB. Those are outlined in the link above.
got it ?
if you have a 32 bit machine available that is the better choice cause you don't have to hassle with the 64 bit drivers too
here some information that should clarify the driver things:
in normal boot the device is "android composite adb interface"
in fastboot the device is "android adb interface"
here again all the possible commands to change bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Still no results
I connected my brother's kindle and the computer immediately recognized it and when I connect mine, it doesnt work! :'(
apparently still having the driver issues :'(
any help?
I have tried the KFU driver and that didnt work
I had a similar problem while trying to install TWRP the first time via KFU except I was stuck at the yellow triangle and not the Kindle Fire screen.
First I replaced run.bat in the KFU folder with the one from this post because my Kindle was 6.2.2. Next I installed the drivers for my uknown device in device manager both by pointing the unknown device to where I saved android_winusb.inf and also ran the install_drivers.bat. I got an error saying they could not install.
Next, I followed the steps here
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
Click to expand...
Click to collapse
and when I rebooted my Kindle, it booted normally and appeared as Kindle in Device Manager. So despite KFU not detecting my device, and the drivers giving me problems, I was still able to issue the command in KFU for normal boot mode and held the power button for 30 seconds and it was back to normal. This is on a Windows7 64bit machine. I hope this helps.
Make me the third. Here is my story.
I have lots of rooted and rom'd devices so I'm agreeing that this might be device related and not the drivers? Or maybe specifically the Kindle driver? Since all my other devices work fine.
I bought my kindle and rooted it on day one 6 weeks ago using TWRP. things have been perfect on my KF. I decided to install CM7.1 yesterday morning and it was working great. I just realized I never rebooted it so what Im going to say shortly may have been bound to happen.
So last night I decided to add a google Market update per a link on XDA that stated this can be updated to my current CM7 install. After this my KF just kept going into TWRP automatically. I then decided to load my backup rooted stock room and still my KF just boots into TWRP.
Next I decided to use rootkindlefire's unroot/stock rom to 6.2.1 (drop the bin renamed to update.zip to the SD) and got a TWRP logo screen. I powered off a couple times and now I get a KF logo screen. I tried the 20 second reset and it flashes (Windows XP see the request for a USB device also), but no KF OS loads. Windows is showing Android Phone > Android Composite ADB Interface but the SDcard does not mount files.
I tried:
Kindle Fire utility and it says: Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on. Press any key to continue . . .
SuperOneClick 2.1 says device isn not found
SuperOneClick 2.3.3 just sits at * daemon not running. starting it now on port 5037 * * daemon started successfully *
Stuck on logo option for Kindle Fire unbrick says: Kindle unbrick in progress... adb server is out of date. killing... * daemon started successfully * error: device not found error: device not found Congratulations, your Kindle should be unbricked!
My Sonxy Xperia, Eris, Vibrant and LG470 all work fine when connected.
At a loss here..
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
scrols said:
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
Click to expand...
Click to collapse
I went to another site and was able to get my kindle recognized by my PC (manually edited the drivers and reinstalled) and now Kindle Fire utility sees my device but KFU keeps saying these two lines when attempting to recover and root
adbd cannot run as root in production builds and
- exec '/system/bin/sh' failed: No such file or directory (2) -
First off, I am very much an iOS person, so Android is very new to me. Bear with me.
My brother got a Kindle Fire today, and naturally I told him he should root it, etc. I rooted it and was installing TWRP 2.0 with Kindle Fire Utility. Unfortunately, silly me accidentally closed the CMD window, resulting in...bad things. It won't boot, the computer will not recognize a USB storage device, and it is stuck on the Kindle Fire logo. KFU does not see it either.
Please someone help. Bro will be pissed if I broke his Fire day one...
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Uninstall/reinstall device drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
How?
kona314 said:
How?
Click to expand...
Click to collapse
oh my
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
oh my
snip
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Yeah, I figured it out, I just came back to edit the post haha.
That did nothing.
OK so you've uninstalled and manually reinstalled your drivers, right?
Are you using KFU or just command prompt to change your bootmode?
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
OK so you've uninstalled and manually reinstalled your drivers, right?
Are you using KFU or just command prompt to change your bootmode?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Neither one even recognize a Kindle.
OK, so command prompt it is.
Turn your Kindle off.
In your command prompt type (don't enter)...
fastboot devices
Plug your Kindle into the computer. It should turn itself on.
Wait about 3 seconds and hit enter. It should return a string of numbers.
Then type...
fastboot -i 0x1949 oem idme bootmode 4000
Then restart (hold power button for 30 sec.)
If you don't get a string of numbers it is usually indicative of a driver issue. In which case....Uninstall and manually reinstall your drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
OK, so command prompt it is.
Turn your Kindle off.
In your command prompt type (don't enter)...
fastboot devices
Plug your Kindle into the computer. It should turn itself on.
Wait about 3 seconds and hit enter. It should return a string of numbers.
Then type...
fastboot -i 0x1949 oem idme bootmode 4000
Then restart (hold power button for 30 sec.)
If you don't get a string of numbers it is usually indicative of a driver issue. In which case....Uninstall and manually reinstall your drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I did not get a string of numbers. I tried reinstalling the drivers earlier... Would it make a difference now? And does the fact that I'm using drivers from the KFU have anything to do with that?
Windows is a real pain sometimes when it comes to adb drivers. Try rebooting your computer and check to make sure your device manager says [Edit:] "Android ADB Interface"
Sent from my Amazon Kindle Fire using xda premium
Quick heads up, when you killed the command prompt in the middle of installing twrp 2.0 you probably just ended up leaving the kindle in fastboot mode (which is usually shown by getting stuck at the firefirefire bootloader) basically you need to plug your kindle into the computer and cd to where the adb is in your android folder like you did when you were installing twrp and punch in the command to change the boot mode back to 4000 (normal boot). In fastboot you won't get recognized by adb but when you punch in the command it will go to the kindle because fastboot is actually sort of like adb where there is a file called fastboot in the same directory on your computer that adb is in that lets you interface with your kf.
So basically plug the kindle it, cd to android/android-sdk/platform-tools/ and enter in:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot reboot
One of those should work. Don't worry about adb not recognizing the device, in fastboot mode you won't see it under adb. But the computer sees it regardless.
---------- Post added at 10:19 PM ---------- Previous post was at 10:09 PM ----------
It just occured to me that maybe you were only using the kfu and not the android sdk if not you should look into installing the android sdk and not rellying on the kfu, while it is useful these situations are easier to deal with when you have complete adb access through android sdk, google the android sdk and install it.
If "fastboot devices" doesn't recognize that a device is connected, no amount of other fastboot commands will work; in which case it's usually a driver issue.
Sent from my Amazon Kindle Fire using xda premium
In you command prompt when you type
dir
...do you see fastboot?
Sent from my Amazon Kindle Fire using xda premium
I tried a different computer...same issue.
The fastboot commands did nothing, stalled on "waiting for device."
soupmagnet said:
In you command prompt when you type
dir
...do you see fastboot?
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I did, see above post.
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
isaiahhhhh said:
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
Click to expand...
Click to collapse
You're fine.
By factory cable do you mean a USB cable from Amazon? If so, that's what I'm using... How do I unbrick?
If I'm horribly wrong, please explain.
isaiahhhhh said:
Well the next thing for you to do is get a factory cable as that's the best way to unbrick a brick. And sorry I guess I missed the fastboot post in the thread, I had an issue where I got stuck in fastboot and the method I posted worked but I guess your issue is different than the one I had.
Click to expand...
Click to collapse
Even with a factory programming cable which will put you in fastboot mode anyway, if there is a problem that is keeping the device from being recognized in the first place, it wouldn't do you any good.
So let's stop and start all over with the basics and try to eliminate any possibility of mistakes.
First, get rid of KFU. Uninstall and delete BOTH the adb_usb.ini and android_winusb.inf drivers. Download and install Android SDK. Configure and and install the android and adb drivers that come with the SDK using the tutorial posted here. http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Sent from my Amazon Kindle Fire using xda premium
It's funny.. this is such a simple process, yet it stumps almost everyone on these boards.
It is simply a driver issue. But it is not something you can just explain to people bow to do. It has been my experiance that even when you give a step by step people will not follow it correctly.
However.. I will attempt to at least get your driver issue solved.
First.. open device manager, device manager can be accessed from windows 7 by clicking the start menu and typing device manager.
Once device manager is up, plug in the kindle, wait for device manager to show something. You will see , unknown device, android phone, kindle fire or something similar.
Next, find the folder you downloaded with the kindle fire drivers. They are just adb drivers, but you will need to know their location. If device manager does not show "adb composite device" then you need to do the next steps.
With the driver folder located, right click on the device in device manager associated with your kindle. Click properties, click update driver, click choose driver location manually, browse to that driver folder, here you will have to uncheck the box that says display compatible devices. You should see "android composite device" as an option. Select.it and continue the install.
If you did that correctly, you should now see the fire as an adb composite device in device manager. It will now take fastboot commands.
If when you plug.in your kindle, your hear the USB connect sound, your kindle.is.not.bricked , you just need to get the right driver on it, and that is all user error when it is not done right.
I will update this thread with some screenshots for you , and verifiy my steps. I'm writing this on my phone while in bed and I stilll need coffe
Sent from my ADR6425LVW using XDA
Serinety said:
It's funny.. this is such a simple process, yet it stumps almost everyone on these boards.
It is simply a driver issue. But it is not something you can just explain to people bow to do. It has been my experiance that even when you give a step by step people will not follow it correctly.
However.. I will attempt to at least get your driver issue solved.
First.. open device manager, device manager can be accessed from windows 7 by clicking the start menu and typing device manager.
Once device manager is up, plug in the kindle, wait for device manager to show something. You will see , unknown device, android phone, kindle fire or something similar.
Next, find the folder you downloaded with the kindle fire drivers. They are just adb drivers, but you will need to know their location. If device manager does not show "adb composite device" then you need to do the next steps.
With the driver folder located, right click on the device in device manager associated with your kindle. Click properties, click update driver, click choose driver location manually, browse to that driver folder, here you will have to uncheck the box that says display compatible devices. You should see "android composite device" as an option. Select.it and continue the install.
If you did that correctly, you should now see the fire as an adb composite device in device manager. It will now take fastboot commands.
If when you plug.in your kindle, your hear the USB connect sound, your kindle.is.not.bricked , you just need to get the right driver on it, and that is all user error when it is not done right.
I will update this thread with some screenshots for you , and verifiy my steps. I'm writing this on my phone while in bed and I stilll need coffe
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Hmm... Windows tells me that it won't update the drivers because the ones I have are the same or better...
Hi guys, some times ago I bricked my KFHD, the factory cable just arrived and now I'm struggling in what seemed a so easy task.. I cannot see my device in ADB.. I feel like I've tried everything, I'm desperate :| I think that the problem it's related to the Device Manager window naming the KFHD driver as "Android ADB Interface" instead of "Android Composite..." but I can't really change that.. I also found that uninstalling those drivers make the KFHD appears as a "Tate-Pvt-08" device, which doesn't seem a normal behaviour.. Tried to reinstall almost anything, tried to add the new lines to both "adb_usb.inf" and "android_winusb" (though I'm not 100% certain I've done it properly).. Please help!!
Try updating the Tate device's drivers to the ones in my signature. Those should work, and it is supposed to initially be displayed as a Tate device when there aren't any drivers and its in fastboot mode, after you install the drivers, what you see should be what everything should be called, idk the specifics because I'm typically in Linux so it doesn't always appear like it does in windows.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Tried to update as "Tate.." and now it's recognized as "Android Device" "Android ADB Interface" (just as if I update with standard drivers).. What am I missing? :|
If that's what it does then that is what it is supposed to be called. On another note adb shouldn't see your device in fastboot mode, because you don't use adb commands in fastboot mode, you use fastboot commands. Try running "fastboot -i 0x1949 getvar product", it should return something with Tate in it, if so your fastboot is working just fine.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
You were sooooo right! In fact everything was fine and ready for my kindle to be fixed! Guess I had a really bad tunnel vision experience.. Thx a lot!!