Database Users

Unbricking Kindle stuck at Boot Logo/Recovery loop

Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!

What is firefirefire? Have yet to see a formal definition of that

androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium

Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.

Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help

Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App

Sorry about that. I wish I could help.

I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App

Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App

My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?

*Snip*
Double post, fail.

CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...

CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App

Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.

Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.

Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"

try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium

Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?

jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.

You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!

[Q] Bootloop in TWRP + bricked device...

I just overall screwed up big time with this thing. I rooted 6.2.1, then uninstalled/froze a bunch of the stock apps (including the default Kindle launcher, as I had Go Launcher installed).
I then decided I wanted to restore to the factory default settings, as I wanted to use Amazon prime, among other things. I went into settings and hit the "restore to factory defaults button" (which was stupid, I know). Unsurprisingly, this resulted in Kindle Fire bootloops.
Trying to fix this, I used the KindleFireTool to install the most recent TWRP...which didn't work at all. It would just stay on the yellow triangle screen. Now, things have gotten even worse, though I don't know why. Whenever I plug the fire into the computer, it goes into TWRP bootloops!
For the brief few seconds that the Fire is on when plugged into my computer, the driver isn't recognized at all (shows up as "kindle" with a triangle next to it in device manager).
I know what I did was dumb, but even so, any help would be hugely appreciated.

YES YES YES!!!! OK HERES HOW I DID IT TO FIX THE BOOTLOOP OF TWRP
First you must download Kindle Fire Utility and extract it to your desktop
then go to command prompt or cmd then type in the location of the folder heres mine for example: C:\Users\Madaran\Desktop\Kindle Fire Utility\tools
then type in fastboot -i 0x1949 oem idme bootmode 4000
For me it said waiting for device all I did is rebooted the device and it worked
as the device reboot it will still go back to TWRP now type this in the command prompt
fastboot -i 0x1949 oem idme bootmode 4000
then it should reboot again and ITS FIXED
----------------------------------
I used this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=1428715

Thank you so much! I'll post results when I get the opportunity.
Well it didn't work...the thing isn't connecting to the computer properly. I think it's a goner.

Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.

I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...

skippwhy said:
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
Click to expand...
Click to collapse
It maybe your battery its low. Try to charge it and connect it again.

Definitely worth a shot
You were right! It was a battery issue

sirmavs said:
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
Click to expand...
Click to collapse
Hey guys... I kinda bricked my Kindle... I tried all the steps mentioned above. My Kindle boots but it freezes on the Kindle Fire Boot Screen. It does not load the home screen of Kindle with Shelf.
Please help

http://forum.xda-developers.com/showthread.php?t=1428428

[HOW TO] Recover Kindle Fire from corrupted read/write permissions in /system (6.2.1)

Link to original thread: http://forum.xda-developers.com/showthread.php?t=1452651
This is a specific guide to restoring your Kindle Fire from boot loop caused by changes in the /system/ directory permissions.
The problem:
After rooting my Kindle Fire, I tried to install the Android Market app and while doing so, messed up my read/write permissions of /system/app/
After rebooting my Kindle, the logo animation started looping endlessly, indicating there was a serious issue taking place.
The specs:
Device: Kindle Fire
Firmware: 6.2.1
Desktop: Mac Mini
OS: OS X Lion
The tools:
You will need,
1. The KindleFireRoot Kit from here (It has tools for all OSs)
2. TWRP 2.0 from here
3. The fbmode file found here to be able to stock fastboot in 6.2.1
The steps:
1. Move all the contents from both the downloaded KindleFireRoot Kit and TWRP into a single directory for convenience.
2. Assuming you were able to root your Kindle in the first place, it's likely you already have drivers installed (Windows). Check by opening a Terminal, navigating to the dir with all the tools and doing this on Windows:
Code:
adb kill-server
adb devices
on Mac:
Code:
sudo ./adb kill-server
./adb devices
Your device should be listed. If it is skip to the next step.
If it's not, install the drivers found in the usb_driver directory (Win only). In this directory you can find the adb_usb.ini file which you need to move to the .android directory that's inside /Users/[your_name]/
3. We will now use the fbmode to fastboot to stock 6.2.1 as explained in this thread.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
4. Now that we can fastboot, we will install TWRP 2.0.
Just run this command:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
...and reboot. The Kindle should boot into a screen with a yellow triangle and TRWP will install itself.
5. What you need to do now is tap the reboot button onscreen. As it reboots, hold down the Power Button until the light turns orange. You will then boot into TWRP. You will see a Menu with a bunch of Buttons.
6. Now it's time to boot up your Kindle as a USB Drive to repair the permissions.
Touch the Mount button and select the checkbox that says System. After that tap on Mount USB
All you have to do after that is type this in the Terminal and voila:
Code:
adb shell chmod 755 /systme/app
7. Reboot your device and enjoy.
Thanks to everyone who helped me figure that out in the original thread and the threads that I've linked. I might be missing a step. PM if you get stuck or just Reply on this thread.

/system/app kindle fire
Hi,
Thanks for the instructions. I got to the point where the yellow triangle shows up on my kindle fire after doing the fastboot command and touching the reboot button on the kindle screen. However, it just locks up after that and I never get to the subsequent menu. All I see is the yellow triangle on the screen with the instructions to press the power button for recovery. I have reset the power many times and all I get is the yellow fire triangle now. Any ideas how to get out of this loop? Thanks.

fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
if you'r done you may have to reset the boot mode to normal (when you are in twrp):
adb shell idme bootmode 4000
adb reboot

Windows doesn't seem to be recognizing my device anymore. I get an unknown usb device when I plug it in. When I run the fastboot commands I get a <waiting for device> from which it never returns. I tried to reinstall my android_winusb.ini file to the kindle, but windows says it is up to date. Windows gives me this error in the device manager: " Windows has stopped this device because it has reported problems. (Code 43)" Help!

you have to update the driver manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41

Thanks, that did it! I also had plugged it into another computer that recognized it as a kindle. I'm not sure if that mattered or not.

This seems to be great. Unfortunately I've got to a different thread and I think I totally bricked my Kindle. I was able to install and run TRWP. However I tried to do a recovery from Amazon Stock img. Then rebooted the kindle. After that the kindle rebooted and got stuck again. I tried to re-run TRWP but this time I got a different error message when tried to run adb shell to go into fastboot. The error message said the system shell could not be found. Adb shell is not accessible and if I do a fastboot command it says waiting for device.
If I do adb devices I can see the actual device # not anymore in recover mode but listed as device. But not able to run the adb shell. I am really frustrated!

that happend many others by trying to flash the original amazon rom
the original rom deletes fff, twrp and root
with a messed up system shell you have no possibility to get to fastboot mode
the only solution is to use a factory cable - you can build or buy one:
http://forum.xda-developers.com/showthread.php?t=1392693
the factory cable forces the kf to fastboot mode
restore with factory cable:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38
handling:
http://forum.xda-developers.com/showpost.php?p=21708081&postcount=157
or in short:
You must insert cable, then switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
test with "fastboot getvar product"
After kindle will be in fastboot, with Kindle Fire Utility install TWRP recovery and with recovery install prerooted stock or CM7 firmware.

[Q] kindle fire stuck!

my kindle fire is stuck on the Kindle Fire screen, with no animation.
i have looked through XDA but could not find anything with my problem.
i do not have TWRP or FFF.
I'm running the stock rom.
kindle is not recognized on ADB.
i uninstalled the driver, but now computer management doesn't have anything for the device listed.
i used the kindle fire utility to install the drivers, still not listed on computer management.
it is recognized in the bottom right as plugged in as a 'android adb interface'
i have tried using the kindle unbrick utility, but it says there is no device plugged in.
EDIT:
i restarted my computer. now the kindle is listed as unknown device in the bottom right and in computer management.
i am still unable to install new driver software on it, though.
EDIT:
I tried using the driver from the .android download, it says that it's not going to work.
if someone could help me, please, it would be great.
EDIT::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPDATE TO THE PROBLEM::::
the kindle is still in the kindle fire boot screen brick.
it went from being an 'unidentified device' to being 'android adb interface'
the error code has switched from code 43 to code 10.
it says Device Cannot start (code 10)
it is not recognized by ADB
unbrick utility still doesn't recognize.
neither does kindle fire utitlity.

look above

look above

look above

can someone please help me..

im having the same problem and cant find an answer anywhere we need help guys

maybe this helps:
for the kfu drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
Click to expand...
Click to collapse
that means:
your kf seems to be in fastboot mode -> adb commands not working
the question is what have you done to come to this situation ?
you can:
- try to switch to normal bootmode
- or try to install fff & twrp (this is done in fastboot mode)
switch to normal boot:
use kfu option 1 - bootmode normal or manually (see above)
when it says <waiting for device> power off the kf by holding the pwr button for ~20sec till it turns off - pwr on again - the command should be resumed and finished - another pwr off/on should bring you back
install fff & twrp:
refer to this post http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
if you can't get rid of the windows drivers:
http://forum.xda-developers.com/showthread.php?t=1430038

Thanks so much I was having this same problem and have been bashing my head against the wall all day. This kind of thing is a little above my paygrade but I'm learning quickly!

[Q] bricked kf fire(not noobish)

alright fellas, I had cm7 and twrp installed..everything was just DANDY and then i followed these steps to upgrade to miui ics build:
"...Step 3: Once transfer is complete, shut down your Kindle Fire.
Step 4: Boot into a custom recovery. ClockworkMod Recovery and TWRP are popular choices and you can choose to install whichever you like.
Step 5: Take a NANDROID backup. This may come handy later on if you have problems with MIUI and wish to revert back to current setup.
Step 6: Do a complete wipe & factory reset from the custom recovery.
Warning: This will delete all your personal data.
Step 7: Flash the ROM you transferred to your Kindle in Step 1. In CWM, you can do this from install zip from sdcard > choose zip from sdcard > [.zip file from Step 1]
Step 8: Wipe both cache and Dalvik cache.
Step 9: Reboot!"
after that Im stuck at the recovery yellow triangle, so i installed the kindle driver thats out there(shows up as android adb device after install) and now after driver install i boot the kf, it recognizes device, then disappears, then shows up, then is gone again. I cant push anything to the KF if it doesnt show up...i cant even quickly push something to it while its in device manager. Suggestions?

You need to use kfu to change boot mode to normal boot.
Or issue the following adb commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk

ammubarak said:
You need to use kfu to change boot mode to normal boot.
Or issue the following adb commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
i'm able to issue the command, reboot the fire and both commands work. However im still stuck at the yellow triangle
i'm able to issue the commands and it reboots. However im right back to recovery triangle

i'm able to issue the commands and it reboots. However im right back to recovery triangle

this worked
"- open a (elevated) command prompt and cd to c:\kfu\tools - leave it open all the time
- issue "fastboot -i 0x1949 oem idme bootmode 4002"
- it says <waiting for device>
- power off the kf by holding pwr ~20sec and power on again
- the kf is in fastboot now
- install twrp -> "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img"
- tap reboot on the kf screen
- update fff -> "fastboot -i 0x1949 flash bootloader u-boot.bin"
- reboot -> "fastboot reboot"
- restore to factory partitioning -> "fastboot oem format"
- boot to twrp -> "fastboot -i 0x1949 oem idme bootmode 5001"
- reboot -> "fastboot reboot"
- now the kf boots to twrp and adb commands are available
- test with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
- now you can download and copy your new rom to sdcard (ie prerooted stock)
- mount sdcard -> "mount /sdcard"
- exit adb shell -> "exit"
- tap install in twrp and install the new rom
- ignore errors about volume "misc" - the kf don't have a volume "misc"
- on the screen where you return after installation tap clear dalvik/cache
- set boot mode to normal -> "adb shell idme bootmode 4000"
- reboot -> "adb reboot""

http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4