Bring out a new Android device to market, and you can be sure that a method to root it will also come out very shortly after. That was what happened to the Amazon Kindle Fire. Thanks to the Android community of developers and enthusiasts, the Amazon Kindle Fire can be rooted–and fairly easily, too.
The rooting process for the Kindle Fire involves some command line typing, but not the complicated ones though. If you have tried installing a printer for your desktop, then this can be a similar thing. Read on to find out more about how to root your Amazon Kindle Fire.
Step 1: Install the Android SDK into your PC. The details about how to install the software development kit will not be discussed here because it’s a totally different subject on its own.
Step 2: You now have to turn on “Allow Installation of Applications From Unknown Sources”. This can be done by tapping the Settings icon at the top right corner. Then, go to More->Device. You can turn on the setting from there.
Step 3: Connect the Kindle Fire to your PC using the micro USB to USB cable. If the connect screen comes up on the screen of the Kindle Fire, please do not tap on connect for this will enable USB connection.
Step 4: Modify android_winusb.inf
%SingleAdbInterface% = USB_Install, USBVID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USBVID_1949&PID_0006&MI_01
Step 5: Create adb_usb.ini and save it into the .android folder.
Step 6: Update the USB driver for the Kindle Fire.
Step 7: Check if Android SDK will now recognize the Kindle Fire.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Step 8: The last part of the process is to root the device. Since we already downloaded the software from Shortfuse, we just have to extract it. After extracting the software, you just have to run it and it will automatically do its charm.
Now that rooting is done, your Kindle Fire will now be open for endless possibilities. More third-party apps can now be installed on the device.
Like this post? Share it!
Good post. However, when m virus software (McAfee) scans the SuperOneClickv2.2-ShortFuse.zip file, it says that the file contains a Trojan named GingerBreak, and will not let me unzip the file. Is this something to worry about? Seems so.
Wouldn’t be the first time that some hacker embedded a Trojan in a supposed hack.
You have to trust where the file came from. An antivirus looks for virus/trojan like behavior. Many “hacks/cracks/root applications etc” are very similar to viruses. An antivirus does not know the difference between a good virus and a bad virus.
OK, well I unzipped the file SuperOneClickv2.2-ShortFuse.zip file any way, and my virus software deleted the detected trojan file, which is needed to root the Kindle Fire… so what do I do now?
screen shot of deleted trojan
Step #3 is unclear. When I plug in my kindle fire, it automatically connects to my pc and displays a explorer window of files on my kindle… I see no connect button to *not* press. ?
Hey! Everything works great except i don’t have a .android folder in users… What did I do wrong?…
I did all the step and when I type in those thing in the command prop is show me “list of devices” but it didn’t show me number like your screen did it just show me word
let me rephrase that after typing in adb devices it show me
“daemon not running…starting it now port 5037
daemon start successfully
list of devices attach
(This part is blank there was no number like the one show on the screen)
I got to step 4 and I have nothing that says andoridusb, I only had asdusb so I open with notepad and it has no clear words at all. Just @#^$(*W@%)(#*&)%(*. No google or any prompts. Getting frustrated. Help.
I get as far as “Shell rooting device…-step7 WaitForDevice 0.05s” Then SuperOneClick just sits and spins. If i do ANYTHING, i get a “not responding” message and it never clears, no matter how long i wait.
I had the same problem as Terry, I get as far as “Shell rooting device…-step7 WaitForDevice 0.05s” Then SuperOneClick just sits and spins.
Very precisely described and works perfectly – also for other devices!
Just a few additional hints:
- the necessary “%SingleAdbInterface% = USB_Install, USB..” VID/PID can be obtained searching in windows device-manager, clicking right at the (at the moment still “defect”) device -> properties -> Details > Device Instance Id
- usually a adb_usb.ini file exists already and contains
# ANDROID 3RD PARTY USB VENDOR ID LIST — DO NOT EDIT.
# USE ‘android update adb’ TO GENERATE.
# 1 USB VENDOR ID PER LINE.
never mind! this “DO NOT EDIT” can be ignored
- I use it just to access as root remotely via adb shell, that means after “adb kill-server” you call “adb shell” – finished!
Does it void the warranty?
After days of trawling the net for youtube videos, xda-developer posts and a number of failed attempts, I have FINALLY succeeded in rooting my Kindle off the back of this page – many thanks indeed!