[7" Kindle Fire HD General] SilentlyScreaming:
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.

*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...

*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.

at this point I rebooted the kindle after about 10 minutes...

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...

***********************************************************
*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.