I was originally going to post this in the existing thread titled: ROOT Kindle Fire HD 7' started by PRallday168, but decided to create a new thread instead. This guide is based on that one, but goes into more detail, aimed at those folks unfamiliar with the process of modifying anything.Sometimes we get a bit frustrated when trying to do something we have not previously attempted, following guides that make an assumption that you already know at least part of what you are supposed to do, leading to confusion and mistakes. So here is the 'Idiot's Guide To Rooting Your Kindle Fire HD'With full academic ethics I will reference all other folks work and provide links when required.This post will constantly change as new information comes to lightThanks for input from Rollout regarding use of the SDK.
Section 2 - Prepare your KindleStart your Kindle Fire HD1) Slide the 'Unlock' bar on the right. Ignore the annoying advert slider on the left.
Click to expand.Eventually you will see on your PC:You can close all open command-prompts now!After reboot all is done! Have fun!Bin4ryThe first stage is now finished.If you are on version 7.2.3 Kindle Firmware you are done. You can re-boot your KindleIf you are not on version 7.2.3 carry out the next stage using QemuRoot for your Kindle Fire.After re-boot, allow time to get the device connected, (check device manager).Check it is connected using the same method as before (brief reminder here. See Section 3 for full description):1) open Command prompt2) change directory to C:roottype:HIGHstuffadb devicesPress Enter/HIGHYou should get an output like:HIGH. daemon not running. Starting it now on port 5037. daemon started successfully.List of devices attachedD025A0A024360KLP device/HIGHIf all is well then navigate to your QemuRoot folder, which you created earlier.
Right-Click on RootQuemu.bat and 'Run as administrator'On the command prompt choose 1) root:HIGHtype 1press Enter/HIGHafter a number of messages asking you to press any key it should re-boot the kindle. Repeat as necessary. Remember to look at the kindle and unlock the screen at the appropriate time. Your device will be rooted after the final reboot is done. You should have SuperUser and access to system files. Section 4 - Setup your rooted Kindle Fire for Google PlayIf You have not already copied the Google files to your Kindle, go up to Section 3, #2 and do it now (Connect via USB first!)If you are running WindowsXP, I do not see an obvious connection to your Kindle that shows up as a removeable drive.
Wow, thanks for this amazing walkthrough.I still need to pick your brains!!I'm getting this info from the CMD window. daemon not running.
Starting it now on port 5037. daemon started successfully.List of devices attachedBut there isnt any numbers below.
I have two entries on device manager and it shows in windows explorer as a driveIf I carry on and run RunMe and select option 1 it just seems to hang on 'Checking if I should run in normal mode or special Sony Mode. Please connect your device with USB-Debugging enabled now'Any ideas?
The apps on the caousel are blurry because they are the icons you see when you tap apps and they are listed, but magnified to a much bigger size. Their resolution is too low. Probably not much you can do about it.Incompatible apps can be copied from another device you own using appmonster. If you do not own another device create one using BlueStacks on your PCI will do another tutorial tomorrow on this subject and the way I got Carbs & Cals working on my Sony Xperia Tipo phone, although it is incompatible if you try and install it directly from the app store. I'm getting this info from the CMD windowList of devices attachedBut there isnt any numbers below. I have two entries on device manager and it shows in windows explorer as a driveIf I carry on and run RunMe and select option 1 it just seems to hang on 'Checking if I should run in normal mode or special Sony Mode. Please connect your device with USB-Debugging enabled now'what should i do??ps: the first time i tried i got.
daemon not running. Starting it now on port 5037.
daemon started successfully.but now i only getList of devices attachedplz help me. By far the best set of directions I have seen, thank you for taking the time to do it.I do have a question. I am still getting permission errors in both the runme.bat, and the rootqemu.
It says permission denied to creating any of the files/folders, such as coping stuff/su over to /data/local/tmp/./su also when coping superuser.any ideas? Been at this for a whileedit: I am using win7, and using admin for my cmd console. It is not working.one example, /system/bin/sh: cannot create /data/local.prop: Permission denied.It does find it and give me shell access in adb though. @timaestroGreat you got it done. In your original post you could not get any devices listed. Had I seen that post before you posted again I would have asked the same question as I did for Danman07 in post#3.Could you post what improvisation you had to make in order to get it to work?@RolloutI am very new to Android as an operating system, so I will not pretend to be any sort of expert at it but I have a couple of ideas.
If you drop RunMe.bat into Notepad you can see the commands used. In this excerpt:HIGHecho Pushing busybox.stuffadb.exe push stuff/busybox /data/local/tmp/./HIGHLine 1 echo Pushing busybox. This causes (echos) the text 'Pushing busybox.' To appear in the CMD window.Line 2 stuffadb.exe push stuff/busybox /data/local/tmp/.
Windows 7 32-bit Free Download Full
The backslash between stuff and adb.exe shows you this is a DOS command meaning Run adb.exe, which is located in the folder 'stuff'.The 'push' command is a parameter passed to the program adb.exe telling it to 'push' or 'send' or 'Copy' the file called busybox which is located in the folder stuff. This time there is a forward slash between stuff and busybox, because the program adb.exe is expecting paths to be described in the Unix/Linux/just about every other OS format except Microsoft.The final part /data/local/tmp/. Is telling adb.exe where it should copy busybox to. This is a path on the Kindle, NOT on your PC. If you are getting 'Permission denied' errors, it could be the permission is denied on the Kindle, NOT your PC and that adb.exe is returning an error message back to DOS, which is displayed on the console.Could you check you have set permissions in your Kindle as in Section 2 of my original post? :I also assumed that it is permission denied on the side of the kindle. I have quite a computer background, including some linux server builds and maintenance.I get the path issues, and just tried some experiments with no success, but will continue.
I did not think of that as so many have had those two scripts just work for them in windows 7.By the time I saw your post yesterday I had tried many variants to it already, to no avail.I followed all your instructions step by step. I just went back and double checked #2, and yes adb is on, allow installation of other apps is on, es is installed and working.It still gives the permission denied, even if I try to do it from a cmd window (as admin), manually instead of using the script.I am at a loss. Nice job on this really detailed guide.! Ive been busy with the holidays and family and all and havent been able to get on here and help. Thank you Inksaver for helping out. On another note the 7.2.3 updated version can now be rooted with only Bin4ry's tool. So you dont have to use QemuRoot.
Also i cant stress this enough but since others are working around the locked bootloader, we are very prone to getting our KFHD's Bricked like me. So head on over to and make yourself a factory cable or simply buy one from SkOrPn's 8th post. I bought mine and it has saved my KFHD twice! He has guides on what is fastboot and how to use his cable. Thanks PRallday168It was your guide I followed to get my Kindle rooted, but I thought it might be useful to take the time to give a really detailed guide for those not so familiar with the whole process.I used to be a moderater on one of the VB forums, and was always helping people out with their projects, which I enjoyed very much.Thanks for the advice on the factory cable.
Time to get out my magnifying loupes and sharpen the soldering iron. Looks like a similar job to soldering a wire on to the cut leg on an IC in the Wii to mod it after Nintendo clipped them off!@RolloutCan't think of any sensible reason here.A couple of things I might try in your situation, first try a different PC and second try a Factory Reset on the Kindle? Inksaver:Thank you for the advice.I got it to write after the factory default reset. Runme.bat ran, and did not give the permission denied after, however when it came back up it said mount: permission denied, are you root?It did successfully push the files before the initial reboot where you hit restore.After a reboot, or even two, it does not give me root. Tried 10 times now.It is the version 7.2.3, so that should be it.
It is not working though.any further suggestions?EDIT Success!!!I found that the Bin4ry Runme has it's own adb in the stuff folder, and relies on running from it. This version does not run on all systems.
What I did was installed the android SDK, copied the RunMe.bat and the 'stuff' folder into the adt-bundle folder in the sdk/platform-tools/. I then modified the RunMe in notepad, and removed the stuff from in front of all of the adb.exe references.
I then opened a cmd prompt, navigated to that folder, ran the Runme, and it worked like a champ. Rollout that is great news! Well doneI am curious about the version of adb.exe in Bin4ry's root package not working on all systems. If I Right-Click- properties I get:Size 162,186Size on disc 163,840Modified 13 Jan 2012 21:50:48Could you confirm the version in the SDK is different?Also, instead of modifying RunMe.bat, would it have worked if you had replaced the adb.exe in the stuff folder with the version of adb.exe you downloaded with the SDK?I am thinking about other forum users getting a similar error to yourself, and if a simple substitution worked then that could be added to the tutorial.
Android Adt Bundle For Windows 7 32 Bit Download
159kb size for the Bin4ry version. 796kb for the SDK version.I did not want to move adb out of the directory with the other SDK tools. I suppose I could have done a symbolic link or something, but it was day two at 3am. It might have worked to copy it over to that folder, but I did not give it a go.It was easier to just modify the RunMe.bat.It is funny that with the version 7.2.3 people are having problems all over, and there is not really a solution anywhere on the net. I posted this on a few other forums as well. Hopefully I stumbled onto a solution for all.Perhaps just putting a modified RunMe.bat for download? That looks like the ticket!
Hopefully it saves some people a great deal of time.From what I have read the problems exist on the version 7.2.3, and there are even some rumors out there that it can not be rooted unless it was prior to upgrading to that version. This came out of the box with that version.
I do not like no as an answer so I kept at it.Great work on the documentation.By the way, doing it this way I did not have to do the ini fie either. Not sure if that's going to be for everyone or not. The strange thing is, when I started my Kindle, and set it up for the first time, within minutes the screen was showing an update in progress, which I left running as I knew no better, and after a restart it was then on 7.2.3, before I had even had a chance to play with it.When trying to root it I was unable to get it recognised by adb until I added the.ini file. After that it all went well.I have asked recent posters what version they have, and as you can see, overall most seem to be succeeding.One possible difference, I am in the UK. Could it be there are slight variations in the firmware depending which country you purchase it from?