[Kindle Fire General] shintokun:
Not sure if this will help anyone, but I had a problem when rooting my new kindle fire 6.2.1

If you tried the Burrito Root method, I saw some few mistakes that I've done or didn't see in the video.

1. Updating the Kindle Drivers

I had previously rooted my android phone before, so when I plugged the kindle fire on my windows 7 laptop, I noticed that the windows was already indetifying it as an android phone, and had already labeled it for ADB. This auto-driver update thing might work for some people, but I find much better success replacing that driver that your computer identifies Kindle as, with the one that the BurritoRoot driver provides.

2. Getting the Kindle Root in the Listed Devices of ADB in command prompt.

This was probably the biggest issue I had when rooting the Kindle Fire. I was scratching my head, thinking why my Kindle Fire wasn't listed in the command prompt after typing "adb devices." I knew I did everything right from the beginning. Or so I thought?

One way I found that fixed that was downloading the Kindle Fire Utility v0.9.1

Unlucky for me, the download link was gone....

LUCKY for me, a fellow member here uploaded a mirror.

I somehow got it to work, with just luck but figured out the exact steps that seem to work for me (on Win 7 64 bit here).

1) Open up command prompt again, do the cd c:\KindleADB etc... upto the point where you typed in adb devices. you should be seeing no listed devices on the cmd (if you have that problem). LEAVE IT OPEN.

2) DOwnload the kindle fire utility, open the run.bat , it should have a message saying daemon started sucessfully, THEN QUICKLY FOLLOW THE NEXT STEP.

3) When the daemon started successfully message popped up on the KFU, go back to your CMD where you typed in adb devices and quickly type in "adb devices" again. it should say something like, killing out of date, starting daemon, and something about successful (Sorry if I'm not that much of a help, I tend to forget what the exact message said).

4) It should list the device. if not type it again.

5) Walla ! it should show a bunch of numbers, under listed devices.

3. Rooting the Kindle Fire in command prompt ERRORS

This wasn't much of a problem as it really was my mistake. I kept getting error messages when i typed in ADB ROOT in the command prompt during the BurritoRoot rooting method.

1) You have to make sure you have the BurritoRoot app installed in your kindle fire before starting the CMD adb root part. The app will tell you when to start typing away in CMD!

2) If you're doing the burritoroot method, you have to make sure you got all the names and directory right.

3) When you're doing the CMD adb root part, copy and paste it usually the best way to do it in CMD to avoid mistakes and erorrs! And no, you don't press CTRL+V in CMD. Rather, you right-click the CMD , then click paste (after copying the line you want to input).

adb remount

adb push su /system/xbin/su

adb shell chown 0.0 /system/xbin/su

adb shell chmod 06755 /system/xbin/su

adb install com.noshufou.android.su-1.apk

adb reboot

Notice all those commands above that you're suppose to type in (or copy and paste). The ones I bolded, people tend to make mistakes there. When you put those files you downloaded into KindleADB, PLEASE MAKE SURE IT IS NAMED com.noshufou.android.su-1.apk, otherwise when you get to the part

adb install [B]com.noshufou.android.su-1.apk[/B]

change it to :

adb install WHATEVER IT IS CALLED.apk that is Superuser.

The most important part is to push the SU file (that has no file extension).

I had my kindle rooted, with Superuser installed, but I couldn't get any pop-ups from Superuser asking permission for any apps! That is, until I found out I forgot to push the su file to /system/xbin/su and other steps to chmod it.

Anyways, I hope this helps anyone that goes through any problem like I did above. If not, sorry to waste your time! If you guys have any other problems, please leave a question below and perhaps I could or a fellow member here could help you.

Thanks again!