Develop Bugs

[Q] Kindle Fire 8.9 Perma-Bricked?

Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.

chickeninferno said:
Hey Guys,
I successfully rooted my kindle fire 8.9" a while back and a few days ago decided to follow: http://forum.xda-developers.com/showthread.php?t=2277105 to install the twrp/custom rom.
In fireflash I moved the bootloader back to 8.1.4 and changed the boot and recovery partitions accordingly. I disabled the recovery auto update. I applied the changes and rebooted (I saw the red kindle fire letters and then it changed to the blue letters). It went into the TWRP screen at which point the guide told me to reboot. I found a "reboot to recovery" option and clicked it. Apparently, this was a very bad thing to do. The kindle boots to the Kindle Fire logo in red letters and stays there. it doesn't go blue and nothing moves. It stays that way until I turn it off.
It no longer will show up in Device Manager at all, but if I turn it on while plugged into the computer, the computer makes fast bump sounds like it sees the device for a second.The first time I plugged it into a different computer windows said it was trying to install a driver for "Jem-PVT-Prod-04" but then the driver installation failed and it doesn't show up in the device manager even with an exclamation mark.
Using different adb tools (Minimal adb and fastboot, kindle adb drivers, and android sdk) yields no response from the device even with a factory cable (which I purchased and arrived this morning). Fastboot just says < waiting for device > after the command "fastboot -i 0x1949 getvar product"
Adb kill-server followed by adb devices leads to a blank list of devices. (I also went into user/.android/ to change the adb_usb.ini file to 0x1949 (which it already was)
I tried KFHD SRT v2.1 http://forum.xda-developers.com/showthread.php?t=2011126 but it can't see the device either.
At this point, I don't know what can be done and am open to trying everything.
Click to expand...
Click to collapse
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.

soupmagnet said:
Just to confirm that you're doing it correctly...have you powered the device completely down, entered 'fastboot -i 0x1949 getvar product', and then turned the device on? And still no luck?
BTW, the factory cable will not work with the KFHD8.9 and can possibly damage it. Don't use it.
Click to expand...
Click to collapse
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
I've run into relatively the same problem with my HD8.9 several times while testing scripts but I've always been able to enable fastboot after rebooting using 'getvar product'. The difference in my case, is that I was always using Linux. You may want to set up a LiveUSB and install the SoupKit from the Dev section and try again to see if it makes a difference. SoupKit is not required, of course, but it is definitely recommended if you're not very familiar with Linux.

chickeninferno said:
Correct, I tried fastboot with the kindle 8.9 off, on,off then on, and on then off. None of these does anything except sit and say < waiting for device >.
Thanks for the heads up on the factory cable. It didn't seem to do anything any different anyway but is unplugged now.
Click to expand...
Click to collapse
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.

chickeninferno said:
Brandonrz,
It does not show up in the Device manager when off, when I send fastboot commands, or when on. It will however show up as Jem-PVT-Prod-04 for ~1 second if I have device manager open and I turn on the kindle (regardless of whether or not a fastboot command was sent).
@soupmagnet,
my flashdrive was dead so I just picked up a new one. Putting linux on it now.
Click to expand...
Click to collapse
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!

Glorious Success!
So I ended up doing a combination of the two solutions and since I know how frustrating this was here's how I did it just in case someone stumbles upon this.
How it magically worked:
1.) Inside of Linux Mint, I installed Soupkit
2.) In terminal i typed "fastboot -i 0x1949 getvar product"
-----The kindle reacted for the first time in a long time and went into fasboot mode. Since I had no idea where to put the boot.img or recovery.img in linux to send them but the fastboot or adb commands, I decided to risk it and move to windows.
3.) I unplugged the kindle
4.) Booted into Win 7 x64
5.) The fastboot wasn't working in windows but I checked device manager and the exclamation mark was lingering. I manually picked the driver of amazon.com/kindle and it installed the adb composite device. Fastboot now works in windows.
5.) ran SR Tool.bat in the KFHD_SRT_2.1 folder and chose option 1 (Enable Fastboot)
-----Success
6.)in SR Tool i chose option 4 (erase cache and userdata)
----Took ~4 minutes but success
7.) in cmd I navigated to my sdk platform tools folder by typing "cd C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools"
8.) I downloaded the boot.img and recovery.img linked here (http://forum.xda-developers.com/showthread.php?t=2011126) and placed them into C:\Users\<username>\Desktop\SDK\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\
9.) in the cmd from step 7 I sent the following commands "fastboot -i 0x1949 flash boot boot.img" and "fastboot -i 0x1949 flash recovery recovery.img"
----Great Success
10.) In SR Tool I chose option 6 (reboot normally)
-----It looped for ~2 minutes but eventually booted like normal but the SR_Tool asked me to make sure that adb was enabled before clicking enter. I enabled it on the device but SR Tool still didn't seem to see that I had done it. Since it rebooted normally, I didn't really care.
11.) The kindle upgraded itself after I set it down to type this response to 8.4.3
I probably could have easily done this is linux, but I didn't know where to put the boot.img and recovery.img. Also, I'm guessing that the system.img is put back on the device when I used the KFHD SRT but I'm not sure.
Now I'm going for round two to get CM 10.1 put on this thing!
Thanks for all of the help. I really thought that I had actually managed to brick the nearly unbrickable kindle fire 8.9"

Congrats on your success and thanks for sharing the experience!
I think one problem with Windows is that, "fastboot -i 0x1949 getvar product" does not work very well on putting the kindle to fastboot if the device driver is not properly installed, kindle will simply bypass the fastboot step and continue(and hang), the whole situation is a dead loop on Windows if the fastboot driver is having problem and the kindle can't boot into the ROM, and to make things even worse, there is no factory cable for HD8.9
So the SoupKit is a real life saver here.

I had the same sort of driver problem after I installed the second bootloader. For me the simple fix was to go into device manager (In Windows 7), uninstall whatever driver was there with the yellow triangle and then reinstall the official kindle adb driver. Congrats on getting it fixed though. It's a great feeling, I know.

Worked form me too!
Brandonrz said:
For those who may be in same situation here is what I did.
Go to device manager. For that second, try to Right click on Jem-PVT-08 and choose update driver software, then browse my computer for driver software, then let me pick from a list of device drivers on my computer. I moved down list and picked Kindle and it installed as adb composite interface or something like that. Once installed the device manager showed "Kindle" and my fastboot was working. I've had the issue before. I hope this helped!
Click to expand...
Click to collapse
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.

DBMmn said:
Thanks much for your pointer. In my case the Kindle showed up as an "Other devices" and I was able to use "browse my computer ..."->"let me pick from a list"->Kindle fire->ADB(ver 1.3).
You are awesome.
Click to expand...
Click to collapse
I'm so glad I could help, it was so frustrating for me.

Brandonrz said:
Are you running windows??? If you are.... when your kindle is powered down and you type in the fast boot commands, go into device ,manager and see if your kindle shows a yellow triangle next to it. Reply asap.
Sent from my Amazon Kindle Fire HD using Tapatalk HD
Click to expand...
Click to collapse
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.

Tyler9097 said:
Im stuck RIGHT here. manually entered fastboot, with the device showing as JEM-PVT-Prod 4. Unable to re-install recovery because <waiting on device>. Please help.
Click to expand...
Click to collapse
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk

Brandonrz said:
Try kingo root or towel root. I believe they might be easier.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!

Tyler9097 said:
Turned out it was a driver compatibility issue with Windows 10. It doesn't recognize the Kindle HD 8.9 properly. Moved it over to a Windows 7 machine and it was working, up until i attempted to flash a new recovery and boot .img . Now it's stuck on the red Kindle logo and computer won't pick up the USB. Halp!
Click to expand...
Click to collapse
Power off the Kindle, type fastboot -i 0x1949 getvar product , plug in the Kindle when you get <waiting for device>, and flash the 2nd bootloader, recovery, and freedom-boot images as directed in Hashcode's thread. Skip to step 5 after downloading the files, as we're already in fastboot mode at this point.
Also, Windows 10 enforces driver signatures, so you'll need to disable that before proceeding with the Kindle driver installation.
Sent from my Amazon Jem using XDA Labs

[Solved] Can't boot into fastboot (8.4.6)

I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten

Try putting it into fastboot again and use these drivers for the device that comes up and see if it will install them:
http://forum.xda-developers.com/showthread.php?p=44446906
Ha, for a minute I thought I saw my name at the end of this post... For the sake of privacy I don't really intend on giving my name out openly to explain why, but if you look at my skype profile it would make sense.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!

kasek said:
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
Click to expand...
Click to collapse
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Yeah, you're right about Windows 8, it's really a pain in the a**.
I'm gonna switch to Ubuntu once they'll publish my beloved shooters (CoD, Battlefield, ...) on Linux. Fortunately, I'm using Linux since my college time ('94) so I guess the only one having problems will be my wife
stunts513 said:
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

confirm rooted in ver 8.4.6
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~

Zukii said:
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Click to expand...
Click to collapse
Shure.
This one worked perfectly for me:
http://forum.xda-developers.com/showthread.php?t=2337634

hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?

kasek said:
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Click to expand...
Click to collapse
I'm like you (8.4.6) somehow I getinto fastboot quite succesfully, I dont know if this is your problem, you seems to try to "fastboot" before you poweroff your device.

don_ernesto said:
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
Click to expand...
Click to collapse
Maybe this link could be helpful:
http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
This was exactly what I did.
Good luck!

Kindle Fire HD 8.9 red triange after root.

Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?

Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.

OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.

In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.

Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.

Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.

Please help to unbrick---stuck in red Screen and can't get into fastboot

Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)

z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?

I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.

Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?

Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.

Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？

stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？

It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk

Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app

[Q] Non-rooted Kindle HD 8.9 not found in device manager

Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.

ray8888888 said:
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
Click to expand...
Click to collapse
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.

stunts513 said:
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
Click to expand...
Click to collapse
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?

ray8888888 said:
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
Click to expand...
Click to collapse
it should be fine to use now, that's just stock rooted, you might wanna consider disabling ota's or flashing another rom onto it but its fine how it is.