Database Develop

[REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial

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.

[Q] Kindle hd 7.4.6 stuck on twrp no os and cant find it under adb devices

Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you

You shouldn't nessasrily need fastboot to fix this, I'm assuming the drivers you don't have installed for twrp is the adb device, so try updating Ur drivers with this version of the drivers: http://forum.xda-developers.com/showthread.php?p=44446906
Once the adb driver work you should be able to go I to twrp, hit advanced, then hit side load, and swipe to start side load, and with it plugged I to your PC put either a cm ROM or the stock rooted amazon ROM from android development into the same folder as your adb command, and run a line with this syntax in a command prompt: adb sideload myrom.zip
If that doesn't work you might be able to use adb push when not in side load mode but I haven't tinkered to much with twrp. If you must resort to using fastboot you shouldn't even need a factory cable in this case, as u can just go into twrp and hit reboot and tap bootloader, that should put you in fastboot. Hope this helps.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Code:
adb shell idme bootmode 1

Solution
Am3nd said:
Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you
Click to expand...
Click to collapse
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~

Am3nd said:
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~
Click to expand...
Click to collapse
Thanks, this helped.

Another noob here, first post. Firstly, thanks very much, this was also a great help to me. Just wanted to say i had a little trouble with the sideload command. Kept returning the error * cannot read 'com10.zip' *. Despite being in the same directory as the adb, to fix you must give the directory in the command like so:
adb sideload C:\pathToAdb\com10.zip
Just in case anyone is having the same issue. Cheers again

I'm stuck! Is a factory cable required?

I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.

It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk

pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.

LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.

pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.

LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.

pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.

I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.

Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.

Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app

Help! Infinite bootloop, can't enter Recovery, and Fastboot usb doesnt work

Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!

First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.

Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.

Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need

Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.

Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910

clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?

Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse

OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...

Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.

Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA

Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?

Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery

Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push

More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1

Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.

Amazon Fire 7" - Which ROM to install?

Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.

moralshixch said:
Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.
Click to expand...
Click to collapse
You need to identify the version of your Kindle. If its the otter2 try these threads over here:
http://forum.xda-developers.com/kindle-fire-hd/fire-2-development
another helpful discussion for you:
http://forum.cyanogenmod.org/topic/90173-otter-or-otter2/
---------- Post added at 02:43 AM ---------- Previous post was at 02:27 AM ----------
If it helps I can attach all the recovery/rom/and gapps that I'm using that seem to work well. I was using pac-rom but switched to slimkat a while ago. I only use this for a bedside alarm clock right now, but I'm thinking of putting it side mounted in my car into my stereo auxiliary running Kodi with the Car Skin they got going on in a thread. I'm not using the latest slimkat rom either I'm using an old version because it works well for me.

How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35

moralshixch said:
How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35
Click to expand...
Click to collapse
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!

MZGSZM said:
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!
Click to expand...
Click to collapse
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)

Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.

monster1612 said:
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)
Click to expand...
Click to collapse
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
MZGSZM said:
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.
Click to expand...
Click to collapse

MZGSZM said:
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Click to expand...
Click to collapse
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
The device does show up in its own category:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assuming this is the correct one, I'm not sure why I still can't get a readout.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
Hate to sound like a nag, but hoping you saw my last post. Any thoughts on why I'm not getting a readout? Thanks again!

MZGSZM said:
The device does show up in its own category:
Assuming this is the correct one, I'm not sure why I still can't get a readout.
Click to expand...
Click to collapse
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.

monster1612 said:
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.
Click to expand...
Click to collapse
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!

MZGSZM said:
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!
Click to expand...
Click to collapse
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.

monster1612 said:
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.
Click to expand...
Click to collapse
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.

MZGSZM said:
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.
Click to expand...
Click to collapse
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.

monster1612 said:
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.
Click to expand...
Click to collapse
Yep, if I type that a message pops up on screen saying it's unauthorized. The kindle then asks me if it should be authorized.

Try running fastboot as root.

basenjidad said:
Try running fastboot as root.
Click to expand...
Click to collapse
Thanks for the suggestion. I gave that a shot, still no luck getting this Kindle to fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
After installing LineageOS on another device, I learned of a command that should force the Kindle to fastboot, and it seemed to work. When I ran the suggested fastboot command I got this output:
Code:
product: AUSTIN
finished. total time: 0.004s
Where might be my next step in finding a compatible ROM?
Many thanks again!