Database Users

I bricked my KF PLEASE HELP

I installed the drivers and everything worked fine. I then rooted it. No Problems. Then I go to install a recovery with Kindle Fire Utility. I press 5 and then enter. It said it installed it and would restart. It restarted into the yellow triangle and now it says device not recognized. I tried to run the Unbrick utility but my PC no longer recognizes my KF. Please help, I bought it today and immediately started rooting. I rooted my Evo without a problem but Idk what to do.

Read through the Unbrick Utility thread. The answers are there.
Sent from my Kindle Fire using xda premium

borborpa said:
Read through the Unbrick Utility thread. The answers are there.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Ok, I have it unbricked. I just need to figure out how to get it to recognize my device

rkeenan said:
I installed the drivers and everything worked fine. I then rooted it. No Problems. Then I go to install a recovery with Kindle Fire Utility. I press 5 and then enter. It said it installed it and would restart. It restarted into the yellow triangle and now it says device not recognized. I tried to run the Unbrick utility but my PC no longer recognizes my KF. Please help, I bought it today and immediately started rooting. I rooted my Evo without a problem but Idk what to do.
Click to expand...
Click to collapse
your KF is OK. Configure your PC to use android composite driver to get adb working and use the following commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk

Yeah, I had just regular ADB drivers before and then I saw in the unbrick thread to use ADB composite. That fixed all of my problems. Thank you. I now have ICS on my KF

U should chang the bootmode to 4000
better use the factory cable

[Q] Question on Kindle Fire Utility

I just got my KF tonight and decided what the hell to go ahead and root it. I read the information in the development thread on the Kindle Fire Utility (ver 0.9.3).
I installed the driver files on Windows 7, no problems, device manager shows my device as a Kindle and not ADB composite.
Once that was done, I started the KFU and got my command prompt stating that it was resetting ADB and waited and waited.
I then got the messages after about 5 minutes stating that the daemon had been started successfully.
I then kept waiting and waiting and waiting for around 15 minutes.
I am not a complete noob to rooting, I rooted an OG Droid and my Samsung Fassy. My question is how long is it suppose to take to get the number prompts in KFU or am I totally missing something here
Please any assistance is greatly appreciated.

It should take few seconds. Apparently, your PC configuration for USB driver is not correct.
I recommend before using KFU that you test the interface using adb. Start with adb devices command. If you get a response from KF with its s/n then you go a he'd and use KFU to root, install bootloader fff, and recovery such as cmw or twrp and finally select a ROM to install.
Sent from my Amazon Kindle Fire using Tapatalk

Well I rechecked through ADB, got this as the feedback. I uninstalled and reinstalled the drivers, device mgr still showing as Kindle USB device.
C:\Users\Ninja\Desktop\ADB>adb devices
List of devices attached
2CBC002600000001 device
Am I suppose to be seeing this output or the name of Kindle on the output?

Yes, you do have ad working.
Now you can root your KF.
Sent from my Amazon Kindle Fire using Tapatalk

the last version of kfu (0.9.3) has a small bug in run.bat
would try to use the run.bat from here:
http://forum.xda-developers.com/showpost.php?p=23536888&postcount=1007

I closed the command prompt while installing TWRP. Please help me.

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...

Kindle Fire 7" wont recognize in the KFU

Ive been trying everything to get it to get noticed by the KFU, it just wont work. My computer has its drivers installed, it registers on the computer... I look in the task bar and it says connected as media device and it also says low powered usb whenever its connected to my pc. I dont know if that is the issue or not but ive tried each usb port and none say anything else. I really want to root this tablet and put jellybean on it but it just doesnt seem to want to work for me >.<

Kindle Fire Utility v0.9.6
imadrummerlol said:
Ive been trying everything to get it to get noticed by the KFU, it just wont work. My computer has its drivers installed, it registers on the computer... I look in the task bar and it says connected as media device and it also says low powered usb whenever its connected to my pc. I dont know if that is the issue or not but ive tried each usb port and none say anything else. I really want to root this tablet and put jellybean on it but it just doesnt seem to want to work for me >.<
Click to expand...
Click to collapse
DO NOT USE KFU ON THE KINDLE FIRE HD 7"
This utility was designed for the original Kindle Fire, not the HD.
If you push it, you WILL Brick (Break) the Kindle Fire 7" HD.
At this point there is only one Bootloader that works on the KFU HD,
that is SafeStrap, although the developer has it on hold at the moment.
Having said this, there is no easy way to upgrade the Kindle Fire HD
to JellyBean - we were able to port over JellyBean but over 50%
of the applications did not work. So, we are at least 1 year away from
posting custom ROM's. Do not try it with SafeStrap, it is a waste of time
at the moment. Sorry........

prokennexusa said:
DO NOT USE KFU ON THE KINDLE FIRE HD 7"
This utility was designed for the original Kindle Fire, not the HD.
If you push it, you WILL Brick (Break) the Kindle Fire 7" HD.
At this point there is only one Bootloader that works on the KFU HD,
that is SafeStrap, although the developer has it on hold at the moment.
Having said this, there is no easy way to upgrade the Kindle Fire HD
to JellyBean - we were able to port over JellyBean but over 50%
of the applications did not work. So, we are at least 1 year away from
posting custom ROM's. Do not try it with SafeStrap, it is a waste of time
at the moment. Sorry........
Click to expand...
Click to collapse
Woops, I have the regular kindle fire, sorry for the misinformation

Follow Up
imadrummerlol said:
Woops, I have the regular kindle fire, sorry for the misinformation
Click to expand...
Click to collapse
imadrummerlol,
No worries, I just did not want you to Brick the Kindle.
If you have the original Kindle Fire and not the Kindle Fire 2 then KFU
should see it. Do you have ADB Enabled on the Kindle Fire?
Did you install these USB Drivers: https://dl.dropbox.com/u/54456659/usb_driver.zip
If yes, you should see Android Composite ADB Interface in the Windows Device
Manager. If not, this is your problem, update the Kindle Driver using our driver.

prokennexusa said:
imadrummerlol,
No worries, I just did not want you to Brick the Kindle.
If you have the original Kindle Fire and not the Kindle Fire 2 then KFU
should see it. Do you have ADB Enabled on the Kindle Fire?
Did you install these USB Drivers:
If yes, you should see Android Composite ADB Interface in the Windows Device
Manager. If not, this is your problem, update the Kindle Driver using our driver.
Click to expand...
Click to collapse
I have ADB mode enabled, and i believe i have those installed if thats what the driver installer in the zip file did. Is it an issue that my kindle says all my usb ports are "low powered"

USB Port Warning
imadrummerlol said:
I have ADB mode enabled, and i believe i have those installed if thats what the driver installer in the zip file did. Is it an issue that my kindle says all my usb ports are "low powered"
Click to expand...
Click to collapse
imadrummerlol,
That is normal since the Kindle uses a high powered USB Charger. You can safely ignore the error.
If you look in the Windows Device Manager, do you see Android Composite ADB Interface?
Download this utility: https://dl.dropbox.com/u/54456659/ADB%20Update.zip
Save the ADB Update.zip to your desktop. Unzip ADB Update.zip to ADB Update on your desktop.
The open the folder. While your mouse arrow is hovering over the ADB Update folder, press the Right
Click Mouse Button, Choose "Open a command window here". Windows will open a Command Prompt.
You will be at the root of ADB Update. Type the following commands (pressing Enter after each one):
Code:
adb kill-server
adb start-server
adb devices
Do you see a serial number after adb devices?

prokennexusa said:
imadrummerlol,
That is normal since the Kindle uses a high powered USB Charger. You can safely ignore the error.
If you look in the Windows Device Manager, do you see Android Composite ADB Interface?
Download this utility:
Save the ADB Update.zip to your desktop. Unzip ADB Update.zip to ADB Update on your desktop.
The open the folder. While your mouse arrow is hovering over the ADB Update folder, press the Right
Click Mouse Button, Choose "Open a command window here". Windows will open a Command Prompt.
You will be at the root of ADB Update. Type the following commands (pressing Enter after each one):
Code:
adb kill-server
adb start-server
adb devices
Do you see a serial number after adb devices?
Click to expand...
Click to collapse
I dont see any numbers, and i tried to reinstall the drivers for the kindle and now windows wont even recognize that i have them on my computer anymore.... Uhg this is becoming such a headache haha

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
imadrummerlol said:
I dont see any numbers, and i tried to reinstall the drivers for the kindle and now windows wont even recognize that i have them on my computer anymore.... Uhg this is becoming such a headache haha
Click to expand...
Click to collapse
imadrummerlol,
Go to our How to Root the Kindle fire using Windows Noob (Easy Edition.
We have a video I think you will find helpful, it takes you through the entire
process and Yes, it does work on the original Kindle Fire. I can be 99% sure
you have a driver problem. The links to this series is below. Keep us posted.

Check your firmware version. I got a Fire for Christmas and tried to root unsuccessfully until I noticed I was on 10.2 firmware which told me I had a KF2. It is exactly the same in every way except it has a 1.2ghz dual core processor and 1gb RAM instead of a 1ghz dual core and 512mb RAM. Aaaaand it has a locked boot loader. So you can root, but no custom recovery, no custom ROMs. Yet.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Kindle Fire 2 vs Kindle Fire
LegendaryCatalyst said:
Check your firmware version. I got a Fire for Christmas and tried to root unsuccessfully until I noticed I was on 10.2 firmware which told me I had a KF2. It is exactly the same in every way except it has a 1.2ghz dual core processor and 1gb RAM instead of a 1ghz dual core and 512mb RAM. Aaaaand it has a locked boot loader. So you can root, but no custom recovery, no custom ROMs. Yet.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
LegendaryCatalyst,
Very good point, many think they have a plain old Kindle Fire when indeed they have a Kindle Fire 2 and
if this is true, you can Brick the Kindle Fire 2 when using the KFU Utility on the Kindle Fire 2. The KFU
utility is only designed for the ORIGINAL Kindle Fire, about 6-8 Months old now.
Thank you for the feedeback.

LegendaryCatalyst said:
Check your firmware version. I got a Fire for Christmas and tried to root unsuccessfully until I noticed I was on 10.2 firmware which told me I had a KF2. It is exactly the same in every way except it has a 1.2ghz dual core processor and 1gb RAM instead of a 1ghz dual core and 512mb RAM. Aaaaand it has a locked boot loader. So you can root, but no custom recovery, no custom ROMs. Yet.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
That is most likely the issue then, its 10.2 firmware on mine haha

Kindle Fire 2
imadrummerlol said:
That is most likely the issue then, its 10.2 firmware on mine haha
Click to expand...
Click to collapse
You are lackey that you did not Brick the Kindle Fire 2!
Well, I am glad someone figured it out before you pushed the Bootloader
to the breaking point. By the way, welcome to XDA!

The usual ADB driver issue.. help please!!

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!!