[7" Kindle Fire HD General] prokennexusa:
Kindle Fire 8.9" - How to Root

zildjian4life218,

First let me welcome you to XDA Community, we are glad you decided to join our team. You will love this community, there are some real geniuses here in the community. Let's get you your issue:

When you run Root Many Android, does the Kindle asked to be Restored? If no, run these commands:

adb kill-server
adb start-server
adb devices

If you do not see a serial number, please proceed to 'A', if you did see a serial number, please proceed to 'B':

A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle, move on to Main Step B

Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.

Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video

The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers

Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this

does not open ADB Communication try the new updated KindleDrivers.exe

Please open an Administrative CMD Prompt and enter:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

Reboot the Computer to apply the above command.

Extract the Kindle Fire ADB drivers.zip to your desktop.

1. Unzip Kindle Fire ADB drivers.zip to Kindle Fire ADB drivers on your desktop.

2. Click windows start button.

3. Next choose Search, in the "Search programs and files" box type "cmd" (don't hit enter or search).

4. The program "cmd.exe" should be listed at the top. Right click that and select "Run As Administrator".

5. Navigate to the Kindle Fire ADB drivers.exe or KindleDrivers.exe using the DOS Command cd.

6. Next, the install will begin, allow the install to complete.

7. While the driver is installing. Go to the Kindle unlock if locked.

8. Pull down the upper bar. Select "More".

9. Now Select the "Security" Tab.

10. In Security is an option to: Enable ADB

11. Select "On" to Enable ADB on the Kindle

If not, We have an alternative driver here: usb_driver

Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response

The alternative driver originates from the Android SDK and is universal for just about any Android device.

The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.

Once we get ADB installed then let's plug-in the Kindle to your computer USB to see if it initializes properly.

Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".

Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes

ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):

Windows XP

To install the Android USB driver on Windows XP for the first time:

1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.

2. Select Install from a list or specific location and click Next.

3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.

4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)

5. Click Next to install the driver.

Or, to upgrade an existing Android USB driver on Windows XP with the new driver:

1. Connect your Android-powered device to your computer's USB port.

2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.

3. Select Device Manager in the left pane.

4. Locate and expand Android Phone in the right pane.

5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.

6. Select Install from a list or specific location and click Next.

7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.

8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)

9.Click Next to upgrade the driver.

B) The next steps are used to Root the Kindle

The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?

Next, as per the Qemu thread you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package as noted in Step A above. Reboot the PC and next the Kindle.

Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.

Plug the Kindle back into USB if it is not already plugged into USB.

1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons (Latest Version is 18.5.1.

NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".

Make sure the Kindle is still plugged into USB.

Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:

Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18.5.1 folder.

Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18.5.1 folder toolbar.

This highlights the Root_with_Restore_by_Bin4ry_v18.5.1 folder.

Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18,5,1 are highlighted in blue.

Next Press the SHIFT Key, next Right Hand Mouse Click

Choose "Open command window here"

A Command window will open, finally type

Code:

RunMe.bat

Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.

The forum notes can be found here: Root MANY ANDROID! Forum.

Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Run Root MANY ANDROID! a second time.

Root Step 3: Finally Click on Superuser.apk under the Apps tab to initialize the Superuser daemon.

Root Step 5: Download suchecker.apk: https://dl.dropbox.com/u/54456659/suchecker.apk

Root Step 4: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download

Root Step 5: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install

Root Step 6: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.

Root Step 7: Download suchecker.apk: https://dl.dropbox.com/u/54456659/suchecker.apk

Root Step 8: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download

Root Step 9: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install

Root Step 10: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.

You should now have root AND if this is true your ADB communication is also functional.