[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version

In your opinion, when looking back at this thread, how easy were the instructions?


  • Total voters
    311
Search This thread
Lately we have been seeing a extremely large number of people experiencing install failures. This is NOT due to the software of it's code. The reason for the failure is due to a Superuser Permission problem. When you run each option you must watch the Kindle closely during the first set of commands, this is CRITICAL! You will see a Superuser Request on the Kindle directly, you MUST click on Allow or Grant otherwise the entire install will fail. Usually once you have granted the first request the rest of the commands will execute as expected.

So, if you have an install failing like Google Apps (Which has successfully worked over the last 60 days), this is due to not responding to the Superuser Popup or Request on the Kindle. We have been looking at options to fully automate these processes without having to deal with the Superuser security window. After several hours OS testing there is no way around this issue, you must pay close attention to the Kindle otherwise all the operations will fail. There is a slight chance some people may have inadvertently click on Disallow or Deny - this will cause every install to fail until we reset the Superuser account. The way to determine if you have the proper permissions to run our software on your Kindle is to run the following command:

Code:
adb wait-for-device
adb shell su -c "ls /system/app"

If the command fails, you have a Superuser permission issue.

Pay attention to the Kindle, you will see a Superuser request, click on ALLOW! Once you allow the ADB Shell access future requests should run fine and our software will no longer fail. You will see a small popup stating "ADB Shell has been granted superuser permissions for interactive shell". Also, open SuperSU or Superuser, look at the Logs after the above command you should see ADB Shell was granted Superuser Permissions. If you look under the SuperSU or Superuser Apps Tab, you should see "ADB Shell #" - if you do not see either entry then Superuser is denying the ADB Request and will need to be reset. Post a response, advising us what version of Superuser you are using, we will respond with a fix.

I read through the above and I completely understand what you're saying. However, my problem isn't a Superuser Permission problem. The above adb shell su -c "ls /system/app" runs perfectly, and returns the full output of the /system/app directory, but yet I still have problems with the script when trying to write to the /system partition. The command to mount /system as rw doesn't seem to be working properly on my system. I've tried a couple alternate syntax formats for the mount command, and even just the adb remount command alone, but am still unable to mount /system as rw from adb. I also verified that I can use adb push to push files to other directories, just not to /system.

Yes, I did see a prompt for ADB Shell the first time I ran an adb command from KFFirstAide and it is now properly authorized and listed in SuperSU. I've attached a screen shot of that, and the output from my ls command below, just to back up what I'm saying.

I'm using a Kindle Fire HD 8.9, perhaps that requires slightly different commands to mount /system as rw.

I also noticed that the script is still doing "cd /data/local/tmp/; rm *" (line 4384 in the Google Apps installation subroutine) and ""rm -r /data/local/tmp" (line 4399), while other parts of the script create a symlink from /data/local/tmp to /data. Since the script exits leaving that symlink in place, and you're not checking for it prior to issuing the forementioned delete commands, you are creating the potential to completely wipe out the /data directory here!

Edited to add: whoops forgot to attach the screen shot. Not sure it's really needed anyway other than to prove that ADB Shell has been granted Superuser permission by the SuperSU app.


Code:
C:\KFFirstAide>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0CA0604252201M0        device

C:\KFFirstAide>adb wait-for-device

C:\KFFirstAide>adb shell su -c "ls /system/app"
APNWidget_Kindle-ATT-1-0-26.apk
APNWidget_Kindle_BaseRoot-1-0-5.apk
ATSystem.apk
ATVAndroidClient.apk
AccountAndSyncSettings.apk
AmazonGamesService.apk
AmazonPlatform-release.apk
Amazon_Apps.apk
AppWidgetPicker.apk
ApplicationsProvider.apk
ApplicationsProvider.odex
AudibleForAndroid-otter-unsigned.apk
BackupRestoreConfirmation.apk
BackupRestoreConfirmation.odex
Bluetooth.apk
Bluetooth.odex
CMS-Service.apk
CSApp-unsigned.apk
Calendar.apk
CalendarProvider.apk
Camera.apk
Camera.odex
CertInstaller.apk
CertInstaller.odex
ChromeBookmarksSyncAdapter.apk
Cloud9-release-unsigned.apk
Cloud9AndroidSystemBrowserProvider.apk
Contacts-release.apk
ContactsProvider-release.apk
DefaultContainerService.apk
DefaultContainerService.odex
DeviceControlService.apk
DeviceControlService.odex
DolbySurround.apk
DolbySurround.odex
DownloadProvider.apk
DownloadProvider.odex
DownloadProviderUi.apk
DownloadProviderUi.odex
DpContacts-release.apk
DrmProvider.apk
DrmProvider.odex
Email.apk
Exchange.apk
FaceLock.apk
Gallery2.apk
Gallery2.odex
GalleryGoogle.apk
Gmail_4.2.1.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GoogleLoginService.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
Google_Voice_0.4.2.72.apk
HTMLViewer.apk
HTMLViewer.odex
IMDb-release-unsigned.apk
IvonaTTS.apk
KCPTutorial.apk
KeyChain.apk
KeyChain.odex
KindleForOtter.apk
KindleSafeMode.apk
KindleStoreWebApp-release-unsigned.apk
LatinIME.apk
LatinIME.odex
Launcher.apk
LiveWallpapersPicker.apk
MarketUpdater.apk
MediaProvider.apk
MediaProvider.odex
MediaUploader.apk
MobileAuthenticationPlatformAndroid-unsigned.apk
MyAccount-unsigned.apk
Nova_Launcher.apk
OOBE-unsigned.apk
OfficeSuite.apk
OneLensAndroidClient.apk
OneTimeInitializer.apk
OtterTutorial.apk
PackageInstaller.apk
PackageInstaller.odex
ParentalControls.apk
ParentalControls.odex
Phone.apk
Phone.odex
PicoTts.apk
PicoTts.odex
Provision.apk
Provision.odex
QuickSearchBox.apk
QuickSearchBox.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
SetupWizard.apk
SharedStorageBackup.apk
SharedStorageBackup.odex
SoftkeyBar.apk
SoftkeyBar.odex
Stk.apk
Stk.odex
Superuser.apk
Swype.apk
SystemUI.apk
SystemUI.odex
TalkBack.apk
TalkBack.odex
TelephonyProvider.apk
TelephonyProvider.odex
UnifiedSearch.apk
UnifiedSearch.odex
UniversalSearch.apk
UserDictionaryProvider.apk
UserDictionaryProvider.odex
Vending.apk
VoiceSearch.apk
VpnDialogs.apk
VpnDialogs.odex
WAPPushManager.apk
WAPPushManager.odex
WebRuntime-release-unsigned.apk
Windowshop.apk
YahooSync.apk
ZicoClient-release-unsigned.apk
air_runtime_dcts.apk
amazonmp3-unsigned.apk
com.amazon.dcp.apk
com.amazon.sso.apk
dtcp_apk.apk
wanpeek_1200010.apk


C:\KFFirstAide>adb shell su -c "/data/local/tmp/busybox mount -o remount,rw /system"

C:\KFFirstAide>adb push FaceLock.apk /system/app/FaceLock.apk
failed to copy 'FaceLock.apk' to '/system/app/FaceLock.apk': Permission denied
 
Last edited:
  • Like
Reactions: markbc01

ejbmvp

Senior Member
Nov 30, 2011
253
41
Grand Rapids, MI
i can also say i have the same problem others are mentioning about getting permission denied when using the software and also trying to push the file. i have verified superuser access by looking at the app and also watching it pop up on the kindle screen.
 

SilentlyScreaming

Senior Member
Feb 7, 2008
201
19
Astana
chrismerriman.com
+1

I've mentioned it in the noob guide to kindle rooting thread, and was met with "you're not following instructions somewhere" response.

I've also previously brought up the issue that no errors appear to be caught, leading to false "All OK, operation completed" type messages.

I've confirmed everything I can think of is set correctly, and I've got what appears to be partial root, but there are certainly a number of us receiving error messages that indicate problems with mounting partitions as RW. I can mount them manually with other apps, and I can create folders where the scripts has problems, but even attempting to send adb scripts one line at a time seem to fail when I use your batch file as a template.

Happy to help with bug finding, but I think we need recognition that, however limited the applicable scenarios are, problems are occurring. We're not all noobs who've never tried things like this before. Some of us users, whilst very capable of making simple mistakes, do tech support for a living, so haven't necessarily forgotten to install drivers/amend configs/follow instructions step by step :)
 

field3d

Senior Member
Oct 10, 2009
67
1
Brick Kindle 8.9 maybe?

I opened this post: http://xdaforums.com/showthread.php?p=38337627#post38337627
All the tools to root were KFFirstAide and qemu. But now how can I recover to stock my kindle because if you see when I used the default to factory option inside kindle that deleted me the ADB USB option and I can´t connect to USB in that mode I just can see like a photo device how can I revive my tablet. Thank you
 

colinrichardson

New member
Feb 18, 2013
2
0
an update

Hi prokennexusa,

I just wanted to provide an update:

I tried using KFFA (I updated the version each time a new one was posted) operations 20 and 21 at least twenty times each with various combinations of repetition, full reboots of PC and Kindle, etc. I also ran a number of other tools within KFFA that were suggested as tests to see how the device responded. I was never able to successfully root the device (KF HD 7) and consistently had access prohibited/failed to write errors.

Out of desperation, I tried the 2-step method outlined in this thread: http://xdaforums.com/showthread.php?t=2035334 , and it worked immediately. I hadn't seen the superuser permission screen in any of my KFFA attempts, but it popped up immediately with the less-automated method.

I then tried some of the other KFFA tools, but they did not seem to work (google play definitely didn't). I was also able to install google play store, etc, using the manual method.

I really have no idea what's wrong with the way I was trying to use KFFA, but thought that an update might be useful to you- I'll copy some of the output from some failed attempts below.

I know I was probably missing fundamental and that dealing with people in my situation is probably really exhausting. I really appreciate the work you're doing.

- Colin


Code:
OPTION 20:


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

******************************************************
* If The Kindle Hangs At This Point, There May Be A  *
*  Driver Problem Or Kindle ADB Is Not Turned On.    *
******************************************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: not found

********************************************
*Here We Go, We Are Now Prepping The Kindle*
********************************************

adb server is out of date.  killing...
* daemon started successfully *
failed on '/data/local/tmp' - Permission denied
link failed File exists

**********************************
*We Are Now Rebooting The Kindle.*
**********************************

Press any key to continue . . .

(MISSED A FEW LINES)




****************************************************************
* You Did Pass Step 1, We Were Unable To Exploit The Kindle So *
*Root Failed. Please Run Option 18 Again, Sometimes The Process*
*Need To Be Repeated Several Time Before You Will Successfully *
* Root The Kindle. If This Method Fails More Than 5 Times Try  *
* Option 21 Which Uses A Different Method To Root The Kindle.  *
****************************************************************

Press any key to continue . . .


OPTION 18:



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

*******************************************************
*We Are Now Installing Google Play Store, Please Wait.*
* During The Install 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?                     *
*******************************************************

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: not found

Press any key to continue . . .

******************************************************
*                  Phase One                         *
*Here We Go, We Are Now Prepping The Kindle To Accept*
*          A Google Play Store Install.              *
******************************************************

/system/bin/sh: su: not found
failed to copy 'busybox' to '/data/local/tmp/busybox': Permission denied
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found

**********************************
*We Are Now Rebooting The Kindle.*
**********************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

(MAY HAVE MISSED OR ADDED A LINE HERE)

/system/bin/sh: su: not found

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

/system/bin/sh: su: not found
2123 KB/s (19576 bytes in 0.009s)
/system/bin/sh: su: not found
/system/bin/sh: su: not found

********************************************************
*We Are Now Installing Five Google Play Store Services.*
********************************************************

/system/bin/sh: su: not found
failed to copy 'AccountAndSyncSettings.apk' to '/system/app/AccountAndSyncSettings.apk': R
ead-only file system
failed to copy 'GoogleServicesFramework.apk' to '/system/app/GoogleServicesFramework.apk':
 Read-only file system
failed to copy 'GoogleLoginService.apk' to '/system/app/GoogleLoginService.apk': Read-only
 file system
failed to copy 'NetworkLocation.apk' to '/system/app/NetworkLocation.apk': Read-only file
system
failed to copy 'Vending.apk' to '/system/app/Vending.apk': Read-only file system
/system/bin/sh: su: not found

**************************************************************
*We Are Now Setting Up The Services And Checking Permissions.*
**************************************************************

/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found


****************************************************
*We Are Now Rebooting The Kindle And Restoring The *
*                   Appearance.                    *
****************************************************

/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

*******************************************************
* Please Go To The Kindle Apps On The Device. Launch  *
*  The Old Android Store Accept The License And Add   *
* Your Google Account To The Android Store Then Close *
*The Application. Please Let Me Know When You Are Done*
*******************************************************

Press any key to continue . . .

(WENT TO KINDLE APP STORE AND THERE WAS NO GOOGLE PLAY)


*******************************************************
*We Are Now Upgrading The Android Store To Google Play*
*Store. Here We Go, We Are Prepping The Kindle For The*
* Upgrade And Performing A Reboot. The Upgrade Is A 3 *
*                   Step Process.                     *
*******************************************************

******************************************************
*                  Phase Two                         *
*Here We Go, We Are Now Prepping The Kindle To Accept*
*         The Google Play Store Upgrade.             *
******************************************************

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: not found

/system/bin/sh: su: not found

**********************************
*We Are Now Rebooting The Kindle.*
**********************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found

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

/system/bin/sh: su: not found
failed to copy 'Gplay3.8.17.apk' to '/data/local/tmp/Gplay3.8.17.apk': Permission denied
rm failed for /data/local/tmp/Gplay3.8.17.apk, No such file or directory
/system/bin/sh: su: not found

************************************************
*We Have Applied The Google Play 3.8.17 Upgrade*
*           Rebooting The Kindle.              *
************************************************


* daemon not running. starting it now on port 5037 *
* daemon started successfully *

/system/bin/sh: su: not found
failed to copy 'Phonesky.apk' to '/data/local/tmp/Phonesky.apk': Permission denied
rm failed for /data/local/tmp/Phonesky.apk, No such file or directory
/system/bin/sh: su: not found


***************************************************
* We Have Applied The Google Play 3.10.10 Upgrade.*
*  We Are Rebooting The Kindle And Restoring The  *
*                   Appearance.                   *
***************************************************

/system/bin/sh: su: not found

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: 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 21:



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

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: not found

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

failed on '/data/local/tmp' - Permission denied
link failed File exists

*******************************************************
*We Are Now Rebooting The Kindle. Please Do Not Forget*
*      To Press Any Key So I Can Continue!            *
*******************************************************

Press any key to continue . . .

*  USB Cable To The Computer, NOT The Factory USB Cable   *
***********************************************************

Press any key to continue . . .

*************************************************
*                 Phase One                     *
*   This Is The First Attempt To Exploit The    *
*  Kindle, If This Fails, Which We Are Sure It  *
* Will Fail, We Have A Second Exploit To Run On *
*                The Kindle!                    *
*************************************************

error: device not found
error: device not found

************************************************************
* We Are Rebooting The Kindle. The Kindle May Look Unusual *
* After The Reboot, This Is Normal. Please Do Not Forget   *
*       To Press Any Key So We Can Continue!               *
************************************************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

(MISSED A BUNCH- WENT VERY QUICKLY)




*****************************************************
*   We Are Now Testing Superuser...Please Wait      *
*       This Test May Tak A Few Minutes..........   *
*****************************************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *



****************************************************************
*     Root Failed. Please Run Option 21 Again, Sometimes       *
* The Process Need To Be Repeated Several Time Before You Will *
* Successfully Root The Kindle. If This Method Fails More Than *
* 5 Times Try Option 20 Which Uses A Different Method To Root  *
*                         The Kindle.                          *
****************************************************************

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

***********************************************
* We Are Now Performing A Cleanup Of The Temp *
*  Directory. If you See The Following Error  *
*    The Directory Is Empty. The Error        *
*"rm failed for *, No such file or directory" *
*    Is Expected And Can Be Ignored.          *
***********************************************

/system/bin/sh: su: not found

Press any key to continue . . .
 

lacoursiere18

Senior Member
Jan 9, 2013
4,183
7,001
LbTs
Hey Chris I just wanted to give you a heads up. There are MANY people on the forum reporting of problems after using a rooting tool on this forum about missing navbars and menubars after their rooting process. I have also posted in sparkym3 thread bc I believe you two are the only ones that have an automated root tool.. Maybe just look into it if you have the time..
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide Software - Ibotta App Request

To All -

We just received a PM from one of our members requesting a copy of the Ibotta App. Since we like to post all pertinent PM's to the thread here we go.

Just in case there are other people interested in this cool App here is the link to the latest version of Ibotta:

Ibotta Version 1.3.1.1401 Download Link: https://dl.dropbox.com/u/54456659/com.ibotta.android-1.apk.zip

This is a really cool app, it is an app that sends you money via Paypal for buying items on the Ibotta list. So all you do is bring the Kindle with you shopping, look at the Ibotta list as you are shopping, purchase the items you need in the Ibotta list, then take a picture of your receipt and Ibotta will send you money via Paypal! Just buy, take a picture for cash, we think we could do this for a few dollars each shopping run. It adds up fast.
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide Software - Rooting Problem

To All-

We just received a PM from one of our members, they were having issues Rooting the Kindle. We like to post all pertinent communications since it may help another person. Here we go.

The question was "I have been trying to root this thing for 3 days now...", here is our response:

We are sorry you are having such difficulty with Rooting the Kindle, here is quick instructions and points to look for on the Kindle:

1. Check C:\Program Files\Android do you have this directory? If yes, please change C:\Program Files\Android to C:\Program Files\Android-Bak
2. Use Microsoft search, enter adb into the Search box and click on search. Do you find more than one copy of adb.exe? There sound only be one in C:\KFFirstAide\adb.exe - rename the rest to adb.bak
3. Use Microsoft search, enter fastboot into the Search box and click on search. Do you find more than one copy of fastboot.exe? There sound only be one in C:\KFFirstAide\fastboot.exe - rename the rest to fastboot.bak
4. Check the Kindle Fire, is "Allow installation of programs" ON under More+ Device?
5. Check the Kindle Fire, is "ADB Enable" ON under More+ Security?
6. Plug the Kindle into USB, check the device Manager do you see:
Kindle > Android ADB Interface
Portable Devices> Kindle
7. If NO, unplug the Kindle and install the ADB Driver from Kindle Fire First Aide
8. Check the Device Manager again, do you see the above devices now? If yes, proceed, if no post what you see here in this thread.
9. OK, now you are ready to test ADB Communication, enter the following at C:\Windows\System32:
Code:
adb kill-server
adb wait-for-device
adb devices
10. If you see a serial number, perfect, proceed. If you get an odd error, please post the exact error in this thread. If you errored STOP here until we figure out the problem. If the output was a serial number with NO "killing server, server is out of date...." then proceed.
11. Launch Kindle Fire First Aide, select Option 21 to Root the Kindle. Pay close attention to the software and the Kindle. When you see "press any key" please press any key so the software may continue. At one point you will see the Kindle asking to be RESTORED, please click on the Kindle Fire "Restore", watch the software for press any key and allow the software to continue by "Pressing any key" on your Keyboard.
12. When done you will have Root. Check in the Kindle Apps for SuperSU or Superuser, please click on SuperSU or Superuser to open the software. Lease this window open and enter this command:
Code:
adb kill-server
adb wait-for-device
adb shell su -c "cd /data/local/tmp/; rm *"
Pay close attention to the Kindle, you will see a Superuser Pop-up or Request, be sure to Allow or Grant the request!
13. Next, go back to the Kindle Fire, look in the SuperSU or Superuser logs, do you see:
"ADB Shell #"
Click on the Superuser or SuperSU Apps tab, do you see:
"ADB Shell #"
Perfect, proceed!
14. You have setup the correct permissions on the Kindle and you have Root, you may now proceed to install the rest of the packages using the latest version of Kindle Fire First Aide. Do Google Play Store first.
 

ejbmvp

Senior Member
Nov 30, 2011
253
41
Grand Rapids, MI
To All-

We just received a PM from one of our members, they were having issues Rooting the Kindle. We like to post all pertinent communications since it may help another person. Here we go.

The question was "I have been trying to root this thing for 3 days now...", here is our response:

We are sorry you are having such difficulty with Rooting the Kindle, here is quick instructions and points to look for on the Kindle:

1. Check C:\Program Files\Android do you have this directory? If yes, please change C:\Program Files\Android to C:\Program Files\Android-Bak
2. Use Microsoft search, enter adb into the Search box and click on search. Do you find more than one copy of adb.exe? There sound only be one in C:\KFFirstAide\adb.exe - rename the rest to adb.bak
3. Use Microsoft search, enter fastboot into the Search box and click on search. Do you find more than one copy of fastboot.exe? There sound only be one in C:\KFFirstAide\fastboot.exe - rename the rest to fastboot.bak
4. Check the Kindle Fire, is "Allow installation of programs" ON under More+ Device?
5. Check the Kindle Fire, is "ADB Enable" ON under More+ Security?
6. Plug the Kindle into USB, check the device Manager do you see:
Kindle > Android ADB Interface
Portable Devices> Kindle
7. If NO, unplug the Kindle and install the ADB Driver from Kindle Fire First Aide
8. Check the Device Manager again, do you see the above devices now? If yes, proceed, if no post what you see here in this thread.
9. OK, now you are ready to test ADB Communication, enter the following at C:\Windows\System32:
Code:
adb kill-server
adb wait-for-device
adb devices
10. If you see a serial number, perfect, proceed. If you get an odd error, please post the exact error in this thread. If you errored STOP here until we figure out the problem. If the output was a serial number with NO "killing server, server is out of date...." then proceed.
11. Launch Kindle Fire First Aide, select Option 21 to Root the Kindle. Pay close attention to the software and the Kindle. When you see "press any key" please press any key so the software may continue. At one point you will see the Kindle asking to be RESTORED, please click on the Kindle Fire "Restore", watch the software for press any key and allow the software to continue by "Pressing any key" on your Keyboard.
12. When done you will have Root. Check in the Kindle Apps for SuperSU or Superuser, please click on SuperSU or Superuser to open the software. Lease this window open and enter this command:
Code:
adb kill-server
adb wait-for-device
adb shell su -c "cd /data/local/tmp/; rm *"
Pay close attention to the Kindle, you will see a Superuser Pop-up or Request, be sure to Allow or Grant the request!
13. Next, go back to the Kindle Fire, look in the SuperSU or Superuser logs, do you see:
"ADB Shell #"
Click on the Superuser or SuperSU Apps tab, do you see:
"ADB Shell #"
Perfect, proceed!
14. You have setup the correct permissions on the Kindle and you have Root, you may now proceed to install the rest of the packages using the latest version of Kindle Fire First Aide. Do Google Play Store first.

question based on #2.. i found more than 1 adb.exe. theres 2 in the KFFirstAide folder, one in the main directory and one in C:\KFFirstAide\Qemu
Do i rename the one in Qemu folder?
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version

To All-

Solution found! THANK YOU TO EVERYONE WHO HAS BEEN SO PATIENT WITH US AS WE ARE WORKING TO MAKE THIS DREAM COME TRUE!

WE JUST FOUND THE SOLUTION TO THE PERMISSION DENIED ISSUE. EVERYONE WHO POSTED THE DETAILED OUTPUT HELPED US THANK YOU TO EVERYONE WHO HAS HELPED!!!!!!!!!!!!!!!!!!!

GIVE US ONE HOUR, WE WILL POST THE NEW VERSION REV 51 THAT HAS FINALLY SOLVED THE PERMISSION DENIED ISSUE!!!!

*******************WE WILL HAVE THE NEW VERSION POSTED BY 16:00 PST GMT -8.**********************

WE WANT TO SPECIFICALLY THANK CHERRYPIE WHO HAS BEEN WORKING HARD TO FIND A SOLUTION. THANKS CHERRYPIE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 

AmrBanawan

Senior Member
Nov 26, 2012
245
43
Alexandria
YAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYYYYYYY!!!!!!!!!!!!! :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory: :victory:
 
Last edited:

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
***Kindle Fire First Aide Revision 4.1.51-Beta - Permission Denied SOLVED***

To All-

We solve the Permission denied issue, here it is hot off the presses, you are the first to receive a copy.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15
 

ejbmvp

Senior Member
Nov 30, 2011
253
41
Grand Rapids, MI
To All-

We solve the Permission denied issue, here it is hot off the presses, you are the first to receive a copy.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15

i was one who kept getting " Permission Denied " errors and i just tried Rev 51 and now it works. so far i have been able to install 2 options. thanks!
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
*Kindle Fire First Aide Revision 4.1.51-Beta for Windows - Permission Denied Solved*

http://xdaforums.com/showthread.php?t=2085587 this is even better than acyd audio engine, this have the acyd audio engine + a lot of other sound tweaks

persano,

Thank you for the links, we are going to stick with Ultra High End options like Sony ClearAudio, Sony Bravia, Sony Xloud and Pimp My Beats. The other sound enhancements are designed for headphones and are too dramatic while our sound enhancement are designed for high end audio systems and focus on expanding the compressed MP3, so the upgrade is very subtle but highly effective.

********Permission Denied Solved*********, here it is hot off the presses, you are the first to receive a copy.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
*Kindle Fire First Aide Revision 4.1.51-Beta for Windows - Permission Denied SOLVED*

Chris, I checked the KindleBackUp directory on the PC after the restore step 25 failed to transfer the image files and it looks like they were not unzipped! I don't know why. I did edit the RunMe.bat file to update and add the gunzip.exe -d statements before I tried the restore but for some reason it did not unzip them. Yes, I had my Windows 7 environment PATH statement updated to point to the C:\KFFirstAide directory. Odd that the script did not execute properly to unzip the image files. Anyway I see that you have updated the latest RunMe.bat file to include the "-d" parameter to the gunzip.exe utility and also added a pause decision step for the user before proceeding to wipe data and cache. Good show!

The contents of the C:\KFFirstAide\KindleBackup directory showed all my image files still unzipped as follows:

02/20/2013 11:19 AM 4,363,942 boot.img.gz
02/20/2013 11:19 AM 132,532 bootloader.img.gz
02/20/2013 11:19 AM 62 crypto.img.gz
02/20/2013 11:19 AM 19,340,227 dfs.img.gz
02/20/2013 11:19 AM 4,348,968 dkernel.img.gz
02/20/2013 11:19 AM 284,993 efs.img.gz
02/20/2013 11:19 AM 105 idme.img.gz
02/20/2013 11:19 AM 44 misc.img.gz
02/20/2013 11:19 AM 5,588,493 recovery.img.gz
02/20/2013 11:20 AM 571,288,789 system.img.gz
02/20/2013 11:19 AM 23,374 xloader.img.gz

I had the latest Java JDK 7.0.15 installed (that's all the Oracle Java download site offers now from your link to Java JRE). fyi.
I let your toolkit install the MS VC++ runtime libs.
I ran the step 25 and that was it.

At this point after the tool wiped my data and cache clean, I was able to just use the tablet with whatever image was left on there. It showed all my original Amazon store apps icons. Some were still installed and some required me to reinstall from the Amazon store. The Amazon store simply reinstalled the apps when I clicked on them without complaining a nag message saying that I had already installed it. So apparently the wipe of data and cache did reset my device to like new. The funny thing is, I still have superUser app and SU root priviedges installed! yea!
It also left in place the Google Play market store app and Google Gmail app! So at least I have those activated and usable now too.
All of my previous Google Play installed apps however were deleted and I had to reinstall them. I have my Kindle HD 8.9 32GB tablet working pretty good now and I am leaving it as it is. I am not going to try to do another restore of my previous rooted image at this time since I am happy and satisfied with the way it is running right now. I have all my Amazon Prime functions back as well as the Google Play store to download non-Amazon apps. yippee! That's good enough for me. (I don't have all the other Google apps like Currents, Earth, Maps, etc. though). I am hesitant to try and rerun your toolkit to attempt to reinstall all the Google app functionality in fear that it is going to corrupt my Amazon Prime functions apps and functions again. If I re-try to reinstall the full suite of Google Apps functions will it move and disable my Amazon apps and functions? Previous posting from you said that the Amazon Apps will have been moved to a "Home" folder and I would have to click on it to restore the Amazon functions. I am not sure about it, so hesitant to corrupt my working environment again.

Anyway, hope this info helps you diagnose and improve the toolkit further.

Also, as I mentioned in previous posts, the ADB drivers installation file that you have in the toolkit fails to install on my Windows 8 Pro (64bit) computers. I tried to install them also in compatibility modes (as Windows 7, Windows XP (SP3) ) and it fails to install on Windows 8 64 bit each time. When I switched to a Windows 7 (32-bit) computer, the provided ADB drivers installed with no problem. So you may want to investigate that and find out what driver is good for Windows 8 (64-bit).

Infobits,

Thank you for the feedback, we need to add a line for Windows 8 users. Try this on Windows 8, drop to command:

Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS 
bcdedit -set TESTSIGNING ON

Then try to install the driver. If it works, send us an update please. We solved the issues with the Google Apps, we found what was causing the problem, it was a corrupt package. Be sure to use the updated version.

We solve the Permission denied issue, here it is hot off the presses.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire First Aide Revision 4.1.51-Beta for Windows - Permission Denied SOLVED

Holo Launcher doesn't work, please help :(

This is what it puts out after the first reboot:

Random Username,

Excellent details! That helped us solve the problem with Holo Install.

We solve ALL the Permission denied issue, here it is hot off the presses.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire First Aide Revision 4.1.51-Beta for Windows - Permission Denied SOLVED

hi chris this is what i got hope it helps

dekor8tor,

The error is "Device Not Found", what this means is that ADB is not recognizing the device for some reason. Please look in the Windows Device Manager, do you see:

Kindle > Android ADB Interface
Portable Devices > Kindle

If no, do you see an Yellow Triangles in the Windows Device Manager? Remember the way to navigate to the Windows Device Manager is Right Hand Mouse Click on Computer, choose Properties, then select the Device Manager tab. OK, what do you see in the Windows Device Manager that refers to the Kindle? Have you looked on the Kindle, do you have ADB Enable ON found under More + Security? Do you have "Allow installation of programs" ON under More+ Device?

Once we get the device responding to ADB Commands then we can begin the process of Rooting the Kindle.

We solve ALL the Permission denied issue, here it is hot off the presses.

Rev 4.1.51 Change Log:
1. Fixed Permission Denied Problem
2. Changed the timing on Option 21
3. Streamline code - processes at a faster rate of speed
4. Changed Enable OTA to Selective Enable

*****Kindle Fire First Aide Revision 4.1.51-Beta for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.51-Beta for Windows Universal Package: https://dl.dropbox.com/u/54456659/KFFirstAide.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 32-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide32.zip

Kindle Fire First Aide Revision 4.1.51-Beta for Windows 64-bit Version: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip

Make sure you are running the latest version of Java SE Development Kit 7u15
 

Top Liked Posts

  • There are no posts matching your filters.
  • 73
    In this Noob series, we will use a software package that will automate the backup, restore and recovery process among many other features - this is a 'Swiss Army Knife' for the Kindle. This tool has been in development for some time now and is still in Beta, although it has been thoroughly tested and can be used safely. This tool is designed to backup, recover and restore the Kindle Fire 2 7", the Kindle Fire HD 7" and the Kindle Fire HD 8.9" (HD 8.9" Does Not Require The Factory USB Cable). The download size is less than 14 MB and automates several processes, no command line knowledge required. Please post any bugs to this Thread so we can quickly make changes to the software, then post an update. Most Bugs are solved within 24 hours.

    To keep your Kindle safe, we have integrated this feature into our software, You do not need any command line knowledge, just as simple as 1, 2, and 3.

    Prerequisites for the Recover Options:
    1. Install The Latest Version Of Java SE: Java SE Development Kit 7u13

    If you are uncomfortable with these procedure, please stop and contact us, we specialize in Kindle customization and development. You can ship the Kindle to our office and have us install all the upgrades, then return it to you turn-key. This service is fee based, contact our office for additional information.

    SOFTWARE UPDATE (CRITICAL RELEASE) ON 06/30/2013 Version 4.1.100 - PLEASE DOWNLOAD THE ENTIRE PACKAGE IF YOUR VERSION IS DATED PRIOR TO THIS RELEASE DATE.

    WARNING! THIS TOOL CAN PERMANENTLY DAMAGE THE KINDLE IF IT IS NOT USED PROPERLY. DO NOT FLASH THE
    KINDLE FIRE 2 IMAGE TO A KINDLE FIRE HD OR FLASH A KINDLE FIRE HD 7" TO A KINDLE FIRE 8.9" DEVICE. THIS
    WILL CAUSE PERMANENT DAMAGE THAT CAN NOT BE REVERSED. ONLY FLASH THE CORRECT MODEL SOFTWARE
    TO YOUR DEVICE.

    HOW TO UPGRADE KINDLE FIRE FIRST AIDE:
    http://xdaforums.com/showpost.php?p=38435305&postcount=1072

    HOW TO CREATE THE WINDOWS PATH: http://xdaforums.com/showpost.php?p=38409721&postcount=1018

    HOW TO FIX THE YELLOW KINDLE TRIANGLE:
    http://xdaforums.com/showpost.php?p=38432739&postcount=1062

    These are the current features on Version 4.1.100-beta:

    • Images are stored securely on our 100TB storage array on a Gigabyte Infrastructure
    • Download is fast - script is fast and lightweight
    • Secure SSL on all images to eliminate image hacking
    • All images are stored behind a firewall with IDS
    • Restores fresh system.img, boot.img and recovery.img
    • Fresh Restore Support the Kindle Fire 2 7"
    • Fresh Restore Support the Kindle Fire HD 7"
    • Fresh Restore Supports the Kindle Fire HD 8.9"
    • Fresh Restore Currently supports software Rev x.2.3
    • ChainsDD Superuser APK and SU Binary Included
    • Automated Backup - Full and Partial Backup
    • Automated Amazon OTA (Over The Air) Disable
    • No Command line Knowledge Required
    • Automated Device Reboot After Restore
    • Pulls Device Information
    • Automated ADB Driver Install
    • Reboot the Kindle into Fastboot Mode
    • Software Support for x.2.4 where applicable
    • Software Support for x.1.5 where applicable
    • Easy Upgrade or Downgrade option
    • Automated Root - Two Versions
    • Automated Google Play Store Installation
    • Automated Google Apps Installation
    • Wipe Dalvik Cache
    • Automated Restoration of the Backup Files
    • Automated Pimp My Beats Install
    • Automated Sony Bravia "Best Resolution Audio Visual Integrated Architecture" Installation
    • Automated Sony xLoud Installation
    • Automated Pimp My Beats Audio Upgrade Installation
    • Android Fix Permissions Script
    • Automated Disable Amazon Ad Services
    • Make Google Play Store The Default Market
    • Unroot For Amazon Returns
    • Install Apex Launcher
    • Install Holo Launcher
    • Install Boat Browser with Flash Player
    • VPN and SIP VoIP Client Install
    • Automated Permission Fixer
    • Automated Alternative Driver Install
    • Automated Busybox Installer
    • Automated Wallpaper Mod
    • Automated Lock Screen Upgrade
    • Fix Broken Install Script
    • AVIC Alice TTS Upgrade
    • Automated Launcher Install which will includes over 2 Launcher Options
    • Flash Custom Recovery
    • Side-load Zip Files like the latest Google Apps Pack
    • Automated TTS (Text To Speech) Install - AVIC Alice
    • Automated Install, Upgrade and Correct ADB
    • Superuser Upgrade Service
    • Install ChainFire 3D Upgrade

    These are the features we will offer soon in 4.2.4 and up:

    • Automated APK Install - Single or Multiple APK's
    • Automated Flash support for Titanium Backup Update.zip Files
    • Automatic Update feature so you are always using the latest version
    • Automated Push and Pull files to and from the Kindle to PC
    • Automated build.prop editor
    • Automated Tune Up and Deodex
    • Automated services.jar editor
    • Remote Storage Option for your boot.img recovery.img and system.img Backup Files
    • Information and Help
    • Special Kindle Toolkit, Tips and Tricks
    • Pull the System Logs (LogCat) to help solve problems
    • Dump Bug Reports to your PC
    • Open Command Prompt for Developers or for Manual Input
    • Automated Custom ROM Support
    • Automated TTS Voice Editor
    • Your Choice of Media Player Upgrades
    • 180 DPI Support
    • Automated Keyboard Upgrade with Framework Edits Included
    • Automated Amazon Book Import to Google Books
    • Much more to come......................
    Now let's get to the software itself. The following is step-by-step guide, please DO NOT modify the batch file in any
    way, this took us weeks to perfect, so please respect the code. If you have recommendations, please post them,
    we love to give you the feature that are important to YOU not us.

    Kindle Fire First Aide Step 1: Using Mozilla Firefox, Google Chrome or Internet Explorer Download Kindle Fire First Aide 4.1.100-Beta:
    KFFirstAide.zip

    Note: Be sure to extract the package to C:\KFFirstAide

    Update Java To The Latest Version here: Java SE Development Kit 7u25

    Kindle Fire First Aide Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide100.zip to your C:\ Drive as C:\KFFirstAide

    Kindle Fire First Aide Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder

    Kindle Fire First Aide 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. Temporary disable the Android SDK.

    Kindle Fire First Aide 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.

    Kindle Fire First Aide 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.

    Kindle Fire First Aide Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.

    Kindle Fire First Aide 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:\KFFirstAide

    Note: Do Not forget the (;) semi-colon before the C:\KFFirstAide

    Kindle Fire First Aide Step 9: That is it! The software is ready. Next we get the Kindle ready to Flash.

    Kindle Fire First Aide Step 10: Next, go to the Kindle, pull down the status menu, select More+ then select Security, make sure Enable ADB is ON. Last, depress the <- and select Device. Make sure 'Allow Installation of Applications' is On.

    Kindle Fire First Aide Step 11: Insert the Original USB Cable to the Kindle, please ensure you have a solid connection, this is VERY critical.

    Kindle Fire First Aide Step 12: Next, make sure the Kindle Fire is Turned Off. Take the other end of the USB Cable and carefully inset it into a free USB Slot on your Computer - be careful to not disconnect the other end.

    Kindle Fire First Aide Step 13 : The Kindle Fire should automatically turn on and boot regular Bootmode. If the Kindle does not turn on depress the power button until it turns on. Next select Option 15 in the Software. The Kindle will reboot and will now see a screen that says: Fastboot Kindle Fire.

    Note: If Option 15 does not trigger the Kindle to boot into Fastboot, then your Bootloader is damaged. Please send SkOrPn a PM to order a Factory USB Cable.

    Kindle Fire First Aide Step 14: Place the Kindle on a safe surface so it does not disconnect when running the software.

    Kindle Fire First Aide Step 15: Launch the KF First Aide software by double mouse clicking on the KF First Aide icon.

    Kindle Fire First Aide Step 16: You will be presented with a Kindle Fire First Aide Menu, carefully select the operations you would like to perform on the Kindle.

    Kindle Fire First Aide Step 17: If the option states "Fastboot" you need to leave the Kindle as noted above, this is Fastboot Mode. As the last operation be sure to Wipe the Cache and User Data which is Backup Option 3 in the Menu.

    Kindle Fire First Aide Step 18: Next, we will disable "Fastboot Mode" and enable ADB on the Kindle Fire. Select Option 10 in the Software Menu, the Kindle will Reboot into Regular Mode.

    Kindle Fire First Aide Step 19: You may now perform the 'ADB Mode' options in the Menu.

    Kindle Fire First Aide Note 1: Remember, after you perform the full Recovery, you are working with a Fresh Copy of the Software. ADB is disabled by default so be sure to Enable ADB under Security and Allow Installation of Programs under the Device Tab.

    Kindle Fire First Aide Note 2: After the complete restore, please be sure to clear the Davlik Cache and the User Data by selecting Backup Option #3. You may also wipe the User Data and Cache by opening a Administrative Command Prompt within the KFFirstAide Folder and enter:

    Code:
    fastboot -i 0x1949 erase cache
    fastboot -i 0x1949 erase userdata 
    fastboot -i 0x1949 reboot

    Kindle Fire First Aide Note 3: The original versions of the Kindle Fire HD 8.9" with a software Versions 8.2.3 or 8.2.4 may find there Kindle Boot-loader loops to a Red Fastboot Screen. If your Kindle is stuck in Fastboot, please follow these steps to recover the Boot-loader: How To Recover Kindle Fire HD 8.9" Bootloader*

    Note: Please be aware of two main options in the Menu - one is Fastboot Mode where you have several Menu Operations that use Fastboot to execute properly and two is ADB Mode where you have several Menu Operations that use ADB to execute properly.

    Backup Option #1 Note: When selecting Backup Option 1 the images will be backed up to the SD Card in a folder named KindleBackup. Please copy this folder to your desktop until we are able to upload it to our secure servers. There will be a restore option in the future that will automatically pull YOUR images for restoration. There is a known Bug in Windows where you will not see the images in the Kindle Internal Drive which can be found in Computer. To overcome this issue, please download and install WiFi File Transfer then open your Web Browser to transfer these Backup files from your Kindle to the PC.

    Backup Option #2 Note: When selecting Backup Option 2 the images are first copied to the Kindle, then they are transfered to your Computer inside a folder named Backup which can be found inside the C:\KFFirstAide folder.

    If this was helpful and you would like to support our work, please send us a donation using this link:
    http://xdaforums.com/dona....php?u=4435645

    We would like to thank Mark Skippen for the "Toolkit" idea. Mark is a real master with Samsung products and his profile can be found here: mskip anyone who owns a Samsung or Samsung built (Nexus) product should obtain his Toolkit.

    *Note: After several conference calls with the Amazon Development Team we found Amazon applied a patch to the Bootloader in an effort to lock down the Bootloader, this patch rarely causes the Bootloader to stick or Bootloop, please use the above link to release the Bootloader. We have removed this patch from the boot-prod.img eliminating future issues with recovered HD 8.9" users.
    9
    Follow Up - Feedback

    You guys rock!

    Sent from my KFHD7 using xda premium

    Krsmqn,

    We thought of you when we were developing this package, It took us over 4 months to perfect. We held back many feature, just wait until we release the Production Version of 4.2.3, it even made us smile:D. As we have said before,
    we are truly honored to be part of the XDA Community and feel blessed to be able to offer this software to XDA Members. This package and version 4.2.3 is fee based elsewhere.
    6
    How To Manually Recover The Kindle Fire 8.9" Stuck In Fastboot?

    To All-

    If you would like to try a last ditch effort in getting the Kindle Fire 8.9" back online, please do the following:

    Step 1: Please run the Kindle Fire First Aide, attempt the HD 8.9" Recovery, if it fails move on to Step 2

    Step 2: Exit the Kindle Fire First Aide utility, double mouse click the KFFirstAide Folder.

    Step 3: Download Boot Image Number 1 from here (save the image to the KFFirstAide Folder): http://dl.dropbox.com/u/54456659/kfhd-8.2.3/Images/boot-prod.img

    Step 4: Download Recovery Image Number 2 from here (save the image to the KFFirstAide Folder): http://dl.dropbox.com/u/54456659/kfhd-8.2.3/Images/recovery-prod.img

    Step 5: Open up an Administrative Command Prompt from within the KFFirstAide Folder by opening up the KFFirstAide Folder then press your Right Hand Mouse Key while you are over the KFFirstAide Folder contents, then select Open a command prompt here. You should see something like

    Code:
    C:\Users\Your Name\KFFirstAide>
    Step 6: Next you would make sure the Kindle Fire is plugged into USB and Turned off, type the following and press enter after the command while the Kindle is off and plugged into USB:

    Code:
    fastboot reboot -i 0x1949
    Step 6: You will see a Windows Command Prompt that will look like:

    Code:
    C:\Users\Your Name\KFFirstAide>fastboot reboot -i 0x1949
    <waiting for device>
    Step 7: Next Power on the Kindle While you see the above, one the Kindle Boots the Kindle will suddenly reboot back into Fastboot although we have seen this step free the Bootloader, so if the Kindle begins to Boot normally unplug it from USB, if the Kindle boot back to Fastboot red screen proceed to step 8.

    Step 8: While the Kindle is in Fastboot Mode type the following at the Windows Command Prompt:
    Code:
    fastboot flash recovery recovery-prod.img -i 0x1949
    Code:
    fastboot erase cache -i 0x1949
    fastboot erase userdata -i 0x1949
    fastboot reboot -i 0x1949
    Step 9: Leave the Kindle Plugged into USB. Wait for the device to Boot back to Fastboot, if the device boot back to a Fastboot screen with odd vertical line running through it, stop here, the Kindle has begun the recovery phase. If the Kindle begins it recovery, it will react odd and reboot several times, this is normal. Wait 10 to 15 minutes. If the Kindle boot back to Red Fastboot Screen proceed to Step 10.

    Step 10: Leave the Kindle Plugged into USB. Next type the following command:

    Code:
    fastboot flash boot boot-prod.img -i 0x1949
    Step 11: Next let's do a little house cleaning. The following commands wipe the old Dalvik Cache and User Data which is, in simple, tied to the old Android Operating System. Having said this, when the new OS attempts to retrieve data from these partitions, a content stream of errors occur in the background, causing the Kindle to react VERY slow and at times completely unresponsive. To eliminate this problem we will wipe these partitions before booting the new OS. Please enter the following commands, press enter after each one:

    Code:
    fastboot erase cache -i 0x1949
    fastboot erase userdata -i 0x1949
    fastboot reboot -i 0x1949
    Step 12: Unplug from USB. The Kindle HD 8.9" will reboot with an odd Fastboot screen with vertical lines running through it, this is normal, do not interrupt the recovery. Let the Kindle begin it's recovery phase. This may take up to 10 to 15 minutes and the Kindle will reboot several times.

    Step 13: Once the Kindle Stabilizes, please be sure to apply the Amazon OTA Patch before connecting the Kindle to your WiFi, otherwise you will loose Root and Google Play Store which are both installed on the images.

    Step 14: After you applied the patches please wait for the Kindle to rebuild itself, this can take up to a couple of hours. If after 4 hours the Kindle is still reacting slow, perform a Kindle Fire HD 8.9" Factory Reset. This option can be found under the More+ > Device > Restore to Factory Defaults. We find this last step is rarely used.
    5
    Update

    To All-

    I have been cleared by my Doctors to return to work, here is my plan to catch up:

    1) 06/12/2013 7:30pm to 11:30pm - Go through PM's respond as needed
    2) 06/13/2013 10:00am - 6:00pm - go through the posts urgent first
    3) 06/14 - 06/20 - Go through Posts
    4) 06/20/2013 - Post an updated version of Kindle Fire First Aide

    I would like to thank everyone for there support during my recovery.

    Best Regards,

    Chris Bryant
    5
    How to update kindle fire first aide

    I get errors that the file exists in an otherwise empty directory, twice. I've attached screen shots. I've tried using both winrar and 7-zip and gotten the error both times.

    Flinsman,

    ***************HOW TO UPDATE KINDLE FIRE FIRST AIDE*******************

    Step 1: Download the update, save a copy of the update to your desktop

    Step 2: Unzip the update TO THE DESKTOP as KFFirstAide32 or KFFirstAide64

    Step 3: Navigate to C:\KFFirstAide look in the Backup folder, do you have any Backup images? If yes, Right Hand Mouse Click over the C:\KFFirstAide\Backup folder choose COPY then navigate to your Desktop choose PASTE this will copy the the Backup image folder and images to your desktop in a folder named Backup, there should be 3 images in this folder if you did a 17 Backup with our software. If you never did a 17 backup ignore this step.

    Step 4: Navigate to C:\KFFirstAide look in the KindleBackup folder, do you have any images? If yes, Right Hand Mouse Click over the C:\KFFirstAide\KindleBackup folder choose COPY then navigate to your Desktop choose PASTE this will copy the KindleBackup image folder and images to your desktop in a folder named KindleBackup, there should be 11 images in this folder if you did a 13 Backup with our software. If you never did a 13 backup ignore this step.

    Step 5: Next navigate to C:\KFFirstAide DELETE the folder and contents

    Step 6: Navigate to your Desktop, find KFFirstAide32 or KFFirstAide64. Rename the KFFirstAide32 or KFFirstAide64 to KFFirstAide on your Desktop

    Step 7: Inspect the Desktop folder name, make sure it is KFFirstAide

    Step 8: Right Hand Mouse Click over the desktop folder named KFFirstAide choose "Cut", next navigate to C:\ - make sure you are not highlighting any folders and choose "Paste" - the folder KFFirstAide will now copy to C:\ - if this fails for some reason choose Copy and Past rater than Cut and Paste

    Step 9: Only do this step if you did Step 3, otherwise ignore this step. Navigate to C:\KFFirstAide, Right Hand Mose Click over the folder named Backup, choose DELETE.

    Step 10: Only do this step if you did Step 4, otherwise ignore this step. Navigate to C:\KFFirstAide, Right Hand Mouse Click over the folder named KindleBackup, choose DELETE.

    Step 11: Only do this step if you did Step 3, navigate to you Windows Desktop, find the folder named Backup, Right Hand Mose Click over the Backup folder, choose "Cut", then navigate to C:\KFFirstAide and choose PASTE. If this fails choose Copy and Paste.

    Step 12: Only do this step if you did Step 4, navigate to you Windows Desktop, find the folder named KindleBackup, Right Hand Mose Click over the KindleBackup folder, choose "Cut", then navigate to C:\KFFirstAide and choose PASTE. If this fails choose Copy and Paste.

    Step 13: You may now remove the KFFirstAide, KindleBackup and Backup folders on your desktop, if they exist.

    Step 14: Let's create a new shortcut. Find the current RunMe.bat shortcut on your desktop, delete it please.

    Step 15: Navigate to C:\KFFirstAide find RunMe.bat - Right Hand Mose Click over RunMe.bat choose Send To - Desktop Create Shortcut

    Step 16: Navigate to your Desktop find the new shortcut, Right Hand Mose Click choose Properties. Find a box and check "Run Program as Administrator" or "Run As Administrator" - Click Apply.

    Step 17: Let's make sure you have the Path statement setup, please drop to a Windows Command

    Step 18: Enter these commands:

    Code:
    cd C:\Windows\
    adb kill-server
    adb wait-for-device
    adb devices
    If you see a serial number after adb devices you are good to go. Close the Command Windows by typing exit. If the command failed, you are missing the path, we have several posts on setting up the Path, Post the error.

    ********UPDATE*********

    *****Kindle Fire First Aide Revision 4.1.66-Beta RunMe 02/25/13 at 00:30 for Microsoft Windows*****

    Kindle Fire First Aide Revision 4.1.66-Beta for RunMe.bat Package: RunMe.zip (Dropbox)

    Kindle Fire First Aide Revision 4.1.66-Beta for RunMe.bat Package:RunMe.zip (Box)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows Universal Package: KFFirstAide.zip (Dropbox)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows Universal Package: KFFirstAide.zip (Box)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows 32-bit Version: KFFirstAide32.zip (Dropbox)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows 32-bit Version: KFFirstAide32.zip (Box)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows 64-bit Version: KFFirstAide64.zip (Dropbox)

    Kindle Fire First Aide Revision 4.1.66-Beta for Windows 64-bit Version: KFFirstAide64.zip (Box)

    7-Zip for Windows 32-bit: Download

    7-Zip for Windows 64-bit: Download

    Oracle Java SE Update: Java SE Development Kit 7u15

    Oracle Java SE 7u15 32-bit : jdk-7u15-windows-i586.exe

    Oracle Java SE 7u15 64-bit : jdk-7u15-windows-x64.exe https://dl.dropbox.com/u/54456659/JavaSE/64-bit/jdk-7u15-windows-x64.exe