Develop Bugs

[BOOT] FIREFIREFIRE 1.3 - Replacement bootloader w/ recovery selection

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIREFIREFIRE​
FIREFIREFIRE is a replacement bootloader originally created by pokey9000 for the Kindle Fire. While the stock bootloader simply boots into the system, FIREFIREFIRE provides an option to boot into recovery and also enables fastboot for a short period of time. Everyone from developers to users of alternative ROMs will certainly benefit from having FIREFIREFIRE on their device.
FEATURES
Recovery Selection - As the Kindle Fire boots up, the power button LED will change from bright green to a dim green. Once it changes to a dim green, press the power button again and release (repeat a few times to be sure). The LED will then change to an orange color indicating recovery selection and boot into recovery.
Enable Fastboot - As described above, when the power button LED changes to a dim green, the Kindle Fire will enter fastboot mode for approximately 4-5 seconds. During this time, fastboot commands can be issued and the device will remain in fastboot until it is rebooted.
Write Partition Tables - During fastboot, issuing a 'fastboot oem format' command will overwrite the existing partition table with the stock table values.
HOW TO INSTALL
From stock bootloader fastboot
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
From FIREFIREFIRE fastboot
Code:
fastboot flash bootloader u-boot.bin
From gscript - Details in the gscript thread
For a step-by-step guide on how to update FIREFIREFIRE from a previous version using fastboot, see this post by smirkis
RELEASE NOTES
1.3 - MD5: 928ae401d91963e1cb8f4dae6ca9519b
March 11, 2012
Replaced the original FIREFIREFIRE boot logo with a "kindle fire android" logo
Shortened the fastboot delay from ~10 seconds to ~5 seconds
0.9 - 1.2
Original FIREFIREFIRE thread
ADDITIONAL NOTES
I originally just wanted to rebuild the FIREFIREFIRE bootloader to bake in a custom boot logo for my own use. That opened the door enough for me to become interested in making some minor improvements in how it handles recovery selection. When I contacted pokey9000, he encouraged me to work on it and gave me enough confidence to begin studying the code. Although I couldn't begin to estimate a timeframe, I hope to continue working on it and build in some enhancements that would be worthy of eventually calling it version 2.0.
The bootloader is possibly the most underappreciated piece of software on the Kindle Fire. It's not overreaching to say that everything else is built on top of this foundation. Without the work of pokey9000, the XDA Kindle Fire community would not have gotten the other great developments as quickly as it did. When the next great device comes along, we will certainly need the work of talented people like pokey9000 again. If you enjoy using your Kindle Fire as an Android tablet, please consider making a donation to pokey9000.
A special thanks to smirkis for having the guts to be the first in line to flash my build on his device.

props to this gentleman for expanding on pokey9ks work, I love the logo and shortened delay. I love being a test dummy, thanks for the opportunity
ill update my gscript method when I get home!
Sent from my HTC Glacier using xda premium

Very nice; I like the logo and it works exactly as it should (guess this means I can stop trying to understand the uboot source myself for the time being lol)

Is this flashable in TWRP?

AustinFire said:
Is this flashable in TWRP?
Click to expand...
Click to collapse
As noted in this thread, fastboot flash shall be used.
Sent from my Amazon Kindle Fire using Tapatalk

I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
You may use KF utility to boot into fastboot, then use fastboot flash mentioned in the header of this thread, then reboot to normal using KF.
Sent from my Amazon Kindle Fire using Tapatalk

ch0mch0m said:
I installed 1.0 using KF utility. Is there a quick way to update it or do I have to go through KFU again?
Click to expand...
Click to collapse
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I saved this from somewhere on XDA, not sure who or what thread:
Code:
Howto flash by hand
1 Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. "adb shell idme bootmode 4002"
2 flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
2b at <waiting for device> press power 30 seconds to power down, then power up
3 disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
4 reboot: "fastboot -i 0x1949 reboot"

it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related

kinfauns said:
Using fastboot is the quickest, most painless way to do it. If you have KFU, then you already have fastboot in the tools directory. I strongly urge anyone playing around with ROMs to learn how to use fastboot. It's an essential tool/skill that will get you out of trouble should something go wrong with your device. Maybe another member has a fastboot tutorial available and can provide a link.
Click to expand...
Click to collapse
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.

Pkt_Lnt said:
I saved this from somewhere on XDA, not sure who or what thread:
Click to expand...
Click to collapse
b63 said:
it's not realy a tutorial but it should clear things up regarding the bootmodes and how drivers and commands are related
Click to expand...
Click to collapse
Thanks for those crib sheets. I was hoping there was something out there that starts off answering the question, "What is fastboot?" and working up from there. While KFU and other press-this-button utilities do a good job of getting the beginner started, it's like teaching someone how to run without walking first. Then when the user gets into a bind because something went wrong, they have no idea what to do next. The General section seems to be filled with these kinds of problems. A while back, I started writing a general knowledge, FAQ style post, but it seemed too rudimentary once I got into it. When I glance at the General section from time to time, I have second thoughts about having shelved it. Maybe I'll dust it off again.

twa_priv said:
I just did install FFF 1.3 using KFU.
Used KFU to set bootmode to fastboot (Bootmode menu -> Fastboot).
However, windows (Windows 7 x64 EE) then complained about the driver and fastboot (and adb) didn't recognize my KF and I was stuck in fastboot mode.
I needed to uninstall the driver, reboot windows, reconnect the KF in order to get windows to reinstall the Android ADB Interface driver.
Then all was fine. Used KFU's fastboot to flash FFF 1.3 and set the boot mode back to normal.
Click to expand...
Click to collapse
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.

kinfauns said:
Well, not to pick at semantics, but I think you used the tools from the KFU distribution and not necessarily KFU's menu interface. Regardless, it sounded like the original poster of the question didn't even want to bother with KFU, so actually typing some commands isn't going to be much of an option either.
Click to expand...
Click to collapse
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.

twa_priv said:
No, I used the KFU batch file to change the boot mode. But I wasn't saying this is an issue with KFU, it's much rather an issue with freaking windows.
Click to expand...
Click to collapse
I understood the part about you using KFU to change the bootmode and the part about you reinstalling drivers. My comment wasn't about either of those things. My point was that there's not a way to reinstall a new FFF from within the KFU menus. You used KFU to change bootmodes, quit out of KFU, then used the fastboot executable to do the actual installation... just as my installation instructions described. Although the fastboot executable is packaged in the tools directory of KFU, it is entirely separate from it. My intent was to clarify this point so that some other reader of this thread in the future doesn't get confused and say, "But he said I could use KFU to install it!"

I just used cmd and fastboot from the adb-sdk (winXP) to install this. Very nice! Great work.

Pkt_Lnt said:
I just used cmd and adb (winXP) to install this. Very nice! Great work.
Click to expand...
Click to collapse
Thanks for the feedback, I'm glad you like it. Did you use dd to write directly to the bootloader partition?
Edit: Nevermind, I see that you changed your post to say fastboot.

if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
first, connect your device to your computer and make sure USB is not mounted
make sure you already downloaded the new fff1.3 and copy it to your sdk folder where fastboot is located
open a cmd prompt if you on windows and cd to the sdk directory where fastboot is located, for me i typed
cd c:/sdk_tools
than go ahead and pre-initiate the fastboot command to install the new fff1.3
fastboot flash bootloader u-boot.bin
you should see a message saying, <waiting for devices>, now go ahead and reboot your kindle.
at startup fastboot is automatically detected and your cmd prompt should say something like
c:\SDK_tools>fastboot flash bootloader kinfauns_u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)... OKAY [ 0.057s]
writing 'bootloader'... OKAY [ 0.188s]
finished. total time: 0.246s
at this point, its still in fastboot. so issue
fastboot reboot
and u should see something like this
c:\SDK_tools>fastboot reboot
rebooting...
finished. total time: 0.002s
no need to change bootmodes, no need to use KFU, nothin.
if your pc has driver issues, avoid fastboot entirely and use my gscript method posted in the OP

smirkis said:
if you already have fff1.0, fff1.1, or fff1.2, all you need to do to install this:
Click to expand...
Click to collapse
Thanks to smirkis for the mini-guide on how to update FFF from a previous version. I've edited the OP to point to his post so others can find it easily.

That is good. Just for info, I used the commands in my post 9 above (note the "take out "-i 0x1949" if FFF is already installed" in step 2) and it works fine.
I used that to install FFF 1.0 and update 1.1, 1.2, and now 1.3 clean and quick.
The really short version is saved now for the next version.

Kindle Fire. Device Manager Sees but Kindle Fire Utility Doesn't

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!

[Q] Kindle Fire stuck on TWRP screen (recovery mode)

Hi everyone,
I'm an Italian new user here on the XDA Developers Forum (so.. please forgive my English ) and I'm here to get help for my new Kindle Fire.
I've received it some days ago and i try to root it to install the Android Market (KF is not yet distribute here in Italy).
I followed some guide founded on italian forums, but now i'm stucked on the TWRP screen (on the KF, in recovery mode).
Some data about my situation
- PC OS: Windows XP Home SP2
- KF firmware: 6.3
- ADB installed
- files fbmode, TWRP 2.0, su, Superuser downloaded and placed in ADB cartel
This is what I've done:
After launching
fastboot -i 0×1949 boot twrp-blaze-2.0.0RC0.img
my KF is blocked on the yellow triangle screen (the one with the "Press power button for recovery" voice)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I run the Kindle Fire Utility - select Bootmode Menu - 3.Recovery
KF reboot a pair of times, with the tipical sound of a device reconnecting to the PC; finally I have the TWRP screen on the KF, with the buttons Install-Backup-Restore-Wipe-Mount-Settings-Advanced-Reboot
Running DOS command, I find my KF in recovery mode
In Windows Device Manager I find just the voice "Android Phone - Android Composite ADB Device" (sorry for the Italian printscreen)
..while I find the voice "Amazon Kindle USB Device" under "Hard Drive"
If i check Control Panel - Hardware Installation (sorry.. I don't know the translation for this word.. could be Hardware Setting or Facility), the device is correctly installed
In Kindle Fire Utility, if I make a different selection on the Bootmode Menu:
1.Normal - Kf reboot a pair of times, then returns on the TWRP screen (Boot Status 0x5003)
2.Fastboot - nothing seems to run
So, I run Kindle Unbrick UtilityV1.1:
Recovery Loop - Kindle unbrick in progress <wainting for device>
..after a few seconds OKAY, Congratulations, your Kindle should be unbricked ...and doesn't proceed.
Stuck at logo - Kindle unbrick in progress <idme> write 4000 to offset 0x1000. Congratulations, your Kindle should be unbricked
..Kf reboot a pair of times, then returns on the TWRP screen
Framework-Res - a pair of DOS command lines, then Kf reboot a pair of times, then returns on the TWRP screen
Modded/system/app - as Framework-Res
Other - Kf reboot a pair of times, then returns on the Yellow Triangle screen
..so, here I am, blocked rooting the KF and without any ideas about how to proceed.
At the moment.. I've got a beautiful expensive mirror, and not a Kindle
I hope someone could help me.. if someone understand my awful English :laugh:

Your FFF and TWRP are outdated. Get the latest TWRP from here: http://teamw.in/project/twrp2/79
And the latest FFF from here: http://forum.xda-developers.com/showthread.php?t=1632375
You're most likely stuck in fastboot mode. You can verify this by seeing if "fastboot getvar product" or "fastboot devices" output anything.
Either way, you don't need to worry about getting out of fastboot mode if you update the bootloader and the recovery; the updates fix the bug related to bootmode changes.

Dasanko said:
Your FFF and TWRP are outdated. Get the latest TWRP from here: http://teamw.in/project/twrp2/79
And the latest FFF from here: http://forum.xda-developers.com/showthread.php?t=1632375
You're most likely stuck in fastboot mode. You can verify this by seeing if "fastboot getvar product" or "fastboot devices" output anything.
Either way, you don't need to worry about getting out of fastboot mode if you update the bootloader and the recovery; the updates fix the bug related to bootmode changes.
Click to expand...
Click to collapse
Thank you in advance for your answer.
I'm goint to download the latest FFF and TWRP as soon as I come back home in the afternoon.
To update them.. How can I do? I download the latest, I cancel the older under the ADB cartel, I put the latest under the ADB cartel and the I re-launch the installing commands by the DOS prompt?
When you say "You can verify this by seeing if "fastboot getvar product" or "fastboot devices" output anything" do you mean to run that commands by the DOS prompt?

You can run those commands from a command line prompt started at KFU/tools
To update FFF, just install its zip from TWRP.
To update TWRP, as you're stuck on fastboot now, type "fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img"

To other people that are going to be asking questions.
See how detailed this question was? This is the kind of stuff people should be asking instead of "oh noes, my kindle is not rooting please help!" It makes it a whole lot easier to help you. *end rant*

Dasanko said:
You can run those commands from a command line prompt started at KFU/tools
Click to expand...
Click to collapse
Done: both the command output anything.
Dasanko said:
To update FFF, just install its zip from TWRP.
To update TWRP, as you're stuck on fastboot now, type "fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img"
Click to expand...
Click to collapse
I try to update at first TWRP.
I download the openrecovery-twrp-blaze-2.1.1.img, put it under the ADB cartel (C:\Programs\Android\android-sdk\platform-tools) and launch (by DOS) the command fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img but it keep looking for the device (the device situation is the same of my last post):
About upgradind FFF:
you tell me to install it from TWRP. On the TWRP screen on the KF I have the Install Button.. but how can I put the new FFF ont the KF root?
Is this the correct procedure?
Sorry for my many questions.. but I'm still stuck in this situation.
I also accept temporary solution to return to the normal situation (KF working, without rooting it), just to use it during my holidays.
Help :fingers-crossed:

To move FFF 1.4a's install zip into the SD card:
Get in TWRP and connect the KF to the computer, if ADB is working properly, run:
adb shell mount sdcard
adb push fff.zip /sdcard/
adb shell umount sdcard
The first command may return an error if it's already mounted, ignore it if that's the case. Then you can just press install, it'll be at the root of the SD card.
About updating FFF: your fastboot drivers may not be installed. You can get the KF stuck in fastboot mode, so Windows will have enough time to detect the device and let you install the drivers, by typing the following from ADB (get in TWRP first):
adb shell idme bootmode 4002
Once your fastboot drivers are sorted, "fastboot devices" or "fastboot getvar product" will return results.
At that point, issue:
fastboot flash recovery twrp.img
(replace twrp with your file's name) to update TWRP, then set the bootmode back to normal with:
fastboot oem idme bootmode 4000
As a side note, TWRP 2.2 is out. You may want to flash that instead of 2.1.1

Back from holidays.. back at work on my KF :fingers-crossed:
I upgrade TWRP at v2.2.0, using Kindle Fire Utility.
Always using Kindle Fire Utility I install the latest version of FireFireFire:
Everything seems ok: with the DOS command adb devices I finally see the KF as "device" (an not as "recovery")
and in Windows Device Manager I find "Android Phone - Android Composite ADB Device" and "Amazon Kindle USB Device" under "Hard Drive"
Completed this operation, I'm stucked at KF logo.
So, I launch Kindle Fire Utility: I choose "Install Permanent Root with Superuser". Something goes ok, somethings goes wrong.
I waited for 30 minutes.. nothing happened.
But the KF passed form the KF logo to the TWRP screen and the command adb devices reported me the passage from device to recovery
..I'm going to burn the KF...
[UPDATE]
Before burning the KF.. I re-launch Kindle Fire Utility - Install Latest FireFireFire.
We are back at KF logo and adb devices - device
I launch Kindle Fire Unbrick v1.1 - Stuck at Logo function
The KF remains stucked at logo and adb devices - still device
I re-launch Kindle Fire Utility - "Install Permanent Root with Superuser". Same situation (no more KF logo but TWRP screen):
I also tried this solution Stuck at KF Logo but it's still stucked at KF logo.
I must say: I ran the "install_driver.bat" but it doesn't worked
I modified the code LANGUAGE in dpinst.xml (0x0409 - italian)

You have FFF1.4 installed, so use it the way it was intended.
http://forum.xda-developers.com/showthread.php?t=1632375
It would also help to read this:
http://forum.xda-developers.com/showpost.php?p=23747567

soupmagnet said:
You have FFF1.4 installed, so use it the way it was intended.
http://forum.xda-developers.com/showthread.php?t=1632375
It would also help to read this:
http://forum.xda-developers.com/showpost.php?p=23747567
Click to expand...
Click to collapse
Thank you Soupmagnet; I downloaded the Bootloader FFF 1.4A;
now i must learn how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file" cause I'm such a noob in this matters.
I hope the link to the guide you posted will help me

When you boot up, if you see a blue Kindle Fire logo, it's already installed. Otherwise, put it on your sdcard via adb or the mount function in twrp, then select install, find and select it in the menu and flash.

soupmagnet said:
When you boot up, if you see a blue Kindle Fire logo, it's already installed. Otherwise, put it on your sdcard via adb or the mount function in twrp, then select install, find and select it in the menu and flash.
Click to expand...
Click to collapse
When I boot up I see a blue KF logo, then it's stucked on the yellow KF logo.
Installing a custom ROM
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!

Emmegei said:
When I boot up I see a blue KF logo, then it's stucked on the yellow KF logo.
Installing a custom ROM
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!
Click to expand...
Click to collapse
The first boot logo is the bootloader (FFF1.4). The second one is the boot animation of the stock Kindle Fire software (which is having conflicts). You need to transfer a ROM to your device, factory reset (wipe) and wipe system. Then flash the ROM as with FFF before. Afterwards it wouldn't hurt to wipe cache and dalvik.

soupmagnet said:
The first boot logo is the bootloader (FFF1.4). The second one is the boot animation of the stock Kindle Fire software (which is having conflicts). You need to transfer a ROM to your device, factory reset (wipe) and wipe system. Then flash the ROM as with FFF before. Afterwards it wouldn't hurt to wipe cache and dalvik.
Click to expand...
Click to collapse
Done.
I transfered the ROM with adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
On TWRP, "Wipe -> Factory Reset"
On TWRP, "Install" -> fff-u-boot_v1.4a.zip + "Swipe to Confirm Flash"
On TWRP, "Reboot -> System".. system stands for 30 minutes trying to rebooting; I manually launch the reboot from adb reboot
KF reboots in recovery mode, with the TWRP screen on.
On TWRP, "Wipe -> Cache + Dalvik"
Is this the correct situation?

You don't wipe anything before installing FFF. It is only necessary to wipe those partitions when you are installing a different ROM. If you try to reboot into the system at this point, nothing will happen because you wiped those partitions. Flash a ROM to fix it.

I'm so lost
I'm so lost about what I need to do to get my kindle working again. I guess I'm stuck in a boot loop. With the kindle plugged into the computer it shows up in the device manager as "Android phone -> Android ADB interface (right?). It first got stuck like this a while back and I could boot into TWRP. I tried to flash an update ROM but couldn't find it with the navigation interface. But a couple of days ago I was poking around trying to get it back and using Kindle Fire Utility I was able to install (it went through the KFU download first) Clockwork Recovery Mod. Using CRM, if I try to apply \sdcard\update.zip it says "no such file or directory" and installation aborted. Can someone point me in the right direction? I hope this is enough info but like I said I am SO confused about what to do next.

more info like maybe start your own thread saying you think your in a boot loop means nothing to me cwmr is not industry standard doubt it ever will be... you have fff.. in a bootloop what does it look like? there are about a hundred ways to incorrectly flash update.zip and only 1 way to do it correctly... I dont recommend this for you because of you level of experience which sounds to be nill to none...android adb interface is the incorrect driver or its an indication of being in fastboot... if your in recovery and plug it in it should read android composite adb interface...at this point I suggest you fix your drivers and do nothing with your kindle till that is sorted and we have more info to digest in order to direct you in the proper fashion with out so much guessing so start a thread provide more detail...
http://forum.xda-developers.com/showthread.php?t=1638452
http://forum.xda-developers.com/showthread.php?t=1644970
http://forum.xda-developers.com/showthread.php?t=1552547

Thank you for your help. I will start a new thread and will try to give as much info as I can. In the meantime Device Manager now says "Android Phone -> Android Composite ADB Interface" Is that a step in the right direction?

Solved?
digz6666 said:
I end up in TWRP mode, cannot do anything, tried rebooting into recovery or bootloader.
It says some errors while moving root_check or something.
mv /system/bin/check_rooted failed
Click to expand...
Click to collapse
Hi there!
I was having the exact same problem and I guess I kinda solved it on my own.
I researched a little bit and found the following post regarding the rename-error:
can be ignored because it's allready renamed ...
Click to expand...
Click to collapse
I thought "Well, nice! But that doesn't solve the problem that I'm stuck at TWRP..."
Then I found a completed log file of the KFU root process which ended with...
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
Click to expand...
Click to collapse
I noticed that there was only one little step between the rename-error and the above final message:
Installing Superuser.apk
Click to expand...
Click to collapse
I found the superuser.apk file in the files folder of KFU, put it on my Kindle Fire, switched to fastboot mode (wasn't sure if I need it) and... installed it! Manually! (via ES File Explorer)
Then I installed the Google Apps and locked the wallpaper via KFU - it worked! I tested the Google Play store - and it worked too!
Do I get it right that everything is fine now? Or is it possible that I'm still missing anything? If the latter is the case I'm not noticing it...
EDIT: Oh, and one more question. I thought that the FireFireFire bootloader would replace the old bootloader. But after the FireFireFire bootloader is finished the stock bootloader starts. Is that right?

bjaxx87 said:
EDIT: Oh, and one more question. I thought that the FireFireFire bootloader would replace the old bootloader. But after the FireFireFire bootloader is finished the stock bootloader starts. Is that right?
Click to expand...
Click to collapse
No. What you're seeing is the stock Kindle Fire animation. There isn't enough room in the boot partition for two bootloaders.

[Q] Newbie trying to make sense of my 1st gen kindle stuck in bootloop?

I read the guide and have been browsing the forums for similar situations.
First of all, many months ago I tried to root my KF with something named "doomlord"? I basically googled how to root, picked one, went at it. It ran fine, though I don't recall trying to do anything with the root. Most recently every time I powered it on, I was in the CWMR menu. I tried to install the latest kindle update from amazon (changed it to .zip, placed it in the folder, tried to install from cwmr menu), to get it back to stock. Didn't work, and the only way I was able to use my kindle was wiping everything and rebooting. I became frustrated and started to try anything I hadn't, I clicked fastboot mode. Now it's been stuck at the yellow triangle, does nothing when power is pressed, isn't recognized by my mac.
Many users had my similar situation but I truly am a newbie and went at this with no knowledge, though I do know some terms through the guide. It seems I'm stuck in a bootloop, and my kindle isn't truly broken for good.
What I want to know, in basic terms:
What do I need to download?
To send commands.. do I use terminal? Seems like I need to get 'fastboot' and 'adb'
I've also seen references to getting kindle fire utility- can I use this even though I used some random doomlord program and it's using CWMR?
How to 'flash' something?
Simple, step by step instructions would be SO APPRECIATED! I apologize for having a question everyone else has asked, but I feel so frustrated at this point.

Anybody?
So far, I have downloaded KFU, adb, fastboot, and FFF 1.2.
I've tried many commands to see if my kindle is in fastboot, it does not seem to be. All commands come back with "-bash: fastboot: command not found". I also am going into the directory of "android" where I put adb and fastboot. I think that is correct.
Not sure what to do with KFU, or FFF that I've downloaded.
Should I wait for the battery to drain? Though I don't think that will fix the problem at all.
Kindle still not being recognized by my mac.
At this point I will just pay somebody to help me successfully fix this or send it out. But if it's as easy as the solutions make it seem, I'd love to just do it myself. I think I'm just confused about what exact steps I need to make, whether that is flashing FFF or TWRP?

Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).

soupmagnet said:
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
Click to expand...
Click to collapse
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you

2hellwu said:
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
Click to expand...
Click to collapse
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.

soupmagnet said:
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
Click to expand...
Click to collapse
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".

2hellwu said:
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
Click to expand...
Click to collapse
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.

soupmagnet said:
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
Click to expand...
Click to collapse
Again, command not found. Does the first step indicate that my fastboot is indeed functional?

2hellwu said:
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
Click to expand...
Click to collapse
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?

soupmagnet said:
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
Click to expand...
Click to collapse
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.

2hellwu said:
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
Click to expand...
Click to collapse
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product

soupmagnet said:
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
Click to expand...
Click to collapse
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"

2hellwu said:
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
Click to expand...
Click to collapse
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?

soupmagnet said:
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
Click to expand...
Click to collapse
ah yes. so, that worked. now at:
Code:
< waiting for device >
~/Desktop/fastboot reboot
at this point KF is still off. power on or no?

Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc

2hellwu said:
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
Click to expand...
Click to collapse
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.

soupmagnet said:
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
Click to expand...
Click to collapse
Before I start this- I should have clarified my main goal is to get my kindle back to stock. I don't have a need for anything extra, I really just use it to read books. From other guides, maybe it seems that my next steps should be to download the kindle update from amazon, and flash that?

In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder

2hellwu said:
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
Click to expand...
Click to collapse
Yes, the mounted volume "Kindle" is your sdcard. Just drag and drop everything into that folder. Be sure to eject the volume from your computer (right-click on it and select eject) before you unmount it in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."

[Q] stuck at "teamwin" logo - twrp does not start - HELP!

hi
first of all iam from germany so my english is not that good.
i got a kindle fire a week ago from a friend. it was not rooted but in a bootloop.
somehow i managed to install twrp via the kf utility. unfortunally it was version 2.1.1.1 so i was not able to install a other rom via sideload.
i also tried the soupkit.
the last idea was that i just copy the zip file onto the device. it stuck in the middle an after 20 minutes i decided to abort.
now the kf just stuck at the "teamwin" logo right before entering the twrp interface.
i tried to reinstall twrp but that didnt worked. i also tired the unbrick tool with no result.
i have a factory cable too.
if you guys have any ideas please let me know!
thanks

nobody really...?

Just speculation. If this had the kindle software on it, then my guess is it tried to update to the 6.3.3 version, which is currently a real problem. Go to this thread and follow the instructions:
http://forum.xda-developers.com/showthread.php?t=2790183
Once you are rooted, please install a different wonderful rom, like kitkat, so that Amazon does not dump on you again!

redassmonkey said:
hi
first of all iam from germany so my english is not that good.
i got a kindle fire a week ago from a friend. it was not rooted but in a bootloop.
somehow i managed to install twrp via the kf utility. unfortunally it was version 2.1.1.1 so i was not able to install a other rom via sideload.
i also tried the soupkit.
the last idea was that i just copy the zip file onto the device. it stuck in the middle an after 20 minutes i decided to abort.
now the kf just stuck at the "teamwin" logo right before entering the twrp interface.
i tried to reinstall twrp but that didnt worked. i also tired the unbrick tool with no result.
i have a factory cable too.
if you guys have any ideas please let me know!
thanks
Click to expand...
Click to collapse
what bootloader is installed, do you see a press power for bootmenu?
likely need adb/fastboot.exe files from KFU, download a twrp.img from http://techerrata.com/browse/twrp2/blaze,
latest is openrecovery-twrp-2.7.1.0-otter.img
verify md5 check sum
move adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe)
and twrp.img to same folder like c:adb
connect fastboot cable to kindle powered off, connect to pc, power on kindle
if you have non stock bootloader use
open command prompt
cd\adb
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot reboot
if you have stock bootloader you also need FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
---------- Post added at 11:39 AM ---------- Previous post was at 10:51 AM ----------
sorry wrong twrp file use openrecovery-twrp-2.7.1.0-otter.img

Ixthusdan said:
Just speculation. If this had the kindle software on it, then my guess is it tried to update to the 6.3.3 version, which is currently a real problem. Go to this thread and follow the instructions:
http://forum.xda-developers.com/showthread.php?t=2790183
Once you are rooted, please install a different wonderful rom, like kitkat, so that Amazon does not dump on you again!
Click to expand...
Click to collapse
step 2 says - "Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)"
i cant put anything on my storage because twrp is not starting. because of that i cant use my storage. (no rom installed...)

redassmonkey said:
step 2 says - "Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)"
i cant put anything on my storage because twrp is not starting. because of that i cant use my storage. (no rom installed...)
Click to expand...
Click to collapse
correct use my instructions to reflash twrp

sd_shadow said:
correct use my instructions to reflash twrp
Click to expand...
Click to collapse
i did. at first everything looks good.
after rebooting the screen stayed black (green power light was on) and windwos played the "connected - disconnected" sounds for a while.
when i tryed to reset the kf (20sec power button) and turned it back on the problem was the same... is there any way to completley erase the kf without twrp? and if yes can i use ur methode to install twrp and flash a rom?

redassmonkey said:
i did. at first everything looks good.
after rebooting the screen stayed black (green power light was on) and windwos played the "connected - disconnected" sounds for a while.
when i tryed to reset the kf (20sec power button) and turned it back on the problem was the same... is there any way to completley erase the kf without twrp? and if yes can i use ur methode to install twrp and flash a rom?
Click to expand...
Click to collapse
did command promt show sending and writing details?
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
should have looked like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
redassmonkey said:
is there any way to completley erase the kf without twrp?
Click to expand...
Click to collapse
no, you need twrp

Yes it looked exactly like this...

could be bootloader is partially toast
try reflashing it like you did twrp
download FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot

sd_shadow said:
could be bootloader is partially toast
try reflashing it like you did twrp
download FFF bootloader.bin
verify md5 check sum
open command prompt
cd\adb
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot
Click to expand...
Click to collapse
same... how ****ed am i...?

redassmonkey said:
same... how ****ed am i...?
Click to expand...
Click to collapse
you are pressing power to open bootmenu, selecting , recovery and releasing power button? does it say v1.5? did it before?

sd_shadow said:
you are pressing power to open bootmenu, selecting , recovery and releasing power button? does it say v1.5? did it before?
Click to expand...
Click to collapse
yes and yes.....

redassmonkey said:
yes and yes.....
Click to expand...
Click to collapse
try booting to fastboot mode with
.
fastboot reboot-bootloader
.
if that works
.
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot

sd_shadow said:
try booting to fastboot mode with
.
fastboot reboot-bootloader
.
if that works
.
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot flash bootloader fff-u-boot_v1.5.bin
fastboot reboot
Click to expand...
Click to collapse
"fastboot reboot-bootloader" worked but after that the fk tryed to boot in recovery again and it stocked at the "teamwin" logo... problem is that at this point no comunication between pc and kf is impossible... adb just says "waiting for device"..
i double checked my version of twrp... it says now V1.4a
i have to go now but i will check your answer tomorrow...
thanks for your help so far! :good:

Don't know could be hardware failure.
Could try Cannibal Open Touch v2.1 recovery (COTR)
cotr.img
fastboot flash recovery cotr.img

sd_shadow said:
Don't know could be hardware failure.
Could try Cannibal Open Touch v2.1 recovery (COTR)
cotr.img
fastboot flash recovery cotr.img
Click to expand...
Click to collapse
that does not work either...
i told you that abter typing "fastboot reboot" the kf screen stayed black and connected - disconnected the whole time. its the same issue like in thuis thread : http://forum.xda-developers.com/showthread.php?t=1413358
the only diffrence is that my kf loads the bootloader again after reseting it. does that help?

kindle is showing as Omap4430 usb device ?

sd_shadow said:
kindle is showing as Omap4430 usb device ?
Click to expand...
Click to collapse
after rebooting yes.

nobody any ideas? iam kind of depressed...