Develop Bugs

[Q] stuck at yellow triangle, can't install drivers. I hope I haven't bricked it.

I'm going to preface this with: I am a visual learner and kind of an idiot, so I went with the option I found that seemed the simplest.
Okay, I tried to root my kindle fire using the method found here: (rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire-6-3-1) because I wanted to try and flash CyanogenMod onto it, and now it's stuck at the yellow triangle push power for recovery mode screen. From what I've read when you push the power button to boot into recovery it's supposed to turn orange, but mine has never done that it's always either had the green power light on or the kindle is totally off.
For a while it was showing up like the picture in the Kindle Fire for Beginners thread (second post) but now it shows up like this (i.imgur.com/MKioa.png) went to delete the device to try and reinstall the drivers. I was told from several of the other yellow triangle threads here on xda that there was supposed to be an option to delete all the drivers when you go to uninstall, and there was the first time I tried to do it but now it doesn't give me that option (i.imgur.com/Ofcg2.png) also KFU tells me that ADB isn't installed (i.imgur.com/y3TkE.png)
For a while my computer wasn't even recognizing that it was connected at all; thankfully a reboot of the computer fixed that problem, but now it's only showing up as a USB Composite Device and I can't install any drivers onto it (i.imgur.com/yHSJV.png)
I've tried power cycling it, rebooting my computer, reinstalling the drivers (before it quit letting me do that), and reading every single related forum post I can find. So far nothing has worked.
I can't figure out how to use TWRP (because I will freely admit to being stupid.) Can anyone give me some suggestions on what I should do to make my fire work again?

You probably have the device in fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
You may or may not have the drivers installed correctly for this mode. It's hard to tell from your description. In this mode, KFU will always tell you ADB is offline because you cannot use adb commands in fastboot mode. KFFB explains why. You need try sending a command like "fastboot getvar product" and see how it responds. KFFB's third post explains how you do this...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
The device and the host computer must be able to see the other the moment it goes into fastboot mode. If the command shows it is waiting for device, force the device off by pressing and holding the power button until it shuts down and turn it back on again. If you can confirm that the device is in fastboot mode using the 1st link above, but cannot send fastboot commands to it, you need to look at your drivers again. Start over by disconnecting the device and reinstalling from KFU's device driver installer. Follow the directions in the 2nd post of KFFB again to uninstall/reinstall drivers if necessary... the particulars are shown in parenthesis for the manual installation procedure.
Once you can send fastboot commands, you will need to change bootmodes to recovery or normal (KFFB's 3rd post). Use this guide to install a ROM...
http://forum.xda-developers.com/showthread.php?t=1638452

okay, well I went to bed and when I woke up it was blinking the 5 second boot loop (from what I found in the forum) so I'll read those links while it's charging on its wall charger. Hopefully they'll explain my problem.
You may or may not have the drivers installed correctly for this mode. It's hard to tell from your description.
Click to expand...
Click to collapse
Is there a way that I can see if I installed them incorrectly? Usually I just have windows 7 do the installing for me.

[Q] bootloop stuck, can't fastboot, need case open short instruction

Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455

lob455 said:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
Click to expand...
Click to collapse
Does it show up in Device manager? as kindle, android phone, or something else...?

sd_shadow said:
Does it show up in Device manager? as kindle, android phone, or something else...?
Click to expand...
Click to collapse
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".

lob455 said:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
Click to expand...
Click to collapse
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.

Thepooch said:
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Click to expand...
Click to collapse
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.

lob455 said:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
Click to expand...
Click to collapse
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.

Thepooch said:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Click to expand...
Click to collapse
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.

lob455 said:
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
Click to expand...
Click to collapse
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.

What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze

sd_shadow said:
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x ..................
Click to expand...
Click to collapse
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.

lob455 said:
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
Click to expand...
Click to collapse
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot

When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.

sd_shadow said:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
Click to expand...
Click to collapse
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.

lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Just place a Rom on your Sdcard and flash it.

lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Try the mount option in twrp again

sd_shadow said:
Try the mount option in twrp again
Click to expand...
Click to collapse
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.

lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck

lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.

Problem getting device into fastboot mode.

Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.

sabres032 said:
Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.
Click to expand...
Click to collapse
with OtterX bootloader v2.05, every time kindle is booting, fastboot commands can be used, but the window is short.
with kindle off, enter command
Code:
fastboot devices
then power on kindle, if you get a response like 123456789 fastboot
then you could try flashing bootloader again, but likely LCD is bad
unzip OtterX bootloader v2.05.zip, copy otterx-u-boot_v2.05.bin from cache folder, paste to your adb folder
verify md5:241A3FD1EDAD0A0D95886DDEB4693E1C
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot

I'll give it another go. One thing I forgot to mention, when I rebooted the device to recovery I pressed the power button and the TWRP screen briefly displayed. Then the screen went blank again.
EDIT: I try the fastboot>devices command, power on the device and Windows comes up with device not recognized and the device booted into ROM. I have confirmed this is also happening with my Kindle Fire so looks like I'm missing a driver. Both devices connect successfully within the ROM and Recovery so is it just a bootloader driver issue????
Screen shot of the error and code number.

Windows 7 or 8?
Sent from my XT894 using Tapatalk

sd_shadow said:
Windows 7 or 8?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Windows 7 32bit. I did a search of the forums and found a thread with a link for signed Kindle Fire drivers from Amazon. Downloaded, installed and rebooted system. Plugged in and powered up my Kindle Fire into SlimKat and Windows recognizes device and I'm able to transfer files no problems. I'll have to try the adb and fastboot commands later, I have to get my son to a college entrance exam soon. I'll let you know the results when I return home.

Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.

sabres032 said:
Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.
Click to expand...
Click to collapse
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode

sd_shadow said:
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode
Click to expand...
Click to collapse
I'm on the OtterX partition, will the drivers still work or do I have to revert back to Amazon partition?

shouldn't need to revert, just use the install drivers.bat, then reboot pc

sd_shadow said:
shouldn't need to revert, just use the install drivers.bat, then reboot pc
Click to expand...
Click to collapse
Sweeeeet!!!!! Thank you. I've just been tasked with a project from the captain at my fire department so once again I have to put this on hold for a few hours. Once I'm done there I'll give it a go and report back.

[Q] KF stuck at "Kindle Fire" screen, details inside, pls help?

So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?

arthurk62 said:
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
Click to expand...
Click to collapse
Can you get into fastboot? Did you restore your backup?

Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175

skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I had a feeling that must've been the case.
I followed your directions, but can't get past the "<waiting for device> message in CMD. Turning the kindle on or off doesn't seem to make a difference. Am I doing something wrong? Are there other alternatives?

Did you follow the steps in the right order
Turn of Kindle
connect the wire
type command
when waiting for device is shown then only turn on your kindle

Similar Problem
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I have a similar problem. I try to give the "fastboot -i 0x1949 getvar product" in windows cmd but it just gves an error. Do I need to install something to fix this

My guess is you don't have the right drivers installed. You have to install the driver while the device is attempting fastboot. If you have the device manager up you'll see it flash for a second when it boots. Right click when it flashes and install the driver.

Kindle Fire (1st Gen) stuck at boot logo after setting fastboot mode.

Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel

joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs

Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.

joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs

sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.

MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device