Good evening scholars, I am at a end with my Kindle Fire. Below is an
exact account of what I was doing and thus the end state of what is now my Kindle.
I have a rooted kindle. Basic root, nothing significant like CynMod. The boot-loader is stock and all. The only thing I really
installed that is not stock is a different Launcher since Amazon's Launcher is just horrid in my opinion.
I was in Rom Toolbox Pro uninstalling Chameleon Launcher because I wanted to run
Apex Launcher instead. So I uninstalled it. At this point there is no launcher running.
I'm using Rom Toolbox as a console so-to-speak. Simply going from one program to the next without actually ever hitting
the home button. So I go to install Apex Launcher and it says installing. However, it didn't do anything at all.
The status bar never moved; simply stayed at 0%. SO! No biggie, I've seen this before. So to make sure it is not Apex or something
I go to the stock Amazon Launcher. I had a backup and tried to install it through Rom Toolbox. Same thing happens,
No response, idle status bar, etc, etc. So at this point I assume it is Rom Toolbox. So I hit the home key on the slide menu.
Well, I have no launcher currently installed so it did nothing. Go figure. So I decide to do a hard reset. So I hold down the power button.The Kindle shuts off and then my troubles started. I hit the power button and it doesn't pass the Kindle is upgrading notice.
So I do another Hard reset adding insult to injury...but, the same thing again. Turn it off again, plug it in to my computer and attempt a fastboot with the stock cable, same results occurred.
So now my kindle shows the standard Kindle Fire Logo at the beginning of the boot cycle and then stops at the Kinde is upgrading...Starting Applications... prompt. Like the link to the photo below.
h ttp://i61.tinypic.com/2s0eeer.jp g
I try rectifying this, reading several articles.
I tried utilizing the Kindle Fire First Aid, the KFHD SRT, even looking into the android SDK a little. But they either - A. Don't recognize the device or, B. Prompts for superuser. Seeing as how my Kindle barely boots how can I check for a superuser prompt?
I go went into my device manager and looked to see if windows registers the Kindle and it does. The device manager displays Hardware ID's indicating something is there.
USB\VID_1949&PID_0007&MI_00
USB\VID_1949&PID_0007&REV_0216&MI_00
I have my hunches on what the problems could be. But I've been working this for a couple days now and have become agitated.
I have never had to many problems with this type of stuff. I won't say I'm a noob at this kind of work however, I feel like it at this point.
Worst comes to worst I would crack her open. But that is risky business. I rarely touch the inside of my devices.
Any words of wisdom are most appreciated.
If you happen to have adb access I'm guessing there's a system app that needs to be chmodd'ed to the right permissions, or if you want you could run "adb reboot bootloader" (and do what I mention next after it's in fastboot mode), however if you have no adb access then you will need to get a fastboot cable and restore with kfhd SRT or kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
As I said before the Kindle does not respond when I use KFHD SRT or the Aid Kit.
That's because for those tools to work you need to already be in fastboot mode with the fastboot drivers installed. Have you managed to get into fastboot mode?
Sent from my Amazon Kindle Fire HD using Tapatalk
As of now what you see is what you get. All I get is a never ending boot screen. I see you made a comment about fast-boot drivers. I might be missing something in the equation. I'm going to retrace my steps and start from scratch. Hopefully I will be able to get this thing working.
Well, I cannot get my Kindle to boot into fastboot. Tried reinstalling ADB drivers and everything. Even tried using the First Aid with no luck. I think the boot loader might be damaged. I keep the kindle off, plug it in, try to initiate a fastboot through the KFFA, it dims and continues normal boot operations. Stopping with the Kindle is upgrading notification.
Those commands aren't going to work unless adb was ever active in the first place, you are going to need a fastboot cable to fix it, the bootloader is behaving just as it should BTW, so it is fine, once you get a fastboot cable it will tell the device to enter fastboot when it powers on, from there kffa should work just fine outside of probably having to install Tue drivers because of how finicky it is. The ones in my signature will surface when the time comes.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Related
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
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Got a brand new Kindle Fire HD 7" for Christmas, obviously couldn't leave it alone. I have rooted about a dozen models of Android phone, and jailbroken multiple iPhones, so I know the trials and tribulations of this process...
So I attempt to root my KF using the Bin4ry and Qemu method. I have a AWFUL time getting the drivers to properly recognise my KF. I end up finding another person's issue such as mine, and go through the LONG way of downloading the adt bundle, and installing all of the google software and drivers that way. EUREKA! Drivers work, KF recognised by my machine. First shot with Bin4ry after the driver mishap, works fine. Takes 2 attempts with the second step with the Qemu method, but again, I get there. after the first time booting up, I factory reset the Kindle. Still have SU on the apps list. Cool! Now what?
I boot the machine and shut it down about 5 times just to check stability, and hard shutdown (power button for 20+ seconds) twice. Every time all is ok, and SU is still there.
Now time to play. I again go through reading a couple threads on changing the launcher, and decide to go with the Nova launcher for now. I download it from the Play store, yet can't seem to find it on my KF. I for some god awful reason decide "well I saw it a couple threads ago, that someone had an issue with the launcher change the name of launcher.apk to launcher.apk1 and then it worked" so obviously I go and do that. Enter the final time I would boot my KF.
Upon reboot, I get the stock/standard "kindle fire" screen with no animation at full brightness. It then goes black for a split second, and comes back with the "kindle fire" screen, but now with the animated "shiny streak" that goes across the logo. I left it there multiple times for a half hour +, no change.
So I don't freak out yet, cause it turned on, and I find it can't be all that bad. So I check for it in device manager...nothing. Check My Computer just to see if its recognised for memory storage...nothing. I run the Bin4ry script again, just to see...nothing. Run Qemu just to be thorough...nothing. Restart my computer, repeat ALL above steps...nothing. Still never see's the KF, also never makes a tone at me when I plug the kindle into the cable. Change USB ports, repeat all, nothing. Back all of the drivers out, and reinstall all of them. Restart. Nothing. Download kindle unbrick utility, that still doesn't see the KF. No adb shell commands ever let me even see that it is seen somehow my my computer.
So now I am stuck. It still seems to me to be a driver issue, but I seriously cannot see how that is possible. I guess while waiting for a response from one of the guru's here, I will repeat my process of backing all of the previous drivers out and reinstalling them. There is NO other software on the kindle except for the Nova launcher and whatever the Bin4ry and Qemu methods install on it.
Sorry for the long post, but I figured it would be better than leaving you guys to ask more questions, though I'm sure you will anyways. My KF is running 7.2.3 before all of this happened...
Thanks for any help, sorry to be that guy!
Jordan
skeeter7424 said:
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Thanks for any help, sorry to be that guy!
Jordan
Click to expand...
Click to collapse
Well the good news is you don't have a driver issue, Its seems you are just stuck in a boot loop and at that point in the boot process adb is not recognized. Check out this thread on how to restore it: http://forum.xda-developers.com/showthread.php?t=1951254
By the way you will need a factory cable. There is a link in the above thread for where to purchase(someone told me they've gotten them on amzon as well). Don't worry they are cheap, about $10-15.
So I see it listed all over the place, but I take it the factory cable is not the one that was supplied in the box?
edit: now i have found what everyone is talking about and have found the writeup on the cable. I am currently sitting at my desk making myself this cable now...we'll see how this goes!
So I got the factory cable made correctly, plugged it in, boom, computer recognizes it. I reload software from the kindle unbrick utility. Now it goes into straight bootloop, KF home screen, blank, KF home screen, blank. Tried with both the factory cable and the stock cable. No changes. Am letting it completely die today to attempt to plug into computer and let it recognize. Should I do this part with the stock cable or the factory modded cable?
skeeter7424 said:
I reload software from the kindle unbrick utility.
Click to expand...
Click to collapse
What are you referring as "the kindle unbrick utility"? Did you try to use KFHD System.img Restore Tool ?
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
skeeter7424 said:
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
Click to expand...
Click to collapse
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
onemeila said:
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
Click to expand...
Click to collapse
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
skeeter7424 said:
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
Click to expand...
Click to collapse
You made your own factory cable right? Did you use a resistor and if so what size? Sounds like you could have shorted something out, cause I've never heard of this problem but I know you can do a lot of damage to both device and pc if a factory cable is not made correctly with at least a 1k resistor(if I remember correctly).
Do you get the fastboot screen. And also I did not use resistor when I made my cable and it works just fine. Only thing weird Is That once I have fastboot screen I have to unplug my fastboot cable and use original cable in order to flash anything but I have had no other issues. Hope this helps.
Sent from my KFTT using XDA Premium HD app
Need a bandaid?
Try this.
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.
Hi this is my problem nephew got kindle fire hd 7 for xmas stupid idea hes only 11 anyway he has put a pin in to the tablet and now has forgotten it when you boot it up all it does is ask for a pin there is no way of getting in to it,how can I get in to this tablet I have some idea of what im doing rooted tablets before so I know how to use adb,now adb see the device gives me a number but I tried to use KFFirstAide to restore the kindle but the programme isn't working as its telling me adb is not working ive looked in to hacking the pin to get into it but from what I have read and watched online its saying you need to have adb working but yet I don't think its enabled on the tablet does anyone know of a back door like on android when you holed the volume down you get the dead droid then you can go to option of restore or is there another way to get into this tablet its brand new never been played with just pin put into it and now cant get into it anyone guide me or help me please proper head scratching happening at the momement thanks in advance
I thought if you typed the pin in wrong enough times it would give you the option to restore factory defaults. If adb wasn't on then I don't see you turning it on externally. If it doesn't present you with a way to format it then I suggest getting a fastboot cable and using fastboot mode to clear the userdata, that would probably do the trick.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
ok will look into this cable thx,and still look to see if there is a way to get this sorted in the mean time thx
Please help.. I have tried to flash my Kindle Fire HD and things turned out pretty bad. When I turn on my kindle fire hd 7 inch the screen goes RED instantly and nothing happens. I believe it is bricked. I have tried to fix this after buying a FASTBOOT cable and that didn't do anything. When I plug my Kindle Fire HD into my computer via the fastboot cable the screen on the kindle says "Fastboot" and a small Kindle Fire text..
I tried using this method to fix it: http://forum.xda-developers.com/showthread.php?t=1951254
But this did not work.
I have uploaded pictures from my phone below on what happens on that tool.
Please help :/
Is this fixable?
and yes. I did install adb + Android SDK + Kindle Fire Drivers properly I believe. But adb says waiting for device forever + fastboot.
http://i.imgur.com/BOdAwrQ.jpg
http://i.imgur.com/UIYvWhF.jpg
It looks like you're using Windows. Can you look under the Device Mananger to see what the Kindle Fire shows up as? (Sorry if I got the name of the program wrong- I haven't used Windows in months).
rioc0719 said:
It looks like you're using Windows. Can you look under the Device Mananger to see what the Kindle Fire shows up as? (Sorry if I got the name of the program wrong- I haven't used Windows in months).
Click to expand...
Click to collapse
I don't think anything comes up. I installed drivers successfully and everything too. And windows randomly disconnects the Fastboot cable or at least makes the noise when I barely moved the plugged in Kindle Fire HD.
Now it says on that program, "sending system 907833 KB" or something like that
then after like 30 minutes or so it says successful. I reboot my kindle then same thing. red screen. So IDK what to do at this point. :/
Sometimes it cancels on the tool and says "error: too many links"
Anyways. If anyone helps I would gladly pay them. Thanks
WELL, Looks like I finally fixed it. After almost a year of bricking it LOL. Thank you XDA for helping with your tools xD
Peace out.
/reqclose
Would you mind posting how you fixed your Kindle to help other users?
rioc0719 said:
Would you mind posting how you fixed your Kindle to help other users?
Click to expand...
Click to collapse
OK, so basically there is a tool out there that will literally restore your KFHD or Kindle Fire 2 if you brick it, etc. It is 100% automated all you need is a
Fastboot Cable
Computer with Windows/Linux
Bricked Kindle
USB Port
The program is here: http://forum.xda-developers.com/showthread.php?t=1951254
It is a bat file, and choose options 1-3 for whatever kind of restore you want. Make sure you have installed Kindle Fire Drivers before doing so.
You use that on a kf2 you'll wish you hadn't. There are separate SRT tools for Tate and Jem. That is the 7" and 8.9" 2012 KFHD.