[Q] Help my kindle is stick on the fastboot mode - Kindle Fire Q&A, Help & Troubleshooting

hi I am using the safe root method of root and trying to flash the FFF and TWRP , in this stib I am stuck in the fastboot mode I unplugged it and reconnect it help plz

Windows version?
How is it listed in Device Manager?
Error message?

I'm having the same problem and had posted a separate thread in the general forum, but coming here I see that I'm not the only one. I was following a guide here on how to saferoot, install FFF and TWRP on a 1st gen Kindle fire and after setting it for fastboot the first time my laptop could no longer see the device and it was stuck sitting at the non-animated "kindle fire" screen. I reset the device, uninstalled drivers and re-installed, rebooted my laptop, all to no avail, so I left it and went to bed. Little did I know that the device wasn't charging while at this screen and just left it plugged to my laptop and went to bed.
Now it seems the device is completely dead, or too dead to boot. The kindle fire screen will display for a couple seconds then the screen goes black, over and over. I used a high power charger(5v 2.2A) instead of the laptop USB port for over 12 hours and it's still just looping. Is there anything that can recover this thing?
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks

g17jimmy said:
I
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Click to expand...
Click to collapse
That is what you wanted.
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
Click to expand...
Click to collapse
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger

sd_shadow said:
That is what you wanted.
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
Click to expand...
Click to collapse
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.

g17jimmy said:
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
Click to expand...
Click to collapse
It will not charge in Fastboot mode, best to flash the twrp and FFF, if it is a stable connection
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Edit: It will not charge in Fastboot mode

It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.

g17jimmy said:
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
Click to expand...
Click to collapse
not sure, but soupkit may only work on 32bit systems

sd_shadow said:
not sure, but soupkit may only work on 32bit systems
Click to expand...
Click to collapse
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!

g17jimmy said:
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
Click to expand...
Click to collapse
tried different usb ports? usb 2.0?

sd_shadow said:
tried different usb ports? usb 2.0?
Click to expand...
Click to collapse
If I leave it hung on the kindle fire screen and plug it in to a different port Windows gives an error (screenshot attached.) If I turn it off (power button 15sec) and then plug it in it comes on and windows sees it properly as an android adb interface, but adb and fastboot still cannot see it.
I haven't looked into messing with it on my mac, I'll check that out, too.

The only live cd I had handy was an old version of Backtrack (BT5r3,) but it's 32bit and still adb and fb cannot see the device, even though the system sees it being plugged in and disconnected.
BTW- on the 64bit Centos 7 side of this system, I installed these packages to make Soupkit at least seem to work:
yum install gtk2.x86_64 gtk2.i686 libXtsc.x86_64 libXtsc.i686 ncurses-libs.i686​
Something about the way the new CentOS works won't allow you to install the i686 libraries without including the x86_64 install at the same time.

Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.

g17jimmy said:
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
Click to expand...
Click to collapse
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot

android tools
I like to have two terminals open. One with root permissions for fastboot commands and a normal terminal for adb. Some distros have a root terminal program, but if you don't, just sudo <gnome-terminal>,<xterm>, or whatever your favorite is.
Thanks to SD_Shadow for all his work. I don't know how he can keep track of all the possible screw ups one can perform rooting and flashing, and get to the bottom of things.

sd_shadow said:
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
Click to expand...
Click to collapse
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.

g17jimmy said:
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
Click to expand...
Click to collapse
another pic

g17jimmy said:
another pic
Click to expand...
Click to collapse
Uncheck all in Mount options
, then try mounting storage
---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------
Also I don't recommend 2.8.x.x, suggest downgrading to 2.7.x.x
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]

OK. I'll go back to 2.7.x and try again.

I tried to downgrade to 2.7.x, but it said "image too large for partition", but while trying to clear that up I seem to have accidentally fixed the sdcard mount. I wiped everything and rebuilt sdcard and now it allowed me to run the install of cm11. What causes the "image too large for partition error"?
Thanks.
Merry Christmas

Related

Kindle Fire is stuck at boot screen, (no animation). Help!

Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...
b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.
updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7
dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.
I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"
I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.
You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.
Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..
I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )
A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..
I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*
Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.
u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick
If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk
In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#

[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) Help bricked kindle fire 6.3

okay so i was trying to root my kindle fire and i didnt get su any where so then i tryed to install cwm and now its stuck at the yellow triangle and it wont go into recovery and it also will not connect to adb i need hellp ASAP
Install drivers as ADB composite with the Android SDK and then use this to change the bootmode
The link you posted is not working due to the period in the URL at the end.
Do not afraid. I have got the same experience Let God bless the search button
http://forum.xda-developers.com/showthread.php?t=1568340
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Click to expand...
Click to collapse
My kindle got the 6.3 update -solved!!
This has got to be one of the fastest ways I have rooted 6.3 kindle update
i went on line here http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html
downloaded the new kindle fire utility and ckick on Install permanent root with super user. got rooted in about 2 minutes with no trouble at all
thanks everyone for your help but i solved it what i was doing was unsing the kindle fire utility trying to instal latest firefirefire but it just sat there and so i just went into the utility and reinstaled the twrp and it booted normal!!
Bricked Kindle
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
ChrisKenison said:
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
Click to expand...
Click to collapse
If you get the yellow triangle logo to come up, then it's probably in fastboot mode. If you reboot it while it's connected to your computer and you get some device detection beeps from Windows, it's likely to be a driver issue. Look here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You might want to read the first post in that thread too.
Watch carefully as the device boots up and you get the yellow triangle logo. If that boot logo comes up and stays there, it's in fastboot. If the boot logo comes up, the screens blacks out, and then the boot logo comes back up (dimmer) then it's either trying to get into recovery or booting into the OS and failing.
I would try setting the bootmode to normal in KFU and when it says "<waiting for device>" reboot the Kindle Fire. Since you have FFF, the fastboot program on your computer will wait for the Kindle Fire's FFF bootloader to get into temporary fastboot and reset the bootmode when the KF is ready.
But, the computer won't even recognize there is a device connected to it
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
And because its not recognized in the device manger, kfu isn't picking it up
Sent from my Galaxy Nexus using xda premium
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
If you can't get the drivers working with the KFU distribution, you'll have a harder time with the SDK. They are the same drivers, but KFU has an updated, Kindle Fire specific .inf file for the driver and also installs the .ini file in the .android folder that you'll need. I don't know what you see in the device manager, but if you don't get one of the devices shown in the post I referred to earlier, I would try another Windows machine. You won't be able to do anything without getting it to detect your KF and load the proper drivers. If you are more adventurous, you could try pokey9000's Firekit (search for it) and try using linux to send it fastboot commands.
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
yea mine is stuck on the firefirefire boot screen
ChrisKenison said:
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
Click to expand...
Click to collapse
Well, if you can't get any of those scenarios to work out, maybe it's a hardware issue. It might be something as simple as a bad USB cable or something more serious within the KF itself. I've never had a problem with Windows or Linux not seeing the KF, so my hands on experience in this regard is limited... my KF has never been broken to that degree. I'm always curious to see what's going on with people's KF when they say nothing works, but my KF has never given me that opportunity.
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
Sometimes in order to install the correct driver you need to delete the original from your computer because it will continue to attempt to revert to the default but beforehand try rebooting your computer and the kindle
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
mistaanime said:
yea mine is stuck on the firefirefire boot screen
Click to expand...
Click to collapse
Run the kf utility again install twrp and fff again

Kindle Fire doesn't show up on ADB or device manager

I'm trying to put Cyanogenmod on my Kindle Fire, but haven't gotten anywhere with it, due to my computer not being able to recognize it. I have ADB installed (have used it with at least 4 other devices).
The issue is that when I connect the tablet to my computer (Windows 7, 64-bit), "adb devices" turns up with nothing. I've read that you have to uninstall the Windows installed Kindle drivers through the Device Manager (even with hidden devices shown). However, my issue is that I can't see the Kindle on the Device Manager. Also, the tablet shows up under "Devices and Printers", so it's not completely unrecognized.
I've also tried installing Kush's ADB drivers, because I thought that would work, but it didn't.
If it is in devices and printers it is in device manager.
Sent from my Amazon OtterX using Tapatalk
sd_shadow said:
If it is in devices and printers it is in device manager.
Click to expand...
Click to collapse
Well, then help me find it in device manager (pictures attached).
Quevvy said:
Well, then help me find it in device manager (pictures attached).
Click to expand...
Click to collapse
So I thought it was showing me hidden devices, but it wasn't. When I view hidden devices, it was listed under Portable Devices. I then right-clicked and then uninstalled the driver to try and install the ADB drivers for the Kindle (ADB setup). When I plug it back into the computer, then it really doesn't show up on Device Manager (but again still on Devices and Printers)
Quevvy said:
So I thought it was showing me hidden devices, but it wasn't. When I view hidden devices, it was listed under Portable Devices. I then right-clicked and then uninstalled the driver to try and install the ADB drivers for the Kindle (ADB setup). When I plug it back into the computer, then it really doesn't show up on Device Manager (but again still on Devices and Printers)
Click to expand...
Click to collapse
Mine show as an android phone.
sd_shadow said:
Mine show as an android phone.
Click to expand...
Click to collapse
While it does show up that way, adb devices returns nothing. I've even tried kill-server and start-server to try and restart it. This means that when I run the Kindle Fire Utility, it doesn't do anything because it can't detect the device.
Reboot pc
Sent from my Amazon OtterX using Tapatalk
sd_shadow said:
Reboot pc
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Had tried it before, but tried it again: ADB comes up with nothing.
I even tried it on another computer, with similar issues. I also tried resetting it to factory defaults, which didn't help either.
Quevvy said:
Had tried it before, but tried it again: ADB comes up with nothing.
I even tried it on another computer, with similar issues. I also tried resetting it to factory defaults, which didn't help either.
Click to expand...
Click to collapse
you unzipped KFU, and not running it still zipped?
sd_shadow said:
you unzipped KFU, and not running it still zipped?
Click to expand...
Click to collapse
I have unzipped it, and am running it from the unzipped location.
check specific drivers do they match this?
Quevvy said:
I have unzipped it, and am running it from the unzipped location.
Click to expand...
Click to collapse
I was able to get the ADB working on a Windows 8 computer, but then when KFU tried to reboot into fastboot mode, it said "waiting for device" for a long time. I think it has frozen. I've tried resetting it by holding the power button for 20 seconds, but I haven't been able to get past the splash screen.
Quevvy said:
I was able to get the ADB working on a Windows 8 computer, but then when KFU tried to reboot into fastboot mode, it said "waiting for device" for a long time. I think it has frozen. I've tried resetting it by holding the power button for 20 seconds, but I haven't been able to get past the splash screen.
Click to expand...
Click to collapse
it maybe in fastboot mode, try restarting KFU a few times, or try command prompt
fastboot reboot-bootloader
if fastboot commands work you can flash Twrp manually
sd_shadow said:
it maybe in fastboot mode, try restarting KFU a few times, or try command prompt
fastboot reboot-bootloader
if fastboot commands work you can flash Twrp manually
Click to expand...
Click to collapse
I tried fastboot, to no avail. Then I ran KFU and during it, Windows said that the ADB device had been recognized, and then the installation of TWRP supposedly went through (have not been able to check it). Then I tried installing FFF, but got the < waiting for device > that was the original problem. This was back on the original computer (Windows 7), but will try on the Windows 8 computer now that the Kindle is back on.
FFF installs with Twrp now
---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------
if twrp installed boot logo should have changed
do you see a press power for boot options?
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
sd_shadow said:
FFF installs with Twrp now
---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------
if twrp installed boot logo should have changed
do you see a press power for boot options?
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
Click to expand...
Click to collapse
Hmm, the boot logo is still the same. I'm going to try and install TWRP again.
Quevvy said:
Hmm, the boot logo is still the same. I'm going to try and install TWRP again.
Click to expand...
Click to collapse
So this is what seems to work the best for me (even though it doesn't work). With the Windows 8 computer, the Kindle is recognized in the ADB devices. I can run KFU and it actually is able to communicate with the device, but then the Kindle stalls when trying to reboot in fastboot mode. I cannot do anything with it in Windows 8. So I connect it to the Windows 7 machine, where I cannot install TWRP, but I can reboot it into normal mode, so it is not bricked, and it is still usable.
As far as I can tell, it never even got to the point where it would have started installing TWRP.
Quevvy said:
So this is what seems to work the best for me (even though it doesn't work). With the Windows 8 computer, the Kindle is recognized in the ADB devices. I can run KFU and it actually is able to communicate with the device, but then the Kindle stalls when trying to reboot in fastboot mode. I cannot do anything with it in Windows 8. So I connect it to the Windows 7 machine, where I cannot install TWRP, but I can reboot it into normal mode, so it is not bricked, and it is still usable.
As far as I can tell, it never even got to the point where it would have started installing TWRP.
Click to expand...
Click to collapse
try manually reboot to bootloader with
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
if that works manually flash TWRP with Fastboot.exe
sd_shadow said:
try manually reboot to bootloader with
[fastboot] stock 6.2.1 fastboot mode without rooting or cables
if that works manually flash TWRP with Fastboot.exe
Click to expand...
Click to collapse
I think my issue was the computer not recognizing the device once it was in fastboot mode. I reinstalled the drivers (which I had done before), but this time they worked on the Windows 8 computer, so I was able to get TWRP and FFF on the device. I am working on getting CM11 on it currently. Thanks for all the help so far!
Done!
Quevvy said:
I think my issue was the computer not recognizing the device once it was in fastboot mode. I reinstalled the drivers (which I had done before), but this time they worked on the Windows 8 computer, so I was able to get TWRP and FFF on the device. I am working on getting CM11 on it currently. Thanks for all the help so far!
Click to expand...
Click to collapse
I got it all working: TWRP, FFF, and CM11. As far as I can tell, there are no issues any more. I haven't tried ADB after putting CM11 on it, but I'm not going to worry about that since I already have the recovery and bootloader installed.

[Q] Kindle Fire 1st Gen Stuck in Fastboot and is not Recognized by the Computer

The kindle is stuck in fastboot mode and will launch immediately into fastboot once the power button is pressed. Also the device does not show up in device manager when connected to a computer. Currently TWRP is installed but I can not figure out the get to the recovery. This started after flashing a custom bootloader while I was converting it into an otterx. Any help is appreciated. Thanks.
N O T E:
I found the solution to my problem. The battery was too low to boot into the recovery so after a full charge the problem was solved
SuperHira said:
The kindle is stuck in fastboot mode and will launch immediately into fastboot once the power button is pressed. Also the device does not show up in device manager when connected to a computer. Currently TWRP is installed but I can not figure out the get to the recovery. This started after flashing a custom bootloader while I was converting it into an otterx. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Stock fastboot or does it say fastboot mode.?
Sent from my XT907 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
Try powering off, and connecting to wall charger.
Sent from my XT907 using Tapatalk
sd_shadow said:
Stock fastboot or does it say fastboot mode.?
Sent from my XT907 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
Try powering off, and connecting to wall charger.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply.
It says fastboot mode and when connected to a wall charger it also goes straight to fastboot mode and is stuck.
SuperHira said:
Sorry for the late reply.
It says fastboot mode and when connected to a wall charger it also goes straight to fastboot mode and is stuck.
Click to expand...
Click to collapse
So you flashed OtterX bootloader? What else did you do? Convert to OtterX partitions? OtterX twrp?
Okay im new to this thread and am (sort of a noob dev). I have the same issue what i did was.
1. download saferoot(installed that worked perfect.
2.went into adb following your guide for twrp and fff while in adb. instead of a (-i) i thought it said (-1) so i put that after 0x1949 i think anyway.
3. noticed what i did then changed it waited a little bit and it just kept saying waiting for device. Then i closed adb and shut it off. rebooted it and opened adb nothing.
It isn't being recognized by windows and it is making the usb connection error sound when plugged in. all that adb says is no device connected. however in my windows devices menu it says other device\kindle? as in a malfunctioned device. i need to try and fix this and i wanted cm11. but if i need to go back to stock i will. Thanks.
Same issue
Relyt2012 said:
Okay im new to this thread and am (sort of a noob dev). I have the same issue what i did was.
1. download saferoot(installed that worked perfect.
2.went into adb following your guide for twrp and fff while in adb. instead of a (-i) i thought it said (-1) so i put that after 0x1949 i think anyway.
3. noticed what i did then changed it waited a little bit and it just kept saying waiting for device. Then i closed adb and shut it off. rebooted it and opened adb nothing.
It isn't being recognized by windows and it is making the usb connection error sound when plugged in. all that adb says is no device connected. however in my windows devices menu it says other device\kindle? as in a malfunctioned device. i need to try and fix this and i wanted cm11. but if i need to go back to stock i will. Thanks.
Click to expand...
Click to collapse
Did you ever get this resolved? I am currently stuck in the fastboot mode, although it doesn't say fastboot on my screen, just the non-animated "kindle fire" boot screen. I have been browsing for a while now and no solution, so hopefully if you found a fix then it is related!
I got rooted, ran some fbmode thing to get to fastboot to install a custom recovery and now I'm stuck here without being able to actually access fastboot. Shows up as "other devices/kindle" with a yellow triangle. Both "adb devices" and "fastboot devices" returns no results. I am now on Ubuntu hoping that the drivers would be as automagic as every other Android device, but still no fastboot/adb devices results.
I'll probably post a new thread by the way, but really hoped you had found a way past this already!
Thanks
uxonith said:
Did you ever get this resolved? I am currently stuck in the fastboot mode, although it doesn't say fastboot on my screen, just the non-animated "kindle fire" boot screen. I have been browsing for a while now and no solution, so hopefully if you found a fix then it is related!
I got rooted, ran some fbmode thing to get to fastboot to install a custom recovery and now I'm stuck here without being able to actually access fastboot. Shows up as "other devices/kindle" with a yellow triangle. Both "adb devices" and "fastboot devices" returns no results. I am now on Ubuntu hoping that the drivers would be as automagic as every other Android device, but still no fastboot/adb devices results.
I'll probably post a new thread by the way, but really hoped you had found a way past this already!
Thanks
Click to expand...
Click to collapse
used install.drivers.bat from kindle fire utility?
windows 7?
Sent from my XT912 using Tapatalk
sd_shadow said:
used install.drivers.bat from kindle fire utility?
windows 7?
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
Actually I followed the guide at Cyanogenmod, but was unable to fastboot so I followed their instructions to manually fastboot and after successfully entering fastboot from running their "./fbmode" script and rebooting, I'm now stuck without being able to contact the device. Nothing shows up under "fastboot devices." I guess I tried on Ubuntu and Windows 8, not Windows 7. I will try installing the Kindle drivers under Windows 7 when I get home later this evening. Thanks.
uxonith said:
Actually I followed the guide at Cyanogenmod, but was unable to fastboot so I followed their instructions to manually fastboot and after successfully entering fastboot from running their "./fbmode" script and rebooting, I'm now stuck without being able to contact the device. Nothing shows up under "fastboot devices." I guess I tried on Ubuntu and Windows 8, not Windows 7. I will try installing the Kindle drivers under Windows 7 when I get home later this evening. Thanks.
Click to expand...
Click to collapse
Hi, did you fix it? if you fixed it, please tell me, I had same problem like you did.
zjwrm said:
Hi, did you fix it? if you fixed it, please tell me, I had same problem like you did.
Click to expand...
Click to collapse
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Sent from my XT907 using Tapatalk
sd_shadow said:
So you flashed OtterX bootloader? What else did you do? Convert to OtterX partitions? OtterX twrp?
Click to expand...
Click to collapse
I flashed the OtterX bootloader and then tried to convert to OtterX partitions. Here something went wrong and now it is stuck in fastboot. The device does not appear in any way in device manager and a live Linux OS does not recognize the device either. Also, when in fastboot it does not seem to run off of the device's own battery, but I can get it to charge the battery if needed by connecting it to wall power.
Thanks for any help
SuperHira said:
I flashed the OtterX bootloader and then tried to convert to OtterX partitions. Here something went wrong and now it is stuck in fastboot. The device does not appear in any way in device manager and a live Linux OS does not recognize the device either. Also, when in fastboot it does not seem to run off of the device's own battery, but I can get it to charge the battery if needed by connecting it to wall power.
Thanks for any help
Click to expand...
Click to collapse
need to get it out of fastboot mode, just keep trying different combinations of power off, connected to pc, power on connected, power on not connected, power on not connected, power on connected to wall charger...
Sent from my KFFOWI using XDA Labs

Categories

Resources