Related
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 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.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
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
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
can someone help me remove custom recovery and the 2nd bootloader i have the stock amazon rom installed
Thanks in advance
Usually updating the stock ROM will do it, if you made backups of the partitions like the tutorials tell you to do you can simply reflash them in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Usually updating the stock ROM will do it, if you made backups of the partitions like the tutorials tell you to do you can simply reflash them in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Never made any back ups
I told someone else to try updating to the latest amazon os using Amazon's manual update the other day to fix this but it for some reason didn't work... But if you download the latest amazon is and update it it should work, however if it doesn't and it boot loops, technically you can go into twrp and tell it to reboot to boot loader (fastboot) and pull the boot loader IMG and recovery IMG from Amazon's update zip file on your PC and flash them via fastboot. If you need me to elaborate any just ask.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I told someone else to try updating to the latest amazon os using Amazon's manual update the other day to fix this but it for some reason didn't work... But if you download the latest amazon is and update it it should work, however if it doesn't and it boot loops, technically you can go into twrp and tell it to reboot to boot loader (fastboot) and pull the boot loader IMG and recovery IMG from Amazon's update zip file on your PC and flash them via fastboot. If you need me to elaborate any just ask.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
do you know of any tutorials on this? i could not find anything and as u can see i dont know much about this stuff so it would be appreciated.
Thanks
Wanna mention ahead of time, i am not responsible if you hard brick your kindle by doing this, i dont like messing with the kindles bootloader unless i have to personally.
Ok follow the instruction on Amazon's Website for manually updating a kindle. This might either bootloop/go straight to recovery once you do this, if not your probably on stock unrooted without twrp or 2nd bootloader, usually you can tell pretty easily since the kindle logo would be blue if it wasn't stock, assuming that for some reason it either does bootloop/go straight to recovery or for some reason works but has twrp and second bootloader please read on.
Keep a copy of the update on your pc. Now this gets a bit more complicated because i realized the update is a bin file, but if i remember correctly it should just be a zip file, so either tell windows open with winrar or 7zip, winzip, etc, or try enabling file extensions in your folder options on windows, and changing the extension to .zip. Once you do that extract u-boot.bin and recovery.img from the recovery folder. Put your kindle into fastboot mode(hit reboot then bootloader in twrp). Now you need a copy of fastboot.exe, so use a utility like kindle fire first aid and remember to put the recovery.img and u-boot.bin into the folder with fastboot.exe. Open a command prompt and cd into the directory that the fastboot command is in (in kffa) and verify we have a connection to the kindles fastboot by running "fastboot -i 0x1949 getvar product"(if it hangs on waiting for device, open your task manager and update the driver for the device with a triangle next to it named jem with the drivers in my signature
.) Once that command can run successfully, run these three commands:
fastboot -i 0x1949 flash bootloader u-boot.bin
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 reboot
Now pray everything went well, because if your bootloader had a bad flash your going to have a hard brick. It should boot into stock os. Tada! I'm going to get soupemagnet to make sure i explained this correctly just to make sure i didn't miss something, you don't want to hard brick the kindle, that's a pain to even attempt to recover from without a major understanding of to solder and hookup an emmc to an sdcard reader.
stunts513 said:
Wanna mention ahead of time, i am not responsible if you hard brick your kindle by doing this, i dont like messing with the kindles bootloader unless i have to personally.
Ok follow the instruction on Amazon's Website for manually updating a kindle. This might either bootloop/go straight to recovery once you do this, if not your probably on stock unrooted without twrp or 2nd bootloader, usually you can tell pretty easily since the kindle logo would be blue if it wasn't stock, assuming that for some reason it either does bootloop/go straight to recovery or for some reason works but has twrp and second bootloader please read on.
Keep a copy of the update on your pc. Now this gets a bit more complicated because i realized the update is a bin file, but if i remember correctly it should just be a zip file, so either tell windows open with winrar or 7zip, winzip, etc, or try enabling file extensions in your folder options on windows, and changing the extension to .zip. Once you do that extract u-boot.bin and recovery.img from the recovery folder. Put your kindle into fastboot mode(hit reboot then bootloader in twrp). Now you need a copy of fastboot.exe, so use a utility like kindle fire first aid and remember to put the recovery.img and u-boot.bin into the folder with fastboot.exe. Open a command prompt and cd into the directory that the fastboot command is in (in kffa) and verify we have a connection to the kindles fastboot by running "fastboot -i 0x1949 getvar product"(if it hangs on waiting for device, open your task manager and update the driver for the device with a triangle next to it named jem with the drivers in my signature
.) Once that command can run successfully, run these three commands:
fastboot -i 0x1949 flash bootloader u-boot.bin
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 reboot
Now pray everything went well, because if your bootloader had a bad flash your going to have a hard brick. It should boot into stock os. Tada! I'm going to get soupemagnet to make sure i explained this correctly just to make sure i didn't miss something, you don't want to hard brick the kindle, that's a pain to even attempt to recover from without a major understanding of to solder and hookup an emmc to an sdcard reader.
Click to expand...
Click to collapse
Okay, let me stop you right there. There's no need to manually flash those images in fastboot and, as you are aware, it isn't the safest option.
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
^^ what he said, I wasn't aware the amazon zip was compatible with twrp, it has files that a flashable zip tend to have but I never looked into it. Now I know something new for future reference. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
soupmagnet said:
Okay, let me stop you right there. There's no need to manually flash those images in fastboot and, as you are aware, it isn't the safest option.
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
Click to expand...
Click to collapse
did what you said but install failed so pushed cynagamod to it and installed now i am stuck on kindle logo cant do nothing not even boot to twrp.
Time for a fastboot mode and kffa... If you at some point installed the drivers for fastboot then this should go smoothly, if not you will have to keep your device manager open I. With does and update the unknown jem device that's detect to the drivers in my signature. Once you do manage to make sure that the jem device is detected and has its drivers installed turn the kindle off and unplug it, then on your PC run "fastboot -i 0x1949 getvar product", once it says waiting for device plug your kindle in. It should go into fastboot mode, once there use kindle fire first aid to restore the system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Time for a fastboot mode and kffa... If you at some point installed the drivers for fastboot then this should go smoothly, if not you will have to keep your device manager open I. With does and update the unknown jem device that's detect to the drivers in my signature. Once you do manage to make sure that the jem device is detected and has its drivers installed turn the kindle off and unplug it, then on your PC run "fastboot -i 0x1949 getvar product", once it says waiting for device plug your kindle in. It should go into fastboot mode, once there use kindle fire first aid to restore the system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
lol i am so lost.
Basically you need to get a copy of kindle fire first aid from the 7" general section of the forum(yes I know it says 7" but its more liken all second generation kf's), open a command prompt as admin, and CD into the kindle fire first aid directory, run the command mentioned in my last post and plug the kindle in while its off. If it goes into fastboot mode then great, if not you have to install the fastboot mode drivers, you must open the device manager, and when you power on the kindle it should briefly show a jem device, you have to update its drivers to the ones in my signature before the device disappears. Once that is working run the command again. and do as previously mentioned.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
soupmagnet said:
To revert to stock (safely), download the appropriate software update for the device from Amazon (onto the device itself), rename it from update.bin to update.zip (very important), factory reset in recovery (extremely important), then install the update.zip in recovery.
Upon rebooting, there will no longer be a 2nd bootloader or custom recovery, and everything will have been reverted back to pure stock.
Click to expand...
Click to collapse
Thank you so much for this solution. Although I get my 7HD to enter fastboot mode with cable - I can't get these other solutions to work.
In TWRP I REBOOT and see RECOVERY - but when I hit RECOVERY it just boots back to TWRP. Is that all I'm looking to do before going to INSTALL the .bin file (now renamed as .zip)???? thanks much...
rightjb said:
Thank you so much for this solution. Although I get my 7HD to enter fastboot mode with cable - I can't get these other solutions to work.
In TWRP I REBOOT and see RECOVERY - but when I hit RECOVERY it just boots back to TWRP. Is that all I'm looking to do before going to INSTALL the .bin file (now renamed as .zip)???? thanks much...
Click to expand...
Click to collapse
Flash from TWRP and then reboot into system. You'll need to Swipe to factory reset first.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Flash from TWRP and then reboot into system. You'll need to Swipe to factory reset first.
Click to expand...
Click to collapse
That worked perfectly. Thank you so very much
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.
Hi,
I got as far as rooting my Kindle then realised I needed a specific cable to enter fastboot mode. Is there a way to install twrp and a different ROM without it or do I need to go and buy one?
Kindle fire 2012.
10.5.1.
Thanks.
You can, but if you soft brick, you will need a fastboot cable to revive your Kindle. Make ONE mistake and that'll happen. After you flash the bootloader, boot.img, and the recovery.img, there's no turning back until you've flashed a rooted ROM or a fastboot cable. So: when you get to the blue screen, you have one chance to enter recovery, or you will soft brick. I reccomened pressing the power button multiple times when it prompts you to enter recovery. Once you're in TWRP, you CANNOT reboot until you've flashed a custom ROM, or you will soft brick. So, unless you have a custom ROM installed already, there's no point in using TWRP's backup system.
Use theese drivers to get your ADB/Fastboot drivers installed. (Assuming you have Windows), and enable ADB Debbuging in Settings>Security.
If you haven't already, ROOT YOUR DEVICE. I recommend Root w/Restore by Bin4ry. Use the Old method (download here)
Next: BACKUP EVERYTHING!!!!!!!!!!!!!!!!!!!!!!!11 You will not be able to go back and do any last-minute backups after this.
Then, search Google for Flashify, and install the .apk) Open it, give it root permisions, tap the 3 dots on the top right, and choose "Reboot bootloader". Tap it once more and then your Kindle (hopefully) will boot into fastboot mode.
Make sure your fastboot drivers are working.
Use theese three
files and this thread for instructions on installing the bootloader and TWRP. Ignore anything that mentions stack override, backing up, and fastboot cables.
Once you're in TWRP, keep your Kindle plugged in and find a ROM. Grab OpenGapps pico for your specific ROM version too. Grab this to gain root. ADB push those to /sdcard/, factory reset, wipe /system, and flash all 3 zip files in this order: 1. ROM 2. Gapps, 3. SuperSu. Reboot & enjoy.