Database Users

[Q] I just can seem to unbrick my Fire.

I used kindle fire utility 7 and installed twrp. My kindle is version 6.2.1 and now when i turn it on its just the triangle with fire. I press the power button to go into recovery mode like it says at the bottom but that does nothing. Oh and my computer doesnt recognize the device! I notices somethings plugged it (3 tone sounds) and thats it. In device manager it's just labeled as "USB device". Iv'e tried just about everything i can find online,but the kindle fire utility just says "waiting for device" no matter what. Can someone please help me with this issue? Its a brand new kindle i literally got 2 days ago and would really like it back to normal
Thanks!

Manually re-install the ADB drivers by going into Device Manager, clicking on "Unknown Device" or "kindle" or whatever it's called, and manually selecting the "Android ADB Composite Interface" from the list of drivers rather than having Windows automatically search for it.
Then, go back to the Kindle Fire Utility and re-install TWRP.
If you want to get rid of root and TWRP afterwards, use the KFU to download the stock update.zip, and flash it using TWRP. That'll get rid of everything and restore the Fire to its original state.

It only has "Android phone". When i click it it asks me to browse a folder for the driver. I dont know what folder to pick. I tried then android programs files folder but nothing.

What exactly do you mean by "Android phone"? Is the ADB interface installed, or is it just listed as "Unknown Device?"

It is listed as "USB device" but the ADB is installed.

Try clicking on "Have Disk" in that last screen and specifying "C:\Program Files\Android\android-sdk\extras\google\usb_driver" or something to that effect as the file path.
You need to give it the path where the file "android_winusb.inf" is stored.

It just says that the path specified doesn't contain information about your hardware.

[Q] Kindle has been wiped in TWRP and Windows only displays device as Unkown

My nephew managed to get into TWRP and somehow wiped the entire thing clean. I purposely keep a recovery .zip in there but even that's gone. When the Kindle is turned on it displays the Fire triangle but then the screen goes black and stays like that. I can boot into TWRP but can't use the mount option or adb because my computer, and the three others I've tried, refuses to recognize the Kindle. It shows up in Device Manager as Unknown and I can't manually install the driver. I've tried every combination of booting it with the computer off or on, uninstalling the Unknown driver, everything. Can you kind folks please save my butt? Thanks in advance for your responses.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Have you tried starting adb services and going back through the FireFireFire Utility, this has fixed a lot of boot errors that I had in the pass?
Let me know if you need help with starting adb services.
Thanks,
JohninLex

Thanks for your reply
Can you please elaborate on this a bit more? Maybe I'm not understanding correctly but I thought starting adb services wouldn't do anything in this instance since it wouldn't recognize the Kindle as being there at all? For instance, when I run Kindle Fire Utility it shows adb devices as being offline. If I could get the Kindle to show up as anything other than Unknown I'm certain I could just update the driver to an android device and have KFU take it over from there.

wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Did you root your Kindle "adb devices"
and the following commands?
adb shell chmod 777 /data/local/tmp
adb install Burritoroot3.apk
or did you download a file from the market to get root?
if you did it the above way with adb commands from a terminal would be great.
Either way lets set the driver, download the Kindle Fire Utility extract it to your desktop. or take note where you extracted it. Then go to your device manager and right click on the Kindle (unknown device) look for update driver and browse the the Kindle Fire Utility folder double click on the drivers folder and let it update the right driver you need for your OS (XP,Vista, 7 x86 or 64). Once it finds the right driver Open up a command prompt by going to start run and typing cmd and hitting enter. Once that is done download the KindleADB files and place them in the C:\ (drag and drop should be fine here ) go back to your command prompt and do the following commands:
** urname** C:\ " cd KindleADB " then hit enter
and then do " adb devices " it may or may not come back with your device sn but as long as it has started is what we are looking for.
Once that is done go back to your desktop leaving everything open and look through the Kindle Fire Utility until you find a file named Run.bat double click and hit run this will reinstall twrp and allow it to be remount-able. If you need a stock Kindle rom with update 6.2.2 I have a back up I can share with you.
I hope this helps but if it does not let me know and we can go back over the the driver section.
Thanks,
JohninLex

I've attempted installing the driver manually many times like you stated and on different PCs all containing KFU and the modified .ini file in the .android folder and the message I get when I attempt to manually update the driver is "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems." When I first got the message I attempted to do it in an x86 system and the driver would still not install. My inability to get ANY computer to read the kindle as anything other than Unknown is the main issue. Even if I could make it read as the default "kindle" with the exclamation point it would be enough for me to fix it. But if I can't get a driver to load I'm hopeless to fix it in any way.

Use Android composite driver on your PC to get adb working. Once the adb is working, there multiple ways to boot or install a new ROM. I recommend to start doing the following commands:
Fastboot mode.
Try these ADB commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Ng you have an Android phone, connect to you PC first to see if adb is working using composite ad driver for Windows operating system
Sent from my Amazon Kindle Fire using Tapatalk

I can't use android composite driver. Every time I attempt to install the driver manually I get the error listed above. No matter what I do I can't get the Kindle to be anything other than Unknown

i had a problem where i could only get the fire symbol screen computer would not recognize. I had to start the kindle fire utility plug my kindle into the computer then turn it off, then have kfu install latest twrp again when it says waiting for device turn device on and it will reinstall that and get you back to the recovery. so maybe you can do the same with obtain stock update. not really sure to the kindle. my computer would recognize kindle fire for a few seconds and thats how i could install new twrp

about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
if you can't get rid of the drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
nevertheless i would never install the original stock rom cause you loose fff,twrp and root
use one of the prerooted stock roms instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20

I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck

Help me save my kindle fire
I used KFU to install TWRP and up to CM9. But after that i restore to rom stock 6.2.
But after kindle start the error sorry loop in screen . I can not access to kindle.
process.android.acore force close
We try to connect and re install TWRP but not successfull. when i connect kindle to my pc (XP and window 7) it only recognize kindle as disk driver (athough i try to uninstall and setup manual driver )..
Help me urgent.
Thanks alot

http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

mhb1509 said:
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Click to expand...
Click to collapse
This comment gave a ton of hope since I have tried everything that has been mentioned already except for adding 0x006 but sadly it did not work. There's absolutely nothing I can do to get out of the Unknown state. I've never had my ass kicked this hard by a piece of hardware. I surrender.

maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038

b63 said:
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
I was reading through that earlier and it was a little too intimidating. I'm just going to sit here and cry for a couple of minutes.

Kindle still recognize as disk driver
I try to do something but adb not working (device not found because it recognize as normal disk driver). My pc use window xp professional.
How can i solve this

My kindle still recognize as normal disk driver
I try to test on some computers (xp, win7) but unfortunately, my kindle still recognize as normal usb only. (not adb device).
So i don know how to fix this problem
Please help me, or give me a hint

xp is a good choice - you don't have to care about the uac (user acces control)
have you checked according to my post #12 above ?
to shorten things up i could take a look with teamviewer if you like
just gimme a pm ...

Have you added the second vendor and the second set of USB command lines in your google/extras folder? If not add those turn off the kindle then turn it back on do "fastboot devices" then put the update.zip in your platform-tools folder then push the update to your kindle to be flashed by twrp. The command for that would be "advt push update.zip /sdcard/update.zip" you can have the kindle already in twrp by this point. Also when all is over you will have to reroot and reinstall fff and twrp. If you need help send me a message.
Sent from my Kindle Fire using Tapatalk

Hard reset on main-board KF
My KF is frozen. I try to do hard reset by hold pw button 20s, but not effected.
So i've just open back-slide my KF, and see KF main-board.
Have hard reset trick on this main-board.
Help me please.

[GUIDE] Kindle Fire For Beginners

What is this guide?
This guide is aimed at the novice Kindle Fire owner who wants more out of their device, but has been overwhelmed by all the jargon and maze of directions on what to do and how to do it. I've read through many of the threads here and I've noticed one common problem. While user-friendly tools like Kindle Fire Utility (KFU) have managed to help countless owners modify their devices, there are still a significant percentage of users who have stumbled along the way. KFU is a great utility, but because it gets the user up and running without teaching them first how to walk, any mishap results in confusion, frustration and another post on the forum asking the same old questions. My hope is this guide will provide the novice users with a general overview, some basic knowledge, and a foundation to help them seek out the answers they need without rehashing topics that have been discussed numerous times. This is not a copy-and-paste how-to guide. I've intentionally left out any commands so the reader is not tempted to fall into the same traps I'm trying to help avoid. If this is your first time with this guide, I suggest that it be read from top to bottom because the document builds upon the knowledge from the previous sections to explain the next.
What is stock? What is rooting? What is a ROM?
Stock is how the Kindle Fire was shipped to you. The term is used interchangeably to describe the original operating system loaded at the factory and the general state of your Kindle Fire. If you've done nothing more than use your Kindle Fire in the Amazon approved way (browsing, reading eBooks, using apps from the Amazon AppStore, etc.), you are running the stock software on a stock device.
The first step outside of this stock state is to root the device. With a stock device, you are using it as a standard user and not an administrator. You have no real administrative privileges and it can only be used as Amazon intended for it to be used. Just as a Windows or Mac OS based computer can be configured to prevent the standard user account from installing new software or performing other low-level tasks, the same is true of the Kindle Fire. Whether this is to protect the user from doing harmful things or locking the device down to Amazon services is a matter of perspective. However, if you want to get outside the confining box of the stock software, you will need root privileges. The process of obtaining these administrative privileges is called rooting. If you like the standard Kindle Fire user interface, but you want some other minor enhancements, rooting may be sufficient for your needs. However, there are tradeoffs for obtaining root privileges on a stock device. While you'll be able to do things like installing apps from the Android Market (now Google Play), Amazon may block services like video streaming to a rooted device. In addition, rooting officially voids the warranty on the Kindle Fire.
The more adventurous user might want to ditch the standard Kindle Fire user interface altogether and install a 3rd party ROM. Also known as flashing, installing a ROM completely replaces the stock Amazon software in favor of an entirely different operating system. This provides a brand new user experience and puts you squarely in the driver's seat of the device, controlling what you use and how you use it. A new ROM will also provide additional features not available or possible in the stock or rooted stock configuration, but you'll have to give up Amazon's Kindle Fire services altogether. Needless to say, installing a ROM officially voids the warranty on the device.
What is a bootloader? What is a recovery?
A bootloader is the first piece of software loaded onto the Kindle Fire when it is powered on or rebooted. In a nutshell, the bootloader is responsible for setting the basic hardware configuration for the device before it hands off control to an operating system. For a stock device, when the "kindle fire" logo first pops up on the display, that's the bootloader doing its job and subsequently telling the Kindle Fire operating system to begin loading. Because the stock bootloader is so limited in its function, an alternative bootloader, FIREFIREFIRE, has been developed to provide some additional functionality. One of these features is easy access to recovery... which leads us to the next question and answer.
A recovery is a mini operating system that allows the user to perform ROM installations, backups, restores, wipes, and other maintenance tasks. For Kindle Fire users, there are two choices for recovery, Team Win Recovery Project (TWRP) and ClockworkMod Recovery (CWMR). Both provide a touch interface to mostly the same set of features, but TWRP seems to be the more popular of the two. Either one will work just fine and will be the go-to spot for flashing a 3rd party ROM. If the installed operating system is malfunctioning or you just want to try something else out for a while, you can use the recovery to backup the current ROM and flash a new one. If you change your mind at a later date, you can also use it to restore a saved backup.
What is fastboot? What is adb?
Fastboot and ADB (Android Debug Bridge) are command line tools for your computer that allow for direct interaction with the device. They are both available for Windows, Mac OS X and Linux.
The 8 GB of storage space on the Kindle Fire is divided up into predefined sections called partitions. The bootloader, recovery and operating system have their own specific partitions. The primary function of fastboot is to flash or erase these partitions on the device. For example, fastboot can be used to flash FIREFIREFIRE or TWRP onto their respective partitions. Because each of these parts has their own particular partition, fastboot can flash or erase them without affecting another. One thing to keep in mind is that while the term fastboot most commonly refers to the command line tool, it can also refer to a particular mode on the Kindle Fire used to accept fastboot commands. Essentially, the Kindle Fire must be in fastboot mode for the computer to send fastboot commands to it.
ADB, on the other hand, primarily deals with file level interactions like copying a file to and from the device. However, ADB's most powerful feature is its ability to start a linux shell and execute some powerful commands directly on the device. The types of shell commands and their usage are outside the scope of this document, but most users won't be utilizing them anyway. Most commonly, adb is involved in the process of rooting the device or preparing it to flash a 3rd party ROM, then mostly unused after the process is complete.
The fastboot and adb commands require the Kindle Fire to be in specific states for the host computer to interact with the device. The fastboot tool needs the Kindle Fire to be in fastboot mode and cannot send commands to the device otherwise. Similarly, the Kindle Fire must be in recovery or booted to an operating system (with USB debugging enabled) for it to work with the adb tool. It's not possible to go back and forth between the two without at least rebooting the device.
What is a bootmode? What is a bootloop?
As the Kindle Fire powers up or reboots, the bootloader begins to do its job and checks for the bootmode of the device. The bootmode tells the bootloader how it should proceed in the boot up process. Most users will just be concerned about three of these bootmodes: normal (4000), fastboot (4002), and recovery (5001). In a great majority of the cases, the Kindle Fire will be in the normal bootmode setting, telling the bootloader to continue right on to booting the operating system. However, there are circumstances when the device needs to be started up directly in fastboot or recovery mode. This is possible by changing the bootmode setting and rebooting the device. Bootmode is a persistent setting, meaning the Kindle Fire will remember this new setting until it is changed again. No amount of restarts or ROM flashes will change the bootmode until it is explicitly changed again. This is a very important fact to remember because it's the cause of so many help requests...
A bootloop is essentially the device booting directly into fastboot or recovery mode on every start up because the bootmode has been set to that particular setting. The posts on the forum describing problems like, "stuck on the yellow triangle" or "keeps going into recovery" are in most cases caused by the bootmode setting. Technically, the device isn't doing anything wrong since it's been told by the bootmode to boot in those modes, but if the user doesn't know about the bootmode or how to set it back, it appears to be broken. The bootmode just needs to be set back to normal using fastboot or adb (KFU uses them behind the scenes to do the same), and the device can be rebooted to the operating system.
What is a brick (hard-brick / soft-brick / unbrick)?
In the strictest sense, a brick is an irreversibly broken device and about as useful as a masonry brick, hence the name. However, this slang term has come to include any malfunctioning device, so we have slightly more descriptive terms like hard-brick or soft-brick to indicate the degree of malfunction or difficulty of repair. To unbrick a brick just means to get the device back to working order.
With respect to the Kindle Fire, it's very difficult to completely brick the device unless physical damage or component malfunction is involved. In all software related bricking circumstances, the malfunctioning device can be unbricked. In 99% of the cases, you can fix it yourself with just a computer and a USB cable (maybe 2 cables, but more on this later). Only in the other 1% of the cases that involve a broken bootloader will you need more extreme measures. Unless you've dropped your Kindle Fire into the bathtub or tossed it off a building, everything will be OK. Take a deep breath, don't panic and keep reading.
How do I unbrick my Kindle Fire?
Let's get the bootloop brick out of the way first. This shouldn't even be considered a brick by definition since the Kindle Fire is actually functioning correctly and working as expected. Regardless, it gets thrown into the realm of bricks, so it's here as well. As noted in a previous section, just getting adb or fastboot to set the bootmode back to normal will fix it. That is unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it's actually a brick at that point.
Most bricks will involve a malfunctioning operating system. These are typically caused by a bad flash or accidentally renaming / removing key components of the operating system. Most of these are probably with the rooted stock Kindle Fire software since these devices are the least likely to have a recovery installed.
The one word most often used in unbricking strategies is fastboot. If fastboot commands can be issued to the Kindle Fire, it's 80% fixed and the hard part is over. All that needs to be done then is to flash a new bootloader and recovery, reboot the device into recovery, flash a new ROM, and it's fixed. Everything else involves the question of how get the Kindle Fire into fastboot mode in the first place. Because the bootloader enables fastboot mode on the device, it plays a key role in the unbricking process and dictates what needs to be done. We'll go from easy to difficult.
With the FIREFIREFIRE (FFF) bootloader installed on the Kindle Fire, a yellow triangle logo (versions 0.9 to 1.2), a kindle fire with android logo (version 1.3) or a white and blue kindle fire logo (version 1.4 and beyond) will appear on the display as the device boots up. If you have FFF installed and running, you already have easy access to fastboot mode because FFF temporarily enables fastboot mode for a short period of time as the device boots up. Send the device a quick fastboot command during this time and it will stay in fastboot mode until it's rebooted again. For just the temporary fastboot mode alone, FFF is worth the price of admission. Even if you never install a recovery and the device will only run the stock Kindle Fire software, the temporarily fastboot will save you from a bad headache if the operating system should ever go bad.
With the stock bootloader, the standard kindle fire logo will appear on the display as the device boots up. Unlike FFF, this bootloader does not have a temporary fastboot mode, so the bootmode on the device must be manually set to fastboot mode (4002) and rebooted. To set the bootmode on a stock device, adb shell commands must be executable on the system. Because unbricking typically means attempting to replace a broken operating system, the chances of getting it done this way aren't so good. Remember FFF from the previous paragraph? This is why FFF and temporary fastboot mode is like a golden ticket to unbricking, a close second to having a factory cable...
With the stock bootloader and a broken system unable to change bootmodes, a factory cable is required. A factory cable is a special USB cable able to force the device into fastboot mode. If the bootloader is working properly, the factory cable can get the device into fastboot mode without any additional help. Anyone handy enough with a soldering iron can modify a generic USB cable with a micro connector into a factory cable. Pre-made cables are also available for purchase in various places or from an XDA member for a reasonable price. With the Kindle Fire off, plug the factory cable into the USB port of the device and then the computer. The Kindle Fire will then boot up in fastboot mode. The factory cable works with either the stock or FFF bootloaders and it's a worthwhile safety net to have around. With a factory cable, unbricking just comes down to "plug it in and flash new stuff" in almost every bricking situation, except the next one...
For the unfortunate owner of a Kindle Fire with a bad bootloader, it's the worst case scenario. Without a working bootloader, the device cannot enable fastboot mode and nothing else can be loaded onto the device. Tinkering with the bootloader partition can certainly put the device at risk, but even this problem can be fixed with some surgery. Firekit offers a set of software and scripts that allows the bootloader to be loaded via USB. However, the Kindle Fire case must first be opened up to short a circuit that enables this USB boot option. Fortunately, the situation rarely comes up and careful flashing of the bootloader partition will minimize the possibility of it affecting the device.
What next?
To all readers - If you've read this far, please provide some feedback on this guide. I'd like to know if you feel it's a useful starting point for beginners and how you think it might be improved. Again, this guide is only meant to be used to build up a new user's knowledge base, so I don't intend to provide step-by-step instructions for these tasks... the guide is already long enough as it is. Otherwise, I'd like to hear what you have to say and perhaps I'll try writing some expanded tutorials in the future.
To the novice user - If you are having problems with your device, look for threads discussing similar problems. Odds are that you are not the first to encounter your specific problem and it's likely to have been discussed already. As a general word of advice... people here (and any other forum in general) are more willing to help you if you've tried to help yourself first. Try reading and searching for things on this forum. There's a lot here… I know. Take your time and digest the information. Hopefully, the base knowledge you've gathered from this guide will help you to understand the discussions. Then if you hit a wall and just can't get anywhere, write your post detailing the problem, things you've tried and what happened as a result. A post that says "It's broken, help me" will get ignored while "I've tried A, B, C and get X, Y, Z... can someone suggest an alternative?" will get a flood of responses. Good luck!

Windows Device Drivers and the Device Manager
Will you be writing more guides?
Thanks to everyone who read my first guide and had so many kind words to say. I sincerely appreciate the posts and decided to continue on with the series with what I feel is the greatest stumbling block for new users using the Windows OS... device drivers. Each day brings another group of users with broken devices and many don't even know if their drivers are loading correctly. I'm hoping to fill the gap with this installment of my guides. I've deviated from the style of the first post and made this more of a step-by-step tutorial rather than a general information guide. If you have not read the first post, I strongly urge you to back up and go through that before continuing.
I want to offer a special thanks to b63, a tireless champion of the lost souls who come here seeking help. Some of the information in this guide have been borrowed from his helpful posts.
What are drivers?
Device drivers are specialized software programs necessary for the Operating System to interface and interact with hardware devices. Simply put, every attached piece of hardware needs a corresponding device driver for the computer to be able to talk to the device. Common peripherals like keyboards, mice, and thumb drives have generic drivers built into the OS, so the user need not worry about them (in most cases). However, other devices may need specific drivers to be installed by the user onto the host computer. If the OS cannot find or load up the proper drivers for the device, programs relying on the device drivers will not function properly.
With respect to the Kindle Fire, ADB drivers must be installed and functioning for fastboot and adb to send commands to the device. For users doing anything other than using the KF in the stock configuration, installing the ADB drivers will be the first step in modifying the device or troubleshooting problems. Proper installation is a crucial step and must be completed successfully before anything else can be done. Neither fastboot nor adb will be able to issue commands to the Kindle Fire without these drivers. Using Kindle Fire Utility provides no exemption because KFU uses fastboot and adb in the background to complete its tasks.
Do yourself a favor and make sure the ADB drivers get installed correctly and test them while the Kindle Fire is fully functional. Trying to get driver issues resolved when the Kindle Fire is malfunctioning just complicates matters and makes the job that much more difficult.
How do I install the ADB drivers?
The ADB drivers can be found in the Android Software Development Kit (SDK) provided by Google. Android developers use the SDK to build software for all sorts of Android devices. If you have an interest in Android development, you might want to go this route, but you will have to edit some configuration files with Kindle Fire specific information. However, the SDK method is probably overkill for most users here.
By far, the easiest and best method of installing ADB drivers on a Windows OS based machine is to use the installer provided in the Kindle Fire Utility distribution. Find the latest version and download it to your computer. The distribution is in the form of a ZIP archive, so the contents will have to be extracted before the files can be used. You can extract the files to any place on your hard drive, but the rest of the directions here will assume they have been placed in the "C:\kfu" folder. To do that...
Right click on the downloaded file and select "Extract All..." from the menu
Type "C:" into the box and press the "Extract" button
Windows should open a window to the C: drive after extraction
Rename the "Kindle Fire Utility" folder to "kfu"
Now the KFU files should be located in the "C:\kfu" folder. Open up the folder and you'll see an "install_drivers.bat" file among the contents. Windows may hide the ".bat" portion of the name, so it might just look like "install_drivers" in the folder. Disconnect the Kindle Fire from the computer (highly recommended) and then run the "install_drivers.bat" batch file. The installer will automatically check for the OS type (32 or 64 bit), and then install the appropriate drivers and configuration files.
Don't worry too much about Windows not being able to verify the publisher of the drivers. The warning is there because the drivers have been repackaged for use in KFU and have not been signed. It's OK to just install the driver software anyway. If Windows refuses to install unsigned drivers, that feature must be disabled before continuing. The process differs for various Windows releases, so search Google and find a suitable method for your system.
International users may have to change the language code in the "C:\kfu\drivers\dpinst.xml" file before installing. For example, German users should open the file with WordPad and change the "0x409" (English) to "0x407" (German).
How can I verify the drivers are loading?
The Windows Device Manager is the key to determining the status of all the computer's devices and drivers. Right click on the "Computer" wherever you can find it (the Start menu, the Windows Explorer, etc.), select "Manage" from the menu and the "Computer Management" program will start up. From the left panel, select "Device Manager" in the "System Tools" category and the large pane in the middle will show a list of device types. Click on the triangle (or plus sign) next to a device type and a list will expand to show all the devices of that particular type.
Now, connect the Kindle Fire to the computer and keep an eye on the device list. Windows will give some device detection beeps and the list will refresh with one of the following items. Refer to the table below…
{
"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"
}
Before getting into the meaning of the table above, a small detail must first be covered. For adb to interact with the Kindle Fire, it must first have the "USB debugging" feature enabled. Without this feature, Windows will not even attempt to load the appropriate driver. The stock Kindle Fire software has this feature turned on at all times, but other ROMs must have "Settings -> Applications -> Development -> USB debugging" enabled. The rest of this document assumes normal mode has USB debugging enabled.
Getting back to the table above, notice the following:
Top row: the device is in fastboot mode. Bottom row: the device is in recovery or normal mode
Left column: the ADB driver has not loaded. Right column: the ADB driver has loaded
When the ADB driver has not loaded, the letter 'K' in Kindle is in uppercase for recovery or normal mode, but in lowercase for fastboot mode
When the ADB driver has loaded, the word 'Composite' appears for recovery or normal mode, but not for fastboot mode
So, if you've managed to get the ADB drivers installed properly, you should see one of the items on the right-hand side of the table. Test it in both fastboot mode and normal mode to be sure it loads correctly in both cases.
What can I do if the drivers won't load?
Windows can be very temperamental when it comes to device drivers. Don't assume the worst right away, but try rebooting the computer, disconnecting/reconnecting the device, and restarting the device in both modes. Fastboot in particular sometimes won't get detected by Windows on the first try and may require a reboot of the Kindle Fire.
If the Kindle Fire comes up as a different device or you get a "Code 10" error, you'll have to explicitly tell Windows what driver you expect to see for the device. The steps below are for Windows 7, but they should be very similar for earlier versions of Windows as well. The following may have to be performed twice, once for normal mode and again for fastboot mode. The steps below are listed for normal mode (and the fastboot equivalent in parentheses). Be sure to have tried installing the drivers using the batch file at least once or you will not be able to complete the process.
Connect the Kindle Fire in normal mode (fastboot mode) to the computer
In the Device Manager, right click on the device and select "Uninstall"
Check the "Delete the driver software for this device." box and press "OK"
Disconnect the Kindle Fire, reconnect and reboot in normal mode (fastboot mode)
The Device Manager should show "Other devices -> Kindle" ("Other devices -> kindle")
Right click on "Kindle" ("kindle") and select "Update Driver Software..."
Select "Browse my computer for driver software"
Do not click the "Next" button, but select "Let me pick from a list of device drivers on my computer"
Select "Android Phone" and then press the "Next" button
Press the "Have Disk..." button
Click the "Browse..." button, point it to the "C:\kfu\drivers\kindle" directory and press "Open"
Press the "OK" button
Uncheck the "Show compatible hardware" checkbox
Select "Android Composite ADB Interface" ("Android ADB Interface") and press the "Next" button
Select "Install this driver software anyway"
Press the "Close" button
The device should now appear in the Device Manager.
Now I can use KFU for everything, right?
KFU is great as a preliminary setup tool, but not so good as a troubleshooting tool. Making it easy also means hiding many details from the user and those details can help you understand what's happening with the device. If you get into a jam with the Kindle Fire, you're much better off getting your hands dirty with fastboot and adb. Whether you've used the SDK or KFU to install the drivers, you got the fastboot and adb programs as part of the package deal. You might as well learn to put them to good use.
Users seem to balk at the idea of using the command line, but all you really need to know is a few simple Windows "cmd" commands to get around the directory structure. Then, you just have to learn a handful of fastboot and adb commands to become a Kindle Fire expert. That doesn't sound so bad, does it?

Windows cmd, fastboot and adb
OK, so what are these commands?
To get started, click on the Start Menu to begin. Then, depending on the version of Windows, either use "Run…" or "Search" and type "cmd" to open up a command line window that will look a lot like...
The last line in this example is called a prompt and it's followed by a blinking cursor.
The prompt tells you where you are in the directory structure. When the "cmd" program first starts up, that location is your Windows user's home directory by default. In the above example, my username is "kinfauns" and my home directory by the same name is in the "Users" directory located on the "C:" drive. The "C:\Users\kinfauns" part of the prompt is the directory path and it uniquely describes the location of the home directory owned by the "kinfauns" user.
The blinking cursor indicates the program's readiness to accept a new command. Each time you execute a command, a new prompt/cursor will appear at the bottom, telling you that it's ready for you to type another.
Now type "dir" (without the quotes) and press Enter, and you'll see the names of all the folders in your home directory. The "dir" command just prints out a content listing of the directory indicated by the prompt. If you open up your home folder in Windows Explorer and look inside, you'll see everything in that folder shown in the list you got from the "dir" command. The "dir" command implicitly operated on the current directory shown in the prompt, but you can also provide an explicit argument to tell it what directory to list. For example, "dir C:\Users" lists all the users directories. Providing an argument after the command name will be important for the next command...
The "cd" command is used to change the current working directory. We need to get to the KFU directory, so we can use "C:\kfu" as an argument to the "cd" command. Type "cd C:\kfu" and press Enter to change to that directory. No output was provided, but the new prompt has a different directory path to confirm the "cd" command has executed successfully. You can try "dir" here to list the contents of the "C:\kfu" directory, but it's not necessary to first list it if you know what's in there already. In this case, we'll "cd" into the "C:\kfu\tools" directory, but you won't have to provide the full path. Since "C:\kfu" is already the current working directory, "cd tools" is equivalent to the "cd C:\kfu\tools" command. The one other key component to navigating the directory structure is the ".." directory. The ".." directory refers to the parent of the current directory, so "cd .." will take you back up to "C:\kfu" and another "cd .." will take you up to the "C:\" directory.
Now you'll be able to navigate through the directories and you should have a fair idea about how to construct a directory path (this will come in handy later). The fastboot and adb executables are in the "C:\kfu\tools" directory, so you'll have to get there using what you learned to be able to use them in the next section. There are just a few more tips that might come in handy...
Shift-right-click on/within a folder and select "Open command window here" to open a command line window with that directory path as the current working directory.
File/folder names or directory paths containing spaces must be enclosed in double quotes.
Drag and drop a file or folder from the Windows Explorer windows into the Command Prompt window. The complete, absolute path of the object will be pasted into the Command Prompt window automatically.
Utilize the "Tab" key to complete a file/folder name without typing it in its entirety (e.g. Try typing "cd C:\kfu\to" and then hit the "Tab" key).
For more information on Windows cmd commands, bleepingcomputer.com has a nice introductory tutorial and ss64.com has a full reference page of commands.
How about those fastboot commands?
Just to review, fastboot is a command line tool used to erase or flash partitions on Android devices. To use fastboot commands, the Kindle Fire must be put into fastboot mode by one of the following three methods...
Set the bootmode to 4002 and reboot
Connect a factory cable and reboot
Issue a fastboot command during FFF's temporary fastboot mode
Fastboot mode can be confirmed in Windows Device Manager as "Android Phone -> Android ADB Interface" when the proper drivers have loaded.
You can also verify the Kindle Fire is in fastboot mode by issuing...
Code:
fastboot getvar product
and it will confirm by returning "product: kindle" as the output. Alternatively,
Code:
fastboot devices
returning "0123456789ABCDEF fastboot" also means the device is in fastboot mode, but this does not seem to stop the FFF temporary fastboot countdown, so the first command is probably more useful to remember.
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.
Use one of the following to wipe a partition on the device...
Code:
fastboot erase bootloader
fastboot erase recovery
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase media
You must be very deliberate when using these commands. The fastboot erase command will immediately start erasing the partition and it will not be recoverable if you change your mind. Erasing the bootloader, boot, or system partitions (especially the bootloader) can seriously brick your device if they are not replaced. In most cases, it's probably best and safest to flash a new image on top of the existing data, but they are listed here for reference. The last two commands are probably more useful than the others. Erasing the data partition is roughly equivalent to a factory reset and the last command will erase the sdcard partition.
Rather than use the fastboot erase commands above, the fastboot flash command can be used to overwrite the partitions...
Code:
fastboot flash bootloader \path\to\u-boot.bin
fastboot flash recovery \path\to\recovery.img
fastboot flash boot \path\to\boot.img
fastboot flash system \path\to\system.img
fastboot flash userdata \path\to\userdata.img
Most users will most likely only need to utilize the first two of these commands to flash a new bootloader and recovery, but the others may still be useful if there's ever a reason to flash them separately.
Just in case you are unsure about what the "\path\to" part of the command means, it refers to the directory location of the file you are flashing. Let's say you want to flash a new recovery image and have the recovery.img file in the C:\kfu\software folder. You would replace the "\path\to" part with "C:\kfu\software" in the command to look like...
Code:
fastboot flash recovery C:\kfu\software\recovery.img
The file name at the end is also a generic example and should be changed to the actual name of the downloaded file.
The Kindle Fire can also be booted directly from a boot image on your computer without first flashing it to the device...
Code:
fastboot boot \path\to\boot.img
Because a recovery image is just another boot image, this feature is useful for testing out another recovery without overwriting the one currently installed. For instance, if you have CWMR installed, but you just want to take a look at the new TWRP release, use "fastboot boot" to boot from that image. It won't affect your CWMR installation and the next restart into recovery will boot into CWMR. Note: This will not work with TWRP 2.0.0 because that distribution is a boot image that automatically flashes the recovery image contained within the boot image. TWRP 2.1.0 and above will behave as previously described.
For even more fastboot commands, take a look at...
Code:
fastboot help
What about the adb commands?
As noted before, adb commands can be sent to the Kindle Fire when it is either booted into the OS or recovery. First check the Windows Device Manger to make sure "Android Phone -> Android Composite ADB Interface" appears in the list and then verify adb is working properly with the following command...
Code:
adb devices
To manage communications between the computer and the device, adb utilizes the services of a background server (daemon). When an adb command is issued, it checks to see that the server is running and starts one as necessary. After this server starts running, adb will output a line with a 16 digit alphanumeric identifier and a short description for each devices that responds to the query (e.g. "3A8F010600000001 recovery"). If you don't see this identifier, then the device drivers are probably not installed or not loading properly... see the previous post about device drivers.
Like fastboot in the previous section, adb can also be used to change the bootmodes on a rooted device...
Code:
adb shell idme bootmode 4000
adb shell idme bootmode 4002
adb shell idme bootmode 5001
These adb shell commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then the device can be restarted with
Code:
adb reboot
These adb commands copy files and folders to and from the device...
Code:
adb push <source on host> <destination on device>
adb pull <source on device> <destination on host>
The arguments enclosed in angle brackets (<>) must be replaced with the path to files and folders as appropriate. To copy a file or folder from the host computer to the Kindle Fire, use the "adb push" command. To illustrate by example, let's say there's a folder full of mp3 files, "C:\mp3" on the computer and you want to copy some or all of them to the Kindle Fire's Music folder.
Code:
adb push C:\mp3\track1.mp3 /sdcard/Music/
adb push C:\mp3\track1.mp3 /sdcard/Music/newtrack.mp3
adb push C:\mp3 /sdcard/Music
The first command copies the track1.mp3 file to the Music folder on the Kindle Fire. The second command copies the same file with a new name on the device. The last one copies the entire contents of the mp3 folder to the Music folder. Note that Windows uses the backslash as a separator while the Kindle Fire uses the Unix/Linux conventions with the forward slash.
Conversely, "adb pull" copies a file or folder from the Kindle Fire to the host computer.
Code:
adb pull /sdcard/Music/track1.mp3 C:\mp3
adb pull /sdcard/Music/track1.mp3 C:\mp3\newtrack.mp3
adb pull /sdcard/Music C:\mp3
These commands are equivalent to the "adb push" examples, but move the files and folders in the opposite direction.
Another useful command is used to sideload an app onto the device...
Code:
adb install \path\to\App.apk
Some of the most powerful adb commands are actually Linux commands. One such example to change the bootmode of the device was covered earlier in this section. "adb shell" commands in this form...
Code:
adb shell <Linux command>
actually execute a Linux command directly on the device. The entire range of available Linux commands cannot be covered here because of the limited scope of this document. Just be aware that any commands in this form are really Linux commands being run through adb. For more information on Linux shell commands, An Introduction to the Linux Command Shell For Beginners is a good place to start.
Most users will be able to get by with the commands covered here, but adb has many other useful commands as well. Be sure to take a look at the built-in help for other useful adb commands...
Code:
adb help
How do I put all these commands together?
A supplement to this guide has been posted with details on how to root a stock device and install a custom ROM. The how-to guide outlines the use of these adb and fastboot commands in real-world tasks to modify the Kindle Fire.
Kindle Fire For Beginners - Supplemental How-To Guide
How can I thank you for this guide?
Hit the "Thanks" button and share your positive experiences in this thread. If you feel like you have more to give, consider donating a few minutes of your time to new users who come here looking for help. None of us were born with this knowledge and we all need a hand up from time to time. Be kind and generous when you post. Thanks for reading!

congratulations !
very well written guide to understand how the kf works
would recommend every new kf user to read it - hope they take the time ...

b63 said:
congratulations !
very well written guide to understand how the kf works
would recommend every new kf user to read it - hope they take the time ...
Click to expand...
Click to collapse
Wow... thanks! I was scanning the general section this morning to see if anybody had posted a response to the guide, but I couldn't find it right away... went to the second page and still couldn't find it so I thought it was deleted for length or something. Only then did I notice it had been made a sticky post. A thanks to b63 for the kind words and a humble bow to whoever made it a sticky.

Thanks for taking the time to write this guide. It is great to see contributions like this for the community to use.

Wow. This is incredible. This is so easy to read and helped me alot with little minuscule things i didn't know which made it hard for me to understand completely. Thanks for the taking the time and making the extra effort to include all the little explanations.

Thanks, this was a good help, I have been flashing ROMs on my Captivate and a couple other Android phones for about a year, but I just got the Kindle on Saturday so I look forward to playing with it, and this guide helped point me in the right direction
sent from my Fusion ICS powered captivate on the xda premium app.

Thankyou for this guide! I have had my Kindle fire for a while now and have so far managed to brick it unbrick it and erase all the system data.(don't ask me how lol) but I did fix that as well.... All kindle fire users should read this!

This should be stickied.

Cl8rs said:
This should be stickied.
Click to expand...
Click to collapse
I am pretty sure that it is....

Excellent guide, helps not only understand KF but Android developement altogether, kudos.

Awesome write upp
Can u pls explain cyanogenmode m confused
Sent from my GT-S5570 using XDA

Many thanks to everyone with good words to say about the guide. I hope it was really worth the read for all of you. I also hope that you'll help spread the word about it to new members who might also benefit from reading it. Thanks.
tejasghalsasi said:
Awesome write upp
Can u pls explain cyanogenmode m confused
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
http://www.cyanogenmod.com/
CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
ROM is another word for firmware. Although the Kindle Fire doesn't have official support (yet) from the group behind CyanogenMod, many hard working developers have used it as a basis for the ROMs you see in the development section. You'll often see it referred to as CM7 (based on Gingerbread) and CM9 (based on Ice Cream Sandwich).

Thank you for this guide. Just in time for my KF to arrive tomorrow.
This really clears the things and what to do with KFU.

thank you for this amazing post -really appreciate you people taking out time to write such posts for noobs like me -must be tedious for you but its lifesaving for us

It's a great orientative post, I couldn't think of anything to add that it doesn't cover already.
Maybe mention that ICS ROMs are in early stages of development and some features aren't working yet? (HWA-> some games, netflix, flash....)

What you could add is a comparison between CM7 and CM9 and ICS and maybe some "best practices".

Dasanko said:
It's a great orientative post, I couldn't think of anything to add that it doesn't cover already.
Maybe mention that ICS ROMs are in early stages of development and some features aren't working yet? (HWA-> some games, netflix, flash....)
Click to expand...
Click to collapse
bambi007 said:
What you could add is a comparison between CM7 and CM9 and ICS and maybe some "best practices".
Click to expand...
Click to collapse
Thanks. I appreciate the suggestions, but I would like to avoid topics that might change from week to week. I know that CM9 is a hot topic right now, but its development is in a very fluid stage. The guide is meant to be a primer for beginners so that they have a foundation of knowledge they can use to find and understand areas of interest specific to the individual. It's not really intended to be a "what's new" guide in the world of Kindle Fire development.
I'm not sure what you mean by "best practices" in this context. I'm thinking about doing an additional guide that's more of a tutorial, but it's just bouncing around in my head for now. When I find some time to organize it, I'll do something with it.
Thanks again for reading.

Thank you for writing this guide! I'm relatively new to rooting devices in general and had my first success with my 4G Amaze and now the KF. But I've always been confused by some of the terms people have used. So thank you for clarifying all this without making me look like a total newb! lol
kinfauns said:
I'm thinking about doing an additional guide that's more of a tutorial, but it's just bouncing around in my head for now. When I find some time to organize it, I'll do something with it.
Click to expand...
Click to collapse
This would be wonderful, I have yet to flash any ROMs onto any devices yet because I still know very little about them, other then what they do. But to know which ones are "best" or more popular would be great.
Ex:
Like CM9 can't do video
CM7 not as "flashy" but can do video
but again thank you for providing this awesome guide!

[GUIDE] Alternate method for rooting the Kindle Fire system version 6.3.1 and 6.3.2

The main reasons to root the kindle is to gain access to the Google Android Market and or flash a Rom. The the act of rooting the stock software is very near obsolete in most cases. For one reason or another this appears to be an arduous task for the kindle, the computer, the utility and for the inexperienced user. There`s a better way, not a new way but far less talked about. My hope is to create a better safety net for the average user. A few simple steps and you`re well on the way. The process involves getting drivers installed correctly, putting a custom recovery in place as well as a bootloader, managing your first backup and installing a modified stock Rom with root. It`s a good idea to first understand some basic things about what your device will need to make all this possible. I do not believe it could be anymore clearly laid out for you than FSM Kinfauns wrote here [GUIDE] Kindle Fire For Beginners. If you`re new to rooting or just to the Kindle Fire this is a must see.
Drivers​
Well I`m sorry the first part is difficult at least for some users it requires getting drivers in order. I`m not going to go into great detail on this it`s very well highlighted in the second post of the above thread. Some things that may help installation.
Avoid using 3.0 USB ports users have had trouble with them not reacting well to fastboot causing serious problems.
Make sure your using the proper cable.
Run the Install_driver bat file first. Any errors during this may indicate the need for a manual installation. Windows XP requires manual installation.
Plug in the Kindle. Watch to see if windows shows installation of drivers and which one. Windows 7 usually shows a popup balloon of the driver it`s installing, click on it to view progress and type.
Open device manager. In device manager you should see "Android phone" click to view driver it should read "Android Composite ADB Interface".
If it reads "Android ADB Interface" more work is needed.
Right click then select update driver.
Click "browse my computer for driver software", and point it to the kindle drivers. On my Windows 7 machine, for instance, it's C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Util ity_v0.9.6\Kindle Fire Utility\drivers\kindle.
Include subfolders and click next. Disregard any warnings update driver software anyway, preferably it will then read "Android Composite ADB Interface".
For manual installation here`s a very good tutorial. How to install Kindle Fire adb USB driver?
Driver flex test​There`s a way to test the driver before ever attempting to send anything to your device. The Kindle Fire driver is in and of itself multifaceted and Windows has only met with the first half of it. A mild introduction to the second half could very well prevent Windows from being confused when you need it function correctly for the technical part of this process. I would consider this "the lesser of two evils" with the only risk being stuck in fastboot. This far less under weighs actually physically breaking something if it were to fail.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
In KFU select # 1 Bootmode Menu then select # 2 Fastboot <4002> the Kindle will be told to reboot in fastboot mode. Setting bootmodes with KFU takes a bit be patient.
Check device manager see that the driver reads "Android ADB Interface" without errors such as an exclamation point or a question mark.
Powering the device off and back on again while attached can prompt new hardware found for updating driver on XP and proper installation of the driver in Windows 7.
If it does have an error or Windows does not recognize the device you must once again right click then select update driver to make it read "Android ADB Interface".
Press any key to continue
If it says ADB status offline Boot Status: Unknown disregard and select # 1 Normal <4000> this will tell the Kindle to reboot in Normal mode.
After booted press any key to continue.
Press 0 to recheck device status.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000. This completes the driver flex test. If you get stuck in fastboot don`t panic there`s no damage, just an altered bootmode. Keep working with your drivers, powering the device off and back on again while attached seems to work pretty well.
Device preparation​
Start with a fully charged battery.
This step is very important under settings/device turn on allow installation of applications from unknown sources.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Status verification​
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
TWRP installation​
Select # 3 Install Latest TWRP Recovery. The Kindle will be told to reboot in fastboot mode. If all goes smooth it will reboot, in the terminal it will download the recovery, send it, write it. Then return your kindle to normal bootmode.
If nothing happens after 3 or 4 minutes and it just sits there <waiting for device> simply hold down the power button while connected till it turns off then turn it back on again. This could even take a few times always wait the 3 or 4 minutes in between.
Bootloader installation​
Hopefully now the risky part is over and you`re booted back to the stock OS of the kindle.
Swipe to unlock the screen.
Do not disconnect the USB file transfer application. If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer. This will show the contents of your sdcard on your computer.
Download bootloader only from here [bootloader][05-26] FFF 1.4A bugfixes + new look + recovery boot [.zip file size]. All files to be flashed in recovery must be in zip form. DO NOT EXTRACT. Do not use the bin file from KFU it`s not intended for flashing in recovery and will break the bootloader.
Drag and drop fff-u-boot_ v1.4a.zip on to your sdcard but do not place it inside of a folder.
Then disconnect the file transfer application when finished transferring.
In KFU select # 1 Bootmode Menu then select # 3 recovery <5001> this will tell your kindle to enter recovery.
In TWRP select install then locate fff-u-boot_ v1.4a.zip tap on it and flash it, leave the boxes unchecked.
When finished hit the home button upper right to return to TWRP home screen.
Select reboot.
Select system if prompted.
First backup and flashing rooted stock​
After reboot Swipe to unlock screen.
Do not disconnect the file transfer application.If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer.
Drag and drop this Rom zip onto your sdcard [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire. Use the standard version not the altrom but do not put it inside of any folder. I`m not trying to highlight just one developers work but this is needed for this method.
Disconnect the file transfer application after the transfer has finished.
Unplug kindle from pc.
Power the kindle off , then back on again. When you see the white Kindle blue Fire logo quickly depress the power button a few times till you get a boot menu select --Recovery--.
In recovery select backup the default selections are fine, swipe to backup. This backup you will later rename noroot631 without spaces. Adding spaces will cause it to fail if you need to restore it.
When finished hit the home button upper right.
Select install.
Tap on GR9 Modaco zip and flash it. Do not enable force MD5 check or zip file verification or it will fail.
When done select reboot.
Select system if prompted.
Final result​
When the Kindle reboots it will have root and have the Google Android Market in your applications.Take note that this is the only Rom that you flash without doing the proper wipes. To increase your safety net it is recommended to perform an MD5 check on fff-u-boot_ v1.4a.zip and Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire using this application WinMD5Free. You may ask" Why so many steps?" or "Why not flash everything at once?" This is to insure everything works throughout the process and prevent mishaps. The entire point of this thread to avoid having to use a factory cable or firekit to rescue your device because something went wrong. I hope that some of my tips and tricks will make your rooting experience safer and easier. Good luck and have fun.
How to flash another Rom​
1. Transfer Rom zip and matching gapps zip to sdcard.
2. Enter recovery.
3. Create a backup.
4. Wipe factory reset.
5. Wipe cache.
6. Wipe dalvik.
7. Wipe system.( unless same Rom, same system, same developer)
8. Flash Rom zip.
9. Flash gapps zip.
10. Select reboot, then system if prompted.
11. Enjoy!
A very special thanks for all they continue to teach me and coaxing me to strive for more.
Kinfauns for Kindle Fire For Beginners
Soupmagnet for All the fun
Thanks to Vashypooh for Kindle Fire Utility
Thanks to Paulobrien for Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire

reserved

Your welcome.

Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?
---------- Post added 12th October 2012 at 12:09 AM ---------- Previous post was 11th October 2012 at 11:53 PM ----------
Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?

adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.

Thepooch said:
adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.
Click to expand...
Click to collapse
Did the trick. Ty sir

No problem.

abd Server offline and offline and offline......
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks

kindle-user said:
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks
Click to expand...
Click to collapse
Very important...what software version is your KF running?

soupmagnet said:
Very important...what software version is your KF running?
Click to expand...
Click to collapse
Hallo
My systemversion is 10.2.1_user_2030020

Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866

Hallo
Thank you for your Info. I will send it back to amazon. With original software do not like it.
best regards
soupmagnet said:
Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866
Click to expand...
Click to collapse

Bump

KFU ERRO
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!

Up!

Thank you your the best Thepooch

svartes said:
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!
Click to expand...
Click to collapse
I had the same issue, I had to rename the recovery file name to twrp.img then it worked perfectly. Also delete the file you created for twrp in the recovery directory in the kfu package and just replace the copy of twrp (if the is one there) in the recovery folder with the one you downloaded and renamed.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

everything is set but when i open the KFU 0.9.9 it look like this.

failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
This is a great guide that goes into more detail than most of them which helps a lot for troubleshooting.
Unfortunately, the /data file system on my fire is read only, so copying the files to root it is not possible. I'm using KFU 0.9.9 and the kindle is running 6.3.2. Compter is windows 7 64-bit. What do I need to do to get permission to write to the kindle's filesystem? See the screenshots below.

Thanks for the guide
Sent from my Amazon Kindle Fire using xda app-developers app

[GUIDE] Install Windows ADB Drivers for Fire HDs ("Newbie Friendly")

➜ No big ol’ SDK ➜ Latest Google drivers ➜ No messing with inf files ➜ ADB from any location ➜ Drag and drop files
Figured XDA needed a couple more ADB driver guides, so I'm bringing these down from Google drive where they've been getting a lot of use--with no complaints so far. :fingers-crossed:
Follow the steps below to install the Google ADB driver for "normal" (OS) mode.
Follow post #2 to install the driver for sideload mode. You must do this to sideload OS .bin files via stock recovery.
See post #3 for basic info/tips for using the command window and entering adb commands.
[EDIT September 21, 2015] If you're running Windows 10, read this:
At step 3 you install 15 Second ADB Installer. Some Win 10 users are reporting a problem. Please do this to help track it down:
- Be sure to run as Administrator.
- If you get an error, post the exact error and when it happens. Do not rerun Installer until someone replies to post.
- If you do not get an error, please post and say so and tell what type of Win 10 you have (home, pro, enterprise, etc.)
Thanks!
Install ADB Driver for "Normal" (OS) Mode
This uses @Snoop05's 15-Seconds ADB Installer. It provides the driver and software you need and puts the path to adb.exe into your PATH variable so you can run ADB commands from any folder.
Before you begin:
(1) Turn off anti-virus software
(2) Disconnect other physical devices that use adb and shut down any virtual ones. This can go very smoothly if you're not running anything that uses adb, including emulators, some photo-sync software, Gatesjr debloater, etc.
1. Make sure adb debugging is enabled on the the device. (Settings->My Device->Developer Options: Debugging)
To open Developer Options: In Settings -> My Device, tap on the serial number until Developer Options appears at bottom of screen.
2. If you've never connected Fire HD to computer, connect now and read this:
a. You may see a USB debugging message on tablet, tap "Always" and "Allow."
Even if you don't see message, Windows should try to install generic MTP drivers (not ADB!). Wait until you see success or failed message.
b. Unplug/replug and wait for Windows Explorer OR for message that prompts what to do when device is connected and choose Open window to Display Files, check Always do this and then OK.
c. Disconnect..
3. If you KNOW there’s no adb driver installed for the device, go to next step.
. . . If driver might already be installed, do hidden steps.
Connect to computer, open Device Manager (instructions below) and see if a driver is listed under Android Device.
- If a driver is NOT listed, go to next step.
- If a driver IS listed, open CMD window in folder containing adb.exe and run adb devices command (step 12).
* If adb devices DOES return an ID, this driver is working and you don’t need to install a different one.
* If adb devices does NOT return an ID:
a. In Device Manager, right-click the driver and choose Uninstall.
b. Unplug the device and restart Windows.​
4. Download the latest version, currently v. 1.4.3, of 15 seconds ADB Installer and run it as Administrator.
If you are not Administrator, right-click the file and choose “Run as Administrator“
Read all about 15-seconds Installer at the link.
Press Y to install ADB and Fastboot
Press Y to install ADB system-wide or N for current user onlyYou should see:
Installing ADB and Fastboot . . .
4 files(s) copied
If you see 0 files copied, post the error with your Windows version and the drive it's installed on.​
Press Y to install drivers
View attachment 3455788​
5. An Install Wizard will run. Look for it and install device software!
6. Connect the Fire to the computer and wait until you see it in Windows Explorer.
7. 6/3/2016 Update for Win 10: Your drivers might already be installed. Check for Allow USB Debugging on tablet. Go to step 12 and run the adb devices command.
. . . If it shows serial number and unauthorized, you need to enable USB debugging and run command again. It should then show serial number and "device." You're done!
. . .If it doesn't show serial number, continue the steps.
Win 7 and 8.1: Open Device Manager:
Win10: ? Win8: Right-click Start Button and choose Device Manager. Win7: Click Start button and type Device Man [enter]
8. Find Fire under Other Devices, right-click it, and choose Update Driver Software.
If you don't see Fire under Other Devices, disconnect/reconnect or try a different USB port, or try toggling Enable ADB in Developer Options. If nothing works, disconnect and reboot both Fire and computer and try again.
{
"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"
}
​
9. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
​
10. Find Android Device, click it and press Next.
. . . If Android Device is not listed, look here.
If you DID NOT run 15 Seconds ADB Installer, STOP, disconnect from PC and run it now.
If you DID run 15 Seconds ADB Installer:
a. Double-click Show All Devices.
b. Under Manufacturer, scroll to Google, Inc, click it and continue.
↠ If Google, Inc is not listed, the ADB drivers are not installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.
11. Select Google, Inc in left pane and then Android Composite ADB interface in right, and press Next.
If the screen you see only has the Model pane (on the right above), scroll down to Android Composite ADB.
↠ If the driver is not listed, drivers have not been installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.​ 12. At the warning screen, press Yes.
Driver is updated!
13. Run the adb devices command and confirm it returns a device id:
a. Open CMD window: Hold down the Shift key, right-click the desktop (or an empty space in a folder) and choose Open command window here.
b. Type: adb devices [enter]
View attachment 3467199
If you see an ID followed by “device,” the driver is installed correctly. DONE!
If you see an ID followed by “unauthorized,” look at the tablet for “Allow USB Debugging?” message and tap OK.
If debugging message disappears before you say “OK,” unplug/replug tablet to see it again.
Repeat the adb devices command and confirm it now looks like above. DONE!
If you do not see an ID, the driver may not be correctly installed or USB debugging might still be disabled on your tablet. Verify all connections and reboot tablet and PC and repeat this step. If adb devices still doesn’t return an ID, follow this guide from the beginning again.

Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.

Info and Tips for Using the Command (CMD) Window - for "Newbies"
Here's some basic info for using the CMD window and entering commands found in the guides.
Open CMD window
Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"
Give commands on-the-fly
If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."
Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.
Install an app (or sideload a bin file)
Open CMD window in the folder containing the file and enter the command: adb install filename.apk
If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"
Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"
Drag & drop files and copy/paste commands
To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.
Drag and Drop
Type: adb install <--type a space after "install"
. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.
Copy and Paste
Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.

Installing drivers for sideload
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?

rking38 said:
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
Click to expand...
Click to collapse
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)

DoLooper said:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
Click to expand...
Click to collapse
Wow...follow the instructions from step one! thanks for your patience

15 Second ADB problem
DoLooper said:
Installing Google ADB drivers for your Fire HD:
Click to expand...
Click to collapse
MRDirtyPixels said:
I followed a guide to install Lolipop on my device, I managed to get the 15 Second ADB Installer but could only get the 1.3 version to work.
When I try to do it now it states on the device that I need 1.3.2 or higher. The 1.4 download gives me an Access Denied message and installed 0 drivers.
Click to expand...
Click to collapse
Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?
Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?
Please let me know these things so I can try to find a fix. EDIT: @MRDirtyPixels I'll post how to update the driver when you reply. Thanks!

Fire HD 6 on 4.5.3
Win7 Ultimate x64
I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".
I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.
Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.
Any ideas would be greatly appreciated.
**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?

You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!

DoLooper said:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
Click to expand...
Click to collapse
Oh, great! I may have overlapped a guide or two. Thanks so much!
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?

jiznon said:
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
Click to expand...
Click to collapse
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/

jiznon said:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.

jiznon said:
. . . (it also states to install sideload drivers). Maybe it should be edited. http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Yes, I see I introduced some confusing info about drivers/versions in last update. I'll fix. thanks.

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
DoLooper said:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
Click to expand...
Click to collapse
Right. I'm still at "Before You Begin:
Install adb device drivers if you don't have them.
Here's an illustrated guide for Windows drivers. Install driver for both OS mode and sideload mode."
Wanted to make sure I don't miss anything. Looks like I'm on the right track. Thanks!
**EDIT: Everything went smooth. Thanks everyone!

Hi DoLooper, I'm currently following your [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") guide to root and update a Fire HD 7 and that's how I got here. I have successfully completed this guide, but only after I solved a problem that I ran into along the way. I solved it myself, so I want to share how I did it.
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Last but not least, thank you very much for spelling everything out step by step, it all seems like a doable task now.

podikan said:
. . .
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Click to expand...
Click to collapse
This is helpful and I'd like to add it, but I'm a little confused. Step 4 is just installing the 15-second Installer software. I don't think it asks anything. Could you please clarify the step where you got that prompt? Also, when it was listed under Samsung, you were able to right-clicking and choose Update and install the google drivers, right? Thanks.

Well, at the end of step 3 the program 15 Second ADB asks "Do you want to install device drivers?" and then a windows prompt appears. This is when I got the following prompt on top of that (only have it in German, sry): imageshack.com/a/img911/8983/bBg2q0.jpg I assume it's some kind of driver, as 15 Second ADB calls it. Is it really specific to a device?
As for your second question, if I remember correctly I was able to do that (I had to dig for it like you explain in step 9 after ". . . If Android Device is not listed, look here."). But afterwards it was still displayed as a (fully installed) Samsung portable device in my device manager. No chance I would go ahead and root from there. That's when I found and removed the Samsung drivers which came with Kies, rebooted, and started the procedure from the beginning.

ADB not cooperating
Ok. I am on a Fire HD 7 Gen 4 at OS 5.1.1, and attempting to downgrade to 4.5.3 for rooting purposes. (My eventual goal is to get CyanogenMod or another 'pure android' ROM on it, if you can help with that, great) When in sideload mode, Windows doesn't detect my device at all (no KFARWI or any other 6-letter combo) but ADB can detect it in both sideload and OS mode. My problem is this: Whenever I attempt to flash a .bin stock recovery, adb stalls for about a second, while on my Fire I only see:
Now send the package you want to apply to the device with "adb sideload <filename>"
Finding update package...
Opening update package...
Verifying update package...
before the device reboots. On adb I then see: "failed to read command: connection reset by peer" Any subsequent attempts without a manual reboot into sideload mode just instantly time out. I have a feeling this has something to do with the weird reboot, but how do I prevent it?

DoLooper said:
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Click to expand...
Click to collapse
thank you