Disclaimer: By following this guide, you understand and accepts that I, and any developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place. I wrote this guide to be used on a Windows computer, but as long as you can do the same things on Mac/Linux, the whole guide applies. If there are any issues, please first refer to the troubleshooting portion at the end of the guide. The 8.9 version of the device does not need the factory cable to enter fastboot mode.
+Note: As of Amazon OS update 8.3.1+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 8.3.1 or higher, please proceed with caution. I strongly recommend you make backups in Step 2.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD 7" look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
+Note: if you know 100% that you have the right model, skip to Step 1 and begin the guide. This part is only for those with knowledge of fastboot and would like to confirm scientifically that they have the right model. You don't need to know how to use ADB or fastboot in order to successfullly complete the guide and install custom ROMs:
In CMD, type:
Code:
fastboot -i 0x1949 getvar product
Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
===== 6. How do I boot into fastboot mode? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 8.1.4 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Again, you need to have Android SDK installed before you can use fastboot. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
Code:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "jem-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. From here, you can begin using fastboot commands to flash to the device's partitions. To exit fastboot mode, after you finished flashing what you needed, type this:
Code:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting
+Note: Some users reported not being able to root on later software versions, so check for 8.1.4 in your Settings, if it's higher than that, you may have some trouble, which is why I provided 3 methods.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 8.9" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 8.9" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device.
Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea. Make sure your ADB drivers are working, and that ADB is turned on in Settings. Open the RunMe.bat file, choose option 1. Now it will ask for your Amazon account password to restore, go ahead and type in your password and proceed. After the device reboots, it will be sluggish, now run the first method again, and you'll be back to normal with root.
You can aso try this: Root Kindle Fire HD with Windows
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager" or any other root application, you want to see the window asking for superuser permissions. Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step. If the root programs say you have root, but you don't see the window asking for the permission, remember to go to the app listing, and tap on superuser to initialize the daemon, then try to check for root again.
Recap:
1. Download the root tools from the threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Step 3: Installation
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 8.1.4 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 8.1.4 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Check that "disable recovery auto update" box, leave everything else alone, unplug the cable, and hit flash (the first option). You will see a progress window, and just hit OK. Then, turn off the device. Now, when you turn it on, this is the way to enter recovery every time: the moment you turn it on, you'll see the yellow Kindle title. Immediately hold down the Volume Up button (leftmost from the power button) before it turns blue, and once it does, count to three in your head and let go and you'll see the TWRP splash logo. Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 8.9" Development forum for custom ROMs.
If you want to save space, you can now go ahead and delete all the files we just used; you no longer have a need for any of them. Keep FireFlash, though, because in the future you might want to update TWRP, then leave everything blank, plug the update image into the recovery partition and hit flash. Only use Hashcode's TWRP builds as of now, because he specifically altered those builds to work on the Kindle Fire HD 7" and 8.9" so the official ones on the TWRP site won't work. If you flash those (especially the "blaze" codename), you will brick the device, so don't do it!
Recap:
1. Download FireFlash and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time. This list contains (somewhat, if not) stable releases only:
1. CyanogenMod 11 by Hashcode (AOSP, Android 4.4 KitKat)
2. ParanoidAndroid Port by jb2kred (AOKP, Android 4.2.2 Jelly Bean)
3. PAC-man by goldflame09 (AOKP, hybrid of CM + PA, Android 4.3 Jelly Bean)
4. CM11/SGT7 by twa-priv (CM + Samsung Galaxy Tab 7 mods, Android 4.4 KitKat)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Now, in case your custom ROM doesn't automatically include GApps, and you would know if you boot up and you don't see Play Store or Google Maps in the app drawer, follow this. Go to this link. You will notice a table, and on the left side, you see the CM version that corresponds to the Android version number. All the custom ROMs should use the row that corresponds to the Android version. For example, CM10.1 runs 4.2.2, CM10.2 runs 4.3, so click on the one that corresponds. If your ROM runs 4.2.2, use the 4.2.2 row, etc. After you finish downloading that .zip file, move it to the sdcard, and boot into TWRP. From there, if you want to be fancy, wipe cache and Dalvik cache before flashing, but you don't have to unless there are problems after you restart. If there are problems, like freezing on boot, or crashing, then boot back into TWRP and wipe the two cache partitions.
Generally, you only need to flash the file and you're done, but you can never be too safe. This also applies to ROMs: if you're moving from ROM to ROM, say Ubuntu Touch to CM10.1, you MUST wipe EVERYTHING except the sdcard itself, and this includes the "Factory Reset" option. However, if you're moving from one update of a ROM to another, say a nightly of CM10.1 to a newer nightly of CM10.1, you can just simply flash the update over the old one, no wiping needed (this is called dirty-flashing). However, again, if you notice problems afterward, simply boot back in TWRP and wipe the two cache partitions. Remember to always make backups before you make changes to an otherwise stable build. If there are issues that you can't seem to resolve, you can always restore back to the previous build.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
5. If there's no GApps for your ROM, use the link to download the proper version.
6. Move the file to sdcard, then boot into TWRP and flash.
7. Reboot, and if there are problems, reboot back into TWRP and wipe cache partitions.
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash, sparkym3 & prokennexusa & Bin4ry for their rooting methods, and myself for the creation of this guide.
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
rebelduke said:
This guide/tutorial was extremely helpful to me as a novice, just starting how to learn to modify my Fire HD 8.9". I'd like to suggest a few changes/enhancements to the guide:
1. In the NOTE paragraph just below the first paragraph you mention issues with 8.4.1. specifically you mention issues with this release but there is no indication if these issues will prohibit successful update if the guide is strictly followed. Also, a cable is mentioned. In other posts I have seen references that indicate that no cable is necessary with the Fire HD 8.9". In fact, one post mentions that using a cable may, in fact, possibly damage the Fire HD 8.9".
2. Because I'm so new at this I'm very paranoid about making a mistake. I've read the horror stories in many of the posts and I'd like to avoid these mistakes. And because I'm so new, my only experience is with the 8.4.1 release and unfortunately it is so new, I suspect, that the developers have not had time to verify that their applications are compatible. I am not complaining since I know that 99.9% of these good people do this out of the goodness of their heart, and not for monetary gain. However, I do wish this issue of software release version could be more fully addressed.
3. Just an example - The heading clearly states that this guide applies to the Fire HD 8.9". Very clear and difficult to misunderstand! In Step 3 Installation, FireFlash is mentioned with no reference to a Fire HD operating system release number. Can I safely assume then that this utility is compatible with 8.4.1? It may be that the answer would be obvious to a more experienced person but to someone like me(and from reading many, many posts there must be a bunch of folks out there just like me), with little experience in flashing, rooting, etc.,I'm at an impasse regarding should I proceed or not proceed Thank you..
Click to expand...
Click to collapse
Thepooch said:
There will have to be some changes to the method to install boot and recovery on both 8.4.1 and now people are receiving 8.4.3 all the present methods will break the system, unless you have a Rom waiting on your sdcard to flash afterwards.
Click to expand...
Click to collapse
I am aware of the changes, but I have not been caught up with the status of the methods and their effects on the tablets. I have placed warnings at the beginning of the guide.
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Sorry about asking about 2! I was actually putting the brackets around the local folder, but I realize now that you only had them to indicate that parameter was optional. However, the error that was occurring before wasn't about the local file...it was about the .img file which did exist. I'm baffled because now if I put the brackets back, it only fails with an error about that, not about the .img file. I realize I'm not making much sense, but I can't reproduce it so that it says the same error that I first mentioned above in 2.
I'd still like to know about 1 though. Thanks.
EDIT: I did Step 3 - Installation. I booted into TWRP and did a backup. I assumed that I did not have to do any wipes or install of any other rom yet, i.e. I just wanted to boot the existing 8.1.4 rom that was already there. However, when I "reboot system" from TWRP, it goes into TWRP again instead of booting up the rom.
I tried doing a restore of what I just backed up, but the result is the same. So does this mean I was required to do the wipes and install of another rom, rather just booting up my existing one? Or is there some other step I'm missing to make it get out of TWRP?
sga999 said:
I have two questions about Step 2 for backing up files.
1. Is boot0block.img ever needed? It looks like it is backed up, but it isn't referred to in the restore step (fastboot commands).
2. The "adb pull" commands don't work for me. For example, this error message displays: "remote object /sdcard/stock-boot.img' does not exist". But the files are definitely there.
Click to expand...
Click to collapse
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Thepooch said:
Boot0block is backed up in the event something happens to that particular partition somewhere along the way, you will know if it does no wifi ect. Shift plus right click inside the folder that adb is located, select open command window here. Run all your commands from that cmd prompt. It will pull all those files to that folder location. Since you will know what folder it is to be pulled to this portion of the command can be omitted [C:\KFHD8Backup].
Click to expand...
Click to collapse
I realized more about the format of the 'adb pull' command and posted late last night. It's in my post above your response. Thank you for answering. Also, it's good to know about what boot0block is in case something fails later.
I also added another question there, wondering about why I can only boot into TWRP, not the stock rom I already had installed. I'm pointing that out again now, just because you(and others?) may not have seen it in my EDIT above.
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Thepooch said:
Do a full wipe and flash a Rom.zip. Now you will need to
Code:
adb push Rom.zip /sdcard/
For obvious reasons just don`t wipe your sdcard .
Click to expand...
Click to collapse
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
sga999 said:
I can do that. But I'm curious to know why you're recommending this. Is it because I had problems booting up the old 8.1.4 rom and you just want me to try some other rom? Or is it that you know that what I did will never work, i.e. using FireFlash with the boot and recovery images and two checkmarks will never allow me to boot into the original rom?
Just "for fun", here's what I see when I try to boot. Times are approximate:
orange 2 seconds, blue 8 seconds, orange 30 seconds, totally black screen 2 seconds, orange 1 second (kind of flickers), blue 3 seconds, TWRP comes up.
My reason for wanting to do this is to "prepare" for going to CM10 (or other) "soon" but not quite yet. I'd like to keep the original rom for now and not wipe any data. Maybe this goal is impossible?
Thanks for your help.
Click to expand...
Click to collapse
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Thepooch said:
Your system is broken for some reason the present method just does that. Flash Hashcode`s 8.4.1 zip. Disable OTA`s with kindlefire FirstAide or Free your kindle http://forum.xda-developers.com/showthread.php?t=2072198 or even Soupkit http://forum.xda-developers.com/showthread.php?t=2162973 . YOU MUST WIPE. Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash Rom.zip disable OTA`s before enabling wifi or you will go in circles.
Click to expand...
Click to collapse
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
sga999 said:
Thanks, Thepooch. If I have to wipe anyway, I may as well just go to CM10 now. The main thing I wanted to know was whether I had done something wrong or whether what I tried to do (i.e. not install a new rom and just boot into the original rom) cannot be accomplished by anyone. I think you are saying the latter, right?
I appreciate all the help you've given me!
Click to expand...
Click to collapse
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Thepooch said:
Well you got a free thanks so make sure you hit mine as well. I don`t believe you did anything wrong but I really could not tell you for sure. I have been stuck just where you are a couple times and I know I did everything right. Others I have helped became stuck the same way because Amazon has been diddling around with the boot for the last three updates. I can only assume that some encrypted part of the framework is running a stack check resulting in the system appearing broken. So yes it would be best to have something to flash before starting this process.
Click to expand...
Click to collapse
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
sga999 said:
Thepooch, it helps to know that you and others ran into this. I did read posts that were similar, but I never was sure if anyone found an answer or knew what went wrong. This is a friend's Kindle that she got in December. I got it rooted for her back then, and I did whatever was necessary to not get OTA's. So it's way back on release 8.1.4. So I don't think Amazon's last 3 updates would have any bearing on this. But who knows! Again, thanks.
Click to expand...
Click to collapse
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Thepooch said:
You will have issues rolling it back that far, just saying there are changes that likely if not done properly will leave you stuck again. My suggestion is to flash 8.4.1 then create a solid backup when booted normal giving yourself a safety net in the event of a mishap.
Click to expand...
Click to collapse
Thepooch, I'm not sure if this is interesting to you at all, but I experimented a little and learned something. As you suggested, I flashed 8.4.1 and decided to try an unusual step.
After I used Fire Flash yesterday and booted into TWRP, I immediately created a backup. But it turned out to be no good in the sense that restoring it did not help me fix the problem of not being able to boot into the 8.1.4 (old) rom (I could only boot into TWRP). But now that I was on 8.4.1, I did a restore of ONLY the data from that old 8.1.4 backup. It seems fine so far, except for Google Play app, which just exits as soon as I execute it.....it's not a big deal to fix that. (There may be other issues, but I haven't hit anything else yet).
So....it seems like something is bad in either the boot or the system portions of the backup. It's probably system since it has framework, which you had mentioned might be causing the problem. Again, this may not be interesting, but I thought I'd let you know.
Makes sense google play rarely works from my restored backups and your system was in good shape if you flashed the 8.4.1 zip prior to restoring data.
Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP with 8.4.3
Has anyone attempted Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP running 8.4.3? If so, were you successful? If you were successful did you follow the procedure defined here or did you have to deviate? If you had to deviate, what were the deviations? Thanks!
How to root kindle fire any version (including 8.4.3) ONE CLICK
Hi I need some help.
KFHD 8.9, non-us user, but bought at amazon, i am unsure of the exact version.
ADB worked ok, device showed there. BUT "fastboot devices" didnt really show anything at all. Still I went ahead with it. Rooted using bin4ry, qemu did not work at all, permission denied error.
I did everything up to the point of flashing the freedom-rom and twrp through fireflash. It did not have 8.1.4 bootloader, so I checked the box, checked the other one and left all else as is. It seemed to flash ok. Then I rebooted,,, and its stuck on orange kindlefire logo, forever. doesn't matter what volumes i hold. tried rebooting and everything.
Now I dont really know what to do... any ideas?
Getting errors trying to install the drivers from the QEMU zip file, so no device ( sdcard ) access from recovery and the Advanced...sideload option is not working either.
I'm on windows 8, when plugging in the KFHD89 to my laptop, I see the kindle show up, but I have the yellow explanation sign. When I try to update driver software, i get error it can't update Windows ADB.
Between windows 8 and ubuntu, I've been able to get fastboot working enough to get all the files loaded...but for the lift of me !!! my copy of CM10.1 and gapps.zip are not seen via recovery...AND...I get stuck at Blue boot logo...so I'm sort stuck in recovery and need to get drivers sorted between windows and/or ubuntu so I can copy the .zip files over.
EDIT: #6 from http://forum.xda-developers.com/showthread.php?t=2277105 helped me out. I was starting ADB Sideload and connecting USB out of sequence. Followed directions and it worked.
Well my problem its different that the ones I've looked over the forum.
I get the cyanogenmod installed , and then I wait for almost 45 mins, with the cyanogenmod logo.
Then it suddenly comes with the new android unlock screen for like 1 second and then it begins again with the cyanogenmod.
But to resolve it, I just turn off the kindle go to teamwin boot and then just restore.
Then it becomes like factory settings..
But I can't get the cyanogenmod to work no matter what.
What I'm missing...
Did u check the cm 10.1 zip files md5 checksum before flashing it? You should always do this, you can do it in es file explorer by going to a files properties and calculating the md5. Compare it to the md5 from the post where u got it from, if its different then re-download it..
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
seekario said:
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
Click to expand...
Click to collapse
Try downloading again, make sure file size is the same as the website says and md5 is the numbers in the description, just above the file or below, also try (make backup first) wipe cache, dalvik cache, data,system, flash rom , flash gapps, wipe internal, wipe dalvik, then reboot
stolen from my drunk kindle by Tapatalk 4
Well looks like I erased everything and it says I don't have a OS installed, but now the cyanogenmod zip its not in the sd card of the kindle.
So I have nothing to flash with, and it won't go to the locked screen.
But I'm stuck with the Team Win recovery project menu .
So its there anything I could do to copy the zip from my pc to the kindle so I can flash it, or even restore it so I can connect my kindle to my pc?
Thanks!
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well Im going to look more info about that adb sideload.
Thanks!
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Guys so sorry to bother u guys again , idk why I have such a big problem following instructions today...
I have flash my android phones before, I tho this was gonna be just like it...
But I was following this thread and nothing so far..
http://forum.xda-developers.com/showthread.php?p=37594973
if u guys got anything I could use.
Thanks!
Eh well I was hoping for more specifics, but I will tell you what I can, because I haven't ever had to use adb sideload. First go into twrp and hit advanced, them hit adb sideload and swipe to start. If your device manager doesn't have the drivers installed for your kindle when its in twrp for adb, you will need to install them, if you have installed adb drivers before and are running the latest twrp version for kindle(2.6.0.0 I believe), then it should be pretty much plug and play, but if you are running an older version of twrp you will need to force install the adb driver for that device because it didn't have the same vendor ID as the kindle like the new twrp has. Usually I think u just have hit update driver and tell it to let u browse for the driver manually, then uncheck only show compatible device drivers( it says something relatively similar to this) and look for the adb driver, can't remember if its the adb composite device or a different one. If all goes well and u haven't got driver issues, which I hope you don't because I think my tut was a bit lacking for installing drivers, then u should goto a command prompt and CD into the directory u have adb in, it would be in the android SDK, or a utility like kffa, anything that comes with adb will do. Make sure to put the zip u are side loading in the same directory as adb.exe. after that just type adb.exe sideload zipfilename.zip. that should put it on your kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I tried that a few times already the adb sideload.
and i just loads, and does nothing, I even waited for an hour, and wouldn't finish :S
So I just think the adb sideload its not gonna do it :S
Just in case u didn't understand whats my problems.
It won't boot up because it has no OS.
So I can't put anything in the sd or backup because I accidently erased everything... even the zip from my sd(cyanogenmod )
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
seekario said:
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
Click to expand...
Click to collapse
OK so type this: adb.exe sideload cm-10.1-20130725-NIGHTLY-otter2.zip
That command should work, just to make sure I'll mention it again, before u run the command, in twrp goto advanced, adb sideload, and swipe the thing to the left, afterwards run this command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
So I put the command and now it says
*cannot read 'sideload' *
any ideas ? thanks!
south956 said:
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I tried that first, and to reboot into fastboot I have to be in the menu, but I have no OS so I can't load anything, it just stays in the kindle fire logo.
I can only access to the Team Win recovery project menu(TWR v2.6) :S
Thanks anyways!
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
south956 said:
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I wish I had, I only have the original cable from amazon :S
I doubt anything can be done til you have fastboot cable, I heard people try adding certain lines in cmd but most say it doesn't work, so a sure fire way would be to either make or buy fastboot cable.
stolen from my drunk kindle by Tapatalk 4
Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4
I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks
One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!
That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?
soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.
Do you have twrp installed?
hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot
any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!
You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards
I have a Kindle Fire HD 7" system version 7.4.3 that has the proverbial "Red Triangle" of death.
This unit has not been rooted and I am very much a newbie.
I have rebooted the unit many times. Periodically it will work and then lock up again with the Red Triangle.
90% of the time I no longer have wireless access as this has been disabled with the error.
After reading many of the posts here, I have considered rooting it to a) back up my system files (including email) and b) reloading the software. However, if I am not mistaken, I need to load an ADB file. Since the "Enable ADB" under Security Settings is on OFF and cannot be turned on, is there any way that I can revive this unit?
What I would really like is to back up those hidden system files that include email files, program data, etc. as well as make this work like it used to.
Can any one help me?
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Edit: I'm a moron, red triangle is the useless stock recovery on the kindle. Least thats my best guess.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I do have a factory cable (same as fastboot cable?) from SkOrPn, but will have to look through the forum for how to do a system reflash. I am glad to know that I have an option to save all of my data.
Unfortunately the red triangle is not limited to the kf2, but don't I wish it was.
Thank you.
Try this: http://forum.xda-developers.com/showthread.php?t=1951254
If that doesn't work try kffa in the general 7" forum.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Since I am such a newbie, I have a couple of questions:
1) Can I assume that the "KFHD_SRT_v1.3.5- 7.3.0 (separate option for restoring factory recovery)" would be the option that I should use for my KFHD running system version 7.4.3? If I read thru this correctly, it will reset the system back to 7.3.0 and then auto update to 7.4.3 once connected to the internet. Is that correct?
2) If so, step 2 says to enter a command if your device recognizes ADB. Will this work on my device since the ADB option is turned off?
Thank you again for walking me through this process. [And by the way, you are not a moron. ]
Step 2 is misleading, you only need that command if you don't have a fastboot cable. I personally haven't had to use this tool, but from what I know it kinda downgrades the system but it should update on its own which also unroots it. And yes the download you were talking about it should be the right one.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
After downloading the KFHD System Recovery Tool (that took a long while) and installing the driver for my KFHD, I am now running the SRT batch file. I am afraid that I am a bit confused here. The batch file gives you the following 7 choices:
1) Restore-Factory Rooted with SuperSU.apk
2) Restore-Factory Rooted with SuperSU.apk, Apex Launcher, and PlayStore
3) Restore-Factory Recovery
4) Erase cache & userdata
5) Check fastboot status
6) Reboot normally (must have a standard cable connected to work)
0) Exit
According to the instructions, I am to select #4 and Erase cache & userdata. Won't this erase my hidden system data (i.e., program data, email, etc.)?
Please advise before I take the next step.
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
pi lady said:
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
Oops, now I am the moron.
I was in the wrong folder/directory. However, when I moved to the KFHD_SRTv.1.3.5 folder and entered this command, the new error message is "cannot load 'boot.img' - so what gives?
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay I have my KFHD temporarily back up again. It is more functional than it was, but not all applications are running yet.
I haven't tried the KF First Aid yet, but will. I have downloaded the zip file and extracted the files so that I will be ready. Not sure yet if I have to upgrade my Java (it is SE v7up25, but not the developer version).
However, before I proceed much further, I really want to back up my KFHD.
- My data has been "backed up" by making a copy via a USB cable and Windows Explorer to my flash drive.
- What is left to back up is the hidden section/partition of my KFHD. All the postings I have seen so far discuss backing up the system (OS) of the KFHD, but what about the area where applications store user profiles and/or data. For example, the email program stores all the email data in this hidden area. How can I get that backed up?
Once this is accomplished, I would feel much more comfortable in running the KFFA as well as the replacement of image files.
Any clues?
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try this dude
https://www.youtube.com/watch?v=k-8lTMLCGfE&feature=youtube_gdata_player
Sent from my SGH-T989 using Tapatalk 2
stunts513 said:
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay after multiple manipulations, I have run the KFHD SRT using Option 1) Restore-Factory Rooted with SuperSU.apk (WooHoo!)
Can I assume that my KFHD is rooted? If so, what do I need to do to actually see these hidden files? (The email program is e-mail.apk or so I have been told.)
Of course with the standard USB cable, I still see the usual stuff with Win Explorer.
What is my next step?
:victory: