Database Users

[Guide?] Fixes to common Kindle Fire rooting problems

Not sure if this will help anyone, but I had a problem when rooting my new kindle fire 6.2.1
If you tried the Burrito Root method, I saw some few mistakes that I've done or didn't see in the video.
1. Updating the Kindle Drivers
I had previously rooted my android phone before, so when I plugged the kindle fire on my windows 7 laptop, I noticed that the windows was already indetifying it as an android phone, and had already labeled it for ADB. This auto-driver update thing might work for some people, but I find much better success replacing that driver that your computer identifies Kindle as, with the one that the BurritoRoot driver provides.
2. Getting the Kindle Root in the Listed Devices of ADB in command prompt.
This was probably the biggest issue I had when rooting the Kindle Fire. I was scratching my head, thinking why my Kindle Fire wasn't listed in the command prompt after typing "adb devices." I knew I did everything right from the beginning. Or so I thought?
One way I found that fixed that was downloading the Kindle Fire Utility v0.9.1
Unlucky for me, the download link was gone....
LUCKY for me, a fellow member here uploaded a mirror.
I somehow got it to work, with just luck but figured out the exact steps that seem to work for me (on Win 7 64 bit here).
1) Open up command prompt again, do the cd c:\KindleADB etc... upto the point where you typed in adb devices. you should be seeing no listed devices on the cmd (if you have that problem). LEAVE IT OPEN.
2) DOwnload the kindle fire utility, open the run.bat , it should have a message saying daemon started sucessfully, THEN QUICKLY FOLLOW THE NEXT STEP.
3) When the daemon started successfully message popped up on the KFU, go back to your CMD where you typed in adb devices and quickly type in "adb devices" again. it should say something like, killing out of date, starting daemon, and something about successful (Sorry if I'm not that much of a help, I tend to forget what the exact message said).
4) It should list the device. if not type it again.
5) Walla ! it should show a bunch of numbers, under listed devices.
3. Rooting the Kindle Fire in command prompt ERRORS
This wasn't much of a problem as it really was my mistake. I kept getting error messages when i typed in ADB ROOT in the command prompt during the BurritoRoot rooting method.
1) You have to make sure you have the BurritoRoot app installed in your kindle fire before starting the CMD adb root part. The app will tell you when to start typing away in CMD!
2) If you're doing the burritoroot method, you have to make sure you got all the names and directory right.
3) When you're doing the CMD adb root part, copy and paste it usually the best way to do it in CMD to avoid mistakes and erorrs! And no, you don't press CTRL+V in CMD. Rather, you right-click the CMD , then click paste (after copying the line you want to input).
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Notice all those commands above that you're suppose to type in (or copy and paste). The ones I bolded, people tend to make mistakes there. When you put those files you downloaded into KindleADB, PLEASE MAKE SURE IT IS NAMED com.noshufou.android.su-1.apk, otherwise when you get to the part
Code:
adb install [B]com.noshufou.android.su-1.apk[/B]
change it to :
adb install WHATEVER IT IS CALLED.apk that is Superuser.
The most important part is to push the SU file (that has no file extension).
I had my kindle rooted, with Superuser installed, but I couldn't get any pop-ups from Superuser asking permission for any apps! That is, until I found out I forgot to push the su file to /system/xbin/su and other steps to chmod it.
Anyways, I hope this helps anyone that goes through any problem like I did above. If not, sorry to waste your time! If you guys have any other problems, please leave a question below and perhaps I could or a fellow member here could help you.
Thanks again!

http://forum.xda-developers.com/showthread.php?t=1417234

Kindle fire stuck in TWRP 2.0 menu noob needs help. Im apologize...

Im sorry, I have tried everything to get my Kindle Fire up and running again. Ive read forum after forum trying to get it up and running. Ive tried the KFU the newest one and the older one. I tried to root my kindle fire and I some how got it stuck on TWRP 2.0. Here are the details of whats going on.
1. I am stuck on TWRP 2.0.
2. My PC does not recognize this device at all.
3. Ive tried deleting the drivers and re-installing the drivers.
4. None of the KFU devices see my KF on the pc.
5. I cant communicate with my KF device through ADB because the PC doesnt see anything.
6. I made the mistake of system restore through the OEM Amazon menu.
7. I dont have any custom roms on my KF device when I scroll through the TWRP menu.
8. I was a dummy and didnt backup the oem device version.
9. I cannot seem to push update.zip because there is no communication between my PC and the KF device.
10. The KF device is not even recognized for a quick second on my PC.
Any help would be greatly appreciated. I tried changing the INI file with the recommended numbers on the forum. Thanks for your time and thank you community in advances. I just wanted to get some better features on the device and i ended up paying the price. Once (i hope) it is restored I will never mess with the device again.

Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!

animefun135 said:
Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!
Click to expand...
Click to collapse
can you explain a bit more? i pressed mount in TWRP, and i dont see my fire appearing in "My Computer"
Thanks

in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440

b63 said:
in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440
Click to expand...
Click to collapse
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.

bradlier said:
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.
Click to expand...
Click to collapse
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything

b63 said:
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything
Click to expand...
Click to collapse
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..

bradlier said:
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..
Click to expand...
Click to collapse
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad

b63 said:
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad
Click to expand...
Click to collapse
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not

bradlier said:
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not
Click to expand...
Click to collapse
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot

b63 said:
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
sorry, but how do i do that?
command prompt? or something else?

bradlier said:
sorry, but how do i do that?
command prompt? or something else?
Click to expand...
Click to collapse
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands

b63 said:
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands
Click to expand...
Click to collapse
hey man that was it.. thanks alot

Thanks for all the help. My actual problem was the drivers needed to be reinstalled and the USB cable I was using was no good. Go Figure!

[Q] boot logo brick (?) [SOLVED]

i'm VERY new to all of this, and i promise i tried my hardest to find an answer in existing threads and google, but haven't found anything to help with my prob:
I tried (?) to root kindle fire [android police thingy], not sure if I succeeded or not (had a lot of "device not found" at the beginning) and tried to install RTL languages support at the same time.
I haven't installed any "TWRP" or "firefirefire" or anything like it.
after the reboot at the end of the RTL, the kindle got stuck on "kindle fire". I tried 20 second power button for several times, on and off power.
kindle fire utlity ("run") says:
adb status: online
adb rooted: no
boot status: 4000
when trying to root through this (temp root), i get: adbd cannot run as root in production builds.
I get the same phrase trying to do anything on the utiility.
Can I do anything to save this from being a 200$ coaster?
THANKS!

you can try to install fff and twrp with kfu (option 5)
then copy one of the prerooted stock images to sdcard:
http://forum.xda-developers.com/showthread.php?t=1402440
would recommend the secure one
and install with twrp:
http://forum.xda-developers.com/showpost.php?p=20543289&postcount=47

imageshack. us/photo/my-images/515/brickc.jpg/
(delete spaces)
i get about the same thing for every option i choose.
any other option?
(and THANK YOU for answering so quickly)

open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back

b63 said:
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
Click to expand...
Click to collapse
$ sign.. (waiting does nothing, "enter" produces yet another $ sign :X )

that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing

b63 said:
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
Click to expand...
Click to collapse
the kf is on 6.2.1 and the kfu is 0.9.2.
img521.imageshack .us/slideshow/webplayer.php?id=brick2m.jpg
(again, delete space)
on the first attempt with no. 5, it started downloading something but my internet went bad and the dl stayed on 52%. I manually downloaded the file and named it "recovery" (in the correct folder). after that, i got the message in "brick 3"
and another thing - even though i keep getting "adb rooted: no", after each time i "root", the device reboots, but it doesn't reboot after the "installation" of the twrp.

that with the recovery was right - it has to be recovery\recovery.img
the file should be ~10mb - maybe we have to do it manually
the problem is that burritoroot is allready installed and kfu can't gain root
you did not install burritoroot with kfu ? (kfu has a special version)
therefor we get the message "... can not run on production builds"
now we can look where the file is located and install with kfu or
install fff and twrp manually
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
second twrp manuell:
•copy recovery.img which you downloaded and renamed to the folder where adb.exe & fastboot.exe is located
•install with "fastboot -i 0x1949 boot recovery.img"
now we reboot into recovery:
•"fastboot -i 0x1949 oem idme bootmode 5001"
•"fastboot -i 0x1949 reboot"
now we should have the recovery system installed ...

b63 said:
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
Click to expand...
Click to collapse
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)

RYuval said:
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
Click to expand...
Click to collapse
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above

b63 said:
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
Click to expand...
Click to collapse
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )

RYuval said:
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
Click to expand...
Click to collapse
that's quite normal
what say your device manager about adb or kindle ?

b63 said:
that's quite normal
what say your device manager about adb or kindle ?
Click to expand...
Click to collapse
until recently, "adb android device" or something like that..
now it says the driver does not suit 64bit... (currently: unknown USB device)

it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
for information in device manager:
normal boot (4000) -> android composite adb interface
fastboot (4002) -> android adb interface

b63 said:
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
Click to expand...
Click to collapse
for some reason, that still doesn't work..
and the driver was properly installed earlier..

RYuval said:
for some reason, that still doesn't work..
and the driver was properly installed earlier..
Click to expand...
Click to collapse
for normal boot - have you ever been/worked in/with fastboot mode ?
we have to get the right drivers for every mode working
i just switched my kf to fastboot and return to normal boot to verify
try to update the driver manually (select manually)
alternately you can delete every driver with kindle or adb and then unplug and replug the kf
that' only a loose description that you see how it is done:
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay

will be updated (drivers installed.) the name's without "composite"

if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver

b63 said:
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
Click to expand...
Click to collapse
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..

RYuval said:
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
Click to expand...
Click to collapse
device not found on what command ?
your on an elevated command prompt (as administrator) ?
fastboot -i 0x1949 getvar product
it should return "kindle"

[Q] Kindle fire utility problems

Issue has been solved see last posts
For some reason when I run "KFU" it says windows cannot find tool/wget and when kfu loads up everything i click says it cannot find path specified. I have tried moving it to C:\ and using cmd... I have also tried earlier versions of kfu but to no avail. i found this http://forum.xda-developers.com/showthread.php?t=1473212 but nothing there helped I dont know what to do can someone please help me..
Sidenote, I have a kindle with 6.2.2 and im using windows 7.
I have rooted a kindle before with kfu and it worked almost flawlessly and that was around kfu 2...

espacially on win7 it seems to be be important to move and rename kfu that it is c:\kfu - it don't like spaces in pathname
check the tools folder of kfu - there should be wget.exe along with all other needed commands - it not -> redownload
i don't double click on run.bat - i use to open a (elevated) command prompt, cd to c:\kfu and enter run.bat
hope this helps ...

That is exactly what i have done it is in c:\kfu no spaces i have used cmd and typed exactly what you said before but when kfu loads it says "adb status offline""adb rooted no""boot status unknown"

I have also redownloaded it multiple times i tried the 9.2 kfu and patched it but that didnt works either i have even tried two different win7 computers and on the other win 7 i tried using kfu 8 but it said adb status offline

what does the device manager say under "android phone" ?
kf is in normal boot mode ?
allready tried a hard reset ? (holding pwr button ~20sec till it turns off - pwr on again)
some other ideas:
restarting adb on pc by issuing "adb kill-server" from the tools directory
checking with "adb devices"
check if you have c:\windows\system32 in your path ("path" at a command prompt)

android adb interface under android phone...
i hit normal boot manually power off and on the KF and the utility is stuck at waiting for device...
kill server goes through but list of devices shows nothing
and path on cmd shows up as c:\users\jamil>
i saw another post that said type set into cmd but that seems to not have done anything
thanks again for helping

this is what path shows
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jamil>path
PATH=C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bi
n\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System3
2\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-S
tatic
C:\Users\jamil>

Okay so i figured it out no when i right-click run.bat with admin rights it get the windows cant find tool.... but i noticed that when my other kindle gets connected it considers itself to be adb composite device when this one considers it self to be adb interface device or something like that i deleted both of the devices drivers and then i connected the one i am working with now and installed the drivers afterwards and voila... i got it too work thank you very much b63 for all the help

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I have done what he did and mine still gives the same error
its in C:\kfu

[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)

This how-to originally started out as a part of the Kindle Fire For Beginners (KFFB) guide, but evolved into this supplemental guide. Because of its origin, this guide assumes the reader is already familiar with KFFB, so reading it is a mandatory prerequisite. Users who post questions in this thread already covered in KFFB will be directed to go back and read it again.
My motives for writing this guide are very much in line with the reasons why I wrote KFFB. I'm hoping users will take the time to learn what they are doing and why they are doing it instead of crossing their fingers and hitting a button on an automated program. While I understand this is the more tedious route to their destination, the knowledge gained here can be used to get back on track when things go wrong or methods inevitably change over time.
The first post in this series details the process of rooting and installing a ROM on a stock device. The two share many of the same preliminary steps, so it makes sense to go over both at the same time.
Preparations
Again, please read Kindle Fire For Beginners before continuing. The conventions introduced in KFFB (e.g. having KFU installed in "C:\kfu") will continue to be used here. Make sure the battery is fully charged. A drained battery is not something you'll ever want to encounter and especially not while in the middle of this process. Create a new folder "C:\kfu\software" on your hard drive. Downloaded software to be installed on the Kindle Fire will be moved there.
Download and install WinMD5Free to some place on your Computer. The developers for most of the software you'll download for the Kindle Fire will provide an MD5 checksum. The checksum is used to verify the integrity of downloaded file, so you can be sure that you haven't gotten a bad download or a corrupted file. Tell WinMD5Free what file you want to check and compare the calculated checksum with the one provided by the developer. If the two match, you can be confident about installing it on your Kindle Fire.
For all required software listed in this document...
Extract (unzip) the files from the compressed archive (unless otherwise noted)
Verify the MD5 checksums if they have been provided
Move them to the C:\kfu\software folder
As with any other how-to guide, it's always a good idea to just read through the document first to get a basic idea of the process involved. Once you are comfortable with the concepts, then go back through and actually perform the steps required.
Getting to fastboot mode
The first step to modifying the Kindle Fire is to get the device into fastboot mode. The easiest and safest way to do this on a stock device is to use a factory cable. The factory cable is safe because it does not require the bootmode to be changed on the device. If something unexpected happens, you'll be able to disconnect the factory cable and reboot straight back into the stock software.
If you choose not to use a factory cable and change the bootmode to get into fastboot mode, you'll be taking a small gamble that you'll be able to issue fastboot commands to the device and change the bootmode back to normal. If you cannot change the bootmode back for some reason (e.g. your device drivers for fastboot mode fail to recognize the device), the device will be stuck in fastboot mode until you find a way to do so. In nearly every case, if you are able to issue the adb commands to get into fastboot mode, you should be able to send the fastboot commands necessary to get out of it. This is just a fair warning out of an abundance of caution... make sure you've done everything to ensure the ADB device drivers have been installed properly.
If you have a factory cable, you can turn the Kindle Fire off and connect the cable to the device, then the computer. The Kindle Fire will power up and put you directly into fastboot mode. You can then skip the rest of this section and go directly to flashing a recovery and bootloader. Otherwise...
Required software:
pokey9000's fbmode​
1) Boot up the Kindle Fire normally and connect a USB cable to the device and computer.
2) Copy pokey9000's fbmode program into a user writeable location on the Kindle Fire...
Code:
adb push C:\kfu\software\fbmode /data/local/tmp/
3) Change the permissions on the fbmode program so it can be executed (run) on the device...
Code:
adb shell chmod 755 /data/local/tmp/fbmode
4) Execute (run) the fbmode program to change the bootmode to fastboot...
Code:
adb shell /data/local/tmp/fbmode
5) Reboot the device...
Code:
adb reboot
Note: In case you are wondering why the "adb shell idme bootmode 4002" command previously discussed in KFFB was not used here, that command requires root privileges not available in the stock configuration. Without root privileges, the above workaround is required.
Installing a recovery and custom bootloader
Required software:
FIREFIREFIRE bootloader
TeamWin Recovery Project (TWRP) recovery
Note: Do not extract the contents of the FIREFIREFIRE bootloader zip file. It will be flashed as-is with TWRP recovery.​
1) Install the TWRP recovery...
Code:
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
2) Set the bootmode to recovery (5001)...
Code:
fastboot -i 0x1949 oem idme bootmode 5001
3) Reboot the device into TWRP recovery. If you used a factory cable to get into fastboot mode, turn off the device by holding down the power button for about 20 seconds. Replace the factory cable with a generic USB cable and the device will start up again automatically. Otherwise...
Code:
fastboot -i 0x1949 reboot
4) Copy the FIREFIREFIRE bootloader zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
5) From the main menu of TWRP, press the "Install" button to flash the FFF bootloader onto the bootloader partition. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
6) Optional: Make a nandroid backup of the stock software. From the main menu of TWRP, press the "Backup" button and then "Swipe to Back Up" to create a snapshot of the stock system. If you change your mind later about rooting or have second thoughts about the ROM, just "Restore" the backup and return to the stock configuration.
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.​
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Installing a custom ROM
It should go without saying, but users who intend on staying with a rooted stock device need to skip this section. Flashing a custom ROM will overwrite the stock software and leave no trace of the original Kindle Fire interface.
Required software:
Any ROM you choose to install. Check the KF Development List as a starting point.
Note: Do not extract the contents of the ROM archive. The recovery program will need the actual zip file to install.​
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!
Cleaning up
The zip files pushed onto the /sdcard during installation are only necessary during the installation process and do not need to take up space on the device after completing the install. Use a file manager or mount the storage device on the host computer to delete the files and reclaim the used space.
Coming soon...?
I've got some other topics in mind, but like I did with the KFFB, I'll see how users respond to this post before I continue. Please feel free to comment and make suggestions. I may not respond to everything, but I will keep the helpful comments in mind if/when I decide to expand this how-to guide. Thanks for reading.
Credits
jcase - For providing the basis for this guide and lending his expertise in rooting devices
pokey9000 - For his work on FFF and providing the fbmode exploit
TeamWin and Dees_Troy - For providing the TWRP recovery and continuing its development
ChainsDD - For the Superuser package​

Unroot or Revert to Stock Software
This second post in the series details the procedures required to undo the steps taken in the first. Use it to unroot or revert back to the stock software like it just came from the factory. If you tried out the rooted stock software or a custom ROM for a while, but just prefer the no-frills stock software, you've come to the right place.
Unrooting the stock software
Required software:
None​
This section assumes the device is already booted into the system software.
1) Uninstall the Superuser app
Code:
adb uninstall com.noshufou.android.su
2) Optional: Set the bootmode to recovery. Alternatively, use the recovery selection feature in FFF to boot into recovery during startup without manipulating the bootmode setting here. If you are more comfortable setting the bootmode directly...
Code:
adb shell su -c 'idme bootmode 5001'
3) Reboot the device into recovery...
Code:
adb reboot
4) Mount the data partition...
Code:
adb shell mount data
5) Optional: Delete the files that the Superuser app left behind...
Code:
adb shell rm -rf /data/data/com.noshufou.android.su
6) Mount the system partition...
Code:
adb shell mount system
7) Re-enable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted.bak /system/bin/check_rooted
8) Delete the su binary from the device...
Code:
adb shell rm /system/xbin/su
9) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have unrooted the stock Kindle Fire software!
Reverting to stock software
Required software:
Amazon Kindle Fire Software Update​
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
2) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
3) From the main menu of TWRP, press the "Install" button to flash the stock software onto your device. Navigate to the /sdcard directory on the left and select the "update.zip" file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
4) Optional: From the main menu of TWRP, "Wipe -> SD Card" to remove all files on the USB mountable storage space. This step will permanently delete all of the files that appear on a computer when the device is connected as a USB storage device.
5) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have reverted the device to a completely stock Kindle Fire!

KFFB Supplement Post #3
Reserved...

Great explanations!
I wanted to thank you for explaining everything clearly so that people can understand what they are doing when installing their bootloader, recovery and new ROMs.
Thanks again... plee3

Thanks so much!
This worked flawlessly. I had gotten stuck trying to root with KFU (I think the driver is slightly funky in fastboot - so KFU failed to flash either recovery or bootloader and left me in fastboot mode) but using the '-i 0x1949' option with fastboot made everything work perfectly.

Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers

Thibor69 said:
Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers
Click to expand...
Click to collapse
I know, right?

can i follow this to root 6.3.1?

xXezmacXx said:
can i follow this to root 6.3.1?
Click to expand...
Click to collapse
Yes, it's been tested to work from 6.2.0 and up.

Needs Sticky
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.

Thanks to all. I'm glad some of the readers got some use out of it.
Docs009 said:
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
If you think this guide will be useful to other users here, you can ask the moderators to review the thread and possibly make it a sticky. I would ask, but it seems a bit... uncouth to nominate my own post for sticky status.
Thanks for reading!

Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.

ExploreMN said:
Well, I followed the instructions. Got as far as "adb shell reboot" after the fbmode command. Now it just sits at "kindle fire" and shows up as an unknown device in device manager.
Is there anyway to recover from this or did I just junk my fire?
Click to expand...
Click to collapse
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

kinfauns said:
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Thanks Kinfauns. I actually got it fixed without even reading about it...I get a little medieval on things that frustrate me and eventually got it figured out...I edited my post to warn people about what tripped me up!

ExploreMN said:
Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.
Click to expand...
Click to collapse
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU. Any how-to guide has to make some set of assumptions and I made the assumption that you'd actually follow the previous set of instructions before proceeding onto the next. I think you'd agree that I cannot possibly account for every possible deviation a user might take away from my actual directions. If I even attempted such a thing, this guide would turn into Encyclopedia Britannica.
In addition, I also gave you ample warning about putting your device into fastboot mode by manipulating the bootmode. I made a clear suggestion for you to get a factory cable and use it to get into fastboot mode the "safe" way. I've never seen any other rooting guide/utility even make mention of this possibility, so I've gone above and beyond what you'd get anywhere else.
With those things together, I believe I've done the very best I can to minimize the possibility that you might get stuck and have to "get a little medieval" on your device. Regardless, I'm glad you got it figured out. Good luck with the rest of it.

kinfauns said:
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU.
Click to expand...
Click to collapse
True enough. Just didn't think it would keep reloading the drivers from the SDK if the SDK was in the path for Eclipse. I'm guessing anyone who set up Eclipse would not think this is an issue and might get stuck like I did...so it's still worth mentioning. (to me at least)

The second installment of this how-to guide has been posted. Included are instructions on unrooting and reverting back to the stock software. Suggestions and comments are always appreciated. Thanks!

Thank you for the excellent guide.
For what it's worth, this guide is very helpful for the admitted "noob" who has somehow failed with a utility like KFU and needs to go back and work through the pieces step by step. Thank you for laying out an instruction manual with enough detail to not only do the steps needed - but also to begin to understand what I'm doing.
I've rooted my KF (thanks to your assistance) so that I could install Swype. I then was able to use OTA-Rootkeeper to "hide" my SU file so that I can use Amazon media on my Fire as I want to, but still get the benefits I wanted from a rooted device (primarily the use of the Android Market, "Google Play", and the use of Swype).
For those that don't *really* want to unroot but do want to still use the Amazon content tools, I HIGHLY recommend the OTA-Rootkeeper utility.
Thanks again!

Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Download the latest zip for Gingerbread/ICS (the filename should end in "efghi-signed.zip"). Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Click to expand...
Click to collapse

DuendePaladino said:
Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Click to expand...
Click to collapse
If you used that script in Firekit, you should have FFF 1.2 and TWRP 2.0.0 installed, so technically, yes.... you can boot into TWRP and start following those directions. However, I would recommend that you upgrade your bootloader and recovery to the versions I have in the previous section... FFF 1.4a and TWRP 2.1.1. I won't go into all the reasons why, but they are "better" and likely to keep you out of trouble in the future. Since you already have FFF installed, it will be easy for you to get into fastboot mode. Once you are in fastboot mode, start with flashing TWRP and continue on from there.