Hi, no I did not load any of the other selections. I only loaded the Google Apps but that failed at first time run due to I had the toolkit installed on my D: drive instead of C: drive. I let the installation continue with all of the errors saying C: drive not found errors since I was afraid to interupt it midsteam and cause major out of sync corrupting of the environment. After I let that finish running, I then fixed the toolkit to run under the correct drive and find the directories. It then reran the Google apps install step and let it finish. When it finished I had the google apps installed but the screen presentation was corrupted. The screen did not show the top and bottom navigation menu bars, so I could not navigate nor access the settings any longer. So something must have got corrupted due to the first running of the scripts with the wrong drive letter.
After this I went ahead just for the sake of it and ran the other google assignments step in the toolkit. When that completed the tablet screen returned back to normal showing the top and bottom menu and navigation screens buttons again. So I was almost there... but then noticed that many of the Amazon apps would not lauch from the top menu launch menu list (e.g. - music, web, video, photos, etc). I had some apps that I had installed from the Amazon store (like ES Explorer, Twitter, Facebook and a few others) and those apps were no longer listed in apps nor to be found anywhere. When I tried to download and reinstall ES Explorer from the Amazon store, it said that I already have that installed and to go find it on my local device. It will not allow me to reinstall it! dang Amazon eco system sux!, So then I attempted to install it from the Google Play app store and that also fails to install saying "incompatible device!". I am so frustrated and worried that I messed up my $402 tablet.
Let's get to the main worry I have though... that is why can't I get any response for fastboot mode? My tablet enters fastboot mode showing the words fastboot on the screen. But then it just hangs and sits there unresponsive to any fastboot issued commands. What do I need to change or do to fix this situation? I want to restore back to my initial system images which are backed up both on my tablet and on my PC drive in the folder named "kindlebackup".
Since the backup recovery images are on my tablet already, is there an adb recovery mode on these Kindle HD 8.9 devices where I can restore them back? (instead of using fastboot mode)? I see you are always cautioning and mention about the fastboot cables that you offer for sale... I see many on ebay too. I am wondering if I have to buy one or not. Can you answer me if this situation I am in is normal or seen before or is my tablet in a unique situation here with damaged bootloader?
P.S. - I keep forgetting to also mention that I ran a few other steps trying to see if they would clear up the missing amazon functionalities too.
I ran the "Fix the Android System Permissions and Anamolies" step and that did not fix it either.
BTW, what Windows OS' have you tested your toolkit and drivers on? I am on Windows 8 Pro. Anyone else using Windows 8 successfully with fastboot mode on the HD 8.9? Maybe I should dig up an old Windows 7 PC drive and try to use fastboot on Windows 7?
Hey! I got out my old Gateway netbook which runs Windows 7 32 bit OS and installed your Windows32Bit toolkit and set it all up. And now your provided ADB drivers installed successfully. And now it successfully can issue fastboot mode commands! That's the good news for me.
The bad news is that the step 25 to restore full backup images did not seem to run or work properly. I noticed that the gunzip.exe commands in the RunMe.bat file were not uncompressing the image.gz files. You have to tell gunzip.exe to uncompress the files by specifying the "-d" option as follows: gunzip.exe -d <imagefile.img.gz>
So I edited those likes for step 25, to add the "-d" option and ran the toolkit to try to restore my sysytem. But then it fails with all these messages:
The system cannot find the path specified.
target reported max download size of 1006632960 bytes
error: cannot load 'xloader.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'bootloader.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'idme.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'crypto.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'misc.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'dkernel.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'dfs.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'efs.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
*****************************************************************
* OK, We Are Done Restoring The Kindle, Now We Will Do A Little *
* House Cleaning By Wiping The Davlik Cache And User Data *
*****************************************************************
erasing 'userdata'...
And it is still hung sitting there saying "erasing 'userdata'"... I am afraid to break out of this routine and see that it did not restore my image files and might now have went ahead and wiped my data and bricked my tablet? Dang! You've got to improve your scripts to not forge ahead wiping and changing any further if such critical errors take place. Your script should halt and not continue to corrupt up the system if a critical file fails to load or execute. Just a suggestion. I hope my tablet is not in a corrupt state after I control-C out of this restore step now... I will post back result later on if it did or not. Also you need to add mention in your first post that the included drivers do not work on Windows 8 for fastboot mode. talk to you later...
Damn, now the tablet won't boot up anymore. It gets paste flashing the Kindle Logo and a Google Android screen appears asking to sign in.
When I sign in with my google account it goes to the wi-fi settings screen to configure your wi-fi settings. But after setting up my wi-fi config, I am stuck on that screeen with no way out of it because once again the screens top and bottom menus and navigation buttons are no longer displayed or available. I plugged the tablet into my PC to see if I can get adb devices to work and it does not see the device any longer! I am stuck and locked out of any further updating it now. The regular USB windows drive does show up when I plug it into the PC and all my folders are wiped clean! Totally wiped all my data, bookls, everything! WTF?
You really should update your scripts to prevent wiping or changing the system if the script encounters a serious error like it did here not loading my backup images... but still went on to wipe the system data and cache. Ouch! Is there anyway to get back into this tablet now?
Update: I rebooted my tablet again with it connected to the PC. It came up again with the Welcome to Android screen asking if I want to sign into an account. This time I refused it and it went on to ask me to sign in to my Amazon Prime acct to register the device. From there it began refreshing my tablet. So it looks like I got back to near fresh system so far. I am checking it out further to see if I can begin all over using it from this state or if anything else might seem to be corrupt or missing. I see a bunch of icons from my previous old apps that were loaded before the wipe out but not sure they are really installed or active at this time. But for now, a sigh of relief from me that my tablet was not locked up and bricked. I can get back into adb now too. So I am relieved.