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.​

Really well written and organized. Despite the fact that i read everything here... I even learned something. This should be really helpful to new users!
--
Sent from my mind to your screen.

Vote for Sticky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

Thanks for this detailed NOOB guide, it helped answer a lot of questions about my device..
I have one query around Q6
Q6: How will I know what version of the stock bootloader is installed on my device?
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.
My kindle device has a software Version of 7.4.3_user_43093XX. So looking tt this guide, i have a KFHD2. Also the bootloader cannot be exploited (right??). The answer to Q6 says "everything beyond that must be replaced with a previous software update" does that mean i should ask Amazon to replace my device? OR i need to downgrade the software on my device?
My device is rooted, and i dont have the factory cable, but i am able to get into fastboot using the "reboot bootloader" method. My aim is to get a custom rom on the device as well as some sort of recovery software (twrp).

Ok first off thats for the write up, it was very helpful. My question for you now is this. Is there any news on rooting the kindle ver 11.0.3.0? All I have read is ver 10, any help would be appreciated.
Sent from my GT-N5110 using Tapatalk 4 Beta

mann75 said:
Ok first off thats for the write up, it was very helpful. My question for you now is this. Is there any news on rooting the kindle ver 11.0.3.0? All I have read is ver 10, any help would be appreciated.
Sent from my GT-N5110 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There are no exploits for the newer 11.xxx Kindle Fire Hd's yet.

LinearEquation said:
There are no exploits for the newer 11.xxx Kindle Fire Hd's yet.
Click to expand...
Click to collapse
How long has this kindle vers. 11 been out for?
Sent from my GT-N5110 using Tapatalk 4 Beta

mann75 said:
How long has this kindle vers. 11 been out for?
Sent from my GT-N5110 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The 11.xxx is a new version of KFHD7 released by Amazon for a cheaper price and removing the camera and HDMI port. It's only been out a month or so.
Sent from my Amazon Kindle Fire HD running Paranoid Android using xda app-developers

LinearEquation said:
The 11.xxx is a new version of KFHD7 released by Amazon for a cheaper price and removing the camera and HDMI port. It's only been out a month or so.
Sent from my Amazon Kindle Fire HD running Paranoid Android using xda app-developers
Click to expand...
Click to collapse
Has there been any news about this vers. 11 being rooted?
Sent from my GT-N5110 using Tapatalk 4 Beta

Thanks OP great FAQ
Might be worth added a note that in the UK and Europe the Kindle Fire (Initial model - Kindle Fire 1) was never sold, so folk in the UK (and Europe with a local device) will only have a KF2. This is reported on Wikipedia.

kindle 1 or 2
thanks for your great tutorial!
//nvm I found out the answer

i have more questions...
- The tips for mac users are the same from the tutorial "Introducing: Kindle Fire 2nd-bootloader + TWRP 2.7.0.0 for the Kindle Fire HD 7" and from the tutorial "Introducing: Kindle Fire 2nd-bootloader + TWRP 2.6 .3.0 for the 2nd gen Kindle Fire "?
- And the silly last question, I've read around here in the forum updates of Amazon can erase all changes you have done in the KF, in fact I'm going to change the rom because I'm tired of losing root every x months. It is possible, indeed, lose custom rom?
Sorry for being a pain, i hope there is someone to have aswers to my questions.

Is it possible to root a Kindle Fire 2 with software version 10.5.1? If I correctly understand this OP, it's not possible. But on another thread somebody said that they achieved root on a 10.5.1 KF2. I'd love to root this thing. Help please?

I can add that firmware 10.5.1 won't boot from the old bootloader, I wish i had taken backup of that firmware. So the only chances are proceding to restore an older firmware or install any ROM vía twrp right away. So no turn back after the fiesta first flash

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...

[Q] Attempted to load android and failed

Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike

mikeroundrock said:
Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike
Click to expand...
Click to collapse
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
OK. I followed your instructions and installed the driver. I then attempted to install a base image following the instructions here:http://forum.xda-developers.com/showthread.php?t=2011126
I chose the following prompts: 1. enable fastboot, then 2. Restore-su/supersu.apk only, then 4. Erase cache and userdata, and finally Reboot normally. No luck.
I'd really appreciate any and all ideas/help. My hope is to turn this brick into something productive again.

What are you using to restore the kindle?

stunts513 said:
What are you using to restore the kindle?
Click to expand...
Click to collapse
All I have are whatever people have shared. As mentioned in my initial post, I do not have a backup of what I had before I started. Perhaps my biggest mistake. My understanding is that I need to get the Kindle software back on it in order to install the Android bits. Perhaps I am in error on that thinking. Please let me know if that is an unneeded step.

Use either kindle fire first aid or system restore tool and stay away from kindle fire utility unless you want a paperweight.

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Rooting Kindle Fire Update 6.3.3 and Flashing FireFireFire and TWRP (2014)
Click link here>> (http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) <<Click link here
Please feel free to share issues, questions and offer help
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on the topic described in the OP
[SIZE=+1]FAQs: For System Version 6.3.3 and 6.3.4[/SIZE]
[SIZE=+1]Q1: Can the Kindle Fire Utility root a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q2: Can the Kindle Fire Utility install a custom bootloader/recovery on a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q3: What can the Kindle Fire Utility with a Kindle Fire 1 with system version 6.3.3?[/SIZE]The included install.drivers.bat can install drivers on a PC
Once the Kindle is rooted, The Kindle Fire Utility can install Google Apps​[SIZE=+1]Q4: What can root a Kindle Fire 1 with system version 6.3.3?[/SIZE]SafeRoot Can [Windows/Linux/Mac]​[SIZE=+1]Q5: Can be used on Linux and Mac?[/SIZE] Yes see
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) by AshtonTS
[Guide] How To Setup And Use Fastboot by demkantor

problem with step 6 " Flashing FFF and TWRP without Fastboot Cable"
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.

skins20 said:
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.
Click to expand...
Click to collapse
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk

sd_shadow said:
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
just say "kindle" in device manager.

skins20 said:
just say "kindle" in device manager.
Click to expand...
Click to collapse
Did you get drivers installed?

x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries) and neither of my computers (one runs linux, one Windows) are able to see the device correctly. Windows shows it as an unknown device, but I have the fastboot drivers installed. That's why I said I need a factory cable, hoping that I'd be able to get it into fastboot to repair it
Click to expand...
Click to collapse
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries)
Click to expand...
Click to collapse
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?

sd_shadow said:
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
Click to expand...
Click to collapse
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
sd_shadow said:
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?
Click to expand...
Click to collapse
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.

x2110311x said:
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.
Click to expand...
Click to collapse
If all you used is the alt fbmode file, it is likely in fastboot mode, which just shows Kindle fire screen with no animation.
If there is animation on the kindle fire screen, it's bootlooping...

It turns out that it was just stuck in fastboot, and windows was having some issues. I did nothing to the drivers, and it worked fine after trying again

Stuck on Kindle Fire(Doesn't Change) screen
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!

dharangamer said:
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
99% of the time drivers are the issue
How is it listed inn device manager?
---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------
Which windows version? 7, 8?

It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.

dharangamer said:
It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.
Click to expand...
Click to collapse
With windows 8, You need to disable driver signature enforcement, before installing drivers, and use the Instal.drivers.bat from Kindle Fire Utility

That took care of it. Thank you so much!

help on kindle 7.5.1
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot

nilnyl said:
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot
Click to expand...
Click to collapse
see http://forum.xda-developers.com/fire-hd/help/how-to-root-kindle-fire-hd-7-firmware-7-t2931436

Can't root KindleFire
hi I am trying to root my kindle but it does work I use the Saferoot way and it does work

Corrupted settings.db- stuck in boot loop
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...

cwaskey said:
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...
Click to expand...
Click to collapse
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options

sd_shadow said:
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options
Click to expand...
Click to collapse
Code:
adb devices
does show my Kindle serial number. As I said, adb seems to be working, despite the fact that the Kindle doesn't complete the boot process.
I have not installed or tried fastboot on my PC, so I can't answer whether that works.
Edit: I should mention that when the Kindle was still running, I allowed just about every permission in the on-Kindle superuser app.

Bricked Kindle Fire HD 8.9?

I'm not an expert by any means at customizing my android devices, so please bear with me.
I have a Kindle HD 8.9. I successfully rooted and installed a CyanogenMod on the Kindle, but my whole reason for trying to mod the Kindle was to get to a version of Android that the Sonos App would run on, and unfortunately the CyanogenMod I chose was too old (I was Android 4.3 and I needed 4.4 or later). I found later builds of mods for the Kindle but none of them would flash successfully, giving me errors where research indicated that my version of TWRP was too old and needed updating. This is where things went very, very wrong.
I downloaded the TWRP app and tried to update using that. No luck. I couldn't figure out how to update TWRP so I got desperate and started doing stupid things. I downloaded a zip file with the latest versions of the img files from TWRP and having no idea what I was doing, in fastboot mode, started flashing IMG files. The last thing I remember doing was flashing the boot.img to the device.
I'm in a situation now where the device will only boot into fastboot mode (when powering on + volume up button). I can see the device in Windows 1 0 device manager and I have the ADB device driver installed properly, but I just can't communicate with the device via ADB. "adb devices" command shows no devices, fastboot devices shows nothing. It seems like a driver issue but I've tried everything I can think of there. So windows can see it, but ADB cannot and at this point I'm totally stuck. I understand that I may have destroyed the tablet at this point but it seems like if Windows can see it, there should be *something* I can do to fix this.
If anyone has any suggestions, I'll try anything and appreciate any attempts to help me out of this mess.

Resolution
I've been struggling with this issue for weeks and no sooner did I post the question here did I find the solution. So, in case anyone else ever has the same issue as me...
When I originally rooted and modified the tablet I was following instructions from a website that had me modify the adb_usb.ini file in my .android directory to include the following: 0x1949. I honestly don't know what that is, some sort of memory address or hardware ID or something... something specific to the Kindle HD 8.9 device I think.
After spending the afternoon browsing the web for solutions I ran into something somewhere that talked about the vendor specific information in the adb_usb.ini file. This made me investigate that part further and I discovered that something I did along the way changed whatever that number is from 0x1949 to 0x1950. I found that out by right clicking on the device in device manager and selecting "properties" then selecting the "Details" tab and selecting "HardwareIds" from the dropdown. The number that showed up there had a 1950 in it and even though I had no idea what I was doing, I figured what the heck, try modifying the adb_usb.ini file to 0x1950 instead.
That change allowed me to see my device when typing "adb devices" at the command prompt and from there I was able to figure out how to update TWRP and finally load a more current ROM. And it *was* an outdated version of TWRP that was preventing me from installing the later versions of the ROM. Once I updated that, then the ROMs flashed without error (as soon as I figured out I needed to be VERY PATIENT because the ROMs took a long time to flash and went to a blank screen several times).
I am now happily running cm-13.0-20160807-UNOFFICIAL-jem on my Kindle HD 8.9 and have successfully installed Sonos app and am operating our Sonos system from this device.
I hope this info helps someone. I wish I was more technical and understood what I did to break things and what I actually did to fix them, but it worked so I guess I won't complain.

Kfhd 8.9 bricked?
I know this post is old but I need advice/help.
Have a Kindle fire he 8.9 tried to do a full conversation but after trying to flash room I can now only get the white/orangeish logo or I can get in to fastboot via "fastboot -i 0x1949 getvar product" I can also flash files ie recovery.img boot.img system.img ect but can't get back in to recovery or os. The restore tool seems to work but don't. At the end if my Whit's any help would be appreciated