Develop Bugs

[Q] Kindle Fire Boot Question

I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.

Luppertazzi said:
I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.
Click to expand...
Click to collapse
Red triangle? Blimp?
Read this...
http://forum.xda-developers.com/showthread.php?t=1623244

Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
I gave you a link to a guide that fully explains what's going on and why "nothing happens." It also gives you a suggestions on what usually works and if it doesn't, the next thing you should attempt in order to fix your problem. If you don't want to try that, you can crack your case open, pull out the battery, find a charger that will charge it offline and stick it back in there.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
Never let your battery complety drain with the new kernel.
Try this:
1. Overnight charge with an iPhone charger (even the Kindle show yellow triangle).
2. If above method won't work,
Extract the kernel from stock firmware (get it from amazon)
Flash the kernel in fastboot (yellow triangle)
Reboot
Charge with wall charger at least 4 hours.
If you're lucky then you can flash Hascode #8 kernel, wipe cache/dalvik and boot normally.

Is it charging even when the yellow blip is on from a wall outlet?

Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.

Luppertazzi said:
Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.
Click to expand...
Click to collapse
Unzip the archive and extract the .bin file inside it.
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on post #3 to learn how to use fastboot.
Then you'll want to get the device into fastboot mode by issuing a command like...
Code:
fastboot getvar product
and then rebooting the KF. The post above will tell you what to look for when you manage to get it into fastboot mode. It will also tell you how to flash the .bin file you extracted from the .zip file and tell you how to change bootmodes if necessary. Also read the OP for FFF 1.4 for details on how to use your new bootloader.

http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html

soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
Click to expand...
Click to collapse
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
Type or paste the command, fastboot flash bootloader fff-u-boot_v1.4a.bin, when you see <waiting for device>, turn the KF on.
Click to expand...
Click to collapse
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?

Luppertazzi said:
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?
Click to expand...
Click to collapse
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.

soupmagnet said:
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.
Click to expand...
Click to collapse
And after reading all that information, which i did, carefully, and trying to understand all of this, the only option i might have is a factory cable to get it into fastboot mode? What about the temporary fastboot, can i profit from that or try to at least?
My main issue is the ADB is offline and i can't get it into fastboot via KFU, shouldn't it be recognized as online nonetheless?
Everybody keeps mentioning the original AC charger, flashing to stock, flashing FFF 1.4a, but i can't even get it to fastboot, recovery is a longshot. How am i supposed to fix this if all the solutions given reffer to fastboot or TWRP, both of which i cannot access?

You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.

soupmagnet said:
You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.
Click to expand...
Click to collapse
Okay, thank you, that's all i wanted to know. I thought my situation was different because ADB kept showing OFFLINE and i couldn't speculate the temporary fastboot or the normal fastboot. If you're saying this is normal when the battery's dead then okay.
I guess i'm buying a factory cable. One last question. When that cable does get in my hands, all i have to do is plug it in my laptop USB port, then into my kindle, gaining automatic fastboot, and then write:
fastboot flash bootloader fff-u-boot_v1.4a.bin
Click to expand...
Click to collapse
and
fastboot reboot
Click to expand...
Click to collapse
and it should have flashed to the newest 1.4a that bypasses this problem, correct?

Yes, assuming your drivers are in good working order.

When I try to troubleshoot someone else's problem, I do my best to understand what it is that they don't understand. Now, I finally see the reason why you are so resistant to trying my suggestions... When the bootloader says "press power button for recovery" it's not URGING you to do anything. It's SUGGESTING and providing a reminder of how to get to recovery. It's like a road sign that says "exit here for rest stop." Whether or not you pass that point with a full bladder, that reminder is ALWAYS there. It has nothing to do with your present situation.
I think you've been convinced that you need to get into fastboot mode. You can follow my previous instructions and send that command during temporary fastboot. If you are successful, it will stop the temporary fastboot countdown and stay in fastboot mode. You can get the factory cable and that will automatically put you in fastboot mode, but you are still going to have to be able to send it fastboot commands anyway. In either case, you'll have to fix whatever is keeping your computer from sending fastboot commands to the device and that's almost always the device drivers. The only difference between my suggestion and soupmagnet's is the factory cable's ability to automatically keep you in fastboot mode so you have more of an opportunity to diagnose the problem.

[SOLVED] I flashed the wrong bootloader, now what?

I falshed the wrong bootloader to my KF. Now it won't power up with no backlight, no kindle fire logo and no led on the power button. What should I do? Do I have to pry the back cover and use the Firekit LiveUSB (http://forum.xda-developers.com/showthread.php?t=1430038)? Will a factory cable fix this? It seems that a correct bootloader is needed to use fastboot so factory cables will not work.
What should I do now?
UPDATE: I solved this issue using the Firekit found here and a post about usb boot in here. I tried several times until I finally succeeded. I do not unbrick it using Firekit because it seemed not to work on my computer, just showing "waiting for OMAP44xx device..".In the end I use
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
found in the other post. And I succeed. I summarized several points. Hopefully, these may help others unbrick their Kindle Fire like me.
To pry KF's back case open, you can use the method found here in iFixit. I do not have those tools as they do but I just use small flat-head screwdriver and one credit card to open it. Be careful when dealing with the clips, because they are easy to break (I broke two of them...).
To short the contact point, you can find the exact position in the picture (the red arrow shows the position) in end of my post or here.
I use a small knife to short it but practically anything is OK if they can conduct electricity just like other posts say. I use the knife to touch the point and the frame of the CPU (as the gray frame shows in the attachment).
After I managed to boot my Kindle into TWRP, I flash the stock ROM but when I choose to reboot, it just shutdown and I cannot power it up. But after I put the back case back, it seems that everything went on well and it is working again!
Thanks to all the people helping me. You really teach me a lot. This unbricking experience us really interesting and I believe I will learn even more from all the people on xda.

Firekit, imho.
Sent from my Amazon Kindle Fire using XDA

Firekit

Thepooch said:
Starting thread after thread isn't going to get it fixed faster either use fire kit or get a factory cable and you flashed the right bootloader incorrectly any bootloader for the kindle will work if you follow instructions
Click to expand...
Click to collapse
Fyi, factory cable will not fix a bad bootloader flash. Needs firekit or some variation of USBboot.
Sent from my DROID4 using Tapatalk 2

Thanks

Hashcode said:
Fyi, factory cable will not fix a bad bootloader flash. Needs firekit or some variation of USBboot.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, Hashcode! Using your method, I manage to unbrick my Kindle!!

freefaling said:
Firekit, imho.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Thank you, freefaling! Using Firekit, I saved the Kindle Fire. Thank you so much!

g0og1e said:
I falshed the wrong bootloader to my KF. Now it won't power up with no backlight, no kindle fire logo and no led on the power button. What should I do? Do I have to pry the back cover and use the Firekit LiveUSB (http://forum.xda-developers.com/showthread.php?t=1430038)? Will a factory cable fix this? It seems that a correct bootloader is needed to use fastboot so factory cables will not work.
What should I do now?
Click to expand...
Click to collapse
Out of curiosity, what boot loader did you install, and how did you install the wrong one?
Sent from my Galaxy Nexus using Tapatalk 2

pbailey212 said:
Out of curiosity, what boot loader did you install, and how did you install the wrong one?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I use this command "fastboot -i 0x1949 flash bootloader u-boot-firefirefire-1.2.zip". I should have used "fastboot -i 0x1949 flash bootloader u-boot.bin" where the u-boot.bin file is extracted from u-boot-firefirefire-1.2.zip. I was confused at that time and now I am clear. When I flash the bootloader using Recovery, I should flash the zip file but if I use fastboot, I should flash the bin file. Hope this may be useful to some newbies like me.

Help
My Kindle Fire is dead. I tried with the factory cable, with KFU, with firekit, with your method, opening the case with and without the short.
Is in a coma, black screen, no charging led lights, W7 doesnt recognize it, Ubuntu 12.04 doesnt work.
Can you help me?
Thank you.

franciscoruiz said:
My Kindle Fire is dead. I tried with the factory cable, with KFU, with firekit, with your method, opening the case with and without the short.
Is in a coma, black screen, no charging led lights, W7 doesnt recognize it, Ubuntu 12.04 doesnt work.
Can you help me?
Thank you.
Click to expand...
Click to collapse
Can you give specific details as to what happened to land your kf in that state?

franciscoruiz said:
My Kindle Fire is dead. I tried with the factory cable, with KFU, with firekit, with your method, opening the case with and without the short.
Is in a coma, black screen, no charging led lights, W7 doesnt recognize it, Ubuntu 12.04 doesnt work.
Can you help me?
Thank you.
Click to expand...
Click to collapse
Try Ubuntu 10.4 and see if that works. Also, provide as much detail as you can about your steps and what results you get.

franciscoruiz said:
My Kindle Fire is dead. I tried with the factory cable, with KFU, with firekit, with your method, opening the case with and without the short.
Is in a coma, black screen, no charging led lights, W7 doesnt recognize it, Ubuntu 12.04 doesnt work.
Can you help me?
Thank you.
Click to expand...
Click to collapse
I found this...
http://forum.xda-developers.com/showpost.php?p=25703127&postcount=18
It seems it won't work without the USB Stick.
I won't even try to use ubuntu from VMWare... I'll go straight to USB Stick... Are you using it?
PS: I'll try it as soon as I have mine KF open.

franciscoruiz said:
My Kindle Fire is dead. I tried with the factory cable, with KFU, with firekit, with your method, opening the case with and without the short.
Is in a coma, black screen, no charging led lights, W7 doesnt recognize it, Ubuntu 12.04 doesnt work.
Can you help me?
Thank you.
Click to expand...
Click to collapse
Can you remember the steps you did to Kindle? I mean, what tweaks did you use to cause you Kindle to be bricked? Given that your Kindle's led lights does not work, it is very possible that you flash the wrong bootloader. Maybe you should read those useful threads like Firekit and USB boot tricks once again, so that you can find more information. I use Ubuntu 11.10, not the latest version, but the Firekit seems not to work on my computer, only to find "waiting for OMAP44xx device..." on the screen no matter I short the contact or not. So I turned to the post here. I issued:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
And it worked! There are some points to keep in mind. Before you do any of these steps, push the power button for 20 secs or more. Then type the commands mentioned in that post. And you short it and while keeping to shorted, you plug in the usb. If you see some text on your screen, then you succeed.

Hermano Francisco,
It's kind of tricky... to mw worked right now... I kept trying, unitl I find the right spot for the short, or the right time... My KF is working so far...
Gonna turn it off, read all the guides... and later I'll try to learn how to put market in it.
Thanks guys for help and all knowledge that you share.

Help me please
Bricked My kindle. Could Not bot up.
I am a Windows User, Tried Ubuntu for this method. But stucks at
"waiting for OMAP44xx device..."
Tried out the Shorting pin point. But no response,. "Is the adb has to set earler before to do this?" if yes please specify How to do that.
I did the Steps.
1. First removed battery wire: (Just to make it Power of if it is on)
2. Pressed Power button for 30 seconds nearly
3. Short the Pin point and Plugd in USB(I already attached One end to PC)
4. Tried out many times. But still.....
5. Before Flasing Bootloader. Kindle works well. I just gave a wrong file name. As a stupid thing. Please dont scold. Help me.

balakrishnan111 said:
Bricked My kindle. Could Not bot up.
I am a Windows User, Tried Ubuntu for this method. But stucks at
"waiting for OMAP44xx device..."
Tried out the Shorting pin point. But no response,. "Is the adb has to set earler before to do this?" if yes please specify How to do that.
I did the Steps.
1. First removed battery wire: (Just to make it Power of if it is on)
2. Pressed Power button for 30 seconds nearly
3. Short the Pin point and Plugd in USB(I already attached One end to PC)
4. Tried out many times. But still.....
5. Before Flasing Bootloader. Kindle works well. I just gave a wrong file name. As a stupid thing. Please dont scold. Help me.
Click to expand...
Click to collapse
When it says waiting is when you apply the short and plug it in keeping it shorted till the script runs

Thanks for ur fast response
Thepooch said:
When it says waiting is when you apply the short and plug it in keeping it shorted till the script runs
Click to expand...
Click to collapse
Thank you for fast response. But as i noted earlier. i did Pin short only during the "Waiting for device prompt in terminal"
What should i do

If your using a 3.0 USB port it very likely will not work use 2.0 only

I hope i am using USB 2.0, My system does not 3.0 Port. Itried now also. NO use. Is there any other way available, Please say

[Q] Kindle fire totally unresponsive after bootloader flash

After flashing firefirefire and twrp 2.1 to a friend's Kindle Fire, the kindle is totally unresponsive. (Yes, I believe I flashed the bootloader incorrectly. I probably flashed the actual .zip rather than a binary.)
Anyways, now:
- The power button never lights, no matter what I do. A/C plugged in, USB plugged in, after holding power button for minutes, after battery disconnected and USB connected, nothing.
- When plugged in to the USB port (Linux running), no messages appear in the syslog that indicate it even recognizes that a device has been connected
- usbboot (with the shorting trick) did not help
- disconnecting battery, then trying usbboot (with the shorting trick) does not help
For what it's worth: I actually accidentally performed the shorting trick on the wrong Kindle (mine) and effectively made it not boot. I WAS able to fix mine using the usbboot (with the shorting trick) and get it back booting. So, I know how this works. One difference I note, when I plugged in my Kindle, and tried the usbboot trick, it did not work (stuck on waiting for OMAP44xx device forever). But when I unplugged the battery, and plugged in the usb cable, at least Linux logged that the USB device was connected, and the power button flashed green, on and off. This other one does absolutely zero - nothing.
It's almost like the USB jack on this Fire is completely hosed. How could flashing the bootloader and recovery do this?
After extensive research, I'm beginning to feel like I'm out of options. The factory usb cable is the only thing I have not tried.
Thanks.
This is the thread I have been following to try to recover. It worked for mine, but not for my friends.
http://forum.xda-developers.com/showthread.php?t=1636883
Update: if you want to know what i did:
sudo ./fastboot -i 0x1949 flash bootloader ~/Downloads/Kindle/u-boot-firefirefire-1.2.zip
(Yeah, I know, just wasn't thinking.)
Update:
I just, on whim, with the battery unplugged, tried the usbboot short trick again, and it worked!
I think I'm back in business.
Update:
After several successful attempts at communication with the device, I was able to get the bootloader overwritten and twrp installed. I had to customize the "usb_fix_parts_and_install_fff_twrp" script to get it to go through. It kept coming back to 'waiting for device'. Maybe I didn't wait long enough. It seemed stuck. Here is my customized script. (I removed the oem format and xloader).
#!/bin/bash
FKDIR=$(pwd)
echo "Loading FFF through USB..."
./usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
#echo "Fixing partitions..."
#./fastboot oem format
#echo "Installing x-loader..."
#./fastboot flash xloader $FKDIR/mmcblk0p1
echo "Flash FFF..."
./fastboot flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
./fastboot flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
./fastboot oem idme bootmode 4000
echo "Loading TWRP..."
./fastboot boot $FKDIR/twrp2-blaze.img
Note: I was running this from my personal Linux (non VM linux system) as root. I just extracted firekit into my download dir and called the commands manually, since I didn't want to bother with a USB stick (since I run linux).

kcburge said:
After flashing firefirefire and twrp 2.1 to a friend's Kindle Fire, the kindle is totally unresponsive.
- The power button never lights
- When plugged in to the USB port (Linux running), not message appear in the syslog that it even recognizes that a device has been connected
- usbboot (with the shorting trick) did not help
- disconnecting battery, then trying usbboot (with the shorting trick) does not help
For what it's worth: I actually accidentally performed the shorting trick on the wrong Kindle (mine) and effectively made it not boot. I WAS able to fix mine using the usbboot (with the shorting trick) and get it back booting. So, I know how this works. One difference I note, when I plugged in my Kindle, and tried the usbboot trick, it did not work. But when I unplugged the batter, and plugged in the usb cable, at least Linux logged that the USB device was connected, and the power button flashed green, on and off. This other one does absolutely zero - nothing.
It's almost like the USB jack on this Fire is completely hosed. How could flashing the bootloader and recovery do this?
After extensive research, I'm beginning to feel like I'm out of options. The factory usb cable is the only thing I have not tried.
Thanks.
Click to expand...
Click to collapse
Unfortunately a factory cable won't help, so save your money. This is caused by a bad bootloader flash. Usually from flashing a corrupt file or a .zip instead of a .bin
If you're using a VM, instead of straight Linux or LiveUSB, that could cause problems as well as the Linux version you are using. It's possible you were able to get yours to work with your current setup because the bootloader was still intact on your device.
Only you would know for sure but it's possible if the battery was low enough then it might have died while installing the bootloader, which would be the only reason you should get a factory cable.

Update:
After several successful attempts at communication with the device, I was able to get the bootloader overwritten and twrp installed. I had to customize the "usb_fix_parts_and_install_fff_twrp" script to get it to go through. It kept coming back to 'waiting for device'. Maybe I didn't wait long enough. It seemed stuck. Here is my customized script. (I removed the oem format and xloader).
#!/bin/bash
FKDIR=$(pwd)
echo "Loading FFF through USB..."
./usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
#echo "Fixing partitions..."
#./fastboot oem format
#echo "Installing x-loader..."
#./fastboot flash xloader $FKDIR/mmcblk0p1
echo "Flash FFF..."
./fastboot flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
./fastboot flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
./fastboot oem idme bootmode 4000
echo "Loading TWRP..."
./fastboot boot $FKDIR/twrp2-blaze.img
Note: I was running this from my personal Linux (non VM linux system) as root. I just extracted firekit into my download dir and called the commands manually, since I didn't want to bother with a USB stick (since I run linux).[/QUOTE]
Nice good job

This is a rather extreme example of excessive quotation of a previous post, something that seems to be endemic to this site. I have seen few if any other web forums, blogs or whatever where people habitually quote fully a long comment that was posted previously, especially when it is likely to appear on the same web page. It's generally considered good practice to quote only the particular statements you are discussing, and to refer back to the post you are discussing by giving its author's id and/or the comment number.
And there is a Thanks button, after all!

aarons510 said:
This is a rather extreme example of excessive quotation of a previous post, something that seems to be endemic to this site. I have seen few if any other web forums, blogs or whatever where people habitually quote fully a long comment that was posted previously, especially when it is likely to appear on the same web page. It's generally considered good practice to quote only the particular statements you are discussing, and to refer back to the post you are discussing by giving its author's id and/or the comment number.
And there is a Thanks button, after all!
Click to expand...
Click to collapse
Sorry, it won't happen again.

How to recover when a bad bootloader flash puts your Fire completely out
I had this same problem, and it came from flashing u-boot.zip instead of the u-boot.bin it contains.
Once flashed and rebooted, the Kindle Fire became completely unresponsive. No power/charge light, USB port appeared completely dead. I called Amazon support and they sent me a new Fire. But I just couldn't accept that it was unfixable, so I kept trying. And I figured it out.
Here's the procedure:
Disconnect the USB cable.
Remove the Fire's back cover.
Disconnect the battery. This step is critical! It ensures that the CPU is completely powered off.
Have your USB cable plugged into the computer, but NOT into the Kindle yet.
Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Plug the USB cable into the Fire. At this point, the Fire has been turned on in USB boot mode and is being powered exclusively by the USB port. You can now stop grounding the USB boot pad.
Now reconnect the battery. This step is critical!
Use usbboot as documented elsewhere to send a good bootloader via USB and boot with it. You should end up in fastboot mode. AND your power light should be back on, probably green! NOTE This only boots with the bootloader you sent, it does not flash it. The bad bootloader is still installed.
Now use fastboot to install a good bootloader, and a recovery if you want. Or use a firekit script...
Finally you can reboot for real. Make sure it will really reboot before you put the back cover on. You may have to change the bootmode back to 4000.
You now have a working Kindle Fire again.
Why it works. This is conjecture based on my findings:
First, as long as the battery is providing power to the Kindle, the CPU is not powered completely down, even in this case where the device seems totally dead from a bad bootloader flash. Therefore, grounding the USB boot pad does nothing, because the CPU only honors this on powerup. Disconnecting the battery and USB forces the CPU to power down. If you then ground the USB boot pad and connect the USB, the CPU powers up and goes into USB boot mode.
It's possible that if you wait a long time (maybe many days) so that the battery discharges to the point that the battery protection circuitry stops all further drain, you might get the same effect without disconnecting the battery. I didn't have the patience to test this.
Second, the bootloaders I used (two firefirefire versions) apparently check whether the battery is connected, and halt if it is not. I suspect this is true of most/all available bootloaders. So even if you get into USB boot mode and send over a good bootloader, once the Kindle starts booting with that bootloader, if it finds that the battery is not connected, it quits: it never gets into fastboot mode. Hence the "waiting for device" messages noted earlier in this thread. Therefore, as soon as you have gotten the CPU in USB boot mode, but BEFORE you've run the usbboot command, you need to reconnect the battery.
The only thing that remains is to listen to the angel choirs sing.
And wonder why you had to brick the replacement Kindle that Amazon sent--and break some of the tabs on its back cover in the process of fixing it--in order to fail at proving to yourself that you did not cause the problem in the first place. And decide whether you're glad that you now own TWO Kindle Fire's with loose back covers...

Great write up hope I never need to use it but lots of people get stuck in your situation so it should come in handy

That's basically what I did. The problems I had were:
1) not performing the short correctly
I used the wands (not sure what they are called) from an ohm meter (disconnected from the ohm meter) to make the contact with the rail. On one of the Kindles it was easier than the other. I must have tried 20 or 30 times on the one that I had the trouble with. After I had resigned that it was not going to work, I decided to try "one last time", and it worked. So, as someone else said. "Don't give up."
2) not performing the short with the battery unplugged.
I performed the whole operation of booting and overwriting the bad bootloader with the battery unplugged.
Thanks for you input.

switched off...need help
I have kf, its switched off and dont switched on, with the USBboot
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
kf switched on, but its loaded once to yellow triangle then switched off, then i turn on kf and no more yellow triangle.... all do in ubuntu, windows dont recognazes kf. and the firekit allows ones do one of his scripts, and that all. i stuck on firekit, whats i need flash on kf to do it works?

Hi. Thank you for your explanation, but I am having trouble understanding one part. Step 5: Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Is there somewhere I can see a picture of this or get detailed instructions? I don't want to do it incorrectly. I screwed my Fire 8.9 up after trying to root using the Bin4ry Tool and appropraite 8.9 drivers. Now I have an unresponsive Kindle Fire 8.9. It won't power on at all.
Thank you for any help.

Yeah ... I was looking for a bit more detail on that part.... I just super-bricked my Kindle Fire 7" and am hoping that this Shorting Trick works... but I also am confused at what a Boot Pad is
[email protected] said:
Hi. Thank you for your explanation, but I am having trouble understanding one part. Step 5: Ground the "USB boot" pad on the Fire's motherboard, as described elsewhere (the USB boot shorting trick). Keep it this way for the next step.
Is there somewhere I can see a picture of this or get detailed instructions? I don't want to do it incorrectly. I screwed my Fire 8.9 up after trying to root using the Bin4ry Tool and appropraite 8.9 drivers. Now I have an unresponsive Kindle Fire 8.9. It won't power on at all.
Thank you for any help.
Click to expand...
Click to collapse

Found this buried in the forums
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51

Old thread, I know, but where can I find how to do the shorting trick

Nandr0idC0nsumer said:
Old thread, I know, but where can I find how to do the shorting trick
Click to expand...
Click to collapse
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs

sd_shadow said:
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Maybe I'm being dumb but I can't find it :silly:

Nandr0idC0nsumer said:
Maybe I'm being dumb but I can't find it :silly:
Click to expand...
Click to collapse
post #4 Unbricking
http://forum.xda-developers.com/showpost.php?p=61563704&postcount=4
Sent from my XT1060 using XDA Labs

sd_shadow said:
post #4 Unbricking
http://forum.xda-developers.com/showpost.php?p=61563704&postcount=4
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
Alrighty I've gotten it recognized on my Linux PC as OMAP444x USB Device!
I haven't a clue what to do next. thanks in advance!

[Q] Need Help - Bricked Kindle Fire

I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.

gwmadrigal said:
I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.
Click to expand...
Click to collapse
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.

Thepooch said:
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.
Click to expand...
Click to collapse
I have done a lot of experiments with my SGS2 about installing ROMS using ODIN or CWR, backing up my own images and making backups. Most of the work I do though is in CWR. I haven't dealt with TWR yet. I also installed ICS on my HP Touchpad. So, even though this is the first time I deal with the KF, I already some experience working with ROMS and images.
Back to the process. I installed the FFF using the Kindle Fire Utility. The KF was forced to fastboot mode via the factory cable. At first I could see on the KF splash screen with the black and orange logo, and now the KF is booting using a Black and Blue kindle fire logo with 1.4a on top. At the bottom of the splash I see instructions of the bootloader selector indicating to press the power button and select the mode that I want to boot. Either Normal Mode or Recovery Mode.
I flashed the TWRP 2.2.2.1 in fastboot mode using my command prompt by putting this code:
Code:
fastboot -i 0x1949 flash recovery [path]\openrecovery-twrp-2.2.2.1-blaze.img
I was following the instructions on this guide.
http://forum.xda-developers.com/showthread.php?t=1638452
I got stuck on step 3 after attempting to boot into recovery mode.
I can select which boot mode I want to go, but none of them work. I only get on the bottom of the screen saying Booting... and then the KF shuts down.
I suspect the battery had a good level of charge, but I can't tell for sure.
Thanks for everything.

Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot

soupmagnet said:
Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot
Click to expand...
Click to collapse
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.

gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
What happens when you change the bootmode to 5001?

soupmagnet said:
What happens when you change the bootmode to 5001?
Click to expand...
Click to collapse
It accepts the command.
The command prompt responds saying something like it took 0. something seconds to execute the command.
Thanks for reading my thread.

If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.

soupmagnet said:
1. If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
2. If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
3. If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.
Click to expand...
Click to collapse
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.

gwmadrigal said:
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.
Click to expand...
Click to collapse
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.

gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.

Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.

soupmagnet said:
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.
Click to expand...
Click to collapse
I tried reloading the u-boot using fastboot and the upload was successful. But it's doing exactly the same.I guess my only question right now, do you know of any good guide that I should start reading to get my feet wet on what the firekit is and how to get started?
Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I have nothing to lose. This KF is already bricked. I can certainly try anything. Which cable do you suggest I use? the Factory cable or the USB cable?
I think I answered my own question now. Using a regular USB cable puts the KF in the bootloop. I will use the factory cable instead. I shut down the KF, put the factory cable connected to my computer and the KF. Right now the KF is in the KindleFire splash screen waiting for fastboot commands of for me to use the button to tell it which mode to boot. I will leave it plug overnight.
Thanks for replying on my thread and trying to help me.
soupmagnet said:
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.
Click to expand...
Click to collapse
I posted a video in utube of what the KF is doing, so you can see what I'm seeing.
Link
Thanks for coming back several times to reply on my thread.

That looks like your battery. From what I can tell, the device is just rebooting, not shutting down.
Unplug the device and hold the power button to perform a hard shutdown.
Plug the device in (it should power up on it's own) and hold the power button to shut it down again.
Leave it plugged into the computer until sometime tomorrow and try again.

Same thing I was thinking 5 second bootloop Thank you the video was very helpful to see just how its acting. Use stock cable to charge not factory.

OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.

gwmadrigal said:
OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.
Click to expand...
Click to collapse
I think you're fine let it rest.

[Q] Accidentally deleted my kindle fire OS

Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!

I did something very similar.
june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?

june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428

lj50036 said:
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428
Click to expand...
Click to collapse
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.

SDK
june726 said:
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.
Click to expand...
Click to collapse
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg dowload....
http://developer.android.com/sdk/index.html

Controverly areadvia
lj50036 said:
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse

june726 said:
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse
Ok.. Well than lets see here.....When can you use adb??? I need as much info as possible... What file are you moving..... Where are you trying to move it to... Copy and paste your commands and outputs this will make it much easier for me and anyone else that would like to help....Thx lj

Phil700 said:
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?
Click to expand...
Click to collapse
Well your problem is nowhere near the same as June's, but I'll go ahead and try to help your anyway. I've had this happen to me once or twice. My suggestion is to redownload your rom and gapps, and then try flagging them again. Hopefully that should work. There is an option in TWRP to mount your kindle on your computer.
Sent from my Nexus 7 using Tapatalk

So far.
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!

System deleted Need Help !!!! Please
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!

Happyy said:
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!
Click to expand...
Click to collapse
Nothing here works for the HDX result=permabrick. All support for HDX is here http://forum.xda-developers.com/kindle-fire-hdx .

Phil700 said:
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!
Click to expand...
Click to collapse
Hey Phil. Doesn't look like you've posted anything else, so you probably won't see this. But oh well... Sorry your problem got left in the dust. I didn't mean for that to happen. You need to shift + right click in the folder with adb.exe and click "open command window here" and then you can do your things. As far as everything else: does your computer do anything when you plug your kindle into it?

I accidentally did this once (at least I think it's the same) and what I did was I went into ADB and side loaded a custom ROM I used CM