Database Develop

[Q] Fire HD stuck on logo screen

Hi,
I made some changes to the build.prop and the kindle will no longer boot, as per instructions I took a backup first but the kindle will not boot so I can restore the file. Is there a recovery mode or any way I can do this?
Many thanks in advance.

Have the same problem except I'm not sure what I did. Last night, I went to bed with the KFHD's screen turned off and woke up to see it powered off. I assumed the battery got drained so I charge it via wall outlet and turned it on. Now I'm stuck on the "Kindle Fire" logo. Usually, the logo "animates" and I can get in but now I'm fkd. Arrrhghh.. hope someone knows the solution. I don't have a fastboot cable either..

vanizial said:
Have the same problem except I'm not sure what I did. Last night, I went to bed with the KFHD's screen turned off and woke up to see it powered off. I assumed the battery got drained so I charge it via wall outlet and turned it on. Now I'm stuck on the "Kindle Fire" logo. Usually, the logo "animates" and I can get in but now I'm fkd. Arrrhghh.. hope someone knows the solution. I don't have a fastboot cable either..
Click to expand...
Click to collapse
You must have a fastboot cord at this point. you can order a fastboot tip from here too http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit

kindle fire hd 7 cant boot

im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.

huntergero said:
im a complete newb to fixing mobile devices and my friend gave me a messed up kindle fire hd.He said he screwed around with the os files and deleted one and he doesnt not know what one it was and when i try to boot it tries to boot but kindle file system recovery comes up. Then it asks me to reboot or factory reset i have tried both multiple times to no avail.I have a fastboot cable so that isnt a issue.Can somebody help me with a step by step or link to one.
Click to expand...
Click to collapse
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.

LinearEquation said:
You will need that fastboot cord.
Here is a system restore tool. I prefer to push the files manually but it will run as a tool http://forum.xda-developers.com/showthread.php?t=1951254
When you turn the Kindle Fire HD 7 on, push up on the volume rocker for three seconds until the screen shows the blue TWRP screen and release rocker and enter TWRP. (you said it boots into recovery?)
If this is the case, you don't need to do a full system restore. You can push a ROM the zips onto TWRP. Get them from the system restore tool.
If you have questions, feel free to ask. The tablet is recoverable unless something wrong is flashed.
Click to expand...
Click to collapse
When it failed to boot in went into kindles reboot software and when i asked the individual i got this from he said he didnt install any recovery software.Can I install twerp now

huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
Nope, it has to be a factory restore using your fastboot cord. I will list instructions.
---------- Post added at 09:50 PM ---------- Previous post was at 09:30 PM ----------
huntergero said:
Can I install twerp now
Click to expand...
Click to collapse
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit

[SOLVED] Please Help Me Help Myself

I finally decided to root my daughters KFHD. I said, "Dont worry once Im done and install a custom ROM itll be 10x better than before." She reluctantly said okay only because shes seen me do the same thing to every phone and tablet Ive ever had. I knew from looking around and doing research here on XDA that there was a good chance something could go wrong and I could end up bricking her kindle. Ill cut to the chase.....Something went wrong with the install of the 2nd bootloader/recovery. I ended up with the lovely RSOD. So I proceded to make a fastboot/factory cable. Now Ive gotten rid of the RSOD but the kindle is stuck in bootloop and eventually itll go into the stock recovery saying blah blah blah kindle wont boot. Ive tried the factory reset option to no avail. One thing I find odd is this is the 2nd type of bootloop Ive seen, the 1st one would show the kindle logo for only a few seconds then it would do like the CRT animation does and bootloop from there, now tho, it actually shows the entire bootanimation, I know this because I can see the gradient color change that goes across the kindle fire logo. At this point Ive flashed everything from hashcodes thread, the 7.2.3 bootloader with the freedom 7.4.6 img and the twrp recovery several times. Ive flashed 2.7 and 2.3 recoveries along with a 7.2.3 boot img and 7.2.3 system img together with no luck. So heres where I need someone from within this wonderful open source community to help meh. Gimme a quick rundown of the kindle boot process with the 2nd bootloader including what boots when and where it boots from. Also when using fastboot whats the correct order to flash what? Should I only be trying to flash a recovery now? I shouldnt need to reflash the bootloader right? what about the boot and system img's do I flash those? This is where I need the help. Thanx in advance for taking the time to read my short novel and for helping me. Oh ya Im on linux so i havent been able to use any of the tools that are available for Winblows.

OK, from what I know you didn't install the stack override in the system partition. That's why its bootlooping.
Sent from my GT-i9100 running CM11

Thank you for the reply....after all the reading I've done I was kinda thinking that may be my problem. Is it possible that I did originally push it to my sdcard, then sometime in between then and now I erased it with the fastboot erase data command? There is no way to push anything to sdcard with fastboot, right?

Well from what I can tell the tablet is burnt. I will post pics after I smash it with a hammer and run it over with my car.

Burnt? Nononoo. Don't waste a device that is still "working". It is just bootlooping. Send it to a dev instead of breaking a good device.

No need to do that lol. Get yourself a fastboot cable and use the SRT or KFFA to restore system
Sent from my GT-i9100 running CM11

I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.

DowneyJM said:
I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.
Click to expand...
Click to collapse
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet

SafinWasi said:
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet
Click to expand...
Click to collapse
Thank you for taking the time to help me I really appreciate it.

DowneyJM said:
Thank you for taking the time to help me I really appreciate it.
Click to expand...
Click to collapse
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help

SafinWasi said:
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help
Click to expand...
Click to collapse
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.

DowneyJM said:
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.
Click to expand...
Click to collapse
No problem mate! Trust me,once we're done with it,both you and your daughter are gonna LOVE it.
OK,basically when the tablet turns on,it runs a binary called the u boot. Now this is Amazon stuff and can't be tampered with. But we have the source code due to GPL and what we do know is that a part in the code allows us to flash unsigned third party kernels,therefore a 2nd bootloader. But it can't just be any boot image,it must be patched with the Amazon u boot AND the stack override. Not only that,you must also have installed the stack override in a specific byte address of the system partition. Once we've done that, we can safely flash a recovery and thus,get the ability to install custom ROMs. Oh,another thing. Amazon patched the u boot on versions higher than 7.2.3,so the stack will cause it to crash and show the Red Screen if it's not 7.2.3
Sent from my GT-i9100 running CM11

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.

Kindle Fire HD Stuck on flash logo screen

I wanted to install Gapps to my Kindle since many of the apps including the web browser are coming up as unsupported. I have rooted my Kindle Fire HD 8.9 and installed TWRP. When I rebooted my kindle to enter the recover mode, it got stuck at logo screen.
At first, when it was logo was flashing if I plugged it in, ubuntu give an error message "unable to mount Jem PVT Prod 04". I discovered that holding the volume up button made the screen go blank but not off. You can plug the kindle in and Ubuntu will recognize the kindle and allow you to access the internal storage.
How can I fix and reboot the Kindle from Ubuntu?
I researched tons of solutions but most of them require Windows which I don't run or I tried the instruction and they don't work or our incomplete.

I received a fastboot cable from Amazon today. I'll see how it works. Any advice would be appreciated.

Okay, I fixed the problem with the Fastboot Cable. Here's the steps that I did to fix it. It was loading Twrp or the bootloader so I reinstall them. I have Android SDK on my computer and my Kindle is rooted.
Step 1.
The correct twrp was difficult to find. This forum offered a site to go to but I found the site was corrupted and the website was trying to download a virus.
I found the twrp and bootload file here.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet/
I placed the files in my android/sdk/platform-tools. (kfhd8-freedom-boot-8.4.3.img & kfhd8-twrp-2.6.0.0-recovery.img)
I typed into terminal "fastboot -i 0x1949 getvar product" without parenthesis. At the waiting for device command, I plugged in the Kindle with the Fastboot cable and held the Volume up button to go into fastboot mode.
I opened the android/sdk/platform-tools and right click the mouse and hit open in terminal
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
From the reboot, hit the volume up to get into twrp.
At this point, I still could go into the kindle so I thought the operating system may be corrupted.
Step 2
In twrp, I backed up the system. and rebooted into twrp.
In twrp, I hit wipe and rebooted back into twrp.
I downloaded CyanogenMod and Gapps to my platform-tools folder again.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet
Step 3
I couldn't access the internal drive so I used ADB to put the files on my kindle.
Here's a video of the instructions I used.
youtu.be/NaK5OxUeDKM
Open the support document for Ubuntu instructions.
First, open terminal in the Platform Tools file and type ADB Devices. When I pushed the two files, his instructions say to use command sudo ./adb-linux push filename /sdcard/. This didn't work. I used "./adb push [filename /sdcard/." without the quotes and it worked.
Step 4
Enter twrp and install the CyanogenMod and Gapps. Reboot
This got my operating system up and running perfectly.
Now bad for a complete Noob.