Database Develop

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows.

The SoupKit
{
"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"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

worked great. thanks for a great tool. easy to use.

Awesome...thank you..just set this up on my ubuntu netbook...going to try it today when I update twrp

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

Works great!

ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux

wojo797 said:
ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux
Click to expand...
Click to collapse
Yeah, when I updated the script, I forgot to change the permissions...
Give me a little while and I'll fix it for you.

3-16-2013: Fixed issue with permissions on the rootplus script

the issue wasnt with the rootplus it was with the soupkit itself the install.sh script

wojo797 said:
the issue wasnt with the rootplus it was with the soupkit itself the install.sh script
Click to expand...
Click to collapse
That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"

[OK thankOTE=soupmagnet;39303980]That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"[/QUOTE]
Ok thank you.. Appreciate the help and all then work...I'll try as soon as possible

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.

04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons.
By the way, there is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon and the requirement to downgrade the stock bootloader before continuing with the 2nd bootloader install process.

Hi,
I'm totally new to linux, and i managed to install the latest Linux mint (v14.0) I was also able to connect to the internet and i downloaded both the soupkit and rootplus using linux. I extractred the files and doubled clicked on the install.sh as per the readme file however, after i double click it, all the contents of the folder disappear and i don't get any options as per the readme file. The same happens with the rootplus install.sh file, all the files disappear.
These are the steps i've followed.
Installed Linux Mint v14.0 on the system after making necessary partitions(ext4 journal)
Internet connectivity present.
Downloaded both the files into the downloads folder and extracted them
double clicked on the install.sh file and everything disappeared fro the respective folders.
Please guide me as i'm completely blank here.
Regards,
CD

Hi,
I was able to make it work. Instead of double clicking the .sh file, i opened the terminal window in the extracted folder, got super user access and executed this command:
sh install.sh
So now my kindle is rooted and ads free.
Thanks a lot @soupmagnet.
Regards,
CD

So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!

anacondo said:
So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!
Click to expand...
Click to collapse
Sorry to answer an old post but yes.

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows

The SoupKit
{
"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"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.​ ​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires.
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

I actually wish I needed this because god damn this is a sexy piece of kit.

Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app

Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1

Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...

soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks

2strokenut said:
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
Click to expand...
Click to collapse
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?

soupmagnet said:
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
Click to expand...
Click to collapse
That worked like a charm! Thanks for all you do!
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.
Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
I exited the terminal and re-ran option 6, this is what it gives me now:
blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >

There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.
[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"

Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.

empoy78th said:
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Click to expand...
Click to collapse
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.

soupmagnet said:
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
Click to expand...
Click to collapse
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
empoy78th said:
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
Click to expand...
Click to collapse
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!

empoy78th said:
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Click to expand...
Click to collapse
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.

3-16-2013: Fixed issue with permissions on the rootplus script

soupmagnet said:
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.

In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.

Installing Android 4.2.2 CM10.1

Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar

PetarHolland said:
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
Click to expand...
Click to collapse
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.

Thanks, i will read this, then i'll post here if i still need some information The entire process seems to be very hard ^^
soupmagnet said:
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Click to expand...
Click to collapse

I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
{
"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"
}
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance

Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
ed! said:
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Click to expand...
Click to collapse
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.

Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1

Indeed... The entire process is hard, i'm trying to organize the information. SO the step are:
-Fastboot
-Installing bootloader
-Cleaning the system/exporting img
-Installing the rom
-Wipe
-Reboot
android :victory:
Right?
Some questions:
I read about a special cable, i can't do the process with the standard miniusb cable?
I read about downgrade the firmware of my kindle... I have the 7.3.0.3 version, i need to downgrade before install the bootloader right?
ed! said:
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Click to expand...
Click to collapse

@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!

Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
E_Zatopek said:
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Click to expand...
Click to collapse

PetarHolland said:
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
Click to expand...
Click to collapse
Just a note of caution, as with all flashing of rom's. Whilst the fastboot cable is not 'required/essential' if you do mess it up , there is a potential that you 'could' brick, and depending to what extent your at, the cable becomes vital. In a nutshell if you can get your hands on a cable its recommeded as the earlier thread stated its a kind of insurance!
Good luck
kgyuszko

Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?

Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse

from ondom
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
PetarHolland said:
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
Click to expand...
Click to collapse

ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
PetarHolland said:
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
Click to expand...
Click to collapse
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.

How can i test if my fastboot work? if i type fastboot on cmd i have the entire instruction of fastboot, so the command is recognised....
seokhun said:
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
Click to expand...
Click to collapse

fastboot -i 0x1949 getvar product

<waiting for device>
but when i plug my kindle fire and reboot, no fastboot, still <waiting for device>
I previously installed the sdk developer tool and changed the PATH adding the skd folder path to the windows shortcut for the cmd.
soupmagnet said:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse

You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.

Nope, i tryed every possibility, plugging turned off, plugging turned on and reboot, leaving to "waiting for device" for 2 hours, and nothing happened. soupmagnet suggested me to use the kindle first aid script to reinstall the adb drivers, seems the best option atm....
seokhun said:
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Click to expand...
Click to collapse

Cyanogenmod logo all the time
seokhun said:
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Click to expand...
Click to collapse
I did exactly this and now i get the cyanogenmod logo all the time after reboot. been this way for 40 mins already. Can someone suggest what to do next?

[Q] [Root] KFHD "7 | HowTo Root on Mac?

I don´t get it managed to root my KFHD "7.
It´s on 11.3.2 and I´m using the stock USB Cable (is factory cable mandatory?). I made chmod 777 for the RunMe.sh and I´m running a MacBook Pro on Mavericks.
"./adb devices" shows my device...
I already found this http://forum.xda-developers.com/showpost.php?p=50985251&postcount=347
I absolutely do not understand, why it won´t work. Of course for some of you it will become absolutely obvious, why it won´t work, when they read this.
This is what I get:
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
remote object '/system/bin/ric' does not exist
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
Pushing busybox ...
5178 KB/s (1085140 bytes in 0.204s)
Pushing su binary ...
4653 KB/s (91980 bytes in 0.019s)
Pushing Superuser app
5267 KB/s (996704 bytes in 0.184s)
Pushing ric
26 KB/s (57 bytes in 0.002s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again ...
Copying files to it's place ...
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Click to expand...
Click to collapse
Yes, I´m root user on the Mac.
Thanks for your help!
Ps: These are the threads I already read and I´m looking at...
[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
manual fastboot whitout factory cable... regarding that, the factory cable doesn´t seem to be mandatory for rooting the device?!
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [12/09 FREEDOM 7.4.6]
That´s what I want on the KFHD: [ROM-AOSP] Unofficial CM11.0 KFire HD 7 (KK 4.4_r1.2) [03/25 CODEC FIXES]

You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access. On another note I just realized that that rooting thread for the 2013 HD didn't have a Linux/Unix compatible rooting script, only a batch file which is for windows, I assume the script is pretty simple, haven't looked at it yet. How about I convert it to bash and see if it will work for ya? I'll just have to grab the mac location for bash but other than that its pretty straightforward.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It´s this one: http://www.amazon.de/Kindle-Fire-Zoll-HD-Display-WLAN/dp/B00CTV13Z4/ref=sr_tr_sr_1?s=digital-text&ie=UTF8&qid=1397119675&sr=1-1&keywords=fire+hd

Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I read it now. Thanks, that would be great. Althought I will most probably send it back, because I were not aware of that fact and the stock ROM is slow and ugly ? But nevertheless that would be good for other Mac users too, I think ?

I'll post it tomorrow as I'm going to bed, I don't wanna work on it while I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk

Fire 7 v5.1.3 - help getting started (Root, Flashing CM, etc)

I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!

Blastyrant said:
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Click to expand...
Click to collapse
FlashFire can be sideloaded; no need to install the Play Store or any other Google components before/after rooting.
http://www.apkmirror.com/apk/chainfire/flashfire/

I can not get any driver installs to take. I have not been able to start the 5.1.2 downgrade to attempt rooting. This has become rather frustrating.
Installed the Kindle Fire USB Drivers and the device becomes recognized. When I plug it in an "auto run" pop-up appears. But I am unable to connect via ADB to begin to downgrade. I have USB debugging turned on and followed the instructions in the Root Junky video guide. After that I restored my system. I tried to associate the driver via Device Manager but am always unable. My Win7 machine is unable to find them when I search as per the many instructions I've read thus far. From what I've read and seen, I should have an option in the "let me pick from a list of device drivers on my computer" button that says "Android devices" or "mobile" and those (or anything even remotely like them) are never in the list.
I then ran the 15 sec ADB Installer v1.4.3. This copys 0 files, when in THIS video guide it shows it copying 4 files. When asked to "install the USB drivers" the program gives me an error log that says "Invalid command or parameter", which has something to do with DPInst_x64.exe. I do not have the permissions to post in the discussion thread for this tool to ask what I am doing wrong.
After that I tried THIS method. When I browse the extracted folder I get a message that "Windows was unable to install your Fire" and "Windows could not find driver software for your device".

WARNING Do not downgrade below 5.1.2. It has been confirmed to brick the device.
Here is a status update for anyone who is attempting to do the same thing and has been running into obstacles.
I uninstalled all of the drivers. I did this with a system restore. But you could just as easily do this manually. I've also seen some "wipe" tools online that claim to rip out all Android drivers, maybe try one of those if needed? Once they were gone I turned the Fire 7 ADB debug mode on. I then installed the Kindle drivers from Amazon. Then I plugged in the Fire 7 via USB and let it "install drivers". I checked Device manager and this time ADB was showing up. I then shut down the Fire, held volume down+power to boot into Recovery Mode. I had to then manually point the Fire in Device Manager to the correct drivers. Then I sideloaded the 5.1.2 firmware and it has flashed successfully. Next is Root and then CM12.1.
Here is what I did:
To start, it was running 5.1.3 out of the box. I never connected it to WIFI, never altered it, never updated it, etc. It was a stock Fire 7 Gen 5.
1. Delete all previous Amazon driver installations (if required)
2. Install THESE drivers (I'm on Win7)
3. Enable ADB debugging on your Fire tablet (Info can be found here)
4. Download and extract THESE ADB Fast Boot Files from Root Junkys.
5. Download the v5.1.2 OS build from HERE and then verify the SHA1 and MD5 checksums with THIS free online tool.
SHA1: 66B5423725B79CEB0D5866FA32FF414A99A4B50A
MD5: 5B0DCC957DEF3ACCFF58BF33794D6D88
6. Connect your powered-off (turned off, in the off state, etc) Fire 7 5th Gen tablet via USB and then hold volume down+power to boot into Recovery Mode.
7. (perhaps optional) If Fire is not listed as a usable device in Device Manager when in Recovery Mode (or has that warning icon next to it), you'll need to manually point it to the drivers you installed.
.....Select Other Devices > Fire and then Right Click it and choose Update Driver
.....Click the button to let you pick from a list of drivers on your computer. Find the Amazon device (Fire Device) in the list and then choose "from disk".
.....Navigate to the default driver install folder (C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers)
.....Select Android Composite ADB interface (this is for Stock ROM, recovery/adb sideload)
More info for step 7 can be found HERE under "Connecting Your Tablet to Your Computer"
8. Hold Select and Right Click anywhere in the extracted ADB Fast Boot Files folder and choose "Open Command Window Here" from the context menu.
9. In the command window type "adb sideload <path to the v5.1.2 firmware>"
.....IE: C:\Users\MyPC\Desktop\Amazon Fire\ADB FASTBOOT FILES WINDOWS>adb sideload "C:\Users\MYPC\Desktop\Amazon Fire\update-kindle-global-37.5.4.2_user_542168620.bin"
.....You can make this easier on yourself by typing "adb sideload " and then drag-drop the v5.1.2 file into the command widow and the correct path will be automatically populated for you.
.....Click Enter, and allow the process to run its course
You should now be running v5.1.2 stock firmware, which is fully rootable. Next up is rooting and then installing CM 12.1.
I'll start reading up on rooting from THIS thread. I'll make a post with what I did after I have it working.

Rooting...
I watched THIS Root Junkys tutorial video for gaining root access. The Super Tool successfully installed KingRoot, but that application is unable to root this device. So what I did was grab the most recent (as of today: v4.9.5) from THIS thread. I renamed that file to Kingroot.apk and replaced the old version found in the Super Tool "apps" directory. I then went through the normal installation procedure and have gained root. To verify this I blocked OTB updates and disabled lock-screen advertisements.
Next up is installing CM 12.1.

Installing Unofficial Cyanogenmod v12.1 (7/10/2016):
I used Root Junkys Super Tool to install Google Play. The tool does eveything for you so there is no need to type out the steps. You can get that tool HERE
Once Google Play was installed, I linked an account and downloaded/installed the current version of FlashFire.
To install CM 12.1 I followed the instructions in THIS thread.
Next up is tweaking CM to my liking and getting the Play store installed.

I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?

Blastyrant said:
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Click to expand...
Click to collapse
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.

Davey126 said:
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Click to expand...
Click to collapse
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.

I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?

Blastyrant said:
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
Click to expand...
Click to collapse
Blastyrant said:
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Click to expand...
Click to collapse
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.

I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)

Davey126 said:
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
Click to expand...
Click to collapse
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!

Blastyrant said:
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Click to expand...
Click to collapse
Blastyrant said:
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Click to expand...
Click to collapse
Glad to hear all is well on both devices and that you are taking time to research and understand the 'why' behind the 'what' & 'how'. Makes the experience much more enjoyable IMO. Not to mention less error prone.
BTW - root procedures are identical for 5.1.1/5.1.2 but it's easy to think they are different reading through the hundreds of contributor posts, some with conflicting information.

I want to use Titanium Backup to backup/restore when it comes time to update CM 12.1. I downloaded it but it says "Root access: Failed". I then downloaded and installed Root Checker by Super User and it says I am rooted. It reports SU Found (/system/bin/su/system/xbin/su) and Busy Box is installed (/sbin, vendor/bin, /system/sbin, /system/bin, /system/xbin). I also ticked on Root access for apps in the Developer options of CM 12.1. I am assuming that I need SuperSU to provide root access to applications?
I installed SuperSU and on launch it asks to update the binary. This always fails. The link it provides takes me to http://supersu.com/insteadbinaryfile.html. It is here that I am getting confused.
Method 2: replace system/ Xbin with SU file, Steps : <-- Where to I obtain the SU file?
Step 1: Install Root.Explorer APK. <-- Is this the app by by Speed Software that cost $3.99?
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize Su (chmod 0777 .su) <-- I am unsure how to do this.
Step 5: delete the other SU files, such as ksu, etc. <-- etc means what exactly? What are the files I would need to delete?
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps <-- Which other authorization apps?
I feel like I am making something easy into something much harder. Any help would be greatly appreciated!

I uninstalled Titanium Backup and SuperSU. I then ticked off root for apps in developer settings, ticked it back on, and rebooted the device. Then I reinstalled SuperSU and this time clicked the "expert" button on first start. It installed and is working. Then I installed Titanium backup and that is also working. So looks like it was just an order of operations needed to solve my problem.

Revisiting this old thread. I am going to upgrade to the Fire Nexus ROM and post my steps.
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714