Develop Bugs

Frequently Asked Questions - 2nd Generation Kindle Fires

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]2nd generation Kindle Fires[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How can I tell if I have a 2nd generation Kindle Fire?[/SIZE]For HD models the answer should be pretty obvious, but the KF2 has nearly the exact same hardware configuration as the original. Short of opening the device, the only way to tell for sure is by checking the software version. Devices running a software version of 6.3.2 or earlier is a 1st generation Kindle Fire. All other versions belong to 2nd generation Kindle Fires.​[SIZE=+1]Q2: What is the most important thing to know about the 2nd generation Kindle Fires?[/SIZE]The 2nd generation Kindle Fires are running on OMAP4 HS processors with “M-Shield” turned on. What that means is ANY alteration to certain partition images containing digitally signed headers (with one exception) will result in the OMAP ROM halting the boot process and the resulting “brick” will be irreparable by anyone but Amazon. For more information, or just for an interesting read, go here: New Kindle Fires are locked​[SIZE=+1]Q3: What partition images contain these signed headers?[/SIZE]The xloader, bootloader, recovery, and boot (kernel) partition images all have signed headers. Any attempt at installing custom versions of these partition images by means of traditional methods to modify the device will result in the aforementioned irreparable “brick”.​[SIZE=+1]Q4: How do I create a partition image with a signed header that can be used on the 2nd generation Kindle Fires?[/SIZE]You can't. Ignoring the fact that the signed header must have the exact same 64Kb signature that Amazon uses in the factory, the software used to produce this signature is not available to the general public, but only to “high volume wireless OEMs and ODMs”.​[SIZE=+1]Q5: You mentioned “one exception” to installing custom partition images? Could you elaborate on this?[/SIZE]While the “M-Shield” technology for OMAP HS processors is pretty robust, the same ccouldn't necessarily be said for Amazon's software. The stock Kindle Fire bootloaders from software updates previous to 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) have an exploitable hole in the boot process which allows the installation of a 2nd bootloader (on the system partition) and unsigned custom recovery & boot (kernel) images, without much fear of doing irreparable harm, but the actual bootloader must still remain stock. It should be noted that stock Kindle Fire bootloaders since the 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) updates have this hole patched and any attempt to install the 2nd bootloader along with unsigned recovery & boot images WILL BRICK THE DEVICE.​[SIZE=+1]Q6: How will I know what version of the stock bootloader is installed on my device?[/SIZE]There is no way to confirm with all certainty what bootloader version is installed on the device, but a very good indicator to look for is the software version itself. Software versions prior to 8.1.4 (KFHD8.9), 7.2.3 (KFHD7), and 10.2.4 (KF2) have bootloaders that can be exploited. Everything beyond that must be replaced with one from a previous software update version. ​[SIZE=+1]Q7: My device is running a software version with a stock bootloader that cannot be exploited (or I am not sure). How can I install the 2nd bootloader for running custom ROMs and recovery?[/SIZE]Use fastboot to flash a signed stock bootloader from a previous software version. It should be noted that this is very risky to do. Sudden losses or surges of power, accidental unplugging of the USB cable, or flashing a bad download can potentially brick the device, for good. Always check md5s on all bootloader downloads, make sure you have a good charge, and keep all small children at a respectable distance. ​[SIZE=+1]Q8: Where can I find the 2nd bootloader and information on how to install it?[/SIZE]
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9”
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
[BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2
[SIZE=+1]Q9: What can I do to restore my device if the 2nd bootloader and custom recovery is not installed?[/SIZE]Use fastboot to restore saved partition images from or for your particular device.​[SIZE=+1]Q10: How do I save my partition images to restore later if needed?[/SIZE]For HD models, there is a script created by kinfauns that will do the work for you, but it will not work properly for the KF2 if the partition layout isn't the same. Regardless of what device you own, this can easily be done on any rooted device using 'dd' to save those partitions to the sdcard, then transfer them to your computer:
Code:
adb shell su -c “dd if=/dev/block/mmcblk0pX of=/sdcard/<filename>.img”
...where 'X' will be a number 1-13 (depending on partition layout) and '<filename>' will be the name of that partition. You can get a list of partition names and corresponding numbers with the following command:
Code:
adb shell su -c “ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name
Use 'adb pull...' to transfer the images to your computer for safe keeping, and avoid trying to save the userdata or sdcard partitions.​[SIZE=+1]Q11: How do I restore a saved partition in fastboot?[/SIZE]
Code:
fastboot -i 0x1949 flash <partition_name> <partition_name>.img
...where '<partition_name>.img' should be the full path to the appropriately named partition image located on your computer. ​[SIZE=+1]Q12: Where can I get saved partition images for my device if I haven't previously saved them myself?[/SIZE]
[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software
[SIZE=+1]Q13: How do I restore my device if the 2nd bootloader and custom recovery is installed?[/SIZE]Generally speaking, most any problem can be resolved by reinstalling a ROM while being sure to wipe data (factory reset) first.​[SIZE=+1]Q14: How will I know if I have a bricked 2nd generation Kindle Fire that cannot be restored?[/SIZE]The device will not show any outward signs of life; no display, no sound, and no LED. The device may still get warm when plugged in or turned on and Windows users may see an OMAP4 device in the device manager. Again, short of sending it back to Amazon, there isn't anything that can be done. ​[SIZE=+1]Q15: What about the 'usbboot' method used on 1st generation Kindle Fires for replacing a malfunctioning bootloader? Could something similar be implemented for 2nd generation Kindle Fires?[/SIZE]Not likely. The 'usbboot' method used to install the xloader, bootloader, and custom recovery on the 1st generation Kindle Fires is different for 2nd generation devices. The most significant difference being the USB loader used to initially flash these images must also have a digitally signed header. As explained by Pokey9000, short of finding an exploit in the OMAP ROM code (unlikely) or somehow acquiring the appropriately signed USB boot tools used by Amazon to flash the bootloader in the factory (even less likely) it will probably never work.​[SIZE=+1]Q16: How will I know if my 2nd generation Kindle Fire can be restored?[/SIZE]Generally speaking, any device that will power on and show at least something on the display, will give you access to fastboot, thus the ability to restore saved partition images, and in effect the device. Many times this will require the use of a factory cable, so in some cases, owners of the KFHD8.9 will be out of luck.​[SIZE=+1]Q17: How can I access fastboot mode on 2nd generation Kindle Fires?[/SIZE]There are 3 methods currently used for accessing fastboot mode on the 2nd generation Kindle Fires. Depending on the model, one or more of these methods may not work.
For all devices, entering “reboot bootloader” in the shell as the root user should reboot the device into fastboot mode.
On HD models, entering a fastboot command that waits for a handshake from the device (i.e. <waiting for device>”) such as “fastboot -i 0x1949 getvar product” and rebooting the device will usually enable fastboot mode when the device reboots.
On the KFHD7 and KF2, a factory cable can be used to access fastboot mode by plugging it into the device after it has been powered down.
[SIZE=+1]Q18: My device, when booted, displays a red or orange screen and does not respond to fastboot commands. What happened?[/SIZE]You probably tried to install the 2nd bootloader and custom recovery without making sure the bootloader you're running is the the unpatched version from a previous update. The red screen, or “Wall of Fire” as Amazon calls it, is displayed when the digital signatures don't match, as would be the case when installing custom recovery on a device with a patched bootloader. A factory cable is needed to get into fastboot so those partitions can be restored to the original signed versions. Since the factory cable doesn't work on the KFHD8.9, owners of these devices may be out of luck. ​[SIZE=+1]Q19: What is a factory cable? What is it used for? How do I use it?[/SIZE]A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the some devices, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a your device once it has been powered down.​[SIZE=+1]Q20: Where can I find information on making or purchasing a factory cable?[/SIZE]
[Info]Making/Using a Factory Cable
SkOrPn
[SIZE=+1]Q21: How will I know when my device is in fastboot mode?[/SIZE]It will say “Fastboot” on the display​[SIZE=+1]Q22: I have access to fastboot mode, but fastboot commands won't work (prompt sits at <waiting for device>). What's wrong?[/SIZE]Your USB/device drivers aren't configured properly.​[SIZE=+1]Q23: Where can I find information on how to properly install the drivers?[/SIZE]
[GUIDE] Kindle Fire For Beginners – Post #2
Let's take some of the mystery out of getting ADB working in Windows
Note: While those tutorials are made for the original Kindle Fires in mind, the information is still the same in regards to installing and configuring USB device drivers.​[SIZE=+1]Q24: I've read all the tutorials and tried various different tools, but I'm still unable to get my drivers working properly. What else can I try?[/SIZE]
SoupKit
[SIZE=+1]Q25: Now that I know all of the important stuff, how do I root my 2nd generation Kindle Fire?[/SIZE]While there are several tools and scripts used to root the 2nd generation Kindle Fires, they all rely on the same basic method, the Bin4ry method , which takes advantage of a remount timing issue during an ADB restore. It is very effective and works for nearly all devices natively running Ice Cream Sandwich.
Note: Despite some of the rumors about using your Amazon account password as the encryption password, this is a misconception. No password is needed because none was set.​[SIZE=+1]Q26: Where can I find information about how to install Google Play on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version
[SIZE=+1]Q27: Where can I find information about how to install Google Apps on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Apps with Speech Recognition Noob (Simple) Version
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.​

Q18: My device, when booted, displays a red or orange screen and does not respond to fastboot commands.
I'm currently in this situation with a KF2HD8.9. Is there any hope for my kindle? If there currently isn't will there be a possibility to have it working again in the future?

Blissful_Tea said:
Q18: My device, when booted, displays a red or orange screen and does not respond to fastboot commands.
I'm currently in this situation with a KF2HD8.9. Is there any hope for my kindle? If there currently isn't will there be a possibility to have it working again in the future?
Click to expand...
Click to collapse
I've never heard of orange screen
Sent from my Amazon Kindle Fire HD using Tapatalk HD

Some users have described having an orange screen in their situation. Whether they were right, wrong, or simply mistaken (color blind), I added it nonetheless to prevent confusion. But, thank you for your feedback.

soupmagnet said:
Some users have described having an orange screen in their situation. Whether they were right, wrong, or simply mistaken (color blind), I added it nonetheless to prevent confusion. But, thank you for your feedback.
Click to expand...
Click to collapse
Hahaha, cool. Thanks for replying!
Sent from my Amazon Kindle Fire HD using Tapatalk HD

does any one have stock rom of 8.9 LTE version?

The "Wall of Fire" issue I have resolved on my KFHD8.9 by turning off the kindle doing the
Code:
fastboot -i 0x1949 getvar product
then when it says "waiting for device" plug the kindle in and turn it on. Doing so forces fastboot. Then I load up Kindle Fire First Aide (there is a long process of getting KFFA working look for a thread on it). Choose option 4 for "KFHD8.9". Then choose option 3 to restore 8.2.4 (no other options on this menu seem to work for my kindle). This process always seems to fix the red screen of death for me.
gamer941 said:
does any one have stock rom of 8.9 LTE version?
Click to expand...
Click to collapse
Have you tried looking into KFFA?

soupmagnet said:
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]2nd generation Kindle Fires[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How can I tell if I have a 2nd generation Kindle Fire?[/SIZE]For HD models the answer should be pretty obvious, but the KF2 has nearly the exact same hardware configuration as the original. Short of opening the device, the only way to tell for sure is by checking the software version. Devices running a software version of 6.3.2 or earlier is a 1st generation Kindle Fire. All other versions belong to 2nd generation Kindle Fires.​[SIZE=+1]Q2: What is the most important thing to know about the 2nd generation Kindle Fires?[/SIZE]The 2nd generation Kindle Fires are running on OMAP4 HS processors with “M-Shield” turned on. What that means is ANY alteration to certain partition images containing digitally signed headers (with one exception) will result in the OMAP ROM halting the boot process and the resulting “brick” will be irreparable by anyone but Amazon. For more information, or just for an interesting read, go here: New Kindle Fires are locked​[SIZE=+1]Q3: What partition images contain these signed headers?[/SIZE]The xloader, bootloader, recovery, and boot (kernel) partition images all have signed headers. Any attempt at installing custom versions of these partition images by means of traditional methods to modify the device will result in the aforementioned irreparable “brick”.​[SIZE=+1]Q4: How do I create a partition image with a signed header that can be used on the 2nd generation Kindle Fires?[/SIZE]You can't. Ignoring the fact that the signed header must have the exact same 64Kb signature that Amazon uses in the factory, the software used to produce this signature is not available to the general public, but only to “high volume wireless OEMs and ODMs”.​[SIZE=+1]Q5: You mentioned “one exception” to installing custom partition images? Could you elaborate on this?[/SIZE]While the “M-Shield” technology for OMAP HS processors is pretty robust, the same ccouldn't necessarily be said for Amazon's software. The stock Kindle Fire bootloaders from software updates previous to 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) have an exploitable hole in the boot process which allows the installation of a 2nd bootloader (on the system partition) and unsigned custom recovery & boot (kernel) images, without much fear of doing irreparable harm, but the actual bootloader must still remain stock. It should be noted that stock Kindle Fire bootloaders since the 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) updates have this hole patched and any attempt to install the 2nd bootloader along with unsigned recovery & boot images WILL BRICK THE DEVICE.​[SIZE=+1]Q6: How will I know what version of the stock bootloader is installed on my device?[/SIZE]There is no way to confirm with all certainty what bootloader version is installed on the device, but a very good indicator to look for is the software version itself. Software versions prior to 8.1.4 (KFHD8.9), 7.2.3 (KFHD7), and 10.2.4 (KF2) have bootloaders that can be exploited. Everything beyond that must be replaced with one from a previous software update version. ​[SIZE=+1]Q7: My device is running a software version with a stock bootloader that cannot be exploited (or I am not sure). How can I install the 2nd bootloader for running custom ROMs and recovery?[/SIZE]Use fastboot to flash a signed stock bootloader from a previous software version. It should be noted that this is very risky to do. Sudden losses or surges of power, accidental unplugging of the USB cable, or flashing a bad download can potentially brick the device, for good. Always check md5s on all bootloader downloads, make sure you have a good charge, and keep all small children at a respectable distance. ​[SIZE=+1]Q8: Where can I find the 2nd bootloader and information on how to install it?[/SIZE]
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9”
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
[BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2
[SIZE=+1]Q9: What can I do to restore my device if the 2nd bootloader and custom recovery is not installed?[/SIZE]Use fastboot to restore saved partition images from or for your particular device.​[SIZE=+1]Q10: How do I save my partition images to restore later if needed?[/SIZE]For HD models, there is a script created by kinfauns that will do the work for you, but it will not work properly for the KF2 if the partition layout isn't the same. Regardless of what device you own, this can easily be done on any rooted device using 'dd' to save those partitions to the sdcard, then transfer them to your computer:
Code:
adb shell su -c “dd if=/dev/block/mmcblk0pX of=/sdcard/<filename>.img”
...where 'X' will be a number 1-13 (depending on partition layout) and '<filename>' will be the name of that partition. You can get a list of partition names and corresponding numbers with the following command:
Code:
adb shell su -c “ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name
Use 'adb pull...' to transfer the images to your computer for safe keeping, and avoid trying to save the userdata or sdcard partitions.​[SIZE=+1]Q11: How do I restore a saved partition in fastboot?[/SIZE]
Code:
fastboot -i 0x1949 flash <partition_name> <partition_name>.img
...where '<partition_name>.img' should be the full path to the appropriately named partition image located on your computer. ​[SIZE=+1]Q12: Where can I get saved partition images for my device if I haven't previously saved them myself?[/SIZE]
[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software
[SIZE=+1]Q13: How do I restore my device if the 2nd bootloader and custom recovery is installed?[/SIZE]Generally speaking, most any problem can be resolved by reinstalling a ROM while being sure to wipe data (factory reset) first.​[SIZE=+1]Q14: How will I know if I have a bricked 2nd generation Kindle Fire that cannot be restored?[/SIZE]The device will not show any outward signs of life; no display, no sound, and no LED. The device may still get warm when plugged in or turned on and Windows users may see an OMAP4 device in the device manager. Again, short of sending it back to Amazon, there isn't anything that can be done. ​[SIZE=+1]Q15: What about the 'usbboot' method used on 1st generation Kindle Fires for replacing a malfunctioning bootloader? Could something similar be implemented for 2nd generation Kindle Fires?[/SIZE]Not likely. The 'usbboot' method used to install the xloader, bootloader, and custom recovery on the 1st generation Kindle Fires is different for 2nd generation devices. The most significant difference being the USB loader used to initially flash these images must also have a digitally signed header. As explained by Pokey9000, short of finding an exploit in the OMAP ROM code (unlikely) or somehow acquiring the appropriately signed USB boot tools used by Amazon to flash the bootloader in the factory (even less likely) it will probably never work.​[SIZE=+1]Q16: How will I know if my 2nd generation Kindle Fire can be restored?[/SIZE]Generally speaking, any device that will power on and show at least something on the display, will give you access to fastboot, thus the ability to restore saved partition images, and in effect the device. Many times this will require the use of a factory cable, so in some cases, owners of the KFHD8.9 will be out of luck.​[SIZE=+1]Q17: How can I access fastboot mode on 2nd generation Kindle Fires?[/SIZE]There are 3 methods currently used for accessing fastboot mode on the 2nd generation Kindle Fires. Depending on the model, one or more of these methods may not work.
For all devices, entering “reboot bootloader” in the shell as the root user should reboot the device into fastboot mode.
On HD models, entering a fastboot command that waits for a handshake from the device (i.e. <waiting for device>”) such as “fastboot -i 0x1949 getvar product” and rebooting the device will usually enable fastboot mode when the device reboots.
On the KFHD7 and KF2, a factory cable can be used to access fastboot mode by plugging it into the device after it has been powered down.
[SIZE=+1]Q18: My device, when booted, displays a red or orange screen and does not respond to fastboot commands. What happened?[/SIZE]You probably tried to install the 2nd bootloader and custom recovery without making sure the bootloader you're running is the the unpatched version from a previous update. The red screen, or “Wall of Fire” as Amazon calls it, is displayed when the digital signatures don't match, as would be the case when installing custom recovery on a device with a patched bootloader. A factory cable is needed to get into fastboot so those partitions can be restored to the original signed versions. Since the factory cable doesn't work on the KFHD8.9, owners of these devices may be out of luck. ​[SIZE=+1]Q19: What is a factory cable? What is it used for? How do I use it?[/SIZE]A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the some devices, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a your device once it has been powered down.​[SIZE=+1]Q20: Where can I find information on making or purchasing a factory cable?[/SIZE]
[Info]Making/Using a Factory Cable
SkOrPn
[SIZE=+1]Q21: How will I know when my device is in fastboot mode?[/SIZE]It will say “Fastboot” on the display​[SIZE=+1]Q22: I have access to fastboot mode, but fastboot commands won't work (prompt sits at <waiting for device>). What's wrong?[/SIZE]Your USB/device drivers aren't configured properly.​[SIZE=+1]Q23: Where can I find information on how to properly install the drivers?[/SIZE]
[GUIDE] Kindle Fire For Beginners – Post #2
Let's take some of the mystery out of getting ADB working in Windows
Note: While those tutorials are made for the original Kindle Fires in mind, the information is still the same in regards to installing and configuring USB device drivers.​[SIZE=+1]Q24: I've read all the tutorials and tried various different tools, but I'm still unable to get my drivers working properly. What else can I try?[/SIZE]
SoupKit
[SIZE=+1]Q25: Now that I know all of the important stuff, how do I root my 2nd generation Kindle Fire?[/SIZE]While there are several tools and scripts used to root the 2nd generation Kindle Fires, they all rely on the same basic method, the Bin4ry method , which takes advantage of a remount timing issue during an ADB restore. It is very effective and works for nearly all devices natively running Ice Cream Sandwich.
Note: Despite some of the rumors about using your Amazon account password as the encryption password, this is a misconception. No password is needed because none was set.​[SIZE=+1]Q26: Where can I find information about how to install Google Play on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version
[SIZE=+1]Q27: Where can I find information about how to install Google Apps on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Apps with Speech Recognition Noob (Simple) Version
*​Forum Rules | New Users Guide | XDA Tour | Report Posts​This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.​
Click to expand...
Click to collapse
What I wanna know is why the hell is this thread in the KFHD Section? I followed your thread to this thread: http://forum.xda-developers.com/showthread.php?p=47659945#post47659945
Followed all the instructions without deviation only to find it was for NON HD Kindle Fires and now I'm fully bricked! Because of this I lost my most prized possesion. Thanks dude.

JonnyLawless said:
What I wanna know is why the hell is this thread in the KFHD Section? I followed your thread to this thread: http://forum.xda-developers.com/showthread.php?p=47659945#post47659945
Followed all the instructions without deviation only to find it was for NON HD Kindle Fires and now I'm fully bricked! Because of this I lost my most prized possesion. Thanks dude.
Click to expand...
Click to collapse
Please quote the exact section you followed. As far as I can see you followed the wrong link since there are three distinct links.
This post contains information on all the kindle fire 2nd generation roms.
Don't blame the op for your mistake:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--》Sent from my mind to your screen

mindmajick said:
Please quote the exact section you followed. As far as I can see you followed the wrong link since there are three distinct links.
This post contains information on all the kindle fire 2nd generation roms.
Don't blame the op for your mistake:
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I was pretty mad at the time I'm over it now. I'm probably gonna pick up a PS Vita and call it a day.

Main Takeaway from this forum
Reading up on the various Kindle Fires, it is said often in many places, but cannot be said often enough. Kindle Fire 2, Kindle Fire HD, and Kindle Fire HD 8.9 are all distinct, separate machines that you need to use different files and procedures on. It seems like the only mistakes that cause unrecoverable bricks are related to folks not understanding this. And even if they have an inkling, they likely don't understand the severity of the distinction.
Custom ROMs and unlocking bootloaders are well documented to be very risky. I know there are disclaimers everywhere. But any help we can give the uninitiated to avoid permanent damage is good karma.

smirciat said:
Reading up on the various Kindle Fires, it is said often in many places, but cannot be said often enough. Kindle Fire 2, Kindle Fire HD, and Kindle Fire HD 8.9 are all distinct, separate machines that you need to use different files and procedures on. It seems like the only mistakes that cause unrecoverable bricks are related to folks not understanding this. And even if they have an inkling, they likely don't understand the severity of the distinction.
Custom ROMs and unlocking bootloaders are well documented to be very risky. I know there are disclaimers everywhere. But any help we can give the uninitiated to avoid permanent damage is good karma.
Click to expand...
Click to collapse
It would be beneficial for XDA to completely split up the forums because I see a lot of bleed through on protocols and techniques.

So, it looks like after failing to root my Kindle and then getting excited by the idea of progress and then bricking it, it looks like I'll have to send it back to Amazon.
Is there anything I need to know before doing so? Does anyone know what the return/repair process looks like? Will they even repair it?
EDIT: Also, I've been using generic Micro-USB-b cables to interface with my Kindle. I can't imagine it's the case, but, to be certain, is it worth ordering the original Amazon cable for any reason (not fastboot/factory, but the "normal" USB-b cable that Kindle's ship with)?

KF HD Stuck at Kindle Fire Screen

Hello, I have a rooted Kindle Fire (with bootloader) and tried to return it to original Amazon Stock OS.
I tried the steps specified on this page androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
After this steps:
"Navigate to the folder where you unzipped the Kindle Fire SRT Tool and double-click on “SR Tool” file. Choose option 1 for “Restore-Factory Rooted with Superuser.apk”. Be patient as it’s very important. The file transfer can take up to 5 minute with no progress notification. If you interrupt the process in any way then you will BRICK your device. After the transfer is done then choose option 4 to “Erase cache and userdata”. Once it’s finished then choose option 6 to reboot."
It rebooted and seemed to be stuck at the white and orange Kindle Fire logo screen. I can turn it off and on by holding the power button, but my computer cannot detect it as a portable device or ADB. But I can enter fastboot mode by plugging the USB while it is turned off, so I don't think it's hard bricked.. I hope so.
Any thing wrong that I have done? Sorry I'm a noob when it comes to this. Help please?
Btw, my Kindle Version 8.4.1

Is it boot looping on the animated kindle logo or the static image one? Cause either way I'm guessing something went wrong with the flash, you should probably reflash the boot and system images, try using kindle fire first aid if the SRT doesn't work, I believe it has a stock rooted image flashing option like SRT. BTW don't confuse boot with bootloader, boot is where the kernel is stored. Just pointing this out because if you don't need to flash the boot loader then u shouldn't, if it corrupts you have a hard brick.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Is it boot looping on the animated kindle logo or the static image one? Cause either way I'm guessing something went wrong with the flash, you should probably reflash the boot and system images, try using kindle fire first aid if the SRT doesn't work, I believe it has a stock rooted image flashing option like SRT. BTW don't confuse boot with bootloader, boot is where the kernel is stored. Just pointing this out because if you don't need to flash the boot loader then u shouldn't, if it corrupts you have a hard brick.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I do have KFFA, which option should I choose? And mine is stuck on a static image one.

Weird sounds like it doesn't want to even try to load the os, maybe some things wrong with the kernel, anyways I haven't ever used kffa, but there should be an option somewhere to restore system image. You will first need to get the device into fastboot mode, just open a command prompt and CD into the kffa directory, I should have a fastboot command, and run this: fastboot.exe -i 0x1949 getvar product
Then plug your kindle in with the power off. If for some reason it doesn't work, which it should because you seem to have flashed something from fastboot before, then u will just have to update a driver before it disconnects.
Edit: OK fixed sorry for the thread mix up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Same problem
I have a KFHD 8.9 with the same problem as the OP. It's stuck on the static (orange) Kindle Fire logo. I have working drivers and I am able to get it into fastboot using "fastboot.exe -i 0x1949 getvar product". The problem is, I don't know any of the history of how it got this way. I have repaired a lot of Generation 1 KF's and I thought I would get started on the Gen 2's so I bought this on eBay this way. I didn't realize how much more risky it was to work on the Gen 2. I also have KFFA working but I can't figure out how to get the stock image onto the KF so I can flash it back to stock. When I go into fastboot mode and use KFFA to reboot to normal more it just stops on the static Kindle Fire logo. Also, I can't get ADB to work at all. Any help would be greatly appreciated.

There's an option in kffa to restore the system partition, should be a fairly obvious choice, if you can't find it try the kfhd system restore tool
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
There's an option in kffa to restore the system partition, should be a fairly obvious choice, if you can't find it try the kfhd system restore tool
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well I tried KFFA Option 7 - Completly Restore the KFHD 8.9 8.1.4 (Fastboot) but it didn't work. There is a problem in RunMe.bat with the wget command when trying to download the .img files from dropbox:
Connecting to dl.dropboxusercontent.com|174.129.21.126|:443... connected.
ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O
=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
Unable to locally verify the issuer's authority.
To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'
Unable to establish SSL connection.
So then, I Downloaded the KFHD_SRT tool and managed to restore the system partition but it still would not boot. Then I saw down at the bottom of the instruction page that to downgrade to 8.1.4 you also need to restore the boot and recovery partitions. After I did that -- PRESTO! my KFHD 8.9 booted up and is now working.
THANK YOU SO VERY MUCH FOR THE HELP!!!!! I will be sure to click the "THANKS" button.

Anchorman42 said:
I have a KFHD 8.9 with the same problem as the OP. It's stuck on the static (orange) Kindle Fire logo. I have working drivers and I am able to get it into fastboot using "fastboot.exe -i 0x1949 getvar product". The problem is, I don't know any of the history of how it got this way. I have repaired a lot of Generation 1 KF's and I thought I would get started on the Gen 2's so I bought this on eBay this way. I didn't realize how much more risky it was to work on the Gen 2. I also have KFFA working but I can't figure out how to get the stock image onto the KF so I can flash it back to stock. When I go into fastboot mode and use KFFA to reboot to normal more it just stops on the static Kindle Fire logo. Also, I can't get ADB to work at all. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey, I got same problem, after I install a bootloader for my KFHD 8.9, the original Kindle OS was unable to boot up, I got 8.4.6 when I recived my KFHD, Is the problem of OS ?

Sorry, but after re-reading my post I realized that I probably gave bad instructions. Mods please delete this post...

Wiped kindle fire HD using TWRP not being detected by pc

i rooted my kindle fire a couple of days ago and then decided to try and install cyanogen mod, to no avail then i was stuck in blue screen repeat and my younger brother who i admit is more tech-savvy than myself managed to get into [TWRP] and he [FORMAT DATA] i don't even have the slightest of idea of how to fix this nor does he, help?

Formatting data shouldn't have been a problem, you sure you installed a ROM for your device and that you did a factory reset beforehand?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Nope, no ROMS on the Device, and when i connected it to the PC i got the JEM-PROD-4 error but i manages to fix that with your modified adb drivers, i just want to get the standard kindle OS back i learnt my lession here g-store and root is good enough, if it isn't broke don't fix it.
I heard factory cable are :/ on the KFHD8.9
I want to restore it to its original state
Is there anyway to maybe push a system image onto the kindle? i installed the ADB as i said before but my kindle still isn't being permanently detected

Just use kindle fire first aid to fix it, its in the 7" general section, also I highly recommend installing a custom ROM, you just have to make sure to put the ROM and gapps on the sdcard ahead of time to make it easy on yourself. If you do decide to do it again just ask for some help when doing it and I'll be glad to post back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Wait so how/when willl my device become recognisable by my system?

I thought you said it was.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

ah its being detected my bad, the KFFA Tut is somewhat difficuilt to understand no videos around?
The eight step of the guide is baffling Kindle Fire First Aide Step 10 tells me to get onto the kindle when it is wiped and locked in kindlefire blue logo repeat i can get into TWRP but thats about it, and also to fix bootloader i need to have superuser/root and i no longer belive that is on here since the wipe

OK I'm not one to go against instructions unless I know what I'm doing, but if you already have java installed, have you tried just running run me.bat? Also what's confusing by in that step? I'm a PC tech so I understand it, but you don't so I don't know which part is confusing.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

broke it down re-arranged it understood did it, i need a factory cable but i hear 8.9 doesn't so i just want to download a system image and smack that onto the kindle i'm download KFDH_SRT_V2.1 right now but i don't know where i should put it in the KFFirstAide directory,
downloading from here http://forum.xda-developers.com/showthread.php?t=2011126 or do i have to tuse the official tool and if so can i get a link.?
constanly updating here, discovered that The tool was in the image or vice-versa and then went to run it only for every time i attempt a CMD command it says fastboot is not recognized as an internal or external command so i can't upload the image to my kindle do i have to move the folder or a file?
Managed to get it to work, go into fastboot and then whatever command i run with fastboot -i 0x1949 flash boot boot.img and the recovery one gives me an errror : flash boot boot.img
error: cannot load 'boot.img': No error :/
after spending at least 5 hours scrolling through thread after thread i give up, is there like a kindle unbricking shop or should i just crack the screen and try to get a use on the warranty?only owned this for 5 days.

OK how do I begin... I don't know what you were trying to do with kfhd SRT by putting it into the kffa directory. Try just downloading the system restore tool, and running it and seeing if you can restore it. From the sounds of it I don't know what you did but the boot.IMG was missing from the kfsrt directory.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

2013 Kindle Fire HD Factory Reset HELP!!

I got a KFHD 2G (2013) from a friend and the problem was simple: when the lock screen came up, he couldn't enter in his passcode because the keyboard wouldn't show up. There was no way to get into ADB since I couldn't get in. I tried to do a factory reset via recovery, but there is no recovery. I built a fastboot cable and tried "fastboot -w" but the partitions could not be formatted. This device seems completely screwed, I trued grabbing the factory update from amazon, but it's in BIN format and won't flash in Fastboot. Inside the BIN file, it seems to just be a recovery-flashable zip, however, it will not boot into recovery so i can't install it. Fastboot reports that two .txt files are missing. I tried extracting recovery.img from the zip and booting it as a ramdisk, however, this just causes it to boot normally. I ended up flashing userdata with boot.img as a way of formatting it, which got the keyboard back, but puts it on a screen saying "Enter password to decrypt Kindle." The password, "LOVE" is not accepted and entering 4 incorrect codes does not prompt a format. I'm at a loss here, it seems like it's just nt possibe for this thing to be screwed completely, but im out of options. what should i do?
HELP!!!
Also, I just realized this thread should be in "7" Kindle Fire HD Q&A, Help & Troubleshooting"

Um so now it's to the point where it's asking to format it because the password is wrong so wouldn't that be the same as formatting it as you had intended on doing earlier? BTW fastboot commands on a kindle fire have to be prefixed with "fastboot -i 0x1949", also I don't know off hand if that command you were going to run is a user data wipe or a complete wipe and a complete wipe would been bad. So at this point if the lock screen asks you to format it and you don't have adb enabled then you probably will have to format it, I thought the new gen had adb access from early on in the boot process but I could be wrong, I suggest looking in the hdx section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Um so now it's to the point where it's asking to format it because the password is wrong so wouldn't that be the same as formatting it as you had intended on doing earlier? BTW fastboot commands on a kindle fire have to be prefixed with "fastboot -i 0x1949", also I don't know off hand if that command you were going to run is a user data wipe or a complete wipe and a complete wipe would been bad. So at this point if the lock screen asks you to format it and you don't have adb enabled then you probably will have to format it, I thought the new gen had adb access from early on in the boot process but I could be wrong, I suggest looking in the hdx section.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
sadly, no adb, its not an HDX because it's only dualcore. i now need a system.img and userdata.img.. i flashed the img from the ADK for this device and now all i get is fastboot.. i need ripped imgs from an actual device. the command i was running was a userdata/cache wipe, and i did prefix it but fastboot couldnt format the partitions because the filesystem wasnt compatible. The lock screen flat out wouldnt ask me to format, and the back button never showed up, which leades me to believe the system image was corrupt too. if anyone can give me system.img and userdata.img i would be eternally grateful! thank you for replying

Ah I knew it wasn't an hdx but they some things on that device that are similar to the hdx, like I think they disabled some fastboot commands from working and such. Hopefully someone more familiar with 2nd gen hd's can help you out more.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Ah I knew it wasn't an hdx but they some things on that device that are similar to the hdx, like I think they disabled some fastboot commands from working and such. Hopefully someone more familiar with 2nd gen hd's can help you out more.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
so i borrowed a friends kindle and backed up his /system. i then sparsed it and it installed fine. when i booted up, i got a red flash and it threw me into fastboot. i then flashed the u-boot from the update file and now im bricked beyond all reair.. i run lsusb and get no mention of the device with my factory cable, and i cant get back in fastboot. the 2nd gen hd's suck so much..

Ouch, was his kindle a second gen HD?
Sent from my Amazon Kindle Fire HD using Tapatalk

[Q] Kindle fire 8.9 LTE 2nd gen on 8.5.1 root help

i recently was given a 2nd Gen Kindle Fire HD 8.9 that has 8.5.1 on it.. it has never been rooted, and does not have officesuites on it. i cannot find a specific how to for a rooting solution. ive found a script that might have worked on http://forum.xda-developers.com/kin...nable-to-root-access-fastboot-kindle-t2933163 if i had officesuites. its a thread that hasnt been active in some months so im not confident on a solution.
my question is..
can someone direct me to a known how-to for rooting a 2nd Gen HD 8.9 with 8.5.1 that hasnt been rooted already.
anyone have an ANSWER and not just that they have the same issues?

not everybody all at once now... ive continued looking and even some KNOWN good methods for 8.5.1 arent working.. none of the tools see the filepath or recognise the kindle. I can verify that adb is connected but then i go back to the tool folder and it starts messing up.

or worse.. links to a method are broken and not updated anymore..

I also need to root my FireHD 8.9 2nd gen that is on 8.5.1. Did you ever find a solution? Were you able to downgrade?

Kingroot was able to root my Kindle with 8.5.1.
Download it in Kindle browser from here: https://kingroot.net/

AlwaysLucky said:
I also need to root my FireHD 8.9 2nd gen that is on 8.5.1. Did you ever find a solution? Were you able to downgrade?
Click to expand...
Click to collapse
You should be able to downgrade with KFHD System.img Recovery Tool
I actually used this tool to fix bricked KFHD 8.9 but the end result is with firmware 8.1.4 so you can pick up from there and root the device. It doesn't really matter what version of firmware you have at the moment.
*Install Android SDK before using this tool.
Below are some notes I made myself when I was fixing my KFHD 8.9 LTE with this tool.
Brick can be fixed by KFHD System.img Recovery tool.
Download KFHD_SRTv2.1-8.1.4, boot and recovery image.
Connect Fire HD 8.9" to computer with regular USB cable then turn it off (it will be turned on automatically when it is connected to computer).
Run SR Tool.bat then choose option 1 and n for next question.
Hold down the volume up button and press power on the tablet for about 3 seconds and then release the power button and continue holding down the volume up button.
Tablet should display the yellow fastboot logo and KFHD recovery tool will verify that you are in fastboot.
Flash the system with option 2.
Erase cashe and user data with option 4.
Open a separate cmd window and navigate to directory where boot and recovery image are.
Use these commands to flash them.
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
Return to the KFHD recovery tool window and select option 6, wait for tablet to fully reboot and then enable adb and allow applications from unknown sources. Reboot takes several minutes so be patient.
KFHD recovery tool then asks to press any key to continue and it is supposed to install google framework but tablet was not recognised at this stage. Without google framework Fire HD 8.9" still works fine though. Just have to make sure that the device is connected with ADB interface. Check on device manager and make sure 'Android Composite ADB Interface' is up and running under Kindle Fire.
Fire HD 8.9" should be in stock stage with fire os 8.14 now.

There is no need to downgrade. Kingroot provides root for this device even with the latest firmware.
Once rooted, TWRP can be installed via the methods presented in other threads.

Looks like Sonic posted his while I was writing . It sounds much easier than going through downgrade. I would say go with kingroot if it works. :good:

SoNic67 said:
Kingroot was able to root my Kindle with 8.5.1.
Download it in Kindle browser from here: https://kingroot.net/
Click to expand...
Click to collapse
Just wanted to give you an extra thanks for such a simple solution. I used the KingRoot APK to root 8.5.1 easily. Then I flashed TWRP 3.0.1-0 successfully using FireFlash. Rebooted into TWRP, flashed RessurectionRemix ROM and BAM, it's like a new tablet.
Kudos to you both for taking the time to help out.