In trying to install a custom bootloader on my Kindle Fire HD 7", I bricked it. When trying to start it normally, it shows "kindle fire" for a few seconds, but then the screen goes black and it becomes totally unresponsive. When I tried booting it with a factory cable, it shows "kindle fire" for a few seconds, and then switches to the "fastboot" logo, but again it is unresponsive. In both cases, my kindle is never found by adb or fastboot or any other utility when connected to my computer. I'm fairly certain this not a driver problem, because my kindle was recognized before, which is how I rooted my kindle. Is there anything else I can try to unbrick my kindle? The main problem is that it is never recognized by my computer. Now what?
What custom bootloader did you try to install?
Sent from my KFHD 8.9 using Tapatalk 2
EEK!!!!
Messing with the bootloader on the kfhd is suicide. You may want to think about calling Amazon and see if they will replace it.
Go into fastboot mode and type this in command prompt wherever you have fastboot.exe and adb.exe (To do that just go to that folder, shift+right click anywhere and select open command window here).
Post the output
Code:
fastboot -i 0x1949 getvar product
and idk if you know this but...if you get your kindle into fastboot mode... all you see is the logo nothing more, and everything else is done through command prompt in windows, So assuming you already know that, what made you think it is unresponsive?
Yeah he is right. Call them, tell them what happened but not how it happened.
Sent from my KFTT using xda app-developers app
AmrBanawan said:
Go into fastboot mode and type this in command prompt wherever you have fastboot.exe and adb.exe (To do that just go to that folder, shift+right click anywhere and select open command window here).
Post the output
Code:
fastboot -i 0x1949 getvar product
and idk if you know this but...if you get your kindle into fastboot mode... all you see is the logo nothing more, and everything else is done through command prompt in windows, So assuming you already know that, what made you think it is unresponsive?
Click to expand...
Click to collapse
The issue is that my kindle is not "discovered", "recognized", or whatever you want to call it by my computer. It has before, because I was able to root my kindle earlier, so I'm fairly certain that it isn't a driver problem, which is the usual response I've found. None of the fastboot commands work because my kindle can't be found.
mharlan95 said:
The issue is that my kindle is not "discovered", "recognized", or whatever you want to call it by my computer. It has before, because I was able to root my kindle earlier, so I'm fairly certain that it isn't a driver problem, which is the usual response I've found. None of the fastboot commands work because my kindle can't be found.
Click to expand...
Click to collapse
Hmmm.. Thats weird what did you exactly do? I would try to reinstall the drivers. When you go into device manager do you see it there when it is plugged in? I had the same problem but my micro usb ports where fried in the Kindle bc I had a faulty fastboot cable.. Let us know if you see it in device manager..
If you tried to install Hashcode's 2nd bootloader, which is the only one that would work, it sounds like you missed a step somewhere. Is that the bootloader you tried to install?
Alright, so it was a driver problem. I ended up removing all drivers and sdk stuff, and then reinstalled and reloaded everything, which enabled fastboot to discover my device when using a factory cable. Problem solved. I found you just have to be careful when setting up sdk, and do every single step as listed on https://developer.amazon.com/sdk/fire/setup.html.
frozen
mharlan95 said:
In trying to install a custom bootloader on my Kindle Fire HD 7", I bricked it. When trying to start it normally, it shows "kindle fire" for a few seconds, but then the screen goes black and it becomes totally unresponsive. When I tried booting it with a factory cable, it shows "kindle fire" for a few seconds, and then switches to the "fastboot" logo, but again it is unresponsive. In both cases, my kindle is never found by adb or fastboot or any other utility when connected to my computer. I'm fairly certain this not a driver problem, because my kindle was recognized before, which is how I rooted my kindle. Is there anything else I can try to unbrick my kindle? The main problem is that it is never recognized by my computer. Now what?
Click to expand...
Click to collapse
I have the exact same problem but found an unusual solution. after 2 months of pain and toil i did something that saved me. When your kindle is frosen on the logo with no animation, you have to restart your computer with your kindle plugged in. I restarted and boom my kindle restarted a few times and booted up. It did not work when i plugged it into usb 3.0 ports, but the usb 2.0 was fine. I just restarted with the kindle plugged in, and it unbricked.
Hope this helps
oliverisboss said:
I have the exact same problem but found an unusual solution. after 2 months of pain and toil i did something that saved me. When your kindle is frosen on the logo with no animation, you have to restart your computer with your kindle plugged in. I restarted and boom my kindle restarted a few times and booted up. It did not work when i plugged it into usb 3.0 ports, but the usb 2.0 was fine. I just restarted with the kindle plugged in, and it unbricked.
Hope this helps
Click to expand...
Click to collapse
Did you hapen to have a facory cable plugged in at the time? and was it the 2013 model?
davethebrave14 said:
Did you hapen to have a facory cable plugged in at the time? and was it the 2013 model?
Click to expand...
Click to collapse
Yes it was a factory cable and no i think i got it in late 2012
So i was going to flash CM11 onto my Kindle fire HD using the freedomboot/twrp method, but i forgot to revert the os back. Now whenever i boot i get a red screen. Now i would be able to fix this (I have a fastboot cable) but ADB/Fastboot does NOT appear with the device. Everything always stays on < waiting for device >. My device manager says Tate-PVT-08, and the kindle goes into fastboot mode fine (Orange FASTBOOT with small kindle fire below it), but NOTHING recognizes it. I NEEEDDD HEELLLLPPPPPP :crying:
P.S I am using windows 8.1 if that helps
Edit: Solved!!! The key was entering the update driver window and click browse my computer, instead of the file option.
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Gospelalex said:
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Click to expand...
Click to collapse
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
vasolini said:
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
Click to expand...
Click to collapse
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Gospelalex said:
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Click to expand...
Click to collapse
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
vasolini said:
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
Click to expand...
Click to collapse
Can`t install them - install failed.
Gospelalex said:
Can`t install them - install failed.
Click to expand...
Click to collapse
Got another cable. Was able to get to fastboot. But couldn`t get past it. Device was shown as tate unrecognized. Pushed to install driver and made it recognized by pc. Tried kindle fire utility v099 to run recovery. The kindle gone into reboot. So now it reboots into main loge, then changes into fastboot loge and then going into continuous reboot again. Windows in the same time stop recognize it. Shows it in usb unidentified for a second because it switches on and off again.
Update:
Managed to return it into fastboot. But in cmd when i run adb.exe devices there is nothing.
I know how to fix this problem. I ran into this 10 times before Android Studio suddenly went through my head.
In order to install the Kindle Fire ADB Drivers, you need to download and install the Android SDK Manager from Google Inc. Then when you install those drivers I mentioned earlier, you won't get errors. It's so weird.
You can try using the Ultimate Unbrick Tool, but I forgot the download link for it. There should be a thread about it here on XDA.
Lots of advanced technical stuff. I suck at explaining without making it a very long explanation because then people stop reading after 10 seconds.
So i made the mistake of factory resetting my kindle from within cm 12 and now teamwin keeps flashing. I have tried to solve using the sr tool but it always says waiting for device.I also tried to use the unbricking utility but it says idme not found and does nothing for the stuck at logo option. i have the kindle adb drivers installed and whenever the kindle goes into fastboot mode it never shows a menu. Also my computer is not recognizing the kindle, however when i plug it in i hea the noise as if it is being recognized. Also when i open the adb console and use adb devices it shows up as in recovery. Any help will be much appreciated.
SO I foolishly issued the fastboot command via ADB when it was working. I started to issue commands in order to install the 2nd bootloader and recovery. Since that point, the Kindle isn't recognized by Windows 10 Pro anymore and I've tried just about every utility, method and button combination there is.
I read that ADB only needs 4 seconds -/+ to initiate commands once the Kindle powers up. I've tried to issue the ADB to get it to boot back in normal mode and it always sits on <waiting for device>. I attached a screen shot showing what comes up in device manager. I've uninstalled the drivers, reinstalled but to no avail.
At this point, I'm willing to try anything. Stand on my head and shake the Kindle 5 times while rotating it clockwise....anything would help.
*UPDATE* I just more or less wiped my laptop which I have all the ADB drivers on as well as Android Studio. I'm going to run some tests to see if I can get that 4 second gap to initiate an ADB command to get the fastboot to go into normal boot more 4000.
*UPDATE 2* I managed to get generic ADB drivers as well as FASTBOOT drivers installed on my laptop. I can communicate with the Kindle a little. At this point, I've tried to issue ADB commands to restart with bootloader and other commands, but it only reboots back into FASTBOOT. The only thing I've been able to see is with KFFA, I can reboot to normal mode but it just comes back to FASTBOOT. I can also issue the test FASTBOOT and it gives me an ID and recognizes the Kindle. I've tried other options within KFFA but nothing seems to stick. I'm now officially stuck. Any help would be fantastic.
*UPDATE 3*
Thanks to this thread http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
I was able, or am in the process of loading a 2nd bootloader + TWRP and then on to CM13.
Any ideas?
Windows 10 Pro
Kindle Fire HD
Rooted with Kingroot
No Fastboot cable
Lots of frustration
Eh back to square one. It reverted and there is no TWRP recovery. It's stuck in FASTBOOT and will take most fastboot commands but I can't get ADB and the drivers loaded to issue any sideload commands.
This is weird.
Hello I have bricked my kindle fire and having similar driver issues I am able to get into fastboot mode with a diy factory cable boot any fastboot command comes back waiting for device . Can I ask where you got drivers please?
I used these:
http://forum.xda-developers.com/showthread.php?t=1890413
I also ran like every single recovery tool out there to help me fix this. After I did fix it, it updated to latest version and there is no root yet for it. I sold it.
If you need help, I think I might still have all the tools I used to get this back to stock and working.
Regards,
rast4man