I have been playing around with my new Kindle Fire 2 and followed some instructions to flash Fire Fire Fire, however now it won't even power on.
I'm guessing it's a bad bootloader flash, I've heard Firekit can be used but that it is first generation only, is this true? If so is there any way of unbricking the Kindle Fire 2
Also will USBboot work - or is that also 1st gen only?
jburtn said:
I have been playing around with my new Kindle Fire 2 and followed some instructions to flash Fire Fire Fire, however now it won't even power on.
I'm guessing it's a bad bootloader flash, I've heard Firekit can be used but that it is first generation only, is this true? If so is there any way of unbricking the Kindle Fire 2
Also will USBboot work - or is that also 1st gen only?
Click to expand...
Click to collapse
Cool, you managed to put a bootloader on a device before a dev did!
Yes, you bricked it. What do you mean by it won't power on? If you see a red triangle, 5 power buttons presses to do a factory reset. If it's just....nothing, here you go!
http://forum.xda-developers.com/showthread.php?t=2035047
Should work. Not positive as I haven't bricked, but that's your best bet so far. Good luck!
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
plinders said:
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
Click to expand...
Click to collapse
Good luck to you two! Unfortunately Recovering a Bricked device takes more time and know-how than simply Rooting devices, so sometimes the users are really SOL when it comes to bricking. I hope we can get more methods like the Samsung thing and PSP pandora battery that makes devices un-brickable. One day hopefully. For now, best of luck!
If it works I would post in the thread I linked and let them know how it went or if you have advice for future people that end up bricking their Kindles!
plinders said:
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
Click to expand...
Click to collapse
A factory cable is not going to do anything at this point. You have written over the uboot which is needed to even get to fastboot. The only thing you can do at this point(which is a method used for original kindle fire but I would imagine the new ones have similiar components, and try this at your own risk cause I'm not 100% it will work) is remove the back, short the usbboot pad to get the device to power on through usb only, then load the original uboot with linux using usbboot commands. That should get you into fastboot where you can then flash original bootloader and recovery.img's depending on how far the process got.
This is not an easy fix especially if you thought using KFU was a smart thing to do. There is a lot more to it than the simple explanation above.
Just out of curiosity what would possess you, because I've seen more people than I would have thought do it, to even try using a utility that was meant for the original kindle fire. There has been so much talk about these new devices having locked bootloaders. The main use for KFU was/is to load a new bootloader.
gen 2 kindle fire won't turn on.
My 2nd generation Kindle Fire will not turn on. Bought for my daughter for Christmas. She turned it off one night and the next day it won't turn on. No attempts have been made to alter it. Went I connect it to my computer it is not recognized and my computer says the device drivers are not present.
Can anyone help? When I connect my Kindle Fire it is recognized. Thanks.
ballsnxs said:
My 2nd generation Kindle Fire will not turn on. Bought for my daughter for Christmas. She turned it off one night and the next day it won't turn on. No attempts have been made to alter it. Went I connect it to my computer it is not recognized and my computer says the device drivers are not present.
Can anyone help? When I connect my Kindle Fire it is recognized. Thanks.
Click to expand...
Click to collapse
That is typical of trying to modify the device incorrectly. Considering the nature of the device, I would say it's impossible for that to just happen on it's own.
What age is your daughter? How sure are you that no attempts have been made to modify the device?
got similar issues now too. after stucked in a bootloop, i read, that the u-boot.bin from the original Kindle Update should fix the bootloader. afterwards the reboot didn't worked and the device shut down. now i cant start it anymore. and the fastboot cable wont wake it up neither.
is it now definitly broken for ever?
HELP!
Hi dear friend, can you lend me a hand on this?? is there any guide I should follow to achieve what you just described before?? please... can you tell me?
onemeila said:
A factory cable is not going to do anything at this point. You have written over the uboot which is needed to even get to fastboot. The only thing you can do at this point(which is a method used for original kindle fire but I would imagine the new ones have similiar components, and try this at your own risk cause I'm not 100% it will work) is remove the back, short the usbboot pad to get the device to power on through usb only, then load the original uboot with linux using usbboot commands. That should get you into fastboot where you can then flash original bootloader and recovery.img's depending on how far the process got.
This is not an easy fix especially if you thought using KFU was a smart thing to do. There is a lot more to it than the simple explanation above.
Just out of curiosity what would possess you, because I've seen more people than I would have thought do it, to even try using a utility that was meant for the original kindle fire. There has been so much talk about these new devices having locked bootloaders. The main use for KFU was/is to load a new bootloader.
Click to expand...
Click to collapse
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
That kindle is hard bricked, there's a slight chance of fixing if it is flashing fastboot mode for a few seconds, but I give it a 10% chance of fixing. We can't fix omap4440 bricks because while we have the means to interface with that device, we need a signed xloader for the kindle to let us flash the other partitions. We can't get the signed xloader (believe its called xloader, might be called something else) unless someone at amazon or TI were nice enough to leak it and probably get fired in the process.
On another note is that android adb composite device staying there the entire time the kindle is plugged in? If it does then you may be able to fix the kindle, I haven't heard of omap4440 and the adb composite being there at the same before. I would guess that adb is the fastboot interface but usually it says Tate when drivers aren't installed and in this case it doesn't but still has an exclamation. I'm curious....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I wouldn't say 100% out of hope...
http://forum.xda-developers.com/showthread.php?t=2391047
Or you could try using "fastboot boot" to boot the bootloader. This takes barely less time so if the fastboot flash fails, try this.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Same exact problem, did anyone find a fix?
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Steveohookem said:
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Click to expand...
Click to collapse
When you remove your OS off any device without one to install, its like giving someone a car with no steering wheel. You now need to push a ROM thru TWRP using ADB. Try using the solution that helped me, which I provided to another user in this thread:
http://forum.xda-developers.com/showthread.php?p=45188927#post45188927
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 06:10 AM ---------- Previous post was at 05:56 AM ----------
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
Creepy never seen that happen on either of my two KFHD7s. Have you tried uninstalling that driver completely? Or uninstalling those drivers thru "Device Manager" AND all others installed for /example the ones provided by Hashcode, then reinstalling them WITH the device still connected? Many times I've realized that these Kindle Fires love to have drivers juggled around. The fastboot cable I made at home using a Samsung USB does FBmode instantly. Try holding the power button for about 20 seconds while unplugged, make sure when you let go it doesn't power back on. If alls well, have the fastboot cable plugged in already to your computer, then attach it to the KF. See if that helps. If not, then believe it or not it might be a hardware failure if the screen goes black as you mentioned...
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
My bad the picture must have not loaded up last time, or I wouldn't have said that much. But more than likely he has a hard brick. Slim chance of fixing it though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
hi guys from Italy, i have the same very problem...now is the end of Settember....any good news about?????????
Not very much, unless you wanna try hooking up your emmc to a USB card reader like kurohyou did and trying to flash the stock partitions from Linux, no there really isn't any new news. That's basically the only way we have to recover from a hard brick, and it still isntna perfected process, he got his kf2 to a soft brick state after un-hardbricking it, but he couldn't un-softbrick it yet, so he is currently working on that part last I heard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Juls69 said:
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Click to expand...
Click to collapse
i think someone finished mapping the rest of the points out on the motherboard but i'm not positive, I'll have to find the thread but the only fix is to solder the kindles motherboard contact point for the emmc to a sdcard reader and hook it up to a pc running linux and flash the bootloader partition with the dd command. Keep in mind I'm referring to the hd 7 2012 model, i don't believe anyone has mapped the points for the 2013 model yet.
edit: foudn the thread: http://forum.xda-developers.com/showthread.php?t=2674737&page=3
use the tutorial for the kf2 or kfhd8.9" but use the contact points mentioned there, might take some researching to know what each of those corresponds to on the sdcard reader. Not everybody is up to soldering on their kindle to fix a hard brick.
Hello,
i found these Thread, because i have the same problems.During the boot the kindle shows the kindle logo then the fastboot logo and the screen goes black. But if use a fastboot-code at the right time, the kindle stay in the fastboot-mode. So i tried to flash the Bootloader and so from Hashwell. The output of fastboot says everythings ok, no errors, but my kindle doesn't leave the bootloop. What i done wrong? I read about the Kindle Fire First Aide-Kit, but i cant find an downloadlink, that still work.
Maybe someone of you can help with this problem.
I have a friend that wants me to fix their Kindle Fire 7 HD, it is NOT the tate model that would easily allow me to unlock bootloader and "fix" it. The tablet automatically reboots a few seconds or minutes (it varies) after it initially powers on. I try to factory reset with no change to anything, I don't think it's actually resetting it.
That model is the kfowsi. Google for that. I think there is a tool that loads a stock system image.
tjustice86 said:
I have a friend that wants me to fix their Kindle Fire 7 HD, it is NOT the tate model that would easily allow me to unlock bootloader and "fix" it. The tablet automatically reboots a few seconds or minutes (it varies) after it initially powers on. I try to factory reset with no change to anything, I don't think it's actually resetting it.
Click to expand...
Click to collapse
see [Help Thread][Kindle Fire HD] 3rd Gen/2013 Ask Any Question, Noob Friendly
http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681
I was on Fire OS 5.1.4 and I've downgraded to 5.1.2 through adb sideload, everything was ok, but after I've pressed on the device reboot, the amazon fire died, and now doesn't make any sign of life. Any way to bring it back to life?
massimilianofurlan said:
I was on Fire OS 5.1.4 and I've downgraded to 5.1.2 through adb sideload, everything was ok, but after I've pressed on the device reboot, the amazon fire died, and now doesn't make any sign of life. Any way to bring it back to life?
Click to expand...
Click to collapse
- charge the device for a few hours
- long press <power> for up to 60 sec looking for any signs of life
- try <power>+<vol-up> and <power>+<vol-down> combinations
Unlikely any of the above will yield positive outcomes but offers a small measure of comfort knowing that you tried everything short of board replacement. In most regions Amazon will replace it if still under warranty.
Hello, I the same has happened.
What have we done wrong to occur? For when we send another device that did not happen again.
Thank you.
Hey Community!
So for years I've been flashing ROMs and stuff on my android phones. Recently I bought a Amazon Fire 7 5.th Gen and tried to downgrade it from 5.1.4 to 5.1.2 so I can use the SuperTool to do the root and other stuff.
But obviously I sideloaded a 5.1.2 FW that was not meant for my Fire 7. After the next reboot the screen remained black. Pushing the power button for more than 30 secs didn't help. Same with the button combination. Opened the backcover, removed the battery, let it sit for a minute and try again. Nothing
When I try to connect the Fire7 to my PC, Windows does the typical "device attached" aka "du-dum" sound. About 1 sec later I hear the "device detached" sound. This scheme repeats iteself in a unregular cycle. Sometimes the device gets attached again after 2 secs, sometimes after 10 sec.
Bought a Factory Cable. Connected it... nothing. So now I think i got a solid hard brick for 23 Euros (plus 10 € for the cable). My hope is gone, but maybe someone got another hint?
Thanks for your help!
I don't think the back cover for the fire 7 (2015) is removable. Are you sure you have identified the device correctly?
dustin66 said:
Hey Community!
So for years I've been flashing ROMs and stuff on my android phones. Recently I bought a Amazon Fire 7 5.th Gen and tried to downgrade it from 5.1.4 to 5.1.2 so I can use the SuperTool to do the root and other stuff.
But obviously I sideloaded a 5.1.2 FW that was not meant for my Fire 7. After the next reboot the screen remained black. Pushing the power button for more than 30 secs didn't help. Same with the button combination. Opened the backcover, removed the battery, let it sit for a minute and try again. Nothing
When I try to connect the Fire7 to my PC, Windows does the typical "device attached" aka "du-dum" sound. About 1 sec later I hear the "device detached" sound. This scheme repeats iteself in a unregular cycle. Sometimes the device gets attached again after 2 secs, sometimes after 10 sec.
Bought a Factory Cable. Connected it... nothing. So now I think i got a solid hard brick for 23 Euros (plus 10 € for the cable). My hope is gone, but maybe someone got another hint?
Thanks for your help!
Click to expand...
Click to collapse
NightCrayon said:
I don't think the back cover for the fire 7 (2015) is removable. Are you sure you have identified the device correctly?
Click to expand...
Click to collapse
- back cover on 5th gen Fire can be removed with a bit of 'encouragement'
- no unbrick solutions (yet) for the described scenario
- if still under warranty contact Amazon for a one time no-questions-asked courtesy exchange
Davey126 said:
- back cover on 5th gen Fire can be removed with a bit of 'encouragement'
- no unbrick solutions (yet) for the described scenario
- if still under warranty contact Amazon for a one time no-questions-asked courtesy exchange
Click to expand...
Click to collapse
"Encouragement" is the right answer
Gonna trie an exchange. I know the kindness of the support so I feel a bit guilty to ask for a refund for my failure. But lets see. TY for your answer