Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Before you panic too much, you need give more information. What were you doing to "brick it"?
Have you tried a hard reset btw? (Hold the power button down for 30 seconds) then let go and turn on?
Worked for me before when I thought messed up
Kgyuszko
Sent from my KFTT using xda app-developers app
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
You were doing something in fastboot mode, What was it? did you try to install the 2nd bootloader by hashcode or just restoring your device?
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
I did something similar and have what i though 'bricked' the kindle. Have another good read through hashcode 2nd bootloader thread, others have has similar, and there are some instructions on how to resolve fastboot cable not recognised, and kndle is bricked. if not, go down the firstaide thread, that also deals with bricked kindles.
good luck
kgyuszko
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
Your problem will be overcome if you follow here
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
duncanidahoe said:
Can't get any computer or OS to recognize my kindle fire HD 7 even with the factory cable. Help!!!:crying:
I was in fastboot mode and did a reboot and when it booted back up it stuck on the start screen and won't let me do anything anymore. The fastboot cable I bought doesn't put it into fastboot mode and it is not recognized by any of my computers or OS. Tried everything but my mac so far. That includes XP, 7, 8 and Ubuntu.
I'll try a hard reset again. I've done that several times hoping that one time it would get recognized by the computer.
Click to expand...
Click to collapse
gogolovedell said:
have you successed to fix it ?
unluckily, I have the same problem.
factory cable is no use.
Click to expand...
Click to collapse
qiudongxiao said:
I just had same problem. Factory cable no use. I intalled Kinology but thought to restore to a Kindle version. When the bootloader was being flashed, a black brick ... Anyone knows how to deal with this? I even opened the case and unplug battery.
Click to expand...
Click to collapse
kindleuser01 said:
Hi, I also ahve a black brick. It won't start after I used the wrong bootloader(the one for KFHD8 isntead if KFHD7)
I do have a factory cable but still nothing.
Click to expand...
Click to collapse
You all have a paperweight on your hands. The factory cable was the very last resort. If you're in warranty, send it in for a replacement.
possible solution
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
When the OMAP USB boots, it first waits a bit to handshake with a host. If the handshake is successful, the host sends a small loader to the OMAP that then does some hardware init and handshakes again with the host to get a payload to shove into RAM. This loader is similar to x-loader in that it has to be small to fit in the SRAM of the OMAP, and does low level initialization like mux, clock, and memory setup. However it differs in that it replaces the MMC and FAT handling in x-loader with USB loading as there's not enough room for a generic x-loader that does MMC and USB.
On HS (fused) OMAPs this initial USB loader payload must be signed just like x-loader has to be for eMMC boot. If the payload doesn't have a signature that checks out, the OMAP halts until it's reset. This is enforced by hardware, so short of finding a sploit in the OMAP ROM code or a copy of Amazon's USB boot tools used in factory it's not going to work.
TL;DR not likely.
Click to expand...
Click to collapse
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
soupmagnet said:
A while back, I brought this question up to Pokey9000, the developer of FireFireFire and Firekit for the Original Kindle Fire. His exact response to me was...
Considering his knowledge of bootloaders and low level hardware stuffs far exceeds mine, and the fact that he's been looking at this issue ever since the B&N Nook devices (maybe even longer), I have to assume he knows what he's talking about.
The information on the page at Mascote seems to contradict what Pokey9000 says because usbboot uses an a-boot(x-loader) instead of this not-so-typical USB loader mentioned previously. And the answer to whether or not the author was actually successful in reviving the KFHD using this method has been left a little ambiguous.
But, as much as it would suck for me to have been the d*ck that told everyone that it couldn't be done, I would LOVE to be proven wrong.
I'd say, if you have a hard-bricked KFHD, then I guess there's not much else you can lose by testing it out.
Click to expand...
Click to collapse
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
bryanfeanor said:
searching i found this page where explain how to fix the hard brick, black screen no sing of life, cant post links so, search in google "new life for a dead Kindle fire hd, is in mascote..... can any expert try it and explain that to the rest of us,
Click to expand...
Click to collapse
Were you able to get yours going using that?
go8soccer said:
Were you able to get yours going using that?
Click to expand...
Click to collapse
sadly no, it´s been more than 3 years now that my kindle brick.
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Otak98 said:
I just recently bricked mine. Black screen. And all it does is charge. I can tell because the cable and device gets hot. Before i waste my time, would this help me. And yes i have that exact version
Click to expand...
Click to collapse
A few hours ago I was given a Tate to fix, and having read around the subject, Djskizo's post sounds either like a complicated homemade factory fastboot cable, or to be honest a fake. Perhaps the OP meant fastboot instead of ADB, but that combined with vague details puts me off trying it. Try a factory cable perhaps, I'm gonna try making one (short out micro usb pins 1 and 4) and I'll get back to you on the results.
Any updates?
Any updates on this? I hard bricked mine yesterday flashing the wrong bootloader. Can't believe how easy it is to brick it. I just have myself to blame, I know...
I saw this post on Mascote and it seems like a post for KFHD Gen 1. Is this the one being referred to, by you guys?
Only Djskizo seems to claim that this works for KFHD Gen 2(tate) so far. Is this true?
Djskizo said:
I have tried this on the 2012 KFHD (tate) and found it to work. After trying every recovery option via adb/fastboot. plus using factory cable. i was left with no choice. i used a pin needle with grounding wire attached to chassis of the kindle. be carefull the top is power(button?), bottom is restart. if you lose contact at all during the process. It will boot/reboot as normal.
with this method you must use CMD(in admin mode from pc) and adb push/pull/install/uninstall as needed. device has no input in this boot.
Click to expand...
Click to collapse
I cant seem to figure out how to do the usbboot trick. I have a fire hd 3rd gen. On the board there is actually a point that says usb boot next to it but when i ground that out and plug it in it's still froze at the unanimated boot screen, sometimes the background also turns white? What am i doing wrong or is this point labeled just to confuse me
Added photos
Here is the pic of the usb boot and the board name.
I WAS BACKING UP MY KINDLE FIRE WITH KF First Aide AND TO MY HORROR IT HAD INSTALLED THE ORIGINAL KINDLE FIRE 2 OS INSTEAD OF MY 7" KINDLE FIRE HD OS I DID NOT COMMAND KF First Aide TOOL TO DO THIS AND I SWEAR TO GOD I DIDN'T. I SELECTED FOR IT TO BACK UP MY ORIGINAL OS TO THE BACK UP FILE. NOW ALL IT DOES IS BOOT DISPLAYS KINDLE FOR A SECOND THEN GOES BRIGHT RED AND I HAVE NO IDEA HOW TO GET IN TO FAST BOOT MODE FROM HERE!!! I AM VERY ANGRY AT THE THE DEVELOPER OF KF First Aide TOOL!!! CAN SOMEONE HELP ME PLEASE. :MY QUESTION IS IF YOU COULD SO KINDLY HELP ME....HOW DO I GET IN TO FAST BOOT MODE WHEN YOU CAN NOT ENTER THE OPERATING SYSTEM CAN YOU DO IT MANUALLY OR NOT?........
I HAVE MANAGED TO CAPTURE THE KINDLE LOGO IN THE 1 SECOND IT IS DISPLAYED AND A PICTURE OF THE RED SCREEN
IF THAT HELPS
ANY HELP WOULD BE AMAZING I AM SO UPSET AND FRUSTRATED :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
pretty much the same thing just happend to me but in different words. We will both get through this together. I'm searching right now on what needs to be done.
plottr said:
pretty much the same thing just happend to me but in different words. We will both get through this together. I'm searching right now on what needs to be done.
Click to expand...
Click to collapse
Thanks buddy I will help you as much as I can with info I find. iv been told I need to get it in to fast boot mode with a factory cable but then saying that I read in another post that does not work iv purchased one of eBay to try out so ill let you know if that works
You can reflash stockboot.img and stockrecover.img files by following step 5 and it will be work well.
putin86 said:
You can reflash stockboot.img and stockrecover.img files by following step 5 and it will be work well.
Click to expand...
Click to collapse
I know that but can't enter fastboot mode
jmar8124 said:
I know that but can't enter fastboot mode
Click to expand...
Click to collapse
That's why you need the factory cable; It's used to boot the Kindle directly into FastBoot mode. From my understanding, the only way a factory cable would fail is if the bootloader is damaged.
Protomartyr said:
That's why you need the factory cable; It's used to boot the Kindle directly into FastBoot mode. From my understanding, the only way a factory cable would fail is if the bootloader is damaged.
Click to expand...
Click to collapse
Ok iv just got one of eBay now how do I use it sorry for the noody question do I just power it on and plug it in and its in fastboot? Also how could I have damaged the bootloader I hope I haven't how will I know if the bootloader its damaged? All I did was install the wrong os from the wrong kindle do your restore packages contain a bootloader?
thanks for your help
jmar8124 said:
Ok iv just got one of eBay now how do I use it sorry for the noody question do I just power it on and plug it in and its in fastboot? Also how could I have damaged the bootloader I hope I haven't how will I know if the bootloader its damaged? All I did was install the wrong os from the wrong kindle do your restore packages contain a bootloader?
thanks for your help
Click to expand...
Click to collapse
I will try to answer to the best of my ability (as I am still a noob with the Kindle HD). If anyone more knowledgeable is reading, you're input would be much appreciated
- Using the factory cable: I think you need to plug in the cable to the Kindle HD (powered off). Then plug in the other end to the computer, and it should power on to FastBoot mode. As far as what to do in FastBoot mode and what commands to use, you will probably have to ask someone more knowledgeable than me.
- Bootloader: When people say 'the bootloader is damaged' they are most likely referring to the fact that the device cannot accept FastBoot commands. When you turn on the Kindle, the bootloader decides whether to turn on the kindle in normal mode or fastboot mode. So if you can't get into fastboot mode, then the bootloader is not functioning properly for some reason.
As far as how you would damage the bootloader? Well... Iike I said before I'm a noob with the Kindle so I can't really answer this. From what I've read, the most common mistake is that people have flashed something onto the Kindle Fire HD 7 that was meant for another version of the device.
I suggest you to try working with one of the senior members/developers to troubleshoot and fix your problem.
Protomartyr said:
I will try to answer to the best of my ability (as I am still a noob with the Kindle HD). If anyone more knowledgeable is reading, you're input would be much appreciated
- Using the factory cable: I think you need to plug in the cable to the Kindle HD (powered off). Then plug in the other end to the computer, and it should power on to FastBoot mode. As far as what to do in FastBoot mode and what commands to use, you will probably have to ask someone more knowledgeable than me.
- Bootloader: When people say 'the bootloader is damaged' they are most likely referring to the fact that the device cannot accept FastBoot commands. When you turn on the Kindle, the bootloader decides whether to turn on the kindle in normal mode or fastboot mode. So if you can't get into fastboot mode, then the bootloader is not functioning properly for some reason.
As far as how you would damage the bootloader? Well... Iike I said before I'm a noob with the Kindle so I can't really answer this. From what I've read, the most common mistake is that people have flashed something onto the Kindle Fire HD 7 that was meant for another version of the device.
I suggest you to try working with one of the senior members/developers to troubleshoot and fix your problem.
Click to expand...
Click to collapse
thanks for all your help its been great ill let you know if the fast-boot lead works unfortunately the stock charging/data lead did not work because it does not supply power to 4th pin like the fastboot leads do to enter fastboot. im normally a wiz with android but the kinle fire hd 7 is one of the worst tabs i have ever owned. im not sure if you are familiar with the AOSP but part of the rules and agreements manufacturers make with Google if they choose to use android is that the system is open source and the ability for advanced super users to modify and customize android how they want it not how the device manufacturer puts it e.g. apple ios (closed source) the manufacturer is allowed to add a boot-loader and stock recovery to prevent accidental damages like wiping partitions etc.... and due to people complaining a lot of manufacturers have not included a boot-loaded unlock tool like htc dev web site but unfortunately you have got amazon...who have locked the boot-loader, disabled button combination and installed a very minimal recovery with just factory reset and reboot, this is actually against the AOSP and i do not know why Google have not done something about this its very frustrating for all of us we have to make our own system recovery tools because amazon do not include one and other such features like 2ndinit boot-loader < (thanks for that) they have actually refereed to the device os as kindle os when its an android 4.0.1 SDK build they make me so angry now i have literally got a £159 brick! i understand its an ebook but they agreed to install android as the default os so they should do it properly haha!!
but im sure in the end google will do something about it an sue them for millions well fingers crossed haha
Hi,
I'm afraid I bricked my new Kindle Fire HD 7''. Completely. After Rooting I tried to install CM using this post:
http://forum.xda-developers.com/showthread.php?t=2128848
Everything went smooth (no errors, all commands successful) until "fastboot -i 0x1949 reboot". The Kindle shut down after that. And never came back. The screen stays off (no backlight), no USB device is detected by Windows after plugging it in. Tried with factory and standard cable. Executing "fastboot [anthing]" always displays < waiting for device >.
Is there any help for my device? I've almost given up...
It is dead. What version was it, the 2012 or 2013 HD? Because the 2013 HD didn't have a bootloader that was exploitable and had no ROMs for it because of that, so by downgrading the bootloader on that model to the 2012's it would hard brick it. If it was the 2012 model and you had this happen I would guess you didn't verify the md5sum of the bootloader before flashing it. The only hope of fixing it is if someone posts the pin out for the emmc so you could solder the motherboard to sdcard reader and flash it from a PC running Linux. Its been done on the kf2 and hd8.9 so you can always hope someone posts it. Don't bother with looking into trying to flash it with USB shorting trick, it only works on the kf1 because of signed file we would need and don't have. Sorry if this sounds a bit pessimistic, I just thought I'd mention things that don't work and things that could in the future.
Sent from my Amazon Kindle Fire HD using Tapatalk
Oh sh**. It's the latest model. I somehow missed the information, that CM only runs on the 2012 model. Rooting worked great, by the way...
I haven't even heard any talk about kurohyou checking out a kfhd 2013's board to trace contacts, only some talk of the 2012 7" HD, usually the tracing process is more than likely going to ruin the board unless you are good at re-balling a emmc chip without a ir soldering station(toaster oven fun time). Since its pretty new I would assume amazon would replace it under warranty. Just tell them it won't turn on. Wouldn't mention trying to flash it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Have you tried to use the Amazon warranty? Just want to know if that would be a possbility to try some risky things with the kindle.
thank & greets
Hi everybody,
bricked my device to the point that it does not boot/react at all. Screen stays black.
Wanted to usb boot the device with FireKit following the instructions here http://forum.xda-developers.com/showthread.php?t=1430038
but my pin layout is different from the picture in the instructions. Could find any more up to date infos.
Attached a picture of my board with version info .
Any help on how to usb boot (short cut) the device and replace the boot loader is appreciated.
Thanks a lot.
Bricka
bricka said:
Hi everybody,
bricked my device to the point that it does not boot/react at all. Screen stays black.
Wanted to usb boot the device with FireKit following the instructions here http://forum.xda-developers.com/showthread.php?t=1430038
but my pin layout is different from the picture in the instructions. Could find any more up to date infos.
Attached a picture of my board with version info .
Any help on how to usb boot (short cut) the device and replace the boot loader is appreciated.
Thanks a lot.
Bricka
Click to expand...
Click to collapse
Not the right kit. Can't just use whatever on your KFHD7.At best you can get a fastboot cord and see it the tablet energizes from that. If it does then you may be able to use this tool on the forums for the Soho that can restore stock. If the fastboot cord does not energize the tablet then it's a paper weight. There is no emmc pin out link there is for some of the older tablets.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Thanks for the reply. Too bad.
Used the fastboot cord before on this device for rooting.
The cable has no effect, now. The device shows no reaction.
I still wondering what that pins/label "USB boot" are for.
They are for amazon who has a signed aboot so they can actually reflash the device using the method you are talking about, unfortunately we don't have a signed aboot, so that method doesn't work.
Sent from my Amazon Tate using Tapatalk
Thanks. Guess I have a new cutting board for the kitchen then...
If you wait long enough someone might have a pinout. I could attempt to figure it out myself but the kindle that goes through the process will more than likely never work again because it involves desoldering the emmc which is balled onto the PCB, unsoldering with a toaster oven is doable however resoldering it with a toaster oven is another story again. I Don!t particularly feel like mapping out points anyways, I get the feeling my test leads are too big cp for the job anyways.
Sent from my Amazon Tate using Tapatalk
I have a 5th gen Fire and I tried downgrading to 5.12 from 5.32.x...it didn't work... I now have a tablet which doesn't show any signs of power... I've tried different software I.e. KFU and the Kindle Unbrick tool but no luck....anyway when I connect it to the PC I hear the sound of when I plug in a USB but then about 3 seconds after then it disconnects and then reconnects and so on but never shows anything on the screen it is completely black. My problem is that it won't stay on long enough to do any significant reflash or any kind of fix. If anyone can help me in keeping it on long enough then I could flash with its stock update. I may even have to solder some points on the board but that's fine so long as I can fix it....
Thanks in advanced any help is appreciated
willie018 said:
I have a 5th gen Fire and I tried downgrading to 5.12 from 5.32.x...it didn't work... I now have a tablet which doesn't show any signs of power... I've tried different software I.e. KFU and the Kindle Unbrick tool but no luck....anyway when I connect it to the PC I hear the sound of when I plug in a USB but then about 3 seconds after then it disconnects and then reconnects and so on but never shows anything on the screen it is completely black. My problem is that it won't stay on long enough to do any significant reflash or any kind of fix. If anyone can help me in keeping it on long enough then I could flash with its stock update. I may even have to solder some points on the board but that's fine so long as I can fix it....
Thanks in advanced any help is appreciated
Click to expand...
Click to collapse
This section is for the 1st generation Fire
see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum links
Sent from my XT1254 using Tapatalk
Edit: thread moved to Fire forum
I have ended up in the exact same spot after attempting a downgrade to 5.1.1.
I downgraded to try and fix an odd problem. I recently wiped my CM version back to stock, but when registering the device it forced me into Kid's Edition - I did the downgrade in an attempt to bypass that. Now it's just a paperweight/doorstop.
dixonge said:
I have ended up in the exact same spot after attempting a downgrade to 5.1.1.
I downgraded to try and fix an odd problem. I recently wiped my CM version back to stock, but when registering the device it forced me into Kid's Edition - I did the downgrade in an attempt to bypass that. Now it's just a paperweight/doorstop.
Click to expand...
Click to collapse
Sorry for your loss; device is unrecoverable. Contact Amazon for a courtesy replacement is still under warranty.