[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

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide - Software Version 4.1.46-Beta 02/21/2013 at 02:01am

Note that at this step in the process, on the Environment Variables page, there are actually 2 sections, each containing a Path variable. The top set of values apply only to the Logged-in User while the bottom set is the System variables (apply to all users system wide).

I assume that you want the user to add the path variable to the System PATH variable and not the user one, right? If so, you should clarify this in the instructions. Or does it not matter?

---------- Post added at 07:19 PM ---------- Previous post was at 06:22 PM ----------

I thought I'd reply here rather than continuing my reply in the other thread since I'm now planning to use this software to accomplish the Google Apps setup.

I had asked a few questions in the last post in that thread which you haven't answered yet so since I've got time now, I proceeded to try to figure some of this out on my own.

For starters, I simply renamed the platform-tools directory of my installed Android SDK to platform-tools-temp which I believe should effectively disable it sufficiently for purposes of this app.

In addition, I hadn't installed in the root but instead in a directory beneath my Util directory (which I set up or the sole purpose of running utilities such as these). Assuming I make the necessary adjustments to the Path statement variable, and also to the hard-coded C:\KFFirstAide in the RunMe.bat, will this utility run correctly from within C:\Util\KFFirstAide on my system so I don't have to keep this software in the root of my hard drive? (I saw one person in this thread who had a problem with the software installed on his D:\ drive which is why I'm asking.)

To start, I have removed Gmail_4.0.5.apk, GoogleCalendar.apk, GoogleCalendarSyncAdapter.apk, GoogleContactsSyncAdapter.apk, OneTimeInitializer.apk, and SetupWizard.apk. I then "Cleared Data" on the following services: Account and Sync Settings, Google Account Manager, Google Play Services, Google Play Store, and Google Services Framework. (I didn't see an entry for Google Login Service but maybe that shows up as Google Account Manager in the list since I did see and clear data on that one.

I just now pulled down the latest version of the software and will start the config process for that on my system after I finish dinner. But before I start, I thought I'd inquire about the directory change I made, and if you anticipate any problems because of it, if I make the required changes to the path variable and the text in the RunMe.bat file.

CheriePie,

Sorry for the delay this has been a juggling match lately.

OK, regarding the Path statement, yes it would be preferred to add the statement to the system wide variable although if you are the only user, it really does not matter. I think the one we recommend is the one that says "Environment Variable", although I can not remember, it has been a while now since we have been on Windows.

Today we may have time to go through our other threads, sorry for the delay.

Yes, you are correct CheriePie renaming platform-tools to platform-tools-temp effectively disables the SDK. You may want to completely remove the SDK since it robs you over 600MB of precious hard drive space. Most people do not need the SDK and our software includes the entire platform-tools utilities. Plus we keep all the daemons updated daily, so in the end having the SDK becomes a completely redundant product.

By the end of today, the new version will allow for the software to be installed on any drive or any directory or any subdirectory. The current version requires you to install it specifically in C:\KFFirstAide ONLY. The reason, we hard code many of the items in the BAT file calling to C:\KFFirstAide - by the end of the day, this will be changed. So download the update tomorrow AM and you may install the software in any location as long as your PATH statement includes the new location of KFFirstAide, does this make sense?

You will run into problems until we make the C:\KFFirstAide dynamic, hopefully you figured this out.

This is Software Version 4.1.46-Beta The RunMe is Dated 02/21/2013 at 02:01am:

Microsoft Windows Kindle Fire First Aide Universal Version 4.1.46-Beta: KFFirstAide.zip

Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.46-Beta: KFFirstAide32.zip

Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.46-Beta: KFFirstAide64.zip

Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/21/2013 at 02:01am. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.

Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages.

Finally, make sure you are running the latests version of Java SE Development Kit 7u13
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide - Software Version 4.1.46-Beta 02/21/2013 at 02:01am

With this tool covering so much ground, and getting updated so often, are there ay plans on including a readme, or help option? (ie Entering, "?27" could print a description of the xLoud and ClearAudio upgrades.) Obviously, this isn't of vital importance, but considering that this thread will hit 100 pages soon, it could be rather helpful.

TB5,

That is a GREAT idea, we will add this to the software over the next week. So what we will do is:

When you select Option xx it will first display a full description of what is going to be installed and ask you if you would like to proceed., if you answer Yes, the software will proceed with the described package, if you say No, it will return to the main menu.

We will try to add this feature today since we agree, it is important.

You will run into problems until we make the C:\KFFirstAide dynamic, hopefully you figured this out.

This is Software Version 4.1.46-Beta The RunMe is Dated 02/21/2013 at 02:01am:

Microsoft Windows Kindle Fire First Aide Universal Version 4.1.46-Beta: KFFirstAide.zip

Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.46-Beta: KFFirstAide32.zip

Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.46-Beta: KFFirstAide64.zip

Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/21/2013 at 02:01am. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.

Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages.

Finally, make sure you are running the latests version of Java SE Development Kit 7u13
 

Random Username

Senior Member
Jan 7, 2013
329
36
Holo Launcher doesn't work, please help :(

This is what it puts out after the first reboot:
attachment.php
 

Attachments

  • Capture1.jpg
    Capture1.jpg
    59.5 KB · Views: 402
Last edited:

dekor8tor

Member
Oct 25, 2011
28
0
Cannock
dekor8tor,

There has to be a problem with your Kindle, we are finally having a large number of people successfully Rooting the Kindle so we know this method works. Heck, this is a know method used be several other tools, it is 99% effective in Rooting the Kindle, having said this we know the method works.

Let's start looking at the Kindle itself. When you run Option 21 does the Kindle ask to be restored? If no, then you have a driver problem. Please grab the Kindle, check More + Security do you see ADB Enable ON? If yes, go to More + Device, do you see Allow installation of programs ON? If yes, plug the Kindle into USB and open the Windows Device Manager, do you see:

Kindle > Android ADB Interface
Portable Devices > Kindle

If yes, the drop to Windows command and run the following command:

Code:
adb kill-server
adb start-server
adb devices

Please post the EXACT output when you enter these commands. Then open a Windows Command Prompt and navigate to C:\KFFirstAide and enter:

Code:
adb shell su -c "cd /data/local/tmp/; rm *"
adb push busybox /data/local/tmp/.

Please post the EXACT output.

This is Software Version 4.1.45-Beta The RunMe is Dated 02/20/2013 at 21:50:

Microsoft Windows Kindle Fire First Aide Universal Version 4.1.45-Beta: KFFirstAide.zip

Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.45-Beta: KFFirstAide32.zip

Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.45-Beta: KFFirstAide64.zip

Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/20/2013 at 21:50. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.

Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages.

Finally, make sure you are running the latests version of Java SE Development Kit 7u13

hi chris this is what i got hope it helps


Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Richard>cd
C:\Users\Richard

C:\Users\Richard>cd C:\

C:\>cd C:\KFFirstAide

C:\KFFirstAide>adb shell su -c "cd /data/local/tmp/; rm *"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

C:\KFFirstAide>adb push busybox /data/local/tmp/.
error: device not found

C:\KFFirstAide>adb shell su -c "cd /data/local/tmp/; rm *"
/system/bin/sh: su: not found

C:\KFFirstAide>adb push busybox /data/local/tmp/.
failed to copy 'busybox' to '/data/local/tmp/./busybox': Permission denied

C:\KFFirstAide>
 
Dec 3, 2012
23
1
It's in Florida
I have followed the process step-by-step and successfully installed the First Aide program. It seems to be running smoothly, at least until I try to use it. I attempted to use an option requiring ADB, but every time I go to use it it starts up normally like so:

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


At this point the screen remains the same, nothing happens, no process whatsoever seems to go on. I have left the computer and Kindle for an extended period of time and when I came back no progress seemed to have been made. I tried this several times and went back through the steps for installation and made sure I had done nothing wrong. I can't find an error or why nothing happens when I choose an option (device not being recognized by ADB possibly?).

I'm sure it's a simple error, as I am no expert when it comes to this, but if anyone had an idea for a solution to my problem that would be great! :D
 

jigga123

Member
Aug 18, 2010
10
0
XBMC

I rooted and installed XBMC as per your other post (thanks for that by the way!). When first started XBMC I saw the Frodo page and it said starting for the first time... and then I got a "XBMC has stopped" message. Now every time I try to go to XBMC I just get the pop up "XBMC has stopped" message and that's all. I can go back to the Kindle home page though and everything else is working ok.
 

Infobits

Senior Member
Jul 11, 2009
144
30
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).

Chris, looks like I spoke too soon. I noticed that the top menu bar was disappearing on me and I could not access settings any longer. If I reboot the tablet, the top menu bar is there initially. But when any notification status message came in and flashed on the top menu bar, it would scroll up and never return. Bummer!

So, I decided to restore again using my original full backed up images.
I did that and all went well up to the last part where it is "erasing " where it just hangs and sits there forever. Is that erasing cache and data step supposed to take a long time? I waited for like 1/2 hour and decided to just Ctrl-Break out of it at which point it says rebooting but at that point the tablet never reboots! I manually rebooted it. I think you need to work on that part!
Anyway I got back to my previous rooted state. Also please note, that I had rooted using another tool Bin4ry, not your tooklkit rooting steps with that restored image before.
Okay all was seemingly back to normal but now the Google Play Store and Gmail were no longer there. I wanted them,
So I tried to run your Install Google Play Store step 18 again and it failed every step copying and moving things due mostly to "read only priviledges errors". I don't know if that is because I have to use your rooting method or if there is just a flaw in the routine. But I let it all finish and at the end it said it did copy over the Google Play Store app and the phonesky app. That's all it succeeded to copy over it seems.
Then I rebooted and the Play Store app icon was there but it would not execute. Corrupt install again.

So next I decided to perform step 7 for a total return to stock HD 8.9 v8.1.4 firmware install. Again it downloaded the stock images and wrote them successfully to the tablet but then again just hung there waiting on the "erasing" message to complete. Again I waited about 45 minutes to let it finish and reboot but it never did. So again I Ctrl-Break out of the routine and it then says rebooting, finished successfully. But the tablet still in fastboot mode never reboots. I again had to manually hold the power button in to power it off and reboot.

But more problems! After I reboot it, it is running way slow as heck!!! It takes forever to execute and display everything. So another corrupt install update with the tool. arghhh!

So again I figured maybe you have some bad stock HD 8.1.4 images downloaded? So I again go back to run a full system restore using my original backed up images. Again it hangs foreever at the "erasing..." message. Am I supposed to wait a long long time for this erase wipe step and let it return on its own? I don't know what is going wrong but even my own original full backup restore is running a bit slow now.
Can you explain if that erase command "fastboot -i 0x1949 -w" is supposed to return when its done or does it just go into la la land? The next command after that is to reboot, "fastboot -i 0x1949 reboot" but it does not ever seem to reach that point unless I force a Ctrl-Break.

Since I break out of the erase data and cache step by not waitng for it to finish on its own, might that be the cause why my tablet is corrupted and running real slow now? I figure an erase should not take so long to complete. Please let me know ASAP so I don't pull my hair out trying to reinstall so many times.

Update: I went into the settings->devices menu on the tablet and did a reset and wipe from within the tablet itself. This totally cleared out the system and the tablet is running like New without lag again. So I suggest checking out why the fastboot -w command does not work correctly when issued from the script.
 
Last edited:
CheriePie,

Sorry for the delay this has been a juggling match lately.

OK, regarding the Path statement, yes it would be preferred to add the statement to the system wide variable although if you are the only user, it really does not matter. I think the one we recommend is the one that says "Environment Variable", although I can not remember, it has been a while now since we have been on Windows.

I have Windows 7 Ultimate 64-bit and the way it looks is that there's a button for Environment Variables. After you click that you're brought to a page with 2 sections. The top section is labeled "User variables for Cherie" (my username) and the bottom section is labeled "System Variables". The Path variable resides in both. But so long as it doesn't matter which one it goes in--I didn't figure it would unless the user is using multiple user accounts--then it shouldn't affect your instructions too much.

I can attach screen shots later if you're interested, let me know.

Yes, you are correct [URL="http://xdaforums.com/member.php?u=4262964"]CheriePie renaming platform-tools to platform-tools-temp effectively disables the SDK. You may want to completely remove the SDK since it robs you over 600MB of precious hard drive space. Most people do not need the SDK and our software includes the entire platform-tools utilities. Plus we keep all the daemons updated daily, so in the end having the SDK becomes a completely redundant product.

I still use the SDK for my mobile phone so yeah I still need it. But I don't have the entire package installed, only the platform tools for using adb commands.



I got it! And yeah, I did get it to run properly from the directory I put it in by doing a global search and replace on the RunMe.bat to change all instances of C:\KFFirstAide to C:\Util\KFFirstAide and all worked well... well, with the exception of the Google Apps still not installing, but that's an entirely different error. Read on...


I did manage to figure all this out myself and posted another message in this thread on page 79. Unfortunately, the process of installing the Google Apps still didn't work though. The full details including a screen cap can be found in this message: http://xdaforums.com/showpost.php?p=38270321&postcount=788

The problem seems to revolve around the /data/local/tmp directory it's trying to use. tmp is actually a symlink back to the /data directory so it's unable to install busybox there. But because of this, I'm also concerned the script may have deleted some files from my Kindle's /data directory. Not stuff in the directories since the -r (recursive) option wasn't specified, but if there were any files in the root of /data, then the adb shell su -c "cd /data/local/tmp/; rm *" command in the script would have deleted them!

I have been considering just taking the lines from the "OPTION23" section of RunMe.bat (the part for the Google Apps install0 and run each line individually to see if I can get past the errors. I deleted the /data/local/tmp symlink and created a real directory in its place. Perhaps this will fix the problem. However note that it's your script that is creating that symlink in the first place. (Line 3274 of RunMe.bat in the version I ran at the time, looks like it's later in the file now.)
 

Krsmqn

Senior Member
Jan 23, 2012
1,220
334
OnePlus 7 Pro
Google Pixel 5
For some reason this xda app won't let me add a picture to the above post.

Anyways, please disregard the color blue in the picture. The box on the bottom (system variables) is how the environment variables should look.
 

Attachments

  • uploadfromtaptalk1361501883991.jpg
    uploadfromtaptalk1361501883991.jpg
    53.3 KB · Views: 53
Last edited:
Okay, latest build, installed as C:\KFFirstAide in root of my drive, Path variable updated.

I can verify connectivity with adb devices command, and the first couple of commands to push busybox over and set it's owner and permissisions work just fine. However, once ADB starts trying to copy files to the /system/app directory I'm getting permission denied errors.

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

C:\KFFirstAide>adb push ChromeBookmarksSyncAdapter.apk /system/app/ChromeBookmarksSyncAdap
ter.apk
failed to copy 'ChromeBookmarksSyncAdapter.apk' to '/system/app/ChromeBookmarksSyncAdapter
.apk': Permission denied

C:\KFFirstAide>adb shell su -c "rm /data/local.prop > nul"
sh: cannot create nul: Read-only file system

I'm not sure what the local.prop has to do with but I'm going to try to copy over these files manually, outside of adb, and then try to pick up from there. Will update again later when I've had a chance to revisit this again. For now, I have to run out to troupe practice.
 

Infobits

Senior Member
Jul 11, 2009
144
30
I have Windows 7 Ultimate 64-bit and the way it looks is that there's a button for Environment Variables. After you click that you're brought to a page with 2 sections. The top section is labeled "User variables for Cherie" (my username) and the bottom section is labeled "System Variables". The Path variable resides in both. But so long as it doesn't matter which one it goes in--I didn't figure it would unless the user is using multiple user accounts--then it shouldn't affect your instructions too much.

I can attach screen shots later if you're interested, let me know.



I still use the SDK for my mobile phone so yeah I still need it. But I don't have the entire package installed, only the platform tools for using adb commands.



I got it! And yeah, I did get it to run properly from the directory I put it in by doing a global search and replace on the RunMe.bat to change all instances of C:\KFFirstAide to C:\Util\KFFirstAide and all worked well... well, with the exception of the Google Apps still not installing, but that's an entirely different error. Read on...


I did manage to figure all this out myself and posted another message in this thread on page 79. Unfortunately, the process of installing the Google Apps still didn't work though. The full details including a screen cap can be found in this message: http://xdaforums.com/showpost.php?p=38270321&postcount=788

The problem seems to revolve around the /data/local/tmp directory it's trying to use. tmp is actually a symlink back to the /data directory so it's unable to install busybox there. But because of this, I'm also concerned the script may have deleted some files from my Kindle's /data directory. Not stuff in the directories since the -r (recursive) option wasn't specified, but if there were any files in the root of /data, then the adb shell su -c "cd /data/local/tmp/; rm *" command in the script would have deleted them!

I have been considering just taking the lines from the "OPTION23" section of RunMe.bat (the part for the Google Apps install0 and run each line individually to see if I can get past the errors. I deleted the /data/local/tmp symlink and created a real directory in its place. Perhaps this will fix the problem. However note that it's your script that is creating that symlink in the first place. (Line 3274 of RunMe.bat in the version I ran at the time, looks like it's later in the file now.)

Yeah, Iam beginning to realize that this toolkit routines was not thoroughly put together. In the Root Method_1 routine I just tried to run again, it threw out error msgs trying to manipulate that /data/local/tmp directory saying:

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

The system cannot find the path specified.
The system cannot find the path specified.

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

The system cannot find the path specified.
Press any key to continue . . .

I looked up the lines in the RunMe.bat script and see that it is trying to execute an old version of adb.exe stored in the Qemc directory.
Chris why don't you just execute the adb in the C:\KFFirstAide directory? Instead it looks like you just slapped in old code to execute another older adb.exe in the C:\KFFirstAide\Qemu directory. Is there something special or different in that older version of adb.exe? I doubt it for executing a make softlink command "ln -s ". Can I remove the reference to Qemu\adb and just use adb?
 

Krsmqn

Senior Member
Jan 23, 2012
1,220
334
OnePlus 7 Pro
Google Pixel 5
It's put together quite well, I think. Maybe you haven't factored in variable change. Chris has continuously manipulated the code to fit the needs of the users. I was one of the first to use this utility and I can tell you that (at that point) the code was perfect. Despite a few voided links and some errors on my behalf, the KFFA utility is the reason why I have very few issues with anything I do with this device.

Truly a case of what my signature says: "if it ain't broke, fix it". Only problem is that it has opened Pandora's box.

Cheers Chris! You do good things.
 
Last edited:
C:\KFFirstAide>adb shell su -c "/data/local/tmp/busybox mount -o remount,rw /system"

C:\KFFirstAide>adb push ChromeBookmarksSyncAdapter.apk /system/app/ChromeBookmarksSyncAdapter.apk
failed to copy 'ChromeBookmarksSyncAdapter.apk' to '/system/app/ChromeBookmarksSyncAdapter.apk': Permission denied



No output returned from the first command to remount system as rw so at first glance, I would assume it was successful. Though perhaps that's not the case because the adb remount command returned an Operation not permitted error, and since the second command fails to copy the .apk to the /system/app directory, it would lead me to believe that the /system partition isn't really writable at all.

So referring back to my previously reported errors, yes there's still the issue of /data/local/tmp being a symlink to /data instead of an actual directory but all the other problems I was experiencing would seem to stem from the fact that the /system partition isn't getting remounted as writable.
 

Infobits

Senior Member
Jul 11, 2009
144
30
It's put together quite well, I think. Maybe you haven't factored in variable change. Chris has continuously manipulated the code to fit the needs of the users. I was one of the first to use this utility and I can tell you that (at that point) the code was perfect. Despite a few voided links and some errors on my behalf, the KFFA utility is the reason why I have very few issues with anything I do with this device.

Truly a case of what my signature says: "if it ain't broke, fix it". Only problem is that it has opened Pandora's box.

Cheers Chris! You do good things.

I am afraid to say that I have just taken the time tonight (or this morning) to analyse the script routines and I can tell you that this script is full of errors and a lot of redundant commands. I just walked through the "Root Method1" and the "Install Google Play Store" routines and see why it is constantly giving denied permissions errors. It makes assumptions that there is no busybox installed and is continuously and needlessly installing and removing it at many steps along the way. As well as there are some serious errors on manipulating the /data/local/tmp directory and turning it into a soft-link to /data directory and deleting stuff.
There are points along the updating path sequence where it looks like it can totally erase the /data directory contents too.
some of the commands that fail need to be executed as super user (root) with the su -c parameters to work properly... but they are not in the script.
Also I mentioned in previous post about the execution of an older adb.exe program in the "\KFFirstAide\Qemc" directory. Totally wrong and uneeded.
It is an older adb.exe than the one in the C:\KFFirstAide\adb.exe. And on my Windows 7 PC when I manually executed these exact sequence of commands it gives errors galore... fail, fail, fail. And each adb.exe version detects that another version of adb.exe daemon is running and kills it. Chris, you are probably fully aware of all this mess and working on it to improve the script but man, you really should not release this stuff in the state it is in. I weeded out the main important commands and executed them by hand on my terminal to successfully install the Google Play Store apps without the corruption that the script creates. The script constantly has permission denied errors thus leaving out file transfers and moves thus why so many folks are getting bad installs. You need to clean it up for sure. Just my own experience with the toolkit so far.
I am a Senior Software Developer/Engineer myself BTW, so I am not just guessing here... I am seeing the messy routines. Great start and toolkit that is helpful... but it definitely needs a lot more cleaning up.
 

Slimepuppy

Senior Member
Jan 6, 2013
89
23
San Antonio
KFHD 8.9, fresh install of 8.1.4, successful Option 14: disable OTA Updates with KFFirstAide 64 downloaded 2/22/13 @ 0130 CST


Chris - it looks like you broke Option 18 - Install Google Play Store

It doesn't look like busybox made it to /data/local/tmp and it went downhill from there.

You know there's a copy of Busybox on the device at /system/xbin? ;)

Andy
 

Attachments

  • gstore1.jpg
    gstore1.jpg
    136.8 KB · Views: 94
Error in RunMe.bat, line 4118

adb push Clibspeexwrapper.so /system/lib/libspeexwrapper.so

should be

adb push libspeexwrapper.so /system/lib/libspeexwrapper.so


Infobits, I'm doing exactly as you're doing now, trying to execute the lines that I need manually. Still having a bit of a struggle mounting my /system partition as writable so instead I'm just pushing the files over to my sdcard for now and will copy them into /system/app directly from the device.
 
Last edited:

procter

Senior Member
Sep 16, 2007
194
8
Long story short, I was trying to redo persano's tweak script on my perfectly fine and rooted Kindle fire HD 7 and forgot to copy back the install-recovery.sh file before restarting the device. Now it goes into a dark screen after the kindle fire logo at each reboot. It's showing up as "Kindle" with a yellow exclamation in my win 7 device manager via USB but it's not using the installed drivers. Tried adb command and it gave me "device not found". I can press and hold power button to power up /down the device too. Does this sound like a damaged bootloader? Would it hurt to try this first aid tool to access fastboot while I am waiting for my factory cable? First bricked device for me:eek:

Sent from my SPH-L710 using Tapatalk 2
 

prokennexusa

Senior Member
Jan 12, 2012
2,637
989
57
Petaluma
plus.google.com
Kindle Fire HD and 2 First Aide - Critical Release ! 02/22/2013 02:23am Rev 4.1.50

To All-

We are sorry we have not been able to respond to any of the posts today, we will focus on the posts tomorrow. We found a serious error deep in the code, please update the software immediately! This version is very close to Production, we will have a couple more Beta releases then we will be going to Stable Releases. This version is VERY stable. Today we had a total of 20 users using the software intensively from 8am to 5pm today. We took these steps to eliminate future issues. Today we spent all day debugging the code.

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.

Here we go Kindle Fire First Aide Rev 4.1.50-Beta 02/22/2013 at 02:23am:

New Features In 4.1.50-Beta:
1. New Detailed Description on every option - pick one of the options, you will see a detailed description and be given the option to exit
2. Backup and Restore are now seamless - the functions have all been tested
3. Apex Launcher Install
4. Holo Launcher Install
5. Boat Browser Adobe Flash Player with Instagram Install
6. Interactive Restore
7. Interactive Enable OTA
8. Google Apps now Include AVX (Android Voice Xtreme) TTS Speech Engine (One of The VERY Best)

Kindle Fire First Aide Microsoft Windows Universal: KFFirstAide.zip

Kindle Fire First Aide Microsoft Windows 32-Bit Version: KFFirstAide32.zip

Kindle Fire First Aide Microsoft Windows 64-bit Version: KFFirstAide64.zip

Be sure to unzip the contents to C:\KFFirstAide - check to be sure you do not have a second folder named KFFirstAide inside of C:\KFFirstAide. Also, check the date and time of the RunMe.bat make sure it is 02/22/2013 at 02:23am.

Also make sure you are not running the Amazon SDK, either disable it or remove it! Finally, make sure you are using the latest version of Java SE: Java SE Development Kit 7u13
 

field3d

Senior Member
Oct 10, 2009
67
1
Kindle Fire HD 8.1.4 Rooted problems

deleted other problem is the cause
 
Last edited:

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