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.

Possibly bricked Kindle Fire....help needed, and appreciated!

A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!

Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.

soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.

soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.

soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?

soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.

Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.

kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.

Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail

I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.

You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?

Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.

soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.

soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?

Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.

soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....

I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.

That will work. Download Ubuntu 10.4

[Q] Bricked Kindle Fire- Stuck on FFF, device not recognized by anything.

Alright folks, I would like to start off with a little introduction:
I'm extremely new to the rooting scene, i've been jailbreaking iphones and ipods since day one. That being said, I probably should have spent more time researching this technique before I went through with it.
Fast forward to today:
I tried rooting my device awhile back, wasn't a 100% successful and I really didn't have the time to work it out. I did have FFF installed and the next window (which i'm not exactly sure what it's called, which allowed me to boot in various moods and such)
Earlier today I got stuck in a boot loop, where my kindle would turn off as soon as i restarted it, and after i selected normal boot mode. I decided it would be a good idea to try a different boot option, so i tried the FF boot, which completely ruined my day.
My current situation is as follows:
I'm currently stuck on the first FFF screen (yellow triangle, with the green light on), i can do nothing else from that screen except hard (cold) reboots. When i plug my kindle in (Mac, windows 7, windows XP), the device is not recognized and i get zero response. I've tried a decent amount of suggestions on this forum, including Kindle fire unbrick (Which can somehow see that there adb is installed, but the bootmode is unknown)
Help out of this current situation would be wonderful. I'm really in a jam here.

Sounds like you are stuck in fastboot and you might have a dead battery too.
You should read this...
http://forum.xda-developers.com/showthread.php?t=1552547
1st post for background information, 2nd post for making sure your device drivers are loading/working, and the 3rd post for fastboot and adb commands. You'll probably need to use fastboot to change the bootmode back to normal.
This one...
http://forum.xda-developers.com/showthread.php?t=1623244
address dead battery problems. You might be affect this by this one as well.

Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?

B4CKlash said:
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
Click to expand...
Click to collapse
What do you mean by recovery screen? Because your first post said FFF and that's your bootloader. If the yellow triangle boot logo comes up and that's all that the display does (doesn't go black and redisplay the boot logo), then it's in fastboot mode. Windows should give you an indication that it's connecting with a series of 2 connection beeps (low->high tone) without a following set of disconnect beeps (high->low tone). The device manager will show something new in the list (this is covered in post #2 in the first URL I pasted for you).
Yes, you need to get something to get recognized by your computer then you need to install the proper drivers for it. Look at post #2 again, and see if you can figure out what device is appearing in the list and get the drivers loaded for it. If you get absolutely nothing, there's something wrong with the bootloader, your USB cable, USB port, or computer in general and it's a bigger problem.
If nothing happens on your computer, find another one and hook it up there. You might also look at this...
http://forum.xda-developers.com/showthread.php?t=1430038
and see if Linux can help you.

I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?

B4CKlash said:
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
Click to expand...
Click to collapse
Windows will be the only one that of the three that will beep at you. There's a better chance of you getting something done with Linux, but it's starting to sound like a bootloader problem to me. There's another user with a similar problem to yours and he's basically where you are now. Both of you might have to open up the case and get it to USB boot mode where you can upload a bootloader to it through USB. Try Firekit and see if it gets anywhere.

KF Stuck at Logo - Sorry

I know this has been covered thoroughly in this forum multiple times, and I have really tried to read as many threads as possible before asking.
I rooted my device months ago and finally got a Nexus 7 and want to give my KF to my kids but wanted it stock first. I must have done something in TWRP that removed my bootloader.
I have tried the unbrick tool, I ordered a factory cable from Skorpn (awesome work btw) and by using KFU, my PC can finally see my Kindle.
The problem I'm having is that none of the commands are working and it looks like the bootloader is either bad or completely gone.
It used to turn on and the logo stayed bright. After I used the factory cable it now turns on, blinks, and goes dim.
All the drivers loaded correctly and KFU see's it online.
When I try to reinstall TWRP through KFU it downloads, but is stuck at waiting for device.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2433 KB/s (510876 bytes in 0.205s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
After reading further, I think I formatted too much and wiped the SD card partition. It doesn't seem like there is a bootloader at all.
Did I miss something in all the reading?
Thanks.

So after doing even further reading I found
http://forum.xda-developers.com/showthread.php?t=1638452
I connected the factory cable and the logo is now staying brightly lit, so I assume it's in FB Mode.
I downloaded TWRP based on the link and FFF, but now I don't know what to do with them.
I went to ADB's site and installed SDK, but I'm not sure how to get the cmd portion to sideload TWRP and then FFF.

I'm doing my best to following along in the instructions and went to the ADB site and installed SDK.
I saved it to my C drive but when I try to do the following, along with "adb devices,
c:\Android\android-sdk-windows>
I get:
'adb' is not recognized as an internal or external command,
operable program or batch file.
Update:
NVM, I had it in the wrong directory.
Once I got that figured out, I did an "adb devices" and no devices came back. Of course I have the factory cable connected and I'm not sure if that matters.
Update:
Ok, now I used a standard USB and it sees my device, but now the logo went back to going dim after reboot.

So it looks like my problem is fairly common, however forum searches don't seem to be helping.
It looks like I wiped too much in TWRP.
Now that I finally figured out ADB, I'm confused about the factory cable.
When it's connected ADB does not see my device but the logo is lit bright yellow. When I use a standard cable ADB sees the device but the turns on and goes dim but the logo is still there.
I've downloaded the ZIP files for TWP and FFF, but I can't seem to figure out how to side load them no matter what I do.

I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.

Copcheck said:
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Click to expand...
Click to collapse
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.

leroy329 said:
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
Click to expand...
Click to collapse
No luck with adding persistence.
I get everything to to boot in Linux, followed all the instructions, but Soupkit still does not see my Kindle.
I've tried my factory cable and a regular cable. No luck
Some has changed though because now my Kindle logo light is solid bright whereas before it would blink and dim.
Good luck to you!

Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.

Copcheck said:
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Click to expand...
Click to collapse
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
When I unplugged the factory cable from the PC and the KF, I could have done 1 of 2 things. Powercycle the KF and hold the power button down to get into TWRP or use a regular USB to side load a ROM and then load it.
Good luck to you, I hope you get it figured out.

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
If you're getting the Kindle Fire orange and white, you haven't installed the new bootloader. Rerun KFU with the Kindle in Fastboot (using Cable) and select install FireFireFire. This will give you the bootloader to reboot to recovery.
Edit: You might as well reinstall TWRP while you're at it, just to be safe.

[Q] Kindle Fire bricked, have factory cable but can't boot recovery, please help!

Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail

farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.

Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!

farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.

I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC

ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.

farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159

ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.

Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.

farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.

Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?

Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?

"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.

jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs