yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] namurt:
SOLVED: even though i have my platform-tools directory in my path variable, i still had to open a command prompt from within the directory. silly windows!

i'm having a bit of trouble upgrading to twrp 2.1.1. i am positive i'm in fastboot mode. both "fastboot devices" and "fastboot getvar product" are returning the proper values. my windows drivers are properly loaded as well. the image is within the same directory as the fastboot executable.

and yet for some reason, when i issue:

fastboot flash recovery openrecovery-twrp-blaze-2.1.1.img

or

fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img

i get:

error: cannot load 'openrecovery-twrp-blaze-2.1.1.img'

what gives?
[Kindle Fire Android Development] kinfauns:
The path only affects where Windows will look for executables. You still have to give fastboot the path to the file you want it to flash.
[Kindle Fire Android Development] ma678:
It always returns "Fastboot: not found".

Anything wrong?

I stuck with yellow triangel and never get into twrp.
[Kindle Fire Android Development] freefaling:
Fastboot

Assuming you have windows, open the file explorer to where you have the fastboot file on your computer (Kindle Fire Utility has it in the "tools" sub-folder). Shift + Right-click somewhere inside the explorer window and select "Open command window here". Now you should be able to get rid of that pesky fastboot not found error.

About the issue of getting stuck at the yellow triangle: once you can access fastboot, set your bootmode to normal using "fastboot oem idme bootmode 4000" and then restart by using "fastboot reboot".
[Kindle Fire Android Development] leswgnr:
Tested 2.1.1 - Works!!

Upgraded from 2.0.0 today. Backup and restore work well with backward compatibility with prior 2.0.0 backups restoring correctly. Haven't yet tried the bootmode changes that are new with this version. I have to agree with prior poster about the swipes required now to initiate actions, not a big fan of them either, but they do work. Works fine with installing Hashode's current ics rom and kernel images in addition to google apps.

Thank Teamwin - great job.

---------- Post added at 04:50 AM ---------- Previous post was at 04:34 AM ----------

Thanks kinfauns &SBlood86, appreciate the response. Took a quick look at the link to Pokey's merged code, gave me some idea what's going on. When I get some more time, maybe I'll look at github. Haven't done C since I worked on a enigma decoder for one the problems in Simon Singh's The Code Book. Would be fun again.
[Kindle Fire Android Development] maw230:
Is there anywhere to get this in a flashable .zip?
[Kindle Fire Android Development] harry_fine:
These are the instructions on the TWRP2 site where I got the download.

Is this correct?

I have seen this in this thread:

And can you confirm I can do this right overtop of my CWM recovery?
[Kindle Fire Android Development] smirkis:
yup. u can issue just the fastboot flash command with your device off. when it sits at waiting for device turn your kindle on and it should flash.
[Kindle Fire Android Development] harry_fine:
Just for anyone reading this post, it worked fine, but didn't have to do the whole thing.

Took the advice above, shutdown the device, typed in (with the proper files present and the executable in my path):

fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img

I got a message that it was waiting for the device. Then I turned the device on and in about three seconds, TWRP2 had flashed.
[Kindle Fire Android Development] smirkis:
thank pokey9k for incorporating fastboot into the boot loader. easy peasy! lol
[Kindle Fire Android Development] ma678:
The first part doesn't work because I still get "fastboot: not found"; however, I solve it taking the advice below.

The second part works like a charm.

Thanks.

---------- Post added at 11:58 PM ---------- Previous post was at 11:57 PM ----------

It rocks.

Thanks a lot.
[Kindle Fire Android Development] dadeo1111:
bricked - no fff or recovery

I did this I found on the team win site with KF on, recognized by adb with device # listed:

Download file above. Execute the commands below from the command prompt with your Kindle connected to the PC.

adb shell

su

idme bootmode 4002

fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img

Device now boots to boot logo with green power led but no further. When connected it's now unrecognized, even after successfully reinstalling the driver - (delete, reboot, use kfu batch file). If someone will point me in the right direction I'd appreciate it.
[Kindle Fire Android Development] ammubarak:
You need to issue a next command to reboot as follows;

fastboot reboot
[Kindle Fire Android Development] dadeo1111:
I can't get fastboot - unrecognized. I connect and get the tone from windows like a usb device connected but adb now won't recognize it.. I've redone the driver 3 times - all seemed successful except the first time - I rebooted windows every step.
[Kindle Fire Android Development] kinfauns:
You'll need to get the situation with your device drivers corrected...

http://xdaforums.com/showpost.php?p=23747671&postcount=2

Make sure the correct interface name (shown in the table) to appear for both normal/recovery and fastboot modes.
[Kindle Fire Android Development] dadeo1111:
I was trying to get twrp back on after changing from it due to lack of support as per a poster here's recommendations. I had no problems going from twrp to cwm but did it using a batch file as I recall. CWM had been fine for me - worked to flash 2-4 cm7 roms - but I want to get ics cm9 soon and know that I need twrp. The rest I've posted to the best of my ability. All shell commands I issued went normally except the last one with the file. It didn't say file not found but used other language I forgot to write down - like unrecognized but unsure if that's it. At that point I should have typed fastboot reboot as I'm finding out now..but I didn't/ I held the button to reboot. And here I am..No FFF, No cw or twrp recovery and I can't get adb back to run fastboot..

I hope this is clearer - I'm really upset about this and having trouble even dealing with it rationally. I appreciate everyone's help and their patience.

---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------

Thanks kinfauns. My device mgr. indicates that they are installed - mine looks like the top right example:

Indicating Android Phone --> Android ADB Interface

But when I go to my folder with the sdk and open a cli there and type

adb shell

I get: "error: device not found"
[Kindle Fire Android Development] kinfauns:
I'm a little confused because you claim not to have FFF, but if you are in the top right corner there, you are in fastboot mode. In fastboot mode, you cannot run adb commands. Do you have the stock bootloader? What's on your screen right now? If you want to start this process over, you can probably just

fastboot oem idme bootmode 4000

fastboot reboot

and reboot into your installed CM7.
[Kindle Fire Android Development] dadeo1111:
FFF was installed and worked but I can't get to it now. The only thing I get is a boot logo - android bot with Kindle Fire text below. . not the stock logo. I reboot, hold the button down to get into recovery but it just shuts off instead...LED stays green till it goes off.
[Kindle Fire Android Development] kinfauns:
The KF logo with android (what you have now) is FFF 1.3...

http://xdaforums.com/showthread.php?t=1541043

That post will tell you how to do the recovery selection properly. If that doesn't work for you, you can get back to fastboot mode (using adb to set the bootmode again from your CM7), and reflash TWRP onto its partition.

http://xdaforums.com/showthread.php?t=1552547

You won't need the "-i 0x1949" part in fastboot with FFF as that's only necessary for the stock bootloader. You can find a review of adb and fastboot in the 3rd post of the thread above.
[Kindle Fire Android Development] dadeo1111:
Thanks very much kinfauns. I'll look at this and figure it out - but I wasn't lying that this has me freaked-out. I may have to come back to it later. I'll have to as it will eat at me..but right now I can't think clearly and don't think I should take a chance of making things worse.

So you say what messed it up is I had the wrong fff version? It figures..this is the first time I'd used adb for anything other than a status check - had never pushed or whatever.

---------- Post added at 03:31 AM ---------- Previous post was at 03:13 AM ----------

I'm confused also.. So, since the driver is installed properly according to my device manager matching the chart (the 2nd and 3rd reinstall also went like it did before when it all worked - unlike a time when driver install failed) why is it when I now attach my kindle to usb and type adb shell I get the device not found error? And what will I need to do to get adb shell to work again? Is it stuck in fastboot? ugh..sorry. :(
[Kindle Fire Android Development] kinfauns:
Stepping aside from it for a while can be a good idea when things aren't going right. It's a sensible thing to regroup. It might also be worthwhile to reread some of the articles and even the posts that were written in this thread. I often find things I've missed and gain a better understading the second time around.

FFF version 1.3 is the "latest" release. It's not wrong by any means. It will do everything you need it to do. I just wanted you to look at the instructions on how to get into recovery, so I didn't have to type it here again.

Regarding adb and fastboot, a quote from the beginner's guide...

The fastboot and adb commands require the Kindle Fire to be in specific states for the host computer to interact with the device. The fastboot tool needs the Kindle Fire to be in fastboot mode and cannot send commands to the device otherwise. Similarly, the Kindle Fire must be in recovery or booted to an operating system (with USB debugging enabled) for it to work with the adb tool. It's not possible to go back and forth between the two without at least rebooting the device.​

If you have the kindle fire with android logo, you are in fastboot mode and therefore cannot send adb commands to the device. You'll have to be in recovery or booted normally into the system to run adb commands. Again, take a look the link I referred to earlier about fastboot and adb commands. You'll find the commands you need to change the bootmode so you can get from one mode to the other and back again if needed.
[Kindle Fire Android Development] dadeo1111:
Typing the fastboot commands to change bootmode from fastboot to regular system and then rebooting did it.

I feel stupid. I'd read all that, really. That beginners guide of yours was great and posted so when I first read it. I think I have a better idea now what's what..but then I did before also. thanks again. I think I thanked your every post, heh.

I just checked and still have cwm so will have to do this again. I think I had the file path wrong. Wonder if I can flash this in recovery with the file on the sd card? More reading..thanks again.
[Kindle Fire Android Development] kinfauns:
It's out of the norm, but you can use adb shell to write it directly to your recovery partition.

adb shell dd if=/sdcard/wherever/you/have/twrp.img of=/dev/block/mmcblk0p5

To be clear, the "/sdcard/wherever/you/have/twrp.img" part has to be replaced with the actual location and filename of the twrp image you are flashing. I suggest you get version 2.1.1 from the twrp page. Be very careful to get the second part of the dd command (starting with "of") correct. You don't want to flash it to some other partition accidentally.
[Kindle Fire Android Development] dadeo1111:
I usually like alternative methods and find them useful for learning inner workings details - but after last night the little confidence I had that I wouldn't brick my device has dwindled.. I want normal - safe and normal.

TWRP upgrading seems to have several methods that work. Is there a way to flash or install the 2.1.1 twrp using cwm? That seems easiest now since I still have that. I'll do the adb or fastboot methods if nec but am curious if this will work.
[Kindle Fire Android Development] kinfauns:
Using fastboot is the "right" way to do this. You can't do it through the CWMR interface. You can also use smirkis' scripts to do it if you want to move some files around, but his script does essentially the same thing as the command I gave you in the last post. It's good to be cautious, but don't be afraid to try out some new things. Imagine all of the things you wouldn't know if you never messed up your Kindle Fire in the first place!
[Kindle Fire Android Development] dadeo1111:
This guy uses cwm to switch cwm to twrp. He installs twrp and then the just deletes cwm..

This is for the touchpad but seems like I could do the same with the fire and root explorer. Sorry to be a pain-in-the-butt.

Another question while you are here: If I do use the fastboot commands to move the new twrp over to the boot directory, will that overwrite the cwm recovery so it loads twrp or will I need to delete the cwm image?

---------- Post added at 05:56 PM ---------- Previous post was at 05:49 PM ----------

I think I see why not - the file types..one is an image, the other a zipped file for flashing - a rom, right?

So I get the kf into fastboot then execute:

fastboot -i flash recovery C:\kfu\software\openrecovery-twrp-blaze-2.1.1.img
[Kindle Fire Android Development] kinfauns:
If somebody took the time to write the proper install scripts and packaged everything inside of a zip file, then yes, it would be possible to do that. As far as I know, nobody has done that and made it available for the public.

Again, to be clear, you want to write to the recovery partition and not the boot partition. If you write it to the boot partition, "normal" boot will always bring you into the recovery program and not boot to the system. And yes, it will overwrite the entire recovery partition with the contents of the new recovery image. You can erase the recovery partition before flashing, but it's unnecessary.

Why the aversion to fastboot?

EDIT: No, the proper fastboot command is...

fastboot flash recovery C:\kfu\software\openrecovery-twrp-blaze-2.1.1.img

You drop the entire "-i 0x1949" when using the FFF bootloader.
[Kindle Fire Android Development] dadeo1111:
I learned computers on DOS in the 80s but I guess the gui now has me by the short hairs. lol I know that a well used gui has safeguards implemented that I don't have pecking in commands with a cli. . I was fairly sure I did no harm yesterday when I bricked but it shook my confidence and made me unsure about any step I took other than pasting in someone else's script.

I reread your most excellent fastboot/adb guide this morning - it helped but am still more secure with using a tried and proven gui..or the script as you mentioned.

What got me into this is that I'd been using the script methods and wanted to do more with the cli on my own..to build my confidence further.
[Kindle Fire Android Development] kinfauns:
The most important thing to know about troubleshooting/fixing the Kindle Fire is FFF. As long as you keep that intact, you can blow away anything else and still recover easily. Learn how to stop its temporary fastboot countdown when it boots up and get it to stay in fastboot mode. Then as long as you don't do something silly to affect the bootloader partition, like flashing it with the u-boot.zip file without unzipping it first (I read in the General section that someone did this), you are basically free to make all sorts of mistakes without major repercussions. With fastboot, you can flash a new recovery. With a new recovery, you can flash a new system. I get the whole confidence thing... just be sure you understand what you are doing before you do it and think about how you can recover if something goes wrong. You'll be fine.
[Kindle Fire Android Development] dadeo1111:
I'm out literally out thanks - only 8 per day, heh. I think where I went wrong yesterday was the file path. I tried once then rebooted manually leaving the kf in fastboot and me basically hysterical, lol. So I'm thinking this below will work.

adb shell

su

idme bootmode 4002

fastboot flash recovery C:\android-sdk-windows\openrecovery-twrp-blaze-2.1.1.img

Do I add a line to boot normally and one to reboot, or will the overwriting reset the bootmode?
[Kindle Fire Android Development] kinfauns:
This is what I was saying about FFF's temporary fastboot mode. With FFF installed, you don't need to jump through those hoops just to get into fastboot mode. When you first boot the device, FFF will start up and soon thereafter automatically give you the opportunity to send it fastboot commands. With the KF turned off, booted into recovery, started up in the system, whatever - send it this command...

fastboot getvar product

and it will tell you that it's waiting for device. Now reboot the Kindle Fire. As soon as temporary fastboot is enabled on the device, it will receive the command and reply with "product: kindle" as the output. You are now in fastboot mode and it will stay that way until you reboot it. So, now you can send the fastboot flash command.

Remember you never changed the bootmode to get here, so the bootmode is whatever it was before you rebooted. Now you can just...

fastboot reboot

and it will start back up in the previously set bootmode.
[Kindle Fire Android Development] dadeo1111:
adb shell

su

idme bootmode 4002

fastboot flash recovery C:\android-sdk-windows\openrecovery-twrp-blaze-2.1.1.img

I do the above and get:

fastboot: not found

I have verified the path is right and the file is there and named the way I typed the command..

---------- Post added at 06:58 PM ---------- Previous post was at 06:54 PM ----------

Thanks - will do this since I can't get fastboot to work..:confused:
[Kindle Fire Android Development] kinfauns:
Those directions are incomplete. It should tell you to reboot after the bootmode change. "fastboot" is a Windows command, not a linux shell command that can be run inside adb shell.
[Kindle Fire Android Development] dadeo1111:
Incomplete? OK.. Weird they post incomplete commands to use on the site. http://www.teamw.in/project/twrp2/79

I guess they assumed a certain amount of prior knowledge was had by the user.. My problem is differentiating and transitioning to and from adb to fastboot to windows shell commands.. I think I get it..

---------- Post added at 07:44 PM ---------- Previous post was at 07:17 PM ----------

TWRP on and working! That last gem about the incomplete commands and me disambiguating the adb from the fastboot commands did the trick and seems to have restored my lost confidence. :)
[Kindle Fire Android Development] kinfauns:
That's actually an improvement over what they had before for 2.1.x versions. The older set of instructions wouldn't flash it at all, but that's another story.

Congratulations on getting it all fixed up... now it's time to break it again and learn some more stuff.
[Kindle Fire Android Development] dadeo1111:
Thanks. Oh, I'm sure I will - break it I mean. I'm really wanting to try ics and it seems to do things a bit differently. I'm completely new to android and have used linux only a little over the years so almost everything I do has a learning curve and at 55 the old dog/new trix hurdle comes into play.

Anyways, you are so good at this I suggest you write a guide to sell on amazon. You'd be doing yourself and anyone that reads it a favor. Not much money to be made but more than what you are getting here..well, not so much pay in thank yous, gratitude, admiration and sheer hero worship as on this forum, heh. Speaking of - as soon as I get my 8 thanks for the new day I'll be over here hitting the Thanks button on a few of these posts that saved me.

I applaud your patience with me - it deserves a standing o.. It should not have taken so many exchanges to get to the meat of this - my bad, sorry. My reading comprehension must go to the same place my reasoning and logic does when I brick a device I can't afford, lol. (disability/fixed income)

---------- Post added at 08:43 PM ---------- Previous post was at 08:38 PM ----------

It's a wonder you do anything else then. I'm sure glad they did the update as twrp seems to be the go-to recoveryfor the KF and is, imo, simpler and more straight forward to use.
[Kindle Fire Android Development] kinfauns:
Nah, the guides I've written are available here for people to freely use to get on their feet. Hearing a couple of nice words or seeing that the person hit the "Thanks" button (the digital version of a handshake) is plenty for me.

I think of a lot of these things as a puzzle as I try to figure out what they missed... what knowledge they lack... the easiest path to the solution. Personally, I think KFU is more a curse than a blessing. "Back in the day..." you'd better have a fairly clear understanding of the process and what mistakes not to make before you started in on your device. Now, it's just like... "You say I just need to hit this button here? Well, I can do that!" and that just builds a false sense of confidence. It's great if everything goes to plan, but if something goes wrong, they start running around screaming, "The sky is falling!" and that's not a conducive environment to learn and build the necessary knowledge to fix something... and you always have to know more to fix it than you do to break it.

Anyway... thanks for your thanks and happy modding!

PS. ICS will likely break the Window device drivers that let you use adb with it. That shouldn't deter you from trying it since there's very little you need in terms of adb commands now that you have FFF and TWRP flashed on your system. Just be aware of it before you plod ahead. Good luck!
[Kindle Fire Android Development] dadeo1111:
Used newly acquired knowledge to put the latest fff from hash a little bit ago. The new twrp and now this near-bullet-proof fff on my Fire I'm feeling pretty good. I've been following along the 3.0 Kernel threads too - heard about the adb device id deal there in another thread -- but also heard hash is fixing it.:cool:.I think his will be the ics I'll try first. But not just yet. There are a couple cm7s I'd still like to look at anyway.

You mention KFU being a curse - I agree, but it saves a lot of time and pulls in folks, one way or another. I looked at the scripts source and it looked like it made sense, was safe, too complicated for me to spend a lot of time to learn, lol. I also read around. saw many great success stories, few real problems and noted how folks were messing up:mostly just impatience, or having the files in the wrong place..you know all about it.

The Fire is the #2 tablet so I expect many more dropping by to learn some android. Your guides will help them along the way..or they will scan them, see how complex using a cli is and send their Fire back to Amazon.heh. It's all good!

Talking about all these windows issues makes me wonder if there are any issues backing up to or storing backups on an ntfs..more reading. Thanked a few more of your helpful posts to me with my new supply of 8 Thanks clicks. :)
[Kindle Fire Android Development] portezbie:
I just switch from CWM to the latest version of twrp, no problems so far, except why does the screen flicker when I am in twrp? Is this just me or is it for everyone?

Is there a fix?

Thanks
[Kindle Fire Android Development] smirkis:
its "normal" in twrp.
[Kindle Fire Android Development] portezbie:
Thank you very much, good to know it's not just me.

Is there any reason to be concerned about this or is it just a small annoyance?

Probably just being paranoid but it makes me worried about damaging the screen or something.
[Kindle Fire Android Development] brizey:
It flickered on the thunderbolt, too.
[Kindle Fire Android Development] paulnsx:
Excellent recovery! Thanks for your work!!
[Kindle Fire Android Development] DangKid:
Can't search right now because I'm on mobile but I have TWRP 2.0 and FFF 0.8 on the kindle fire. Is there anyway to flash TWRP untethered or do I still need to flash through adb?

Sent from my Samsung Infuse running AOKP.