How to root / jailbreak Kindle Fire using one click solution – SuperOneClick, also enable sideloading apps

Kindle Fire just started shipping yesterday and a super easy one click root / jailbreak solution is already available. We went through the steps, were able to reproduce it and duplicate the end result and we also streamlined it a bit especially for the ones that do not excel in computer skills so here it is for your Kindle Fire rooting / jailbreaking pleasure.

What is the root process bringing to the table? The possibility to install Google Android Marketplace (remember, by default Kindle Fire only comes with Amazon Marketplace), sideloading books on Kindle Fire is another enticing possibility as well.

First of all, all the credit goes to the user death2all11o that posted the solution on AndroidForums and also on XDA Developers.

Step 0. Enable sideloading on Kindle Fire

…or enable the installation of apps from unknown sources. This is exactly sideloading apps many of you are probably interested in. If you only want to add a market like GetJar, this is the only step you want to perform. Touch the top bar on your Kindle Fire and select More…->Device then turn on the Installation from unknown sources. It is that easy, thanks Amazon for not deliberately trying to hide this option. If you need a complete tutorial in enabling sideload on Kindle Fire, here it is!

Step 1: Prerequisites

You will need two different applications installed on your PC

a. Android SDK Windows (MAC OS X, Linux also available) from here. For Windows get the installer_r15-windows.exe. Android SDK relies on Java SE development kit that you can install from here. Choose the installer that matches your platform, install it and you can ignore the registration request at the end.

Once the Android SDK is installed, check the box – Start SDK Manager and proceed. This will take you to a dialog box prompting to install various components, ensure Tools is checked, scroll down to Extras and  select Google USB Driver package as well then proceed with the Install Packages button on bottom right corner. The whole process will take several minutes of downloading and unzipping files. Click Yes at various prompts asking you to update/kill ADB server.

b. SuperOneClick v2.3.3 from here (thank you CLShortFuse, please donate to him if you like this tutorial) or direct download from here. In order to install SuperOneClick, you’ll also need .NET Framework 2.0 or newer. unzip it into a new folder. In my case, I created a folder called SupperOneClick under c:\temp and unzipped all the files in there.

Step 2: Prepare the Kindle Fire rooting / jailbreaking environment

You will need to modify the following two files:

a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder

In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android

Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.



Note: It is a good idea to actually type the 0x1949 instead of copying it. I had reports of x getting copied as a special character.

b. android_winusb.inf  – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver

Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.

;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01


After you finished, save and close the android_winusb.inf. If you used Notepad and you cannot save the file over the old one due to rights issues, save it somewhere else, for example on the desktop and then copy it from there over the original file.

Step 3: Launching the Kindle Fire rooting process

a. Connect your Kindle Fire to your computer via USB

b. Open a command prompt window (Start->All Programs->Accessories->Command Prompt)

c. ADB path might not be registered with your system, so navigate wherever you installed Android SDK and to the folder that contains adb.exe. In my case, the folder is C:\Program Files (x86)\Android\android-sdk\platform-tools

If you don’t know hot to change the folder in Command Line Window, you should use CD command. Foe example to change the folder to C:\Program Files (x86)\Android\android-sdk\platform-tools use the following command:

cd C:\Program Files (x86)\Android\android-sdk\platform-tools

d. type adb kill-server followed by enter

e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)

Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.

Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.

If you installed the driver correctly, you should see the following dialog:

f. Launch SuperOneClick.exe and Click on Root button. Sit back and enjoy the process!

Step 4: That’s it! You have a rooted Kindle Fire!

Share your experiences with the community so everybody can profit from your experience

If you want to install Android Marketplace and other Google Apps, follow our tutorial in How to install Android Marketplace on Kindle Fire. YouTube, Netflix, Facebook are just minutes away ;).


  • de lee

    I did everything, but it just hung there after adb server . . . daemon etc . . . The only thing I don’t know if I did correctly is the adb_usb. Do I make a return and a new line to add the 0x1949 or do I add after the period? Thanks.

  • Hi de lee,

    I made a return and added the code on a new line

  • de lee

    it’s not showing the list of attached devices after I type adb devices . . . that’s the problem

  • This might sound like a dumb question, but did you plug it in? Did you see any activity in Windows regarding any USB drivers being installed when you plugged it in?

  • Nicole Sands

    I had to go to Device Manager and manually update the drivers to path C:Program Files (x86)Androidandroid-sdkextrasgoogleusb_driver

  • Anonymous

    I am stuck.
    The Command Prompt


    what do I do? Backspace does not delete the line.
    Sorry – I have not done this before
    Thank you so much

  • I updated the tutorial for those that are not familiar with the command prompt. basically use the cd command (from change directory) to navigate around the file structure.

  • Philip Powis

    I am hung here as well Daemon started successfully in superoneclick and then nothing…

  • Lon Lawrence

    I think I could do it, but I think I’ll wait. Somebody will come up with a true one-click, plug it in to the computer and press a button.

  • Had the same issue..ended up being because I copied and pasted his 0x1949. Something was off with the “x” I had to delete it and type it in manually and it fixed the issue. Looked like his x was a special character or something.

  • Damien Hall

    I am having a problem where the driver will not install at this step. I made the modifications to the android_winusb.inf file but then after trying to manually install the driver in Device Manager, it “cannot find the file specified”. Please help!

  • Damien Hall

    I am running Win7 x64, tried it both on PC and laptop with same results. The device will connect as a drive in Explorer but will not connect to ADB

  • Damien Hall

    I am running Win7 x64, tried it both on PC and laptop with same results. The device will connect as a drive in Explorer but will not connect to ADB

  • Damien,

    If you go in the Device manager, do you see the Android Composite ADB Interface driver installed and functioning properly? In my case this driver is in the first position in Device manager. You can also unplug the Kindle, restart the PC and try again after you changed the two files.

  • Damien Hall

    Thanks… I tried restarting and have the same problem. The Android Composite ADB Interface driver is not installed, this is the part that doesn’t seem to want to install.

  • I did everything — including updating the drivers for google/android USB on my XP machine… but adb doesn’t list my Kindle Fire under DEVICES even tho it shows up as a drive in explorer… Ideas?

  • I have the driver installed — and it show’s up under the Device Manager in explorer. However, adb won’t list it under ‘devices’ … Ideas?

  • K S

    i dant find the adb_usb.ini. I’ve looked in c:documents and settingsmy and there is no .ini file. it doesnt matter if the kindle is connected to the computer or not, the file is not there

  • You can create a new one then, the only info it needs inside is one line containing 0x1949.

  • Scott Washington

    For anyone who doesn’t see anything listed under ‘devices’, I had this problem until I found out that if you just copy and paste from here, the ‘x’ will be a different character and not be read right. So all I did was just manually type in 0x1949 and everything worked out.

  • de lee

    Of course it was plugged in, lol. I’ve done jailbreaking so doing these things isn’t new to me, but it’s just weird it didn’t show a device.

  • de lee

    I will try that tonight to see if that works. Thanks!

  • Henry Greene

    Scott, thanks!!! You are now an “X” Man!

  • Jim Gaal

    Do not have the requisite .android folder.

    Windows 7 enterprise, running in a virtual machine.

    Fire shows up and connects fine to windows. It is not listed in adb devices, as I dont have the .ini file to edit to make it show. Cannot create a folder named .android, so not sure how I can create the .ini

    Any suggestions?

  • de lee

    Yes, the device manager didn’t have the correct android driver! Thanks!

  • Anonymous

    I completed all steps successfully, but I don’t see SuperUser app installed (already tried to restart). Any idea why?

  • I am running into the same issue and it’s very frustrating. Did you ever find a fix?

  • I am running into the exact same issue on two PC’s and it is very frustrating. Did you ever find a fix?

  • Damien,

    I had the same problem but finally got mine working. I forgot to copy the lines under [Google.NTamd64] – I just had it under [Google.NTx86].

    Now the Device Manager found the android_winusb.inf file and adb devices show the Kindle Fire!!!

  • Windows7 32bit will NOT let me update the driver and I have been trying for DAYS. Im getting: “The folder you specified doesn’t contain a compatible software driver…blah,blah” OR I get:”Windows has determined that the driver software is up to date..blah”

    Please note: I DID replace the “android_winusb.inf” file with the one listed above using NotePad under Admin permissions.I checked the driver folder a million times also.

    Im stuck, can someone help?

  • Anonymous

    Mine did that initially but I all I needed to do was choose the usb_driver folder for the driver update, instead of either amd64 or i386.

  • L T

    superoneclick has this “gingerbreak” that was detected as a trojan by mcafee. is this safe to install ?

  • L T

    superoneclick has this “gingerbreak” that was detected as a trojan by mcafee. is this safe to install ?

  • Anonymous

    im getting everything down, but when running the” SuperOneClick.exe ” it stops running then says ” Operation not permitted ” help please


    After Running “SuperOneClick” it stops and at Routing device Step 7….operation not permitted

  • Anonymous

    Hung up at Step 7….help!

  • Anthony Gartner

    Issues at Step 7

    getprop > /data/local/tmp/output 2>&1

    export TEMPRANDOM=17284

    export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output


    END:17284export PS1=””

    rm /data/local/tmp/boomsh > /data/local/tmp/output 2>&1

    export TEMPRANDOM=21770

    export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

    END:21770export PS1=””

    rm /data/local/tmp/sh > /data/local/tmp/output 2>&1

    export TEMPRANDOM=42402

    export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

    END:42402export PS1=””

    chmod 700 /data/local/tmp/zergRush > /data/local/tmp/output 2>&1

    export TEMPRANDOM=51816

    export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

    END:51816export PS1=””

    cd /data/local/tmp/ > /data/local/tmp/output 2>&1

    export TEMPRANDOM=33503

    export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output

    END:33503export PS1=””

    export TEMPRANDOM=19226;export PS1=END:$TEMPRANDOM;./zergRush

    [**] Zerg rush – Android 2.2/2.3 local root

    [**] (C) 2011 Revolutionary. All rights reserved.

    [**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

    [+] Found a GingerBread ! 0x00000118

    [*] Scooting …

    [*] Sending 149 zerglings …

    [*] Sending 189 zerglings …

    [-] Hellions with BLUE flames !

    END:19226export PS1=””

  • What os version do you have on the Kindle Fire?

  • Eric Manning

    I am also getting stuck on Step 7. “mount: Operation not permitted”. Did Amazon do something to the current firmware? My version is 6.2.2. AFAIK this wasn’t happening before. Fortunately this does not brick my Kindle! Help ShortFuse!

  • Justin Oehlmann

    You Fucking Rock This is the only place on how to get the ADB working …love & kisses

  • Taty Graesser

    whenever i hit root,the thing stops responding