I may have messed this one up big time.I have read other threads and they aren't helping. I attempted to root my kindle fire using the kindle fire utility. Something weren't wrong about the time it was installing firefirefire. Now it's not accepting fastboot commands or adb for that matter. It just says <waiting for device>. This is all rather sad to me. I'm like a child who has broken his favorite toy. If someone with a little more skill could help me, that would be wonderful.
Factory Cable
So a factory cable has failed to work as well, although that may be from bad build quality.
Provide more info please http://forum.xda-developers.com/showthread.php?t=1644970
Afterburner anonymous said:
I may have messed this one up big time.I have read other threads and they aren't helping. I attempted to root my kindle fire using the kindle fire utility. Something weren't wrong about the time it was installing firefirefire. Now it's not accepting fastboot commands or adb for that matter. It just says . This is all rather sad to me. I'm like a child who has broken his favorite toy. If someone with a little more skill could help me, that would be wonderful.
Click to expand...
Click to collapse
This is a typical problem with the way Windows handles
drivers. For some reason, when switching from normal to fastboot mode (necessary for firefirefire), the drivers stop working and need to be reinstalled. Sometimes it works smoothly, but most of the time, getting the drivers to work in fastboot mode seems impossible. Just keep working at it
Afterburner anonymous said:
So a factory cable has failed to work as well, although that may be from bad build quality.
Click to expand...
Click to collapse
A factory cable simply puts the device in fastboot mode, which it's already in.
josepho1997 said:
Do a hard reset on you kindle fire whiles its plugged in. Then update the drivers again. Now open up another KFU run.bat and select 1(bootmode) and 1(normal). Now your Kindle Fire should finish rooting.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
TKS Man!
FFF now works in my kindle.
Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
DIRKxxxDIGGLER said:
Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
Click to expand...
Click to collapse
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
guitarman2010 said:
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
Click to expand...
Click to collapse
Its first generation...
DIRKxxxDIGGLER said:
Its first generation...
Click to expand...
Click to collapse
In most cases I've seen of Windows complaining of an unknown device, it seems to be a problem with the bootloader. The fact that you can't even get it to accept commands from the Mac leads me to believe it is the same in your case.
You'll likely need to put the device in USBboot ("shorting trick") and install a working bootloader with Firekit.
"That's a special kind of stupid. The kind that makes me laugh."
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Thanks guys, I'll try that when I get home from work today and report back.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks for your help, it's up and working now with stock kernel and rom. Really appreciate your help!
Sent from my SAMSUNG-SGH-I747 using xda premium
Relikk356 said:
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Click to expand...
Click to collapse
I having the same problem but for Kindle fire hd 7". I tried to use both stock cable and factory cable but it didn't work anyway. Any solution? please help me. Thank you
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me. (I just installed stock Ubuntu to a flash drive with the fk file on root, I'm fairly certain that's all that needed to be done?)
Anyways, my Kindle is unresponsove, and the usbboot trick has yet to work for me. I really want to save this guy. I've heard the KF cannot be completely bricked through software/flashing. I hope it's true! Any help would be greatly appreciated. Thank you.
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
chris_m128 said:
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
Click to expand...
Click to collapse
Thanks fro replying. I'm pretty sure a factory cable only puts it into fastboot if you have a working bootloader. I don't, so I don't think it would work.
I remember an instance where a friend of mine had a broken bootloader, and we used a factory cable to restore it, this was on the kindle fire. we had to first reflash the bootloader. I hope this is possible here.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
but you'll have to ask someone with more experience than me sorry.
jophish said:
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me.
Click to expand...
Click to collapse
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
Click to expand...
Click to collapse
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
jophish said:
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
Click to expand...
Click to collapse
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
jophish said:
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
Click to expand...
Click to collapse
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
plinders said:
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
Click to expand...
Click to collapse
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Same Here..
I was thinking that all kindle fire are the same... installed fire fire fire using KFU and device got bricked....!
Hope someone here could help us get our devices up and running again...
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
jophish said:
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
Click to expand...
Click to collapse
I am sure they can figure it out. Can you boot into TWRP?
If so, you can still recover...
Dame problem
plinders said:
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
Click to expand...
Click to collapse
Same problem dude, did you fix it?
i.robert said:
Same problem dude, did you fix it?
Click to expand...
Click to collapse
Not yet I'm afraid. Everything I tried so far hasn't worked.
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
No, Absolutely nothing. I really would like to get this working.
jophish said:
No, Absolutely nothing. I really would like to get this working.
Click to expand...
Click to collapse
same here we need a new firekit for the kf2
Help..
any updates on the fix? I hope someone out there could help us revive our bricked kindle fire 2... :angel:
kindle fire 2
flashed wrong bootloader (fff)
no power
no lights
no adb
shorting trick is not working for me :crying:
hard bricked kindle fire hd 7" fastboot cable flashing 8.9 bootloader,recoveries,ect.
So i had purchased a fastboot cable to unbrick my kindle fire hd 8.9 out of a boot loop. adb read great, ran fastboot and got it restored finally using kfhd tool. then started to attempt to load 2nds bootloader and twrp and now it seems to be hard bricked! won't even turn on or anything connected with the fastboot cable now and was working flawlessly earlier. major help would be appreciated ;please please--------------------------
ii
edit:- so what i thought was the 8.9" kindle fire hd is actually now that ive opened into hardware had come to be the 7" Kindle fire hd . So i believe the source of my hard brick via the fastboot cable (that was working so i should have known right there) trying to flash 8.9" bootloader, and recoveries, and imgs. Is there anyway out of this mess? the only avenue i could think to even work would be attempt the linux usbboot shorting trick withg the command prompts. only problem im having is find a tutorial or a pic confirming what i support to short on motherboard. all i can find is on different hardware with the kindle fire hd 8.9". ive ran the kfhd utilities but just runs as cant not load img or device not reconized. help..........
Naughtybutbritt said:
So i had purchased a fastboot cable to unbrick my kindle fire hd 8.9 out of a boot loop. adb read great, ran fastboot and got it restored finally using kfhd tool. then started to attempt to load 2nds bootloader and twrp and now it seems to be hard bricked! won't even turn on or anything connected with the fastboot cable now and was working flawlessly earlier. major help would be appreciated ;please please--------------------------
ii
edit:- so what i thought was the 8.9" kindle fire hd is actually now that ive opened into hardware had come to be the 7" Kindle fire hd . So i believe the source of my hard brick via the fastboot cable (that was working so i should have known right there) trying to flash 8.9" bootloader, and recoveries, and imgs. Is there anyway out of this mess? the only avenue i could think to even work would be attempt the linux usbboot shorting trick withg the command prompts. only problem im having is find a tutorial or a pic confirming what i support to short on motherboard. all i can find is on different hardware with the kindle fire hd 8.9". ive ran the kfhd utilities but just runs as cant not load img or device not reconized. help..........
Click to expand...
Click to collapse
This is the HDX forum. not the HD. You will probably get better answers from someone actively working on THAT device, than you will here. You really should never mess with things you don't fully understand & you should NEVER use tools designed for older models or other devices. Older devices have different hardware in many instances, so everything is different. Flashing bootloaders or firmware for another device is often time a fatal mistake. I could be wrong, again check in the appropriate forum, but unless you have a custom recovery or safestrap installed, you are likely up a creek, short of jtag & to be honest, with the way the newer devices are, even that is a long shot.
The shorting trick doesn't work on the HD models, well it does but it doesn't, we need a xloader or uboot(can't remember which) that is signed by amazon when you start the process because the processor is a high security model. Only amazon and TI have those files and they aren't public. If it is hard bricked the best bet is to wait until we get the pinout for a 7"HDs emmc, once we do that you can solder a USB sdcard reader to the motherboard of the kindle and reflash the boot loader from linux and it will run again, so far we can do this on the kf2 and the hd8.9" model but we still are waiting for the 7" HD pin out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app