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!

[q] usb boot only

Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.

thequietone said:
Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
Click to expand...
Click to collapse
Are you opening up the case each time you use usbboot?
What Firekit script are you using to boot the device?
What happens when it fails to fully boot in to the system?
Is your battery charged?
usbboot only loads a bootloader into memory temporarily. Once you've got the device booted, you need to flash a new bootloader permanently onto the device. I suggest FFF 1.4a...
http://forum.xda-developers.com/showthread.php?t=1632375

usb boot only
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.

Get it booted temporarily disconnect the battery then reconnect it let it continue to charge via usb maybe it will correct your problem. Or replace your system with something stock like without going fully stock paul has a new release http://forum.xda-developers.com/showthread.php?t=1439916 good luck

usb boot only
So unplugging the battery while plugged in via USB doesn't work, however I am able to get it to boot into ICS I just have to unplug the USB right after the script says Flash FFF... That would lead me to believe it's a problem with the boot loader, but I have tried several times to flash it with fff-u-boot_v1.4a.zip with no luck.

thequietone said:
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Click to expand...
Click to collapse
The fact that you are able to use those scripts indicates you are in usbboot mode (4003) or the hardware is defaulting to usbboot on its own which probably indicates that something about your bootloaders is a little off...
Try using the "fix all" script (I don't recall the exact name). This will return your partition table back to stock and then flash both the 1st and 2nd stage bootloaders.
Also try flashing FFF 1.4a again with TWRP and take note of the output it gives you if it fails.

usb boot only
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB

thequietone said:
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
Click to expand...
Click to collapse
See if you can set the bootmode back to normal and reboot it. Running as root...
Code:
usbboot /root/firekit/aboot.bin /root/firekit/u-boot.bin; fastboot oem idme bootmode 4000; fastboot reboot

usb boot only
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)

thequietone said:
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
Click to expand...
Click to collapse
Did you ever have Hashcode's CWM recovery installed on your device or have you always used TWRP?
Have you run those Firekit scripts again after you installed FFF 1.4a?
The only other thing I can think of is that your device's bootmode is set to USB boot and that's why it doesn't load up the bootloader already installed on your Kindle Fire. It's seems to be waiting for you to use usbboot to send it a bootloader. Get to TWRP again, flash FFF 1.4a and run these adb command to set the bootmode to 4000 and reboot...
Code:
adb shell idme bootmode 4000
adb reboot

The problem is I can't get FFF 1.4a installed. When I try to do it via TWRP which is the only utility I have tried it appears to load successfully, but when I do the reboot, the screen won't come on and there is no power light. So I hold down the power button for the 20 seconds then run the FireKit commands hook up the USB and it boots back up, but won't boot on it's own.

Have you found a fix yet? I may have a solution from my experience with mine, which was bricked beyond imaginable (don't ask how ). I was able to install FFF+TWRP and restore to stock perfectly fine.

It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.

thequietone said:
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
Click to expand...
Click to collapse
You didn't answer the question of whether or not you've used Hashcode's CWMR.
From TWRP, run these commands...
Code:
adb shell idme ?
adb shell parted /dev/block/mmcblk0 unit b print
and paste the output here.
Also, if you can load ICS, download/install smirkit...
http://forum.xda-developers.com/showthread.php?t=1500935
and try to install FFF 1.4a that way. Using smirkit will raw write the bootloader image directly onto the partition.

Here is the screen shot. Couldn't get smirkit installed.

Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!

Still Unresolved
Nope I am still having the same issue. Right now, I just try to keep it charged hoping it won't die, because if it does then I have to USB boot to get it back up and running
dmp2007 said:
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Click to expand...
Click to collapse

shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.

I haven't heard of it responding to touch. Mine works perfectly except for always having to USB Boot if it dies or if someone holds down the power button too long.
QUOTE=dmp2007;28967427]shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.[/QUOTE]

I too get this, I've been through what feels like every thread on here about this, only a few of these show up as the 'usb boot only' though and they all end in no answer. I have tried all forms of partitioning up to and including dd'n the p1.img over top of xloader and p2.img on top of bootloader.
With usb, i can go back fully stock (however, even fully stock wont boot without usb boot.. so its got to be busted xloader or bootloader), i can get TWRP installed, any ROM and its all usable.. until as OP said.. power out or reboot needed. It's bothering me enough just wanting to fix it I keep rebreaking perfectly good installs thinking some nugget I found/missed re-reading endless posts is the one.. just in case someone else comes through with this, here are my findings:
happened to me as originally I bricked to the point had to crack it open and short it to get it to boot via usb, finally working well using liveUSB firekit. However, from that point on, would NEVER boot on its own, and would NEVER shutdown/reboot without needing 20-30s of power button molestation. perhaps this is left over issue of the pin short... dunno
Once i figured out I could usbboot, basically went on with everything as normal. recovery, roms, back to stock, back to rom, etc etc. What seemingly never works, or simply oui can never get to, is the bootloader. All indications that I have known/been able to check seem to think its iinstalling, perhaps we are just never making it to it (xloader death)
So then I went crazy and tried everything from adb/fastboot raw on Mac, windows and linux, setting bootmode to 4000 every way with every tool listed on this site possible.. no joy.. usbboot is a must. Tried zeroing the mmcblk0p1/p2 and writing good versions on top, nothing.
Current state.. if I, via adb/fastboot/twrp/recovery do a reboot or shutdown.. the kindle shuts down screen and led's only (sometimes even leaving the green power light on, but almost ALWAYS just all black, but not off) .. dmesg notes that its stuck in a usb connect/disconnect loop, with an error:
new high-speed USB device number 33 using ehci_hcd
unable to get BOS descriptor
New USB device found, idVendor=0451, idProduct=d00f
New USB device strings: Mfr=33, Product=37, SerialNumber=0
Product: OMAP4430
Manufacturer: Texas Instruments
USB disconnect, device number 33
rinse, repeat, about every 3 seconds.
As you can see, BOS descriptor can't be found.. which is just a little stupid because the port its plugged into is 2.0
bcdUSB 2.00
but maybe there is still something there? not changing any port though, usbboot has no problem.
I sniffed the traffic of the usb bus while plugging in the USB cable after shutting down via 30 second hold, and its pretty much the same thing, just bouncing the connection before it has time to get started.. so it seems to be hitting this "issue" both on shutdown/reboot and startup. As I can't really tell, with usb being the only way for me to talk to the KF, I can only assume after a hard shutdown when I push the button again its probably doing the same thing (no lights, no screen), but I can confirm once I plug in the usb and it tries to boot itself.
Only sort of difference is sometimes it can go down into the dark reboot and I am able to run usbboot and it comes back up (usb never unplugged) but its been sporadic so I haven't chased it.
At this point I just want to figure out exactly what bit needs flipped in the front somewhere so I can reboot my KF like all the cool kids so I'll probably keep hacking on this issue until I really really brick it or hopefully help comes along or I figure it out myself. One good sign is I know have completely working dev/hack environments on OSX, win7, liveusb ubuntu AND linux mint debian so, I guess that is something.
YOU ARE NOT ALONE USBBOOT ONLY PEOPLE!! one love. =P

Bricked my Fire TV Stick 1?

Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.

I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?

l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....

mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.

l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "

bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.

l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.

bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.

Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?

If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?

Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.

One last bump for ideas before putting it into the trash.