[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only]

redbean25 · Jul 17, 2012

CannibalAngel said:
Well, I would like to root to be able to run apps like Titanium Backup and Root Explorer. I would rather root the device before I install any ROM but if this is the only way I can get it to work, I guess I will have to do it like this.

Could you provide the steps to install FFF and TWRP?

Once I install those, will I be able to use TWRP to preform a backup before I wipe and install a new ROM?

Thank for the reply!

For your findstr error, check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type

echo %path:;=&echo.%

That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:

%SystemRoot%\system32

Dqm56 · Jul 21, 2012

deleted

CannibalAngel · Jul 26, 2012

redbean25 said:
For your findstr error, check your PATH variable in Windows. Either view it by right clicking on My Computer and selecting Properties, then going to the Advanced Tab and selecting Environment Variables, or open a CMD window and type

echo %path:;=&echo.%

That will show all the entries, each on a new line so they are easier to read. Make sure there is a path entry for C:\WINDOWS\system32. If there is not add the following:

%SystemRoot%\system32

I'm not sure why this would make a difference but I checked anyway. %SystemRoot%\system32 is not in the path. How do I add it?

EDIT: Figured it out and that worked! I finally got my Kindle rooted!!!!! Thank you for the help!

redbean25 · Jul 26, 2012

CannibalAngel said:
I'm not sure why this would make a difference but I checked anyway. %SystemRoot%\system32 is not in the path. How do I add it?

EDIT: Figured it out and that worked! I finally got my Kindle rooted!!!!! Thank you for the help!

Awesome! Glad it worked. It worked because the findstr execurable is located there.

CannibalAngel · Jul 26, 2012

redbean25 said:
Awesome! Glad it worked. It worked because the findstr execurable is located there.

Thanks again!

kiawin · Jul 27, 2012

tundrwd said:
Finally found a reference to running dpinst32.exe with the /LM option - that installed the KFU drivers.

HOWEVER - it still shows an ADB status of "offline", and Boot status as "unknown" - now where to go?

I had the same issue. Apparently it is owing to our username in Windows has a space (or more). This cause the install_drivers.bat to break.

Solution is simple, edit the install_drivers.bat and include double quotations (" ") to all file paths which has %userprofile% (line 9 & 10)

Uninstall what ever drivers you have installed previously by going to Device Manager, go to Android Phone and uninstall it.

Re-run install_drivers.bat and after that execute run.bat.

That should work

raywaldo · Jul 27, 2012

simple solution that I missed!

kiawin said:
I had the same issue. Apparently it is owing to our username in Windows has a space (or more). This cause the install_drivers.bat to break.

Solution is simple, edit the install_drivers.bat and include double quotations (" ") to all file paths which has %userprofile% (line 9 & 10)

Uninstall what ever drivers you have installed previously by going to Device Manager, go to Android Phone and uninstall it.

Re-run install_drivers.bat and after that execute run.bat.

That should work

Great catch! :good:

That is a great tip that a lot of people may need. It could fix some strange problems. Not only on this kit but on a lot of things run from scripts.

jdiamond7 · Jul 28, 2012

I apologize if this has been addressed in a previous post. I have searched the thread and forums up and down and haven't found a solution.

I am having an issue rooting my wife's kindle fire. I am using KFU v0.9.6 to root Kindle Fire version 6.3.1. I previously have rooted mine (months ago) with no issues so I have some experience with this. Bottom line is that everything appears to work except the actual rooting. Drivers load fine, TWRP and FFF install no problem, but I do not get root. Attached is a screenshot of the KFU output.

I even went as far as to try to do the manual root but I get the same error when removing check_rooted, "can't rename '/system/bin/check_rooted' : No such file or directory.

Since I do have FFF and TWRP it would seem to me that I could just flash a pre-rooted system image if I could get my hands on one. I have not been able to find one though.

Anyone have any thoughts?

raywaldo · Jul 28, 2012

jdiamond7 said:
I apologize if this has been addressed in a previous post. I have searched the thread and forums up and down and haven't found a solution.

I am having an issue rooting my wife's kindle fire. I am using KFU v0.9.6 to root Kindle Fire version 6.3.1. I previously have rooted mine (months ago) with no issues so I have some experience with this. Bottom line is that everything appears to work except the actual rooting. Drivers load fine, TWRP and FFF install no problem, but I do not get root. Attached is a screenshot of the KFU output.

I even went as far as to try to do the manual root but I get the same error when removing check_rooted, "can't rename '/system/bin/check_rooted' : No such file or directory.

Since I do have FFF and TWRP it would seem to me that I could just flash a pre-rooted system image if I could get my hands on one. I have not been able to find one though.

Anyone have any thoughts?

I have jelly bean running nicely on my wife's kf.
Check the "android development" forum for roms. I used the eye candy 3.4 version. It works nearly as well as my Nexus 7.
Sent from my Nexus 7 using xda premium

quickbird144 · Jul 28, 2012

raywaldo said:
Great catch! :good:

That is a great tip that a lot of people may need. It could fix some strange problems. Not only on this kit but on a lot of things run from scripts.

kiawin said:
I had the same issue. Apparently it is owing to our username in Windows has a space (or more). This cause the install_drivers.bat to break.

Solution is simple, edit the install_drivers.bat and include double quotations (" ") to all file paths which has %userprofile% (line 9 & 10)

Uninstall what ever drivers you have installed previously by going to Device Manager, go to Android Phone and uninstall it.

Re-run install_drivers.bat and after that execute run.bat.

That should work

I'm a bit slow. Could you elaborate on how to do this exactly?

jdiamond7 · Jul 28, 2012

raywaldo said:
I have jelly bean running nicely on my wife's kf.
Check the "android development" forum for roms. I used the eye candy 3.4 version. It works nearly as well as my Nexus 7.
Sent from my Nexus 7 using xda premium

Thanks for the reply, I should have specified that I need a stock rooted system image. My wife wants to keep her stock OS (God knows why). I also tried to flash the nfx-update-kindle-6.3.1 update but that didn't seem to give me root either.

quickbird144 · Jul 28, 2012

Nvm got it!

AndroidLover813 · Jul 28, 2012

Rooted My Amazon Kindle Fire

Just wanted to express my thanks to the developers of this Utility. If all instructions are follwed to the tee, you wont have a problem. I'm uploadinding this pick to prove root access on my Kindle Fire:....
Anyway!!!!s good luck and happy flashing!!!!

jdiamond7 · Jul 29, 2012

jdiamond7 said:
I apologize if this has been addressed in a previous post. I have searched the thread and forums up and down and haven't found a solution.

I am having an issue rooting my wife's kindle fire. I am using KFU v0.9.6 to root Kindle Fire version 6.3.1. I previously have rooted mine (months ago) with no issues so I have some experience with this. Bottom line is that everything appears to work except the actual rooting. Drivers load fine, TWRP and FFF install no problem, but I do not get root. Attached is a screenshot of the KFU output.

I even went as far as to try to do the manual root but I get the same error when removing check_rooted, "can't rename '/system/bin/check_rooted' : No such file or directory.

Since I do have FFF and TWRP it would seem to me that I could just flash a pre-rooted system image if I could get my hands on one. I have not been able to find one though.

So I was finally able to gain root access to my wife's KF. I had first tried flashing several pre-rooted stock system images with no luck. I even flashed an old OS version and tried Burritoroot and it still didn't work!

Finally I found this archived thread and found that others had experienced this as well. I followed the instructions to flash eldarerathis's stock rooted with insecure boot image and it worked!

Unfortunately the ROM's version was 6.3 and no sooner had I booted into it then the device immediately rebooted and updated to 6.3.1. I had lost root access before I was able to do anything! I then tried to use KFU to root again and this time it worked! I now have a rooted 6.3.1 on my wife's device.

Thanks Vashypooh, eldarerathis and all the other devs for your awesome work!

ProfEngr · Jul 29, 2012

You could try the modaco roms. I'm running that as the alternate with NRG rom via dualboot.

Sent from my Thunderbolt using one opposable thumb.

TheYar · Jul 30, 2012

Another user needing help

I'm fairly experienced with Windows drivers and with Android, including a lot of work with ROMs on Samsungs and Motorolas, but I'm lost now.

Got a new Kindle, got the Utility. Installed drivers fine. Connected Kindle fine. Ran the Utility, rebooted into fastboot (I guess), and now nothing.

The Kindle will only say "kindle fire" on the screen. I can turn it off by holding the button for a long time, but that's it.

Windows will not recognize the device as anything but "unknown device." So of course adb doesn't work and the Utility just says "waiting." I've rebooted the Kindle and PC many times. I've reinstalled the drivers many times. 0x1949 and 0x18d1 are in the .ini file.

When I try to install the drivers manually, Windows says that the driver is not compatible with the device.

Is there any way out of fastboot so I can try to start over? Or is there something else I can look at to get the abd interface back up? All the research I did ahead of time pointed me to this utility as the simple way to root and flash; I'm kinda bummed that I'm now stuck at a bootscreen.

Any help would be appreciated.

a1exus · Jul 31, 2012

Is it ok to update my 6.2 to 6.3.1 and then do all good stuff: root / unlock / boot recovery / etc

TheYar · Jul 31, 2012

AndroidLover813 said:
Just wanted to express my thanks to the developers of this Utility. If all instructions are follwed to the tee, you wont have a problem. I'm uploadinding this pick to prove root access on my Kindle Fire:....
Anyway!!!!s good luck and happy flashing!!!!

I followed instructions precisely, and have been bricked for hours now.

The method described in the OP relies on you being able to successfully start up a new ADB driver upon reboot of the Kindle. Many people experience problems with this, which results in what I hope is only a soft brick, but so far I have been unable to resolve it. As always, proceed at your own risk. In my opinion, the OP needs to be updated with more than just the standard disclaimer language, and instead point out that numerous people have reported fairly serious failures when attempting to connect back to the Fire once it has entered fastboot.

EDIT: After a lot of help and a lot of tinkering on my own, I got back into normal booting. I can't be certain what fixed it, but it involved manually deleting a lot of driver information from /Windows and from device manager, installing the fastboot interface driver manually within 5 seconds of booting the KF (that was kinda tricky and involved rebooting it a 2nd time in the middle of the driver install process), and then even though fastboot didn't seem to see the device, issuing manual fastboot commands to reboot normal anyway. Success.

drink · Jul 31, 2012

TheYar said:
I followed instructions precisely, and have been bricked for hours now.

I have the same booting forever issue ((

UPD:
Resolved! I just installed permanent root despite ADB Status = offline in kindle utility.

TheYar · Aug 1, 2012

drink said:
I have the same booting forever issue ((

UPD:
Resolved! I just installed permanent root despite ADB Status = offline in kindle utility.

Good. It seems that once you have an ADB Interface or Fastboot driver up and running without errors, but you still can't see the device with adb or fastboot, then you can either a) completely uninstall and reinstall the driver while the device is still plugged in and running and see if that works, or b) attempt to issue scripted or manual fastboot/adb commands anyway and see if they work, despite the device still failing to respond to a "devices" query. Either of these methods seems to have intermittent success.

The main trick I discovered that helped me is that in some cases you need to time your driver installation so that it completes within like 4 seconds of plugging in the cable. Fastboot won't let driver communications start up except for like within the first few seconds, and if you miss that timeslot, Windows is likely to establish a bunk driver for the device that will persist every time you plug it in afterwards.

[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only]

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts