Whilst attempting to flash CM11, I ran into problems. Twrp was installed and successfully booted into recovery, but CM11 wouldn't boot, I kept getting the KF bootlogo.
In trying to fix it, I erased the boot and bootloader img files, but accidentally pulled the fastboot cable before I could reflash them.
The device now won't boot, even using the fastboot cable. I've tried holding the power switch for up to 2 minutes but nothing.
Is the device beyond saving?
thanks
Does the screen even turn on?
Sent from my LG-P769 using Tapatalk
hello stunts
no, nothing happens, screen is totally blank which doesn't give me a good feeling
cecr said:
hello stunts
no, nothing happens, screen is totally blank which doesn't give me a good feeling
Click to expand...
Click to collapse
If it doesn't even turn on,I'm afraid it's hard-bricked.
thanks for your reply safinwasi, what does it mean though, is it totally beyond repair? I read about opening the case and shorting something out but think it was for a different model and the instructions seemed incomplete.
can anything be replaced to restore it?
just bumping this to see if there is anything that can be done with this device
If you have a steady hand, a soldering iron, and a USB sdcard reader, then it is salvageable.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
If you have a steady hand, a soldering iron, and a USB sdcard reader, then it is salvageable.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thanks for your replies. I thought recovery was possible but didn't know how. I managed to find someone who knew how to do this and now my Fire is working again
Related
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?
Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?
khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.
just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.
The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.
demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:
All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.
I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium
Hi all,
Kindle fire HD ( rooted) got OTA update and after the update its stuck on the Kindlefire logo screen. Tired resetting it by pressing 20sec / also tried 30 sec but no joy. Also tried pressing the volume Up and power but its stuck on the kindlefire log.
Tried to run recovery (KFFA) but my laptop does not detect kindle fire at all. I guess factory cable is the last option but I dont have it and need to order one . But I was wondering if Amazon could replace it under warranty ?
Cheers
ipsearch said:
Hi all,
Kindle fire HD ( rooted) got OTA update and after the update its stuck on the Kindlefire logo screen. Tired resetting it by pressing 20sec / also tried 30 sec but no joy. Also tried pressing the volume Up and power but its stuck on the kindlefire log.
Tried to run recovery (KFFA) but my laptop does not detect kindle fire at all. I guess factory cable is the last option but I dont have it and need to order one . But I was wondering if Amazon could replace it under warranty ?
Cheers
Click to expand...
Click to collapse
Of course your computer won't detect it, ADB requires both devices to be fully-booted and can communicate. Use your regular cable to boot into fastboot and restore. Read my thread in my signature, #6 & #7.
seokhun said:
Of course your computer won't detect it, ADB requires both devices to be fully-booted and can communicate. Use your regular cable to boot into fastboot and restore. Read my thread in my signature, #6 & #7.
Click to expand...
Click to collapse
Thanks for the reply, I will try to follow your post #6 & #7.
I am still confused, I had only rooted Kindle and got google play installed and it was working fine. It seems that there was OTA firmware upgrade and after that upgrade when the device rebooted its stuck on the kindle fire screen.
Appreciate your reply.
Cheers
I dont know what is going on ? Android SDK is installed and even ADB is working but somehow my laptop does not detect the Kindle. It is just stuck on waiting for device.... ?
Getting error on step 2 Qemutool.bat ?
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Pls help.
ipsearch said:
I dont know what is going on ? Android SDK is installed and even ADB is working but somehow my laptop does not detect the Kindle. It is just stuck on waiting for device.... ?
Getting error on step 2 Qemutool.bat ?
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Pls help.
Click to expand...
Click to collapse
Try using root with restore by bin4ry.
Sent from my air conditioner unit running CyanogenMod
dugoy13 said:
Try using root with restore by bin4ry.
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Tried Binary too but does not work.
Possibly Solved
ipsearch said:
Tried Binary too but does not work.
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Dude, no offense meant really, but posting this big long thing everywhere isn't really helping anybody.....
If your kindle is stuck, you'll need a factory cable. You need to be able to get to fast boot so you can use the Kindle SRT tool, that allows you to flash a clean ROM to your device through fast boot.
Sorry...
DroidIt! said:
Dude, no offense meant really, but posting this big long thing everywhere isn't really helping anybody.....
If your kindle is stuck, you'll need a factory cable. You need to be able to get to fast boot so you can use the Kindle SRT tool, that allows you to flash a clean ROM to your device through fast boot.
Click to expand...
Click to collapse
They had similar problems giving similar answers. I was just trying to solve the problem.
CVanB said:
They had similar problems giving similar answers. I was just trying to solve the problem.
Click to expand...
Click to collapse
Sorry, didn't mean anything anything bad by that, I just found it's always easier to try the simple things first one by one and not overload with info because the problem usually is just something simple. I wasn't saying that you shouldn't try to help, that's what we should do as a community, just that we should take it one step at a time with simple items first. Again didn't mean anything bad, hope you weren't offended
from my Viped out one x
DroidIt! said:
Sorry, didn't mean anything anything bad by that, I just found it's always easier to try the simple things first one by one and not overload with info because the problem usually is just something simple. I wasn't saying that you shouldn't try to help, that's what we should do as a community, just that we should take it one step at a time with simple items first. Again didn't mean anything bad, hope you weren't offended
from my Viped out one x
Click to expand...
Click to collapse
It's okay, so the problem is solved? Also, ipsearch make sure you look on the forms for your problem because, other people may have the same problem and it might already be solved no offense.
CVanB said:
It's okay, so the problem is solved? Also, ipsearch make sure you look on the forms for your problem because, other people may have the same problem and it might already be solved no offense.
Click to expand...
Click to collapse
Manage to boot Kindle HD, had to use factory cable, then used SRT tool and use option 4 and that manage to fix it. THANKS EVERYONE for your help.
HELP
Hi there guys, I can see that some of you already solved the problem. In my case, I have an UNrooted kindle fire HD. It suddenly shut down when I was playing. ANd then now, it wont open anymore. Been trying to read some forums and stuff but it still wont get fixed. It opens, but only up to the KINDLE FIRE logo only. I dont really know that happened and I dont have a freakin' clue on how to fix it. Can somebody help me please? I miss my kindle so much.:crying:
letsyrkdelrosario said:
Hi there guys, I can see that some of you already solved the problem. In my case, I have an UNrooted kindle fire HD. It suddenly shut down when I was playing. ANd then now, it wont open anymore. Been trying to read some forums and stuff but it still wont get fixed. It opens, but only up to the KINDLE FIRE logo only. I dont really know that happened and I dont have a freakin' clue on how to fix it. Can somebody help me please? I miss my kindle so much.:crying:
Click to expand...
Click to collapse
I am not an expert but this is what helped me.
(1) Try charging the knidle
(2) also try getting Factory cable and use the recovery tool.
Cheers
ipsearch said:
I am not an expert but this is what helped me.
(1) Try charging the knidle
(2) also try getting Factory cable and use the recovery tool.
Cheers
Click to expand...
Click to collapse
HI, yes i've tried charging the kindle using my laptop. Well, the battery is drained. And it charges for quite sometime and then when it gets enough charge, it opens by itself. I cannot hold the power button for it will shut down and wont push thru charging. HEnce when I leave it charging, like I said it would open on its own then eventually shut down on its own again. At this part, I dont know if it still charges. Tried leaving it overnight too but still wont open. As for the factory cable, I dnt know where I could get it. I am from the Philippines. And how do I get that recovery tool? Thanks
Hey guys I have a kindle fire that was running 7.4.6.. I rooted it without any issues and tried to install the Cynogen mod. I was then sent into a bootloop because the TWRP wouldnt load but i was able to get it into fastboot Before the blue kindle logo. I used KFHD_SRTv1.3.5 in an attempt to restore it back to factory settings. I am unable to get out of this loop as my video below will show. Please help me! I understand I am a novice at this and shouldnt of been tinkering around with it since I dont know much about kindles or android for that matter.
youtu.be/viFtTpe059s
dkrutz said:
Hey guys I have a kindle fire that was running 7.4.6.. I rooted it without any issues and tried to install the Cynogen mod. I was then sent into a bootloop because the TWRP wouldnt load but i was able to get it into fastboot Before the blue kindle logo. I used KFHD_SRTv1.3.5 in an attempt to restore it back to factory settings. I am unable to get out of this loop as my video below will show. Please help me! I understand I am a novice at this and shouldnt of been tinkering around with it since I dont know much about kindles or android for that matter.
youtu.be/viFtTpe059s
Click to expand...
Click to collapse
And you're holding down the + volume button when it boots?
G_G_L said:
And you're holding down the + volume button when it boots?
Click to expand...
Click to collapse
I have indeed tried that multiple times I did not in the video because it doesn't seem to do anything
You need a factory cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
I am using a factory cable
dkrutz said:
I am using a factory cable
Click to expand...
Click to collapse
Just to confirm...
factory cable = fastboot/programming cable
...not the stock USB cable
fastboot cable worked like a charm thank you
soupmagnet said:
Just to confirm...
factory cable = fastboot/programming cable
...not the stock USB cable
Click to expand...
Click to collapse
I haven't found any other thread where someone admitted to doing something this dumb. Was set to install Go Launcher on KFHD, thought i had copied it to device. Used ROM Toolbox Pro to freeze stock launcher.apk. Started having problems navigating on KFHD when going to flash go launcher (I know I should have done that first, especially now). Rebooted without thinking about not having a launcher. Now it wont boot into anything usable. Win 7 pc cant find it thru USB even when I was going to try to copy the stock launcher over somewhere. Running stock ROM. Can't boot up into any kind of recovery mode. Willing to do factory reset but can't figure that out from where i'm stuck either.
Any ideas on how to either recover to stock or unfreeze stock launcher w/out access to any launcher? Any and all help is appreciated.
UPDATED: I have just ordered SkOrPn's Factory Cable (as described here: http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9) in case that is part of anyone's solution.
Its is part of the solution, u just need to reflash the system image from kindle fire first aid in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its is part of the solution, u just need to reflash the system image from kindle fire first aid in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
No way to bring up a recovery screen using the power and vol buttons, huh?
When i reboot w/ this cable it should be detected as usable by Win7, right?
If it can't find drivers for it use the ones in my signature, also stock recovery is useless, u can't get into it from a key combo, only if certain circumstances happen do u even get into it, and all it allows u to do is factory reset which typically is pointless and just wipes your data.
Another thing to mention, just plug the fastboot cable in until your kindle displays "fastboot" on the screen, once that happens switch back to using a normal cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If it can't find drivers for it use the ones in my signature, also stock recovery is useless, u can't get into it from a key combo, only if certain circumstances happen do u even get into it, and all it allows u to do is factory reset which typically is pointless and just wipes your data.
Another thing to mention, just plug the fastboot cable in until your kindle displays "fastboot" on the screen, once that happens switch back to using a normal cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
10-4. I've got the right drivers, was blowing things out and in pretty well until I screwed up the launcher. Thanks!
SUCCESS!
Device went into fastboot immediately when using skorpn's factory cable, but couldn't get my kindle recognized by Win7 to use adb. Installed drivers from 3 or 4 different sources with no luck, but sparkym3's did the trick (http://forum.xda-developers.com/showthread.php?t=1893838). Ran onemeila's restore (http://forum.xda-developers.com/showthread.php?t=1951254) from the img with built-in Apex launcher, and voila!
I just got my kindle and didn't like the kindle fire hd os so i tryed to get it to an android os. I followed this guys video and it worked so far until i got the the twrp recovery. i did the command fastboot -i 0x1949 reboot and it shut down but never rebooted. Plz help!!!
More details please, though I'm guessing based on what happened you flashed the wrong bootloader in fastboot then rebooted. If that's the case it is hard bricked. But more details will be helpful to diagnose this to make sure, like what commands you ran or what exactly you did.
Sent from my Amazon Kindle Fire HD using xda app-developers app
More details
stunts513 said:
More details please, though I'm guessing based on what happened you flashed the wrong bootloader in fastboot then rebooted. If that's the case it is hard bricked. But more details will be helpful to diagnose this to make sure, like what commands you ran or what exactly you did.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
here are some more details:
-I was watching a video on how to change the os on the kindle fire hd 8.9 inch and I thought it would work on kindle fire hd 7" and everything did work even the fastboot or something like that pooped on the screen while i was doing some commands. Then when i did the command for the fastboot reboot it turned of and never came on. I tried many ways of getting it back on like holding the power button for 20 seconds and then trying to turn it back on. Then i thought it might still be running so I thought that maybe leaving it without a charge for a while would do it and so far nothing. I started this yesterday and yesterday was when it stopped working. Still haven't charged it yet. Also is there anyway for my kindle to be restored and back to normal with that kind of hard brick. (i am a noob at this ) Thx for your response!
robotdjman said:
here are some more details:
-I was watching a video on how to change the os on the kindle fire hd 8.9 inch and I thought it would work on kindle fire hd 7" and everything did work even the fastboot or something like that pooped on the screen while i was doing some commands. Then when i did the command for the fastboot reboot it turned of and never came on. I tried many ways of getting it back on like holding the power button for 20 seconds and then trying to turn it back on. Then i thought it might still be running so I thought that maybe leaving it without a charge for a while would do it and so far nothing. I started this yesterday and yesterday was when it stopped working. Still haven't charged it yet. Also is there anyway for my kindle to be restored and back to normal with that kind of hard brick. (i am a noob at this ) Thx for your response!
Click to expand...
Click to collapse
You hard bricked you're tablet. There is no recovery for this at this time. The ROM's are specific for the model and firmware.
HardBrick
LinearEquation said:
You hard bricked you're tablet. There is no recovery for this at this time. The ROM's are specific for the model and firmware.
Click to expand...
Click to collapse
ok well, i was researching about a factory cable for hard bricked kindles. I was wondering if that would work at all? I don't mind if i get my apps or books back as long as it get working again.
Also thanks for your help!
robotdjman said:
ok well, i was researching about a factory cable for hard bricked kindles. I was wondering if that would work at all? I don't mind if i get my apps or books back as long as it get working again.
Also thanks for your help!
Click to expand...
Click to collapse
The factory cables help with soft bricked Kindle's. You can get a cord and try it if you want. Flahing a Jem to a Tate is almost a sure hard brick. If you plug your tablet via USB into your PC, look in the device drivers area on your PC, do you see "OMAP" anywhere?
Devices
LinearEquation said:
The factory cables help with soft bricked Kindle's. You can get a cord and try it if you want. Flahing a Jem to a Tate is almost a sure hard brick. If you plug your tablet via USB into your PC, look in the device drivers area on your PC, do you see "OMAP" anywhere?
Click to expand...
Click to collapse
Do you mean device manager, if so i don't see that there, and hard brick means its dead and ill have to buy a new one right?
If its still under warranty just send it in to amazon and tell them it won't turn on, that by itself should get you a free replacement.
Sent from my Amazon Kindle Fire HD using xda app-developers app