Develop Bugs

[recovery] twrp2 install on windows

okay, this is to try to simplify the install for most windows users...
for starters get over to the teamwin website and download the official rc0 which comes with firefirefire bootloader so you can easily get into recovery with our 1 power button.
after youve downloaded the recovery file, put this file in the directory that your adb and fastboot is in, connect your device and open a cmd window
cd to the directory adb and fastboot is in, for me i typed
cd c:\sdk_tools (enter)
c:\sdk_tools becomes the directory, so now
adb shell (enter)
su (enter)
idme bootmode 4002 (enter)
so now your bootmode is set. now type in:
exit (enter)
exit (enter)
adb reboot (enter)
it should reboot to the splash screen of kindle fire in fastboot mode, now type in
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img (enter)
it should install, show team wins image, then reboot to the yellow triangle of firefirefire...
this is okay. from here, on windows, my computer did NOT read the device anymore and it was stuck in fastboot and wouldn't take commands. this issue is related to the drivers for some reason... what i did was reboot my pc, reconnected my device and it came up as a unknown device. this is okay!
go to devices and right click the one with an xclimation mark and click update drivers. choose manually and then choose out of available drivers. you need to select android phone or something android related depending on what drivers you had installed previously. i chose my asus android device since thats what i had when i first got adb working. after u choose android device choose adb generic and it should install fine.
after this get back in ur cmd prompt, cd to the proper directory and type this in
fastboot devices (enter)
u should get a listed device.
from here you can then change bootmode to properly reboot ur device
fastboot oem idme bootmode 4000 (enter)
fastboot reboot (enter)...
should be done! enjoy!

After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.

krelvinaz said:
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
Click to expand...
Click to collapse
when using apps to boot to recovery, can u get out of recovery without issue? someone said it gets stuck in the wrong bootmode?
Sent from my HTC Glacier using xda premium

I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).

krelvinaz said:
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
Click to expand...
Click to collapse
Yep, if you do everything right and have FFF and TWRP installed correctly, you should be able to flip between ROMS without too much trouble, and without have to use fastboot again.

Hmm...while attempting to reinstall the drivers for the Fire, I'm at a road block.
I see the kindle in device manager, and am informed that it's not installed correctly, but while manually choosing the drivers I'm greeted with the following (attached).
This is after choosing Android Phone from the available drivers.
Any ideas, guys?

reboot ur device and reconnect to ur PC.
Sent from my HTC Glacier using xda premium

Bricked?
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help

ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium

leglerreddin said:
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
Click to expand...
Click to collapse
when the device is in fastboot it is unrecognizable with adb, just enter the fastboot commands and you'll be fine.

smirkis said:
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I wish that was the case, i have tried a million different fastboot and adb commands, ive rebooted, used another os, the drivers are installed as an android composite adb interfaced, its still not registering as an adb or fastboot device.

EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers

CrackMonkey91 said:
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
Click to expand...
Click to collapse
I still had issues installing drivers after it booted to the yellow fire triangle (on Win7 x64 - even after adding the other device id to both x86 and x64 sections of the inf and ini of the drivers). Rebooting my computer with the Kindle plugged in caused the Kindle to reboot normally after which I used a terminal to set the boot mode to 4000:
Steps I took after doing step 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' (enter):
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
- Open the terminal app. (I used Terminal Emulator)
- Type 'su', press enter. (Superuser will pop-up - select allow)
- Type 'idme bootmode 4000', press enter.
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.

uunnzz said:
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
Click to expand...
Click to collapse
this my friend, is interesting.

Stuck at KindleFire white/orange logo. Unresponsive to ADB commands.

First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help

I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?

veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?

Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!

wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.

kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?

wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.

wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.

kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.

Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app

Kindle Fire stuck on boot triangles

I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>

Justos said:
I was told to post this here:
The Problem:
I tried to take the crappy amazon software that only works in the US off this kindle fire, Installed JandyKane and Gapps with no problems (i cleared dalvik cache, regular cache, and factory reset) Also installed Clockwork Recovery (which i read somewhere that might have been the problem).
(note: I used the KF utility)
Now when i turn the device on, it shows the Kindle fire logo for a second or two, then a bunch of triangles float on the screen forever and nothing happens.
Ive tried a few unbrick utilities but it keeps saying it cant find the device. Im having troubles booting into recovery mode. (the utility says device not found)
This isnt even my Kindle Fire and its causing me so many problems >.>
Click to expand...
Click to collapse
Is this what you're refering to when you say you see floating triangles?
http://androidbootanimation.com/wp-content/uploads/2012/08/nexus-7-bootanimation.jpg
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Also, I would highly suggest flashing TWRP (team win recovery project) rather than CWM on the Kindle Fire, on most devices I would recommend CWM but on this one it doesn't work as well and leads to problems >>
I also assume that you flashed firefirefire because you said you saw the kindlefire logo before it went to the triangles so you should be fine on that front.

nschiwy said:
Is this what you're refering to when you say you see floating triangles?
If so, That is the jandycane/Jellybean Boot animation. On first boot that could take a few minutes before it finishes. It does, however, sound like you are having other problems... have you tried contacting the kindle using fastboot?
Click to expand...
Click to collapse
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?

Justos said:
Yes thats it! Im going to leave it on for about 5-15 minutes and see what happens. il let you know
I have tried to boot into fastboot mode with the utility and it says cannot find the file specified.
btw: i dont think i installed firefirefire...
EDIT: Yep, after letting the animation run for 10 minutes still nothing.
Im going to try using TWRP now. Il let you know if it helped.
EDIT2: Nope im getting random errors in the command prompt. Is it 100% necessary to use this program?
Click to expand...
Click to collapse
If you're talking about KFU, then no. It is not 100% necessary, It is just designed to make it easier for users so they don't have to use command prompt on their own. I am uploading KindleADB from the burrito root method to help us with what you need to do. I will post a link here when it is finished uploading. Do you know how to use command prompt/adb at all?
KindleADB.zip: http://www.mediafire.com/?1fb30q3wqf95b3i
download this file and unzip and then place it on the root directory of your C:/ Drive (this is not completely necessary, it is just for convenience)
Then try seeing if your device shows up in adb by typing in:
Code:
cd /
cd kindleadb
adb devices
OR
Code:
cd /
cd kindleadb
fastboot getvar product
Either way you want it to show either a series of numbers or say something like amazon kindle or something to that degree, if it is blank or does not leave the <waiting for device> status then we will need to go in another direction. My suggestion for fastboot would be to turn the kindle completely off and then do those commands and then plug in your kindle when it says <waiting for device>... get back to me on your results and we can go from there

Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .

I'm having the same issue here.
The triangles keep turning and nothing happens.
In the KFU the devices keep showing OFFLINE and Boot Status UNKNOW.
The cd /
cd kindleadb
adb devices
don't show the device and
cd /
cd kindleadb
fastboot getvar product
show waiting for device
Edited:
I dunno what i've done, but im KFU appears Online in normal boot (4000), but the options don't work anymore.

Justos said:
Did both of them. On the first part it says
List of Devices attached: (nothing shows up)
second time i did exactly what you said. it was waiting for device before i turned the kindle on, nothing happened.
EDIT: Okay I tried using the utility again, whenever i try to fastboot or boot into recovery it gives me this error
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
Click to expand...
Click to collapse
As long as you have CWM instead of TWRP, you're just wasting your time trying to install Jelly Bean. Install TWRP and try again.

same problem
I have the same exact problem with my fire, it happened two days ago but i hadn't seen anyone else with the problem. I couldn't fix it so i ordered a factory cable on ebay, I'm waiting on that now...

no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...

Thepooch said:
no fff? how about just booting to recovery and flashing a new rom after a full wipe or restoring a backup or have the normal ways of doing things just become obsolete lol I mean so you cant flash isc or jelly bean mount your sd card in recovery transfer one of a few different cm7 roms which will flash right on cwmr and your golden ...
Click to expand...
Click to collapse
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found

recovery?
Reinaque said:
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
Click to expand...
Click to collapse
i'm seeing that too when i try to change it to recovery on KFU, but now its actually showing adb online and boot status 4000 as oppposed to when it said offline and unknown for me

What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?

Justos said:
What are all the ways to boot into recovery mode? It wont do it with the KFU.
I understand what I need to do now, Factory reset, then install TWRP, then firefirefire, then flash the rom and Gapps?
How am i supposed to do this if i cant get into recovery mode?
Click to expand...
Click to collapse
First I would try using the kindle unbrick utility:
I couldn't find the thread for this so I just have it uploaded to my mediafire account: http://www.mediafire.com/download.php?6kxjs8kbmgn8h3l
I also found this Kindle Fire Unbrick Utility, it might actually be a newer version of the one I provided above with a Graphic UI: http://forum.xda-developers.com/showthread.php?t=1428428
If that doesn't work I would suggest trying a linux environment to contact your device, as Android is linux based and therefore can communicate with a linux machine better than a windows machine. (plus drivers are always a giant mess in windows)
Use this guide to make a portable linux box to try to save your kindle:
http://forum.xda-developers.com/showthread.php?t=1670405
If all else fails, you're probably going to need a factory cable to get your Kindle back up and running:
http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
Once you have this you can run commands from linux very easily to unbrick your kindle. If you need help with this feel free to PM me.

Amazon KF2 (v.10.4.3 & v10.4.6) - Install CyanogenMod

First - sorry for my English. Last monday i received my KF2 and when I could not find the instructions on this forum for version 10.4.3 - i decided to try it myself.
Introducing: Kindle Fire 2 (v10.4.3 & v10.4.6 already tested) installing CyanogenMod
** YOU SHOULD HAVE A WORKING NORMAL (NOT FASTBOOT) CABLE + ADB DRIVERS/ACCESS ON YOUR PC. **
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
INITIAL SETUP INSTRUCTIONS
STEP 1. Install ADB Drivers for Kindle HD and enable ADB on tablet Settings->Security->Enable ADB->On
Check ADB:
Code:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for ADB on your PC before proceeding.
STEP 2. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # This will take a few minutes
Take those files and put them somewhere safe.
STEP 3. Getting root
Just follow this threat http://forum.xda-developers.com/showthread.php?t=2075959 -> everything working fine
STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Open cmd and promt:
Code:
adb shell su -c "reboot bootloader"
Your Kindle should reboot in fastboot mode, and now flash bootloader:
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 reboot
STEP 5. Install TWRP
First, download CM and GAPPS and copy it to SDCARD:
CM-10.1 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the top rom CM10.1 version)
1. Copy com.powerpoint45.FMKilo-2.apk to the tablet (you can get this apk from here http://d-h.st/n7L)
2. Enable on Kindle: Device -> Allow Installation of Applications
3. Use file browser (i recomended to use ES Explorer) to install apk.
4. Run Tweezermod Installer and answer on all question about Super User -> "Allow"​
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
In this time your kindle can not boot, u'll see BLUE logo, then ORANGE and then device restarted again. Don't worry - it's ok
STEP 6. Install CyanogenMod
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
Dont forget to do FULL WIPE - cache, dalvik cache, factory reset, system.
Enjoy
Tested on my Kindle Fire 2 v10.4.3 & v10.4.6

7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.

pythonjosh said:
7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.
Click to expand...
Click to collapse
Check STEP 1 to check ADB. If it not working check this manual https:// developer.amazon.com/sdk/fire/connect-adb.html
When ADB start working - copy CM and GAPPS to kindle:
Promt in CMD:
Code:
adb push /path/to/filename /sdcard/download/filename

I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.

I found instructions via terminal emulator to get it rebooted into fastboot, in hopes of flashing CM 10.2 via fastboot.
Looking up the fastboot syntax for flashing a new rom, I've always used recovery on my other devices, but i don't have that option now.

pythonjosh said:
I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.
Click to expand...
Click to collapse
ADB Sideload - good idea. Try this manual:
1. Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
2. From the command line on PC, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.​
My mistake in manual. Better way - copy rom file to sdcard before STEP 5.

I'm still unable to use adb sideload, reports "device not found". I have the usb drivers installed, your tutorial is the only one I have used, I can't use TWRP at all.
It works, but USB drive mounting doesn't work, ADB sideload doesn't seem to work. No errors in the log, but ADB reports device not found.
I don't know what to do from here. It's nothing like 4EXT or CWM.

Ok so I have got it in fastboot by going to Advanced->Terminal, idme bootmode 4
Once in fastboot , fastboot -i 0x1949 devices returned a device number
I flashed CM10.2 using "fastboot -i 0x1949 flash system CM102.zip
Then I ran fastboot -i 0x1949 oem idme bootmode 1
Then rebooted, doesn't load ROM, got back into TWRP, changed bootmode back to 1, reboot, says I have no OS.
That's my current status. Seems others have been at this point before, still workin on this.

Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.

pythonjosh said:
Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.
Click to expand...
Click to collapse
Don't trash the old one after u get the new one, we have a viable method now to unbrick a hard bricked kindle. The person behind the fix is working on a more user friendly version of the device that doesn't require soldering. Check it out: http://forum.xda-developers.com/showthread.php?t=2391047
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

kindle fire 2 completely dead
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:

jeffrey00345 said:
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:
Click to expand...
Click to collapse
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.

kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
thanks for your reponse I would try to get a replacement from Amazon.
---------- Post added at 03:29 PM ---------- Previous post was at 02:59 PM ----------
kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
I have contacted Amazon and they said that they would send a replacement to me but now I'm worried because I didn't tell them that it was my fault, I just told them the Kindle is not working.Is this ok?

Trying to make it work
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?

"STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/o...rod-10.2.4.bin"
On 2nd gen Kindle Fire Non-HD. ver 10.4.6 rooted , can this step be completed without a fastboot cable?
I have the original usb cable. Maybe with Kindle Aide?
or tweezermod?
http://forum.xda-developers.com/showthread.php?t=2106463

Hello, I also I have the 10.4.6 rooted.
I have the same question that adaweawe, I can install bootloader / recovery with the original cable?
thanks

movesandpepper said:
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?
Click to expand...
Click to collapse
try other USB ports. one of my usb ports did not recognize. try install both driver exe from the zip.

Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
What I'm doing with the standard USB cable.
edit
After trying on a USB, now the error is this:
target reported max download size of 486539264 bytes
error: cannot load otter2-u-boot-prod-10.2.4.bin

galaxyn84 said:
Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
Click to expand...
Click to collapse
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
" *Note: After several conference calls with the Amazon Development Team we found Amazon applied a patch to the Bootloader in an effort to lock down the Bootloader, this patch rarely causes the Bootloader to stick or Bootloop, please use the above link to release the Bootloader. We have removed this patch from the boot-prod.img eliminating future issues with recovered HD 8.9" users. "
http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
and
+Note: As of Amazon OS update 7.3.x+, 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 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2271909
applies to 2nd gen nonHD too i think
also hesitant to try tweezermod due to some bricks:
http://forum.xda-developers.com/showthread.php?t=2106463&page=4
I'm rooted and downgraded to bootloader version 10.2.3 and it still causes the red screen? I used the computer method and the terminal doesn't have any errors but recovery is not there. My Kindle Fire 2 is disconnected from wifi so it won't be updated to 10.4.1 Any idea why?
Click to expand...
Click to collapse
i really want to install cyanogenmod 10.1 on my rooted 10.4.6 without fastboot cable, but i think amazon updated bootloader to make it impossible without fastboot cable.
i disabled OTA updates and hope someone figures out 10.4.6 -> CM 10.1 without fastboot cable

adaweawe said:
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
Click to expand...
Click to collapse
HI
I enter fastboot mode as shown in the tutorial
"" "" Adb shell su-c "reboot bootloader" "" "" "
I ask for superuser permissions, accept and restart in fastboot mode
Appear a black screen with fastboot logo in red, and a traffic light with flashing green light.
But I can not move from there ....

[Q] No fastboot/ADB unauthorized/TWRP loop = Bricked?

Hi all,
I apologize in advance, but I was unsure if there was another thread my issue would best be posted. I have a kindle hd 8.9 32gb that is now stuck in a boot loop at the twrp (2.8.3.0) splash screen (after installing the new Candy5 5.1.1 rom). The rom installed fine and ran perfectly the 1st time, but upon the next device restart it entered the recovery loop and never gets past the splash screen. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. With the 8.9 and no ADB, I also am also unable to enter fastboot mode. Any thoughts or suggestions, or am I bricked with the only possibility being a direct e-MMC restoral? *my soldering kung-fu is extremely weak*
Thanks in advance for any answers!

I have the same problem as you. I updated CM to 12.1, perform a factory reset and I got stuck on twrp screen which is blinking...

Possible Solution
I did something similar but with latest CM nightly rom and got stuck in the twrp recovery mode as a continuos loop, but mine was detected with the status "recovery" via adb;
Check if your adb /fastboot drivers are correctly installed and your not pluggin your kindle to a usb 3 port, then try this:
adb reboot bootloader
It will order the kindle to reboot in fastboot, after that you can just reflash the kindle to its original state with the fastboot commands from your backup.
Dont forget to erase the userdata, cache and all that stuff, you can do it with kindle firstaide
After that just redo all the process of rooting and install a Custom Rom.
Note: I got stucked on a loop of the kindle fire logo, cuz i didnt erase the userdata, but I was able to enter fastboot after the restore, thats why i suggest you delete the cache and other stuff

EDIT: Nevermind. Managed to resolve the issue by booting into fastboot mode, erasing cache and userdata using SR Tool from the KFHD_SRTv1.3.5 and then sideloading the ROM and GAPPS. I lost everything but it means i do not have to buy another KFHD.
Really grown attached to it, especially when the guys at Cyanogenmod keep on releasing updated OS's every year or so, making my tablet feel new every time.
Good work fellers.
I have a Kindle Fire HD with the CM12.1 ROM installed. After installing a nightly i did a factory reset from within the OS and it is stuck in a bootloop occasionally flashing on the teamwin splash screen.
Have i bricked my system or is there a solution.
I posted here because it appears that the op and myself have the same issue.
I tried ADB method but when i use the command "adb device" it shows as unauthorized so it will not allow me to run the adb shell or reboot command.
Any solutions will be much appreciated.

Hi to all
I have the same problem with twrp blinking after a factory reset on cm 12.1 ... I tried adb or fastboot commands (with KFHD_SRT_v2.1 or latest android sdk tools) but I cannot see my device. Consider that I installed adb drivers on a win 8.1 pc with 2.0 and 3.0 usb ports and I am using the standard cable included in the kindle fire hd 8.9 package.
Where I am wrong? A fastboot cable can solve the problem? Sorry for this question but I read many threads and there are different opinions about that...
Thanks in advance for any help.

KFHD 8.9 stuck in bootloop
hey guys,
im need of help a few days ago i tried installing a 2nd bootloader and rom to my kindle fire hd 8.9 i used the wrong files which were the ones for the hd 7 i believe i rooted my kindle succesfuly but the problem came once i flashed it, it just rebooted and now its stuck in a bootloop i have android sdk installed and the kindle fire adb drivers installed i try to put my kindle into fastboot mode by typing in this code: fastboot -i 0x1949 getvar product. once i type that into the cmd it says waiting for device i plug in my turned off kindle and it just turns on and goes into the bootloop and doesn't go into fastboot mode can anyone help me figure out why it won't go into fastboot mode thank you.

albertferrari_1995 said:
hey guys,
im need of help a few days ago i tried installing a 2nd bootloader and rom to my kindle fire hd 8.9 i used the wrong files which were the ones for the hd 7 i believe i rooted my kindle succesfuly but the problem came once i flashed it, it just rebooted and now its stuck in a bootloop i have android sdk installed and the kindle fire adb drivers installed i try to put my kindle into fastboot mode by typing in this code: fastboot -i 0x1949 getvar product. once i type that into the cmd it says waiting for device i plug in my turned off kindle and it just turns on and goes into the bootloop and doesn't go into fastboot mode can anyone help me figure out why it won't go into fastboot mode thank you.
Click to expand...
Click to collapse
When it's in the TWRP bootloop, the device should be in adb mode, so you can flash recovery, erase cache, etc..
I'd start off with a "adb erase cache", and that should get you past the TWRP bootloop.
---------- Post added at 03:21 PM ---------- Previous post was at 03:15 PM ----------
jstevensaz said:
Hi all,
I apologize in advance, but I was unsure if there was another thread my issue would best be posted. I have a kindle hd 8.9 32gb that is now stuck in a boot loop at the twrp (2.8.3.0) splash screen (after installing the new Candy5 5.1.1 rom). The rom installed fine and ran perfectly the 1st time, but upon the next device restart it entered the recovery loop and never gets past the splash screen. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. With the 8.9 and no ADB, I also am also unable to enter fastboot mode. Any thoughts or suggestions, or am I bricked with the only possibility being a direct e-MMC restoral? *my soldering kung-fu is extremely weak*
Thanks in advance for any answers!
Click to expand...
Click to collapse
I'm in this same situation... BUT, I finally got into TWRP and was starting to restore the ROM, but then my battery died... while i was in TWRP recovery.
Now my device won't power on (won't get to the Kindle Fire boot logo). I can't adb or fastboot, since the device won't power on, even when I plug it into the computer. I've tried charging it overnight, hoping that would help.
Nothing.
Do any of you Android gods (@Hashcode) have anything else I can try? Anything in the Android SDK that might help and at least allow the device to accept a charge?
Thanks!

Same problem
I'm in the same situation as the OP. Unfortunately, my device is unauthorized in ADB and since I'm stuck in the TWRP loop, there's not much else I can do. I wondered if it was perhaps the drivers causing the issue, so I fuddled around uninstalling and reinstalling to no avail. One thing to note is I'm using Windows 10, not sure if that could be causing any issues.

adb devices - Unauthorized - Amazon Jem- TWRP swithed to Cyanogen Recovery
I have similar issue. I have a kindle hd 8.9 16gb.I had 2nd boot loader installed with TWRP recovery. One day, I rebooted at it and it rebooted into cyanogen recovery for some reason (after installing the new CROM 5 5.1.1 rom). The rom installed fine and ranOK the 1st time, but upon the next device restart it entered the cyanogen recovery loop which has some options i.e. 1. Reboot system 2 apply update, wipe data /factory reset 3. wipe partition, 4. wipe media 5. reboot to bootloader ( fast boot mode)6. Power down and 7.view recovery logs,. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. adb devices results into xxxxxx ( some number ) unauthorized. I have tried all the options. No. 5 takes me to fast boot mode. but I can’t go any farther. The boot loop is driving me crazy . Can anyone help me? Thanks in advance.

tukky52xda said:
I have similar issue. I have a kindle hd 8.9 16gb.I had 2nd boot loader installed with TWRP recovery. One day, I rebooted at it and it rebooted into cyanogen recovery for some reason (after installing the new CROM 5 5.1.1 rom). The rom installed fine and ranOK the 1st time, but upon the next device restart it entered the cyanogen recovery loop which has some options i.e. 1. Reboot system 2 apply update, wipe data /factory reset 3. wipe partition, 4. wipe media 5. reboot to bootloader ( fast boot mode)6. Power down and 7.view recovery logs,. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. adb devices results into xxxxxx ( some number ) unauthorized. I have tried all the options. No. 5 takes me to fast boot mode. but I canâ??t go any farther. The boot loop is driving me crazy . Can anyone help me? Thanks in advance.
Click to expand...
Click to collapse
when in fastboot mode, hook the kindle up to a PC with a terminal/command prompt (also make sure the kindle drivers are installed if you're running Windows) and enter fastboot -i 0x1949 oem idme bootmode 4000. you should see successful text on both the kindle and your terminal after running that command. if that's true, just do fastboot -I 0x1949 reboot afterwards to reboot the kindle.

monster1612 said:
when in fastboot mode, hook the kindle up to a PC with a terminal/command prompt (also make sure the kindle drivers are installed if you're running Windows) and enter fastboot -i 0x1949 oem idme bootmode 4000. you should see successful text on both the kindle and your terminal after running that command. if that's true, just do fastboot -I 0x1949 reboot afterwards to reboot the kindle.
Click to expand...
Click to collapse
Thanks Moster1612:
Just one more thing. adb devices comand gives me F:\WINDOWS\system32>adb devices
List of devices attached
B0C91004250411V7 unauthorized
can you help me with that. I think i am close to solving this issue.
I did follw your instruction and here is what i git
F:\WINDOWS\system32> fastboot -i 0x1949 oem idme bootmode 4000
< waiting for any device >
...
OKAY [ 0.050s]
finished. total time: 0.058s
F:\WINDOWS\system32>fastboot -I 0x1949 reboot
fastboot: unknown option -- I
F:\WINDOWS\system32>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s
My device went back to cyanogen recovery boot cycle again. Is it because adb devices not recognizing the device?

tukky52xda said:
Thanks Moster1612:
Just one more thing. adb devices comand gives me F:\WINDOWS\system32>adb devices
List of devices attached
B0C91004250411V7 unauthorized
can you help me with that. I think i am close to solving this issue.
I did follw your instruction and here is what i git
F:\WINDOWS\system32> fastboot -i 0x1949 oem idme bootmode 4000
< waiting for any device >
...
OKAY [ 0.050s]
finished. total time: 0.058s
F:\WINDOWS\system32>fastboot -I 0x1949 reboot
fastboot: unknown option -- I
F:\WINDOWS\system32>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s
My device went back to cyanogen recovery boot cycle again. Is it because adb devices not recognizing the device?
Click to expand...
Click to collapse
No, that's a separate issue. What I would suggest right now is for you to download the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flash the files as directed to in step 5. However, don't power off the kindle - it's already in fastboot mode, so there's no need to turn it off and tell it to reboot into the bootloader. Also, ignore the post warning about flashing the freedom-boot image - we're only using it temporarily.
Once you have the files flashed, reboot into recovery. If you're in TWRP, go ahead and flash CM or another ROM. Just avoid booting into system until you do so.

Flashing files in Flashboot mode.
monster1612 said:
No, that's a separate issue. What I would suggest right now is for you to download the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flash the files as directed to in step 5. However, don't power off the kindle - it's already in fastboot mode, so there's no need to turn it off and tell it to reboot into the bootloader. Also, ignore the post warning about flashing the freedom-boot image - we're only using it temporarily.
Once you have the files flashed, reboot into recovery. If you're in TWRP, go ahead and flash CM or another ROM. Just avoid booting into system until you do so.
Click to expand...
Click to collapse
Hi Monster 1612! Thank you very much for helping me out. Please bare with me b/c I am a newbee. Should I download File no.2 & 3 from Step 2 or more. Can you explain a little more about "reboot to the bootloader from CM recovery" . If I do that it takes my device to fastboot mode. What is flash the files as directed to in step 5. How to flash the files in flashboot mode". Is there a link about this? Are you talking about codes in the box in Hashcode's thread? I really appreciate your help.

The files and instructions should be located in this thread.
As for booting into fastboot mode on the kindle, this should be easy - in its current state, it just boots into Cyanogen Recovery, right? Anyway, you just need to choose option 5 in that recovery menu to enter fastboot mode.

monster1612 said:
The files and instructions should be located in this thread.
As for booting into fastboot mode on the kindle, this should be easy - in its current state, it just boots into Cyanogen Recovery, right? Anyway, you just need to choose option 5 in that recovery menu to enter fastboot mode.
Click to expand...
Click to collapse
Thanks Sir!
I will follow the instructions and report back later!

KDHD recovery stuck in yeloow/white logo
tukky52xda said:
Thanks Sir!
I will follow the instructions and report back later!
Click to expand...
Click to collapse
I downloaded the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flashed the files as directed to in step 5 from Hashcode link.. Didn't power off the kindleas at it was already in fastboot mode as you said. Once I had the files flashed, rebooted into recovery. Wow, it rebooted into TRWP recovery mode. with 8 buttons (reboot,advance,mount,setting,restore backup,isnstall, wipe). I was so happy because of your help. Then I did the stupid thing. I rebooted probably into the system. Now My device is stuck in Kindle fire Yellow/white logo. Now ADB command works but adb devices dont bring anything ( waiting for devices). The driver is installed but my PC does not see it device manager. I lost fastboot mode too. I was so close sir because your help. I remember you telling me to flash into a ROM and not boot into system.
That makes me a real noob. Now please help me if you can. What is next? Is thre still a hope?

tukky52xda said:
I downloaded the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flashed the files as directed to in step 5 from Hashcode link.. Didn't power off the kindleas at it was already in fastboot mode as you said. Once I had the files flashed, rebooted into recovery. Wow, it rebooted into TRWP recovery mode. with 8 buttons (reboot,advance,mount,setting,restore backup,isnstall, wipe). I was so happy because of your help. Then I did the stupid thing. I rebooted probably into the system. Now My device is stuck in Kindle fire Yellow/white logo. Now ADB command works but adb devices dont bring anything ( waiting for devices). The driver is installed but my PC does not see it device manager. I lost fastboot mode too. I was so close sir because your help. I remember you telling me to flash into a ROM and not boot into system.
That makes me a real noob. Now please help me if you can. What is next? Is thre still a hope?
Click to expand...
Click to collapse
The bootloader should still be responsive regardless of what's been flashed onto the kindle. Go ahead and completely turn off the kindle (hold the power button down for 10 seconds till the screen turns off), and then open a terminal on your PC. Type in fastboot -i 0x1949 getvar product , and plug in the kindle when you see <waiting for device>. After a few seconds, the kindle should be in fastboot, and the prompt should have outputted something like "jem-pvt-prod-04". Now repeat that flashing process again, and type fastboot -i 0x1949 reboot when done. Press and hold the recovery key (the one closest to the camera) until you're in TWRP, then flash CM or another chosen ROM from TWRP.
Happy to help!

monster1612 said:
The bootloader should still be responsive regardless of what's been flashed onto the kindle. Go ahead and completely turn off the kindle (hold the power button down for 10 seconds till the screen turns off), and then open a terminal on your PC. Type in [fastboot -i 0x1949 getvar product [/I], and plug in the kindle when you see <waiting for device>. After a few seconds, the kindle should be in fastboot, and the prompt should have outputted something like "jem-pvt-prod-04". Now repeat that flashing process again, and type fastboot -i 0x1949 reboot when done. Press and hold the recovery key (the one closest to the camera) until you're in TWRP, then flash CM or another chosen ROM from TWRP.
Happy to help!
Click to expand...
Click to collapse
My friend , you are becoming a saviour. Have you got any donate button for support? I would like to contribute. This time I am not going to rush. Want to make sure I undestand everything. What is [/I] before / after fastboot -i 0x1949 reboot and fastboot -i 0x1949 getvar . I hope its not any part of command. BTW, I dont see any key near the camera ( recovery Key?). I have kindle fire HD 8.9. This has power key and up and down volume key.

tukky52xda said:
My friend , you are becoming a saviour. Have you got any donate button for support? I would like to contribute. This time I am not going to rush. Want to make sure I undestand everything. What is [/I] before / after fastboot -i 0x1949 reboot and fastboot -i 0x1949 getvar . I hope its not any part of command. BTW, I dont see any key near the camera ( recovery Key?). I have kindle fire HD 8.9. This has power key and up and down volume key.
Click to expand...
Click to collapse
So far, I don't have a donate button - I'm worried about its legality, cause I'm not 18 for at least another year.
Anyway, the button we're talking about is volume up. It's the one closest to the camera, and the boot partition's programmed to boot into recovery when this button is pressed and held during initial boot (I.e.: when the Kindle Fire logo appears and changes from orange to blue). The fastboot flashing process I described above goes like this:
1) Power the kindle off completely, type fastboot -i 0x1949 getvar product, plug in kindle when prompted.
2) Kindle should boot into fastboot, and "jem-pvt-prod-04" or similar text will appear.
3) Flash TWRP, freedom-boot, and the 8.1.4 bootloader as you did before.
4) Type fastboot -i 0x1949 reboot when you're done flashing, then immediately press and hold volume up as soon as you see the kindle fire logo. Keep holding until you're in TWRP.
5) Flash a ROM, as well as gapps if desired.
6) Profit
Hopefully, this clears up any confusion.

monster1612 said:
So far, I don't have a donate button - I'm worried about its legality, cause I'm not 18 for at least another year.
Anyway, the button we're talking about is volume up. It's the one closest to the camera, and the boot partition's programmed to boot into recovery when this button is pressed and held during initial boot (I.e.: when the Kindle Fire logo appears and changes from orange to blue). The fastboot flashing process I described above goes like this:
1) Power the kindle off completely, type fastboot -i 0x1949 getvar product, plug in kindle when prompted.
2) Kindle should boot into fastboot, and "jem-pvt-prod-04" or similar text will appear.
3) Flash TWRP, freedom-boot, and the 8.1.4 bootloader as you did before.
4) Type fastboot -i 0x1949 reboot when you're done flashing, then immediately press and hold volume up as soon as you see the kindle fire logo. Keep holding until you're in TWRP.
5) Flash a ROM, as well as gapps if desired.
6) Profit
Hopefully, this clears up any confusion.
Click to expand...
Click to collapse
Hi Moster 1612!
I followed step by step evrything went by the book in fastboot mode ( see below). You are great. However, I cant understand for some reason, it did not boot into TWRP recovery and went back to Kindle fire logo. I did press the volume up key As soson as KF yellow logo came in but it stayed yellow. . I can turn it off by pressing for 10 secs. Now what my young friend?
Here are the illustrations:
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 getvar product
< waiting for any device >
product: Jem-PVT-Prod-04
finished. total time: 0.034s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.024s]
writing 'bootloader'...
OKAY [ 0.048s]
finished. total time: 0.079s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.457s]
writing 'boot'...
OKAY [ 1.524s]
finished. total time: 1.997s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 1.056s]
finished. total time: 1.517s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s