Related
Hi guys,
I've screwed up royally...
I got my Kindle Fire 2 (not HD) today and... tried to root it. Unsuccessfully.
It's now got a flickering Kindle Fire logo and it's responding with a 30 second to 1 minute lag (so unusable).
My Vista laptop still recognises it as an ADB device but I don't know what to do now
Can anyone help me please?
Many thanks.
EDIT: I've held the power button for 20+ seconds and it still does this...
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
433Mhz said:
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
Click to expand...
Click to collapse
Thanks I'll try that and report back
It's beyond laggy though, so it's gonna be a pain
UPDATE: I love you 433Mhz It's worked, I wish I could give you a million thanks. I really hope Amazon reverse their stance on the locked bootloader with an OTA update, because that was all I wanted to start with haha.
Thanks again mate
Think I'm bricked
The root process went perfectly clean and it rebooted fine. Then I couldn't find instructions to install the Play Store. I finally found some that said to copy GoogleServicesFramework.apk to the Kindle and install, I did that cleanly. Then to copy vending.apk to /system/app/ and I did that and was able to change permissions to 664. I then rebooted the Kindle. It goes straight to the triangle. If you push the power button 5 times it reboots to the same thing. I did not try to flash TWRP to it because I saw some having problems with it. I have 10.2.1 on it. I have the proper drivers installed and each time the Kindle rebooted during boot the computer beeped that it recognized it. Since the triangle the PC no longer recognizes it, it does not show up in Device manager and it does not show up in explorer as connected. I think it is hard bricked but wanted to run it by everyone.
Sparkym3's root process went flawlessly on my Fire2, It only took a couple minutes to root and be booted to a working Kindle. I just screwed up the market process somehow.
Let me know your thoughts. Being that everything went so clean with rooting I have a hard time thinking it can be the drivers, cable, usb port.
I've rooted a phone and 2 tablets multiple times but never had this happen. Any help is greatly appreciated.
This is an exact description of the problem:
I get the Kindle Fire logo, sits there several seconds, reboots and the power light goes out and back on, then the logo comes up again, it flashes a couple of times then I get an orange triangle with an exclamation point inside Below that is a message stating "Your Kindle device cannot boot".
Below that is You can reset device to Factory defaults to fix this issue (all data will be deleted from the device"
<Menu options>
To reboot your device, press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession.
Well the 4 second thing does not work at all, more like 20 seconds. The pressing 5 times just reboots to the same problem and warning triangle. I tried fastboot commands but nothing.and my laptop no longer recognizes the Kindle and nothing is in Device Manager about the Kindle now. The fastboot command just says waiting for device. As I said above the root process went flawlessly and the Fire reboot 3-4 times and the laptop beeped each time that it saw it.
Any help is greatly appreciated
So, I'm totally lost. Maybe a frisbee at this point.
http://forum.xda-developers.com/showthread.php?p=33156486
Trys this
Sent from my SAMSUNG-SGH-T989 using xda premium
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
Ops wrong link srry tthast for the hd :banghead:
Sent from my SAMSUNG-SGH-T989 using xda premium
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.
Hello,
I had a KFHD 7" 2012 a while back. I reverted it from CM11 to Fire OS. That red screen came up (was about 3 years ago so don't remember exactly what it said).
I got a fastboot cable and it booted to fastboot, and I reflashed the bootloader.
One problem: the wrong bootloader. I flashed the bootloader for the original Kindle Fire.
Hard Bricked. No response from ANYTHING. Nothing. I can open the back cover, but don't know what to do when inside. Any USB Boot thing I need to do?
Not even plugging it to my PC comes up with ANYTHING in device manager.
It was my sister's tablet, she got a Galaxy Tab Pro and I still have my Tab S, but I'm kinda curious if theres still hope for it. Who knows? Maybe I'll donate it if it gets fixed.
Thanks in advance
-Ryan
Wow. This seems like a HUGE problem. If the Kindle doesn't respond, then this is really bad.
Are you sure the Kindle Fire isn't responding? Have you tried forcefully turning it off (press power button for up to 20 seconds), and then plugging it into the fastboot cable? If it can get to the Fastboot logo then I think you can unbrick it.
I just need to remember the link to the Ultimate Unbrick Tool. If the device isn't showing up in the device manager (starts with tate) in any of the dropdown menus, there is most likely NO fix for this.
DarknesGaming said:
Wow. This seems like a HUGE problem. If the Kindle doesn't respond, then this is really bad.
Are you sure the Kindle Fire isn't responding? Have you tried forcefully turning it off (press power button for up to 20 seconds), and then plugging it into the fastboot cable? If it can get to the Fastboot logo then I think you can unbrick it.
I just need to remember the link to the Ultimate Unbrick Tool. If the device isn't showing up in the device manager (starts with tate) in any of the dropdown menus, there is most likely NO fix for this.
Click to expand...
Click to collapse
Ok I've shorted the USB_BOOT pin and it's coming up in Device Manager as "OMAP44xx USB DEVICE."
No display on the screen no matter what I do.
I've tried compiling USBBoot from source and running it on a Linux machine, and it recognizes the device, and gets stuck at "Unknown Error: -7"
There is not much documentation on this tool so I wonder if anyone knows.
(Actually, if anyone knows, it's probably @Hashcode, but I really doubt I can get a hold of him)
Nandr0idC0nsumer said:
Ok I've shorted the USB_BOOT pin and it's coming up in Device Manager as "OMAP44xx USB DEVICE."
No display on the screen no matter what I do.
I've tried compiling USBBoot from source and running it on a Linux machine, and it recognizes the device, and gets stuck at "Unknown Error: -7"
There is not much documentation on this tool so I wonder if anyone knows.
(Actually, if anyone knows, it's probably @Hashcode, but I really doubt I can get a hold of him)
Click to expand...
Click to collapse
I'm going to take a wild guess and say that a udev rule might need to be added into Linux. I'm not sure though, as I don't think this has been done before with a kindle in this state. I'm going to do research on it before replying any further.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I'm going to take a wild guess and say that a udev rule might need to be added into Linux. I'm not sure though, as I don't think this has been done before with a kindle in this state. I'm going to do research on it before replying any further.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you for the reply - you actually may be right. I'll try that when I get home but I haven't a clue how to udev so... yeah some research will be done on my end too.
Thanks!