Develop Bugs

[Help!] Bricked Kindle Fire/ Won't even start

After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.

That doesn't sound good. Press and hold the on button for like 20 seconds and see if anything happens.

jaredkzr said:
After I rooted my kindle and installed adw.launcher everything was going fine. I rebooted my kindle and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working. Even when I plug it in the orange charge light doesn't even come on. I need help badly and I would prefer not to have to send it in to get a replacement. The entire reason I created this xda account was to fix this. Please I need help.
Click to expand...
Click to collapse
Try the Hard reset option as explained by GBH2 and if it doesn't help, then please list down what exactly did you do to root your device, stock FW version etc.
Sent from my GT-I9100 using XDA App

I have already tried the hard reset but to no avail. I have no idea what happened to it. I think I will just have to get a replacement. I followed instructions off of mobilemag and of course I can't place the link in this post.

I literally just had same issue... holing power button for 20+ seconds did the trick here.
Running CM7 w/ MAC address fix.

mine's bricked too
I also have a bricked Kindle and not sure what to do about it.
I had my KF rooted and working. Then, I followed these instructions to get a better keyboard. In short, I edited one row of the secure table in settings.db, trying to enable Hackers Keyboard. I followed the instructions very carefully, including changing permissions. When I rebooted, it stuck at the kindle fire logo, and it is still stuck there.
I can connect via adb, but can no longer burrito root. Can't run 'su'. I'm searching these forums trying to figure what to do next.

do you have twrp available ?
if not you could follow this post: http://forum.xda-developers.com/showthread.php?t=1414832

fixed
Thanks. I found that thread via http://forum.xda-developers.com/showthread.php?t=1356257&page=61 and it saved the day.
I was able to fastboot, twrp, and eventually solve my problem.
I had updated settings.db, then used `adb push` to put it in the right place. Then, I chmod-ed it as the instructions warned. However, it was owned by root not system! With twrd, I was able to get back into adb. Chown-ing and chgrp-ing that file to system solved my problem.
(Unfortunately some of the other stuff I did along the way broke a few apps... anyway I'm happy to have a working KF again.)

good to hear !!!

Did you ever get your KF to work? I can not get mine to turn on after KFU 0.9.5 used to do perm root. Now nothing works at all

Kindle fire wont power on /boot
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue

hi vertcam9 how do you force boot it please.
omniac

omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
I think my issue is a busted USB port already.

ok thanks tried that, but it is deader than that.
omniac

Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.

Seriously people...
vertcam9 said:
I'm facing the same issue here, i have FFF 1.4a and TWRP 2.2.2.1 installed and JB 4.2.1 from twv. However i noticed whenever i pressed reboot from menu or power it off, i cannot turn it on again.
Luckily i have an OTG cable which help me force boot it, but i want to solve the issue coz i dont want to use the OTG cable always to turn it on.
Note: Holding power button for 20secs did not solve the issue
Click to expand...
Click to collapse
vertcam9 said:
Hello, i have a Factory Cable (USB cable) with a different pin configuration. Basically if you have a working bootloader, you just plug it in (with a PC) and it will go to the FFF screen.
Click to expand...
Click to collapse
Normally I would assume you had a 2nd generation device and tried to modify it, but I see your first post was made back in April and then edited two days ago?!? Is this a new problem or the same problem you had eight months ago?
I'm pretty sure your USB port isn't bad and you just have a broken bootloader. If you have a 1st generation device, the Firekit w/shorting trick to put the device in USBboot will do the trick.
omniac said:
hi vertcam9 how do you force boot it please.
omniac
Click to expand...
Click to collapse
omniac said:
ok thanks tried that, but it is deader than that.
omniac
Click to expand...
Click to collapse
How about some details...better yet, start a new thread...In the Q&A section.
Smmoph said:
Dead is right on the mark for mine also. With pc never detecting my CM9 , I updated my TWRP to v2.2.2.1, in hopes to go to CM10
And for first time saw *bootloader* as an option in TWRP . Screeching halt!!! Beware.
Click to expand...
Click to collapse
This sounds like a completely different problem. You should probably start a new thread as well...In the Q&A section.

I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!

samiultahir said:
I have the exact same problem!!!!!!!!!
After I rooted my kindle, everything was going fine. My kindle turned off and when I rebooted, it got stuck in a bootloop. I tried to fix it by reflashing a fresh image and out of nowhere it refuses to start. Absolutely nothing shows up at all. The screen doesn't come on, the logo, nothing. The battery was at 75% when it was working.
This has been the problem since 5 months...
I am using a kindle fire 5th generation and don't have a factory cable.
Can somebody plz help!!!!!!!!!!!!
If so, can someone post a link for a cheap factory cable however I really don't want to use/buy one.
Thanks!
Click to expand...
Click to collapse
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs

sd_shadow said:
this is only for Kindle Fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1028 using XDA Labs
Click to expand...
Click to collapse
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:

samiultahir said:
Oh Thanks Anyways but do you know a fix for this?
BTW I think my device is hard bricked. :crying:
Click to expand...
Click to collapse
post in the correct forum
Sent from my sailfish using XDA Labs

[Q] Might be bricked.

I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.

And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.

Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?

I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!

How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.

Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed

Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?

Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.

To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034

soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.

Can you boot into recovery? Do you know how?

soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore

Guess I will be buying a new one.

TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.

soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.

fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109

soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.

fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375

soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.

Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".

[Q] Need Some help with a bootloop

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.

[Q] Kindle Fire Bricked??(Hopefully not)....

i had rooted my kindle with firefirefire by KFU and had accidentally erased the SDCARD, so i found a new gingerbread kindle fire OS.zip online no problem and installed it, had it up and working again, all fine and dandy.
Then everytime i booted it up it would always come up with the whole blue "kindle fire" and "press power button for boot options" screen and i decided i didnt want twrp on my kindle anymore and that i wanted to return it back to factory condition. so i looked up on youtube how to de-root you kindle fire and i referenced myself with this video:
http://www.youtube.com/watch?v=AzbmxV45x10
i downloaded the update.zip and flashed my kindle with twrp (just like it said) and everything went fine. however the next time i turned it on (well when it turned itself on after the update) it just got stuck in a boot loop... it will display the factory setting "kindle fire" with the red color, not twrp's blue "kindle fire", then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo) then it will shut off. after about 5-10 seconds of being off, it will boot itself back on and repeat the same cycle again.
i have tried to hook it up to the computer, but it only shows up in "My Computer" for about a millisecond. thought maybe it was just my computer that couldnt load fast, so i tried a different computer, same thing.
i have tried holding the power button down for anywhere between 20- 60 seconds, still nothing.
i have tried opening the KFU and going to install firefirefire and letting it load to the point of <waiting for device> and then plugging in my device, still nothing.
i am extremely grateful of any ideas and solutions you guys/girls can offer and help me out. i loved my kindle fire quite dearly and used it everyday. i am willing to accept the fact that i have a $200 brick, but will do just about anything to fix. please help http://forum.xda-developers.com/images/smilies/frown.gif

Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.

James.Whaton said:
it will display the factory setting "kindle fire" with the red color...then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo).
Click to expand...
Click to collapse
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.

soupmagnet said:
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.
Click to expand...
Click to collapse
i do have a rocketfish cable that is a step up from the factory cable, always worked in the past whenever i used it for the kindle, i can get it to charge, just not stay connected to my computer... i dont quite know why this happened because all i did was install that update... not quite sure why it did this... any ideas on how to get it back to normal?

Thepooch said:
Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.
Click to expand...
Click to collapse
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?

James.Whaton said:
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?
Click to expand...
Click to collapse
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864

soupmagnet said:
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864
Click to expand...
Click to collapse
my computer will detect the device but only for a second, because it never fully loads it is only in the booting mode.my computer cant see it due to the kindle not being available. where would i purchase a foctory cable becuse by the way you guys are talking about it it sounds like the cable isnt just a cable but it can make it boot differently... the cable i have now connects it to the computer very easily and just fine, and the only reason that it isnt working now is because the kindle is in a boot loop.

http://forum.xda-developers.com/showthread.php?t=1392693 post 9 James the factory cable will force the device into fastboot so you can use kfu to resend fff and twrp to the device in order to do a full wipe and flash a new system.

forgive me for being curious, but how exactly does this factory cable work? i know that it isnt you who is making them, but i would hope that if you are suggesting to use it you would understand how it works... i have my cable here so why go buy a new one instead of just doing it myself? it seems like it is just a simple soldering job, which i could handle. after a little research it looks like i need to connect pin 1 to pin 4 which wouldnt be all that difficult to do by myself.
could anyone tell me how i could simply create on myself. yes ive read this post:
http://forum.xda-developers.com/showthread.php?t=1392693
but they never quite explain in detail what i need to do to make one. i watched a couple videos on youtube to figurre out what i had to do, but i still would like a more professional opinion as to what i need to do and as to how it works. thank you

lost OS
i have done every thing to the T to get OS back. when i down load the new OS and place it in the kindle updates folder it does not show up in TWRP when I unmount the KF.
suggestions> I have been beating my head on this since some screwball decided to pay with it.

[Q] Kindle Fire 2 completely bricked after flashing wrong bootloader.

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: