Develop Bugs

[SOLVED] Stuck on Kindle Fire screen... (and tried EVERYTHING)

1) Yes I checked search results.
2) Yes I've googled.
3) Yes I've tried the Kindle Fire Utility, the http://forum.xda-developers.com/showthread.php?t=1356257... links options.
With that being said, here's my issue;
Got a KF a couple days ago...
Yesterday, followed some online instructions to put GO Launcher EX on there to replace the carousel deal.
Followed instructions to the T.
Restarted. Got to "Choose your OS" screen (or whatever it precisely says...)
Picked GO... then it froze.
Now, when it restarts (yes, its the 30 second hard restart), it gets stuck on the Kindle Fire splash screen.
I have tried the above utilities.
I have hard restarted.
I have fully charged and ran the battery dry and tried again.
When I use the utilities, the problem is, my PC will not recognize the Kindle (it see's it as a removable storage device, but it doesn't click over to 'Kindle', and thus the utilities can't interact with the device itself, I suppose).
I've tried different USB ports and connecters (I have 2 regular kindles in the house, too). But I know all the peripherals work through cross-testing.
Essentially, what else can I do? (I got it from WalMart, and they're currently out of stock, so I can't return it till next week, but I'd like it fixed before then if possible)
I've tried several different methods from these forums too, but I *always* hit the same snag... whenever any utility is 'waiting for device', it simply will not find it, because the PC doesn't see it properly. It sees *something* (removable storage) but not as a kindle, and thus won't allow the utilities to interface with it.
Are there any physical things I can do to hard reset it without destroying any warrantys?
Any help appreciated!

there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
first i need to know if you have fff (custom bootloader - yellow triangle) on it ?
then do you have a recovery (twrp) on it ?
what os/bit of computer ?

In kindle utility go to bootmodes and enter normal (4000). Just had that problem last night.

awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
b63 - I hope your right!
no - I do not have the yellow triangle.
no - I do not have TWRP on it, i have tried, but cannot get anything onto the kindle.
my PC is window7, 64bit

Euryon said:
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
Click to expand...
Click to collapse
Do you have all the kf drivers installed on your computer? I know that when I unbricked mine I had all the drivers installed but I had to reinstall them for some reason. If you do not have them I can post them later on tonight when I'm at home. However, I have TWRP installed on mine, and Cyanogenmod 7.2, so hopefully yours is able to connect to your computer.
---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------
b63 said:
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
Click to expand...
Click to collapse
In order to remove the bad launcher, you need to have your device connected to your computer to remove it using adb.

ok so b63 helped me out big time here....
about 2 hours ago we got on a teamviewer session (download this if you want these guys to help you with serious issues!)
took me a minute to figure out how to allow him/her proper access to my screen
anyway
i don't understand the technical stuff
but
what i had done wrong is that i didnt root the KF before trying to install the GO... software (i think)
b63 had a heck of a time trying to discern the problem with me being about as useful as a dead fish, but get there he/she did
after much fanangaling, b63 managed to install the TWRP and ADP on my KF, allowing it to fastboot, and basically allowing it to be read by my PC, and so fixed.
im sure it would have taken b63 all of 5 minutes in real time, but using the quirky teamview and my slow net speed didn't help
still, thanks VERY MUCH to b63 for fixing the **** out of my KF, and being very helpful and patient all along!
thanks

Just wanted to drop b63 a note here that I "thanks"ed their post above - not necessarily for the post but for going above and beyond. The people on these forums are (for the most part) really great. (Too bad there have to be a few who are demanding of the developers to get this feature or that fix done faster without taking into account that the devs do this all in their free time.)

YES, search finally led me here!
Euryon, I have the exact same thing happening with my KF right now.
Do you remember any specifics of how b63 carried out the steps you listed?
b63, any chance you could help me with mine? My issue is identical with Euryon's down to the letter.

Same Problem
Could someone please help me i have the same problem

same problem here! please can someone give a step by step? My fire is unrooted and I did nothing to it except try to install the go launcher and after I selected it as the default launcher it got stuck at the kindke fire logo.

I tried the Kindle unbricking utility but it cannot find the device even after I installed the adb composite interface

also, my fire is not showing up as a kindle - it is showing up as an android device.

rollno88 said:
also, my fire is not showing up as a kindle - it is showing up as an android device.
Click to expand...
Click to collapse
Have you added the fires usb ID to your system?
Sent from my Amazon Kindle Fire using Tapatalk 2

thanks for replying, and I have no clue how to do that. I'll search and get back .
---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------
okay, I already did that by editing the android sdk(as a prerequisite to rooting, which I planned to do eventually) - so when I connect my fire it first shows up as a kindle, and after updating the software through windows and installing drivers through KFU, it comes up as an android device and the interface is adb composite. Now if I try to install TWRP through KFU it keeps switching between adb composite interface and plain adb. And both KFU and KUFU keep waiting but are unable to find my device.

also, my fire alternately shows up as a usb composite device and an android device. PLEASE help

okay I solved it with KFU (finally!) although I have no clue how I did it as I didn'tdo anything I hadn't tried earlier so, managed to install TWRP and then wiped everything and finally my fire could be read - then I deleted go launcher and now my fire is back from the grave
A big thank you to all the helpful posts at this forum - u guys are the best

Same issue
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
edit: when rerunning KFU, i kept getting the message that many execs failed because "/system/bin/sh" directory does not exist.
I don't know if that helps narrow down what might be happening, but I saw that coming up a lot in the cmd prompt.

zeissbickham said:
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with an emphasis on post #2. You need to know what mode your device is in by looking at the device manager and make sure your drivers are loading correctly for that mode. If you can get to TWRP, you can mount your USB mass storage device, copy a new zip file of either the stock software or a custom ROM and flash it.

Thank you. I will be trying this shortly.

fully bricked
I followed the guide and got to a point where the Kindle Fire animation was playing. It loaded up to the unlock screen and then automatically shut itself down - would not stay on when either connected or disconnected. Tried installing a ROM but still shut down. Started the recovery and hit factory reset, still auto shutdown. Tried clearing a partition as described in the tutorial and now it's fully bricked. Will not turn on when connected to computer, to outlet, to another cable.
Thanks for trying to help.

[Q] Kindle stuck at static Kindle Fire logo

Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.

Sounds like it's stuck in fastboot bootmode to this noob. I had the same problem at one point and used command line to fix with the simple bootmode switching commands - can't recall if I used fastboot or adb tools..but either should work. And if I'm reading your post right, you've tried these so this is likely above my meager skill level, heh. You are handling it better than I did, I might add.
If I may point out where you went wrong:
Mattamus Prime said:
After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
Click to expand...
Click to collapse
There are apps in the Google Play store that will temporarily remove your root status so you are able to use services that detect and shut down when root is detected. OTArootkeeper.apk is one that I've heard of.
And don't ever chose to lose fff once you have that as this is your lifeline to unbricking.
Hopefully someone with better chops than I on this will post up - continue with your patient reading and take a little comfort that this is most probably fixable.

First off, I applaud you for trying to figure out and fix the problem yourself using the guides available. Thank you. The information you provided will go a long way to getting the help you need.
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Once you have done that and you still can't change your bootmode, try using recovery to flash a custom rom. It's possible the stock boot image you have has been corrupted. You can use the "mount" function in recovery to push another rom to your sdcard. If that works you can stick with a custom rom like MoDaCo. It's the same stock stock interface with Google apps and services installed and you don't have to worry about OTA updates. OTA Rootkeeper will let you easily switch between "rooted" and "unrooted" so you can take advantage of Amazon's VOD.
And if you still want pure stock you can d/l a new copy of the update and try again.

Thanks for the suggestion. I did try OTA Rootkeeper, but when I went into my Instant VOD, it still had the buttons grayed out. I tried temp unroot, reboot Kindle, and still grayed out, so I assumed Rootkeeper wasn't working for me, thus, the looking for the unroot tutorials.
A little bit of extra information, when I hook up my Kindle Fire, my drivers says Android Composite ADB Interface. When I try to switch to Fastboot to have it switch to Android ADB Interface, it doesn't switch. It just stays as Composite.
Thanks again.

soupmagnet said:
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Click to expand...
Click to collapse
I followed the advice in the Beginners Guide, uninstalled whatever drivers I had, rebooted my comp, then installed the ones that came with the KFU download.
Are there any other drivers I should be looking for?
Also, a little bit of more information, I tried switching to Fastboot through KFU, received some messages to the effect of "system/some file name file not found (2)", (I apologize for not being specific, typing from memory), it then reboots my Kindle Fire, then I execute the commands:
fastboot getvar product
After that, it just says <waiting for device>
In fact, after any command I do in cmd, I get that message. So I believe it may be a driver issue, like was suggested, or my Kindle isn't far enough into the boot process to be found.

It definitely sounds like a driver issue. Keep working on your drivers.
If that doesn't work, you can try it on a different computer OR set up a Linux LiveUSB for issuing adb/fastboot commands.

FIX for Kindle stuck on logo
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
MattamusPrime said:
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Click to expand...
Click to collapse

K_Krish said:
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
Click to expand...
Click to collapse
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.

me too
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
I am stuck at the very same place you are. I was in an endless bootloop after trying to flas back to the Stock Amazon ROM using TWRP. Once i got the drivers sorted out and ADB could see my device i used KFU to "Install permanent Root with Superuser". The KF went to reboot into fastboot and the screen said "waiting for device" for about ten minutes. Now the KF is stuck at the white and orange "kindle Fire" boot logo. Windows will no longer see the KF as an android device. It only shows up as an "unknown device" in the device manager.

Try this
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Ok, I dont know, how to fix this (as I was not in this situation). Try following the steps - Download update.zip through KFU. Connect your Kindle to PC and install the android driver. If your PC detects the kindle copy update.zip file to kindle and try to install that.

sounds like a job for this http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info

dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Im in the same boat you are. I have tried everything stuck on same logo device is recognized in devices as android phone and adb interface but cannot connect to unbrick utility or KFU and doesnt show as a drive either. tried to search devices in cmd using fastboot commands and nothing shows either. I decided to purchase a factory cable today on ebay. Keeping my fingers crossed because after reading everything I could find I think it is my only option.

No, your problem is as "simple" as fixing your drivers so the computer can communicate with the device through adb and fastboot. KFU relies on those two tools to do pretty much anything. Unfortunately, Windows is stupid and is not very effective when dealing with certain USB devices.
In order to, say, install TWRP, you need adb to change the bootmode to accept fastboot commands, and use fastboot commands to overwrite the recovery partition. In the process of going between different boot modes, Windows had a hissy fit and decides not to communicate with the device at all. Hence the need to fix/reinstall the drivers. It doesn't always work out that way and you get stuck where you are right now. A factory cable will put you in fastboot, but it wont make Windows communicate with the device. You can continue to fight with Windows drivers and hope to get lucky, or you could try other, more effective options...
http://forum.xda-developers.com/showpost.php?p=30629067

omg .... I survived a bricking. Soupkit saved me!!!
Somewhere on the many tabs I have open, as I frantically search for ways to unbrick my Kindle fire... I run into " SoupKit" for Linux ... install it... mess around with the Bootloader .. change it to 4002 I believe the value was ... my Kindle that I've been working on for literally 6 hrs is back on! ... now on the figuring out how to root it / remove demo software. SOUPKIT!
E]

About to throw my kindle fire away if I can't get this last effort to work...

Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.

favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?

Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?

favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?

Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium

Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.

Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.

Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?

favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.

Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.

favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.

Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)

You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.

Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app

It's totally fixable.

Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app

Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.

Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)

Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.

favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."

KF2 + 2nd Bootloader + Do's and Dont's?

Hi All,
Today I should be picking up a KF2 (Kindle Fire 2nd Gen) today from a friend. And although I have experience with this device in the past, as I rooted one a while ago, and installed Google PlayStore bits and bobs for another friend... This was a while back.
A few months back, I read somewhere although cannot find it now... That Amazon have rolled out a serious Update to most Kindles (KF2, KF-HD, and possibally KF-HDX) that has updated the baseband/kernel to a certain version. Which prevents Unlocking, and tampering with it could cause the device to Hard Brick...
So was wondering, what is the best procedure to tackle this? Easy method to Root / Recovery??
And what does this 2nd BootLoader actually do?? Does it allow you to DualBoot both original stock Kindle firmware as well as second partition for Custom Roms??
Thanks, Lister

OK first off which kindle do you have, because a kf2 is. Of a 2nd gen kfhd. If its a 2013 kindle fire HD, don't bother with second bootloader because it will just brick it. If it is in fact a kf2 then here's what second d bootloader does. Basically we can't unlock our devices bootloader so 2nd bootloader is a workaround. It allows us to run our own unsigned kernels and custom recovery. Once we have that we can flash a custom ROM like cm. And no no dual booting, Amazon's os is too different from cm to be able to.
To install 2nd bootloader + twrp you must be rooted, suggest kindle fire first aid for that, there's a tutorial in the dev section for kf2 for installing second bootloader + twrp here.
Make sure you check the md5sum of the bootloader before flashing it so you don't risk hard bricking, also I suggest putting the ROM and its gapps on the kindle ahead of time if your are running 10.4.8 because it will boot loop into recovery after the process until you flash a different rom, so its easier to have the ROM o. Ahead of time rather than "adb push" it.
Sent from my Amazon Kindle Fire HD using Tapatalk

Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister

Lister Of Smeg said:
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Click to expand...
Click to collapse
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.

Hi @stunts513,
Just wanted to say THANK YOU SO MUCH!!!
With your help, you have helped me accomplish what seemed like a scary trip to KindleFire Bricks'ville...
But thanks to you, I am all rooted, TWRP'd and ready to go... Shall flash a rom, and sort dads Birthday Pressie now...
Really appreciated, top guy!! thank you... Lister
stunts513 said:
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Click to expand...
Click to collapse

Rooting KF2
Can you give a list of the links that you used to root you KF2?
I've tried to connect to my with ADB but I can't get it to see my device. I can connect my KF2 to my WINXP machine, and transfer files, but I can't get ADB to recognize the device, and I can't get any root options to work. Any help would be appreciated. Ultimately I would like to install a new ROM like CM, but until I can do the basics, I can't get that done.

You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Click to expand...
Click to collapse
Checked and verified that USB debugging is in fact turned on on my kindle.
Settings>>Security>>Enable ADB is ON.
Settings>>Device>>Allow Installation of Applications is ON
I still can't get adb to recognize my device.
I installed ADB from adt-bundle-windows-x86-20140321.zip if that makes any difference.
I had read in the forums that I might need a special cable for fastboot. Is that what I'll need to get?

For what it's worth, I just found and followed this tutorial:
EDIT: Well crap, this forum won't let me post the outside url. I guess if you search for "Setting up ADB driver for Kindle Devices" by David Isbitski" on developer dot amazon dot com, you will be able to find the tutorial
It was very helpful, and it was the first tutorial I've found that actually showed how to install adb windows drivers for the kindle fire.
In windows Device Manager >> Portable Devices >> Kindle is installed, then uninstall Kindle, as they are the wrong drivers.
In the SDK Manager
Go to TOOLS >> Manage Add On Sites
Go to the User Defined Sites tab
add the url found in the tutorial listed above, save and quit that window.
Back at the manager, do "Packages >> Reload" to update the list.
For the kindle fire 2nd generation, I had to expand "Android 4.0.3 (API 15) to find and install:
"Kindle Fire 2nd Generation"
Under Extras, install:
Amazon AVD Launcher (Windows)
Kindle Fire Device Deffinitions
Kindle Fire USB Driver
Once installed go to \extras\amazon\kindle_fire_usb_driver and run "KindleDrivers.exe"
You should then find "Device Manager >> Kindle Fire >> Android Cmposite ADB Interface"
You can then stop/start adb, then do a adb devices.
That is what worked for me!

New to the forum and trying to recognize what you are doing here......
I have a Kindle Fire 2nd Gen with 10.4.8 SW installed. Would like to dump a much newer Android version on it and looking for the correct path.
Any help is greatly appreciated.
Thanks

I tried to install twrp and now my kindle fire hd 8.9 and now it does a boot loop

I tried to install twrp and now my kindle fire hd 8.9 and now it does a boot loop. I've tried to get into the fast boot or use the kindle fire unbrick utility but the reboot doesn't let it get a chance to connect. I believe I used the wrong twrp version and or messed up with a setting in the kindle flash app. I bought a factory/fastboot cable and want to know how to fix this. It's not here yet but I want to know how to fix it despite this. I've tried the majority of methods including the kindle utility. When I go to recovery it just hangs on a black screen. My computer recognizes it but ADB/Kindle Fire Utility do not. my PC recognizes it with a funny name and lets me open it and it's files. It's rooted and I don't know how to check bootloader. Thanks in advanced!

I am new at this myself, I was stuck in a bootloop myself & I to had trouble getting ADB to work, sounds as tho you don't have the drivers installed yet. The part in the directions that seems to be left out is to click on "show all" then click next. I waited forever for the list. So, control panel> device manager> (right click on the troubled device) >update drivers> pick from list> click " SHOW ALL"> hit next then at the bottom> wait for it, wait, waiting. When the list comes up, go down to Google and click it> click next, i think it was, then you should see ADB drivers. If it worked you should now see your device in the device manager under Android device. Now I don't remember where I got the files to bring it back to stock but, I think under one of "DragonFire's" post he had perfect directions to recover back to stock, I think the files might be there as well. I hope this helps you, I too have yet to get a rom to flash right and have used the ADB to reset a few times now. Time for me to try to again