about an hour of operation is blocked twice. but I installed superuser and super su again and now it works perfectly, probably not installed correctly or installation order was not correct and perhaps because of it to be blocked @ prokennexusa thank you very much
[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version
- Thread starter prokennexusa
- Start date
about an hour of operation is blocked twice. but I installed superuser and super su again and now it works perfectly, probably not installed correctly or installation order was not correct and perhaps because of it to be blocked @ prokennexusa thank you very much
Just had to jump back in the thread to say a BIG thanks for this tutorial. I was a bit nervous to try it out, but it turned out to be a snap. 100% success!
Root the Kindle Fire HD 8.9 with Windows8 successfully
Thanks for the detail tutorial. I followed the instruction and rooted my kindle fire hd 8.9" successfully.This is my first time to root an Android base device. My platform is Win 8 64bits and Kindle OS 8.1.4.
Thanks for the detail tutorial. I followed the instruction and rooted my kindle fire hd 8.9" successfully.This is my first time to root an Android base device. My platform is Win 8 64bits and Kindle OS 8.1.4.
Last edited:
What could I do if I try the first step several times but kindle 8.9 is still reacting very slow?
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
stefanescupatronu,
You conclusion sounds correct. In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
https://dl.dropbox.com/u/54456659/KFFirstAide64.zip
stefanescupatronu,
You conclusion sounds correct. In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
https://dl.dropbox.com/u/54456659/KFFirstAide64.zip
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
Braves1995,
Great work Braves1995! In the future all these operations are now automated in our new software Kindle Fire First Aide.
In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
Braves1995,
Great work Braves1995! In the future all these operations are now automated in our new software Kindle Fire First Aide.
In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
m44898,
Great work m44898! Yes, this method works beautifully on the Kindle Fire HD 8.9".
In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
m44898,
Great work m44898! Yes, this method works beautifully on the Kindle Fire HD 8.9".
In the future, you may use our software Kindle Fire First Aide to Root the Kindle. Our new software has two methods to Root the Kindle. You are able to Disable OTA, Root, Install Google Play, Install Google Apps and many other functions.
Here is a link to the new software: KFFirstAide32.zip Or KFFirstAide64.zip
Her are the forum notes: Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
chenzhengbin,
That is a sign of incomplete Root, let's have you use our new software to solve the problem. Please follow these instructions.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Note: Do Not forget the semi-colon before the C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
chenzhengbin,
That is a sign of incomplete Root, let's have you use our new software to solve the problem. Please follow these instructions.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAideNote: Do Not forget the semi-colon before the C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
Kindle Fire 2, have previously attempted rooting with partial success, using your guides here at XDA, decided to try out FirstAide today (no factory cable (ordered and arrived in UK, but I'm in Kazakhstan for now), so only using options open to those of us with normal USB cables.
I think the FirstAide package could do with a little better error catching btw, I tried it for the first time, and qith a few steps, final message doesn't reflect errors that occurred.
Also, I think you need to add a reboot step after adding FirstAide's directory to the path statement.
Option 24 (I decided to try this before attempting rooting methods, as I've never managed to avoid an error about the build.prop (or whichever file it is that is altered?) gives me a dialogue in German asking for a path. I cancelled it as I wasn't sure what is was looking for, FirstAide then asks if I'm sure I want to proceed with the restore function!!!
Anyway, decided to try both rooting options if necessary, some more screen grabs from the process. I tried the first rooting method listed in FirstAide first...
at this point I rebooted the kindle after about 10 minutes...
FWIW, apps that require root already mostly worked, and apps to check your rooted status return mostly positive results, but not 100%, with things like SU not found, but superuser OK, or files/directories(?) being only read-only
Anyway, I rebooted the kindle for good luck, then tried the second rooting method in First Aide...
the process bombed out, the command prompt window just disappears
if I pause it before that, I get what is I'm assuming standard messages...
I don't appear to have gone backwards, but certainly no further forward just yet.
Anyway, thought I'd let you know the results, in case it helps add/modify your script at all.
I think the FirstAide package could do with a little better error catching btw, I tried it for the first time, and qith a few steps, final message doesn't reflect errors that occurred.
Also, I think you need to add a reboot step after adding FirstAide's directory to the path statement.
Code:
*We Are Rebooting The Kindle. The Kindle Will Look Unusual*
*After The Reboot, This Is Normal, This Is The First Step.*
***********************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A024670ALR device
can't find 'Gplay3.8.17.apk' to install
**********************************************
*We Have Applied Part One Of The Upgraded. We*
*Are Now Rebooting. This Is The Second Step.*
**********************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
can't find 'Phonesky.apk' to install
error: device not found
error: device not found
error: device not found
***************************************************
* We Have Applied Part Two Of The Upgraded. We *
* Are Now Rebooting. This Is The Third Step. *
*We Are Now Rebooting The Kindle And Restoring The*
* Appearance. *
***************************************************
error: device not found
***************************************************
* The Install Was A Success! Please Open Google *
* Play Store In The Kindle Apps, Press Continue *
*The Store May Close, This Is Normal. Open Google *
*Play Store, Wait 2 Minutes For Everything To Sync*
* Then Close Google Play Store. Wait 1 Minute And *
* Open Google Play Store Again, Then Wait Another *
* 2 Minutes, Then Close Google Play Store Again *
* Waiting Another Minute. That Is It, Google Play *
* Store Is Installed And Upgraded To 3.10.10 *
***************************************************
ECHO is off.
Press any key to continue . . .Option 24 (I decided to try this before attempting rooting methods, as I've never managed to avoid an error about the build.prop (or whichever file it is that is altered?) gives me a dialogue in German asking for a path. I cancelled it as I wasn't sure what is was looking for, FirstAide then asks if I'm sure I want to proceed with the restore function!!!
Anyway, decided to try both rooting options if necessary, some more screen grabs from the process. I tried the first rooting method listed in FirstAide first...
Code:
*Please Make Sure ADB Is Enabled On The Kindle By Going To*
* The Kindle Menu More - Security - Enable ADB (Turn On) *
*And You Have The Kindle Plugged In To USB Using A Normal *
* USB Cable To The Computer, NOT The Factory USB Cable *
***********************************************************
Press any key to continue . . .
************************************************
* OK Here We Go, We Are Beginning The Process! *
************************************************
****************************************************
*We Are Now Prepping The Kindle, Please Wait.......*
****************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A024670ALR device
******************************************************
*We Are Now Beginning The Root Process, Please Wait. *
*During The Upgrade The Kindle Will Look Unusual, Do *
*Not Worry Or Interrupt The Install Process Once The *
*Install Starts. Make Sure The Kindle Is Plugged Into*
* USB, Are You Ready? *
******************************************************
Press any key to continue . . .
******************************************************
*Here We Go, We Are Now Prepping The Kindle To Accept*
* An Automated Install. *
******************************************************
**********************************
*We Are Now Rebooting The Kindle.*
**********************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/system/bin/sh: cannot create nul: Read-only file system
***********************************************************
*We Are Rebooting The Kindle. The Kindle Will Look Unusual*
* After The Reboot, This Is Normal. *
***********************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
*********************************************************
*We Are Now Testing To See If We Have The Proper Access.*
*********************************************************
The system cannot find the file specified.
Code:
root@android:/ #
*******************************************************
*Success! We Are Now Installing The SU Binary.........*
*******************************************************
error: device not found
error: device not found
error: device not found
'db' is not recognized as an internal or external command,
operable program or batch file.
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
***************************************************
*OK, We Are Done With The Binary, Now We Are Going*
* To Reboot The Kindle. *
***************************************************
error: device not found
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
*****************************************************
*We Will Now Test The SU Binary.....Please Wait.....*
*****************************************************
The system cannot find the file specified.FWIW, apps that require root already mostly worked, and apps to check your rooted status return mostly positive results, but not 100%, with things like SU not found, but superuser OK, or files/directories(?) being only read-only
Anyway, I rebooted the kindle for good luck, then tried the second rooting method in First Aide...
the process bombed out, the command prompt window just disappears
if I pause it before that, I get what is I'm assuming standard messages...
Code:
***********************************************************
*Please Make Sure ADB Is Enabled On The Kindle By Going To*
* The Kindle Menu More - Security - Enable ADB (Turn On) *
*And You Have The Kindle Plugged In To USB Using A Normal *
* USB Cable To The Computer, NOT The Factory USB Cable *
***********************************************************
Press any key to continue . . .
************************************************
* OK Here We Go, We Are Beginning The Process! *
************************************************
*******************************************************
* We Are Checking The Kindle Fire To Make Sure It Is *
* Compatible With This Method Of Rooting. *
* We Are Now Waiting For The Kindle To Show Up In ADB *
* Please Make Sure You Have The ADB Driver Installed *
* Make Sure ADB Is Enabled Under More+ Security *
*******************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.I don't appear to have gone backwards, but certainly no further forward just yet.
Anyway, thought I'd let you know the results, in case it helps add/modify your script at all.
Re blocking OTA Amazon updates, another option to try is installing DroidWall, and then only tick the applications you specifically want to allow access to the internet.
FWIW, be careful... I allowed Google Play app, forgot all about the firewall TBH, then wondered why updates were failing. Other services must be enabled I'm assuming. HOWEVER, one thing to consider is that droidwall may not be 100% effective - Google Play based app updates would sometimes get ~700kb downloaded before they failed.
FWIW, be careful... I allowed Google Play app, forgot all about the firewall TBH, then wondered why updates were failing. Other services must be enabled I'm assuming. HOWEVER, one thing to consider is that droidwall may not be 100% effective - Google Play based app updates would sometimes get ~700kb downloaded before they failed.
adb server out of date - killing
Many thanks for all your work and help! This KF First Aide tool looks amazing, though I couldn't get it to work for me. Every time I tried to perform any action, I got the "adb server out of date" error. I tried updating the adb files to the ones dated 12/28, but no luck. I've followed every step in the guide, so I don't know what else to do, maybe I'm just too noob for the noob guide.
Though I did manage to root my wife's KF2 with another guide and then used the manual options in your google play, disable OTA, and go launcher guides to turn it into a pretty awesome tablet. So thanks again!
Many thanks for all your work and help! This KF First Aide tool looks amazing, though I couldn't get it to work for me. Every time I tried to perform any action, I got the "adb server out of date" error. I tried updating the adb files to the ones dated 12/28, but no luck. I've followed every step in the guide, so I don't know what else to do, maybe I'm just too noob for the noob guide.
Though I did manage to root my wife's KF2 with another guide and then used the manual options in your google play, disable OTA, and go launcher guides to turn it into a pretty awesome tablet. So thanks again!
Last edited:
I disabled OTA updated followed by instructions in OP but after I reboot kindle it updated to new version and I had to root it again. Does anyone know how to disable OTA updates permanently?
Just grab the script from the package and run it with smanager.
Thanks for the helpful tutorial, I've run through all the install (sorting out the paths etc), installed the drivers, run first aide, but neither root method 20 or 21 have any results, and the kindle 7 HD doesnt get rooted.
I've even tried the alternate drivers and still no progress.
This is the output from first aide
Any help would be greatly appreciated
Cheers
I've even tried the alternate drivers and still no progress.
This is the output from first aide
Code:
* OK Here We Go, We Are Beginning The Process! *
************************************************
****************************************************
*We Are Now Prepping The Kindle, Please Wait.......*
****************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D025A0A024240NSX device
******************************************************
*We Are Now Beginning The Root Process, Please Wait. *
*During The Upgrade The Kindle Will Look Unusual, Do *
*Not Worry Or Interrupt The Install Process Once The *
*Install Starts. Make Sure The Kindle Is Plugged Into*
* USB, Are You Ready? *
******************************************************
Press any key to continue . . .
******************************************************
*Here We Go, We Are Now Prepping The Kindle To Accept*
* An Automated Install. *
******************************************************
**********************************
*We Are Now Rebooting The Kindle.*
**********************************
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/system/bin/sh: cannot create nul: Read-only file system
/system/bin/sh: cannot create /data/local.prop: Permission denied
***********************************************************
*We Are Rebooting The Kindle. The Kindle Will Look Unusual*
* After The Reboot, This Is Normal. *
***********************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
*********************************************************
*We Are Now Testing To See If We Have The Proper Access.*
*********************************************************
The system cannot find the file specified.Any help would be greatly appreciated
Cheers
Can't root kindle fire hd 8.9 with options 15 or 16
I've tried both options. (15) Tells me that /system/bin/su is not found, and while 16 does reboot my kindle into fastboot mode (the kindle screen literally displays 'fastboot' on the screen), nothing happens after that. The only options I see available in (Fastboot) mode are to restore the kindle, among others, and nothing along the lines of "root the kindle", etc.
Perhaps I need superuser/su pre-installed? It appears I would first need root before doing that.
I'll be trying the manual method using ROOT MANY ANDROID later today.
I've tried both options. (15) Tells me that /system/bin/su is not found, and while 16 does reboot my kindle into fastboot mode (the kindle screen literally displays 'fastboot' on the screen), nothing happens after that. The only options I see available in (Fastboot) mode are to restore the kindle, among others, and nothing along the lines of "root the kindle", etc.
Perhaps I need superuser/su pre-installed? It appears I would first need root before doing that.
I'll be trying the manual method using ROOT MANY ANDROID later today.
So, after 10 hours of installing, rebooting, bad results, uninstalling, rebooting, reinstalling, bad results, etc... I am close to suicide. Everytime I attempt the process with some variation that I feel might help, I've explored other root programs and options, but it seems like it is really coming down to the communication between my computer and Kindle via ADB, or rather drivers not being installed correctly.
First off, I am running windows 7 as the administrator (unlocked the profile through computer management). I successfully applied the bcdedit commands disabling integrity checks and testsigning. I added the necessary paths to environmental variables, and I deleted every relevant phantom device. I take it most those pre-requisites are not necessarily order specific, besides that they must be done before rooting and they can all stay constant through my multiple attempts to (re)install drivers correctly.
Now what I've seen with drivers- I've only seen 2 sets of failing results: either I use the Kindle_Fire_ADB_driver.exe (Choice 1) and in Device Manager I see "ADB composite whatever" under Android Phone and I see "Kindle" under Portable devices, but there is no Kindle tree with an ADB device under it.
Or, I could use the updated KindleDrivers.exe (Choice 2) and first I see in Device Manager my Kindle under Portable devices, but there is no ADB device, unless I update the drivers, use the "usb_driver" folder and I can see "Kindle ADB composite device" just under the Kindle tree, nothing in Portable Devices (which means I can't explore the kindles files through my computer either).
Now, if I do Choice 1, and I try to use KFFirstAide, I can run option 11, or option 15 and I see a device connected through ADB with the necessary code, but when I try to follow through I get messages saying "/system/bin/sh su: : not found" and it fails. I also tried option 20, and I also got error messages where objects in "/system..." were not found or not accessible. My Kindle is responding to KFFirstAide rebooting it, but nothing seems to be transferring
Choice 2: I try running option 11 in KFFirstAide, and the devices list is empty.
I've tried my best to troubleshoot where the issue was, but after 10 hours of frustration, I'd be insane to expect any different results by my own methods. Please help! Thanks!
First off, I am running windows 7 as the administrator (unlocked the profile through computer management). I successfully applied the bcdedit commands disabling integrity checks and testsigning. I added the necessary paths to environmental variables, and I deleted every relevant phantom device. I take it most those pre-requisites are not necessarily order specific, besides that they must be done before rooting and they can all stay constant through my multiple attempts to (re)install drivers correctly.
Now what I've seen with drivers- I've only seen 2 sets of failing results: either I use the Kindle_Fire_ADB_driver.exe (Choice 1) and in Device Manager I see "ADB composite whatever" under Android Phone and I see "Kindle" under Portable devices, but there is no Kindle tree with an ADB device under it.
Or, I could use the updated KindleDrivers.exe (Choice 2) and first I see in Device Manager my Kindle under Portable devices, but there is no ADB device, unless I update the drivers, use the "usb_driver" folder and I can see "Kindle ADB composite device" just under the Kindle tree, nothing in Portable Devices (which means I can't explore the kindles files through my computer either).
Now, if I do Choice 1, and I try to use KFFirstAide, I can run option 11, or option 15 and I see a device connected through ADB with the necessary code, but when I try to follow through I get messages saying "/system/bin/sh su: : not found" and it fails. I also tried option 20, and I also got error messages where objects in "/system..." were not found or not accessible. My Kindle is responding to KFFirstAide rebooting it, but nothing seems to be transferring
Choice 2: I try running option 11 in KFFirstAide, and the devices list is empty.
I've tried my best to troubleshoot where the issue was, but after 10 hours of frustration, I'd be insane to expect any different results by my own methods. Please help! Thanks!
CJM4 - so is your kindle currently working? are you just trying to get root or have the attempts made the kindle unstable?
I had no luck using the first aide tool for rooting. I would stick to the alternative option that is mentioned in the OP.
"1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop"
Im unsure if it makes much difference, but I saw it mentioned before. Make sure you are not using a usb3 port to connect your cable.
Also make sure you are right clicking on the .bat files and running as admin from there.
I had no luck using the first aide tool for rooting. I would stick to the alternative option that is mentioned in the OP.
"1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop"
Im unsure if it makes much difference, but I saw it mentioned before. Make sure you are not using a usb3 port to connect your cable.
Also make sure you are right clicking on the .bat files and running as admin from there.
After so many attempts I can't say what finally worked. My Kindle was stable through all the failures (though it moved slow at times) and I think I ended up using Root_with_Restore_by_Bin4ry_v18 and it did finally work. It may have been that I was trying through a USB 3.0 port. I did use KFFirstAide to get rid of amazon ads and to turn off the automatic updates (I can see the ads are gone, but I am skeptical about the auto update).
Now it's working beautifully. Cheers!
Kindle Fire HD and 2 First Aide - Release Version 40 02/18/2013 at 23:57
CJM4,
When you have time download the latest version, we fixed the issues with the Rooting. All option work beautifully now.
Software 02/18/2013 at 23:57 the current version is Rev 40:
Kindle Fire First Aide Revision 37 Minor Release - Download the complete package:
Kindle Fire First Aide Microsoft Windows 32-bit Version: KFFirstAide32.zip
Kindle Fire First Aide Microsoft Windows 64-bit Version: KFFirstAide64.zip
Kindle Fire First Aide Microsoft Windows Universal Package: KFFirstAide.zip
Please extract the package as C:\KFFirstAide - BE SURE TO REMOVE THE EXTENSION OF 32 OR 64, since these packages will extract with numbers on the end.
Be sure to add the Windows Environment Variable of C:\KFFirstAide to the Path Statement, if you require instructions please go to the first page of this thread.
Be sure to REMOVE the Android SDK, this will cause the process to fail.
Finally, it is very important to make sure you are using the latest version of Java SE:
Java SE Development Kit 7u13
CJM4,
When you have time download the latest version, we fixed the issues with the Rooting. All option work beautifully now.
Software 02/18/2013 at 23:57 the current version is Rev 40:
Kindle Fire First Aide Revision 37 Minor Release - Download the complete package:
Kindle Fire First Aide Microsoft Windows 32-bit Version: KFFirstAide32.zip
Kindle Fire First Aide Microsoft Windows 64-bit Version: KFFirstAide64.zip
Kindle Fire First Aide Microsoft Windows Universal Package: KFFirstAide.zip
Please extract the package as C:\KFFirstAide - BE SURE TO REMOVE THE EXTENSION OF 32 OR 64, since these packages will extract with numbers on the end.
Be sure to add the Windows Environment Variable of C:\KFFirstAide to the Path Statement, if you require instructions please go to the first page of this thread.
Be sure to REMOVE the Android SDK, this will cause the process to fail.
Finally, it is very important to make sure you are using the latest version of Java SE:
Java SE Development Kit 7u13
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
100This is a simple Step-by-Step guide on How To: How To: Root the Kindle Fire 7" HD, Kindle Fire HD 8.9" and Kindle Fire 2 with Windows - Noob (Simple) Version. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3. We attempt to keep this tutorial updated regularly - adding information from the end users experience. We have recently upgraded the storage servers to increase uptime, you now have two options for the downloads both are ad free. Option one is a Dropbox Storage Server and Option two is a Ubuntu One Storage Server, if one is under maintenance you may use the other download link. When you are done with the tutorial, please take the time to post feedback, this is very important to us - without your feedback, we have no way of knowing if we are doing our job. Finally, if you feel we did a decent job, please think about donating to us using the "Donate to Me" button - this is how we make a living, without your kind donations we would no longer be able to do this for a living.
Prerequisites:
1. Software: Windows XP, 7 or 8 Workstation 32bit or 64bit
2. Hardware: Free USB 2.0 or Greater Port
3. Kindle Fire HD 7", Kindle Fire HD 8.9" or Kindle Fire 2 7"
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://xdaforums.com/showthread.php?p=36373627
It is important that you use our Utilities since we have modified the ADB daemons plus we did little tweaks in some of the batch files. PLEASE USE OUR UTILITIES, WE ARE RECEIVING A NUMBER OF FAILURES CAUSED BY USING ANOTHER PARTIES UTILITIES. IF YOU FOLLOW THE STEPS BELOW, EXACTLY, YOU HAVE A 99% CHANCE OF SUCCESS.
Unplug the Kindle from USB.
A) Although the processes do not use Java directly, the software does call to some Java API's so we need to make sure Java is updated to the latest version. Please go to Oracle's site here: Java SE Development Kit 7u13 download and install Java SDK 32-bit or 64-bit. Reboot your computer after installing the Java update.
B) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle, move on to Main Step C
Note: Please remove any old or outdated drivers by following the instructions in Post #361 here: http://xdaforums.com/showpost.php?p=37733595&postcount=361
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers(Dropbox) or Kindle Fire ADB Drivers(Ubuntu One)
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Please open an Administrative CMD Prompt and enter:
Reboot the Computer to apply the above command.Code:bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS bcdedit -set TESTSIGNING ON
Extract the Kindle Fire ADB drivers.zip to your desktop.
1. Unzip Kindle Fire ADB drivers.zip to Kindle Fire ADB drivers on your desktop.
2. Click windows start button.
3. Next choose Search, in the "Search programs and files" box type "cmd" (don't hit enter or search).
4. The program "cmd.exe" should be listed at the top. Right click that and select "Run As Administrator".
5. Navigate to the Kindle Fire ADB drivers.exe or KindleDrivers.exe using the DOS Command cd.
6. Next, the install will begin, allow the install to complete.
7. While the driver is installing. Go to the Kindle unlock if locked.
8. Pull down the upper bar. Select "More".
9. Now Select the "Security" Tab.
10. In Security is an option to: Enable ADB
11. Select "On" to Enable ADB on the Kindle
If not, We have an alternative driver here: usb_driver(Dropbox) or usb_driver(Ubuntu One)
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
C-1) The next steps are used to Root the Kindle - Preferred Method (Automated Version)
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Note: Do Not forget the semi-colen before the C:\KFFirstAideCode:;C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
You may view the Kindle Fire First Aide Forum Notes here: http://xdaforums.com/show....php?t=2096888
C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version):
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Win32 or Win64 folder.
Next Single Left Mouse Click on the Win32 or Win64 folder tool-bar.
This highlights the Win32 or Win64 folder.
Note: Make sure none of the files within the Win32 or Win64 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.Code:RunMe.bat
Root Step 2: When the Kindle reboots it may react VERY slow, this is normal - leave it alone. Immediately proceed to Step 1 again. If the Kindle reboot normally and appears normal, then proceed to Step 3 you are almost done.
Root Step 3: Download suchecker.apk from here: Root Checker Basic(Dropbox)
Root Step 4: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download
Root Step 5: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install
Root Step 6: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.
You should now have root AND if this is true your ADB communication is also functional.
D) Finally, let's disable the Amazon OTA (Over The Air) Updates so your hard work is not destroyed.
OTA Step 1: Open Kindle Fire First Aide - Select Option 14 to Disable OTA.
Note: You may still install the updates manually after you have read the install notes and know what to expect. The updates and manual install instructions can be found on Amazon Support here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350
E) Finally drop to an Administrative CMD and enter:
Reboot the computer to apply the above command.Code:bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS bcdedit -set TESTSIGNING OFF
When you run Root Checker, the output should be similar to:
Next, move onto our How to: Install Google Play Step-by-Step Thread5ADB Communication Issues
Once you plug in the Kindle, it takes up to 2 minutes for Windows to detect it. So having said this *daemon started successfully*
Should not be displayed for longer than 2 minutes.
Where did you download the Utilities? From us or the developers? Our utilities use new updated adb.exe daemons
dated 11/05/2012 11:06AM
If the adb.exe has the correct date stamp, then make sure you are following our instructions on how to open a command
prompt. If you are following the instructions exactly then....
You must have Windows 7 which requires you to open an Administrative Prompt by choosing Run as: Administrator when
opening the CMD Shortcut.4How to Remove Old Device Drivers from Vista & Windows 7
Skirball,
The key when removing a driver is to check the box next to "remove the driver from the driver database" - here is a how to for other people having the same issue.
First make sure the Kindle is unplugged from USB.
One of the most annoying issues with Windows is when your hardware manufacturer fails to provide a proper driver for the operating system. Even when you do find the proper driver, sometimes the manufacturer releases an updated version which you then need to install on top of the older version. As if that's not enough, every version of Windows from the past 10 years or so, including server versions will retain the older driver binaries even if you upgrade or change hardware.
There is a logic behind this behavior. If, for example, you're using a removable USB disk drive, which has once been plugged in, Windows will install the appropriate driver for it. When you eject that drive, Windows retains the drivers so that they will be ready the next time you connect the drive.
But what about replacing a video adapter? A network interface card? A printer that has been thrown away? What about working with a laptop that you once used to connect to an external device, and has not used that device since? What happens to that driver if you never connect that device to your computer again?
With time, your computer will gather an increasing number of unused drivers that not only take space on your hard disk, having been still installed, they might cause problems if they are somehow enabled. In some cases they can also cause hardware conflicts. And to make things worse, when you do want to use the same device after a long period of inactivity, even if you re-install an updated version of the driver, Windows might still use the older version of it.
So how do you remove these old and un-used drivers? Let me show you.
By default, Device Manager will only show you the devices it's currently using.
What you need to do is to configure Device Manager to show all those non-present device drivers, sometimes known as "phantom devices".
1. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties.
Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
2. Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
3. In the System Variables section click on the "New" button.
4. In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1.
Click Ok.
5. In the Environment Variables window notice how the new variable appeared in the System Variables section. Click Ok.
6. In the System Properties window click Ok.
7. Log off and log on.
8. Open Device Manager (Control Panel > System > Hardware > Device Manager).
9. From the View menu click Show Hidden Devices and notice the change.
10. Now begin to remove each Phantom Device by Right Mouse Click Uninstall Device or Remove Device, be sure to check the box "Remove Driver From Windows" if offered the option, as you remove each Phantom Device.3Feedback
OHMY!! I wish i could hug you right now,
I finally got it rooted after 3days
just had to download SDK and install the driver that way through the video and reboot pc/kindle and BAM!! ROOOOOTEED. lol
3 days of trying to figure this out, finally paid off....thank you. :laugh:[/QUOTE]
Good Job! The best hug you can give us is to click on the Thanks meter to the Right and
Rate the Thread at the top. I knew you could do it!2ADB Communication Issues
Please verify the date of the adb.exe daemons. Reply back with the date if the daemon in Root_with_Restore_by_Bin4ry_v17Root_with_Restore_by_Bin4ry_v17 Stuff folder.
Next download this mini-test utility: https://dl.dropbox.com/u/54456659/ADB%20Update.zip to your desktop
Unzip ADB Update.zip to your desktop
Open the ADB Update folder on your desktop
Make sure the Kindle is still plugged into USB.
Double Mouse Click and Open the ADB Update folder.
Next Single Left Mouse Click on the ADB Update folder toolbar.
This highlights the ADB Update folder.
Note: Make sure none of the files within the ADB Update are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:adb kill-server adb start-server adb devices
Respond with the results.
