Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Bahamutmaester said:
Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Click to expand...
Click to collapse
ncvikingx97 said:
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you are getting stuck at the ROM's bootanimation and it won't go any further, your system software is broken. You'll have to get to recovery or at least into fastboot mode to fix it. If you have the stock bootloader, you have no easy way to get into recovery, so you'll probably need a factory cable. Read this...
http://forum.xda-developers.com/showthread.php?t=1668159
This probably won't hurt either...
http://forum.xda-developers.com/showthread.php?t=1552547
Thanks
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
ncvikingx97 said:
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
Click to expand...
Click to collapse
I hope you are joking...
http://forum.xda-developers.com/showthread.php?t=1550999
didn't work
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
ncvikingx97 said:
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
Click to expand...
Click to collapse
Download in use Kindle Fire Utility from the development section. Use it install window driver for KF, install TWRP, and reset boot mode. It is the tool for you. You just need to study how to use it.
Hope it helps.
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.
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:
Well I've searched the forums and I can't find anything similar, which leads me to think I'm just missing something really obvious, but this is really frustrating me so I need help.
I'm trying to use the Kindle Fire Utility v0.9.6 to install TWRP and FireFireFire bootloader to my first-gen Kindle, so I can install Hashcode's Jelly Bean. I think I've got the normal drivers working as it shows up as ADB: online, although Boot mode: unknown is also reported. When enter "Install TWRP" it says it's putting the kindle into fastboot mode, but my Kindle seems to have other ideas. It just reboots normally and the utility is stuck on "waiting for device".
I've read one of your fastboot guides, which said that inserting the factory cable then inserting into a computer should activate fastboot mode. Well I tried that with what I think was the original cable, and it just booted normally.
I some small experience with rooting, but basically I'm a noob. I do have some Linux systems handy if they're required.
Any help would be appreciated!
Can't help much since i don't have a kf1..
But i CAN tell you that the ORIGINAL cable is not the same as a factory cable.
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
Can't help much since i don't have a kf1..
But i CAN tell you that the ORIGINAL cable is not the same as a factory cable.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
OK thank you, I didn't know that.
However I think even if I did get hold of one of these factory cables, it wouldn't help much as I need to get this program to work primarily...
any ideas what might be causing adb to be online but boot status unknown?
Personally, KFU v0.9.5 worked better for me.
Exactly the same result with that version, I'm afraid. :crying:
Are you using a USB 3.0 port? Maybe that's why. USB 3.0 is high speed, so maybe the connection got messed up...
How old is your computer?
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!
I'm afraid that's not it... It's a 4 year old mid-range Win7 64 bit laptop. I did root my phone using this computer... I think I'll try using one of the XPs that I have on hand to see if that makes a difference.
Well I've tried on two XP computers and I can't even get the drivers to install.
Oops...
OK thanks for your input guys, you've been really helpful.
I feel really stupid now - my kindle is actually a kindle fire 2. That makes sense. For some reason I thought that a second-gen kindle fire was the kindle fire HD, and therefore mine was a kindle fire.
Sorry for wasting your time.
ben08112 said:
OK thanks for your input guys, you've been really helpful.
I feel really stupid now - my kindle is actually a kindle fire 2. That makes sense. For some reason I thought that a second-gen kindle fire was the kindle fire HD, and therefore mine was a kindle fire.
Sorry for wasting your time.
Click to expand...
Click to collapse
How'd u figure that out?
Well I saw everyone talking about software version 6, and I thought it strange that mine had software version 10. I then did some research and found that there were two kindle fires that look identical. Apparently one way to distinguish is by looking at the software version.
So I picked up a refurbished Kindle Fire 1st Gen for dirt cheap. Tried to root with KFU 0.99. It downloaded the necessary files, and said it would reboot the device, which it did, then got stuck in Fastboot. I have read this forum for about an hour straight and it looks like my best option is to get a factory cable and save myself hours of trying things. Most of the suggestions I find are way out of date, so I'm not sure what the CURRENT recommended suggestions are to fix this problem.
I can't get the Kindle Fire to show in Device Manager since it has been stuck in Fastboot mode. It just shows as "unknown device" in the USB section, even after uninstalling old drivers and reinstalling the ones with KFU, rebooting, etc. Should I just order a factory cable, or does anyone have suggestions for up-to-date things to try? (Today is 6/7/2013) Or will a factory cable not even work if I can't get the device to register in Device Manager anymore?
I have probably rooted 30 devices from Apple TVs to Android tablets and phones. This is the first problem I've ever run into!
Any suggestions are much appreciated. Thank you!
Something similar happened to me. I used KFU and then the Kindle got stuck in the logo screen. I reinstalled the drivers on a different computer and plugged in the Kindle. I just reset the boot mode and it worked fine.
Sent from my XT907 using xda premium
notdeadyet01 said:
Something similar happened to me. I used KFU and then the Kindle got stuck in the logo screen. I reinstalled the drivers on a different computer and plugged in the Kindle. I just reset the boot mode and it worked fine.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Thanks, that works for me. :victory: