Develop Bugs

[FIX] Regarding TWRP 2.0 for Kindle Fire

Hello, I'm Pyrostic and I alpha tested the Kindle Fire build of TWRP 2.0.
The build that was posted last night was that of an older version. The build has since been fixed and re-uploaded at: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
See @agrabren on twitter for the latest details on TWRP 2.0
For Kindle Fire TWRP 2.0 support please see the Kindle Fire RootzWiki forum. Team Win will not be providing support here.
During install when your device gets to the "Reboot" screen run
Code:
adb shell
idme bootmode 4000
If you did flash the old version and you find yourself stuck at the Kindle Fire screen you simply need to replace your twrp-blaze-2.0.0RC0.img and run the following snippet of code.
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if you haven't flashed yet. Please DO NOT FORCE install this new image using a dd command such as this:
Code:
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Simply follow the following instructions after downloading the image at http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img in an ADB prompt:
Code:
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
This will install both the FIREFIREFIRE U-boot and TWRP 2.0 .
FURTHERMORE if you did use the DD commands stated above you may not be able to get into ADB, and I hope fastboot still works for you. If it does, try :
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
If you are having problems please try the following. It has been reported that it is helpful to others.
If you LOVE TWRP 2.0 on your Kindle Fire. I suggest donating to @agrabren (<--- donation link) for his hard work and thanking me here for my testing .
I will not be replying to this thread. If you have issues please join us on RootzWiki for follow up support. I merely posted this here because I do care for my community in general.

There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.

Is there anything I can do since I used the dd command and am now stuck at the firefirefire screen?
Edit: Tried the "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" and all I got was < waiting for device >
Fix: I followed http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 worked like a charm

i did the dd install... not having any adb issues though. are there any other problems with installing it that way?

I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium

ags29 said:
There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.
Click to expand...
Click to collapse
Yes a couple things, put the twrp-blaze-2.0.0RC0.img file in the folder where you have fastboot installed. and It doesn't sound like you have fastboot on your computer. Please look around.

borborpa said:
I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.

I also use dd method to install FIREFIREFIRE and twrp. After that I lost the ADB connection. Try to issue the comand:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
But it shows < waiting for device >...
My Solution:
Change the VID to 0x18D1 and issue the command:
fastboot -i 0x18D1 boot twrp-blaze-2.0.0RC0.img
The < waiting for device > msg will still be showed. Don't worry. Reboot you KF. During the reboot period, the twrp-blaze-2.0.0RC0.img will flash to your KF. After the twrp installation process is completed, you ADB will BACK~~~

my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!

pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
i downloaded it about 2 hours ago (dunno what 9:30 am is for you.. its 8:51 for me right now so... yea) and it didn't cause any problems that I can notice. if I did flash the newer version what problems could I expect to see? fastboot works, firefirefire works, and adb works.
if it matters any I'm running CM7 not stock rom. Maybe that's why I haven't been having these issues.

MayfairDROID said:
my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!
Click to expand...
Click to collapse
This post saved my kindle when that happened to me

What's the advantage of using this one over the old one? Old one works fine for me.

Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112.. annnnd it worked (but not before adding the 18D1 line to the .inf file and reinstalling the kindle drivers through Device Manager).

pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
Now I'm totally confused. I dled it after 10. It worked just fine, I rebooted multiple times into it, did a backup and everything. Now I just rebooted, and I'm stuck at the FIREFIREFIRE screen, and can't see the device in adb. Windows won't even recognize the driver.
[FIXED] brian112358's post above fixed the problem.

Thanks..that worked
Now next time i need to get into the TWRP 2.0, I just hit the power button during reboot correct?
Thanks again!
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
ags29 said:
Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O
If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112..
Click to expand...
Click to collapse
Works like a champ...give it a shot

what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install

ckong1 said:
what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install
Click to expand...
Click to collapse
My fix unfortunately doesn't fix everything! There may some extra steps depending on what state you are in and how you got there. Did the device driver install, and can you see it listed in Device Manager as "Android Phone" > "Android Composite ADB Interface"? That is the most important step for this to work for you.
If you can see that try just doing the following:
Code:
fastboot oem idme bootmode 4000
fastboot reboot

i can't seem to get driver to install, kindle comes up as unknown device

ckong1 said:
i can't seem to get driver to install, kindle comes up as unknown device
Click to expand...
Click to collapse
So what happens if you follow the same instructions. I just updated my OP to include it saying either kindle or unknown, as it could work in either state (as posted by other people)
"In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
Click to expand...
Click to collapse

when i select "Let me pick from a list..." "Android Phone" is not an option, only "Unknown Devices" is shown. I try clicking that and i get:
windows has stopped this devices because it has reported problems. (Code 43)
Tried updating vendor list and adding 18d1 to winusb, still cannot install driver
Update:
After restarting the kindle and connecting it, it comes up as "kindle" in devices manager. driver will install but it still is not recognized by adb...

[Q] Kindle Fire Bricked: exec "system/bin/sh": No such file or directory

I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory

i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7

b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.

adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot

b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.

your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times

b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.

Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery

qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery

osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery

qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >

just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img

b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >

the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works

b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.

would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry

I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.

You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.

@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm

When it says waiting for device, what happens when you unplug and plug in the device?

[Q] KF Stuck on FireFireFire 1.3 - Not Recognized by ADB

Edited OP to be shorter to the point:
I am stuck in fastboot but can not establish an adb connection to set the boot mode back to 4000.

Xplorer4x4 said:
I was tired and trying to update my KF to FFF1.3 and TWRP 2.1.0. I am now stuck at the new FFF boot logo(green android guy with KF text under neath). The update to FFF1.3 went smooth. Then I moved on to TWRP. So I tried flashing the img file via terminal emulator rather then using ADB over my computer. So first I set the boot mode to 4002. Success! Then I tried to flash the img file, but was getting errors(I think it was because I forgot to cd in to the downloads folder so Terminal Emulator knew where the file was). Well Due to not being able to flash I had to set up my PC again for the KF to use ADB as I had a system crash since then. So I got hung up with not being bale to use ADB and decided to reboot the KF, thinking it needed a reboot before the PC would recognize it. After rebooting I for stuck on the FFF 1.3 logo. I know ADB is fully functional now(forgot to install an API) but the KF Utility will not recognize the device to be able to reset the boot mode to 4000.
Any suggestions?
Click to expand...
Click to collapse
can't use term to flash like adb, gotta use the dd if= method.
might be I'm fastboot if its stuck at the startup logo.
Sent from my HTC Glacier using xda premium

Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D

DeadChex said:
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
Click to expand...
Click to collapse
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.

Xplorer4x4 said:
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Click to expand...
Click to collapse
opps, I lied... you cant issue idme from fastboot.... nor can you issue fastboot shell...
so, no adb at the very beginning of the KF boot? Does fastboot notice it
Try "Fastboot Reboot" if fast boot works... or 'Fastboot continue"

DeadChex said:
so, no adb at the very beginning of the KF boot?
Click to expand...
Click to collapse
Nope, not at all.
Does fastboot notice it?
Click to expand...
Click to collapse
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?

Xplorer4x4 said:
Nope, not at all.
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Click to expand...
Click to collapse
the boot process goes... Bright LED (first turning on) > Dim LED (Fastboot and Button input) > Bright LED (Normal Boot)
Where is it stuck?
Use "fastboot devices" to see if its listed in the beggining (when bright green)
but, if its going Bright, that means its not trapped in fast boot
(Fastboot is a diffrent program from ADB completly, just throwing that out there, I've attached it if you need it)

Something very enlightening I found somewhere around this great place:
"
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
then you only have to count 1 and 1 together and can master nearly each hanging situation !
"
Edit: You do need the file in the above post when doing this over usb.
Sent from my Amazon Kindle Fire using XDA

freefaling said:
Something very enlightening I found somewhere around this great place:
Click to expand...
Click to collapse
This is great information but totally useless with out a working ADB.
DeadChex said:
(Fastboot is a diffrent program from ADB completly, just throwing that out there)
Click to expand...
Click to collapse
I am aware, but thanks anyways.
fastboot devices does give an out put after the dim. Did not test before the dim.
Good News: I tried the "fastboot -i 0×1949 oem idme bootmode 4000" command again and got an unrecognized vendor ID. So despite following the instructions to modify the 2 .ini files, and accept the install driver warning, and selecting the location for the ini manually as you should, I realized something was wrong with adb. So I used the install driver bat from the KF Utility zip,and got adb working. Issued the 4000 boot command and back in business.
Thanks for all the help guys! I think you guys managed to provide the fastest responses to help I have ever needed, and it is rare I ask for help, so that makes the experience that much better.

[Q] Bricked Kindle. I use fastboot, but always get < waiting for device >

Yesterday, I got the Update 6.3.1 and because I have CMW installed, it blocked the update and I get the yellow triangle. Then I changed the recovery from CMW to TWRP and my kindle update successfully with stock bootloader and recovery back. And I can get in the system.
I want to root it again but on my Mac, I cannot use the KFU, so I use the method here (http://forum.xda-developers.com/showthread.php?p=24129239).
After I issued these commands:
"
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
"
the terminal returns something like "Could not get PIPE properties" and it stucks here. And later, I typed ctrl+c to stop the command and "fastboot oem idme bootmode 5002
fastboot reboot"
Then the screen is black and blank. I do not know what to do. I have tried fastboot but always get "< waiting for device >". Even I hit the power button for 1 minutes, the light is not on and the screen is still black. But it seems that the battery is stll a little bit hot, which may indicate that it is using the battery. What should I do now?

You could just keep holding the power button down for a long time maybe you will get it to boot but otherwise I believe you need a factory cable. http://forum.xda-developers.com/showthread.php?t=1550999

Thanks for your reply!
Thepooch said:
You could just keep holding the power button down for a long time maybe you will get it to boot but otherwise I believe you need a factory cable. http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Thank you so much! I ordered a factory cable and it is on the way. No matter how long I push the power button, nothing happens, no power light, no backlight....When I charge it, the charger get hot, which may indicate it is being charged. Can a factory cable save it? I guess I may flash the wrong bootloader. I should unzip the u-boot-firefirefire-1.2.zip file and then flash it. But I flash it directly without unzipping. Such a silly mistake!

You don't unzip it just flash it in recovery but look at this post too http://forum.xda-developers.com/showthread.php?t=1392693 there is a new bootloader here http://forum.xda-developers.com/showthread.php?t=1632375 follow the instructions you most likely corrupted the bootloader partition flashing a new one will fix that but you need to get to a state where you can until then your in limbo with a draining battery factory cable is maybe your only rescue. I'm not familiar with Mac so I can't really help ya there http://forum.xda-developers.com/showthread.php?t=1430038 good luck

Thepooch said:
You don't unzip it just flash it in recovery but look at this post too http://forum.xda-developers.com/showthread.php?t=1392693 there is a new bootloader here http://forum.xda-developers.com/showthread.php?t=1632375 follow the instructions you most likely corrupted the bootloader partition flashing a new one will fix that but you need to get to a state where you can until then your in limbo with a draining battery factory cable is maybe your only rescue. I'm not familiar with Mac so I can't really help ya there http://forum.xda-developers.com/showthread.php?t=1430038 good luck
Click to expand...
Click to collapse
I use the command "fastboot -i 0x1949 flash bootloader <name of firefirefire image here>". Does the "<name of firefirefire image here>" is like "u-boot-firefirefire-1.2.zip" or "u-boot.bin"? Sorry, but I am quite confused.

g0og1e said:
I use the command "fastboot -i 0x1949 flash bootloader <name of firefirefire image here>". Does the "<name of firefirefire image here>" is like "u-boot-firefirefire-1.2.zip" or "u-boot.bin"? Sorry, but I am quite confused.
Click to expand...
Click to collapse
When flash with fastboot you need to flash the u-boot.bin file
The zip file is for flashing by TWRP
they are used for two different method.

Problem Solved!
Problem solved here and I posted here.

Bricked Kindle Fire HD 7
Hi, so i bricked my kindle fire hd completely. i got a factory cable it it shows as fastboot kindle fire on the screen. But when i run the kfhd recovery tool, and try to restore it, all it says on the command prompt is, waiting for device. Help please!!

hii
wj3pic said:
Hi, so i bricked my kindle fire hd completely. i got a factory cable it it shows as fastboot kindle fire on the screen. But when i run the kfhd recovery tool, and try to restore it, all it says on the command prompt is, waiting for device. Help please!!
Click to expand...
Click to collapse
........
same problem , no solution l feel unlucky...

[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."