Develop Bugs

!!!(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

[Q]KF bricked, can't restore it

Hello friends, I have a little doubt over here.
I was trying to root my Kindle Fire v6.3.1 to install Google Play and that kind of things by using the Kindle Fire Utility 0.9.6. I chose the Permanent Root with Superuser option and after it rebooted by using Fastboot, it stuck on the boot screen (the one that says kindle fire, the fire on yellow/golden letters).
I had installed the ADB drivers succesfully, as it was recognized by Windows; but I didn't install the TWRP tool. I have tried some things I read on this forum:
1. I powered it off, then opened the KFU, and chose Normal Bootmode. Then I plugged the KF and it turned on automatically. However, my pc didn't recognize the Kindle so KFU keeps waiting the device.
2. I tried turning it off, then on and pressing the power button 3 seconds to activate the recovery menu. It didn't appear.
Also, I'd like to remark that it doesn't turn off immediately. I have to press the power button a few times to do it, but it doesn't follow a pattern.
Thanks, and I'm sorry if something similar already existed. I've searched a lot and I can't find a solution.
PS: As English is not my native tongue, I might have made some mistakes.

seems to be the issue lately with kfu all it does when you select permanet root is get you stuck in fastboot. Did the kfu terminal show anything being pushed to your kindle? Also its very likely that twrp or fff didnt get installed if you did not select those options. Now its just a matter of getting it out of fastboot some info here may help http://forum.xda-developers.com/showthread.php?t=1705063

I'm sure I didn't install neither TWRP nor FFF. Regarding to KFU, all I can remember is that first it rebooted the Kindle in Fastboot Mode, then it downloaded some files I didn't have and then kept waiting for the device.
Now, when I connect the Kindle turned on, it appears as unknown device. When I try to update the drivers using ADB, still names it as 'unknown device'.
Thanks.

Adb won't see it in fastboot try some things in the link I posted there are other approaches here:
http://forum.xda-developers.com/showthread.php?t=1660636
---------- Post added at 06:37 PM ---------- Previous post was at 06:34 PM ----------
When you get tired of messing with windows stupid drivers http://forum.xda-developers.com/showthread.php?p=26491884
In Linux you will use sudo for your fast boot commands if you make a live USB setup

Thanks, I'll check 'em tomorrow!

THANKS, thanks man. I've managed to unbrick it by following the steps listed on this post: http://forum.xda-developers.com/showthread.php?t=1660636

Yayyyy!! Your welcome
Sent from my DROIDX using Tapatalk 2

Just be careful with it now
Sent from my DROIDX using Tapatalk 2

[Q] Kindle Fire is unknown device

Hi, I'm stuck in twrp bootloop. When I connect my kindle to PC (Win7) sometimes it shows unkown device and sometime nothing happens. I've searched the web for solutions for 4 weeks and nothing helped me. I tried mount USB storage in twrp, nothing happens. I just want my PC (Win7) to recognize my kindle, then I will follow the instructions from other threads.
*I have a factory cable.
**If you need more information,tell me.

What do you mean by twrp bootloop? Does it keep booting into TWRP over and over?
You're most likely experiencing a driver issue. Try to follow the directions here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2 and see if it helps any. Just having the KF show up on the device manager is a good step forward, even if mounting usb storage isn't working.

Are you stuck in FFF or TWRP? What color is the Logo?
Drivers are the #1 cause of pain for KF owners trying to root. What steps have you taken to install the drivers? Are you using KFU?
You should be reading: if you havent
http://forum.xda-developers.com/showthread.php?t=1552547
More spesifically this post regarding how drivers should look, and what to do if they dont.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.

Y.Always.Me said:
I'm stuck in TWRP. Every time I load the device I get to TWRP.
I've read the threads you provided, nothing helped.
I did ''add legacy hardware'' in device manager, now I got Android composite ABD Interface shown but it has the code 10 error.
Click to expand...
Click to collapse
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).

Dasanko said:
Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?
The bootloop is very easy to fix - you're most likely stuck in the Recovery bootmode (5001), so having fastboot or ADB set your bootmode to Normal (4000) will solve it, but first you need to sort out ADB/fastboot, which are showing a drivers problem.
As a side note, this probably happened because you are using an outdated FFF/TWRP. When this is fixed, it's in your best interest to update to the latest version of each (1.4a, 2.1.1 respectively).
Click to expand...
Click to collapse
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.

Y.Always.Me said:
I tried, (Have you tried plugging in the KF, uninstalling every single driver relating to Android (even samsung android drivers!), the KF, restarting the computer, and then running install_drivers.bat included in KFU?), but it didnt help.
I have TWRP 2.0.0.
now I dont even get unkown device. What else can I do?? I just want it to show on my PC.
Click to expand...
Click to collapse
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.

Dasanko said:
TWRP 2.0 included FFF, so you can use fastboot -
Issue "fastboot getvar product" and then plug in the KF, see if the fastboot driver is working. Otherwise, you're stuck on a driver problem again.
If it does list one device, then you can go with "fastboot oem idme bootmode 4000" and then "fastboot reboot". That should get you back on Normal bootmode and out of the TWRP bootloop.
Next would be updating both TWRP and FFF to prevent this from happening again, but there's the pending driver issue. I can't really add much more, other than carefully going through the post linked earlier, step by step.
Click to expand...
Click to collapse
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)

Y.Always.Me said:
when I issue "fastboot getvar product" I get('fastboot' is not recognized as an internal or external command, operable program or batch file.)
Click to expand...
Click to collapse
Download KFU and then open a command prompt in the "tools" directory.

Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.

Y.Always.Me said:
Idid, it says <waiting for devive>
I pluged KF, nothing happened.
then I restarted it and nothing happened.
I gess I'm stuck for good.
Click to expand...
Click to collapse
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.

Dasanko said:
Means you have a driver problem, which takes us back to the starting point. Can't do anything else until you manage to get the drivers installed properly, sorry. Alternatively, you can, on a different computer, download KFU and then run install_drivers.bat BEFORE you plug in the KF for the first time.
Click to expand...
Click to collapse
I tried nothing happened.

If you are doing flashes and nothing is working go to mount and make sure there are no checks in the boxes for system and data if so remove them then reflash or restore a backup after restore or reflashing a rom go back and check to make sure those boxes still have no check inside them then reboot I have had frequent errors like this when flashing roms that have the gapp package prebaked into the rom I do not have this issue when flashing gapps seperately

I found that from 20% - 80% battery it takes 12 hours

[Q] Help my kindle is stick on the fastboot mode

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

[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