This is my first post on the forum so i say hello everyone! First sorry for my English I have a bricked Kindle Fire 2 After root and installing TWRP Recovery my Kindle flashlight was shinging orange color and it was suspended. I turn it off and now i can't charge it and i can't turn it on. The flashlight is dark, not shining. I try Kindle Unbrick Utility, Firekit Live USB but my KF is still dead. Can someone help my with my problem? What should I do?
Does your computer recognise the device? I mean at all? If not then more then likely your logicboard/motherboard on the kf2 might be dead which will make your kf2 as useful as a paper weight ( just telling the truth)
Sent from my Amazon Kindle Fire using xda app-developers app
czechu85 said:
This is my first post on the forum so i say hello everyone! First sorry for my English I have a bricked Kindle Fire 2 After root and installing TWRP Recovery my Kindle flashlight was shinging orange color and it was suspended. I turn it off and now i can't charge it and i can't turn it on. The flashlight is dark, not shining. I try Kindle Unbrick Utility, Firekit Live USB but my KF is still dead. Can someone help my with my problem? What should I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#34
No my computer doesn't recognize the KF.
So the device motherboard is totally dead? Or today is no solution for that problem? Factory cable doesn't help?
czechu85 said:
No my computer doesn't recognize the KF.
So the device motherboard is totally dead? Or today is no solution for that problem? Factory cable doesn't help?
Click to expand...
Click to collapse
If your computer didn't even pick up or turn on the kindle and since this is a KF2 i would say that this is dead based of that link soupmagnet posted.
Sorry
I think that my device is Kindle Fire 2 (I got it from my friend without any box). In the back of the device is this numbers Model No D01400 FCC ID: ZEV-1229. Is this KF2?
czechu85 said:
I think that my device is Kindle Fire 2 (I got it from my friend without any box). In the back of the device is this numbers Model No D01400 FCC ID: ZEV-1229. Is this KF2?
Click to expand...
Click to collapse
There are two ways to tell, one of which is not an option at this point. But if it was originally purchased on or before Oct. 2012, it is a KF1. Otherwise, there's a good chance it's a KF2.
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#34
Click to expand...
Click to collapse
Could you tell me more about this shorting trick? I must do it when the Kindle Fire is not connected to the computer? How to use Firekit along with the shorting trick? I try to use Firekit but my computer doesn't recognize the device becouse it is powered off. In this week i will get the info when the Kindle Fire was purcheased so i will be 100% sure what type of device I have. Thank's for help!
czechu85 said:
Could you tell me more about this shorting trick? I must do it when the Kindle Fire is not connected to the computer? How to use Firekit along with the shorting trick? I try to use Firekit but my computer doesn't recognize the device becouse it is powered off. In this week i will get the info when the Kindle Fire was purcheased so i will be 100% sure what type of device I have. Thank's for help!
Click to expand...
Click to collapse
Since the bootloader isn't working, there is no access to fastboot to reinstall it. In order to do that now, the bootloader must be installed to the device using the OMAP4boot tool, 'usbboot' (Firekit uses this), to communicate with the device using low level usb commands (that is, assuming it's a KF1). In order for usbboot to work, the device must first be put into usbboot mode (4003). According to Pokey9000, sometimes when there is corruption of the bootloader, the device automatically gets dropped into usbboot and Firekit work without a hitch. However, most of the time this is not the case and the device must be forced into usbboot mode using the shorting trick.
I won't go into any more detail about how to make it all work without first knowing whether you have a KF1 or a KF2.
BTW, just because your device doesn't show anything on the display, doesn't mean it's not on
soupmagnet said:
Since the bootloader isn't working, there is no access to fastboot to reinstall it. In order to do that now, the bootloader must be installed to the device using the OMAP4boot tool, 'usbboot' (Firekit uses this), to communicate with the device using low level usb commands (that is, assuming it's a KF1). In order for usbboot to work, the device must first be put into usbboot mode (4003). According to Pokey9000, sometimes when there is corruption of the bootloader, the device automatically gets dropped into usbboot and Firekit work without a hitch. However, most of the time this is not the case and the device must be forced into usbboot mode using the shorting trick.
I won't go into any more detail about how to make it all work without first knowing whether you have a KF1 or a KF2.
BTW, just because your device doesn't show anything on the display, doesn't mean it's not on
Click to expand...
Click to collapse
HI Soupmagnet
Well i'm in the same situation with my KF2 - so if you have any input to get it up and running again - please share...
I got the OMAP4BOOT working - but any attempt gives me a "unexpected 2nd stage response"
Really need some input
http://forum.xda-developers.com/showthread.php?t=2228539
Thanks
I have done a lot of reading. But I still not sure if fixing my KF2 i possible.
Some threads says they got the 2nd bootloader and then not really the right one course of the signed Amazon Keys is still unknown.
Some threads says that KF7 HD is the same HW and that solution can be used, but that solution doesn't include OMAP drivers.
So is the conclusion still that if you get a OMAP device you are f•••ked.?
2ND GEN Kindle Fire Bricked - SOLUTION
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2228539
Click to expand...
Click to collapse
Now there's a solution, you can use this method http://forum.xda-developers.com/showthread.php?t=2415870
It envolves such surgery soldering the e-MMC to a SDCARD reader but then you might be able to flash a new bootloader and re-start all the procedures.
Thanks to kurohyou
Good Luck! :victory:
Related
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Lyrekz said:
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Click to expand...
Click to collapse
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
kinfauns said:
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
Click to expand...
Click to collapse
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Lyrekz said:
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Click to expand...
Click to collapse
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
kinfauns said:
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
First of all. thank you for the help. And now my Kindle is stuck on the Kindle Fire screen.
Mine is stuck here too..been 3 days.. ordered the factory cable.. hopefully that works.
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Readyreadyready
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
soupmagnet said:
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
larmores said:
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1096 using XDA Labs
Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.
Does KFU recognize it? If it does you are good to go.
Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.
http://forum.xda-developers.com/showthread.php?t=1644970
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!
Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.
Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon
Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.
nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?
Please help! I was trying to flash an ICS rom on my kindle fire 2. I rooted it a few days ago and flashed JB rom by following the instructions here..
"http://forum.xda-developers.com/showthread.php?t=2105077"
Everything was working fine untill i flashed Gede ICS rom. Now whenever i press the power button the device keeps repeating the logos
First the Kindle Fire one and then the Blue and White Kindle Fire logo.. The later one stays for only a second.
Before, i could press the power buttong by pushing it during that logo but that doesn't seem to work now...
If only i can enter recovery mod i have powerpoints45's ROM resting in a folder in the internal SD card..
EDIT: When i plug the device with the PC using a usb cable (the normal one) nothing happens.. it doesn't show up in the devices list and neither do i hear any kind of sound..
haiderxabbas said:
Please help! I was trying to flash an ICS rom on my kindle fire 2. I rooted it a few days ago and flashed JB rom by following the instructions here.. "http://forum.xda-developers.com/showthread.php?t=2105077" Everything was working fine untill i flashed Gede ICS rom. Now whenever i press the power button the device keeps repeating the logos first the Kindle Fire one and then the Blue and White Kindle Fire logo.. the later one stays for only a second. Before, i could press the power buttong by pushing it during that logo but that doesn't seem to work now... if only i can enter recovery mod i have powerpoints45's ROM resting in a folder in the internal SD card..
Click to expand...
Click to collapse
yeah you flashed a kindle fire (1) rom for a kindle fire 2, thats a guaranteed brick. do you have a fastboot cable?
chris_m128 said:
yeah you flashed a kindle fire (1) rom for a kindle fire 2, thats a guaranteed brick. do you have a fastboot cable?
Click to expand...
Click to collapse
You mean a factory cable! No but i'll get it tomorrow if that's what i need to fix it.. can it be fixed? or is it bricked for good? =(
yeah they can usually fix 95 percent of kindle fire bricks, im pretty sure you'll be able to fix your kindle with it. and yes factory/fastboot cable are on in the same.
Thanks i need those kind of words to keep my hope up.... what do i have to do after i get the cable? coz its not being recognized by windows..
No sound! No yellow mark! no nothing.. it's like i didn't attach it at all...
I don't pretend to be an expert on this, hopefully someone with a little more knowledge than me will chime in, but the factory cable when automatically start your kindle fire in fastboot mode, it will be able to be read by your pc, the only trouble you might run in is with drivers, but it's nothing that can't be fixed. Then i would go over to hashcode's rom and follow step by step his instructions (fastboot method) for installing bootloader and then cm10.1. But like i said, someone with more information than me will hopefully post on here
haiderxabbas said:
Thanks i need those kind of words to keep my hope up.... what do i have to do after i get the cable? coz its not being recognized by windows..
No sound! No yellow mark! no nothing.. it's like i didn't attach it at all...
Click to expand...
Click to collapse
alright I had that problem before sounds stupid but turn on the kindle before attaching the cable make sure the drivers are installed I have them if you need them and what system is running on your pc? and before all of that you need to find your self someone with backed up fastboot cables.
hillconnor13 said:
alright I had that problem before sounds stupid but turn on the kindle before attaching the cable make sure the drivers are installed I have them if you need them and what system is running on your pc? and before all of that you need to find your self someone with backed up fastboot cables.
Click to expand...
Click to collapse
I installed the drivers but i'm not sure whether they are the right ones coz they don't seem to work now.. i'm running windows 7 x64 and it used to detect the device before it got bricked but now it doesn't do anything..
I searched all over the market today but can't seem to find a factory cable is it okay if i try to do the home made Fastboot cable thing? or should i order one online instead..
Home made thread:
http://forum.xda-developers.com/showthread.php?t=1392693
Why don't you think the drivers are working and homemade fast boot cables are okay but if there not done right they just want work or cut out half way though my fast boot cable it great just make it your self or get a Scorpion cable
I don't hear the sound the window makes when you connect something to the PC.. other than that there is no device recognized in the device manager.. so i figured there might be something wrong with the drivers too now.. i'm trying to make one if i can't i'll be getting the scorpion one you mentioned.. thanks
buy them from here, he makes the best
http://forum.xda-developers.com/showthread.php?p=21115858
scroll down to where you find xda user SkOrPn and read the ordering information and how to contact him
Try fixing with Linux
haiderxabbas said:
I don't hear the sound the window makes when you connect something to the PC.. other than that there is no device recognized in the device manager.. so i figured there might be something wrong with the drivers too now.. i'm trying to make one if i can't i'll be getting the scorpion one you mentioned.. thanks
Click to expand...
Click to collapse
I had the same problem: I bricked it when I wiped the data (and the rom I was going to load). I tried Windows and Mac, to no avail. Then I used my Linux machine.
Get an Ubuntu Live CD, and check out this tutorial; it worked like a dream:
http://desire.giesecke.tk/tutorial-adb-on-xubuntu/?wpmp_switcher=desktop
I was able to adb sideload the Rom and Gapps very easily via the terminal and TWRP on the KF2 - with a regular / stock micro USB cable.
Be sure to use 1949 and 0x1949 as the Kindle vendor IDs in the tutorial.
yudanjah said:
I had the same problem: I bricked it when I wiped the data (and the rom I was going to load). I tried Windows and Mac, to no avail. Then I used my Linux machine.
Get an Ubuntu Live CD, and check out this tutorial; it worked like a dream:
http://desire.giesecke.tk/tutorial-adb-on-xubuntu/?wpmp_switcher=desktop
I was able to adb sideload the Rom and Gapps very easily via the terminal and TWRP on the KF2 - with a regular / stock micro USB cable.
Be sure to use 1949 and 0x1949 as the Kindle vendor IDs in the tutorial.
Click to expand...
Click to collapse
I 'v asked my cousine to bring the factory cable on his way back here from Cyprus. Thank you Yudanjah i'll try your method too and then tell you if it worked for me or not..
So i used the tutorial i found here:
http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire-6-3-1/
to try to root my kindle fire first gen. Well it froze at the logo after a fastboot command was sent. I have spent about 3 hours trying to fix it with no luck. ADB does not connect at all, windows says theres a problem with the hardware. I cant get any connections to it whatsoever. Even in linux.
I've tried these things:
1. ADB through windows
2. Kindle Fire Utility and all its options (never sees the kindle)
3. SoupKit and all its options (same issue, linux is unable to enumerate the device)
I URGENTLY need this kindle unbricked. My mom will kill me if she cant get to her birds to feed them (don't ask). She uses it every day, and i told her rooting would be nooo problem. Well now i'm screwed. Please help if there's anything that can be done to this.
Thanks Guys
Josh
Edit: Anyone with this issue, I rigged up a factory cable (http://forum.xda-developers.com/showthread.php?p=20380015) by crossing pins one and four with a breadtie and got really lucky, forced it back to normal mode from fastboot. It is the ONLY thing that will work in this case, i tried everything else!
hi
once the factory cable is connected, what do you do?
joshcrumley100 said:
So i used the tutorial i found here:
http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire-6-3-1/
to try to root my kindle fire first gen. Well it froze at the logo after a fastboot command was sent. I have spent about 3 hours trying to fix it with no luck. ADB does not connect at all, windows says theres a problem with the hardware. I cant get any connections to it whatsoever. Even in linux.
I've tried these things:
1. ADB through windows
2. Kindle Fire Utility and all its options (never sees the kindle)
3. SoupKit and all its options (same issue, linux is unable to enumerate the device)
I URGENTLY need this kindle unbricked. My mom will kill me if she cant get to her birds to feed them (don't ask). She uses it every day, and i told her rooting would be nooo problem. Well now i'm screwed. Please help if there's anything that can be done to this.
Thanks Guys
Josh
Edit: Anyone with this issue, I rigged up a factory cable (http://forum.xda-developers.com/showthread.php?p=20380015) by crossing pins one and four with a breadtie and got really lucky, forced it back to normal mode from fastboot. It is the ONLY thing that will work in this case, i tried everything else!
Click to expand...
Click to collapse
Flash a recovery in fastboot
Sent from my Amazon Kindle Fire
?
with the factory cable connected its not recognized
androvista said:
Flash a recovery in fastboot
Sent from my Amazon Kindle Fire
Click to expand...
Click to collapse
Once the device boots up into fat boot use a normal USB cable
Sent from my finger to your face
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
javipas said:
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
Click to expand...
Click to collapse
The fact that you don't know what device you have is a little disturbing. If your device said "otter" anything in fastboot, then you definitely do not have a Kindle Fire HD.
If that's the case, you flashed the wrong bootloader for your device and it is very unlikely that you will ever recover it.
The device IS a Kindle Fire, maybe not an HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
javipas said:
The device IS a Kindle Fire HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
Click to expand...
Click to collapse
Oh my...
Have a seat, my friend, because you're about to learn something...
In fastboot, if you were actually successful in sending the "fastboot devices" command (not possible on the HD), the output would be something similar to the following...
Code:
1234567890ABCDEF fastboot
...however, if you had a Kindle Fire HD7 and used the "fastboot getvar product" command, the output would be something like "TATE-XXXX-XXX". Respectively, the Kindle Fire HD8.9 would be "JEM-XXXX-XXX", the Kindle Fire 2 would be "OTTER-XXXX-XXX" and the original Kindle Fire would be "kindle".
Furthermore, only the original Kindle Fire and the Kindle Fire 2 (non-HD), have the model number D01400.
Now, whether you have an original Kindle Fire or a Kindle Fire 2 is still up for debate because you are clearly confused about what device you have in the first place. If you are lucky, and in fact have an original Kindle Fire, you will be able to restore it using Firekit. Unfortunately, considering the information available, I'm willing to bet that you have a Kindle Fire 2, and thus there is no way for you to restore your device.
Thanks for the clarification, that was perfect. I'm affraid I've got a Kindle Fire 2 then, so it seems there's nothing to do. Maybe in the future some method will appear to recover this second generation, who knows.
Greetings soupmagnet!
Easy Way to tell KF&KF2 from HDs: If it has a camera its a HD. Duh.
Sent from my Amazon Kindle Fire using xda app-developers app