Develop Bugs

Unbricking My Kindle Fire

About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM

a very nice post for people who have bricked their kindles and need a factory cable!

Thanks for the kind words Steve. I hope this cable gives you confidence in flashing your Kindle long into the future. Glad it worked out for you.
Oh, and you did not see any evidence of modification because I do not modify the cable, I just cut off the original micro connector and install my own, already modified of course with a resistor and all I have to do is re-solder the 4 wires back onto their original pins and then fill the entire casing with 400 degree SureBonder PDR Hot Glue (the worlds strongest known hot glue, according to them anyway lol)... That way it looks and feels like a true manufactured store bought cable. However, doing it my way is still in fact more work, but the end result clearly justifies it.
Anyway, again glad I could be of service to you and my fellow XDA friends.

Where do I run the command from?

The3rdEye said:
Where do I run the command from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3

smoen02 said:
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
Click to expand...
Click to collapse
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!

andersonrel said:
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
Click to expand...
Click to collapse
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.

kinfauns said:
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
Click to expand...
Click to collapse
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I´m gonna try this and will post results. Thanks a lot.

kinfauns said:
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
Click to expand...
Click to collapse
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?

Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have

andersonrel said:
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Click to expand...
Click to collapse
Fix your drivers. Read this:
http://forum.xda-developers.com/showthread.php?p=23747671
djsaxon said:
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
Click to expand...
Click to collapse
First, fix your drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Then:
http://forum.xda-developers.com/showthread.php?p=25400963

kinfauns said:
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
Click to expand...
Click to collapse
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.

maw230 said:
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
Click to expand...
Click to collapse
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963

soupmagnet said:
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
Thank you.

hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?

jakelongryan said:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
Click to expand...
Click to collapse
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.

soupmagnet said:
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
Click to expand...
Click to collapse
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread

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

Stuck at Kindle Fire Logo [Bricked]

So I downloaded KFU to root a Kindle Fire, And when I chose root permanently with super user, the Kindle rebooted and got stuck at the Kindle Fire logo. The computer won't recognize it anymore so I can't do anything with the usb. It says unknown device in device manager. Is there anything I can do? I'm willing to buy a factory reset cable if need be.

Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.

NewPwnage said:
Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.
Click to expand...
Click to collapse
I've tried that, but when I click the "stuck at logo" button, it says waiting for device twice, then it says that my device should be unbricked now. Unfortunately, the device remains stuck.
I think the major issue which needs to be addressed is that the computer is not recognizing it as a kindle. Once that is fixed, unbricking it shouldn't be too difficult.

Me too!
Hi,
I just joined specifically so I could post in this thread, because I have exactly the same problem - only difference is the device manager has "android adb interface", with a yellow exclamation point sign, nested under "android phone". The unbrick utility says the Kindle should be unbricked, but it manifestly is not.
Is buying a factory cable the only way to go? Is that very likely to work? Is there any chance at all I can still root it? This is actually the 2nd KF which has had the exact same issue after giving the root command in KFU...

Josepho1997 said:
I sent you a PM.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Really? I'm not seeing it. Would I find it somewhere other than "private messages"?

If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.

Thepooch said:
If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.
Click to expand...
Click to collapse
Is fastboot the mode where it only shows the kf logo? I thought that was the boot loader...or am I just confusing things?
Anyway, thanks for the info, I sincerely hope it will help someone else, but unfortunately I don't know what I could do with it now - I've unplugged it, and now the device isn't recognized by kfu or my PC - and of course, it's stuck at the KF logo. And I'm not positive, but pretty sure that once the kf froze after I issued the root command, I did power it off then back on. Seems like the logical thing to do.

This happened to me. You have to use a factory cable or USB pin short trick which I did. After that it reinstalled my drivers and I then got twrp flashed and then perfection!
***if you choose to do the USB pin trick I'm not responsible for any hardware malfunctions or anything that will make you kindle into a paper weight I'm simply saying its what I did.***
Sent from my SAMSUNG-SGH-I727 Skyrocket on CM10 JELLYBEAN

Me too! please help!
Hello everyone! I feel like I have this exact same problem! My kindle is stuck at the blue and white kindle logo for about 2/3 seconds and then it just completely goes dark! I plug it into my computer and it doesnt even recognize my kindle anymore under my computer, nor does it show "adb android phone" on device manager.. PLEASE HELP ME!!
SUPER urgent! All help would be greatly appreciated!!!

Glad it was an easy fix chrisleealee enjoy the modified stock for awhile but when you do decide to move on here is my pick http://forum.xda-developers.com/showthread.php?t=1778010 don't forget to add system to your scheme of wipes when changing systems good luck and have fun

Wrong thread. Sorry. Glad your issue has been resolved.
---------- Post added at 07:53 PM ---------- Previous post was at 07:46 PM ----------
Use a factory cable. It will make life easy. Sticker on that logo too, same situation. I created my own factory cable and that solved it. Hope this helps.
Also, try to check your adb drivers.

[Q] Need help with rooted(?) possibly bricked kindle fire

Back story: I purchased a used Kindle Fire on Ebay about a week ago, not knowing that it had been rooted. I was looking for a standard Kindle fire for my son so he would stop using my tablet (lol) and the parental controls are better and more books and so on... none the less when I got it I noticed that it booted differently (I had a kindle fire prior) and it booted into Android. I have had problems with trying to be able to get my computer to recognize it. It looks for missing drivers and I have been all frustrated, but figured that we would just have to download off of it, well, we went on a trip this past weekend (11 hours) and my son wanted to watch a movie, turned it on and it wont boot past the yellow triangle now. I have tried a hard reboot, I have tried to turn it on and hold it and watch for the orange light to no avail. The light is either green or its powered off.
I don know what to do at this point? I cant hook it to my computer (wont even recognize as an F drive or mass media) and I cant boot past the orange triangle. Yes, I am a newb (apologies) but a very frustrated one if that counts?
Sadly I think the thing is bricked and I will take a $150 hit (ugh)

No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)

Yes, you would be correct in that I just want it stock, sure Android is great but my son is 4 and he just needs the basics for his books and angry birds lol. So, I attempted what you said, powered off all of the way and turned back on, as soon as I see the yellow triangle I hold the button and it wont turn orange, it will just power back off. I used to be able to touch the screen when the yellow triangle came up and it would take me into some menu (TWRP?) but it wont do that anymore either, its just remains either off or on the yellow triangle.
soupmagnet said:
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Click to expand...
Click to collapse

Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.

I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
soupmagnet said:
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
Click to expand...
Click to collapse

Save yourself the trouble mail it to me I will fix it then you reimburse me the return postage or better yet I can show you how to fix it without even mailing it . 150 for a first gen kindle is pretty high you kinda already got taken.

[email protected] said:
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
Click to expand...
Click to collapse
Pay attention to what I said previously...
soupmagnet said:
Extract the KFU and run the install_drivers.bat
Click to expand...
Click to collapse
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.

I think I am officially over this thing... I downloaded the drivers and went to plug in the kindle fire to the computer and now its just looping the triangle... it turns on for a second and then off and on and off and so on... UGHHHHHH....
soupmagnet said:
Pay attention to what I said previously...
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
Click to expand...
Click to collapse

You let the battery die. I won't go into how it happened but to get it to charge, you need to...
With the device turned off, Plug the device into USB and hold the power button until it shuts off again. If you can get it to stay off, leave it plugged in for about half a day and turn it on again.