Database Users

[Q] Kindle fire bricked, adb : device not found, help me

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

[Q] Kindle Bricked no adb, not recognized

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

[SOLVED by Linux method by pokey900] Yellow triangle, pc doesnt detect my kindle fire

Hey everybody.
I have tried all options regarding kindle fire utility and no success.
Here's my story:
I have rooted 6.2.1 firmware. ALl worked fine for the past month. Yesterday went online on my kindle fire for about ah hour. Today I tried to turn my device on and twrp screen appeared (though i didnt hold power button for no second) and started installing updates (updates within twrp). But I was very stupid by holding power button and the device was turned off.
When I tried to turn it on again yellow triangle came on and nothing happens. The PC doesn't recognize my device, kindle utility doesn't help.
SO I think nothing will help until my PC detects the KF. In device manager i see no question marks, KFU cant detect the KF.
Please help me somebody

Your KF can be bootable. First you need to connect your KF to your PC and use a general adb Android Composite driver for Windows to communicate to your KF. Once you are able to communicate I.e
advanced devices and you see the SN of the KF, then follow the instruction given in the fastboot thread available under development ofKF.
Regards
Sent from my GT-S5830 using XDA App

how can I "use a general adb Android Composite driver for Windows to communicate to my KF"???
Thank you

me.biturbo said:
how can I "use a general adb Android Composite driver for Windows to communicate to my KF"???
Thank you
Click to expand...
Click to collapse
Plug your device into PC, then follow the instruction from the link below to install and connect your KF
http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/

Hi, firstly I have Windows XP, following the link provided I cannot complete these steps:
Click on Windows (Start at bottom left).
Select Devices and Printers.
I don't see that "Select Devices and Printers. "
I try to right-click on my computer-properties-hardware-device manager.
I don't see kindle there, I don't see any question marks.
So, any ideas?

cruel91 said:
Plug your device into PC, then follow the instruction from the link below to install and connect your KF
jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/[/url]
Click to expand...
Click to collapse
Previously I installed drivers and everything, I gain root access ect, I have TWRP installed. I connected my kindle to PC multiple times without any issues, but...
everything changed yesterday. I guess my device got updated without my knowledge. Amazon is very unfair. They should have implanted an option if people wanted to update automatically or manually, like every Windows or any other OS has got.

Here is what happening now:
I open KFU go to boot mode, then connect my kindle fire and press 1 (normal mode) very fast (it looks like the computer recognizes the device for a couple of seconds only) then triangle disappears and...... I see kindle fire words. I start jumping of joy (for 2 seconds maybe) then the triangle shows up again and nothing happens.
So sad

would try to follow this thread starting at post #2:
http://forum.xda-developers.com/showthread.php?t=1455501
here the prerooted stock roms:
http://forum.xda-developers.com/showthread.php?t=1451747

My issue was solved via LINUX solution found here http://forum.xda-developers.com/showthread.php?t=1430038
To be short:
1. Download Ubuntu 11.10 - Latest Version (about 700MB)
2. On the same ubuntu website foolow step to to create bootable USB stick and follow the steps provided
3. Download file from the buttom of the post http://forum.xda-developers.com/showthread.php?t=1430038 and copy it to the root of your bootabel USB.
3. Now boot your pc from USB
4. Now you should be in Linux
5. Now I quote: "When Ubuntu desktop shows up, press the Windows key on your keyboard and type "term". Hit enter to run the terminal.
In the terminal window, type "sudo /cdrom/fk".
You should now have a prompt that says "[email protected]:~/firekit#"
Now the most important part. SInce my pc recognized my kindle fire for 4-5 seconds only I needed to be very quick. SO this is what I did next:
I typed in the terminal "install_fff_twrp_from_stock" and didn't click ENTER.
Then for the first time during this process I connected my kindle to PC, waited one second and then hit enter for the above command to take effect. A couple of seconds was enough and Now I've got working KF.
Thanks to the guy who wrote LINUX SOLUTION, e.g. pokey9000

[help] kindle fire stuck at yellow triangle/reboot loop

Hi, I've recently rooted my Kindle Fire device using KFU v9.3. After this, I noticed that FFF and TWRP weren't installed. So I used KFU to install FFF and it worked perfectly. I tried to install TWRP and it failed saying
"Oops… something went wrong with the download.
The recovery downloaded is not correct.
Please try the download again."
However, on the second try it worked up until a point where KFU said "Setting Normal bootmode" followed by "waiting for device...". This was when my kindle got stuck on the yellow triangle screen and my computer has not been able to recognize it since.
I have tried to install drivers via the install_drivers.bat file in KFU, however i get the error "install failed (Unsigned)" I tried to use Zombiepirates' Kindle Fire Unbrick Utility and selected "Stuck at logo" but it can't find the device.
Now when I plug my kindle into the computer it just keeps turning on and off and my computer doesn't recognize it.
I'm using a WIndows XP pc and I have access to a windows 7 one if needed.

Try this..
http://forum.xda-developers.com/showthread.php?t=1422832

Have you tried using KFU to change the bootmode back to normal despite your kindle not being detected? After you attempt to change the bootmode to normal perform a hard reset (hold the power button for 30 seconds) and your kindle should be detected. Hope this helps, worked for me for the same issue

I can't, whenever I use "install_drivers.bat" I get an error that says "Install failed (Unsigned)"
Do you know how I should go about fixing this?

BluesHawk said:
Have you tried using KFU to change the bootmode back to normal despite your kindle not being detected? After you attempt to change the bootmode to normal perform a hard reset (hold the power button for 30 seconds) and your kindle should be detected. Hope this helps, worked for me for the same issue
Click to expand...
Click to collapse
Yes I have. It says "waiting for device" and I did a hard reset to my Kindle but still it's "waiting for device" now my Kindle is just shutting on and off rapidly whenever it's plugged into the computer

Is windows blocking the driver? You're on XP right? Try this, then try installing the driver.
Right click on My Computer then select Properties to open System Properties.
In “System Properties” dialog box, select the Hardware tab.
Click on Driver Signing button.
Make sure "block" option isnt checked. That wouldn't let you install any uncertified drivers.

BllgpapaG said:
Yes I have. It says "waiting for device" and I did a hard reset to my Kindle but still it's "waiting for device" now my Kindle is just shutting on and off rapidly whenever it's plugged into the computer
Click to expand...
Click to collapse
The same thing is happening to me. My kindle is rebooting when plugged into the computer, KFU or KUU aren't able to do anything. I'm using Windows 7 but I can't bring up the drivers because the device isn't recognized by windows
any ideas on how to stop this rapid rebooting is much appreciated
Edit
a link to my post on a similar issue can be found here

MasterJoefus said:
The same thing is happening to me. My kindle is rebooting when plugged into the computer, KFU or KUU aren't able to do anything. I'm using Windows 7 but I can't bring up the drivers because the device isn't recognized by windows
any ideas on how to stop this rapid rebooting is much appreciated
Click to expand...
Click to collapse
Update your kindle fire driver with the file in the KFU directory.
Go into Device Manager, find the Kindle fire, update the driver and point it to the driver in the KFU directory. (KFU>drivers>kindle)

_Justin said:
Update your kindle fire driver with the file in the KFU directory.
Go into Device Manager, find the Kindle fire, update the driver and point it to the driver in the KFU directory. (KFU>drivers>kindle)
Click to expand...
Click to collapse
The kindle is not listed in the device manager because after the kindle reboots a few times while connected to the pc, windows stops adding it to the device manager. Is there any way to manually add it and add the drivers?

MasterJoefus said:
The kindle is not listed in the device manager because after the kindle reboots a few times while connected to the pc, windows stops adding it to the device manager. Is there any way to manually add it and add the drivers?
Click to expand...
Click to collapse
I don't know why it's doing that. Is it constantly rebooting? Try another USB port or PC.

from the op of 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
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
hope this helps ...

@b63
THANK YOU! Your post about drivers is the most direct and effective way to install drivers. I wish I could thank you a million times.

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Kindle Fire in FFF Loop
I am also having the same issue as well. Tried running the KFU for unbricking and still nothing as my PC nor my laptop is able to recognize my KF. Not sure what to do. It is constantly just looping while connected via USB and if I disconnect it, it powers off.
Any help would be great.

sounds like empty battery
would try to charge it with the wall charger for some hours
if it turns on if you plug it to the wall charger try to power it off by holding the pwr button ~20sec till it turns off to allow charging

noob needs help with ice cream sandwitch gone wrong!!
Hey ya'll,
So I'm sure you're tired of noobs posting but I just need a little help. I rooted my kindle last night and then tried giving it ics 4. So, I wiped everything (as instructed) and before hand I added the cm09 file along with the gapps. Yet, when I downloaded and extracted these two files they came out as multiple files so I first extracted the files to my desktop. I then transferred the individual files to the root of my kindle. When trying to "install" them , the individual files(which cm09 and gapps had been comprised of ) popped up but I couldn't do anything with them (flash ,etc). So, then I tried condensing all the gapps files into one "gapps" folder and all the cmo9 files into one "cm09" folder and transfer it to the root. Same thing happened. What I think I should haev done is not extracted either and just have sent the unzipped files to the root of my kindle...woops...I am a dumb noob after all! So, now I'm stuck with my kindle and when I turn it on to "normal mode" (not the TWRP) the "kindlefire" insignia pops up at start up like normal but it just sits there like that. Any idea of what I should do and where I can get the files to do it so that I too can have the LIMITLESS POWER OF ICE CREAM!!?? MWAHAHAHAHA...really though..any help ?

would try to boot to twrp - tap mount and mount sdcard - copy the cm9 file to the root of sdcard as instructed - install it with twrp - that should do it
you can install the necessary gapps afterwards - if i remember right it is also described how to do in the op of cm9

i just wanted some help. I rooted my kindle fire and flashed everything had cm7 on it one point and wanted to try miui's rom. I did as instructed but its stuck on the fff screen. Ive also tried as b63 instructed. But every time i connect my kindle it shows up for a brief second and disappears. What do i do? Please help! thank you!

You are 100% correct.
b63 said:
sounds like empty battery
would try to charge it with the wall charger for some hours
if it turns on if you plug it to the wall charger try to power it off by holding the pwr button ~20sec till it turns off to allow charging
Click to expand...
Click to collapse
If the yellow triangle is flashing and the tablet turns of when you unplug it from your computer then the battery is totally dead. I figured that out after 7 hours of frustration!

Yea I had that same issue with mine. I connected it to its factory shipped charger and about an hour later it was turning on and staying on.
Sent from my Kindle Fire using Tapatalk

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